Strange behaviour in G1 movement
deckingman last edited by
@zesty_lykle That's really weird. So when an S1 parameter is used, the firmware is looking for a change of state of the end stop switch. But I've been through the complete list of G and M codes and can't see anything anywhere that might define a different speed when and S1 parameter is used.
Can you post your config.g and I'll compare it with my CoreXY config to see if anything leaps out at me.
Please post your config.g file.
deckingman last edited by
Here is a long shot. I see you use mesh grid bed compensation. Also, your Z speed and accelerations are low (not saying there is anything wrong with that, just making an observation). So I'm wondering is G1 XY moves are slow because the mesh compensation is active and it's having to wait for the Z axis. Then maybe when the S1 parameter is present, it's classed as a homing move so any mesh bed compensation is not being acted on.
As I said, just a long shot - I don't use any form of flatness or level compensation so it might aslos explain why I can't replicate the behaviour on my machine.
Since I don't have any of that connected yet, not even the Z stepper, I think I will comment it all out and reduce the config file to the absolute minimum.
No, didn't make any difference.
It is consistent. Everything I try doesn't make any difference.
JoergS5 last edited by JoergS5
@zesty_lykle Your M208 is a bit strange, as in the G-Code example
M208 X200 Y200 Z90 ; set axis maxima
M208 X-5 Y0 Z0 S1 ; set axis minima
of https://reprap.org/wiki/G-code#M208:_Set_axis_max_travel the values are different.
In your config you write S0 as minima and S1 as maxima as comment:
; Axis Limits
M208 X150 Y150 Z0 S0 ; Set axis minima
M208 X-150 Y-150 Z300 S1 ; Set axis maxima
but it's other round in the RepRap documentation.
Maybe the Z direction is wrong (M574 Z1 endstop at low end, so at 300?) And your behavior comes from the fact that the z-homing isn't done or something.
Man I could kiss you!
Yep, that solved it.
I can now move everywhere at speed with no S parameter.
It still feels odd to define Z300 as minima and Z0 as maxima but it does the trick.
OK now I can continue with the real tests. Thank you again.
@zesty_lykle Z300 should be maxima and Z0 minima, why do you need to define it the other way around? Possibly your Z axis is moving in the wrong direction?
Nah, it is just that because I have 0,0 set in the center, and not left front, it comes out a bit strange, but it works nicely.
To pick up a tool, in the toolchange macro, I have to go outside the print boundaries. Now I do that with a relative statement with the S parameter set. It works, but is there a different way to do it?