ControlLogix via Ignition Edge – Browse Works, Values Bad_NotConnected

Ignition
1

I’m troubleshooting an issue where Ignition (via an Edge gateway) can browse ControlLogix tags, but cannot read values. All tags show Bad_NotConnected. Below is a summary of what has been checked and the current state. I’ve had Ignition tech support check gateway configuration with me and was told everything seems OK there. I’ve also had the vendor/OEM check their firewall and PLC configuration and they said everything seems OK there.

Architecture

  • ControlLogix PLC with:

    • CPU in slot 0

    • Safety module in slot 1

    • Spare slots in 2–3

    • EN2T in slot 4

  • Ignition Edge gateway connects directly to the EN2T IP

  • Main Ignition gateway uses a Remote Tag Provider, but the issue occurs even locally on Edge

What is working

  • Device connection shows Online

  • OPC Quick Client can browse tags

  • PLC tag metadata is visible

  • Driver used: Allen‑Bradley Logix Driver

  • PLC firmware is compatible

  • Vendor/OEM confirmed:

    • PLC tags have External Access enabled

    • PLC configuration appears correct

What is NOT working

  • Tag values do not update

  • All tags show:

    • Quality = Bad_NotConnected

    • Value = Bad_NotConnected

  • Same behavior occurs:

    • In Designer

    • In OPC Quick Client

    • On the Edge gateway itself (so not a remote tag provider issue)

2

In the Edge Device connection setup, did you specify the slot of the Processor? Is it set correctly? It should be set to the slot of the Processor it’s getting the tags from, not the Ethernet module it’s connecting to.
0 is the default but I have accidentally set that incorrectly thinking it was the setting above or below it before. Might not be the problem but you didn’t mention that as part of your setup.

3

If you see tags in the browser then add a tag from there and check it's value that way. Add a point that is valid like the plc's time in seconds.

4

I tried to mess around with that and put 4,0 as my path as the EN2T is slot 4 but then I was not able to browse through the tags

5

It doesn’t matter what slot your ethernet module is in. If your processor is in slot 0, it should just be 0. This isn’t like a comms path in an explicit message.

6

it is slot 0 yes

7

Then that setting should be 0

8

It is.. I was trying other paths as part of troubleshooting but i agree that that is not the solution so the slot value is back to 0 and connection path is not being used.

9

Bad_NotConnected isn't even a StatusCode used by the Logix driver. You must have something else funny going on - maybe your loopback OPC UA connection isn't even functioning, or you're accidentally pointing to / connected to another server somehow.

2 Likes
10

OK.

Silly question, have you tried restarting any of the tags? If you right click on one in the tag browser in your designer, there should be a Restart Tag option.

11

On the status > modules page I can see that OPC UA is Active and Running. When I go to the tag editor for one of my bad tags I see that the OPC server is Ignition OPC UA Server and the Item path is ns=1;s=[VanRX_PLC]QIT191.Tag, so I think that all looks OK

12

Just tried that but no change :frowning:

13

I re-added tags from the browser but once they are added and I drill into them I just see bad_notConnected

14

What firmware is the processor? Are you sure you're using the right driver for the firmware of the processor? Logix driver is for firmware v21+ but use the regular AB driver for older firmwares.

When using the OPC quick client is it able to read/subscribe to tags without issues or do you get the same error?

Can you send screenshots of your configuration of the driver and anything else relevant? Sometimes it can be something else that you might be overlooking that another set of eyes catches.

1 Like