Inconsistent values from Versaprobe

  • gardenweazel
  • gardenweazel's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
22 Nov 2024 19:42 #315046 by gardenweazel
Replied by gardenweazel on topic Inconsistent values from Versaprobe
I believe that I see what is going on.

There is a variable named MAXPROBE that is called from the INI as follows:  #<_ini[VERSA_TOOLSETTER]MAXPROBE>
There is also a variable that is read from the versaprobe screen saved in the qtdragon_hd.pref file as follows:  ps_probe_max_z_travel
The variable is also know as max_z_travel is some of the functions.
It appears as if both VARS are used for the same purpose. If I'm not mistaken the documentation indicates that the values are to be set and used in the INI file under VERSA_TOOLSETTER (brackets omitted).

I somewhat ignored the values in the qtdragon_hd.pref file which when I compared were NOT the same values. I know for a fact that my Z will travel more that 115mm which is what it was set at in the pref file. However, in my INI file I have set the value of 150mm which covers the length of all my tools.

Additionally I found a typo which I submitted a pull request a few hours ago.

I'll test this shortly and respond appropriately.

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

  • gardenweazel
  • gardenweazel's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
22 Nov 2024 22:40 #315067 by gardenweazel
Replied by gardenweazel on topic Inconsistent values from Versaprobe
These changes didn't help but, what does work is clicking on the "Measure/Probe Current Tool" button.

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

  • gardenweazel
  • gardenweazel's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
22 Nov 2024 23:32 #315069 by gardenweazel
Replied by gardenweazel on topic Inconsistent values from Versaprobe
I am attaching two DEBUG files. The first is a FAILURE and the second SUCCEEDED. Looks as if the G43 is the difference. The failure is G43 Offset zero and then it succeeds with the G43 Offset of one(1) after I click start for the second time; 

FAILURE
 

File Attachment:

File Name: machine_lo...LURE.txt
File Size:3 KB


SUCCEEDS
 

File Attachment:

File Name: machine_lo...EEDS.txt
File Size:2 KB
Attachments:

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

More
23 Nov 2024 05:19 - 23 Nov 2024 05:30 #315082 by Aciera
Replied by Aciera on topic Inconsistent values from Versaprobe
Interesting. There is also a discrepancy between 'Selected' tool and 'Loaded' tool.

Fail:

17:06:22 Started program from line 1
17:06:27 Current Comp Mode: 400.000000
17:06:27 Current Coord System: 540.000000
17:06:27 G43 Tool Offset: 0.000000
17:06:27 Current Selected Tool: 42.000000
17:06:27 Current Selected Pocket: 42.000000
17:06:28 Current Tool Loaded: 99.000000
17:06:28 Current Tool Index: 99.000000

Success:

17:12:17 Started program from line 1
17:12:23 Current Comp Mode: 400.000000
17:12:23 Current Coord System: 540.000000
17:12:23 G43 Tool Offset: 1.000000
17:12:23 Current Selected Tool: 42.000000
17:12:23 Current Selected Pocket: 42.000000
17:12:23 Current Tool Loaded: 42.000000
17:12:24 Current Tool Index: 42.000000
Last edit: 23 Nov 2024 05:30 by Aciera.
The following user(s) said Thank You: gardenweazel

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

  • gardenweazel
  • gardenweazel's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
23 Nov 2024 05:53 #315085 by gardenweazel
Replied by gardenweazel on topic Inconsistent values from Versaprobe
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
23 Nov 2024 10:06 - 23 Nov 2024 10:16 #315092 by Aciera
Replied by Aciera on topic Inconsistent values from Versaprobe
[edit]
Ah ok, you are changing from the probe to T42 when the routine fails.
Last edit: 23 Nov 2024 10:16 by Aciera.
The following user(s) said Thank You: gardenweazel

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

  • gardenweazel
  • gardenweazel's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
23 Nov 2024 15:08 #315110 by gardenweazel
Replied by gardenweazel on topic Inconsistent values from Versaprobe
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
23 Nov 2024 16:33 - 23 Nov 2024 16:35 #315118 by Aciera
Replied by Aciera on topic Inconsistent values from Versaprobe
So I had some time to actually look at this:
; -------------------------------------
; --- 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: 23 Nov 2024 16:35 by Aciera.
The following user(s) said Thank You: gardenweazel

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

  • gardenweazel
  • gardenweazel's Avatar Topic Author
  • Offline
  • Elite Member
  • Elite Member
More
23 Nov 2024 16:56 #315121 by gardenweazel
Replied by gardenweazel on topic Inconsistent values from Versaprobe
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
23 Nov 2024 18:08 #315127 by Aciera
Replied by Aciera on topic Inconsistent values from Versaprobe
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.284 seconds
Powered by Kunena Forum