Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 424
» Latest member: ferrim
» Forum threads: 416
» Forum posts: 2,127

Full Statistics

Latest Threads
Automate Provisioning for...
Forum: Software
Last Post: Armin@netPI
Yesterday, 03:46 PM
» Replies: 2
» Views: 25
System software V1.2.2.0 ...
Forum: News
Last Post: Armin@netPI
November-26th-2020, 04:25 PM
» Replies: 0
» Views: 44
NIOT-E-NPIX-4DI4DO with n...
Forum: Software
Last Post: zen89
November-25th-2020, 01:06 PM
» Replies: 3
» Views: 272
NIOT-E-NPI3-EN Excessive ...
Forum: Hardware
Last Post: Armin@netPI
November-25th-2020, 07:35 AM
» Replies: 11
» Views: 246
missing the menu items fr...
Forum: Software
Last Post: Armin@netPI
November-20th-2020, 07:41 AM
» Replies: 5
» Views: 175
UL certificate
Forum: Hardware
Last Post: MGharat
November-19th-2020, 11:41 AM
» Replies: 2
» Views: 68
Forum: Hardware
Last Post: Armin@netPI
November-19th-2020, 07:06 AM
» Replies: 1
» Views: 64
NPIX-4DI4DO and NetPi-Nod...
Forum: Software
Last Post: alhammi
November-16th-2020, 01:35 PM
» Replies: 4
» Views: 251
Profinet name lost after ...
Forum: Software
Last Post: Armin@netPI
November-16th-2020, 01:07 PM
» Replies: 7
» Views: 209
Get host MAC via REST API...
Forum: Software
Last Post: bschandra
November-16th-2020, 09:26 AM
» Replies: 4
» Views: 309

Posted by: jmontanes - September-8th-2020, 07:29 AM - Forum: Hardware - Replies (4)

hello, we recently bought your product:
We have already installed it and it works perfectly, but we need to use some GPIO from the raspberry, how can we do it?

  Data logger
Posted by: Jan - September-4th-2020, 01:06 PM - Forum: Software - Replies (11)

Dear Support Team,

I 'm working with a netPi (NIOT-E-NPI3-51-EN-RE) and I want to know, if it's possible to use that Device as Data logger?

The device had 4x USB Slots and I want to connect one of it with a hard disk.
It would be great, if it's possible to program it in NodeRed.

I hope you can help me.
Best regards,

Posted by: tad - September-2nd-2020, 05:41 AM - Forum: Software - Replies (2)

Dear Armin,

The code for OpenPLC is posted on the following website.
Why not register with Hilscher's Docker Hub?


By the way, I confirmed that I created its Docker image file on Raspberry Pi 3B and deployed the image to netPI.
Currently, OpenPLC is running properly on netPI.
Therefore, I was wondering why Hilscher hasn't posted the image to Dokcer Hub.
Then, I can directly use OpenPLC on netPI without Raspberry Pi.

Thank you very much for your information.
Best regards

  how to unpack netPI to replace the microSD card
Posted by: tad - September-2nd-2020, 05:33 AM - Forum: Hardware - Replies (2)

Dear Armin,

I have seen an web site that shows how to remove the microSD card of netPI by showing a picture.
I can't find this site anymore, so could you please let me now the site if you know?

Thank you very much for your support.
Best regards,

  Communication between PLC and Netpi
Posted by: Dipro - August-31st-2020, 08:35 AM - Forum: Software - Replies (4)

Dear Hilscher team

We are building a prototype to send gathered information from a S7 1500 PLC to netpi via Profinet.
The connection seems to work, both the PLC and the fieldbus node don’t show any error.
For first test we set up an output address (1 Byte) in the PLC and assign the first bit with a switch conntected to the PLC. But the information received with the fieldbus node never displayed the information sent and additionally the information read from the fieldbus node switches each time between 2 different values. We stopped sending from the PLC but the fieldbus node kept reading 2 different values. Then we tried to send one Byte to the PLC but it probably never came through, the fieldbus input node then stated 2 different values but still switching as mentioned before.
I have the feeling we are just missing some detail but we are struggling to find it.

Attached you can find some screenshots regarding the PLC and Netpi settings

Best regards

Attached Files
.pdf   attachment.pdf (Size: 856.08 KB / Downloads: 2)

  OpenPLC V3 - Dockercontainer
Posted by: ioexpert - August-28th-2020, 09:13 AM - Forum: Projects - Replies (1)

I had updated the OpenPLC V3 docker container and made it public at docker hub: https://hub.docker.com/r/ioexpert/netpi-openplc

It is now possible to select "Hilscher netPI" also from the hardware settings section to drive the IO-extension-card directly.
Here is the patch https://github.com/schreinerman/openplc_v3-netpi to do it manually.

Btw. if used together with NodeRED, the OpenPLC can be connected via Modbus TCP. For the dashboard, I had also added a container making it possible to display the dashboard URL of NodeRED directly fullscreen on a display connected via HDMI using this docker repo: https://hub.docker.com/r/ioexpert/armv7-...board-hdmi

Feel free to try my stack script from https://github.com/schreinerman/rpi-open...tree/netPI to combine OpenPLC, NodeRED and HDMI-Dashboard containers.

  Docker trusted content
Posted by: Armin@netPI - August-27th-2020, 04:50 PM - Forum: Projects - No Replies

This thread is dedicated to a Docker security feature named "Docker trusted content".

In simple words: a repository and hosted containers are both trusted and signing was executed by person(s) of trust. So the whole repo authenticity is guaranteed even during image pulling time.

"Docker trusted" relies on "Notary" which is an open source project. Here is written what Notary exactly is https://docs.docker.com/notary/getting_started/.

In sum there is an extra Notary server required that runs independently of the repository server and manages alongside the trusted collection of content generated.

Here is how to deploy a Notary server. Remark: A Notary server can only be installed on AMD CPU compatible hosts - hosting on a Raspberry Pi or a netPI is not possible (I haven't found any source how to do this, maybe you?). For the test I made all the following executions were executed in a Linux Ubuntu shell:

Install some basic tools/commands:

apt update &&
apt install gnupg2 pass &&
# install docker
apt install -y docker-ce docker-ce-cli containerd.io &&
mkdir -p ~/.docker/trust &&
# install docker-compose
apt  install -y docker-compose &&
# install go language
cd /tmp &&
wget https://golang.org/dl/go1.15.linux-amd64.tar.gz &&
tar -xvf go1.15.linux-amd64.tar.gz &&
rm -r /usr/local/go &&
mv go /usr/local &&
export GOROOT=/usr/local/go &&
export GOPATH=$HOME/go &&
export PATH=$GOPATH/bin:$GOROOT/bin:$PATH &&
source ~/.profile &&
# install cfssl tools
go get -u github.com/cloudflare/cfssl/cmd/cfssl &&
go get -u github.com/cloudflare/cfssl/cmd/cfssljson

Install the Notary client tool:

wget --no-check-certificate -O /usr/local/bin/notary https://github.com/docker/notary/releases/download/v0.6.1/notary-Linux-amd64 && chmod a+x /usr/local/bin/notary

Install and run the Notary server:

cd / &&
git clone https://github.com/theupdateframework/notary.git &&
# generate own certificates
cd /notary/fixtures &&
./regenerateTestingCerts.sh &&
# build and start the notary server
cd /notary/ &&
docker-compose build &&
docker-compose up -d &&
sh -c 'echo " notaryserver" >> /etc/hosts'

Please take notice that the code contains the call to the script "regenerateTestingCerts.sh". This is executed to create own certificates and to overwrite the existing ones coming with the Notary sources. For a productive operation you should of course generate/copy keys and certificates in accordance to your companies security policy and exchange them manually with the existing ones.

Test the Notary server:

openssl s_client -connect notaryserver:4443 -no_ssl3

Make the notary server certificate known on the local machine. 

rm -f /etc/ssl/certs/root-ca.pem &&
cp /notary/fixtures/intermediate-ca.crt /usr/local/share/ca-certificates/intermediate-ca.crt &&

Generate an alias for the Notary client

alias notary="notary -s https://notaryserver:4443 -d ~/.docker/trust --tlscacert /usr/local/share/ca-certificates/intermediate-ca.crt"

Pull a test image "Hello-World" we want to sign for test:

docker pull hello-world:latest

Switch Docker to trusted mode and make the Notify server address known:

export DOCKER_CONTENT_TRUST_SERVER=https://notaryserver:4443

Generate a trusted person as a signer and a key pair for it. Example generates the person "hilscher":

docker trust key generate hilscher --dir ~/.docker/trust

In order to test it further you need an account on public Docker Hub registry and you get back a name for your [repository]. So replace the [respository] in the code sequence below with your repositorys name

docker tag hello-world:latest [repository]/hello-world:latest

Generate a repository key (auto-generated when not available) and then add the signer "Hilscher" to this repo. Only this person can modify the repo from now on

docker trust signer add --key ~/.docker/trust/hilscher.pub hilscher [repository]/hello-world:latest

Login to Docker hub ... enter your credentials when asked:

docker login

Push the trusted container image. The meta data is uploaded to the Notary server automatically as well:

docker push [repository]/hello-world:latest

Inspect the image

docker trust inspect --pretty [repository]/hello-world:latest

Now if someone has a trusted Docker running using the command


Tell him first how to reach your Notify server as URL like https://[URL]:4443. Then hand him over also the certificate from here /notary/fixtures/intermediate-ca.crt to make it know on the machine that pulls the images and he will be able to pull any of the trusted image from your repository.

  HilscherAutomation / netPI-bluetooth entrypoint.sh error
Posted by: bbaskii - August-24th-2020, 06:12 AM - Forum: Software - Replies (6)


I am using HilscherAutomation / netPI-bluetooth docker container on Raspberry Pi 3B+. After i build and run, i am getting the following error. 

starting dbus ...
* Starting system message bus dbus
/etc/init.d/entrypoint.sh: line 66: /opt/vc/bin/vcmailbox: No such file or directory
/etc/init.d/entrypoint.sh: line 68: /opt/vc/bin/vcmailbox: No such file or directory
Failed to write reset command
Can't initialize device: Success

Did anyone faced and resolved this issue? If so please help me to fix the error. 

Thanks in Advance,

Heart Container management over the internet >> Hilscher netFIELD
Posted by: Armin@netPI - August-19th-2020, 04:34 PM - Forum: News - No Replies

Hilscher sells the device >netPI RTE 3< (NIOT-E-NPI3-51-EN-RE) loaded with a different system software under the brand "netFIELD" and named it >netFIELD Connect< (NIOT-E-TPI51-EN-RE/NFLD). The hardware is identical but what's the difference between both products?

The device I am talking about is https://www.hilscher.com/products/produc...renfldpns/. Here is a list of what's different:

Main brand                | netPI                          | netFIELD
Device brand name         | netPI RTE 3                    | netFIELD Connect
Device ordering code      | NIOT-E-NPI3-51-EN-RE           | NIOT-E-TPI51-EN-RE/NFLD
Software generation       | V1                             | V2
Software status           | Feature freeze, patches only   | Continual improvements/updates
OS kernel                 | Linux 4.9.x                    | Linux 4.19.x
Security enhanced OS      | Yes                            | Yes
Hilscher signed Linux     | Yes                            | Yes
Real-Time kernel patch    | Yes                            | Yes
SSH access                | No                             | Yes
Root rights               | No                             | Yes, with sudo
Host file system access   | No                             | Yes
Industrial protocols      | PROFINET,EtherNet/IP,EtherCAT  | PROFINET,EtherNet/IP,EtherCAT
Local management web UI   | Hilscher development/design    | Open Source "cockpit" project
Software white labeling   | No                             | Yes
SD card memory size       | 8GByte, type MLC, 384 TBW      | 8GByte, type MLC, 384 TBW
Usable SD card space      | 6.3GB                          | 3.3GB (+3GB backup reserve)
Docker support            | Yes                            | Yes
Docker version            | 18.xx.xx,restricted            | 19.xx.xx, unrestricted
Docker instances          | 1                              | 2, 1x local/1x remote mngabl.
Docker local mgmt.        | Portainer web UI               | Linux console / cockpit UI
Public container repo     | "hilschernetpi" hub.docker.com | "hilschernetpi" hub.docker.com
Remote management         | No                             | Optional, via www.netfield.io portal
Portal subscription       | No                             | Portal usage per device/month
Docker remote administr.  | No                             | via portal
SaaS container ecosystem  | No                             | via portal and app/container store
Fleet software deployment | No                             | via portal
Remote access to local UI | No                             | via portal
Remote software update    | No                             | via portal
Data distribution service | No                             | via portal, RESTful API

In short: >netFIELD Connect< is the logical evolution of netPI. Along with the portal www.netFIED.io the devices allow you to deploy and manage devices and containerized projects centralized from anywhere in the world.

  compatibility netHat with raspberry 4
Posted by: jmontanes - August-18th-2020, 07:09 AM - Forum: Hardware - Replies (2)

Hello, I would like to know if this product:


it is compatible with the raspberry py 4 and how it connects to it