HIya DAVE Read again I said from all my experience and testing in the real world. I also said that it can be FAIRLY realiable IF you load up the Macro code with enough controls but very rarely is THAT method useful as it slows it to a crawl in the real world.

 DOn't THINK I am the only one to see this as a problem I can assure you I'm not.

Bait you up NAW, but I am looking forward to you showing US the proper programming to get it right(;-) You were going to do that correct?

Now that is a proper baiting if I ever did one(;-).

No flaming intended or perceived here, Just an open discussion, you are the Gameboy I am just the old chip slinger.

(;-) TP

HIYA DAVE, I do have a question(;-)

"2) ask that those stating something as a fact to please consider not stating personal experiences as a proven fact. "

IF you do NOT use pesonal experience to "TEST" and "PROVE" an event FIRST HAND under controlled conditions how does one learn to seperate fact from urban legend ?

(;-) TP

get an isMoving in there after that code "F30" in post #23 - that should put the cat amongst the pigeons - sorry

Cheers

Ian

That hasn't been a problem, but I can see how it could blow past the feedrate update without a IsMoving().  I'll add that.  Thanks for pointing that out.

NOw  Don' take what I said WRONG as the Mach CB function is a VERY powerful tool I have macros that write a complete ready to run Gcode  file that is over 900,000 lines long based on input parameters from the operator AND it only takes about 5secs to do so AND then loads that Gcode program into MACH and is ready wating for the OP to press the start button.

(;-) And if we had conditional Gcode we would not be having this conversation as I would never need to USE a macro to do anything seroius with motion code.

But I have learn over the years and with PRIOR experiences to NOT trust CB with Motion code.

Your Mileage May vary based on actual conditions at time of use, (;-) TP

This sounds kind of like my problem
http://www.machsupport.com/forum/index.php?topic=2965.0
"Here is the real problem ,if I Ref'd Z 0.0 say 1" to 8 " off of the plate the Z Axis starts to  move down trying to find the switch or 8 " and it does ,then once the switch closes the Z Axis takes forever to come to a stop(say about 1") ,"

HIYA DAVE, Could you post your version of the macro used? Maybe we can find something to help your situation.

(;-) TP

I will not be able to post it untill monday. But I will also post a video of what the machine is doing.

Thanks
Dave

This sounds kind of like my problem
http://www.machsupport.com/forum/index.php?topic=2965.0
"Here is the real problem ,if I Ref'd Z 0.0 say 1" to 8 " off of the plate the Z Axis starts to  move down trying to find the switch or 8 " and it does ,then once the switch closes the Z Axis takes forever to come to a stop(say about 1") ,"

What's your X and Y acceleration set at?  G31 uses that, not the axis that the G31 is using.  If you have a slow accel and a high probe feedrate, it WILL take forever to stop.

HIYA DAVE, That is not a problem. Get it when you can so we can maybe help you get this thing to work properly. Plasma cutting is a really FUN process to create metal art and such.

It does not matter who may be right or wrong or not as long as we get you cutting like it should.

(;-) TP

What's your X and Y acceleration set at?  G31 uses that, not the axis that the G31 is using.  If you have a slow accel and a high probe feedrate, it WILL take forever to stop.

If that's the case, it's a serious bug that needs to be reported to Brian.