(Previously the Profile checkbox was unchecked under Advanced Meter Settings. Sometimes Kamstrup water meters need that since they don't have two way communication to the Kamstrup Water Concentrator, and you cannot order profile from them like you can from Electricity Meters. Kamstrup meter orders are generally not done until the meter is 70 hours old, because readings should come in automatically, and be picked up in the UtiliDriver Autofeed, which is a rolling 72 hours record of the records that were recently read. We should not insert autofeed values if the meter maxdate is older than the autofeed, if Profile is selected - in that case we should create meter read orders on the server, that will communicate to the meter via the Electricity Concentrator or repeater, and read the old profile from the meter itself)

This message was transcribed from Whatsapp support

which corresponds with what we have on pnpscada:

Therefore the reason pnpscada is not up to date to today is because the kamstrup server autofeed is not up to date

Unfortunately pnpscada builds on the foundation of the UtiliDriver Kamstrup server and its ability to read the Kamstrup METER in a timely manner, and if that is not in place, there is nothing we can do about it from our side.

In the case of this particular meter, the problem is between the kamstrup server and the meter

To troubleshoot this specific problem, just browse
http://x.x.209.x/utilidriver/api/collection/meters/4B414D00000001F0XXC/readings/   (url changed to protect customer privacy and security)

that 4B414D00000001F0XXC denotes the meter itself, you can find it in pnpscada under Edit->Meter Details under the multidrop id.

This will give you the 72hour auto feed, just for this meter

it is xml

there is a funny thing with the Autofeed though, and that is that the actual time of the readings in the autofeed is based on when it came in (72 hour window) not the date of the data