# Modbus TCP SOCOMEC

**URL:** <https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602>\
**Category:** Ignition\
**Created:** [June 25, 2018, 11:02am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602 "2018-06-25T11:02:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![HALW80](https://avatars.discourse-cdn.com/v4/letter/h/47e85d/32.png) [@HALW80](https://forum.inductiveautomation.com/u/HALW80)\
**Post date:** [June 25, 2018, 11:02am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602/1 "2018-06-25T11:02:37Z")

</div>

I have a Socomec Diris a40 power monitor and have made a connection to it.  
I am having issue reading the registers as the manual states addresses 50512 to 50586  
Anyone successfully got data from similar?

---

<div class="post-metadata">

**Author:** ![ivan\_soto](https://avatars.discourse-cdn.com/v4/letter/i/e56c9b/32.png) [@ivan\_soto](https://forum.inductiveautomation.com/u/ivan_soto)\
**Post date:** [June 30, 2023, 1:23am UTC](https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602/3 "2023-06-30T01:23:54Z")

</div>

By any chance, Were you able to get this going?

---

<div class="post-metadata">

**Author:** ![carles.centeno](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carles.centeno/32/67402_2.png) [@carles.centeno](https://forum.inductiveautomation.com/u/carles.centeno)\
**Post date:** [July 2, 2023, 9:57pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602/4 "2023-07-02T21:57:10Z")

</div>

What's happen exactly?

> [@Ignition8 with Modbus TCP problems](https://forum.inductiveautomation.com/t/ignition8-with-modbus-tcp-problems/24823):
>
> Hello, I’m starting a demo/proof of concept with Ignition 8 for the plant where I’m currently working and as a starting point I’d like to get a modbus TCP device (SOCOMEC Diris A40 electricity meter) connected via Modbus. I tried reaching the device with Ananas64 and I can read correctly with the read holding register function. However, I can’t seem to get Ignition to communicate with the device at all. The device addresses are in the 50000 region (still Holding registers), so the Ignition add…

Here there are some ideas to solve this issue.

- Span GAPS in driver configuration  
or
- HR450512 \<-- ADD '4' in front of register

---

<div class="post-metadata">

**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:** [July 2, 2023, 10:06pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602/5 "2023-07-02T22:06:40Z")

</div>

Yuck. I've worked with at least 10 different brands of power meters, and socomec are the worst for getting data out of.

A previous integrator on a project I currently work on has defined registers of e.g. HRF345 for active power phase 1.

Good luck.

---

<div class="post-metadata">

**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 2, 2023, 11:41pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602/6 "2023-07-02T23:41:16Z")

</div>

> [@carles.centeno](#):
>
> HR450512 \<-- ADD '4' in front of register

Definitely never this.