Hi guys,
We having strange problem with connecting to Modbus device, We are using Ignition v7.9.
The device connected for a sec and afterword it disconnected again over and over.
We have tried to use 3rd party software (Modscan32) without any problem.
Also we are able to connect another Modbus device without any problem.
What could be the problem?
Are you actually successfully reading at least one tag? Most Modbus devices will time out if nothing is being polled.
Yes I am able to read and also write with modscan32.
any logs?
can you post an example of how you have this tag setup in Ignition as well as the device configuration?
This screenshot shows Modscan32 targeting slave/node address #1. Ignition defaults to using node zero if not specified in its manual addresses.
The problem is at a higher stage with the connection itself (before I added a tag I am able to connect to the device at the gateway)
First you create a device connection.
Secondly, then you create a tag and poll.
If you don't do the second operation, the first will disconnect as a result.
Some devices are also badly behaved (abrupt disconnect) when asked for addresses or queried with functions they don't support. Instead of replying with the error code(s) required by the specification.
A wireshark capture may be required to definitively diagnose this device's behavior. (Captures of both the working Modscan and the non-working Ignition.)
The OP has also not yet provided the OPC Item Path involved here. It might be something simple, but we aren't magicians.
We aren't. You are. 
Don't test with a whole UDT. Test One tag, corresponding to your Modscan32 sample.
The error indicates that the device is abruptly disconnecting. Very bad behavior.
If you get that with a single tag on the Ignition side, using an address known to work with Modscan, then you will need to perform wireshark captures. (Are you running Modscan from the gateway server? If not, there may be other firewalls interfering.)
Was just about to say that but saw Phil was typing and knew he would put it more succintly.
Ensure you disable that UDT from polling before you try reading the single tag.
The situation is similar with one tag. wireshark I installed i checked the situation in the modbus network nothing like that in the traffic. only successful read/write. but I see PLC IP 10.118.44.245 Server IP 10.118.50.35 maybe that's the problem?
Please post the actual capture files. A screenshot of a capture is useless.
ilan,
Did you ever found it what was the problem is? I'm having the same issue with a Moxa Cellular Gateway.
Thanks,
Start a new topic with as much relevant information as you can instead of reviving more than one old topic.
Understood.