since Revision #2 it is possible to change the micro-sd-card of the netPi. Therefore it is possible to use larger micro-sd-cards as the original 8GB-one. Since I like the original Hilscher-Image with its security features quite a lot, I would not want to miss it on a larger sd-card.
Therefore I have backuped the original Image with win32-Disk-Imager, which worked well. I was also able to flash this image to the new card using balenaEtcher. When I inserted the new card into the netPi, everything worked well. The only problem is that I forgot to extend the filesystem/logical Volume on the new card to be able to use the additional space. So my 16 GB-card still worked like a 8 GB-one. After googeling, try and error, I actually managed to extend the Logical Volume which is used by the netPi for storing our data, with the underlying volume group and physical volume. After that I was able to use the complete 16-GBs of the new card on this netPi.
I thought "hey, now I know what to do" and wrote a quick manual of how to do the extension. Trying this at the second netPi, I wasn't able to do it again. After hours of trying, I surrendered and found a kind of a "hack" which helped me out. I flashed the Image of netPi(1), which I was able to sucessfully extend to 16GBs, to the netPI(2). After that of course the netPI(2) did not boot, since the Hardware-ID of the netPi did not match the hardware-ID written to the image by Hilscher. But I managed to change the hardware-ID wirtten to the Image by coping one Partition of the original netPi(2)'s Image to the 16-GB Image of netPI(1). Now I am able to reproduce 16GB netPi Images, but as you might guess, I can't handle e.g. 32GB cards now
To cut a long story short.....Would anyone who is trying to do the same/has done the same and is more into filesystems and logical volumes than me be willing to share his way of doing it with me (and everyone else) in form of a quick manual? Or would one of the Support-Team be that kind?
I am pleased about to announce you today the release of a full featured Node-RED container that includes all ever developed netPI specific Node-RED nodes (until now they were offered in separate containers). Those are
netpi-nodered-npix-rs232
netpi-nodered-npix-rs485
netpi-nodered-npix-io
netpi-nodered-npix-ai
netpi-nodered-user-leds
netpi-nodered-nxpix-leds
node-red-contrib-fieldbus (on netPI RTE 3 only)
node-red-contrib-fram (on netPI RTE 3 only)
Additionally it includes some community maintained nodes we feel they are a must have on netPI in case Node-RED is the choice. Those are
node-red-contrib-generic-ble
node-red-contrib-modbus
node-red-contrib-opcua
node-red-dashboard
As usual we are offering the container ready for your deployment on our netPI repository here.
Please find attached my schreenshot..I dont understand from where the timing information is dispalyed in Docker container?
This is not matching with my system
I was facing the problem many times now, that my netPis stoped working. When I tried to reach the edge-gateway-manager than, the Error "502 - Bad Gateway" was shown. I've been using software version 1.1.4/1.1.5/1.1.6
It happened to me, when I ran a mariadb-database-server on the netPi and other containers tried to read/write data from/to it. (I know the database-sd-card-issue with 3000 w/e cycles). How can it happen, that the nginX-Server does not respond anymore? The "act"-LED keeps flashing, though.
I've attached the syslog from right before the freeze and right after it.
I am very pleased to announce the availability of the CAN extension module NIOT-E-NPIX-RCAN for netPI RTE 3 and CORE 3 today. Order it through Hilscher directly or our Web Shop (update coming soon). The part numer is #1322.063.
The module USPs are
· CAN 2.0 A/B compatible, ISO 11898-1:2015
· 1MBaud max. transmission rate
· Usage via SocketCAN software interface
· With jumper for CAN bus termination
· Kernel driver capable of accommodating highest bus loads
We are currently testing the netPI (NIOT-E-NPI3-51-EN-RE) and the expansion module NIOT-E-NPIX-RS485. After installing of Raspbian and the terminal program(Minicom), we encountered a problem when it comes to communication using the RS485 expansion module.
You have to switch a GPIO-Pin to either send or receive via the RS485 interface, as mentioned in the Thread: "https://forum.hilscher.com/Thread-niot-e-npi3-51-en-RS485-Industrial-Ethernet" by Armin@netPI from April-12th-2019, 07:19 PM
On this site "https://www.netiot.shop/epages/es767660.sf/de_DE/?ObjectPath=/Shops/es767660/Products/1322.011" the product description states that "full-duplex oepration is possible".
According to the block circuit diagramm on page 21 of the hardware description "https://www.netiot.com/fileadmin/user_upload/netIOT/netMAKER/netPI/documents/netPI_Erweiterungsmodule_HW_04_DE.pdf" full-duplex is not possible, because there are only two wires. Even half-duplex is difficult to achieve because it requires its own switching driver which manages whether you want to send or recieve using the RS485 module. And I did not find such a driver after some research.
Now here is my question: Is there a such a driver for the serial port to work with standard programs? If there is none, the system would not be usable for us in its current state.
Deutsch/German:
Hallo!
Wir testen zurzeit den netPI (NIOT-E-NPI3-51-EN-RE) und dem Erweiterungsmodul NIOT-E-NPIX-RS485, nach Installation von Raspbian und eines Terminalprogramms(Minicom) sind wir auf ein Problem gestoßen, wenn es zum Thema Kommunikation kommt.
Man muss einen GPIO-Pin umschalten, um über die RS485-Schnittstelle entweder Senden oder Empfangen zu können, laut Forumthread:
"https://forum.hilscher.com/Thread-niot-e-npi3-51-en-RS485-Industrial-Ethernet"
Eintrag von "Armin@netPI" am April-12th-2019, 07:19 PM
Auf dieser Seite "https://www.netiot.shop/epages/es767660.sf/de_DE/?ObjectPath=/Shops/es767660/Products/1322.011" in der Produktbeschreibung ist zu lesen, dass "Vollduplex-Betrieb möglich" sei.
Laut Blockschaltbild auf Seite 21 der Hardware-Beschreibung "https://www.netiot.com/fileadmin/user_upload/netIOT/netMAKER/netPI/documents/netPI_Erweiterungsmodule_HW_04_DE.pdf" ist Voll-Duplex nicht möglich da es nur zwei Drähte gibt. Auch Halb-Duplex ist schwer realisierbar, da dafür eine eigene Umschaltvorrichtung/ein eigener Treiber nötig ist, die/der zeitgesteuert immer hin und her schaltet oder die die Signale räumlich voneinander trennt. Und so eine Umschaltvorrichtung/so einen Treiber habe ich nach einiger Recherche nicht gefunden.
Nun meine Frage: Gibt es einen Treiber, damit die serielle Schnittstelle mit "standard" Programmen funktioniert. Ansonsten wäre das System für uns im derzeitigen Zustand nicht benutzbar.
"A tool for defining and running multi-container Docker applications", says the Docker Compose definition and yes it is indeed a second tool named "docker-compose" that needs to be installed next to "docker" tool to participate from deploying multiple containers at a time. On native machines it is no problem to post install docker-compose but on netPI it is not there.
But the good thing is deploying a stack of applications at a time is supported by netPI as well using the "stacks" feature of standard Docker. Lean more here about the difference between stacking and composing.
To use the stacks function on netPI open the Docker web GUI portainer.io and then click the menu item "Stacks". Click "+Add stack" and check the "Web editor" feature in the middle and copy and paste the content of your compose YAML file into the web editor frame. Finally click "Deploy the stack".
Since Docker compose often starts many containers at a time you have to patiently wait for downloading the container images the first time you use this function.
Here is how a typical compose file content looks like:
The example above configures and starts 4 containers in a single step:
CODESYS Soft PLC
Grafana graphical tool
Node-RED IoT tool
InfluxDB database
netPI at the moment supports the compose file reference version 2.x. Find here the compose file reference. The version is usually the first statement in a compose file.