Plasma Breakaway signal

[electroklas]

Noticed (in brookwood i2C A/D manual) the IOsender THC Monitor tab having an indication for a breakaway signal.
I cant find any references to this in any documentation (or in the github repos except for a isolated struct statement)
Is this implemented?
What input signal would i use for that?
(iMXRT1062 based board, ie T41U5XBB)

[terjeio]

Is this implemented?

No.

What input signal would i use for that?

The safety door input could be hijacked, or even the full door functionality used as-is?

[electroklas]

Next questions along the same line...
Is 'Spindle enable' correct signal to control the 'Plasma Arc On' ?

Is the ArkOK signal implemented? (also indicated by the THC MonitorTab)

And lastly, is the Probe signal correct signal for floating head trigg (height probing function before pierce)

(I haven't found any specific documentation of how to use grblHAL for plasma usage, is there anything written about it?)

[terjeio]

Is 'Spindle enable' correct signal to control the 'Plasma Arc On' ?

Yes.

Is the ArkOK signal implemented? (also indicated by the THC MonitorTab)

Yes, but it will not be shown in the THC monitor before arc on. If you want to check the input before that you can use the $pinstate command.

And lastly, is the Probe signal correct signal for floating head trigg (height probing function before pierce)

Yes. Should the plasma plugin perform a probe automatically (configurable) on arc on?

(I haven't found any specific documentation of how to use grblHAL for plasma usage, is there anything written about it?)

No, at least not yet. I have used the LinuxCNC documentation as a reference.

Note that there is code to enter tool change mode if the arc ok signal is lost, the idea behind this is that jogging to is then possible and that could be used to reposition before restarting the job. Currently this is not working at all an will cause issues. The code should be changed to initiate a feed hold instead:

static void pause_on_error (void)
{
    stateHandler = state_idle;
    system_set_exec_state_flag(EXEC_FEED_HOLD);   // Set up program pause for manual tool change
//    system_set_exec_state_flag(EXEC_TOOL_CHANGE);   // Set up program pause for manual tool change
    protocol_execute_realtime();                    // Execute...
}

Obvoiusly this requires more work, do you have any input on how to handle this?

[electroklas]

And lastly, is the Probe signal correct signal for floating head trigg (height probing function before pierce)

Yes. Should the plasma plugin perform a probe automatically (configurable) on arc on?

Still trying to figure out the workings and responsibilities of all system parts.... but in the GRBL setup I ran before starting the upgrade, the probing was initiated and controlled by settings in the Fusion 360 Cam/Postprocessor... I was using the OpenBuilds Post for Plasma... So I guess that's a No... (No automatic, at least not with that toolchain).

About ToolChange... I'm to inexperienced with this all to really have a clue...

Will a manual commanded FeedHold turn the arc off? (And reinitiated at cycle start/resume)

(Still in the planning phase of the wiring, so nothing running yet)

[terjeio]

About ToolChange... I'm to inexperienced with this all to really have a clue...

The thing about toolchange mode is that it suspends the gcode stream and allows jogging. So it could somehow be used to restart a job.

Will a manual commanded FeedHold turn the arc off? (And reinitiated at cycle start/resume)

It is an option if laser mode is enabled. Not sure if it will work though. Laser mode should be ok to enable since you do not want the arc to be on during rapids anyway. $63 in General settings:

Code can be hooked into events like feed hold/resume from feed hold if needed, I only need specifications for what to do. I can even attach G65 style macros to events if that is desirable.