Arc OK intermitent issues on torch fire

I feel sorry for the OP.....
Update PlasmaC to at least version 0.182
Use a hardware ARCOK if possible
Software ARCOK works properly, it is just trickier to set up.
If torch on is working, leave it as is. To test it, use the MESH/Ignore ArcOK feature in PlasmaC and cut something while watching the ARCOK input on halshow or halmeter.

B.T.W, there might be cases when an opto can cause issues with starting something. To long ....

tommylight wrote: I feel sorry for the OP.....
Update PlasmaC to at least version 0.182
Use a hardware ARCOK if possible
Software ARCOK works properly, it is just trickier to set up.
If torch on is working, leave it as is. To test it, use the MESH/Ignore ArcOK feature in PlasmaC and cut something while watching the ARCOK input on halshow or halmeter.

B.T.W, there might be cases when an opto can cause issues with starting something. To long ....

Ok so i just did around 40 cuts with meshmode and not one issue while starting the arcs, could the machine be getting a false arcok reading within the first 1 second triggering the invalid arc maybe? (short video of screen)

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

File Attachment:

File Name: plas_connections.hal
File Size:1.71 KB

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?