Hello,
I have three Acopos P3 SafeMotion, two 8EI034HWSS0.0200-1 and one 8EI017HSS0.0600-1, and two works fine, but one (8EI034HWSS0.0200-1) has some problem, the LED SE is constantly on. I installed the latest version of the SafeMotion hardware module and AcoposP3, but it did not help.
It has been doing this since the first power up.
I am using AS (4.12), Safedesigner (4.4.1), ACP10/ARNC0 5.29.1, mappSafety 5.24.1, AR P4.93, the main controller is 4PPC80.101E-10A.
From logger:
Hardware config:
Hi Mihajlo,
This looks like a holding brake error.
Have you double checked the wiring to ensure that the brake is wired correctly? If your other axes are functioning correctly, I recommend comparing the wiring between this axis and the others.
Hello @s4gia ,
I have a similar problem as you had. Did you solve it?
On one Acopos P3 (8EI034HWSS0.0200-1) the LED SE is constantly on. It has been doing this since the first power up. I am using AS (4.12), Safedesigner (4.4.1), ACP10/ARNC0 5.29.1, mappSafety 5.24.1, AR P4.93, the main controller is 4PPC80.101E-10A.
I have three Acopos P3 SafeMotion, two 8EI034HWSS0.0200-1 and one 8EI017HSS0.0600-1, and two work fine, but one (8EI034HWSS0.0200-1) has some problem, the LED SE is constantly on. I installed the latest version of the SafeMotion hardware module and AcoposP3, but it did not help.
From logger:
Does anyone have any suggestions on what I should try and how to solve the problem?
BR,
Mihajlo
this is my Hardware config.
Did you already try to exchange the two 8EI034HWSS0.0200-1 ?
To see if the problem sticks to this specific hardware or if it might be related to the connected cabling or thelike…
@Mihajlo_Tatovic I have moved this question into this topic of yours since it’s the same issue asked twice
Please keep it to one topic next time.
@Zwi Fyi in case you are looking for this topic, this should ping you 
Hello @marcusbnr ,
I tried swapping drivers and again this driver is in the same error status.
So I most suspect a software (some register or firmware collision) problem because the driver is new and has been behaving like this since the first time it was turned on.
@michael_w Thank you for merging the topics..
I realized later that it was better to start a new topic because the problem is similar but not exactly the same.
BR,
Mihajlo
If you changed the drives and the error went along WITH the drive, the drive itself has a fault. Unfortunately it’s not very clear from your phrasing.
I have two same Acopos P3 SafeMotion (one works and one fail), to check the wiring/cable I did the following:
I switched each cable from the working driver to the faulty one, and from fault driver to wrking driver.
The situation is the same, the faulty driver still gives the same error.
This means that the problem is not with the cabling and the rest of the hardware. The problem is with the ACOPOS P3.
And Roman’s suggetion was to switch the drives and see if the issue stays on the same drive.
But it looks like, just as said, that the drive is at fault. Contact your local B&R office and get it exchanged I guess
