RRF3.01-RC12 Not Loading Config-Override.g on startup?
-
I'm happy to post my config, bed, override, and etc files.
I highly doubt my M500 parameters are an issue. As I said, after running M500 the override is updated properly.
-
bed.g:
Orion Send code... Status Idle Mode: FFF Tool Position X -0.3 Y 0.0 Z 229.79 Extruder Drives Drive 0 0.0 Speeds Requested Speed 0 mm/s Top Speed 0 mm/s Sensors Vin 11.9 V MCU Temperature 30.2 C Z-Probe 0 Tools Extra Control All Tool Heater Current Active Standby Hot End T0 - Load Filament Heater 1 active 24.2 C 0 0 Bed Heater 0 off 24.7 C 0 0 Temperature Chart System Directory 0:/sys/bed.g ; bed.g ; called to perform automatic delta calibration via G32 ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue Mar 31 2020 14:38:51 GMT-0400 (EDT) M561 ; clear any bed transform ; Before running this, you should have set up your Z-probe trigger height to suit your build, in the G31 command in config.g. ; 10 points, 6 factors, probing radius: 65, probe offset (0, 0) G30 P0 X0.00 Y65.00 Z-99999 H0 G30 P1 X56.29 Y32.50 Z-99999 H0 G30 P2 X56.29 Y-32.50 Z-99999 H0 G30 P3 X0.00 Y-65.00 Z-99999 H0 G30 P4 X-56.29 Y-32.50 Z-99999 H0 G30 P5 X-56.29 Y32.50 Z-99999 H0 G30 P6 X0.00 Y32.50 Z-99999 H0 G30 P7 X28.15 Y-16.25 Z-99999 H0 G30 P8 X-28.15 Y-16.25 Z-99999 H0 G30 P9 X0 Y0 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)homedelta.g:
; homedelta.g ; called to home all towers on a delta printer ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue Mar 31 2020 14:38:51 GMT-0400 (EDT) G91 ; relative positioning G1 H1 X290 Y290 Z290 F1800 ; move all towers to the high end stopping at the endstops (first pass) G1 H2 X-5 Y-5 Z-5 F1800 ; go down a few mm G1 H1 X10 Y10 Z10 F360 ; move all towers up once more (second pass) G1 H2 X-15 Y-15 Z-15 F1800 ; move down a few mm so that the nozzle can be centred G90 ; absolute positioning -
config.g
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.8 on Tue Mar 31 2020 14:38:51 GMT-0400 (EDT) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Orion" ; set printer name M665 R88.512 L178 B85 H230 ; Set delta radius, diagonal rod length, printable radius and homed height M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them ; Network M552 S1 ; enable network ;M552 S2 ; enable AP Mode network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 goes forwards M569 P1 S0 ; physical drive 1 goes backwards M569 P2 S1 ; physical drive 2 goes forwards M569 P3 S1 ; physical drive 3 goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z80.00 E93.30 ; set steps per mm M566 X1200.00 Y1200.00 Z1200.00 E2100.00 ; set maximum instantaneous speed changes (mm/min) M203 X20000.00 Y20000.00 Z20000.00 E3600.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z1000.00 E3000.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z1000 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 Z0 S1 ; set minimum Z ; 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 ; Z-Probe M558 P5 C"e0stop" H15 F500 T6000 ; set Z probe type to switch and the dive height + speeds G31 P500 X0 Y0 Z-0.32 ; set Z probe trigger value, offset and trigger height M557 R75 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 B0 S1.00 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M570 H0 S360 P180 M308 S1 P"e0temp" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M143 H1 S280 ; set temperature limit for heater 1 to 280C M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"fan0" ;Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" ;Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T50 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 S"Hot End" D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; Custom settings are not defined ; Miscellaneous M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss M501 ; load saved parameters from non-volatile memory T0 ; select first toolconfig-override.g:
; config-override.g file generated in response to M500 at 2020-05-13 16:54 ; This is a system-generated file - do not edit ; Delta parameters M665 L178.000:178.000:178.000 R88.538 H229.532 B85.0 X-0.062 Y0.097 Z0.000 M666 X-0.141 Y0.567 Z-0.426 A0.00 B0.00 ; Heater model parameters M307 H0 A340.0 C140.0 D5.5 S1.00 V0.0 B0 M307 H1 A340.0 C140.0 D5.5 S1.00 V0.0 B0 ; Workplace coordinates G10 L2 P1 X0.00 Y0.00 Z0.00 G10 L2 P2 X0.00 Y0.00 Z0.00 G10 L2 P3 X0.00 Y0.00 Z0.00 G10 L2 P4 X0.00 Y0.00 Z0.00 G10 L2 P5 X0.00 Y0.00 Z0.00 G10 L2 P6 X0.00 Y0.00 Z0.00 G10 L2 P7 X0.00 Y0.00 Z0.00 G10 L2 P8 X0.00 Y0.00 Z0.00 G10 L2 P9 X0.00 Y0.00 Z0.00 -
@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
TronXY X5S with Duet 3 MB6HC and Roto toolboard : Cartesian bed-slinger with Duet 3 Mini 5+ WiFi and 1LC : RRP Fisher Delta v1 with Duet 2 Maestro : Polargraph with Duet 2 WiFi
-
@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.
-
@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. -
@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.
-
Bump, any other ideas?
-
If you manually send M501 does it get executed?
-
I think the problem is the same!
This variant,M500 P31, helped me
Before that, I also used a simpleM500
Had posted it here before
https://forum.duet3d.com/topic/15317/reprapfirmware-3-01-rc6-released/147?_=1589506715771 -
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).
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 Thanks David. That is how I understood it as well. So what am I missing?
-
@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.
-
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 zstopHERE 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 -
@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.
