# Communicating with Anybus Explict Messaging

**URL:** <https://forum.inductiveautomation.com/t/communicating-with-anybus-explict-messaging/76718>\
**Category:** Ignition\
**Created:** [July 21, 2023, 4:55pm UTC](https://forum.inductiveautomation.com/t/communicating-with-anybus-explict-messaging/76718 "2023-07-21T16:55:06Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [July 21, 2023, 5:03pm UTC](https://forum.inductiveautomation.com/t/communicating-with-anybus-explict-messaging/76718/3 "2023-07-21T17:03:50Z")

</div>

Yes, my new client driver option supports this type of messaging since v2.1:

> [@Automation Professionals' EtherNet/IP Communication Suite V2](https://forum.inductiveautomation.com/t/automation-professionals-ethernet-ip-communication-suite-v2/68190/103):
>
> A regression fix (@barrier support) and a fix for the slightly wider array optimizations of v2.1.1. Arbitrary unbrowsed symbol support is close... (Intended for ML8xx and Omron NJ/NX applications.) For Ignition v8.1+: v2.1.4.231991530 Latest official release is on my [Module Sales](https://www.automation-pros.com/modulesales.html) page, as usual.

You will need to construct a supplemental XML configuration file that specifies the data types for each class/instance/attribute that you want to decode. Or leave unspecified to get byte arrays.

---

_[View the full topic](https://forum.inductiveautomation.com/t/communicating-with-anybus-explict-messaging/76718)._