When the machine homes with the new cartographer, the z axis speed is very nice. Maybe it uses the max speed of the printer as per the printer.cfg, not sure because I cannot find any speed mentioned in the config.
But when I do a QGL this z axis speed drops considerably and is annoyingly slow. The whole point of the cartographer is to speed things up but I simply cannot find any entry in the config that relates to this speed. I am not brave enough to simply add some line of code with some speed in the QGL section, but maybe I should? If so, what should this line of code look like?
Also, if this speed is missing, what does the machine use for z axis speed in this case?
Thanks.
I realise the speed needs to remain within reason for the scanner to perform an accurate detect while getting closer to the bed. But my point is that if the original homing moves that come with the scanner itself are faster then the QGL speed, it stands to reason that the QGL speeds can be the same without stretching the scanner’s capability.
Strange thing is that in neither section I can find any reference to any z axis speed during probing. So where is this determined?
Not sure, as I do not use the Cartographer. Usually the [probe] / [probe_eddy_current] section is leading here. Have you checked the Cartographer’s documentation for an equivalent?
i have and I am currently talking to cartographer help ticket section on discord. there is no mention of speed anywhere but in the documentation of a simple p[robe you do have the speed which is default set at 5 mm/s.
I am wondering they set their default speed higher for the homing but my QGL is using the default 5 without mentioning anything. but I do not dare to simply add speed to my config without knowing what might happen.