ok, I have configured DSPLE to have ModbusRTU slave on its rs485 port, Modbus TCP slave and BACnet/IP slave on its ethernet port.
I am passing some data between all the slave ports, no problems.
Now, I use one client software to monitor all three ports, Modbus RTU is solid, BACNet/IP is solid, but Modbus TCP keeps dropping in and out.
Is there something funky about DSP's modbus TCP slave driver and tcp socket closures? It looks as if once in a while when I write or read from that TCP port DSP shuts the TCP socket down and reopens it later.
As I said, BACnet/IP coming out of same ethernet jack is sold.
any ideas?
thanks.
I am passing some data between all the slave ports, no problems.
Now, I use one client software to monitor all three ports, Modbus RTU is solid, BACNet/IP is solid, but Modbus TCP keeps dropping in and out.
Is there something funky about DSP's modbus TCP slave driver and tcp socket closures? It looks as if once in a while when I write or read from that TCP port DSP shuts the TCP socket down and reopens it later.
As I said, BACnet/IP coming out of same ethernet jack is sold.
any ideas?
thanks.