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



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
9 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
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

  NodeRed and EtherCAT
Posted by: Schranz - September-2nd-2019, 03:37 PM - Forum: Software - Replies (1)

Currently I use a netPI RTE 3 as a profinet client with a hilschernetpi/netpi-nodered-fieldbus container.
Now I need to do the same as an ethercat client. Possible with NodeRed (FIELD ecs)?

The sample container hilschernetpi/netpi-netx-programming-examples works.

  create container in Portainer v1.12.4
Posted by: dcatteeu - August-29th-2019, 09:59 AM - Forum: Software - Replies (2)


I have a NetPi with Portainer v1.12.4. 

I can't seem to figure out how to start a container from an image that is available on my local docker registry.

I can specify a docker registry, but the NetPi has no way of knowing where to find it. I think I need somehow to specify it's ip address (adding it to /etc/hosts) and its certificate (adding it to /etc/docker/certs.d/<myregistry>/ca.crt).

Am I missing something or is this not possible in this old version?


  NPIX-RS485 with auto direction control now available
Posted by: Armin@netPI - August-26th-2019, 07:18 AM - Forum: Hardware - No Replies

We changed the RS-485 transceiver used on module NIOT-E-NPIX-RS485 in REV#2.

The new part - MAX13488E - features auto direction control and is switching between TX (transmit) and RX (receive) mode automatically once you enabled it. The advantage is to be no longer compelled to handle switching in software causing unpredictable/prolonged switching times and loss of serial receive data if too long.

The MAX13488E is pin compatible to the previous used transceiver SN65ALS176 in #REV1. Instead of using the TX_EN pin to switch between TX/RX as done before on #REV1 you have now just to set the TX_EN pin to "high" state a single time and automatic direction control is enabled.

With Node-RED for example you could just inject a "true" to a rpi gpio node directed to GPIO17 (TX_EN) and you are done:

[{"id":"287692d1.c61e06","type":"inject","z":"d31910c1.fd0618","name":"","topic":"","payload":"true","payloadType":"bool","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":295.5,"y":599,"wires":[["6bbb3ed9.4bb6d8"]]},{"id":"6bbb3ed9.4bb6d8","type":"rpi-gpio out","z":"d31910c1.fd0618","name":"","pin":"11","set":"","level":"0","freq":"","out":"out","x":483.5,"y":599,"wires":[]}]

After pulling the TX_EN pin to high state the NPIX-RS485 module will get compatible with any serial communicating program or Node-RED node.

Download the latest NPIX modules documentation highlighting the modules' difference in the download section here .


  Exporting and importing container images
Posted by: Armin@netPI - August-23rd-2019, 10:39 AM - Forum: Software - No Replies

Sometimes it is necessary to move a ready evolved container from one netPI to another or to save its current state to an external location.

For this purpose the netPI Docker web GUI features the export and import function.

Here are the steps how to proceed

  1. Supposing you have a running container then click it in the Containers overview page and click Stop first of all to block its SD memory card activities.
  2. In the same window you have the option to create an image of exactly this container. Type in an Image name and press Create. This may take a while.
  3. On the Images overview page you can now recognize a new image named as provided representing a 1:1 copy of your container.
  4. Click its image id and you'll get the option Export this image. Click it and after some minutes (be patient) you'll get a file image.tar as output within your browser context. Save it to anywhere you want.
  5. The way back is to use the Import function within the Images overview page to load it back onto any device.
Make sure you have the netPI system software V1.2.0.0 running since this version uses a prolonged timeout value for the browser connection to successfully bridge the long response time of the image creating function.


  Accessing Siemens S7 PLCs over Node-RED
Posted by: Armin@netPI - August-23rd-2019, 08:01 AM - Forum: Projects - No Replies

Today I want to highlight a Node-RED node that is able to read/write data from/to a Siemens PLC (S7-1200 or S7-1500) over Ethernet(PROFINET) on netPI.

The node's home is here https://flows.nodered.org/node/node-red-contrib-s7comm and is maintained by Hilscher.

We have included this node in netPI's Node-RED Docker Container you can pull from repository "hilschernetpi/netpi-nodered" from Docker Hub on your netPI.

If you have an "old" type of PLC such as S7-300 or S7-400 having no Ethernet connectivity but MPI/PROFIBUS instead you can use this device https://www.hilscher.com/products/produc...nl-50-mpi/ in between netPI and PLC and your are able to use ths S7  node too.


Information NPIX-RCAN with node-red-contrib-canbus node
Posted by: Patrick@netPI - August-22nd-2019, 02:36 PM - Forum: Projects - No Replies

The standard "node-red-contribute-canbus" node is not able to parameterize the interface.
But the attached flow can do it. The interface name of the NPIX-RCAN is "can0".

For immediate use you can use the "hilschernetpi/node-red" Docker Image. This this includes the "node-red-contribute-canbus" node.

You can buy the CAN module at NIOT-E-NPIX-RCAN


Node-RED flow

[{"id":"4d07c78.7bb0238","type":"tab","label":"Flow 1","disabled":false,"info":""},{"id":"e5be7b4b.3043c8","type":"canconfig","z":"","channel":"can0","bitrate":"1000000"},{"id":"eb182264.f344f","type":"candump","z":"4d07c78.7bb0238","name":"candump","vconfig":"e5be7b4b.3043c8","x":120,"y":140,"wires":[["620e867b.c95678"]]},{"id":"620e867b.c95678","type":"debug","z":"4d07c78.7bb0238","name":"","active":true,"console":"false","complete":"true","x":310,"y":140,"wires":[]},{"id":"cca38704.e615e","type":"exec","z":"4d07c78.7bb0238","command":"ip link set can0 down","addpay":false,"append":"","useSpawn":"false","timer":"","oldrc":false,"name":"Interface down","x":320,"y":60,"wires":[["60373f1f.8fd19"],[],[]]},{"id":"e6062ba0.bee45","type":"exec","z":"4d07c78.7bb0238","command":"ip link set can0 type can triple-sampling on bitrate ","addpay":true,"append":"","useSpawn":"false","timer":"","oldrc":false,"name":"Interface setup","x":660,"y":60,"wires":[["b6405ee3.c72bc"],[],[]]},{"id":"b6405ee3.c72bc","type":"exec","z":"4d07c78.7bb0238","command":"ip link set can0 up","addpay":false,"append":"","useSpawn":"false","timer":"","oldrc":false,"name":"Interface up","x":850,"y":60,"wires":[[],[],[]]},{"id":"bef5bf08.aa042","type":"inject","z":"4d07c78.7bb0238","name":"Init can0","topic":"","payload":"","payloadType":"num","repeat":"","crontab":"","once":false,"onceDelay":0.1,"x":140,"y":60,"wires":[["cca38704.e615e"]]},{"id":"60373f1f.8fd19","type":"change","z":"4d07c78.7bb0238","name":"1MBit","rules":[{"t":"set","p":"payload","pt":"msg","to":"1000000","tot":"str"}],"action":"","property":"","from":"","to":"","reg":false,"x":490,"y":60,"wires":[["e6062ba0.bee45"]]}]

  UL certified since 2018
Posted by: Armin@netPI - August-21st-2019, 01:21 PM - Forum: News - No Replies

To complete the netPI documentation I want to offer to you the official UL compliance letter from year 2018

Attached Files
.pdf   NOA Letter.pdf (Size: 153.51 KB / Downloads: 6)

  Used Pins
Posted by: JAAAW - August-16th-2019, 10:06 PM - Forum: Hardware - Replies (1)


The NetHat uses pins 24, 21, 19 & 23 for SPI0 and GPIO pins 22 & 23.

Which pin ensures the power supply? Are there any other pins that are used?


  [SOLVED] Help with fieldbus node
Posted by: Farani - August-14th-2019, 02:21 PM - Forum: Software - Replies (5)


I am trying to receive and send boolean value to my test PLC with the fieldbus node. I was able to rec from the PLC without error. But i was unable to send to the PLC through the fieldbus output node. How can i test this?

Error message : OUT_NODE expects the property 'payload' as an object

Attached are the snapshots.        

  BLE pairing problems with bluez 5.50
Posted by: abmn - August-8th-2019, 07:52 AM - Forum: Software - Replies (1)

Dear community,

I encounter problems pairing BLE devices with the NetPi using the current Bluetooth Docker image (https://hub.docker.com/r/hilschernetpi/netpi-bluetooth). As BLE device I'm using a Bosch XDK (Bluetooth 4.2/BLE) with BLE tutorial example. No security ("Just Works") is used for pairing. Other BT 4.2 or 5.0 device I tried had the same issues. 

Here's what I did:

"hcitool device" shows that the BT RF device is available ("hci0   B8:27:EB:A4:D7:88")

"dmesg" shows no errors or warnings, Bluetooth configuration looks fine

In "bluetoothctl"
- default agent is on, BT device is on
- "list" correctly shows the BT RF device ("Controller B8:27:EB:A4:D7:88 BlueZ 5.50 [default]")
- "scan on" correctly lists all available BT devices around, also the Bosch XDK ("Device FC:D6:BD:10:27:10")
- I trust the device: "trust FC:D6:BD:10:27:10"
- "pair FC:D6:BD:10:27:10" at first seems to work: "[CHG] Device FC:D6:BD:10:27:10 Connected: yes", the device's services and characteristics are displayed. 
- But after seconds, the device is disconnected: "Failed to pair: org.bluez.Error.AuthenticationCanceled"

"dmesg" now shows error "Bluetooth: SMP security requested but not available"

The same device pairs, connects and runs nicely with iOS or Android phones using free BLE tools as "LightBlue". 

Happy to read your ideas!