@dc42 Yes... Yes I do. Thank you. Could not find that anywhere and it was auto-generated i guess.
Happy as can be now.

Greetings,

I noticed this issue recently when i updated my D300VS printer to the 3.x.x firmware. Normally I home after a print and most prints my head ends in the center so I never noticed this bug for a year.

If i home when the head is centered (X=0.0, or Y=0.0) there is no issues full travel, but if the head is at the edge of the plate while near the bottom (X=100, Y=100, Z=0) the homing is not working as expected. The first leg hits and then it only lets the second legs run for about ~50mm to 100mm and fails.

The latest update 3.5.4 firmware (saw stated issue with homing and bug fix notes about wrong zip so updated) at least the printer retries again at this new height and makes it to a full home but it still throws the (Error: G0/G1: insufficient axes homed) but at least it gave it another try and is fully homed and seems to be fixed.

Is there some sort of hard limit in the delta printer homing mechanics to make sure it does not rip your arms off if a stop fails and i am exceeding them? I would assume that limit should start once the first arm hits and it should not be determined by height of gantry.

Is anyone else seeing this issue?

Thanks,
Aaron

I think that a great way to do my if statement at the end. I can call my own macro end code for the Duet. The Repetier will not know what that means and march along the added end code that the slicer has just for it. In my Duet end macro I can call the M0 command so it just stops after what I wanted it to do and not finish the code for the Repetier that is in the gcode file.

Also apparently I am trying to solve some problems that are not an issue on the Duet3D.

Thanks,
Lucidwolf

PS. The Duet3D has spoiled me for sure over a Ramps compatible Mega. Its going to be hard to go back.

Greetings,
I just got a second delta and this has complicated my tool string as it relates to G code. I would like to slice the code such that it could work for both the RepRap and Repitier printer, but slight things make it difficult for the End GCode in the slicer. I don't care if the gcode file messes with M83 vs M84, but at the end of printing I would like to find a way to restore the machine state to before it started.

I would like to have a way for the printer to either stop reading the G-code with an IF statement at the end and run its own clean up. Or maybe let it run the file through but then at the end run a system G file similar to config override that sets the machine back into its normal state.

Is there an M-code that I can't seem to find? Is there a way to run something after a print to set my units, relative vs. abs, etc... back to what was in my config.g file? Sorry if i just fail to google. I spent about 10 min searching and failed at finding anything. Maybe this is all handled in Octoprint like controllers that do this for you once you have multiple machines and handling start up and shut down for each is a pain.