Inconsistent values from Versaprobe

More
17 Oct 2024 18:05 #312420 by gardenweazel
I'm using QTDragon HD and having issues when probing.

I am using the steps as outlined in the qt_auto_probe_tool.ngc file start off with.

From machine_log.dat (VIM line numbers precede each line)

 17 17:11:22 Loaded tool 0
  18 17:11:22 Tool 0: PROBE
  19 17:11:28 Cannot switch pages while in AUTO mode
  20 17:11:39 Versa Probe: Start Cycle: Go to Tool Setter
  21 17:12:08 Versa Probe: Start Cycle: Probe Tool Setter Z Height
  22 17:12:17 HISTORY Tool Setter height Z[-148.426]
  23 17:13:17 Versa Probe: Start Cycle: Probe Z Height of material
  24 17:13:27 HISTORY Probe Material Top Z[-115.031]
  25 17:14:47 Cannot switch pages while in AUTO mode
  26 17:14:52 Versa Probe: Start Cycle: Probe Outside Edges, Finish At Corner
  27 17:15:17 HISTORY Outside XPYP  Xp[0.302] Lx[0.000] Yp[0.027] Ly[0.000]
  28 17:15:56 Started program from line 1
  29 17:17:30 Tool 16: whiteside router bits - whiteside rd210
  30 17:17:47 Tool 16: whiteside router bits - whiteside rd210
  31 17:17:47  Probe Height: -148.4200
  32 17:17:47 Run timer stopped at 00:01:50
  33 17:17:47 Loaded file /home/andy/uploads/Large-Serving-Tray-REVISED-V2-POCKET-2.ngc
  34 17:17:47  Block Height: -115.0300
  35 17:17:47  Probe Result: 229.0947
  36 17:17:47  Calculated Offset: 262.4847
  37 17:17:47 Linear move on line 231 would exceed Z's positive limit
  38 17:17:47 Linear move on line 231 would exceed joint 3's positive limit
  39 17:17:47 invalid params in linear command
  40 17:17:47 Abort Parameter is [3]
  41 17:17:55 Started program from line 1
  42 17:18:17 Tool 16: whiteside router bits - whiteside rd210
  43 17:18:17  Probe Height: -148.4200
  44 17:18:17  Block Height: -115.0300
  45 17:18:17  Probe Result: 229.0912
  46 17:18:17  Calculated Offset: 262.4812
  47 17:43:20 Run timer stopped at 00:25:24

Here's the popup message:  NOTE the MDI line number 231 has no Z axis movement and the program file has not even started to execute. At this point the new tool change has already taken place and the new tool is being measured.

 

Not sure what is causing this but, after I "Clear all" the and restart the file from the beginning it runs as expected without the error.

Finally, worth noting is that I noticed my tool table appears to have been altered and is NOT from previous runs. Has many missing columns.
It appears as if something has written to the tool table when it should have not.
Here's a couple of lines in my current tool table that reflects this issue, note that tool 16 has the Z set.

T15  P15  D+6.350000 ;whiteside router bits - whiteside ru210
T16  P16  D+6.350000 Z+258.012190 ;whiteside router bits - whiteside rd210
T17  P17  D+6.350000 ;whiteside router bits - whiteside rd207

And here is a backup that I took a week or so ago:

T15 P15 X0 Y0 Z0 A0 B0 C0 U0 V0 W0 D6.35000 I0 J0 Q0 ;whiteside router bits - whiteside ru2100 -- 1/4 inch upcut spiral- solid carbide 
T16 P16 X0 Y0 Z0 A0 B0 C0 U0 V0 W0 D6.35000 I0 J0 Q0 ;whiteside router bits - whiteside rd2100 -- 1/4 inch downcut spiral- solid carbide 
T17 P17 X0 Y0 Z0 A0 B0 C0 U0 V0 W0 D6.35000 I0 J0 Q0 ;whiteside router bits - whiteside rd2074a --o-flute 1/4 inch downcut spiral - solid carbide 

Any ideas?

 
Attachments:

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

More
18 Oct 2024 00:55 #312454 by gardenweazel
So, the call to save the tool offset is in the qt_auto_probe_tool.ngc on or around line 202-203 seems to be mangling the tool.tbl format.

203 G10 L1 P#<tool> Z[#<calculated_offset>]

Which occurs after the OKAY click of the tool change prompt. I've checked it before and after.
The following user(s) said Thank You: tommylight

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

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