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



Search Forums

(Advanced Search)

Forum Statistics
» Members: 424
» Latest member: ferrim
» Forum threads: 416
» Forum posts: 2,127

Full Statistics

Latest Threads
Automate Provisioning for...
Forum: Software
Last Post: Armin@netPI
Yesterday, 03:46 PM
» Replies: 2
» Views: 25
System software V1.2.2.0 ...
Forum: News
Last Post: Armin@netPI
November-26th-2020, 04:25 PM
» Replies: 0
» Views: 44
NIOT-E-NPIX-4DI4DO with n...
Forum: Software
Last Post: zen89
November-25th-2020, 01:06 PM
» Replies: 3
» Views: 272
NIOT-E-NPI3-EN Excessive ...
Forum: Hardware
Last Post: Armin@netPI
November-25th-2020, 07:35 AM
» Replies: 11
» Views: 246
missing the menu items fr...
Forum: Software
Last Post: Armin@netPI
November-20th-2020, 07:41 AM
» Replies: 5
» Views: 175
UL certificate
Forum: Hardware
Last Post: MGharat
November-19th-2020, 11:41 AM
» Replies: 2
» Views: 68
Forum: Hardware
Last Post: Armin@netPI
November-19th-2020, 07:06 AM
» Replies: 1
» Views: 64
NPIX-4DI4DO and NetPi-Nod...
Forum: Software
Last Post: alhammi
November-16th-2020, 01:35 PM
» Replies: 4
» Views: 251
Profinet name lost after ...
Forum: Software
Last Post: Armin@netPI
November-16th-2020, 01:07 PM
» Replies: 7
» Views: 209
Get host MAC via REST API...
Forum: Software
Last Post: bschandra
November-16th-2020, 09:26 AM
» Replies: 4
» Views: 309

  USB to RS485 convetrer
Posted by: MGharat - October-19th-2020, 09:27 AM - Forum: Software - Replies (2)


do USB to RS485 converter work with netPI core directly? we are testing it but face issue. we connected modbus energy meter through our USB to RS485 conveter to USB port of netPI. attached is Modbus flow n settings herewith.
In this we are not able to connect to Modbus meter , no data is received, no error in debug, also the Modbus Read node is always Green even though we remove USB conveter from netPI, I think it is not detected .
one more point we can not search for other serial ports as marked in image.

Is any other setting related to usb driver required? 

Thanks & BR

Attached Files Thumbnail(s)

.txt   nodered flow Modbus RTU.txt (Size: 1.16 KB / Downloads: 0)

  Internet on the fieldbus-side
Posted by: COswald - October-19th-2020, 08:52 AM - Forum: Software - Replies (2)

Good Morning Hattersheim,

my problem is, that I have a Industriel PC behind the NIOT-E-TPI51-EN-RE and this is not able to access the Internet.
This would be great for normal situation, but we have to be able to do so.

What is special here? We don't use the fieldbus side in ProfiNet-Mode, but in LAN-Mode via the LAN-Enabler Docker-Container.
I have also installed the TOSIBOX-Soft-Lock, which is working fine. Without any special routes in the Gateway.
Is where something special with this?

Here are some screenshots of the LAN and route settings in the gateway:



I'm looking forward reply.

Kind regards,

Carsten Oswald

  NIOT-E-NPIX-4DI4DO with netpi-netx container
Posted by: WalterSchaefer - October-16th-2020, 02:17 PM - Forum: Software - Replies (3)

Hello Armin.
I use NIOT-E-NPI3-51-EN-RE with NIOT-E-NPIX-4DI4DO module inserted.
I work with profinet, thats why  ntpi-netx-programming-examples container is installed.
Now I need access to 4DI4DO.
1. Where can I find GPIO numbers, to which this module is connected?

2. How can I get access to GPIOs from ntpi-netx-programming-examples container? (preferably from C++ code). Do I need to install wiring-pi?

Thank you.
Best regards,

  Get host MAC via REST API inside container
Posted by: bschandra - October-14th-2020, 01:30 PM - Forum: Software - Replies (4)

Hi all,

we need the MAC address of the host system inside a container on the Hilscher netPI.
For me it seemed to be a suitable solution to get the LAN settings, and also the MAC, from the Hilscher REST API.

As described in this thread, we first logged in with the admin user to get the authentication cookie.

curl -L -k -X POST 'https://<HOST-IP>/login' -H 'Content-Type: application/json' -d '{"username":"admin","password":"<PASSWORD>"}'

With the authentication cookie we are able to get various information from the API. The following requests all worked.
curl -L -k -X GET 'htps://<HOST-IP>/?page=infocenter' -H 'Cookie: <COOKIE>'

curl -L -k -X GET 'htps://<HOST-IP>/get/devicestatus/getCPUStatus' -H 'Cookie: <COOKIE>'

curl -L -k -X POST 'https://<HOST-IP>/system' --header 'Cookie: <COOKIE>; Content-Type: application/x-www-form-urlencoded' -d "argument=reboot"

But the request to get the LAN settings always responds the following:
{"status":"Failed","message":"Permission denied"}

Here's the request as we tried:
curl -L -k -X GET 'htps://<HOST-IP>/get/networksettings/lansettings' -H 'Cookie: <COOKIE>'

The admin user has all read & write rights in the application, also for the REST API.

Can anyone imagine what we are doing wrong here?

Is this a good way to get the MAC-address of the host system or is there a better solution?

Many thanks in advance.

Best regards

  USB camera
Posted by: tad - October-9th-2020, 02:48 PM - Forum: Software - Replies (4)

Dear Armin,

Is there any condition to use a USB camera under standard netPI software environment (Yocto Linux + Docker)?
For example, can I use a UVC compatible camera (from Node-RED)?

(I would like to know what kind of USB camera I should purchase.)

Thank you very much for your information.
Best regards,

  netPI profinet device name
Posted by: WalterSchaefer - October-7th-2020, 09:29 AM - Forum: Software - Replies (2)

I try to connect NHST-T100-EN/PNM V3 with NIOT-E-NPI3-51-EN-RE over profinet.

On the NIOT I've installed netpi-netx-programming-examples container.
There a /home/pi/PNS_simpleConfig was started (with sudo). At the first start all necessary drivers were installed. Now the application works well (as I understand). Every second it shows a string: "netX watchdog is alive: nnnn"

NHST device was not able to communicate with it.
I plugged NIOT Profinet port to PC and made a scan with "Ethernet device setup" tool. As expected, IP was And device name was empty.
When I set up device name to "netx51repns" manually by this tool, all errors gone. Now everything looks good.
But now I wonder why device name was not setup. I use your pre-built exmaple "PNS_Simpleconfig". I did not compile it by myself, just run binary.

At the othe hand, I did some debug an found, that device name is set up correctly in SetConfigParams function:

memcpy( ptSetConfig->abNameOfStation, "netx51repns", sizeof( "netx51repns" ) );

I've set a breakpoint to this line and device reached it.
Do you have ideas how to make example working without manual device name setup?
Thank you.

  compatibility btw RPi 3B and netPI regarding to microSD card
Posted by: tad - September-30th-2020, 06:09 AM - Forum: Software - Replies (4)

Dear Armin,

I would like to confirm whether my recognition is correct or not, please.

There is a micro SD card which is running on a raspberry pi 3B.
This software environment can be also launched on netPI when this micro SD card is inserted into netPI.
Is that correct?

As far as I investigated, the above is correct.
- I prepare a 32GB micro SD card with FAT32 format.
- Raspbian and Docker are installed on the SD card on RPi 3B+.
- I take out the SD card from RPi 3B+ and insert it to netPI.
- Raspbian and Docker are correctly running on netPI.

Thank you very much for your information.
Best regards,

  Accessing a modbus device connected to RTE port from Node-RED
Posted by: tad - September-29th-2020, 09:36 AM - Forum: Software - Replies (10)

Dear Armin,

I need you help, please.

I'd like to separate network segments for IT and fieldbus.
For this, using netPI RTE 3, I created a container of 'hilschernetpi/netpi-netx-ethernet-lan'.
A modbus device is now connected to the fieldbus segment (RTE port).

Then, I want to output data to the modbus device using 'Modbus-Write' node with Node-RED.

But, I think 'Modbus-Write' node recognizes that TCP is the standard IT port.
Because Modbus communication doesn't start at all.

As a test, I confirmed that Modbus communication can be done properly when the modbus device is connected to the standard IT port.

Therefore, my question is:
Is it possible to make 'Modbus-Write' node recognize RTE port?

Thank you very much for your support.
Best regards,

Attached Files Thumbnail(s)

  netPI with 32GByte High Endurance SD card
Posted by: Armin@netPI - September-29th-2020, 08:25 AM - Forum: News - Replies (3)

Today I want to announce netPI will be getting available in near future in a 32GByte industrial SD card version featuring high endurance.

The new SD card of type PSLC is not only delivering you 4 times more capacity but also a 5 times higher endurance and 5-10% more read access speed.

Instead of the 384TBW (Terabytes Written) endurance the 8GB SD card we sold netPI so far is providing, the new 32GB delivers you an endurance of 1920TBW instead.

While I was always speaking critical in threads/post when it came to recommend netPI for database use cases such as storing data on netPI periodically, now with the new 32GB high endurance SD card I see no problem with it at all. The 32GB card's endurance can be compare to those featured by today's SSD disk drives you are typically using in personal computers.

P.S.: this thread relates back to my post from 2017 where I was talking about the SD card durability in general.

  Freshly received netPI cannot boot - Invalid partition 2
Posted by: bfjp - September-25th-2020, 11:02 AM - Forum: Software - Replies (7)


I've received two netPIs NOIT-E-NPI3-EN. Taken fresh from the box one of the pis did not want to boot up properly and cannot find the kernel image

The boot screen message is:
    Wrong Image Format for bootm command
    Error: can't get kernel image!
    SCRIPT FAILED: continuing...
    ** Invalid partition 2 **

I tried the recovery tipps found in the forum with the recovery image from the USB Stick.
It results in a verification error:
    initrd[1]: Running device_data ...
    WARNING: Failed to connect to lvmetad. Falling back to device scanning.
    Reading all physical volumes. This may take a while...
    WARNING: Failed to connect to lvmetad. Falling back to device scanning.
    mount: mounting /dev/mapper/rootfs-BACKUP on /mnt failed: No such file or directory
    mount: mounting on /tmp/nvdsrc/ failed: Invalid argument
    cp: can't stat '/tmp/nvdsrc/nvd/device_data': No such file or directory
    initrd[1]: Verifying device data...
    initrd[1]: Device data not present / failed to verify device! Reboot may recover data.
    Error - device verification not possible. Device data need to be restored! Please contact distributor. Boot process stopped!

Further data of the affected Pi

  • Part No: 1321.510
  • MAC B827EBA9E8E6
  • Date code 20/16
  • Data Matrix inhalt: 1321510220453
Can it be recovered by myself at this point? And how? Or does it need servicing / replacement?

Best regards