Royce last edited by Royce
I just configured my homeall.g in the system editor.
So far, everything looks ok, except that, at the end of the homing procedure, the firmware seems to add some movements that are NOT defined in the homeall.g file.
This is my homeall.g:
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool on Sun Jul 15 2018 21:09:13 GMT+0200 (Mitteleuropäische Sommerzeit) G91 ; relative positioning G1 Z5 F6000 S2 ; lift Z relative to current position G1 S1 X-305 F1800 ; move quickly to X endstop and stop there (first pass) G1 X5 F6000 ; go back a few mm G1 S1 X-305 F360 ; move slowly to X axis endstop once more (second pass) G1 X5 F6000 ; go back a few mm to prevent running the motor into the Y endstop mount G1 S1 Y-305 F1800 ; move quickly to Y endstop and stop there (first pass) G1 Y5 F6000 ; go back a few mm G1 S1 Y-305 F360 ; move slowly to Y axis endstop once more (second pass) ; config this after I did the home offset setting stuff ; G90 ; absolute positioning ; G1 X15 Y15 F6000 ; go to first bed probe point and home Z ; G30 ; home Z by probing the bed ; G1 Z5 F100 S2 ; uncomment this line to lift the nozzle after homing
After the second homing pass on Y axis, the firmware goes to X15 Y15 and lifts Z for 10 more mm, even when this is not defined in the homeall script.
Is there any other location where this movement may come from?
Thanks in advance,
PS: At the moment this script should only home X and Y as I didnt configure the piezo orion as a z probe yet
If you send G28 then homeall.g will be run first. After that, if at least one axis has been flagged as homed but there are axes remaining flagged as not homed, it will try to home those axes. So in your example, it will run homez.g after running homeall.g, because homeall.g does not home Z.
For testing purposes you could add e.g. G92 Z0 at the end of homeall.g in order to flag Z as homed.
Royce last edited by
Perfect, that answers my question.