About DanielV

DanielV · ‎07-22-2024

Hello, first of all, these kind of errors are not that relevant and can be ignored by clearing them. To get to the correct cause of the errors, please go to the logbook, (eventually activate the developer view), scroll to the errors and have a look at the dynamic description of them. There is mentioned which diagnostics are not registered at the diagnostic system. Please post this information as well as the versions of your installed apps. Thanks, Daniel

DanielV · ‎09-20-2023

Yes, the Data Layer node /framework/exceptions/* might not be available if the "safe mode" is active which is the case for your problem. When you created a system report and saved it on your laptop, have a look inside the zip file. There should be at least one "rexroth-automationcore.ctrlxex.log" file in "<date>_systemreport.zip\logs\rexroth-automationcore\". In this file you can find further information about the exception. If you can't interpret this file, please post either the file or better the whole system report to the forum so we can have a look at it.

DanielV · ‎09-19-2023

Hi Kelvin, as you can see from the description text, there is an exception (probably at startup) which leads to a restart of the Automation Core app. To get more information about the exception, you can have a look in the Data Layer node /framework/exceptions/* or if not available generate a ctrlX CORE system report which you can find in the question mark symbol in the right upper corner of the control webpage. If you have problems to analyze the exception log, do not hesitate to post it here. Best regards, Daniel

About DanielV

Re: Error in diagnostics

Re: Condition detected that triggered a safe machine state

Re: Condition detected that triggered a safe machine state