Hi,
I would like to inquire, how well NetPI performs under very humid conditions, say (70-100%).
Thanks

During the last month testing a netPI running Node_RED I encountered twice a profinet failure (LED ERR Red Solid).
Is there somewhere a log file, which could give me some more information what could have caused the error?

Kann der netPI so verwendet werden, daß er eine Hersteller ID für Profinet erzeugt um z.B. einen Antrieb zu simulieren?

Ist die straton Laufzeitumgebung von CopaData sicher auf dem netPi unter Docker nutzbar?

https://www.straton-plc.com/en/news/succ...raspberry/

In case you address your netPI with its hostname like https://NTB827EB237AC1 instead of its IP address then opening the Docker Web-GUI fails on a mouse click.

Internet Explorer 11 interprets a hostname base address as an "Intranet" address and automatically switches on the compatibility view by any reason we don't know. This leads to a script error in Docker Web-GUI and stop processing the web site.

Make sure you disable the Internet Compatibility View checkbox and everything runs as it should.

Whenever it comes to reset netPI to factory settings because

* you have forgotten your netPI login credentials
* you did a misconfiguration of LAN/Wifi settings causing netPI to be no longer accessible
* you just want to reset it to factory default by any reason

a software recovery needs to be executed via a USB stick containing the system software.

We will be publishing netPI's system software image as a download link on this web site soon. Meanwhile you'll get the latest system software on demand emailing to netpi@hilscher.com instead.

The recovery procedure is described in the TOP 10 FAQ list here.

Hello,
I hava a problem with my netPI. It's no longer accessible via the webfrontend. When I boot it up, it obtains its IP from the DHCP server and is reachable via that IP for a very short time. If I am lucky I can access the landing page for like five seconds. After that I does not reply to any http requests, nor does it respond to a ping. I can't reach the control area or the docker area. The only thing connected to the PI is the network cable and the power supply.
I am not sure if that is new, but the red LED "ERR NS" is permenantly on.
The IP is well known and not the issue.
What can I do about that. Is a factory reset inevitable?
Best regards
Timux

Thanks to Eben Upton, one of the Raspberry Pi founder, we got an easy to understand explanation why netPI isn't vulnerable to the exploits spectre and meltdown.

Here is his post Spectre and Meltdown

You get netPI in single pieces or a few of them at amazon. Additionally we offer direct OEM business with this platform. There are two options:

a.) Full featured netPIs as you get them at amazon (sealed 8 GB SD card, preloaded software, pre-assembled) in a batch size of always 120 pieces and multiples.

b.) Bare metal netPIs with no SD card and no software, separated housing, PCBA, cooling pads, screws for self-assembly, completely open for your SD card and software in a batch size of 120 units and multiples.

Get in touch with Hilscher's sales channel under sales@hilscher.com if you have interest in any of these businesses.

Any container image is based on a parent image as described here. You can build your own base image or use already published ones.

We really appreciate the work of company Resin.io in generating loads of Docker base images for different hardware platforms. One of their public repositories on Docker Hub named armh7f-debian is compiled for armv7hf architecture based platforms and delivers seamless compatibility with Raspberry Pi 2/3 respectively netPI.

Company Resin.io is very active in providing latest images of released versions of debian whenever they come out and all their images support cross build of ARM code on x86 machines allowing automated builds on Docker Hub. This is why we feel your are in good hands using their offerings and recommend to use the Debian:jessie image as base image for your work. Also we use it as basis for most of our example netPI Docker images provided here.

Since netPI is not offering SSH connectivity the Docker CLI cannot be used. Instead a Pi 3 have to be used for developing netPI Docker images.

This command pulls the latest Debian:jessie image onto your Pi 3:

docker pull resin/armv7hf-debian:jessie

This command starts a container from the image and jumps into a bash shell:

docker run -ti --entrypoint=/bin/bash resin/armv7hf-debian:jessie