Probe screen V2 with Gmoccapy T/M6 causes system to pause - Solved+Corrections

More
04 Jan 2022 08:53 #230733 by Eyecon
After some editing of the subroutines, I managed to get Probe screen v2 (github.com/verser-git/probe_screen_v2) to work with Gmocappy however when I try to do a tool change/M6 from MDI or in auto mode, linuxcnc just "pauses" as if waiting on some pins to fire. I tested the tool change signal for the probe module created by the gladevcp handler and it works correctly, all my iocontrol tool change pins are netted correctly as far as I can tell. Does anyone have recent experience with this?

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

More
05 Jan 2022 13:44 - 05 Jan 2022 14:09 #230864 by Eyecon
In case anyone is interested, I managed to get it to work after moving the iocontrol tool prepared loopback signal to load with the gladevcp module rather than in the postgui Hal.

However I discovered that the gcode logic for tool remaping doesn't make sense(I could be wrong):
- The code uses the following to setup tool offset upon tool change:
G10 L1 P#<tool> Z[#<touch_result> - #<_hal[probe.probeheight]> + #<_hal[probe.blockheight]>]
The probeheight and blockheight(both are pins setup by the gladevcp panel) are measured relative to machine zero using other macros. Instructions say to measure the tool setter(probeheight) height first then the workpiece height(blockheight). Incidentally, measuring either one using the provided macros also sets your Z zero point of the current WCS to that height (i.e. your WCS Z zero becomes the top of the workpiece if you follow the provided instructions, also not sure why you'd do that)

-Continuing with the provided  instructions, a T*** M6 in the g-code would trigger the system to measure the currently loaded tool against the tool setter. Based on the code above, the current tool offset would be updated to be  difference between the original reference probe/tool and the currently loaded/measured tool + the height of your workpiece!! This is obviously wrong.

-There is a commented line in the same macro file that would set  the currently selected work coordinate system(P0) Z to your original workpiece Z height + the difference between reference and current tool. This could work provided your WCS Z is always set to be the top of the workpiece..fair assumption for mills with a vice I guess??  I think is the more elegant solution would be to just set the offset of the current tool as follows:
  G10 L1 P#<tool> Z[#<touch_result> - #<_hal[probe.probeheight]>]
This is especially useful with the fusion360 EMC post which by default adds a G43 H0 after an T***M6. If you are like me(manual tool changes, no ATC) and have all the tool offsets setup to zero in the Fusion360 tool library, the G43 H0 does nothing. 
If I misunderstood the logic or misinterpreted the instructions, I'm happy yo be corrected. Hope this helps
Last edit: 05 Jan 2022 14:09 by Eyecon.

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

Time to create page: 0.070 seconds
Powered by Kunena Forum