I have a question regarding the migration from ACP10 to mapp Motion.
Currently, we home our axes with absolute encoders using mcHOMING_BLOCK_TORQUE. After the homing procedure, we store the offset value from the axis object (homing.status.offset).
On every system restart, we use this stored value together with mcHOMING_ABSOLUTE to restore the correct absolute position.
As far as I understand, homing.status.offset is no longer available in mapp Motion, correct?
If that is the case, what is the recommended workflow in mapp Motion for this use case? Is there a replacement for homing.status.offset, or is there a different approach that B&R recommends for retaining and restoring the absolute position after a restart?
Hello,
I would suggest to use mcHOMING_RESTORE_POSITION mode. During your calibration procedure using mcHOMING_BLOCK_TORQUE are the homing offsets stored in remanent memory and than are used after next CPU startup for restoring of correct position. So you do not have to take care about the offset on your own.
See help: Homing restore position
Homing mode and remanent variable can be configured in drive configuration:
Than you are just using mode mcHOMING_DEFAULT after startup, which activates the homing mode from drive configuration → mode “Restore position” in this case.
thank you for your reply. We are not using remanent variables for storing the offsets. Everything that is relevant after system restart is stored in a .csv file. The reason why we are not using mcHOMING_RESTORE_POSITION is this fact:
The B&R Help says:
“The application is not permitted to write to this variable! The data is protected by a checksum. An error message will appear when attempting to restore the position if this data is overwritten.”
If we would read the offsets from .csv file and write it to the RestorePositionVariable, the mcHOMING_RESTORE_POSITION would would fail afterwards because of a checksum error, correct? Or would this also work in mappMotion?
I think, if you save the complete structure of variable of type McAcpAxRestorePosType including the checksum, than you should be able restore the position without an error.
Sorry I do not know how the gather the absolute offset in mapp Motion.
I believe the parameter is still on the drive. 172: Homing: Offset. It’s just not brought back to the PLC automatically via the ACP10AXIS_typ. After homing is complete you should be able to do a MC_BR_ProcessParID_AcpAx to read that ParID.
As I’ve had it explained to me, the move from ACP10 to mapp Motion didn’t remove any ParIDs that already existed on the drives. It cleaned up/removed the complexity that ACP10 had and merged the ACP10 and ARCN0 functionality into one unified architecture. The ACOPOS drives are still the same;. Hence I can use the same ACOPOS drive on either an ACP10 or mapp Motion system.
(I’ve been in B&R long enough that I had written and supported applications with nc_Actions, before there mapping table, before the initialization parameters in the hardware view, before alot of the ease of use that ACP10 developed over time).