Node-RED + fram nodes
Made for netPI RTE 3, the Raspberry Pi 3B Architecture based industrial suited Open Edge Connectivity Ecosystem
Debian with Node-RED and fram nodes for ferroelectric random access memory access
The image provided hereunder deploys a container with installed Debian, Node-RED and fram nodes to communicate with the onboard ferroelectric random access memory on netPI RTE 3,
Base of this image builds debian with installed Internet of Things flow-based programming web-tool Node-RED and two extra nodes fram read and fram write providing access to netPI's 8kByte FRAM FM24CL64B.
To allow the access to the Node-RED over a web browser the container TCP port
1880 needs to be exposed to the host.
To grant access to the FRAM from inside the container the
/dev/i2c-1 host device needs to be added to the container.
STEP 1. Open netPI's landing page under
https://<netpi's ip address>.
STEP 2. Click the Docker tile to open the Portainer.io Docker management user interface.
STEP 3. Enter the following parameters under Containers > Add Container
Host "1880" (any unused one) -> Container "1880"
Restart policy" :
Runtime > Devices > add device:
Host "/dev/i2c-1" -> Container "/dev/i2c-1"
STEP 4. Press the button Actions > Start/Deploy container
Pulling the image may take a while (5-10mins). Sometimes it takes so long that a time out is indicated. In this case repeat the Actions > Start/Deploy container action.
After starting the container open Node-RED in your browser with
http://<netpi's ip address>:<mapped host port> e.g.
http://192.168.0.1:1880. Two extra nodes fram read and fram write in the nodes fram library palette provides you random access to netPI RTE 3's FRAM. Their info tabs in Node-RED explain how to use them.
DockerHub web platform is x86 CP based, but an ARM CPU coded output file is needed for Raspberry systems. This is why the Dockerfile includes the balena steps.
View the license information for the software in the project. As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained). As for any pre-built image usage, it is the image user's responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.
Hilscher Gesellschaft fuer Systemautomation mbH www.hilscher.com