NTP protocol of the ION 8650

[Rafaelsdsz]

Hello,

We are having problems with a GPS that synchronizes with ION 8650 meters via NTP protocol. This issue is occurring with two firmware versions of ION meters.

On client 1 we have the following scenario:

ION 8650 meters with firmware version 004.031.002, synchronized with GPS via NTP, configured with a 1 hour sync interval present the following failure:

We have 18 meters with the settings, being synchronized via NTP protocol with GPS and so far 9 meters have this type of failure without simultaneous synchronization error, and another 9 meters in the same GPS network do not have any fault. The meters request sync, which supply wrong data and time works for 1 hour as programmed in the sync interval and return to true data and time. What causes data storage at wrong data and times on the client.

On client 2 we have the following scenario:

ION 8650 meters with firmware version 004.040.001, synchronized on the same network with GPS via NTP, configured with a 1 minute sync interval at which they present the following failure:

We have 4 meters with the settings, being synchronized via NTP protocol with the GPS and so far 2 meters have this type of failure without simultaneous synchronization error, to which the other 2 meters on the same network do not differ any failure. The meters ask for sync, where providing wrong data and time works for a few minutes and returns to true data and time. What causes data storage at wrong data and times on the client.

What version of NTP or SNTP are the ION8650 meters using?

Have there been any NTP protocol changes in the latest firmware updates?

What might be causing it to fail?

[Juan_Arias]

@Charles_Murison  

[Charles_Murison]

Hello @Rafaelsdsz 

What version of NTP or SNTP are the ION8650 meters using?
I am not 100% sure, but I believe this is V3. I know for sure V4 is not supported on the meter. Most V4 servers are backwards compatible to V3 devices.

Have there been any NTP protocol changes in the latest firmware updates?
No changes that I know of.

What might be causing it to fail?

Cannot say from this data alone. 

If possible would be good to get packet captures from this system. 
Ideally with a switch port mirroring the traffic to/from the meter to a second port where computer is capturing the Ethernet traffic. Wireshark is a common software to do this. The port mirror is important, may switches will hide traffic from ports it knows the traffic does not concern. So you might see the meter send out messages but never see what is sent back to the meter.

If you are able to capture the Ethernet traffic, would also be good to get the event log from the meter.

Regards,

Charles