Moveback on arclost and THC on/off state

[Robertspark]

Andrew,
M209-m212 do directly toggle two pins in sync with motion.

Because the neuron does not use the uccnc THC internal control you can use them for whatever you want.

Check you are looking at the latest screenset of the development one I sent you as the original neuron screenset I have does not have all the ports pins and check boxes listed as per the current default screenset

[Robertspark]

Andrew, sorry I am WRONG , the original neuron screenset does have the ports and pins for M209/M210 + M211/M212

Why can you not use them as standard high speed synchronous IO's?
{they have no effect on the stand alone neuron THC + z axis as we are not using the z-axis}

[shad]

Rob, the M209/M210 + M211/M212 commands allow to activate/deactivate antidown and antidive future. But the state of the correspond pin is change when antidive or antidown event issue.

[Robertspark]

Rob, the M209/M210 + M211/M212 commands allow to activate/deactivate antidown and antidive future. But the state of the correspond pin is change when antidive or antidown event issue.

Andrew, I don't think that is 100% correct.

In order to use M209/M210+M211/M212, you need to enable THC (M205) or they will not work

M209/M210 = THC antidive Down {when feedrate drops belowthe threshold percentage setting}.
Firstly change the "threshold percentage" to zero (0%)

Now you can toggle the output when ever you want in sync with motion.

M211/M212 = THC anti down
This you can toggle at any time {providing M205 THC / AVC is enabled}

Remember UCCNC is not intelegent with regards to THC control {it cannot see / know THC "events"} ..... It does not know what the voltage is..... it can only see ArcOK, THCUP/THCDN.
So if you want to lock the z-axis from diving you need to enable M211.
If you want to use automatic feedrate antidive, you have to enable M209 + set the feedrate threshold percentage

UCCNC cannot see the "event" you talk about in your post.
________________________
Suggestion:

Open up UCCNC and go to the configuration >> I/O Setup tab.
Setup the pins for AVC, THC antidive + THC antidown (say port 2, pins 4,5 & 6 {easy to see})

Now you can either toggle the checkboxes or go to the run screen and use the MDI to enter: M205, M209 + M211 and M206 one at at time and each time you enter the Macro in the MDI have a look at the diagnostics screen and the pins status, you will see them change.
_________________________

No it is not "the best" solution.... because you must enable M205 in order to use M209 + M211....... but that all depends what you want to use M209+M211 for.... do you need to have a "master" output enabled or do you want them run individually.

With the neuron it does not matter which macro you actually use for AVC as again UCCNC is not intelegent ..... the only "event" it sees is arc OK {and if you set the feedrate threshold to zero (0%) then the feedrate will have no effect on M209

[shad]

Rob, you right.
I could not even think that this way works. I am set the "threshold percentage" to zero (0%) and M209/210 turn on/off corresponding pin even machine is not run
Thank you!

[shad]

Hmm, Today I decided to use M209/M210 commands for control AVC from code....
Strange, I can't to drive THC antidive pin using M209/M210 commands. Threshold value set to zero. THC enabled.
If I am set threshold to 100% and enable antidive - antidive corresponding pin turn on/off during program execution if acc/dec issue.
If threshold is zero - not changes of the pin state.

[cncdrive]

Yes, that is how it works, if the antidive is enabled and threshold set to 0% then the output will be always inactive, because the feedrate can't go below 0%.
If the threshold is 100% then the output will be inactive when the controller can maintain the programmed speed (which is the 100%) and will be active as soon as the feedrate falls below the programmed feedrate, because even 99.9999% is lower than 100%, so anything else than 100% in this case will activate the antidive output.

[shad]

Yes, you right.
In this case we can't use M209/210 commands to activate/deactivate the antidive output from g-code (control AVC state for stand alone THC - just we try to make a trick and use M209/210 for direct control of the antidive output independent from antidive state).
M205/206 - Using these commands makes it impossible to use the moveback on arc lost on holes, corners (where THC is OFF).
M10/M11 - we use this output for fast control of the plasma cutter, for example turn off torch before end of cut.
We still NEED another ONE synchronous with motion command for control output pin from g-code.
Balazs, please try to think about this. This output will control AVC state for stand alone THC.
Thank you!

[shad]

Balazs, can you make a modification for M209/210 and Threshold value?
We need to have this: the antiddive state must to be always active if we set threshold value to zero (independent from difference between Fset and real feedrate). Then we can turn on/off antidive future using M209/210 macros to allow corresponding output pin change state.
It's look like said Rob.
Is it possible?