RRF3.01-RC12 Not Loading Config-Override.g on startup?

KeeganB

@droftarts said in RRF3.01-RC12 Not Loading Config-Override.g on startup?:

@KeeganB Try sending M98 P"config.g" and see if you get any errors. Not sure of the effect of those '{1}' lines at the end of the config.g.

Ian

Interesting. Those {1} values don’t show up in the dwc editor. They only appeared when I copied and pasted. I wonder if that’s the issue.

I’ll try pasting to a text editor, cleaning those up, and then saving a new config.

KeeganB

@droftarts
Nope, i don't think that is it. I pasted it in BBEdit, and it looks clean. I think the form code snippet tool added those {1}'s.

Phaedrux

@KeeganB said in RRF3.01-RC12 Not Loading Config-Override.g on startup?:

I think the form code snippet tool added those {1}'s.

Yes I think you're right.

KeeganB

Bump, any other ideas?

Phaedrux

If you manually send M501 does it get executed?

zerspaner_gerd

I think the problem is the same!
This variant, M500 P31, helped me
Before that, I also used a simple M500
Had posted it here before
https://forum.duet3d.com/topic/15317/reprapfirmware-3-01-rc6-released/147?_=1589506715771

dc42

To clarify:

M500 without the P31 parameter will always save the M665 and M666 parameters to config-override.g.g. I have just verified that this is still the case. It will also save the G31 parameters to config-override.g if a G31 command was read from config-override.g when the Duet was started.
If you add the P31 parameter then M500 will unconditionally include a G31 line in config-override.g.

From your description, you should not need to use M500 P31. You would only need to so that if you have changed the G31 parameters, e.g. the trigger height (Z parameter).

KeeganB

@dc42 Thanks David. That is how I understood it as well. So what am I missing?

KeeganB

@Phaedrux Yes. If i boot up the machine from powered off and send M501 as the first thing I do, it loads the values from the override files and you can see the Z value change.

KeeganB

SOLVED:

I had my end stops configured as active-low rather than active high. DOH.

For others following this that may learn from it, here is my incorrect code:

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

HERE IS THE CORRECT CODE:

; Endstops
M574 X2 S1 P"xstop"                                    ; configure active-high endstop for low end on X via pin xstop
M574 Y2 S1 P"ystop"                                    ; configure active-high endstop for low end on Y via pin ystop
M574 Z2 S1 P"zstop"                                    ; configure active-high endstop for low end on Z via pin zstop

dc42

@KeeganB said in RRF3.01-RC12 Not Loading Config-Override.g on startup?:

I had my end stops configured as active-low rather than active high.

I think you mean you had them configured as low-end (axis minimum) endstops instead of high end (axis maximum) endstops.