# Error after mappMotion upgrade \[5.24 -\> 5.31\] (-1067377735)

**URL:** <https://community.br-automation.com/t/error-after-mappmotion-upgrade-5-24-5-31-1067377735/12565>\
**Category:** Mechatronics & Motion\
**Tags:** mapp-motion\
**Created:** [September 8, 2026, 7:52am UTC](https://community.br-automation.com/t/error-after-mappmotion-upgrade-5-24-5-31-1067377735/12565 "2026-09-08T07:52:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![krausertm](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/krausertm/32/98_2.png) [@krausertm](https://community.br-automation.com/u/krausertm)\
**Post date:** [September 8, 2026, 7:52am UTC](https://community.br-automation.com/t/error-after-mappmotion-upgrade-5-24-5-31-1067377735/12565/1 "2026-09-08T07:52:42Z")

</div>

Hi all!

Can anyone point me in the right direction how to fix this error?

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

It popped up after switching from 5.24 to 5.31.

I tried checking Hardware.hw, but I didn’t see anything unusual. It seems there was an issue like this before:

 ![image](https://europe1.discourse-cdn.com/brcommunity/original/2X/7/7213c8d90437a40f78985e9b2beaf7022f50e75a.png)

Currently I’m still trying to figure out how to fix it manually… Maybe some of the B&R colleagues can check out the previous ticket? 🙂  
Hopefully that gives a hint on whats causing this issue and how to workaround it manually…

Thanks in advance!

Best Regards!  
Marcel

---

<div class="post-metadata">

**Author:** ![krausertm](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/krausertm/32/98_2.png) [@krausertm](https://community.br-automation.com/u/krausertm)\
**Post date:** [September 8, 2026, 8:04am UTC](https://community.br-automation.com/t/error-after-mappmotion-upgrade-5-24-5-31-1067377735/12565/2 "2026-09-08T08:04:34Z")

</div>

I think I’ve found the issue:

In my upgraded project, the first ACOPOS P3 had

`<Parameter ID="McAcoposTypeID" Location="DriveConfiguration/Module" Value="AcoposP3DConfig" />`

at the top. I noticed in a newly created project as well as for the second ACOPOS P3, it had a different value

`<Parameter ID="McAcoposTypeID" Location="DriveConfiguration/Module" Value="AcoposP3TConfig" />`

After I changed it, it’s working again! 🙂

BR!

---

<div class="post-metadata">

**Author:** ![michael\_w](https://avatars.discourse-cdn.com/v4/letter/m/FF8800/32.png) [@michael\_w](https://community.br-automation.com/u/michael_w)\
**Post date:** [September 8, 2026, 8:25am UTC](https://community.br-automation.com/t/error-after-mappmotion-upgrade-5-24-5-31-1067377735/12565/3 "2026-09-08T08:25:09Z")

</div>

Hi @krausertm ,

glad you found the solution. What I am interested in, since I already started looking into reproducing it here, just for completeness: Which exact hardware module does your project have? P3DConfig is for dual axis, P3TConfig for triple axis, afaict.  
Full name please, if possible 🙂

Thanks and best regards  
Michael

---

<div class="post-metadata">

**Author:** ![krausertm](https://dub1.discourse-cdn.com/brcommunity/user_avatar/community.br-automation.com/krausertm/32/98_2.png) [@krausertm](https://community.br-automation.com/u/krausertm)\
**Post date:** [September 8, 2026, 8:58am UTC](https://community.br-automation.com/t/error-after-mappmotion-upgrade-5-24-5-31-1067377735/12565/4 "2026-09-08T08:58:06Z")

</div>

Hi @michael_w

both drives are 8EI8X8MWTS0.xxxx-1

They’ve been with 5.24 too! I traced it back in and it seems that 2024 a dual P3 was replaced with a triple axis one, but the McAcoposTypeID did not change!

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

Versions at that time were:  
AS: 4.11.6.26  
mappMotion: 5.16.0 XT

So I don’t think there’s an issue in the current mappMotion versions… You could try to check if replacing a dual ACOPOS with a triple one in AS6 still leaves that parameter unchanged though…

Best Regards!