- This topic has 7 replies, 3 voices, and was last updated 1 week ago by
.
-
Posts
-
I have a device that uses the Modbus protocol, but it operates within an internal network. I connect it to the public network through a router. It logs into my cloud server and sends a hello packet to inform the server of its identity. Subsequently, my cloud server communicates with the device using the Modbus protocol. How should I configure my network to communicate with the device?
I noticed that TcpServerChannelLogic has implemented hello packet handling, but it might not be able to collect a complete hello packet.
If you have a router, then you are probably building a network between the router and the server, the network settings do not relate to the settings of the Modbus device. You need to figure out the network. There are several different options, depending on the construction of the network. As a rule, you need to ensure the availability of devices behind the network of the router that connects to you.
The topic doesn’t really relate directly to scada, more to network settings.
There was an error in my description. The actual situation is as follows: my device cannot access the internet, and it supports the Modbus RTU protocol. I have installed another networked device on this equipment, which is custom-developed. It can connect to my cloud platform and is also connected to the non-internet-enabled device via 485. When the networked device connects to the cloud platform, it sends a hello packet.
I have installed another custom-designed network device on this equipment.
So we need to figure out how it was planned to work? It should be something like an interface converter with TCP Client mode.
To understand, you need to know what kind of device you have made for communication.
- You must be logged in to reply to this topic.