Homing problems

Phaedrux

Warning: the height map was loaded when the current Z=0 datum was not determined probing. This may result in a height offset.

Do not load the heightmap in config.g

@capmjk said in Homing problems:

G29 S1

Remove this from config.g. The best place to load the heightmap is in your slicer start gcode after the auto calibration or at least after establishing the Z0 point with a single G30 at the center of the bed.

Can you post your bed.g? How are you doing the auto delta calibration?

CapMJK

@phaedrux

; bed.g
; called to perform automatic delta calibration via G32
;
; generated by RepRapFirmware Configuration Tool v2 on Mon Apr 08 2019 07:52:58 GMT+0100 (British Summer Time)
M561 ; clear any bed transform
G28  ; home all towers
; Probe the bed at 6 peripheral and 6 halfway points, and perform 6-factor auto compensation
; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g.
G30 P0 X0 Y169.9 H0 Z-99999
G30 P1 X147.14 Y84.95 H0 Z-99999
G30 P2 X147.14 Y-84.95 H0 Z-99999
G30 P3 X0 Y-169.9 H0 Z-99999
G30 P4 X-147.14 Y-84.95 H0 Z-99999
G30 P5 X-147.14 Y84.95 H0 Z-99999
G30 P6 X0 Y84.9 H0 Z-99999
G30 P7 X73.53 Y42.45 H0 Z-99999
G30 P8 X73.53 Y-42.45 H0 Z-99999
G30 P9 X0 Y-84.9 H0 Z-99999
G30 P10 X-73.53 Y-42.45 H0 Z-99999
G30 P11 X-73.53 Y42.45 H0 Z-99999
G30 P12 X0 Y0 H0 Z-99999 S6
; Use S-1 for measurements only, without calculations. Use S4 for endstop heights and Z-height only. Use S6 for full 6 factors
; If your Z probe has significantly different trigger heights depending on XY position, adjust the H parameters in the G30 commands accordingly. The value of each H parameter should be (trigger height at that XY position) - (trigger height at centre of bed)
G29
M500

I only had to do a g30 in the past when i changed something like a nozzle. But now it seems i need to set x,y,z manually to zero after every startup.

i got rid of the G29 S1 although its strange that is has been in there for ages without a prior problem.

Phaedrux

@capmjk said in Homing problems:

its strange that is has been in there for ages without a prior problem.

You just updated your firmware though did you not?

@capmjk said in Homing problems:

I only had to do a g30 in the past when i changed something like a nozzle. But now it seems i need to set x,y,z manually to zero after every startup.

I'm not sure how you managed to escape having to home the towers after a power cycle? The axis are marked unhomed at power on.

CapMJK

@phaedrux
in the past when the printer homed it set the height after homing to homed height (the one in the config). Now it seems the printer thinks on power on he is homed, then adds the height he travels upwards while homing the first time and adds it ontop.
Then of course he ends up at z=600-800 something and can't travel anymore because he is higher than the maximum z-height i have configured.

JoergS5

@capmjk said in Homing problems:

Now it seems the printer thinks on power on he is homed,

I am not sure whether you updated, because config says RRF version 2, and M122 tells your firmware is 3.3. Your endstops may have been S0, which is not valid in 3.3 any more, you need to use S1 with a !, please check https://duet3d.dozuki.com/Wiki/RepRapFirmware_3_overview#Section_M574 first statement, if the endstops behave opposite now.

Phaedrux

At first power on does the DWC think the printer is homed?

If you send M119 to check the endstop status does it think they are triggered when not actually depressed?

Have you re-run a delta auto calibration since we solved the original homing problem?

Have you removed the G29 S1 from config.g yet?

CapMJK

@phaedrux
No it tells me that no axis is homed.
M119 tells me that all endstops are working properly.
I have to run a delta calibration after every boot at the moment, else it doesn't print correctly.

Have removed G29 S1 from config.g.

Still weird stuff. Have to zero x and y every time after boot. Its driving me mad even though its only 2 quick commands.

The problems arose before i updated the firmware, came out of the blue.

Well yesterday of my belts ripped so i replaced all of them. I think my printer just punishes me for organizing a second one and buying a duet 3 for the new one.

CapMJK

@capmjk update:

calibration now also needs to be done after every bootup. else the heightmap is wrong

JoergS5

@capmjk said in Homing problems:

; Endstops
M574 X1 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
M574 Y1 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
M574 Z1 S1 P"zstop"

I wonder why M574 sets the endstops to low end. IMO it should be X2, Y2, Z2.

CapMJK

@joergs5 thats true. I changed it but i wonder why it worked for so long.

OK now i got a different problem. Now it ALWAYS sets height after homing to the original homed height but does not save the z- value after g30

Phaedrux

I may not understand your comment correctly, but homed height would only be saved if you run a delta calibration and then send M500 to save it to config-override.g.

Nothing will get saved after just sending G30. That will only be applied for the current power on cycle.

JoergS5

@capmjk you will not be able to store the Z position between reboots, because when stepper are turned off, they change position by +- 2 full steps each in worst case. It's necessary to measure Z0 position every time after power on and let set the firmware the stepper position.

Another point because you said mesh compensation is not correct: G31 is set to have 0 offset for X and Y, is this correct? Is your probe at the same XY position like the nozzle?

CapMJK

@joergs5 yes. My current probe is manually attached but centered directly below the nozzle.

i know that the current z-pos cannot be saved but before i made your change with the endstops even the homed height was gone after every power off. That is working now

@Phaedrux since i corrected the endstop position to be top side z height is not even saved within a power cycle. As an example: I moved the printer to z=0 after homing and it was 20mm above the bed. So i put g92 z25 -> moved it down until it was the correct height, put g92 z0 in, then M500 and homed. But after the homing z0 was again 20mm above the bed. So even in the power cycle it did not remember the new z0 height and instead set the original homed height after homing.

Phaedrux

@capmjk said in Homing problems:

moved it down until it was the correct height, put g92 z0 in, then M500 and homed. But after the homing z0 was again 20mm above the bed. So even in the power cycle it did not remember the new z0 height and instead set the original homed height after homing.

That's not how homed height is saved. You must do a delta auto calibration and then save it with M500.

https://duet3d.dozuki.com/Wiki/Calibrating_a_delta_printer

CapMJK

@phaedrux i know that now. It worked though because my endstops were wrongfully configured as low end for the last year. Don't ask me though WHY it worked that way.

By the way: Its all working properly now. Thanks alot all of you!

I will be back in time probably since i am currently installing my new Duet 3 into my second printer.