# IP Device Connection **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [January 27, 2025, 10:27pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452 "2025-01-27T22:27:16Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Thomas\_McHale](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@Thomas\_McHale](https://forum.inductiveautomation.com/u/Thomas_McHale)\ **Post date:** [January 27, 2025, 10:27pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/1 "2025-01-27T22:27:16Z")
I am working on a project for a device from Radix this is something that is used to get temperature and humidity readings from our production floor. in order for me to connect and grab data from this device what next steps do i need to take to make it work, [http://radix.co.in/products/hawkeye-rh-t-dp-indicator-hawkeye](http://radix.co.in/products/hawkeye-rh-t-dp-indicator-hawkeye) - Microcontroller based - RH, Temperature & DP measurement - Software programmable channel ranges, units & input types - Slave display unit - RH+T+DP remote - User programmable for 1,2 or 3 channel measurement - 3-row, 0.8” (20.3 mm), large, bright LED display - 3 programmable Alarms with visual annunciation - 3 programmable Alarms with open collector outputs to operate external relays - Real Time Clock with battery back-up - Software calibration for all 3 channels - Calibration history / schedule for validation - RS485/MODBUS RTU multidrop communication for PLC, SCADA, etc. - 24 VDC or 85~265 VAC SMPS supply - Powerful, user-friendly SCADA available - FDA 21CFR Part11 compliant SCADA version also - Advanced digital RH+T sensor technology ---
**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:** [January 27, 2025, 10:36pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/2 "2025-01-27T22:36:50Z")
> [@Thomas\_McHale](#): > > RS485/MODBUS RTU multidrop communication for PLC, SCADA, etc. Easiest thing to do is probably put something like a Moxa MGate in front of it and then use Ignition's Modbus TCP driver to connect. ---
**Author:** ![Thomas\_McHale](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@Thomas\_McHale](https://forum.inductiveautomation.com/u/Thomas_McHale)\ **Post date:** [January 27, 2025, 10:46pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/3 "2025-01-27T22:46:18Z")
thanks will check it out ---
**Author:** ![Thomas\_McHale](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@Thomas\_McHale](https://forum.inductiveautomation.com/u/Thomas_McHale)\ **Post date:** [January 27, 2025, 10:47pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/4 "2025-01-27T22:47:25Z")
> [@Kevin.Herron](#): > > Moxa MGate I have probably 100 of these items with different IP address just fYI ---
**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:** [January 27, 2025, 11:03pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/5 "2025-01-27T23:03:52Z")
Nothing in the specs on the page you linked say anything about these devices even having an ethernet port, let alone whether they can communicate over some known protocol on it. ---
**Author:** ![Thomas\_McHale](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@Thomas\_McHale](https://forum.inductiveautomation.com/u/Thomas_McHale)\ **Post date:** [January 28, 2025, 12:41pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/6 "2025-01-28T12:41:06Z")
![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/2/52aed18fc6a9b35a739f71077bb1cf1b66eefb77.png) [http://radix.co.in/products/hawkeye-pro-eth-hawkeye-pro-eth?family\_id=data-logging-in-cleanroom](http://radix.co.in/products/hawkeye-pro-eth-hawkeye-pro-eth?family_id=data-logging-in-cleanroom) it seems they have two models the Hawkeye ETH is the one I have with the ethernet port. ---
**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:** [January 28, 2025, 12:45pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/7 "2025-01-28T12:45:10Z")
Looks like these have Modbus TCP support, so you'll just use Ignition's Modbus driver to connect directly. Next step would be to find a user manual or some other documentation that tells you what registers the data you want is in and then try to connect to one of these with the Modbus driver and get a value. > **[Connecting to Modbus Device | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/opc-ua-drivers/modbus/connecting-to-modbus-device)** > > 1. Go to the Config section of the Gateway Webpage. > **[Modbus Addressing | Ignition User Manual](https://docs.inductiveautomation.com/docs/8.1/ignition-modules/opc-ua/opc-ua-drivers/modbus/modbus-addressing)** > > Manually Addressing a Modbus Device ---
**Author:** ![Thomas\_McHale](https://avatars.discourse-cdn.com/v4/letter/t/7feea3/32.png) [@Thomas\_McHale](https://forum.inductiveautomation.com/u/Thomas_McHale)\ **Post date:** [January 28, 2025, 12:56pm UTC](https://forum.inductiveautomation.com/t/ip-device-connection/101452/8 "2025-01-28T12:56:07Z")
thanks will check it out