# 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:** 1\
**Showing post:** 4

<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

---

_[View the full topic](https://forum.inductiveautomation.com/t/modbus-tcp-socomec/18602)._