Another plasma component...

Phill, sounds awesome. Looks like I am going to my shed tomorrow.

This is what I had in mind. Include an image file name like this for a given entry in the tool table


This would be very useful.

Just a question. How are you guys implementing external THC enable/disable (eg from sheetcam generated gcode)?

I had a quick look at the plasmac.comp source and it was not immediately apparent. There was a THC enable pin but I assumed it is hooked to the GUI.

Rod

It is a hack I made to plasmac_run.hal. I added an OR2 between the GUI output pin,plasmac_run.thc-enable and the plasmac component pin, plasmac.thc-enable. The signal from the Gcode file is a M62-M65 P.01 controlling motion.digital-out-01 and is connected to the other input of the OR2. I described the function to Phill a while back in this thread. I think this in the example PP I posted as well.

I will fix my configuration to match the Plasmac branch when the external THC enable function is added back in.

John

islander261 wrote: Rod

It is a hack I made to plasmac_run.hal. I added an OR2 between the GUI output pin,plasmac_run.thc-enable and the plasmac component pin, plasmac.thc-enable. The signal from the Gcode file is a M62-M65 P.01 controlling motion.digital-out-01 and is connected to the other input of the OR2. I described the function to Phill a while back in this thread. I think this in the example PP I posted as well.

I will fix my configuration to match the Plasmac branch when the external THC enable function is added back in.

John

John thanks. I really think plasmac should have an external hold pin that is by default connected to one of the motion.digital-output-nn pins so the THC can be placed on hold from gcode. In fact, 2 pins or'ed internally would be better as this would leave one for user extensions. (if only to let me continue experimenting with my kerf crossing component before its eventually folded into plasmac).

By my reading of the docs, it would be enough for the or'ed output of these pins to be simply hooked internally to axis.z.eoffset-enable as last time I looked, plasmac sets this to true and never looks at it again.

Docs: linuxcnc.org/docs/devel/html/motion/exte...-offsets.html#_notes

John, which motion. digital-output-nn pin do you use for gcode hold?

Rod

I am using motion.digital-out-01 for THC enable. I never have the THC hold between cuts so switching the plasmac.thc-enable pin before and after the cut works fine for me. I am not trying to cause a "hold" in the external offsets sense, actually I want to reset all the EO counts when I do this. Previously I tried to use the EO "hold" and ran into a bunch of problems with accumulated corrections causing soft limits problems. Just enabling and disabling EO enable fixed this problem. I am just wanting to control the THC Enable check box from Gcode.

John

THC enable/disable can be done via the new tool table.

Cheers, Phill