OPC UA driver defenitions?

Ignition
1

Hello all;

we are currently tracing back an issue were L7X controllers expirence fault code 62…meaning a Major Non-Recoverable Fault and completed erased the PLC. in researching tag writing types (DMA or Symbolic instance - tag name), we’ve found with newer controllers you want symbolic because the memory in newer controllers is free-form. meaning one moment it may be set for a tag, the next its memory for a rung.

my question is can someone define the differences between opc-ua driver 2.7.0 and 2.7.1 rc3. more specifically relating to what i stated above.

any help is greatly appreciated.

2

Are you using the new Logix v21+ driver that was released with 7.7 or the legacy ControlLogix/CompactLogix driver?

3

well we have 2 sites using ignition, with one site using 2 servers, not in redundancy.

site one is running ignigtion 7.7.1 rc3, opc-ua driver 7.7.1 rc3

site two, server one is running ignition 7.7.0, opc-ua driver 2.7.0
site two, server two is running ignition 7.7.0, opc-ua driver 2.7.0

4

Next to the device entry in the gateway does it say “Allen-Bradley ControlLogix” or “Allen-Bradley Logix Driver”? The former means you’re using the legacy driver for v20 and prior controllers, the latter means you’re using the new v21+ driver.

The v21+ driver uses symbolic or instance id addressing when doing reads and writes; it does not use memory location based addressing. This is no longer possible in firmware v21 and newer and is the reason a new driver had to be developed in the first place.

I’ll have to check if the older driver uses memory location addressing for writes - I suspect it does, but this is allowed in v20 and prior firmware versions.

5

it looks to be on all 3 servers that we are using the legacy driver. can you please research the addressing for writing for this driver?

thank you so much for the quick responses and support.

6

I confirmed with the developer of the older driver, it does not use memory location based addressing when doing writes.

7

Thank you very much for the quick responses.

That’s what I needed clarification on.

Thanks again.