# mappMotion mcHOMING\_ABSOLUTE (migrating from ACP10)

**URL:** <https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454>\
**Category:** Mechatronics & Motion\
**Tags:** mapp-motion\
**Created:** [August 28, 2026, 6:50am UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454 "2026-08-28T06:50:18Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![dominik.lehnberg](https://avatars.discourse-cdn.com/v4/letter/d/FF8800/32.png) [@dominik.lehnberg](https://community.br-automation.com/u/dominik.lehnberg)\
**Post date:** [August 28, 2026, 6:50am UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454/1 "2026-08-28T06:50:18Z")

</div>

Hi everyone,

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?

Thanks in advance for your help!

---

<div class="post-metadata">

**Author:** ![tomas.proks](https://avatars.discourse-cdn.com/v4/letter/t/FF8800/32.png) [@tomas.proks](https://community.br-automation.com/u/tomas.proks)\
**Post date:** [August 28, 2026, 9:16am UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454/2 "2026-08-28T09:16:41Z")

</div>

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](https://help.br-automation.com/#/en/6/motion/mapp_motion/mapp_axis/konzept/steuerung/referenzierung/homingrestorepos.html)  
Homing mode and remanent variable can be configured in drive configuration:

 ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/1/1c3dd5b494eeaa7df0afd7fe08f9275ed94a20a1.png)  
Than you are just using mode mcHOMING\_DEFAULT after startup, which activates the homing mode from drive configuration → mode “Restore position” in this case.

---

<div class="post-metadata">

**Author:** ![dominik.lehnberg](https://avatars.discourse-cdn.com/v4/letter/d/FF8800/32.png) [@dominik.lehnberg](https://community.br-automation.com/u/dominik.lehnberg)\
**Post date:** [August 28, 2026, 9:36am UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454/3 "2026-08-28T09:36:06Z")

</div>

Hi Thomas,

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?

---

<div class="post-metadata">

**Author:** ![tomas.proks](https://avatars.discourse-cdn.com/v4/letter/t/FF8800/32.png) [@tomas.proks](https://community.br-automation.com/u/tomas.proks)\
**Post date:** [August 28, 2026, 9:55am UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454/4 "2026-08-28T09:55:40Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Matt\_Buck](https://avatars.discourse-cdn.com/v4/letter/m/FF8800/32.png) [@Matt\_Buck](https://community.br-automation.com/u/Matt_Buck)\
**Post date:** [August 28, 2026, 2:26pm UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454/5 "2026-08-28T14:26:16Z")

</div>

I believe the parameter is still on the drive. [172: Homing: Offset](https://help.br-automation.com/#/en/6/ncsoftware/acp10_parameter/html/homing_offset.htm). 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](https://help.br-automation.com/#/en/6/motion/mapp_motion/mapp_axis/programmierung/kernbibliotheken/mcacpax/funktionsbausteine/mc_br_processparid_acpax/fb_procparid.html) 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).

---

<div class="post-metadata">

**Author:** ![Samuel](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/samuel/32/155_2.png) [@Samuel](https://community.br-automation.com/u/Samuel)\
**Post date:** [August 31, 2026, 6:03am UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454/6 "2026-08-31T06:03:51Z")

</div>

Hi Dominik,

here you can find, how it works:

[https://help.br-automation.com/#/en/6/motion%2Fmapp\_motion%2Fmapp\_axis%2Fkonzept%2Fsteuerung%2Freferenzierung%2Freferenzierung.html](https://help.br-automation.com/#/en/6/motion%2Fmapp_motion%2Fmapp_axis%2Fkonzept%2Fsteuerung%2Freferenzierung%2Freferenzierung.html)

 ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/9/94f1bf3a5725ce839e9c23183067ede83a7277fe.png)

Instead of the described direct homing you can of course use Block torque for the initial homing.

BR, Samuel

---

<div class="post-metadata">

**Author:** ![Martin.Schrott](https://avatars.discourse-cdn.com/v4/letter/m/FF8800/32.png) [@Martin.Schrott](https://community.br-automation.com/u/Martin.Schrott)\
**Post date:** [August 31, 2026, 11:39am UTC](https://community.br-automation.com/t/mappmotion-mchoming-absolute-migrating-from-acp10/12454/7 "2026-08-31T11:39:23Z")

</div>

Hello @dominik.lehnberg ,

> [@dominik.lehnberg](#):
>
> As far as I understand, `homing.status.offset` is no longer available in mapp Motion, correct?

With mappMotion this value can be read with [MC\_ReadParameter](https://help.br-automation.com/#/en/6/motion/mapp_motion/mapp_axis/programmierung/kernbibliotheken/axis/funktionsbausteine/mc_readparameter/fb_readpar.html), “ParameterNumber” = 1019.

BR, Martin
