July-30th-2018, 06:21 PM
Hello Eyad,
it doesn't matter if you control GPIOs of DI/DO module NIOT-E-NPIX-4DI4O module or NIOT-E-NPIX-EVA. It is the same thing. With EVA you have the advantage that all pins are available free to use. With 4DI4DO the are phsically coming with input and output bus drivers.
Look to the Docker Container we provide: https://hub.docker.com/r/hilschernetpi/n...d-npix-io/. Go further to source code here https://github.com/Hilscher/netPI-nodere...ib-npix-io.
You can see that is is using the offical rpi-gio node.js library provided on the web here: https://www.npmjs.com/package/rpi-gpio
So with our source code you can compile your own node-red GPIO Docker container for you privat EVA board setup.
it doesn't matter if you control GPIOs of DI/DO module NIOT-E-NPIX-4DI4O module or NIOT-E-NPIX-EVA. It is the same thing. With EVA you have the advantage that all pins are available free to use. With 4DI4DO the are phsically coming with input and output bus drivers.
Look to the Docker Container we provide: https://hub.docker.com/r/hilschernetpi/n...d-npix-io/. Go further to source code here https://github.com/Hilscher/netPI-nodere...ib-npix-io.
You can see that is is using the offical rpi-gio node.js library provided on the web here: https://www.npmjs.com/package/rpi-gpio
So with our source code you can compile your own node-red GPIO Docker container for you privat EVA board setup.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
