forum.cncdrive.com

Hi, there is a slight delay maybe about 2 to 3 seconds when my system is doing inital height sensing. What happens is that the torch goes down finds the surface of the material but remains on the material for about 2 seconds before coming back up to pierce height. I only notice this happening with UCCNC there was no delay when I was using Mach3. Is there anything I could check to make the delay shorter. It would sure save some time when doing jobs with lots of pierces. I am using a floating head and sheetcam mp1000 post processor. Thanks

Will try to get a gcode sample
UC100
1.2038 (I think)

Check the delay values setup on the spindle setup page for the M3 and M5.

I see the delay is zero on the spindle setup page.

I re-read your post a few times and if I understand you correctly the delay happens when the surface is touched and not when the torch is turned on, is this correct?
So, if I understand it correctly the delay happens when the surface is touched and before the torch goes up and only after is the M3 torch on command,
so the delay happens when still the surface touching is in progress, correct?
If it is then the delay is in the surface measurement routine. Which macro are you running to measure the surface? What code is in that macro?

Hi Terry,

Yes, it would be good to see at least one sample g-code file.
And if it runs a macro to touch the plate then I should also see the macro file, or if there is no marco call for the touch then a g-code file is enough.

I've just tested the UC100 probing with a simple g-code file with the G31 in the g-code file:

Code: Select all

G0 X0 Y0 Z0
G31 Z-100
G1 X0 F100
G31 Z-100
G1 Z0 F100
G31 Z-100
G1 Z0 F100
M30


This code runs fine without any noticable delays.

So, I will need a sample g-code file...

(G28.1)

N0100 G00 Z0.7500
N0110 X1.2448 Y2.9995
N0120 Z0.1500
N0130 G28.1 Z0.12
N0140 G92 Z0.0
N0150 G00 Z0.0800
N0160 G92 Z0.0
N0170 G00 Z0.1500
N0180 M03

Timed the delay to be around 3sec

OK, I ran your code with some random settings using a UC100 and the G28.1 in your code take around 0.5seconds at me.
The G28.1 is not a fast code though, it is to home the machine, so software has to syncronise a few times with the motion controller.
However the 3sec still sounds like a lot, much more than what I see.

Can you post your .pro profile file to let me test it also using your settings?

And the same time I advice you to use the G31 instead of the G28.1, that code is for probing and it works much faster.