# Difference between Ethernet/IP Suite Connections **URL:** \ **Category:** General Discussion\ **Created:** [July 25, 2024, 2:14pm UTC](https://forum.inductiveautomation.com/t/difference-between-ethernet-ip-suite-connections/93745 "2024-07-25T14:14:00Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Colton\_Cederberg](https://avatars.discourse-cdn.com/v4/letter/c/8edcca/32.png) [@Colton\_Cederberg](https://forum.inductiveautomation.com/u/Colton_Cederberg)\ **Post date:** [July 25, 2024, 2:14pm UTC](https://forum.inductiveautomation.com/t/difference-between-ethernet-ip-suite-connections/93745/1 "2024-07-25T14:14:00Z")
Hello, pturmel made a Ethernet/IP suite that when installed in the modules section of your Gateway gives more options to use in the device connections. The added connections can be seen in the photo attached. Does anyone or pturmel know the difference in use between the three or examples of how each would be used. I am also unable to @ pturmel because I am a new user. Thank You! ![Screenshot 2024-07-25 090413](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/0/204c13da96b2be5fce18c45ca3bb23eec4135545.png) ---
**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:** [July 25, 2024, 2:22pm UTC](https://forum.inductiveautomation.com/t/difference-between-ethernet-ip-suite-connections/93745/2 "2024-07-25T14:22:01Z")
I'm pretty sure there is a user manual for these, but here you go: @pturmel edit: [https://www.automation-pros.com/enip1/UserManual.pdf](https://www.automation-pros.com/enip1/UserManual.pdf) ---
**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:** [July 25, 2024, 2:39pm UTC](https://forum.inductiveautomation.com/t/difference-between-ethernet-ip-suite-connections/93745/3 "2024-07-25T14:39:52Z")
If you're simply looking for a replacement driver to access tags in the PLC, you need the Generic EtherNet/IP Client Device. I believe the other 2 are for directly connecting to I/O (I think this is the first option - EtherNet/IP Class 1 Host Device), and for simulating a "virtual rack" to allow a PLC/scanner/ethernet card to connect the virtual rack and treat it like I/O. ---
**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 25, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/difference-between-ethernet-ip-suite-connections/93745/4 "2024-07-25T15:02:31Z")
"Class3" is what the protocol specification calls "request/response" traffic, aka "polling", and uses just TCP/IP. In my driver module, this is the "Generic EtherNet/IP Client Device" option. Use it to **replace** IA's v21+ Logix driver, MicroLogix 800 driver, and Omron NJ/NX driver. It also supports other functionality within the "Class3" part of the EtherNet/IP specification. The above part of my driver is licensed as the "Client Option". "Class1" is what the protocol specification calls scheduled traffic, like I/O connections and producer/consumer tags. Scheduled traffic is _initiated_ with a class3 "Forward Open" request and response, but then actually transfers data over UDP/IP. Within my module, the "Adapter Option" allows Ignition to behave as a virtual remote I/O chassis for other PLCs to scan. Many connections, from multiple PLCs, are allowed when setting up unique connection points (assembly numbers). The adapter option also enables Ignition to receive data transfers from/to other PLCs via those PLCs' messaging instructions. And it allows other PLCs to subscribe to **producer** tags in Ignition. Select the "EtherNet/IP Class1 Host Device" to use these features. The "EtherNet/IP Class1 Target Device" is also available with the adapter option--it is a cut-down implementation of the Host Device intended to behave as multiple identical occupants of slots in the virtual I/O chassis. (Use with Rockwell's ETHERNET-BRIDGE and CIP-MODULE elements in a Logix Processor's I/O configuration.) When licensed with the "Scanner+Adapter Option", the class1 functionality expands to include the ability to be a scanner for EtherNet/IP I/O devices, and to configure **consumer** tags in Ignition, subscribed to real PLCs producer tags. This option also allows the use of **arbitrary** class3 requests to other devices via scripting. Select the "EtherNet/IP Class1 Host Device" to use these features. The user manual Kevin linked above goes into great detail as to what is possible.