# OPC UA comunicating with AB L32E Firmware 20.19

**URL:** <https://forum.inductiveautomation.com/t/opc-ua-comunicating-with-ab-l32e-firmware-20-19/12368>\
**Category:** Ignition\
**Created:** [November 16, 2016, 10:38pm UTC](https://forum.inductiveautomation.com/t/opc-ua-comunicating-with-ab-l32e-firmware-20-19/12368 "2016-11-16T22:38:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![eduardra](https://avatars.discourse-cdn.com/v4/letter/e/ecc23a/32.png) [@eduardra](https://forum.inductiveautomation.com/u/eduardra)\
**Post date:** [November 16, 2016, 10:38pm UTC](https://forum.inductiveautomation.com/t/opc-ua-comunicating-with-ab-l32e-firmware-20-19/12368/1 "2016-11-16T22:38:06Z")

</div>

I was testing the Ignition software. Tested it with a Spare Allen Bradley PLC with firmware V17. Worked great. Later to standardize to my production PLCs, I tested with the same PLC but with firmware V20.19  
After this change the OPC server can see the tags but the actual data on the tags is reported as Value NULL and Quality Unknown. In the tag browser the tags show up with a green question mark.  
My Ignition version is 7.9.0 and my OPC-UA Version is 4.9.0. I’m getting to the point i think the Ignition software can’t communicate with AB firmware 20.19. Any advice on this?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 17, 2016, 12:43am UTC](https://forum.inductiveautomation.com/t/opc-ua-comunicating-with-ab-l32e-firmware-20-19/12368/2 "2016-11-17T00:43:20Z")

</div>

Allen-Bradley apparently updated the security in v20.19 firmware with the same restrictions as in v21+. Use the v21 driver in this case. There’s no help for the loss of performance, as the previously available direct memory access was a key optimization in the older driver.  
Or go back one revision on your firmware.

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [November 17, 2016, 4:51am UTC](https://forum.inductiveautomation.com/t/opc-ua-comunicating-with-ab-l32e-firmware-20-19/12368/3 "2016-11-17T04:51:16Z")

</div>

This is discussed here as well: [inductiveautomation.com/forum/v … 53&p=59786](https://inductiveautomation.com/forum/viewtopic.php?f=92&t=16353&p=59786)

---

<div class="post-metadata">

**Author:** ![Dan\_Bridgeman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dan_bridgeman/32/3610_2.png) [@Dan\_Bridgeman](https://forum.inductiveautomation.com/u/Dan_Bridgeman)\
**Post date:** [February 1, 2021, 12:49am UTC](https://forum.inductiveautomation.com/t/opc-ua-comunicating-with-ab-l32e-firmware-20-19/12368/4 "2021-02-01T00:49:04Z")

</div>

Would it be possible to modify the description of the new driver to specify that it is necessary for v20.19? It’s misleading to have it say that it’s necessary for v21+, and that the legacy driver is good for all up to v20.