Drive errors log in CtrlX logbook

[Anonymous]

Why does a Drive not log into the CtrlX logbook if it has an error? It has the schema as it would log itself into the logbook with main- and detail-code. When a error occurs it is recognized in the motion app and the error can be cleared in the motion app, so reading and writing on the drive is possible. The error that occurs when the drive has an error:

There is no information delivered. The question is why not.

[Jochen_Mueller · Accepted solution]

Currently the connection to the drive is made via the axis profile of the motion app. If the device brings up an error this creates only a motion error in the logbook. (As you mentioned)

In the future we will have a separate drive app running at the core (beside the motion). I do not know any details, but I expect that we will have a better diagnostic info for the logbook.

[Rathinavel]

Hello,

Do we have any updates in the topic? which is the app should be used for the same.

[CodeShepherd]

We already have the DRIVE Connect App version 1.20 available that will write all drive errors (from Rexroth drives) into the ctrlX CORE logbook. See online documentation.

We are also working on a feature that should be available in version 2.06 (RM24.03) that drive errors parameter can be connected via our axisprofile into the ctrlX MOTION so they are displayed when mapped.