without any change in motion app / axes profile since some days motion app is hanging in Configuration/Running. The only way is to set it to running manually. Then everything is working fine till next time of booting (restart, shut off/on).
The only thing which was changed at the ctrlX was adding a SD-card and doing some PLC code changes. But these don't have this effect.
I tried to activate trace but it is not possible to set variables to true....wether in setup nor in service mode.
Solved! Go to Solution.
Please, like you also mentioned, try to switch on traces, then save your app data (active configuration), set logbook to persistent and reboot control. Afterwards do a system report so we have all information necessary.
Writing Data Layer values are not limited to an operation mode and should be possible at any time.
Trying activating trace but it's not possible. Can't write the parameters.... wether in service, configuration or run mode..
I already saw your picture above. But it just shows that you have entered (or it was already entered) "false". "Write" and "Discard" buttons stay gray/disabled as long the value in the window above do not change. So just overwrite "false" with "true" and then they will get active.
Ah, sorry, didn't know that it is possible to write / type directly into that field. Yes, after renaming 'false' to 'true' it's poosible to 'write'.
So, now there is a app-data-archive and a diagnostic log. Hopefully that contains the needed information to solve that issue.
As said, after switching to running everything is working fine without any issue whole day long.
Your configuration seems to be fine and in the logbook only AxisProfile messages are available.
Could you please provide us a screenshot in the error case of the tooltip of the partially operating notification in the top bar? So we can see which parts are OP and which not.
Also an export of all diagnostics after reboot would be better. So we also see what the rest of the system is doing.
OK, I tried to get the information needed. See diagnostic log.
After booting it looks like this:
There is a 'i' icon which means...
Optional variables aren't the reason, isn't it?
The configuration looks like this:
Don't know what to assign...Things which are needed are assigned.
Setting Axis in RUN manually it works without any issue till next boot.
That means, with every start up, first to do is connecting with Core to set Motion App / Axis in RUN