FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
257 views 6 comments
by anonymous

The manual says 

Modbus TCP over Serial Gateway

The Modbus TCP over Serial gateway serial type allows redirecting TCP data coming to a specified port to an RTU specified by the Slave ID. The Slave ID can be specified by the user or be obtained directly from the Modbus header.

This RUT 955 worked for a bit for sending Modbus data via the WAM port then stopped working. Since I was having other issues such as randomly not being able to reach the WUI from the WAN side I upgraded the firmware to the latest and the WUI changed. Now when I setup the new Modbus TCP over serial it does not work. There is no information on this anywhere. I can get to the RUT 955 when I enable the Modbus TCP over serial option but I get a time out. I cannot enter slave devices as before under the Modbus serial master. I assumed that it just passed all IDs from the Modbus TCP to serial interface and waited for a response. 

1 Answer

0 votes
by anonymous

Hello,

  

Thank you for reaching out!

Could you try deleting the created Modbus TCP over Serial Gateway configuration and re-create it?

I'd also like to ask you to attach a troubleshoot file. It can be generated by navigating to System → Administration → Troubleshoot and can be attached to the original post.

A few more suggestions:

  • Make sure the IP Filter contains the IP of the device that is connecting to the router or simply enter 0.0.0.0/0 (this will allow all of the machines from LAN to connect);
  • The listening IP should be the IP address of the RUT955;
  • Make sure the Slave ID is of the Modbus RTU device;
  • Baud rate is the same on both ends;

   

Best regards,
DaumantasG 
by anonymous

I have tried all of your suggestions. Which I have already tried many times. Here is the event log.

image

EVENTS LOG

Events per page

ID

DATE

EVENT TYPE

EVENT

239 2023-02-02 14:38:19 Web UI Authentication was successful from HTTP 192.168.88.246
238 2023-02-02 14:27:16 Web UI Authentication was successful from HTTP 192.168.88.246
237 2023-02-02 14:27:05 WiFi WiFi client disconnected: 90:32:4B:0F:C1:5F
381 2023-02-02 14:26:35 DHCP Leased 192.168.1.172 IP address for client 90:32:4b:0f:c1:5f - DESKTOP-368NUG5 in WiFi
236 2023-02-02 14:26:31 WiFi WiFi client connected: 90:32:4B:0F:C1:5F
916 2023-02-02 14:25:29 CONFIG firewall configuration has been changed
915 2023-02-02 14:25:29 CONFIG rs_modbus configuration has been changed
914 2023-02-02 14:25:20 CONFIG firewall configuration has been changed
913 2023-02-02 14:25:19 CONFIG rs_modbus configuration has been changed
912 2023-02-02 14:25:13 CONFIG firewall configuration has been changed
911 2023-02-02 14:25:13 CONFIG rs_modbus configuration has been changed
910 2023-02-02 14:25:13 CONFIG firewall configuration has been changed
909 2023-02-02 14:24:55 CONFIG firewall configuration has been changed
908 2023-02-02 14:24:35 CONFIG firewall configuration has been changed
907 2023-02-02 14:22:36 CONFIG rs_modbus configuration has been changed
235 2023-02-02 14:21:54 Web UI Authentication was successful from HTTP 192.168.88.246
380 2023-02-02 14:19:09 Network Operator Connected to AT&T EIOTCLUB operator (internal modem)
379 2023-02-02 14:19:09 Network Type Joined LTE network (internal modem)
378 2023-02-02 14:19:09 Mobile Data Mobile data connected (internal modem)
377 2023-02-02 14:19:02 Network Operator Connected to AT&T EIOTCLUB operator (internal modem)
376 2023-02-02 14:19:02 Network Type Joined LTE network (internal modem)
375 2023-02-02 14:19:02 Mobile Data Mobile data connected (internal modem)
374 2023-02-02 14:18:48 Mobile Data Mobile data disconnected (internal modem)
373 2023-02-02 14:17:19 Network Operator Connected to T-Mobile EIOTCLUB operator (internal modem)
372 2023-02-02 14:17:19 Network Type Joined LTE network (internal modem)
by anonymous
Hello,

Events log will not provide me with much information, thus troubleshoot file will be required here.

Best regards,
DaumantasG
by anonymous

https://community.teltonika-networks.com/?qa=blob&qa_blobid=12167402020589082922

Here is the trouble shoot file. One of our engineers just completed a call with Teletoika trying to fix it. They played with some settings but were unable to fix the issue. They said to check the connections but it was working and does work with another master. Also I see no data at all on the RS-485 port. If you have no suggestions I will return the unit and try another one. 

by anonymous
If you already have contacted our engineers directly, then it's most likely better to continue the query there.

There are also ways of verifying functionality of the RS ports. For example you could set the RS485 port to Console mode and log if there is any output.

  

Best regards,

DaumantasG
by anonymous
I have contacted Teltonika directly and I have tried here but nobody seems to be able or willing to help. Very disappointed.
by anonymous

Hello,

  

could you try setting the Slave ID manually? The listening IP should also be 0.0.0.0.

Also, I can see that your IP Filter rule is either misconfigured or missing. In the Modbus TCP over Serial Gateway configuration, open your instance, scroll down to the IP filter, select the Interface as WAN, and enter the IP address 0.0.0.0/0. This will allow all traffic to reach this service, and if it helps it can be narrowed down to the exact client IP for security reasons.

  

Let me know if this helps!

Best regards,
DaumantasG