We are encountering communication issues between our modem RUT906 and our PLC Schneider M241.
They are connected using an Ethernet cable.
The number of satellites is updated correctly but the GPS coordinates are only updated restarting the machine.
I looked into all the settings in Services > GPS and was not able to find an explanation for this.
AVL & NMEA settings are all configured to their default state.
Do you know which settings impacts the data sent by Ethernet to a PLC ?
By “restarting the machine” I meant the RUT906.
The firmware version of the RUT906 is RUT9M_R_00.07.14.3
We tried with newer firmawer but the issue remained.
After talking with our developper, here is how we get the data we want from the modem.
He configures the PLC as a TCP Modbus master and the modem as a TCP Modbus slave.
The PLC is then set up to read specific Modbus registers corresponding to GPS data, such as latitude, longitude and number of satellites.
From our tests, the number of satelites is updated correctly but the GPS position is never updated even we move 40 to 50 meters.
Is there a possibility that the GPS coordinates registered data is not being updated in the modem ?
Thanks for providing more information. Regarding the GPS coordinates, they should be updated regularly, both the longitude and the latitude values as well.
And double check the GPS Longitude and GPS latitude register values & representation (data types) shown in the table, and compare them to your settings to ensure that they are correct?
I’d also like to ask about the GPS antenna that is being used & the environment that the Teltonika device is being used in. What kind of antenna is it, and what environment are you guys testing this scenario in?
I have verified the GPS Longitude and Latitude register values and data types and they are correct.
We use a Hemisphere GNSS A52 antenna.
We tested moving a rover forward and backwards in a field. The max distance was under 50 meters.
I’ve sent you a form to fill out so we can continue our conversation in private, to avoid accidentally leaking any sensitive information. In the Ticket ID field, simply enter the thread’s number, which is 14610.
