Homeall issues
-
basicly modified mine to:
G91 ; Relative positioning
G1 Z5 F6000 ; Lift Z by 5mm
G1 S1 X-305 Y-305 F3000 ; course home X or Y
G1 S1 X-305 ; course home X
G1 S1 Y-305 ; course home Y
G1 X5 Y8 F600 ; move away from the endstops
G1 S1 X-10 ; fine home X
G1 S1 Y-10 ; fine home Y
G1 Z-300 F1800 S1 ; Move Z down until the switch triggersG90 ; Absolute positioning
this solved it yeah, dunno why the reprap code generator did it this way, as the other ones are that way aswell, eg:
; homex.g
; called to home the X axis
;
; generated by RepRapFirmware Configuration Tool on Sun Jun 18 2017 15:09:50 GMT+0200 (Vest-Europa (sommertid)); Lift Z relative to current position
G91
G1 Z5 F6000
G90; Move quickly to X axis endstop and stop there (first pass)
G1 X-305 F1800 S1; Go back a few mm
G91
G1 X5 F6000
G90; Move slowly to X axis endstop once more (second pass)
G1 X-305 F360 S1; Lower Z again
G91
G1 Z-5 F6000
G90 -
You dont need all that, it is redundant. Use the modified one i gave you.
-
You can modify your other ones to be stripped down as well.
-
I'm using a CoreXY, so modified mine to match the https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_CoreXY_printer
like I said, all the homing files are directly from the Reprap configurator. -
I'm using a CoreXY, so modified mine to match the https://duet3d.com/wiki/Configuring_RepRapFirmware_for_a_CoreXY_printer
like I said, all the homing files are directly from the Reprap configurator.I get it that it comes from the online configurator but it is not needed in DC42s fork (probably not needed in standard reprap)
G1 S1 X-305 Y-305 F3000 ; course home X or Y
G1 S1 X-305 ; course home X
G1 S1 Y-305 ; course home Yit is these parts that I am referring to only the first line is needed.
There are some examples from DC42 himself in this blog article and since he designed the fork i tend to follow his advice over what the online generator produces: https://miscsolutions.wordpress.com/2014/06/11/five-tips-for-using-dc42-firmware-on-the-reprappro-ormerod/
-
Also i believe the wiki shows both options as a reference that they can be done individually or combined in a single command. When sent individually per line the motion is handled one at a time x or y will move then the other.
when combined on the same line both motions will be executed at the same time.
What you have is redundancy as you can see in DC42s blog post he only uses the single line as well
-
You can easily test this for yourself… just remove the two single lines and you will find that the behavior is exactly the same as before because the other two lines do nothing but slow down the queue before moving on to the next command as they shouldnt because x and y are already in the commanded positions from the first line.
-
I get it that it comes from the online configurator but it is not needed in DC42s fork (probably not needed in standard reprap)
G1 S1 X-305 Y-305 F3000 ; course home X or Y
G1 S1 X-305 ; course home X
G1 S1 Y-305 ; course home Yit is these parts that I am referring to only the first line is needed.
On a Cartesian printer, you need only the first line. On a CoreXY printer you need all 3 because the first move will be terminated when either homing switch is triggered.
-
I get it that it comes from the online configurator but it is not needed in DC42s fork (probably not needed in standard reprap)
G1 S1 X-305 Y-305 F3000 ; course home X or Y
G1 S1 X-305 ; course home X
G1 S1 Y-305 ; course home Yit is these parts that I am referring to only the first line is needed.
On a Cartesian printer, you need only the first line. On a CoreXY printer you need all 3 because the first move will be terminated when either homing switch is triggered.
What is the purpose of this? Why not just have the second two lines then?
-
The purpose is to speed up homing, by moving the print head diagonally towards the homing corner until one of the axes has been homed. If your printer has a square print area and you start with the print head diagonally opposite the homing corner, this will halve the time it takes to home the X and Y axes.
-
Sorry i get that, i mean the purpose of the endstops triggering all motions to stop. Does the core xy endstops remain active after a homing sequence? just trying to understand the need for the difference in behavior.
-
Sorry i get that, i mean the purpose of the endstops triggering all motions to stop. Does the core xy endstops remain active after a homing sequence? just trying to understand the need for the difference in behavior.
No. Once homing has been completed, the end stops are ignored. But of course, once homing has been completed, the printer won't then move beyond the axes minima and maxima as defined in M208 of the config.g file.
-
Sorry i get that, i mean the purpose of the endstops triggering all motions to stop. Does the core xy endstops remain active after a homing sequence? just trying to understand the need for the difference in behavior.
What the firmware does when a homing switch is triggered during a G1 S1 move is to stop a motor or motors. If you wanted the X homing switch to stop X motion but allow Y motion to continue on a CoreXY machine, you would need to recalculate the move and change the speed and/or direction of both motors when the switch is triggered, instead of just stopping motors. Although this would not be impossible to do, it would be a lot more complicated, for no real advantage.
