# Modbus TCP to AccuEnergy Energy Meters **URL:** \ **Category:** Ignition\ **Tags:** modbus\ **Created:** [December 16, 2024, 6:29am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860 "2024-12-16T06:29:19Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Sasi\_Rai](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@Sasi\_Rai](https://forum.inductiveautomation.com/u/Sasi_Rai)\ **Post date:** [December 16, 2024, 6:29am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/1 "2024-12-16T06:29:19Z")
Hi All, I have got a couple of AccuEnergy energy meters that I need to read values from. I have been able to read values using Modbus Poll. But no such luck with Ignition. I have added one of the meters to device connections with Modbus TCP as the protocol. The IP Address is correct and zero-based addressing is checked. Here's a screenshot from the literature: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/a/7/a7af5cd9249a0c9898ed0f7108e9072ae1956aa3.png) I want to read the Frequency. So, I have a tag called 'Frequency' with value setup as: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/a/0a189028ddbc9d1bbd3c354931c1b84ad9b906b9.png) with 'HRF0', I was expecting the two registers at 4000H and 4001H to be read and converted to a Float. However, the value is being displayed as 'Uncertain\_InitialValue'. What am I doing wrong? Has anyone worked with AccuEnergy meters? Any guidance would be awesome. Thank you all! ---
**Author:** ![jonathan.taylor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jonathan.taylor/32/4048_2.png) [@jonathan.taylor](https://forum.inductiveautomation.com/u/jonathan.taylor)\ **Post date:** [December 16, 2024, 9:50am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/2 "2024-12-16T09:50:34Z")
Have you scanned the point with a modbus tool like CAS? Have you tried with a device id? i.e. `[EnergyMeter1]1.HRF0` ---
**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:** [December 16, 2024, 12:52pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/3 "2024-12-16T12:52:49Z")
Use `HRF16384` or `1.HRF16384`. You may also need to configure the Ignition device's advanced settings to use Zero-Based Addressing, and possibly also Swap Words. ---
**Author:** ![JordanCClark](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jordancclark/32/83362_2.png) [@JordanCClark](https://forum.inductiveautomation.com/u/JordanCClark)\ **Post date:** [December 16, 2024, 2:12pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/4 "2024-12-16T14:12:01Z")
On MODBUS devices, I usually start with just trying to read the individual registers as a INTs. It serves as a sanity check that data is actually reading before jumping to the more complex forms. ---
**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:** [December 16, 2024, 2:14pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/5 "2024-12-16T14:14:03Z")
> [@JordanCClark](#): > > It serves as a sanity check This check is dramatically easier, via Ignition's Quick Client, when the driver supports browsing of all of the variations. (\* _Cough_ \*) ---
**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:** [December 16, 2024, 3:30pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/6 "2024-12-16T15:30:04Z")
As @pturmel pointed out, you need to use the decimal addresses, but I just wanted to note that I think on the hex version, you are confusing the leading 4 as a 4xxxx style holding register, but when you convert to decimal you get the 16384 for 4000h meaning in any other software that you use the 4xxxxx style to read holding registers you'd need to prefix that value with a 4 (416384). Ignition doesn't use this format, so use the addressing like previously shown. ---
**Author:** ![Sasi\_Rai](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@Sasi\_Rai](https://forum.inductiveautomation.com/u/Sasi_Rai)\ **Post date:** [December 17, 2024, 3:57am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/7 "2024-12-17T03:57:20Z")
Yup. I am using Modbus Poll and reading is good. ---
**Author:** ![Sasi\_Rai](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@Sasi\_Rai](https://forum.inductiveautomation.com/u/Sasi_Rai)\ **Post date:** [December 17, 2024, 4:00am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/8 "2024-12-17T04:00:16Z")
Thanks pturmel. I had to use 1.HRF16384. I had already turned on the Zero Based Addressing. And didn't need to swap words. You solved it, as always! ---
**Author:** ![Sasi\_Rai](https://avatars.discourse-cdn.com/v4/letter/s/ed655f/32.png) [@Sasi\_Rai](https://forum.inductiveautomation.com/u/Sasi_Rai)\ **Post date:** [December 17, 2024, 4:02am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-to-accuenergy-energy-meters/99860/9 "2024-12-17T04:02:22Z")
Agreed. I tried to do so but couldn't. I tried with both Hex and Decimal address. But I missed the preceding node address.