Modbus TCP Device Issue

Ignition
1

Hi Guys,

I connected a Comet P8641 (Modbus TCP 4 channel temperature monitoring unit) to my desktop PC on a local network and was able to add the device to a trial version of Ignition I have running on my desktop.

I then added all the tags and was getting values.

I then disconnected it from my local network, connected it to our automation network (which has a bunch of Modbus TCP devices communicating happily through port 502), added it to our gateway (status says connected and I can ping it) and copied and pasted all the tags from my local Ignition to our corporate one.

Unfortunately all the tags’ quality is ‘Uncertain_InitialValue’…

Any ideas?

2

My colleague took a look and instead of adding tags via the designer tag browser he added a tag to the OPC Server via the gateway → OPC UA → Device Connections → {Device} → More → Addresses

Not working tag (added through designer tag browser):

image
image1699×349 38.3 KB

Working tag:

image
image1699×351 37.1 KB

As you can see they are configured identically.

I believe he has discovered a bug and a work around - just thought I would share.

3

The OPC Server name is different.

4

Ahhhhh! Thanks Kevin!

5

In a recent version we cleaned up the error diagnostics on tags that have an incorrect OPC server name:

image
image1624×356 42.2 KB

and

image
image2024×1524 395 KB

Hopefully this helps people out in the future.

2 Likes