November-18th-2019, 03:22 PM
(This post was last modified: November-18th-2019, 03:30 PM by Armin@netPI.)
1.) Here is the link where we statee which SANDISK card is used today: https://forum.hilscher.com/Thread-SD-card-duration
2.) Once the device has a FLASH configuration active and then an application like Node-RED now tries to "re-"configure the netX in RAM mode (cause it does not know about the FLASH configuration is active) this will fail for sure. And yes netX contains an ARM CPU ... and once the firmware is started and a FLASH configuration is found active then netX will be immediately starting PROFINET communication, independent of the Raspberry Pi host CPU has been started or respectively the container has been started. As long as no user application is runnin, netX will exhange the data in internal buffers.
3.) No Docker in no way can be configured to start containers in any order. This function does not exists. The only thing you know is for sure that they will be started.
2.) Once the device has a FLASH configuration active and then an application like Node-RED now tries to "re-"configure the netX in RAM mode (cause it does not know about the FLASH configuration is active) this will fail for sure. And yes netX contains an ARM CPU ... and once the firmware is started and a FLASH configuration is found active then netX will be immediately starting PROFINET communication, independent of the Raspberry Pi host CPU has been started or respectively the container has been started. As long as no user application is runnin, netX will exhange the data in internal buffers.
3.) No Docker in no way can be configured to start containers in any order. This function does not exists. The only thing you know is for sure that they will be started.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
