Can the XY travel speed between G30 test points be changed?

Luke'sLaboratory

You can edit your bed.g to have travel moves at arbitrary speed (G0 Xnnn Ynnn F3000000000000000000000000000000000) between probe points and then the "normal" probe command.

fcwilt

@luke-slaboratory said in Can the XY travel speed between G30 test points be changed?:

You can edit your bed.g to have travel moves at arbitrary speed (G0 Xnnn Ynnn F3000000000000000000000000000000000) between probe points and then the "normal" probe command.

I don't see where G30 accepts a F parameter.

The M558 command has a T parameter which is the travel speed between probe points.

Frederick

Luke'sLaboratory

@fcwilt From my bed.g - Travel moves before the actual probing - speeds it up nicely

G1 X5 Y600 F120000
G30 P0 X5 Y600 Z-99999

G1 X587 Y600 F120000
G30 P1 X587 Y600 Z-99999

G1 X300 Y10 F120000
G30 P2 X300 Y10 Z-99999 S3

fcwilt

@luke-slaboratory said in Can the XY travel speed between G30 test points be changed?:

@fcwilt From my bed.g - Travel moves before the actual probing - speeds it up nicely
G1 X5 Y600 F120000
G30 P0 X5 Y600 Z-99999

G1 X587 Y600 F120000
G30 P1 X587 Y600 Z-99999

G1 X300 Y10 F120000
G30 P2 X300 Y10 Z-99999 S3

So the T parameter of M558 doesn't work for you?

Frederick

kb58

@luke-slaboratory Ah, okay, I see what you did. While I'm sure that it works, it sort of "cheats" in that it requires what sw engineers call "magic numbers." That is, if you ever redefine your probe points, you have to remember to also change a second set of number, potentially located somewhere else.

fcwilt

@kb58 said in Can the XY travel speed between G30 test points be changed?:

@luke-slaboratory Ah, okay, I see what you did. While I'm sure that it works, it sort of "cheats" in that it requires what sw engineers call "magic numbers." That is, if you ever redefine your prop points, you have to remember that you have a second set of number somewhere else.

The M558 T parameter should do they job. If it's not something is not working as intended.

Frederick

kb58

@fcwilt Yes, M558 is perfect since it's already there and had set travel speed to 6000mm/min. Upped it to 10000, which sounds huge but since it's per minute, it's not too bad. Will see what the printer thinks, though!

Luke'sLaboratory

@fcwilt

I'm pretty sure this is the original reason I split it out into moves then probes - RRF3+SBC has been rough with growing pains, and I prefer explicit commands to implicit.

@kb58
I wrote these before variables. If I were to write them today - I would write them as variables and just have one definition for all points, like I do my toolchanging macros.

fcwilt

@luke-slaboratory said in Can the XY travel speed between G30 test points be changed?:

@fcwilt

I'm pretty sure this is the original reason I split it out into moves then probes - RRF3+SBC has been rough, and I prefer explicit commands to implicit.

Well using the SBC and all bets are off. It lags behind RRF "SD mode".

I'll have to test the T parameter on my SBC setup. If it works there is no reason to not use it.

Frederick

mikeabuilder

@kb58 said in Can the XY travel speed between G30 test points be changed?:

Ah, okay, I see what you did. While I'm sure that it works, it sort of "cheats" in that it requires what sw engineers call "magic numbers." That is, if you ever redefine your probe points, you have to remember to also change a second set of number, potentially located somewhere else.

Why not set variables for the test points, then reference them in the G30 commands? Meets the goal of not having to hard code those numbers in twice.