New day new problem

Hello

I still do not have the Ohmic sensor working, however that is not where the frustration is at this point.I power up the table home all axis, pick a material from the list load a simple G-code, and the Z axis drives into the top limit switch. No matter what I do, run it to the bottom of travel zero the DRO out, and it drives to top limit. If I click on the probe button it drives down very near the lower limit, stop and drive back up to near the top limit, which I assume is near as it should operate. I have a floating head switch which show in Hal Show as working, but tripping it does no effect the probe check action.I have finger boned in the G38 command with a distance of 1.75” it drives down that distance and returns up fine. But the floating head switch has not effect on its travel, but does get an error about the switch being pushed. I have downloaded the material list from this site for a Hypertherm 45 and have used it in my testing. I have loaded in the wrench .NCG code and tried to run it. Same thing drives to the Z limit.I will attach the TAZ file for a look as to what is happening.I have scratch built 9 tables using different control electronics and software doing my own research. Even the first table as a beginner to the world of CNC Plasma did not cause as much frustration as Linuxcnc. Please do not get me wrong you all have been a great help getting me this for, and I do say thank you for that. I am beginning to think QTPlasmaC is a bridge to far, and too new that not many if any are using it for plasma successfully.
Again Thank you very much.
Tom
 

thanks for your reply and suggestion how do I remove the Ohmic section from the INI and Hal. I have a working float switch and have used them in the past, it would make me very happy to get it operational and not look back. I had placed the switch offset in the place for it value. but at this point I cannot get past the Z moving up at the start. If you have a functioning set of files I can copy maybe that would help, even just to see it work properly.
Putting the data to work with my table is not hard, but getting it past the Z problem must be done first.

Tom, sorry its been such a drama.
I've finally got QTplasmac up and running here at home where I have a 7i76e attached (minus any motors and limits). Between now and the weekend, I'll try and load up your config and see what is going on.
I've really been under the pump recently.

The recommendation to get plasmac up and running was to first build a simple XYZ machine that has all the motion homing and limits sorted out before installing qtplasmac. I think you may have jumped in boots and all so its been a bigger task.

I have done that one step at a time as I said, I think my Z problem is from a Macro attached to the cycle start button. I can do many things like homing and moving the table motors, making small G-code movements as single line operations. Load the material list and select one to be used, load a cut routine no problems . But as soon as I click on the cycle start, Z moves up to the limit it make no other movement as moving to the location of the first cut operation.  Normally for a cut operation I see the table move to the location of the first pierce then start to move the Z axis.  I can clear that and move around fine.  The Docs say all Z movements are controlled by QTPlasmaC not the G-code in the routines loaded by the operator. 

So when you run a gcode program Z moves up but when you press the probe test button Z moves down, is that correct?
If so it is very odd as it is the same code used for both.
Do the jog buttons on the GUI move the Z axis correctly?
I have no idea what g38 commands would do, they should not be used in QtPlasmaC/Plasmac, as the probing is controlled internally.
Can you post a sample of the gcode that you are running.

All movements seem as the should, probe test moves down for about 2" stops and moves back up about the same, no errors shown.  the jog buttons work fine and in the directions indicated.  I can do small G-codes like move X 10" and vary the speed, they move angin in the directions indicated by a + or - in the g-code line. Here are 2 for the same DXF different Post Processor as indicated on the top lines.  The G38 is a probe command to find the metal surface, but as you say QTPlasmaC controls that.
 

G38.n axes
G38.2 - probe toward workpiece, stop on contact, signal error if failure

G38.3 - probe toward workpiece, stop on contact

G38.4 - probe away from workpiece, stop on loss of contact, signal error if failure

G38.5 - probe away from workpiece, stop on loss of contact

From the G-code manual

Boy you can make a guy feel bad

acourtjester wrote:

G38.n axes
G38.2 - probe toward workpiece, stop on contact, signal error if failure

G38.3 - probe toward workpiece, stop on contact

G38.4 - probe away from workpiece, stop on loss of contact, signal error if failure

G38.5 - probe away from workpiece, stop on loss of contact

From the G-code manual
 

Tom, QTPlasmac does not use conventional probing. It is all done internally on an M3.

I got your config opening  here with my Linuxcnc and a 7i76e. Its close  to midnight here, So I will look at it over the next few days and wire in some pins to match your config.