Is the Control Panel WebUI the only way to provision the Basic Settings (the ones in the Control panel) or is there a possibility to automate the Provisioning (maybe also via an additional package, maybe the Control Panel has some REST interface, ...) ?
We have uploaded today a new system software in the version V1.2.2.0 as recovery packages for your netPIs.
Here is the changelog
allow IP setup of netPI RTE 3 Real-time Ethernet ports via netPI web UI "network" settings if the container hilschernetpi/netpi-netx-ethernet-lan is used in host mode
fixed docker start problem after an unintended device power cycle caused by a written but blank docker host configuration file /etc/docker/daemon.json triggered by a missing file system sync thereafter
Info about how to update your device you find there as well in the FAQ in the "For Developers" section.
ATTENTION! Applying a recovery package sets back a device to factory default and deletes all the containers installed and the settings configured. So make sure you saved all your data before executing the recovery.
Hello,
We have two NIOT-E-NPI3-EN units that we are currently evaluating internally for a host for a software product we are currently developing. Both units carry part #1321.510. Both units have been configured identically with both the internal gateway manager settings and with the current Docker configuration.
But one of the units is showing a constantly higher CPU usage that has brought the web server down to unusable performance levels and cannot be used. The poor performing unit has a CPU usage of 26 to 32%, even in an idle state, whereas the unit that functions correctly has a CPU usage of 3% in an idle state.
When evaluating the downloaded syslog on the poor performing unit, we noticed the log file is excessive in size, over 630MB in size compared to just a few MB's in size for the properly functioning unit on any given day sense we started testing. When evaluating the log, we have found over 341 entries in the first minute of operations. The vast majority of the entrees seem to be system related and we cannot determine their meaning. I included an attachment of the first minute of the Syslog for startup reference.
The date code on the inoperable unit is 19/38 and the date code on the properly functioning unit is 20/16.
Can someone please advise what we can do to continue to try to trouble shoot this unit or if there is another direction we should take to remedy this units performance? Please let me know if there is any other information I can provide as well?
I've been scouring for solutions in this forum for the past few days and I could not find the issue I am facing.
I currently have an RTE with me, with NPIX DIO expansion and a Keyence retroreflective sensor that is supposed to output 0 or 1 in NetPi Node-Red.
My container configuration is the same as per the github instructions of NetPi Node-Red (mapped /dev/gpiomem, running on privilege mode etc.)
My flow for a start is simple:
1st attempt:
-NPIX Input node to Debug node to see if any value comes out.
The outcome of this flow:
-The Input node status shows (cleared)
-The msg.payload only shows 0 once
From a documentation I read:
-Any unconnected ports on the DIO module will show 0
2nd attempt:
-Swapped the sensor signal wire from DIN 0 to 1
-Still same result
3rd attempt:
-Read the documentation and this forum and found out that DIN 1 coincides with RPi GPIO 14
-Installed RPi-GPIO nodes from the palette, used the input node and finally mapped the GPIO 14 and connect it to debug node as per 1st attempt.
-It still shows zero
I have checked that physical connection using a multimeter:
-Shows 24V, coinciding with the 24V external power supply that I am using to power up NetPi and the retro sensor
-NPIX Expansion slot PWR led shows green
I think Im missing out on something here. Please advice.
Many thanks!
Alhammi
[EDIT] Added attachments for better clarity of the issue. Also, this is likely to be a novice issue as this is only the second time that I used NetPi for developments.
Posted by: tad - November-10th-2020, 05:13 AM - Forum: Software
- Replies (5)
Dear Armin,
Today, I pulled a docker image of Node-RED (hilschernetpi/netpi-nodered) to netPI RTE 3.
When I tried to configure PROFINET IO items, I didn't see the menu items such as Project, Download,,,.
If you may find any mistakes, would you please give me advice?
Note:
- I tried the above with both system software 1.2.0.0 and 1.2.1.0.
Thank you very much for your information.
Best regards,
we found an issue regarding the naming in Profinet:
The NetPi loses its Profinet name after restarting the NetPi via the config page and after power loss and we even observed a case when rebooting the container we had to name the Netpi another time. After renaming the NetPi with the PLC (Profinet Master) the communication is working as expected until another shutdown.
Right now we are not sure where the problem comes from.
We are using the netPI for a Dockerized application stack to retrieve and store data of a customer's production process.
Now we want to visualize the data with an Angular SPA that's running in Docker.
With this we are reaching the bounds of the netPI's hardware resources.
As the new Raspberry Pi 4 is out, I am wondering if there's a new version in planning that's based on the RasPi 4.
Do you have this on your agenda in the near future?
New dialog "Proxy" in control panel under tab "Network" to configure a HTTP,HTTPS,FTP proxy
Removed Wifi channel 14 support for region Japan which was not allowed
Set WPA2 standard as security method in "Wifi Access Point" mode. WPA1 supported no more
Corrected problem that the service "Wifi Access Point DHCP server" may not work after an unintended (power loss) shutdown and reboot
Corrected problem that "Wifi Access Point DHCP server" does not work if there is no eth0 Ethernet connection is active (cable inserted) during boot times
Info about how to update your device you find there as well in the FAQ in the "For Developers" section.
ATTENTION! Applying a recovery package sets back a device to factory default and deletes all the containers installed and the settings configured. So make sure you saved all your data before executing the recovery.
