Arc OK intermitent issues on torch fire

I see from your ini file that you are using Mode 1. PlasmaC does not care about the arc voltage for Arc OK in Mode 1, that is the responsibility of the plasma source, PlasmaC only uses the Arc OK signal from the plasma source.

You seem to have two different issues, one is where it sees the Arc OK then loses it and the other is where it doesn't even see the Arc OK. First of all I would trace all the ARC OK wiring from the plasma source to the 7i76 card, checking for loose connections etc. If you are comfortable opening up the plasma source I would check inside it as well.

If you don't see anything wrong then I would try two things, one would be to add the debounce as described in an earlier post and the other would be to add some contact wetting as described in other threads.

cheers ill check into these things tomorrow.

snowgoer540 wrote: Also, if I were you, I would debounce the arc-ok input assuming it is a mechanical relay from your plasma cutter. The following changes will give you 5 servo-thread counts of deounce (if your servo-thread period is 1mS, then a 5mS debounce). This may (or may not) save you some headaches later.

Edit your plas_connections.hal file and make the following changes:



Change:

Code:

loadrt debounce cfg=3

To:

Code:

loadrt debounce cfg=3,1

Add:

Code:

setp debounce.1.delay 5 addf debounce.1 servo-thread

Change:

Code:

net plasmac:arc-ok-in hm2_5i25.0.7i76.0.0.input-10 => plasmac.arc-ok-in

To:

Code:

net plasmac:arc-ok-in hm2_5i25.0.7i76.0.0.input-10 => debounce.1.0.in net plasmac:debounced-arc-ok debounce.1.0.out => plasmac.arc-ok-in

So i added this to the hal file
if i wanted to add a bigger delay to the arkOK do you know exactly what i would change?

Also checked the wiring and its solid, I did also just update from v0.144 to v0.185 before making this topic.

luftlupus wrote:

snowgoer540 wrote: Also, if I were you, I would debounce the arc-ok input assuming it is a mechanical relay from your plasma cutter. The following changes will give you 5 servo-thread counts of deounce (if your servo-thread period is 1mS, then a 5mS debounce). This may (or may not) save you some headaches later.

Edit your plas_connections.hal file and make the following changes:



Change:

Code:

loadrt debounce cfg=3

To:

Code:

loadrt debounce cfg=3,1

Add:

Code:

setp debounce.1.delay 5 addf debounce.1 servo-thread

Change:

Code:

net plasmac:arc-ok-in hm2_5i25.0.7i76.0.0.input-10 => plasmac.arc-ok-in

To:

Code:

net plasmac:arc-ok-in hm2_5i25.0.7i76.0.0.input-10 => debounce.1.0.in net plasmac:debounced-arc-ok debounce.1.0.out => plasmac.arc-ok-in

So i added this to the hal file

Attachment not found

if i wanted to add a bigger delay to the arkOK do you know exactly what i would change?

Also checked the wiring and its solid, I did also just update from v0.144 to v0.185 before making this topic.

You should change this line:

Add:
Change the 5 to whatever you feel appropriate. This number (5 in this case) is the number of servo-thread counts. If your servo thread is set to 1mS, this equates to 5mS. Just so you know.

Do you still have issues going on?

Yes still same issue persisting. 20-30% of the time the arc will try to fire for a split second then pause and say invalid ArcOK signal. but ran mesh mode like what was suggested and didn't have one issue running 50 cuts. arcOK light was on solid on every cut. I can only thing there's a split second every now and then when the arcOk signal coming back is just that little bit to slow and it pauses itself due to no arcOK.

Is it "valid arc lost" or "no arc detected"

phillc54 wrote: Is it "valid arc lost" or "no arc detected"

valid arc lost..

Try the following in yout connections.hal file:
you can adjust the time to suit, the above is 0.1 seconds.

phillc54 wrote: Try the following in yout connections.hal file:

Code:

setp plasmac.arc-lost-delay 0.1

you can adjust the time to suit, the above is 0.1 seconds.

Ok this is great my "valid arc lost" issue has been resolved i did 120 cuts no worries. Thanks everyone for the help with troubleshooting that issue

I then ran some actual cutting jobs and ran into this issue which was the other side to this topic,
Every now and then when it goes to pierce the metal it fires and blows the metal out but thinking it hasnt removed the metal due to no arcOK coming back it tries to start the arc again but the metal is already gone so its got noting to arc onto hence ruining the start point for that cut. >>

When that happens do you notice if the Arc OK led is lit on the GUI.