bionhill.blogg.se - Modbus server and device not communicating

#MODBUS SERVER AND DEVICE NOT COMMUNICATING DRIVERS#
#MODBUS SERVER AND DEVICE NOT COMMUNICATING UPDATE#
#MODBUS SERVER AND DEVICE NOT COMMUNICATING DRIVER#

#MODBUS SERVER AND DEVICE NOT COMMUNICATING UPDATE#

Modbus 2: version 2.5.057 (contact Engiby if an update is needed).This has been implemented in the following versions:

#MODBUS SERVER AND DEVICE NOT COMMUNICATING DRIVERS#

To be able to share the Open Data Mode (communication mode used for open TCP/UDP) between several drivers (even using different TCP ports), the communication drivers must use a specific mechanism.

#MODBUS SERVER AND DEVICE NOT COMMUNICATING DRIVER#

Modbus TCP dosn't work in parallel of the EIBNet/IP driver In this case, less TCP connect/disconnect is needed and the handling of the internal sockets is improved. It such difficulties remains, it may be worth to place one Modbus Link FBox for each Slave station (up to 10 are possible). UDP is not specified as possible option in the Modbus specification but work well also. If possible use the UDP protocol instead of TCP. After a socket is closed (normally or because of broken link) the firmware needs some time to free the unused sockets.Įnsure that you are using a recent firmware and Modbus driver. This is partially due to the fact that the PCD has a limited number of internal sockets. In some cases, difficulties have been noticed to reconnect slaves after a break of the link (broken cables or powered off devices). Adjust it in "Slave application" FBox.ĭifficulties to reconnect after broken link The default value is 1, but some master send the request with address 0 or other. This is shown online in the "Master Link" FBox.

Check the station address to which the master sends its request.

This error is also indicated by the error 'Application timeout' in the Master FBox. In a simple slave program, after the "Slave Link" FBox a "Standard Application" FBox must be placed.

You did not place any application FBox.

TCP connection is possible but not replay is received by the master. These remarks are also valid if UDP is used. If this don't work, don't look further for a Modbus problem. If possible try to establish a PG5 connection with the online option 'SOCKET' from the same point as the Modbus master. If you are connected over a router, ensure that the TCP or UDP port 502 is open and routed to the correct IP address.Įnsure that that Saia PCD ® configuration is correct: IP communiation activated, correct IP address and subnet mask. LAN installations are generally of good quality, but ensure that all patch cables are placed correctly. If no TCP connection is possible from the master, it is most probably a cabling problem, a bad network configuration or a configuration error of the Saia PCD ®. Typical troubles with the Modbus Slave Driver Here you can fined the list of the last modifications of the Modbus 2 driver : Modbus 2 History In very rare cases you may also encounter known and fixed problem of the driver itself.

Note also that a lot of information is also given in the Modbus FAQ documents Note that a good knowledge of the partner device is necessary to correctly configure the driver on the Saia PCD ®.įor trouble shooting Modbus RTU and ASCI (serial), please refer to this document: Modbus Trouble shooting This document may help you to solve problems you may encounter when using the Modbus TCP protocol with the Engiby driver on Saia PCD ® systems.