Inconsistent values from Versaprobe

More
1 year 10 months ago #317045 by zieluch
I am running into similar problem but maybe I found root cause. Need to do some more testing but please check below and share the result.

Can you please do the following:
  • M6 overwrite routine macro - On the tool change remove all the G43 command except one at the end after tool measurement., in my case it was m6 g43 on semi manual change
  • start linuxcnc
  • go to tool table and set in column Z =0 for probe and two random tools which you later test on example T1 and T2.
  • load probe m6 t99
  • go to object and measure it.
  • change to t1: m6 t1 with tool measurement
  • check if offset is correct if so try another tool t2
  • if T2 is ok now check other tools (one which has Z <>0 value in the tool table)
I have rack change for tools 1-5 and rest I am changing manually in the position. And I notice that the tools changed manually i was lading with M6 G43 in the tool_change macro. This causes error as I was changing G54 Z offset after loading tool. I need to make more test .

cheers
Michal

Please Log in to join the conversation.

More
1 year 10 months ago #317047 by gardenweazel
I'll test this later this afternoon.

Thank you so kindly for assisting.

Please Log in to join the conversation.

More
1 year 10 months ago #317118 by gardenweazel
I'm sorry but this does not work for me as described.

Few have chimed in(thanks for those that have), does anyone have VersaProbe working as expected?

Please Log in to join the conversation.

More
1 year 10 months ago #317137 by zieluch
Can you share your ini file and tool change macro ? 

 

Please Log in to join the conversation.

More
1 year 10 months ago #317211 by gardenweazel
Sure.
The attached qt_auto_probe_tool.ngc file has been altered however, I can use the same file that comes with the master
and there are no differences in the outcome.

In the ini file the reference to this line was added by me per another thread here .
# This is the MAX Z travel to my spindle chuck without a tool.
Z_REF = -183.97

Of particular interest, is that after I add my probe tool Z offset, it gets removed somewhere during the procedure.
It was:  T99  P99  D+2.000000 Z0 ;3D Probe
It's now:  T99  P99  D+2.000000 ;3D Probe

Thanks for your help, can you share your probe NGC file?
 

Please Log in to join the conversation.

More
1 year 10 months ago #317220 by MaHa
Can you try to replace this 2 lines from
Code:
#<zworkoffset> = [#5063 + #[5203 + #5220 * 20] + #5213 * #5210] #<tool_length> = [#<zworkoffset> - #<_ini[VERSA_TOOLSETTER]Z_REF>]

to
Code:
#<zworkoffset> = [#5063 + #[5203 + [#5220 * 20]]] #<tool_length> = ABS[ABS[#<_ini[VERSA_TOOLSETTER]Z_REF>] - #<zworkoffset>]

Please Log in to join the conversation.

More
1 year 10 months ago #317236 by MaHa
I just realized, there is something missing. You need to know the distance from   #<_ini[VERSA_TOOLSETTER]Z_REF>  (-183.97) to table surface. This must be added to toollength. Then you can work with table as base.
I think the toollength probing result you get now, is wrong by exactly this value.

Please Log in to join the conversation.

More
1 year 10 months ago #317237 by gardenweazel
I will measure this from Z0 to table top but, what's the VAR that I add it to?

Please Log in to join the conversation.

More
1 year 10 months ago #317238 by MaHa
In the ini, under Versaprobe there is Diameter. Maybe you can add below HEIGHT = nnn and use it as #<_ini[VERSA_TOOLSETTER]HEIGHT>
It could look like this:
Code:
#<tool_length> = ABS[ABS[#<_ini[VERSA_TOOLSETTER]Z_REF>] - #<zworkoffset> + #<_ini[VERSA_TOOLSETTER]HEIGHT>]

Please Log in to join the conversation.

More
1 year 10 months ago #317254 by gardenweazel
I tried what you recommended, this time after the back-off touch, nothing happened and the spindle just sat there with no movement. Although no error.

For some crazy reason I also lost control of my WHB04B-4 MPG. Incredibly annoying!

As an FYI in versaprobe routine there is a BLOCKHEIGHT and PROBEHEIGHT which is what I suspect that you're eluding to here.

I'd like t o hear from ANYONE who's is successfully using VersaProbe successfully using the master.

Realistically, I simply want an error free manual tool change with minimal error margins.

Thanks @MaHa!

Please Log in to join the conversation.

Time to create page: 0.119 seconds
Powered by Kunena Forum