During normal operation, C80 suddenly restarted and after startup, C80 entered the N/A mode.
At this moment, AS is unable to connect with C80, and SDM is also unable to connect.
Only after performing a USB update on the C80 will it return to normal.
What are the possibilities for C80 to enter the N/A category?
If you can not get Access to the Device with the Automation Studio its difficult to get a logger entry. So hard to tell what goes wrong. I just start Brainstorming โฆ
I would start with checking the Versions of B&R Software in comparison to latest version.
Does the application use some File-Write functions FileIO-Library or similar? If yes can they be temporary disabled for testing.
If the Device does not reconnect after the restart it looks like some how the AR-Installation gets corrupt but this is only a assumption.
Is it the only device showing this issue / do you have other C80 for Comparision?
Can you install a Empty Dummy Project, does it show same issues?
How long is the intervall of the issue daylie / weekly โฆ ?
Michael Bertsch is right with his comment to update to the latest versions.
We had the issue that Linux and Automation Runtime due to the paralel access to memory trigger a race condition in the hypervisor. If you use Automation Studio 4 this issue is fixed with Automation Runtime O4.93. If you use Automation Studio 6 this issue is fixed with Automation Runtime 6.4.