October-8th-2019, 01:13 PM
(September-19th-2019, 10:56 AM)Armin@netPI Wrote: Yes this is exactly what I expected.
I can confirm that running Fieldbus Container at the same time as Codesys container on one netPI causes this problem. I have seen this with my device too.
This happens exactly at the time when Codesys is performing its licence checks (this is our assumption) after around 5 minutes of running. During this license check it talks to the GPU of the Raspberry CPU and does a lot of other things. This mechanim seems to have influence on the netX communication over SPI and interrupts it so that the netX watchdog triggers (default 1000msec) and the PROFINET protocol stack stops to work within netX and finally the Node-RED node stops operation. The SPI communication is reestablished by the netX driver but then it is too late.
The only chance you have is to manually increase the watchdog time that is configured by the Fieldbus webConfigurator dialog along in netX. The file responsible for configuring the watchdog time is /usr/lib/node_modules/WebConfigurator/PROFINET_IO/Device/WebContent/Structures/ConfigurationStruct.js. In there you find a string
Code:this.WdgTime=1e3
1e3 = 1 exponent 3 = 1000 -> so 1000msec
Change it to "10e3" and save the file.
After that change you need to go again into the Fieldbus Web configurator and click "save" to overwrite the existing configuration file. Then redeploy the Node-RED flow
Overall we cannot recommend to run Codesys and netX based communication (Fieldbus container) at the same time.
Thx
Armin
Hi Armin,
Thank you for your reply. I'm sorry for the delay in my feedback.
As you suggested, I have changed the Wdgtime to a larger number, however, the problem is not solved (as shown in the attached pictures).
Could you please help me with this?
Much appreciation.