# ACOPOS error 6054: Power stage: Overcurrent

**URL:** <https://community.br-automation.com/t/acopos-error-6054-power-stage-overcurrent/6937>\
**Category:** How-To & Wikis\
**Tags:** acopos, mapp-motion, acp10\
**Created:** [May 14, 2025, 7:35am UTC](https://community.br-automation.com/t/acopos-error-6054-power-stage-overcurrent/6937 "2025-05-14T07:35:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![roidmayrp](https://avatars.discourse-cdn.com/v4/letter/r/FF8800/32.png) [@roidmayrp](https://community.br-automation.com/u/roidmayrp)\
**Post date:** [May 14, 2025, 7:35am UTC](https://community.br-automation.com/t/acopos-error-6054-power-stage-overcurrent/6937/1 "2025-05-14T07:35:05Z")

</div>

Below you will find some ideas and information how to analyse the ACOPOS error 6054: Overcurrent (mappMotion -1067378778) and how the individual current limit value is calculated.

In general, this error is reported if at least one of the current sensors (phase U, V or “W”) or the chopper current sensor reports overcurrent. So here no mains side overcurrent is meant, normally it is about the output current from the ACOPOS into the motor direction.

The error gets reported when one current phase reaches approximately Imax (eff)\*sqrt(2)\*1.35, so a value which is 35% higher then the peak current of the motor connection which can be found in the technical data.

**Example from a specific support case**

8EI8X8HWD10 drive with 24Aeff as peak current per motor connection

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

With that chosen drive the limit for error 6054 on one current phase would be calculated as follows: 24 \*sqrt(2)\*1.35 = 45,8A (in case of the error that value should be seeable on either ParID 209, 210 or 863)

**Analysis/Suggestion**

It is recommended to make a trace (sampling rate: 200µs or higher) of the error situation with e.g. the following ParIDs:

209: VCTRL\_I1

210: VCTRL\_I2

863: VCTRL\_I3

213: ICTRL\_ISQ\_REF

214: ICTRL\_ISQ\_ACT

218: ICTRL\_ISD\_REF

219: ICTRL\_ISD\_ACT

250: SCTRL\_SPEED\_REF

Trigger on ParID 469 \> 0 with a proper negative delay so that the situation before the error can be seen in the trace. Also save the NCT.

Since the overcurrent monitoring takes place in the FPGA with a sampling time of ~3.6µs this means, that there can be situations where the overcurrent value is not reached according the ParID trace (since the sampling rate of the trace is lower).  
The measured phase current value displayed in the trace corresponds approximately to the mean value for a 50µs time range before the latch time.  
It can not be ruled out that an overcurrent was detected in such a case then. But an extrapolation of the current value can give an idea, into which direction the current value was moving and if the limit value could have been reached or not. Below an image which explains that in more detail (but in connection with an 8BVI0220 with limit value 105A where the ParID trace just shows approx. 90A).

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

Note:  
Make sure to check the configured motor parameters inside the AS project and cross-check them with the motor parameters from the datasheet (especially for asynchronous motors). Also check for set value jumps which could cause a current jump as a consequence.