# Installing Modbus **URL:** \ **Category:** General Discussion\ **Created:** [September 30, 2024, 3:41pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614 "2024-09-30T15:41:17Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mimoun\_el\_hajeby](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@mimoun\_el\_hajeby](https://forum.inductiveautomation.com/u/mimoun_el_hajeby)\ **Post date:** [September 30, 2024, 3:41pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/1 "2024-09-30T15:41:17Z")
I am trying to get tags from a device that only uses serial communication through RS232 ,to get tags to ignition , anybody knows how to do that . ---
**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:** [September 30, 2024, 3:46pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/2 "2024-09-30T15:46:26Z")
Ignition's modbus driver can do that, via serial port on the Ignition gateway, though it is most robust to use a Serial-to-Ethernet converter and configure Ignition to use Modbus RTU over TCP. I recommend the Moxa family of devices for use with my alternate driver, and offer Moxa configuration advice in the user manual. That advice applies to IA's driver, too. ---
**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:** [September 30, 2024, 3:51pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/3 "2024-09-30T15:51:47Z")
> [@pturmel](#): > > though it is most robust to use a Serial-to-Ethernet converter and configure Ignition to use Modbus RTU over TCP. Slight correction - it's best to use a Modbus TCP _gateway_ that converts Modbus RTU to Modbus TCP, and then to use the standard Modbus TCP driver. Moxa makes both serial to ethernet converters and Modbus TCP gateways. ---
**Author:** ![mimoun\_el\_hajeby](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@mimoun\_el\_hajeby](https://forum.inductiveautomation.com/u/mimoun_el_hajeby)\ **Post date:** [September 30, 2024, 3:57pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/4 "2024-09-30T15:57:22Z")
thanks for reply , you mean to use converter serial/ethernet and connect from the device to plc or just that converter without plc and ignition will find it .i know little about Modbus , i know its master/slave messaging . ---
**Author:** ![Matrix\_Engineering](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matrix_engineering/32/19781_2.png) [@Matrix\_Engineering](https://forum.inductiveautomation.com/u/Matrix_Engineering)\ **Post date:** [September 30, 2024, 3:57pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/5 "2024-09-30T15:57:25Z")
My go-to is the Moxa MB3170, DIN rail mount, 2 power inputs, RS232 and 485, two RJ45 ports. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/8/d8370da042c099158f84aa9ebf61185b930ae023.jpeg) ---
**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:** [September 30, 2024, 5:46pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/6 "2024-09-30T17:46:34Z")
> [@Kevin.Herron](#): > > it's best to use a Modbus TCP _gateway_ that converts Modbus RTU to Modbus TCP, and then to use the standard Modbus TCP driver. The Moxa 5000 series NPort devices are dramatically cheaper port-for-port, and can have many more ports. For single-client (Ignition) applications, I'll take the NPort products almost every time. (The exception is when using the IA driver in a redundant pair.) ---
**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:** [September 30, 2024, 5:48pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/7 "2024-09-30T17:48:11Z")
Yeah, but you said robust, not cheap. The hack that it is putting Modbus RTU directly onto TCP can't reasonably be called robust... ---
**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:** [September 30, 2024, 6:00pm UTC](https://forum.inductiveautomation.com/t/installing-modbus/96614/8 "2024-09-30T18:00:33Z")
We'll have to agree to disagree. Setting the Moxas to buffer properly for Modbus (they don't, out of the box, which is why I have an appendix for that) makes packet assembly and delivery exceedingly robust. As long as the driver enforces Modbus packet timing rules, it'll recover from network hiccups remarkably cleanly.