# 1756-L61/B Rev. 20.019

**URL:** <https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588>\
**Category:** Ignition\
**Created:** [March 17, 2021, 5:59pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588 "2021-03-17T17:59:36Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![toddhowden](https://avatars.discourse-cdn.com/v4/letter/t/2acd7d/32.png) [@toddhowden](https://forum.inductiveautomation.com/u/toddhowden)\
**Post date:** [March 17, 2021, 5:59pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/1 "2021-03-17T17:59:36Z")

</div>

Has anyone had issues connecting to an AB 1756-L61/B controller running version 20.019? I have been able to connect similar controllers with earlier versions without issue but have difficulty getting this controller to read. Recreated and verified addressing and slot information. No issue connecting to it and going online with RSLogix. Just can’t get a good connection in Ignition. When using Quick Connect values come back as bad. I am using the Legacy AB ControlLogix driver for ver. 20 and prior.  
Thanks,

---

<div class="post-metadata">

**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\
**Post date:** [March 17, 2021, 6:04pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/2 "2021-03-17T18:04:39Z")

</div>

Try the newer driver. Rockwell, bless their hearts, updated the security in the firmware at 20.19.

---

<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:** [March 17, 2021, 6:06pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/3 "2021-03-17T18:06:29Z")

</div>

Being on firmware 20.19 is a worst-case scenario for performance. You have to use the newer Logix driver but it also doesn’t actually support the newer instance-based tag reads so the driver has to fall back to symbolic access.

---

<div class="post-metadata">

**Author:** ![toddhowden](https://avatars.discourse-cdn.com/v4/letter/t/2acd7d/32.png) [@toddhowden](https://forum.inductiveautomation.com/u/toddhowden)\
**Post date:** [March 18, 2021, 4:45pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/4 "2021-03-18T16:45:28Z")

</div>

Thanks. Will check it out.

---

<div class="post-metadata">

**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\
**Post date:** [November 30, 2022, 9:12pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/5 "2022-11-30T21:12:43Z")

</div>

This information helped me troubleshoot a very confusing problem in a test environment. I had to convince some people that upgrading from 20.18 to 20.19 actually breaks stuff in an existing Ignition SCADA.

It's certainly unintuitive for a minor revision to completely change everything but that's what Rockwell did. I think Rockwell should have made that a major revision because of the far reaching impact of the change and the perception that people have of minor revisions.

Thanks for the information.

---

<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 30, 2022, 9:24pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/6 "2022-11-30T21:24:57Z")

</div>

> [@Steve\_Laubach](#):
>
> Rockwell should have made that a major revision

It was, actually. Rockwell _ **backported** _ the security changes from v21 to v20 to accommodate some processor models that cannot run v21+.

---

<div class="post-metadata">

**Author:** ![toddhowden](https://avatars.discourse-cdn.com/v4/letter/t/2acd7d/32.png) [@toddhowden](https://forum.inductiveautomation.com/u/toddhowden)\
**Post date:** [December 1, 2022, 12:17pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/7 "2022-12-01T12:17:39Z")

</div>

Thanks again for the additional information. Not a fan of version 20 and have been working around it.

---

<div class="post-metadata">

**Author:** ![Steve\_Laubach](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_laubach/32/60900_2.png) [@Steve\_Laubach](https://forum.inductiveautomation.com/u/Steve_Laubach)\
**Post date:** [December 1, 2022, 1:25pm UTC](https://forum.inductiveautomation.com/t/1756-l61-b-rev-20-019/44588/8 "2022-12-01T13:25:39Z")

</div>

Thanks for the information. That's hilarious.

That explains why I was told to use the new driver for 21 and the old driver for \<21 and that later changed. I must have gone through Ignition training between the release of 21 and the backporting.
