Uploaded November 2019 | Updated September 2026, 2 weeks ago
One way to implement a ModbusTCP slave with e!COCKPIT for integration with 3rd party HMI's and SCADA systems, where variables are persistent in the PLC and can be written from both the HMI & PLC program (not Input & output like when using the e!COCKPIT network configurator)
Example e!COCKPIT Project:
app.box.com/s/0cgr0pri47p4fdoqf6nmbeolwq4tl70n
Please note that after you download, create the boot project and then power cycle the PLC. Otherwise the PLC variables may not match the Modbus Slave array values.
One way to implement a ModbusTCP slave with e!COCKPIT for integration with 3rd party HMI's and SCADA systems, where variables are persistent in the PLC and can be written from both the HMI & PLC program (not Input & output like when using the e!COCKPIT network configurator)
Example e!COCKPIT Project:
app.box.com/s/0cgr0pri47p4fdoqf6nmbeolwq4tl70n
Please note that after you download, create the boot project and then power cycle the PLC. Otherwise the PLC variables may not match the Modbus Slave array values.










