# Modbus TCP driver to H0-ECOM (DL06 CPU)

**URL:** <https://forum.inductiveautomation.com/t/modbus-tcp-driver-to-h0-ecom-dl06-cpu/114443>\
**Category:** Ignition\
**Created:** [March 11, 2026, 2:34pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-driver-to-h0-ecom-dl06-cpu/114443 "2026-03-11T14:34:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![OkiePC](https://avatars.discourse-cdn.com/v4/letter/o/f6c823/32.png) [@OkiePC](https://forum.inductiveautomation.com/u/OkiePC)\
**Post date:** [March 11, 2026, 2:34pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-driver-to-h0-ecom-dl06-cpu/114443/1 "2026-03-11T14:34:47Z")

</div>

I’m in the middle of an installation at a site with two old DirectLogic D0-06 CPUs, one has an H0-ECOM and the other has an H0-ECOM100. The latter works fine, but I could not for the life of me get the H0-ECOM to work with Ignition’s Modbus TCP Driver. I have DirectSoft (PLC programming software) on the same machine with the gateway and it works fine. Luckily, the PLC with the newer H0-ECOM100 is going away today, so I moved it to the other PLC, changed its IP address and it worked fine. One thing that is interesting is that there is no place I can find in the H0-ECOM to set the network mask. In any case, for future readers who are dealing with antique hardware, you may find that the H0-ECOM is a dead end that must be upgraded to the H0-ECOM100 for use with Ignition

EDITED: Changed RTU to TCP

---

<div class="post-metadata">

**Author:** ![OkiePC](https://avatars.discourse-cdn.com/v4/letter/o/f6c823/32.png) [@OkiePC](https://forum.inductiveautomation.com/u/OkiePC)\
**Post date:** [March 11, 2026, 2:36pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-driver-to-h0-ecom-dl06-cpu/114443/2 "2026-03-11T14:36:19Z")

</div>

I guess I could mark this as Solved.

---

<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:** [March 11, 2026, 3:31pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-driver-to-h0-ecom-dl06-cpu/114443/3 "2026-03-11T15:31:19Z")

</div>

I'm curious what prompted you to think the Hx-ECOM modules support Modbus RTU? The docs indicate they only do the proprietary DirectSoft protocol.

---

<div class="post-metadata">

**Author:** ![OkiePC](https://avatars.discourse-cdn.com/v4/letter/o/f6c823/32.png) [@OkiePC](https://forum.inductiveautomation.com/u/OkiePC)\
**Post date:** [March 11, 2026, 3:39pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-driver-to-h0-ecom-dl06-cpu/114443/4 "2026-03-11T15:39:20Z")

</div>

I meant Modbus TCP in my original post.

You’re right I think. The old HMI was using a Koyo driver with that PLC. The original ECOMs don’t claim to support Modbus TCP. Now I feel a bit dumb for creating this thread.