# Direct Connection from Ignition to Wago via Ethernet I/P **URL:** \ **Category:** Ignition\ **Created:** [June 2, 2022, 10:41pm UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324 "2022-06-02T22:41:05Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![seano](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@seano](https://forum.inductiveautomation.com/u/seano)\ **Post date:** [June 2, 2022, 10:41pm UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/1 "2022-06-02T22:41:05Z")
Is there a way to connect Ignition to a Wago 750-363 or similar via Ethernet I/P? I’d like to use a direct Ethernet I/P connection in this case, not one of the workarounds (e.g. using Modbus TCP instead or the new generation Wagos with MQTT/onboard OPC servers, buying a completely different PLC, etc). ---
**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:** [June 2, 2022, 10:42pm UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/2 "2022-06-02T22:42:27Z")
Maybe using @pturmel 's EtherNet/IP driver, but not using any of Ignition’s standard drivers. ---
**Author:** ![seano](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@seano](https://forum.inductiveautomation.com/u/seano)\ **Post date:** [June 2, 2022, 11:05pm UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/3 "2022-06-02T23:05:21Z")
@Kevin.Herron Thank you! A prompt no is the next best thing. @pturmel is your driver at full release? Looking for something reliable / relatively straightforward that isn’t too much harder to add new tags than the built in Rockwell drivers as I’ll have electricians wanting to add tags from time to time. The fallback option is Modbus TCP but then I’ll need to map tags every time. Lead times for many PLC brands are getting ludicrous here in New Zealand. ---
**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:** [June 3, 2022, 12:14am UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/4 "2022-06-03T00:14:11Z")
> [@seano](#): > > driver at full release? It's been in production release since October 2017. (I had to go look.) > [@seano](#): > > isn’t too much harder to add new tags than the built in Rockwell drivers Not sure what you mean. I/O connections are totally different from processor tag-based connections. Though the data brought in is **presented** as if tags in a processor. Some effort must be expended creating structured types or assemblies that match the byte-for-byte layout of the I/O buffers of the target device. You can make most edits without stopping the device. Let me know what actual models you will be using and get me the EDS files. I'm happy to help customers deploy this module. Note that scanning I/O is a _ **Premium** _ feature of the module. The base version makes Ignition an I/O **adapter**. ---
**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:** [June 3, 2022, 12:28am UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/5 "2022-06-03T00:28:59Z")
I just read the application note for the 750-363 with an L32 processor. A bit more complicated than typical devices, but no surprises. I expect it to work. ---
**Author:** ![Andy\_King](https://avatars.discourse-cdn.com/v4/letter/a/dfb087/32.png) [@Andy\_King](https://forum.inductiveautomation.com/u/Andy_King)\ **Post date:** [May 29, 2024, 7:09am UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/7 "2024-05-29T07:09:52Z")
Hi there, did you ever get this to work? looking at doing something similar, with using a Wago Ethernet module with IO modules attached and then connecting directly to ignition ---
**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:** [May 29, 2024, 11:52am UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/8 "2024-05-29T11:52:57Z")
There was no follow-up back then, but I would still expect it to work with the Scanner+Adapter options of the latest version of my module: > [@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… ---
**Author:** ![seano](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@seano](https://forum.inductiveautomation.com/u/seano)\ **Post date:** [May 30, 2024, 4:37am UTC](https://forum.inductiveautomation.com/t/direct-connection-from-ignition-to-wago-via-ethernet-i-p/60324/9 "2024-05-30T04:37:41Z")
Hey mate, we were in a huge rush and in the end I went indirectly via a ControlLogix. Your only option for this specific application without a workaround or alternative architecture is @pturmel's driver. I needed to match the number of bytes in and out with the number/size of IO modules on the fieldbus coupler. From memory, any error in either manifested as a "Wrong number of output bytes" (or similar) error, even if the mistake was in the number of input bytes. We also had to set a couple of options in the coupler's web portal, I think including setting the clock (?). Teething problems aside, it worked pretty well. Phil's driver does more or less the same thing, but brings the data into Ignition. I assume you are integrating a bunch of old Wagos into a more modern system like I was?