# Micro820

**URL:** <https://forum.inductiveautomation.com/t/micro820/8881>\
**Category:** Ignition\
**Created:** [August 8, 2014, 1:47pm UTC](https://forum.inductiveautomation.com/t/micro820/8881 "2014-08-08T13:47:59Z")\
**Posts on this page:** 13\
**Page:** 3

<div class="post-metadata">

**Author:** ![jamshidzade](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jamshidzade/32/24927_2.png) [@jamshidzade](https://forum.inductiveautomation.com/u/jamshidzade)\
**Post date:** [June 19, 2021, 7:46pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/41 "2021-06-19T19:46:50Z")

</div>

Yes its works fine thanks for your help

---

<div class="post-metadata">

**Author:** ![Antoine\_Rvl](https://avatars.discourse-cdn.com/v4/letter/a/8491ac/32.png) [@Antoine\_Rvl](https://forum.inductiveautomation.com/u/Antoine_Rvl)\
**Post date:** [August 11, 2021, 2:11pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/42 "2021-08-11T14:11:21Z")

</div>

@Kevin.Herron  
Is there any update regarding \*\* EIP driver for the 820/850 Micros \*\* ?  
I really would like to avoid doing modbus mapping with micro820.

---

<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:** [August 11, 2021, 2:14pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/43 "2021-08-11T14:14:38Z")

</div>

Sorry nothing has changed. Still going to do it eventually, still lower priority than other projects.

---

<div class="post-metadata">

**Author:** ![Kevin\_Klusman](https://avatars.discourse-cdn.com/v4/letter/k/cab0a1/32.png) [@Kevin\_Klusman](https://forum.inductiveautomation.com/u/Kevin_Klusman)\
**Post date:** [January 6, 2022, 9:19pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/44 "2022-01-06T21:19:39Z")

</div>

@Kevin.Herron  
Well, maybe this will help. Can’t map a string to the Modbus setup in the Micro820 so there would be functionality gained by developing a driver.

---

<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:** [January 6, 2022, 9:28pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/45 "2022-01-06T21:28:35Z")

</div>

I might beat Kevin to it. (:

---

<div class="post-metadata">

**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\
**Post date:** [January 6, 2022, 11:06pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/46 "2022-01-06T23:06:03Z")

</div>

For some odd reason modbus doesn’t like my facility, so i communicate to a controllogix and from there to ignition.

---

<div class="post-metadata">

**Author:** ![chris3](https://avatars.discourse-cdn.com/v4/letter/c/65b543/32.png) [@chris3](https://forum.inductiveautomation.com/u/chris3)\
**Post date:** [May 31, 2022, 6:07pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/47 "2022-05-31T18:07:24Z")

</div>

Any update for the Micro820 driver?

---

<div class="post-metadata">

**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\
**Post date:** [May 31, 2022, 7:08pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/48 "2022-05-31T19:08:30Z")

</div>

As far as I know , no. Modbus comms is still the preferred way .

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [May 31, 2022, 7:44pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/49 "2022-05-31T19:44:28Z")

</div>

I keep looking for updates on this as well. Granted, I don’t know how Ethernet/IP is implemented in the native Ignition drivers, but when looking at the pylogix code, there doesn’t seem to be much of a difference besides not allowing bulk reads/writes, a different comm path, and how strings are handled.

> **[GitHub - dmroeder/pylogix: Read/Write data from Allen Bradley Compact/Control...](https://github.com/dmroeder/pylogix)**
>
> Read/Write data from Allen Bradley Compact/Control Logix PLC's - GitHub - dmroeder/pylogix: Read/Write data from Allen Bradley Compact/Control Logix PLC's

If this is all that’s required, I would think this would be something IA can easily add to the existing driver to add compatibility quickly.

---

<div class="post-metadata">

**Author:** ![chris3](https://avatars.discourse-cdn.com/v4/letter/c/65b543/32.png) [@chris3](https://forum.inductiveautomation.com/u/chris3)\
**Post date:** [June 1, 2022, 3:44am UTC](https://forum.inductiveautomation.com/t/micro820/8881/50 "2022-06-01T03:44:16Z")

</div>

@michael.flagler I agree with you that the communication cannot be much different. As for the compatibility with the native A-B drivers, I did manage to get a “connected” status when trying to apply the Logix driver to it but got bad values on the tags.

Setting up peer-to-peer networks over EIP with the Micro820/850/870, CompactLogix, and ControlLogix is pretty painless and the messaging is set up the same basic way in all of the above.

Another situation that raises the question of compatibility is that A-B has the proper controller type as “Logix” when setting up the DF1 rslinx driver to connect through the Micro820 serial port.

I did get the Modbus TCP driver working just fine but there would certainly be advantages to an ethernet driver and the demand seems to be there for it.

---

<div class="post-metadata">

**Author:** ![dmroeder](https://avatars.discourse-cdn.com/v4/letter/d/a698b9/32.png) [@dmroeder](https://forum.inductiveautomation.com/u/dmroeder)\
**Post date:** [November 11, 2022, 5:24am UTC](https://forum.inductiveautomation.com/t/micro820/8881/51 "2022-11-11T05:24:43Z")

</div>

Stumbled upon this, obviously late to the game. You're right, there weren't many changes to support Micro8xx controllers. The path changed slightly, strings are handled different and there are a few CIP objects that they don't support. The Micro8xx support unsigned types, which Rockwell didn't add to the Logix platform until recently (certain controllers and firmware revisions).

I was reluctant to support it at first because I don't personally use them, so I didn't want to sign up for something I couldn't support. My Rockwell rep gifted me one, so I decided to add support.

I can appreciate that Kevin might be in a similar boat: Do I really want to take this on, considering everything else that needs to be done?

---

<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 11, 2022, 1:07pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/52 "2022-11-11T13:07:38Z")

</div>

It's supported in my expanded EtherNet/IP module. Still in pre-alpha testing, but not for much longer.

---

<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:** [January 4, 2023, 4:11pm UTC](https://forum.inductiveautomation.com/t/micro820/8881/53 "2023-01-04T16:11:20Z")

</div>

Now in public beta with MicroLogix 820, 850, and 870 support:

> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190):
>
> Automation Professionals is pleased to announce its latest EtherNet/IP Communications Suite driver module, a major upgrade to its EtherNet/IP Class1 Communications module, as a Public Beta. As of April 15, 2023, this is now a Production Release. The primary new feature is its new Generic EtherNet/IP Client Driver, a drop-in replacement for IA's Logix V21+ driver and its Omron NJ/NX driver. It does work with older Logix processors, and also works with Rockwell's MicroLogix 8xx family (ethernet…

[Previous page](https://forum.inductiveautomation.com/t/micro820/8881.md?page=2)
