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.

cancel
Showing results for 
Search instead for 
Did you mean: 

Watchdog error

Watchdog error

Nspire
Occasional Visitor

 

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.

Nspire_0-1710493988243.png

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.

Nspire_1-1710494535011.png

Nspire_2-1710494569392.png

 

4 REPLIES 4

CodeShepherd
Community Moderator
Community Moderator

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)?

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?

Sgilk
Frequent Contributor

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.

CodeShepherd
Community Moderator
Community Moderator

Are there any news? Could this issue been solved?

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist