Hello Armin,

Now we want to use netPI to connect MES system and the machine tool which on field at the same time. Both network are standard TCP/IP ethernet protocol, they are different network segment, but on our netPI just has one ethernet interface. We have considered the way to use WiFi. Do you have any other suggestions for this question? 

Looking forward your reply.

Lingyue

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.

Hi,

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?

Thanks,
david.

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 and instantly once you enabled it by a GPIO. The advantage now is to be no longer compelled to handle switching in software by a non-realtime driver that is causing jitter of the switching times switching from TX mode back to RX mode after a request has been sent. If then a responder is sending back data too fast it could easily happen that the first incoming chars are getting lost if the switching was 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 gets 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:

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.
   

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.

Thx
Armin

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

To complete the netPI documentation I want to offer to you the official UL compliance letter from year 2018 and the FCC documenation from year 2017.

Attached Files

  NOA Letter.pdf (Size: 153.51 KB / Downloads: 16)
  2ANEG0001_DSS.pdf (Size: 124.79 KB / Downloads: 6)
  2ANEG0001_DTS.pdf (Size: 125.01 KB / Downloads: 4)

Hi.

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.        

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! 

-Alexander