e!COCKPIT Dynamic IO Mapping - Part 1 @WagoKurt
e!COCKPIT Dynamic IO Mapping - Part 1  @WagoKurt
Uploaded February 2019 | Updated September 2026, 2 weeks ago
Simple example scenario where one program can work in three different hardware IO configurations. This is helpful because you only need to manage one program instead of three, which can save engineering time and reduce the chance of human error when trying to keep three programs up to date with changes.

Example Program:
app.box.com/s/hzdmxei8ikw3a01g692u778xrovs107m
e!COCKPIT Dynamic IO Mapping - Part 1IFTTT Webhooks + Node-RED for simple alarm notification with the WAGO IO SystemWAGO Data Plotter App 2.1 TutorialProgrammable LLM ControllerPlay audio w/ Raspberry Pi & PLC (Using Modbus & NodeRED)Watson Visual Recognition with Raspberry Pi (NodeRED) & PLCNode-RED with Native MQTT IOIP Camera RTSP & Node-RED TutorialNode-RED Simple Gateway Application Tutorial - Part 3Advanced CoDeSys Tutorial - Working with Arrayse!COCKPIT Codesys Modbus TCP LibraryRaspberry Pi Node-RED Tutorial with Modbus & MQTT
Kurt Braun |

e!COCKPIT Dynamic IO Mapping - Part 1

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER