FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We have started the migration process.
This community is now in READ ONLY mode.
Read more: Important
information on the platform change.
03-15-2024 10:24 AM - edited 03-15-2024 10:30 AM
Good morning all,
I already tried to search but i could not find any solution to this problem. I'm still trying to debug but with no success until now.
I develop an app (c++) to read multiple information from ethercat and i can read all of what i want and create multiple nodes in datalayer to show the processed information. When i run my app in the virtual core, i don't have any problems or errors. However, when i run in a real core, after some minutes i have the errors in the following image.
When the errors occur, ethercat stops and consequently my app stops reading information. if I acknowledge the errors, ethercat starts again and my app also. But some minutes after is the same problem.
I will leave here some more prints in order to try to help.
03-15-2024 11:36 AM
Moved to corresponding sub forum SDK as self made apps are used.
It seems that you app is influencing the realtime capability of the ctrlX OS and so the watchdog of the scheduler jumps into account.
Could you give some more information how you read information from the EtherCat?
Could you please share a system report of your ctrlX CORE (see how to)?
03-15-2024 12:07 PM - edited 03-15-2024 12:47 PM
I have some loops using readSync and one separated loop using sharedmemory.
For readSync some loops with this:
comm::datalayer::DlResult dlResult = _client->readSync(addressEthercatSlaveConfigInfo, &slaveInfoData);
Edit: I tried to debug now and I commented all the code related to sharedmemory and the error disappeared.
The code I used is similar to the SDK example. what could be causing this?
03-15-2024 02:00 PM
Hi @Andrefs ,
Could you post the sharedmemory related code or a generic example? It seems that section is taking too long to execute and tripping the watchdog.
09-06-2024 09:34 AM
Are there any news? Could this issue been solved?