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

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 334
» Latest member: mmilos
» Forum threads: 317
» Forum posts: 1,487

Full Statistics

Latest Threads
PM - develope OPC UA Serv...
Forum: Software
Last Post: Armin@netPI
January-17th-2020, 11:12 AM
» Replies: 5
» Views: 15
SPI access using extender
Forum: Hardware
Last Post: Armin@netPI
January-16th-2020, 03:15 PM
» Replies: 8
» Views: 30
Read analog sensor values
Forum: Hardware
Last Post: crolfes
January-16th-2020, 01:47 PM
» Replies: 2
» Views: 13
connecting Mitsubishi via...
Forum: Hardware
Last Post: Armin@netPI
January-14th-2020, 10:58 AM
» Replies: 11
» Views: 36
Using MariaDB on NetPi
Forum: Software
Last Post: Armin@netPI
January-13th-2020, 06:47 AM
» Replies: 21
» Views: 56
NPIX-4DI4DO keep inputs g...
Forum: Hardware
Last Post: Armin@netPI
January-9th-2020, 09:09 AM
» Replies: 1
» Views: 7
connec Mitsubishi using M...
Forum: Hardware
Last Post: Armin@netPI
January-8th-2020, 03:24 PM
» Replies: 1
» Views: 7
Mosquitto MQTT Broker
Forum: Software
Last Post: Armin@netPI
December-16th-2019, 07:22 AM
» Replies: 2
» Views: 78
Automatic setup of NetPI ...
Forum: Software
Last Post: Armin@netPI
December-12th-2019, 03:23 PM
» Replies: 3
» Views: 19
running ethercat slave
Forum: Projects
Last Post: MGharat
December-10th-2019, 10:06 AM
» Replies: 6
» Views: 20

 
  Default listening TCP/UDP ports
Posted by: Armin@netPI - February-9th-2018, 01:36 PM - Forum: Software - No Replies

By default netPI listens to the following ports:

TCP:
[ul]
[li]Port 80,nginx -> web server / reverse proxy [/li]
[li]Port 443,nginx -> web server / reverse proxy [/li]
[li]Port 49152, upnpd -> UPnP daemon [/li]
[/ul]

UDP:
[ul]
[li]123,ntpd -> Network Time Protocol daemon [/li]
[li]137,nbnsd -> Netbios Name Service [/li]
[li]1900, upnpd -> UPnP daemon [/li]
[li]5353, avahi-daemon -> Zeroconf [/li]
[li]60843, avahi-daemon -> Zeroconf temporary port [/li]
[li]36517, avahi-daemon -> Zeroconf temporary port [/li]
[li]41429, dnsmasq -> DNS proxy temporary port [/li]
[/ul]


  Custom NPIX modules
Posted by: Armin@netPI - February-9th-2018, 12:33 PM - Forum: Hardware - No Replies

NPIX modules tailored to your requirements - in which your ideas can add to the basic functions of netPI - is a service we offer.

What you need are three things:

  •    A PCBA
  •    A metal bracket
  •    Two screws

There are two options how to come to an own NPIX module:
  •    You share your idea with us. We make the design and take care of the whole production on a bid basis.
  •    You take care of the design. You deal with the metal bracket manufacturer. You do the production yourself.

For your reference you find the NPIX connector pinout document here and the board outline dcoument here. Also you find the user manual of the Hilscher designed NPIX modules in the "downloads" section here as well as a 3D model of the metal bracket within the provided netPI 3D CAD model.

Next to certain 3,3V, 5V, 24V and GND signals the remaining 36 pins of the NPIX connector are wired to the Broadcom CPU BCM2837 (Raspberry Pi chip) or the netX Industrial Network Controller (on netPI RTE 3 only). Roughly one half of the pins connects to the BCM CPU, the other to netX. With those connecting to BCM we set the focus on specific signals only. Connected are a UART, an I2C, an SPI and some GPIOs. Keep in mind that the BCM SPI0 signals are not available since they are used for communications between the BCM CPU and netX CPU.

Tell us about your project and we will come together to a solution. Mail your idea/concept to netpi@hilscher.com


  NTP setup (Network time protocol)
Posted by: zulliger@software-natives.ch - February-7th-2018, 07:09 PM - Forum: Software - Replies (1)

One of the first things you need to do, once a virgin NetPI3 got unboxed, is to setup NTP, according to the "netPI - Getting Started with the netPI" video. Otherwise, customers run into severe issues, such as not being able to run Docker containers. The reason for the need of NTP is obvious, but I wonder why doesn't the NetPI3 either:
- Setup a generic NTP by default, or
- Offer this setup in a kind of wizard, e.g. right after changing the password?
Is this an oversight? Are there any technical issues I don't grasp? Or is it planned, but you didn't yet had time to implement it?


  DHCP/DNS issue: Couldn't access NetPI3 out-of-the-box
Posted by: zulliger@software-natives.ch - February-7th-2018, 06:56 PM - Forum: Software - Replies (5)

Initially, when I connected my new NetPI3 to my LAN, I wasn't able to access it by the described instructions (opening the browser and enter the "name" mentioned on the sticker). I also couldn't "ping" it because the "name" could not be resolved.

After some debugging, I could resolve the issue by reconfiguring my router (pfsense): The DHCP-Server didn't automatically update the DNS entries. I can't remember the very details, because already some days past since then, but may claim is: I think that the way to initially access the NetPI3 is not working under all circumstances (possibly including some "pretty popular" ones, as my "pfsense" setup was quite virgin).

Question: Are you aware of that? If not, would it help if I reproduce the issue and provide more information on this?

Another possibly related question: In one of the forum posts you mention the Tcp/Udp ports opened by the NetPI3. According to that post, bonjour is running as well. Why? Can it be used as another option to initially access the NetPI3?


  General Forum Rules and Guidelines
Posted by: zulliger@software-natives.ch - February-7th-2018, 07:43 AM - Forum: netPI - Ruggedized Raspberry Pi with Industrial Ethernet - Replies (3)

I'd like to keep up with new information. Therefore, I'd like to get notified by emails upon new forum entries. Either for each post and reply or just upon new posts or maybe as a daily summary (most preferred option). I couldn't find a way to setup this right now. Am I missing something? If not: Are you planning to implement such a feature?


  System software V1.1.0.0 out now!
Posted by: zulliger@software-natives.ch - February-2nd-2018, 08:10 PM - Forum: Software - Replies (2)

Thanks for the new system software. Installation worked like a charm.

Just today, I was looking for a new software, but did not look at the forum. Instead, I checked out https://www.netiot.com/netpi/industrial-...-on-netpi/. Over there, I clicked the "download"-link - but that link is broken (404). That made me think that no "public" software was yet released. Maybe it'd be good to fix the link.


  Container IP address - Network Options
Posted by: kimsmyth - January-29th-2018, 11:56 PM - Forum: Software - Replies (2)

Hello all, looking for a little advice, all I want is a RaspberryPi (with Codesys) container that I can set (and change afterwards) its IP address. What network option do I need when creating the container (Bridge, host, Container).


  Create own trusted Docker registry server
Posted by: Armin@netPI - January-27th-2018, 02:55 PM - Forum: Software - No Replies

netPI pulls images from trusted Docker registry servers only. Trusted servers provide a trusted certificate from an official Certificate Authority (CA) to rely on its digital signature. The most popular trusted Docker registry is Docker hub. But you can run trusted Docker registry servers yourself on-premise as well. We show you how.

Here is how you set up your own trusted Docker registry server with help of an official Certificate Authority such as Let's Encypt.

  • First you need a domain name (hostname) of your server. Get one from noip for example. Let's suppose you got a name mydockerregistry.ddns.net.
  • As next configure DynDNS service on your Internet Router as described here so that your router is reachable through your domain name over the internet.
  • Then set up a physical server. Run Linux on it for quick results. Ubuntu will do it.
  • Configure your Internet Router to forward the TCP ports 80 and 443 to the server. Port 80 is needed to demonstrate control over the domain during one time certification process. Port 443 is needed to run the Docker registry across.
  • For an automated certificate issuance you need a web server installed on your server. For quick results we recommend Nginx. To install it simply call sudo apt-get install nginx.
  • Additionally install CertBot, a software that is automatically requesting a certificate from Let's encrypt for your domain. On the web site select as software Nginx and as system Ubuntu and it will be providing you an installation instruction. Execute the proposed commands on your server.
  • During the procedure you will be asked for the domain name you want the certificate for. Enter your domain name mydockerregistry.ddns.net(our example) at this stage.
  • The certificates and keys will be genrated and stored on your server in the folder /etc/letsencrypt/live/mydockerregistry.ddns.net/. Port 80 forwarding on your Internet Router is no longer needed.
  • Now install Docker on your server as described here
  • The certificates and keys need a renaming and a merge so that the Docker registry can use them. Call
    cd /etc/letsencrypt/live/mydockerregistry.ddns.net/cp privkey.pem domain.keycat cert.pem chain.pem > domain.crtchmod 777 domain.crtchmod 777 domain.key
  • Finally run the Docker registry with the following docker command
    $ docker run -d \  --restart=always --name registry \  -v /etc/letsencrypt/live/mydockerregistry.ddns.net:/certs \  -v /opt/docker-registry:/var/lib/registry \  -e REGISTRY_HTTP_ADDR=0.0.0.0:443 \  -e REGISTRY_HTTP_TLS_CERTIFICATE=/certs/domain.crt \  -e REGISTRY_HTTP_TLS_KEY=/certs/domain.key \  -p 443:443 \  registry:2
  • Now you are able to acess your Docker registry over mydockerregistry.ddns.net. e.g. call the command docker pull mydockerregistry.ddns.net/myimage for example to pull an image named myimage across the internet.
If you want to turn your Docker registry server into a local server you should close all forwarded ports in your Internet Router first and then add the hostname to your server's files /etc/hosts and /etc/hostnames e.g. 127.0.0.1 mydockerregistry.ddns.net(our example). Then run a local DNS server in your network translating the hostname to the local IP address of your server and that's it. All access to mydockerregistry.ddns.net are running now locally.


  Kann keine Docker Images laden
Posted by: rjenni - January-25th-2018, 07:44 AM - Forum: Software - Replies (1)

Habe einen netPI RTE3. Kann keine Docker Images installieren. Folgende Meldung wurde beim ersten Versuch angezeigt sobald ich versuchte ein Image herunter zu laden:
https://dseasb33srnrn.cloudfront.net/reg...7VWIS5YZ6Q: x509: certificate has expired or is not yet valid

Auch ist mir aufgefallen, dass die ERR NS Led dauernd leuchtet. Im Handbuch steht dazu, dass es einen IP Adressen Konflikt gibt. Das kann aber unmöglich sein, es sind nur drei TN im Netzwerk und alle haben eine eigene IP Adresse. Auch das WLAN ist konfiguriert in einem unterschiedlichen IP Range.

Mittlerweile sehe ich diese Meldung nicht mehr, jedoch bricht der Vorgang nach etwa 10 Sekunden erfolglos ab.

Kann man irgend eine Log-Datei auslesen, um ihnen die Diagnose zu erleichtern?


  Specification Inquiry
Posted by: ephluxiot - January-23rd-2018, 10:39 AM - Forum: Hardware - Replies (2)

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