RRF3.2 request to enable G43 & G44 Tool height offset

jay_s_uk

@EducatingSavvas don't worry, I won't be going anywhere

EducatingSavvas

@jay_s_uk Can I ask what firmware version you are using. I'm following your workflow but having to make random changes. I'm using RRF 3.2 beta 2.

jay_s_uk

I'm also running 3.2beta3.2

EducatingSavvas

I can confirm I've been able to create macros to set the wasteboard and tool length. My wasteboard setting macro is:

M291 P"Jog spindle until tool tip touches surface of waste board." R"Set Waste Board" S3 X1 Y1 Z1 ; jog to wasteboard
G10 L2 P9 Z{move.axes[2].machinePosition}		; save coordinate to G59.3 WC
G10 L2 P2 Z{move.axes[2].workplaceOffsets[8]} – {move.axes[2].workplaceOffsets[7]}	; Subtract G59.3 from G59.2 and set offset in G55
M400							; wait for last command to end
M500							; store to memory
G55							; swap to G55 WC

and stationary tool length setting macro:

G55				; return to G55 WC
G10 P1 X0 Y0 Z0			; reset axis tool offset
M291 P"Press Ok to peform probe cycle" R"Warning" S3
G30 S-1	K0			; begin probing movement
G91				; incremental movement
G1 F500 Z3			; move up 3mm
G90				; absolute movement
G30 S-1	K0 			; begin probing movement
M400						; wait for current move to finish
G10 L2 P8 Z{move.axes[2].machinePosition}		; store probe ocaiton to G59.2 P8 
G10 L2 P2 Z{move.axes[2].workplaceOffsets[8]} – {move.axes[2].workplaceOffsets[7]}	; Subtract G59.3 from G59.2
M500			; store to memory
G53 G0 Z-10		; move to safe z position

I use G54 to mirror the G53 machine position - so work in G55. I use G59.3 to set the wasteboard, and G59.2 for stationary touch probe. for set Thank @jay_s_uk for pointing me in the right direction.

tom33

@jay_s_uk Hi, thanks for sharing this macro. When you write "G10 L2 Z" which system coordinate will change the G53 ? Because there is no P parameters
Thanks,

jay_s_uk

@tom33 I don't use G53 in my probing macros. I've only used it in the context of tool changing. But, it uses the machine coordinates as a base (so from the machine 0,0 position) and not workplace coordinates

tom33

@jay_s_uk ok so like that there is no a G54/G55 for change the work coordinate system at the begining of a gcode ?

jay_s_uk

@tom33 I believe setting the system in CNC mode (M453) automatically puts the machine in G54

chiefmonkey

Guys this seems to be a great work around for the limitation on variables, as from what I can tell you are using the work offsets of non used coordinate systems to store the values from your probing, and then performing the math on them to get the result you desire.

The only syntax that I am having a hard time following is where do the "move.axes[].machinePosition" and "move.axes[].workplaceOffsets[]" come from. I assume they are calling something at the firmware level, but it seems documentation on this is limited.

I have seen other threads where people are using these meta commands, but finding documentation on them is rather limited. I've gone so far as to dig into linuxCNC as it appears some of this work is derived from there. Any suggestions on where to learn more on the meta command structure would be greatly appreciated.

Phaedrux

@chiefmonkey https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands

Have you seen this? Actual variables are now available as well.

chiefmonkey

@phaedrux said in RRF3.2 request to enable G43 & G44 Tool height offset:

https://duet3d.dozuki.com/Wiki/GCode_Meta_Commands

I have seen that, we are a bunch of mechanical oriented guys in our group, so programming is taking us quite a while, so much different then C that I used to use.