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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 296
» Latest member: fpirou
» Forum threads: 293
» Forum posts: 1,361

Full Statistics

Latest Threads
[SOLVED] Storing data on ...
Forum: Projects
Last Post: Armin@netPI
11 hours ago
» Replies: 18
» Views: 142
Cannot start container
Forum: Software
Last Post: Armin@netPI
Yesterday, 01:00 PM
» Replies: 7
» Views: 30
How to access Root Direct...
Forum: Software
Last Post: Armin@netPI
Yesterday, 11:19 AM
» Replies: 8
» Views: 83
Central CODESYS PLC manag...
Forum: News
Last Post: Armin@netPI
October-15th-2019, 05:04 PM
» Replies: 0
» Views: 6
netPI access for remote P...
Forum: Software
Last Post: Armin@netPI
October-15th-2019, 09:12 AM
» Replies: 3
» Views: 24
[INFO] CODESYS V3.5.15.0 ...
Forum: Software
Last Post: Armin@netPI
October-13th-2019, 08:56 PM
» Replies: 5
» Views: 29
Codesys 3.5.14.0
Forum: Software
Last Post: Armin@netPI
October-9th-2019, 08:28 AM
» Replies: 3
» Views: 32
netPI Node-Red fieldbus n...
Forum: Software
Last Post: Armin@netPI
October-8th-2019, 03:55 PM
» Replies: 5
» Views: 49
[INFO] Support for MTConn...
Forum: Projects
Last Post: Armin@netPI
October-1st-2019, 08:20 AM
» Replies: 8
» Views: 179
32 vs 64 bit OS
Forum: Software
Last Post: Armin@netPI
September-30th-2019, 02:14 PM
» Replies: 4
» Views: 44

 
  Reset netPI to factory settings by software recovery
Posted by: Armin@netPI - January-10th-2018, 09:09 PM - Forum: Software - No Replies

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.


  Webfrontend not reachable
Posted by: timux1991 - January-9th-2018, 01:12 PM - Forum: Software - Replies (3)

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


  netPI not vulnerable to spectre or meltdown
Posted by: Armin@netPI - January-6th-2018, 08:06 AM - Forum: Software - No Replies

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




  netPI for OEMs
Posted by: Armin@netPI - December-18th-2017, 07:52 PM - Forum: Software - No Replies

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.


  [INFO] Best base image to use for own containers
Posted by: Armin@netPI - December-15th-2017, 08:25 AM - Forum: Software - Replies (1)

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


  OpenVPN
Posted by: Armin@netPI - December-15th-2017, 07:56 AM - Forum: Software - No Replies

There is a new container available under https://hub.docker.com/r/hilschernetpi/netpi-openvpn/ using OpenVPN techniques to provide you a secure VPN tunnel into this container (and if iptables command is used additionally in the container to all the other containers installed) if you connect to it with an OpenVPN Client.


  UMTS/LTE support via USB router/modem sticks in a container
Posted by: Armin@netPI - December-6th-2017, 05:27 PM - Forum: Software - Replies (3)

We recognized a high demand for a 3G/4G/UMTS/LTE support of netPI using USB router sticks plugged into one of the four netPI USB ports.

As of today we can tell you that the current delivered netPI firmware 0.9.1.0 does not support the mapping of those USB devices into containers. We are working right now on a solution and we will be providing you a support for those devices in one of the coming firmware updates quite soon.


  Inter-container communication with help of DNS
Posted by: Armin@netPI - December-4th-2017, 07:02 PM - Forum: Software - No Replies

Docker automatically assigns IP adresses to all those containers started in default bridged network mode. A disadvantage is that each time netPI boots different IP addresses are assigned to these containers which makes a predicable inter-container communication impossible.
Instead is it recommended to create a local user-defined network on the system first where Docker is automatically operating a DNS service for. Then, in case a container is started, you can specify this user-defined network as network the container shall run with.
The embedded DNS server provides the discovery service for any container created with a valid name. Only then it maintains the mapping between the container name and its IP address on the network the container is connected to.
Example: Create two containers with names Container1 and Container2. For both containers specify your user-defined network to connect to. A DNS service will be provided automatically on this network. You can then address the containers over their names with a ping command for example like ping Container1 or ping Container2 instead of using their IP addresses.


  CODESYS Control
Posted by: Armin@netPI - December-4th-2017, 03:20 PM - Forum: Projects - Replies (10)

A new container has been published that allows to run "CODESYS Control for Raspberry Pi" on netPI.

The container's repository and image is located here https://hub.docker.com/r/hilschernetpi/n...sys-basis/ ready for your download.


  Loading times for images from Docker Hub
Posted by: Armin@netPI - December-3rd-2017, 01:47 PM - Forum: Software - No Replies

The loading time depends on several factors.

First of all it depends on your Internet connection, then of course on the size of the image. What you must know is that images on the web are packed. Once an image is loaded to netPI Docker starts unpacking it when a container is created of it. Usually the ratio is 1:3 which means an image of a size of 200 MB will be 600 MB effectively on netPI later.
Another parameter that influences the load and start time is the number of layers the image consists of. The more layers the more time is needed to unpack layer per layer.
For an image of a size of 185MB we measured a time for loading and unpacking of about 5 minutes. The start of a container afterwards is just a thing of some milliseconds in relation to how many other containers have to be started at the same time.
After using the +Add container option in netPI's Docker management UI patiently wait as long as the tiny gearwheel turns after you pressed Start container which indicates the image is loaded and about to be started. Once an image is loaded it will not be loaded again and containers of it will be started as a normal service along with all the other netPI's system services.