Inconsistent values from Versaprobe

More
1 year 11 months ago #315085 by gardenweazel
99 is my probe. 42 another tool that I am switching to. The probe is still in the collet at that point. My code has the tool change at the beginning of the task. So I would think that is correct.

Please Log in or Create an account to join the conversation.

More
1 year 11 months ago - 1 year 11 months ago #315092 by Aciera
[edit]
Ah ok, you are changing from the probe to T42 when the routine fails.
Last edit: 1 year 11 months ago by Aciera.
The following user(s) said Thank You: gardenweazel

Please Log in or Create an account to join the conversation.

More
1 year 11 months ago #315110 by gardenweazel
Yes, correct. 
Would adding a G43 to this make a difference? 
RS274NGC_STARTUP_CODE = G17 G21 G40 G80 G90 G94 G54 G97 G64 P0.025 S5000

Please Log in or Create an account to join the conversation.

More
1 year 11 months ago - 1 year 11 months ago #315118 by Aciera
So I had some time to actually look at this:
Code:
; ------------------------------------- ; --- Begin Initial data gathering ---- ; ------------------------------------- ; --ANDY #<tool> = #<selected_tool> ; --ANDY #<pocket> = #<selected_pocket> #<tool> = #<_selected_tool> #<pocket> = #<_selected_pocket> #<local_start_x> = #<_x> #<local_start_y> = #<_y> #<local_start_z> = #<_z>

#<_x>, #<_y>, #<_z> are relative positional values so your start position depends on whether you have g43 tool offset active or not.
The routine is set up to always return to the start position with G43 active so if your start position was stored in G49 then your spindle will always have to travel further up by the measured tool offset then where it started. This is why you are getting limit violation errors.

Just calling G43 is not the right way to go about it. If you have no tool set then the offset will just be zero and you'll be no better off.
Basically you need to start out by setting up your probe length in the tool table (ie Z offset for tool #99) and then do 'T99 M6 G43'  or, if your probe length has to be measured after each startup, you may want to use 'G43.1 H...'
linuxcnc.org/docs/html/gcode/g-code.html#gcode:g43

So really the same the others have already pointed out but it has taken me a long time to catch on. :)
Last edit: 1 year 11 months ago by Aciera.
The following user(s) said Thank You: gardenweazel

Please Log in or Create an account to join the conversation.

More
1 year 11 months ago #315121 by gardenweazel
Thanks for your help, I really appreciate it!

In the qt_auto_probe_tool.ngc script, I read the following:

The following workflow assumes using both a XYZ probe and a Z Toolsetter:
1 - Initial Setup: Before beginning the program, setup the Probe Tool as
having a zero z-offset in the tool table. (Non-zero tool lengths
for the probe tool can be made to work, but have multiple extra
steps required, and it is easy to have the tool offset interfere with
the remap coding and cause incorrect adjustments to your offsets.
This procedure assumes a zero length.)


It sounds as if the script documentation may be incorrect or perhaps previous codes changes have impacted the script?

Do you mean "G43 H99" ?? 
"G43.1" doesn't have an H parameter according to the online docs.

Please Log in or Create an account to join the conversation.

More
1 year 11 months ago #315127 by Aciera
Well, I just read the notes in the routine and it seems that the recommended setup is quite different from what I suggested. So you'll probably want to follow the text in the ngc file.
I don't really know as I have never used it. But it certainly would not make sense to use 'T99 M6 G43' as I suggested as that would of course trigger the remapped routine.
The following user(s) said Thank You: gardenweazel

Please Log in or Create an account to join the conversation.

Moderators: cmorley
Time to create page: 0.391 seconds
Powered by Kunena Forum