QtPlasmaC v2.9 do not wait for the time in parameter "Start Fail Timer"

More
18 Dec 2024 19:48 #316927 by Diel
Hi everyone.
I am setting up a Plasma Cutter with QtPlasmaC v2.9 in mode 2 with one parallel port and step motors and a Hypertherm PowerMax 105.
The configuration is working fine but I am having a hard time with the ARC OK signal as the message of "valid arc lost" keep showing up.
It looks like it does not wait the time set on parameter "Start Fail Timer" after turning the torch on to turn on the message. It also does not try to turn on the torch again after the time set on parameter "Retry Delay" not even once (even with the parameter "Max Starts" set to 3.
As outputs I just configure the axis motors and Plasma Torch ON.
As inputs I have ESTOP IN, Plasma Float Switch, Plasma Move Up, Plasma Move Down and Plasma Arc OK.
It does have to be able to wait for the Arc OK signal and try to restart the plasma if the signal does not show up

Any information will be helpfull to find out where I have a problem with my configuration.

Thank you all.
 

Please Log in or Create an account to join the conversation.

  • tommylight
  • tommylight's Avatar
  • Away
  • Moderator
  • Moderator
More
18 Dec 2024 23:00 #316958 by tommylight
Moved to PlasmaC section.
-

It looks like it does not wait the time set on parameter "Start Fail Timer" after turning the torch on to turn on the message. It also does not try to turn on the torch again after the time set on parameter "Retry Delay" not even once (even with the parameter "Max Starts" set to 3.
 

You are looking in the wrong place, that is all valid if arcOK is not detected
In your case it is detected and lost, and this almost always happens due to interference from lack of proper grounding and shielding, so that is the first thing to check, recheck and only when those are OK move on to other stuff.
One thing that helps with troubleshooting is setting a bit of delay for the ARCOK signal in hal.

Please Log in or Create an account to join the conversation.

More
19 Dec 2024 03:14 #316968 by snowgoer540
If this is happening at the end of cuts, it’s generally caused by the arc going out either because the slug dropped or the material was already cut while the machine still has some distance to move before reaching the M5.

If that’s the case, then you can set a lost arc delay as described here:

linuxcnc.org/docs/devel/html/plasma/qtpl...html#_lost_arc_delay

Please Log in or Create an account to join the conversation.

Moderators: snowgoer540
Time to create page: 0.058 seconds
Powered by Kunena Forum