Hello everyone.
The axis lights are blinking green. I checked the manual to see what’s wrong, but it doesn’t show any problems. All four of my axes are in the same condition: one HWS17 and one HWT4X5.
Can you tell us what the problem? Axis are not moving at all?, not moving as expected? etc…
-Which leds are green ( I assume from ACOPOS P3? or Mullti?), which software are being used? ACP10 or mappmotion?
-If axis are not moving when the command are sent, you may check the logger to see any entry, out the output from function bloc.
-Is the enable signal activated?
-Are you using safeMotion, if so, is the safemotion properly activating the axis?
Please include more information.
1 Like
Hi there,
have you already looked inside the logger in Automation Studio? There you can normally find all relevant information about errors and co.
Please also tell us more about your used AS version, with all mapp Modules, so troubleshooting will be easier!
BR
Julian
Hello, I’m using an Acopos P3. The driver enables, but I can’t power on the axis because the “ready to power on” message doesn’t appear. The axis lights are green but blinking. I’m using an ACP10. I can’t figure out why this is happening.
I checked the logs but there doesn’t seem to be any problem. The “ready to power on” message doesn’t appear in mpaxisbasic.
For the Acopos P3, the LED codes can be found here:
Ax1/Ax2/Ax3 - LED status indicators
So, it would seem these are the possible errors:
The module is not ready for operation.
-
Examples:
-
No signal on one or both enable inputs
-
DC bus voltage outside the tolerance range
-
Overtemperature on the motor (temperature sensor)
-
Motor feedback not connected or defective
-
Motor temperature sensor not connected or defective
-
Overtemperature on the module (IGBT junction, heat sink, etc.)
-
Disturbance on network
As others have mentioned, the logger will tell you more. But from my experience, the most likely
cause here are the enable inputs. Are you sure those have +24V? Are they connected to a safe output
or E-stop?
1 Like
Hello, is it a SafeMotion Drive? Whats the material and/or serial number?
Lg Michael
1 Like
I would expect a missing enable signal or missing 3 phase power supply. Check network command trace of the drive.
Hello,
If ReadyToPowerOn is not TRUE you can just PowerOn and then you will see the Error Messages due to some missing preconditions.
There was a Community Thread where one member had mentioned a way to trigger this errors without a power on command but i don’t remember, and could not find in short.
With the Errors you can continoue your diagnosis.
Greetings
Michael
1 Like
If you write PARID 340 [CMD_ERR_STATE_INTO_FIFO] to 1 on the axis giving you trouble, it will give you all the reasons that keep it from going into ReadyToPowerOn state.
Good luck!
2 Likes
Hi @eem.ferhat ,
Please upload the SystemDump, so far we are guessing based on our motion experience.
We don’t know yet if you are using ACP10 or mapp Motion, in general we have a lot of messages on the network command trace but in case of mapp Motion you can open Drive Log and display only the messages related to the drive with issue with a simple filter.
Normally when I’m on rush during commissioning in similar case, I open axis test window(ACP10) or mapp Cockpit(mapp Motion) and I do 2 things:
a)Execute an home command with mode direct: if you have an encoder issue you see error/s
b)command a power of the axis (as Michael wrote in his comment): you see the error for example for temperature sensor, main power…
Thanks
Ciao
Valerio
Apparently ACP10 is in use
1 Like
Thank you, your information was very helpful.
Hi @eem.ferhat , Could you share with us, when you have time, which was the cause of the problem on your ACOPOS P3?
Thanks
Ciao
Valerio