Configuring Plasmac - a complete THC/plasma config for any hardware

opps yeah you are right that was indeed a silly mistake but correcting it doesnt chnage anything
at last i have to comment out my arc ok and torch-on pins and finally it runs
but as soon i uncomment them it says pins 8 out not found or 11 i not found

For the torch on you have lower case O instead of zero

Hi,
I just got my plasma table changed over to PlasmaC on Debian Stretch. Thanks for all the efforts in this! Yesterday I did a successful cut with it. Now today I had trouble with the touchoff. It would come down (ohmic probe) touch steel and trigger ohmic probe, but continue down till I got error " bottom limit reached while probing down. Then when I shut down Linuxcnc I get the following error. Last night I tried adding my custom PYVCP panel to axis (probably not a good choice because it didn't work). Does this have anything to do with my problem? What is the best way to add my own custom buttons to Plasmac?

Last night I tried adding my custom PYVCP panel to axis (probably not a good choice because it didn't work). Does this have anything to do with my problem? What is the best way to add my own custom buttons to Plasmac?

Can you post your ini file?
How many extra buttons do you need?

I need four extra buttons, I have my downdraft table divided into 4 sections. I need them to control the zone valves. Sometime I would like to have it control them automatically with the location of the cutting torch. I attached my ini and also a second error report. Thanks, EW

Like this?



This is actually using custom component that divides the table into 2 zones, but you can use the Lincurve component to create the zones along the Y axis position and trigger a switch accordingly.

A quick test seems to show that you cannot mix GladeVCP and PyVCP in Axis, that would probably be the reason for your errors.

You could create a GladeVCP panel for Axis but you wouldn't be able to use Axis with the run panel on the right hand side, you would have to have the run panel as a tab behind the preview.

The other option would be Gmoccapy with a GladeVCP panel on the right hand side.

Gmoccapy also has the option of Macros

I didn't see a reference to a PyVCP panel in your ini file

I just noticed in your ini file that you have:That file is normally created by LIB:basic_sim.tcl to show what HAL commands were created for the sim config.
It should be commented out in a working config.

I didn't see a reference to a PyVCP panel in your ini file

I removed the PyVCP from the INI and still get the errors.

I just noticed in your ini file that you have:
HALFILE = ./imperial_plasmac_cmds.hal

I have my hal commands spread between that file and my original hal file. Should I combine it to one single hal file?
Do I have all the commands I need, or which commands don't I need with Plasmac? Do I need the PID Commands on all the axis with a stepper system?

rodw

This is actually using custom component that divides the table into 2 zones, but you can use the Lincurve component to create the zones along the Y axis position and trigger a switch accordingly.

Looks Good.
On my table I have very similar setup, but I have the table divided into quarters. 2 X sections and 2 Y sections. I'm not sure that I fully understand the Lincurve component yet. Would that work with the four sections? E.W.