November-16th-2020, 01:07 PM
(This post was last modified: November-16th-2020, 03:32 PM by Armin@netPI.)
Well ... if you run Node-RED and Ethernet LAN at the same time then each of the containers is grabbing the single resource netX51 industrial network controller for its own purpose. This will no and never work. You can either let netPI a PROFINET device or you let him do Ethernet LAN. Both at the same time is not possible.
This is by the way why the cifx0 loading procedure fails. The LAN container has a firmware file that is loaded into the netX51 chip during container start and also the Node-RED container has another PROFINET firmware file that loads it into netX51 .... if both are loading the netX51 chip over SPI the same time or with a little delay in between this will cause a conflict on single SPI bus.
As I said each firmware load will delete the netX flash memory completely. So once the Node-RED configures the chip to be a PROFINET device ... right after that the LAN container overwrites the firmware and the flash memory is getting empty again and the given PROFINET name is gone.
Thx
Armin
This is by the way why the cifx0 loading procedure fails. The LAN container has a firmware file that is loaded into the netX51 chip during container start and also the Node-RED container has another PROFINET firmware file that loads it into netX51 .... if both are loading the netX51 chip over SPI the same time or with a little delay in between this will cause a conflict on single SPI bus.
As I said each firmware load will delete the netX flash memory completely. So once the Node-RED configures the chip to be a PROFINET device ... right after that the LAN container overwrites the firmware and the flash memory is getting empty again and the given PROFINET name is gone.
Thx
Armin
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)