We are using TRB145 as modbus serial cllient with selected “Schedule: 10:00:00” in “Frequency” tab. Our client wants once a day at 10 a.m. to read a value. We are sending that value through MQTT with “data to server“ and save it to database on our server. Everything works okey, every day we have a value at 10:00:00 but sometimes we have values also at 09:59:59, 00:00:00 or 23:59:59. When this happens I go to teltonika device and see that there is more than one request per day when it should be exactly one at 10:00:00. Cant find why is that?
Hi,
This has to be related to your device’s configuration.
Can you share your “Modbus Serial Client” and “Data to Server” configuration screenshots?
Hello,
To better understand your setup, could you please share screenshots from your TRB Modbus serial client configuration as well as from your Data to Server configuration to see how the Modbus request polling is interacting with the data publishing process?
Best regards,
Modbus Serial Client configuration: I have one modbus serial device (DFM) and 2 configurations with different frequency (DFM-2,DFM-3) connected to it. The first one is on 60 seconds period with 6 parameters and the second one is on schedule at 10:00:00 with only one parameter.
Data to server configuration: type MQTT with 5 min period to send all data collected from modbus parameters.
Hello,
Apologies for the delay. I just wanted to follow up and ask whether the Modbus data to server sending discrepancy is still noticeable.
If so, as I understand, both of these Modbus Serial Client configurations are for the same physical meter, correct? In that case, please try increasing the timeout values to 5 and, for testing purposes, set the QoS parameter in the Data to Server configuration tab to 0.
Also, please make sure your TRB is running the latest stable firmware release.
Best regards,
Yes, both of these Modbus Serial Client configurations are for the same physical meter. But we have multiple physical meters with the same configuration and the discrepancy is the same everywhere.
Which timeout to increase to 5, the one in modbus device or the one in data to server? But why to put QoS to 0 (“fire and forget” messaging with no acknowledgment from the receiver)? We could miss some messages. The QoS should be 1 or 2.
The TRB devices were with latest stable firmware when they were installed on different sites. The one that the screenshots were taken from is with firmware 07.15.2, all trb devices are with different firmware. The problem is that I don’t want to upgrade firmware when the device is 500 km from us and if something happens when upgrading (because of the mobile network etc.) we can’t do anything fast enough and it will stop working.
Update: I have increased both timeouts to 5 and the discrepancy is the same as before.
Hello,
Thank you for the update. In this specific case, to understand and troubleshoot the situation better, we’ll need to continue this process privately, because sensitive/publicly unshareable information, such as the troubleshoot file, configurations, logs, etc., needs to be collected.
You should find a support request form in the inbox of the email address you used for your forum registration. Kindly fill out the form, and please reference Ticket ID: 15681 when submitting it. Once the form is completed, we’ll contact you directly via email to investigate the issue in detail and help work towards a solution.
Best regards,
This topic was automatically closed after 60 days. New replies are no longer allowed.