Changes to config.g ignored when printing.
-
I have a CoreXY printer with a BMG extruder and V6 hotend. I also have a BLTouch and three z-axis motors.
Originally it was controlled by a 6HC connected to a Raspberry Pi using the latest available firmware.
The first time I realised this issue was when setting up the bed levelling where the BLTouch probes nears the z-axis motors and compensates. No matter what I changed, it refused to move to the points I inputted. The config files showed my new settings but when the command was run, the probe was nowhere near those points.
I decided to remove the Raspberry Pi. This seemed to work.
This was a few months ago.
Present Day:
I am trying to calibrate the z-axis offset. No matter what I do (turn the printer off, click the emergency button), it refuses to use the new value for the z-offset.
I run the proceedure for getting the z-offset, I input it into the config.g and then I test it by re-homing. Sometimes I'll power off and then power on. But it ignores the values stored in the config.g.
Is there a command I am missing to save these changes to the board? A button to press?
I haven't had this issue before with the Duet 2 or when I first got the Duet 3 6HC.
Many Thanks.
-
@mjimeyg config.g is normally only read at startup. Therefore, after you make a change to config.g, you need to either reset the board (e.g. use the Emergency Stop button), or run M98 P"config.g" for the changes to take effect. This has always been the case.
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 Would powering off and on achieve the same thing?
Based on that then something else is wrong. Do you know what it could be?
-
@mjimeyg said in Changes to config.g ignored when printing.:
@dc42 Would powering off and on achieve the same thing?
Based on that then something else is wrong. Do you know what it could be?
Yes, cycling the power will run config.g again. If you use config-override.g and have M501 in your config.g file, then it will also run config-override.g. So anything that is in config-override.g will do as it says and override the values that are in config.g. Do you have anything in config-override.g ?
-
@deckingman Yes, I've included it below.
; config-override.g file generated in response to M500 at 2021-11-28 10:26 ; Heater model parameters M307 H0 R0.488 C616.200:616.200 D2.60 S1.00 V23.9 B0 M307 H1 R1.258 C207.600:207.600 D11.70 S1.00 V23.2 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.00Could the G10 commands be overriding it? I didn't add them and assume they were generated by either the firmware or the reprap config tool.
-
@deckingman I commented out those G10 lines but it didn't affect anything.
-
@mjimeyg I guess you'd better tell us what procedure and commands you are using to set the z offset. It would probably help if you post your entire config.g and any homing files that use the z offset (i.e. homez.g and homeall.g).
-
@deckingman I use the following guide for z-offset calibration: BLTouch on Duet WiFi – Configuration and usage
My files:
config.g:
; Configuration file for Duet 3 (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Thu Jan 09 2020 15:44:47 GMT+0000 (Greenwich Mean Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"RatRig" ; set printer name M667 S1 ; select CoreXY mode ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S1 ; disable FTP M586 P2 S1 ; disable Telnet ; Drives M569 P0.0 S1 ; physical drive 0.0 goes forwards M569 P0.1 S1 ; physical drive 0.1 goes forwards M569 P0.2 S0 ; physical drive 0.2 goes forwards ; Left M569 P0.3 S0 ; physical drive 0.3 goes forwards ; Rear M569 P0.4 S0 ; physical drive 0.4 goes forwards ; Right M569 P0.5 S1 ; physical drive 0.5 goes backwards M584 X0.0 Y0.1 Z0.2:0.3:0.4 E0.5 ; set drive mapping (Left:0.2 - Rear:0.3 - Right:0.4) M671 X-30:230:25 Y120:556:120 S15 ; Kinematic bed ball locations - front left, front right and rear center M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E409.00 ; set steps per mm M566 X900.00 Y900.00 Z12.00 E120.00 ; set maximum instantaneous speed changes (mm/min) M203 X6000.00 Y6000.00 Z1000.00 E1200.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2) M906 X800 Y800 Z800 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y0 Z0 S1 ; set axis minima M208 X500 Y500 Z500 S0 ; set axis maxima ; Endstops M574 X1 S3 ; configure sensorless endstop for low end on X M574 Y1 S3 ; configure sensorless endstop for low end on Y M574 Z1 S3 ; configure sensorless endstop for low end on Z ; Z-Probe M950 S0 C"io7.out" ; create servo pin 0 for BLTouch M558 P9 C"io7.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds ;M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved G31 P500 X-29 Y-12 Z4.53; set Z probe trigger value, offset and trigger height M557 X15:470 Y15:470 S40 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" A"Bed" T100000 B3950 ; configure sensor 0 as thermistor on pin temp0 M950 H0 C"out0" T0 ; create bed heater output on out0 and map it to sensor 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M307 H0 A436.5 C459.5 D4.1 S1.00 V0 B0 ; disable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M308 S1 P"temp2" Y"thermistor" A"Hotend" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor on pin temp2 M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Fans M950 F0 C"out7" Q500 ; create fan 0 on pin out7 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"out8" Q500 ; create fan 1 on pin out8 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 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 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss T0 ; select first tool M501config-override.g:
; config-override.g file generated in response to M500 at 2021-11-28 10:26 ; Heater model parameters M307 H0 R0.488 C616.200:616.200 D2.60 S1.00 V23.9 B0 M307 H1 R1.258 C207.600:207.600 D11.70 S1.00 V23.2 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.00bed.g:
; bed.g ; called to perform automatic bed compensation via G32 ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Thu Jan 09 2020 15:44:47 GMT+0000 (Greenwich Mean Time) M561 ; clear any bed transform ;G28 ; home M558 F160 G30 P0 X10 Y115 Z-99999 ; probe near left leadscrew G30 P1 X240 Y465 Z-99999 ; probe near rear leadscrew G30 P2 X450 Y115 Z-99999 S3 ; probe near right leadscrew and calibrate 3 motors G1 X0 Y0 F20000 G29 S1homeall.g:
; homeall.g ; called to home all axes ; ; generated by RepRapFirmware Configuration Tool v2.1.5 on Thu Jan 09 2020 15:44:47 GMT+0000 (Greenwich Mean Time) M400 M913 X70 Y70 ; drop motor current to 70% M400 G91; relative positioning G1 H2 Z20 F12000 ; lift Z relative to current position G1 H1 X-500.5 F10000 ; move quickly to X axis endstop and stop there (first pass) G1 H2 X5 F12000 ; go back a few mm G1 H1 X-500.5 F7000 ; move slowly to X axis endstop once more (second pass) ;G1 H2 Z-10 F6000 ; lower Z again G90 ; absolute positioning M400 M913 X100 Y100 ; return current to 100% M400 M400 M913 X70 Y70 ; drop motor current to 70% M400 G91; relative positioning ;G1 H2 Z10 F12000 ; lift Z relative to current position G1 H1 Y-500.5 F10000 ; move quickly to Y axis endstop and stop there (first pass) G1 H2 Y5 F12000 ; go back a few mm G1 H1 Y-500.5 F7000 ; move slowly to Y axis endstop once more (second pass) ;G1 H2 Z-20 F6000 ; lower Z again G90 ; absolute positioning M400 M913 X100 Y100 ; return current to 100% M400 ;G1 H2 Z20 F12000 ; lift Z relative to current position G1 X250 Y250 F6000 ; Move probe to middle of bed M558 F500 ; Set the probing speed G30 ; Do a single probe to home our Z axis M558 F50 ; Set a slower probing speed G30 G1 H2 Z20 F6000 ; lower Z again G32 ; Run 3-point bed calibration defined in bed.g ;G1 H1 Z-275 F360 ; move Z down stopping at the endstop ;G90 ; absolute positioning ;G92 Z0 ; set Z position to axis minimum (you may want to adjust this) ; Uncomment the following lines to lift Z after probing ;G91 ; relative positioning ;G1 Z5 F100 ; lift Z relative to current position ;G90 ; absolute positioningThose are my files.
-
Which offset exactly are you changing?
-
@phaedrux I am changing the config.g file, line 50, the z argument of the G31 command:
G31 P500 X-29 Y-12 Z4.53; set Z probe trigger value, offset and trigger heightI would like to reiterate two things:
1- This is board was working with this firmware and has stopped accepting the changes recently. I have not made any hardware or firmware changes.
2- The calibration process works perfectly. I can perform it as listed in the provided webpage and get a good offset. The issue lies in that the value is ignored once the board is reset. So, if I perform all the calibration settings and set the G31 command manually, the bed will level. It is how I am still printing. But if I turn the printer off or save the changes to the config.g file, then once the board has reset itself, it ignores the value saved and listed... by aproximately 0.3.
Finally, this is not an issue limited to the G31 command. Any changes are ignored to any command.
-
After you try changing it can you send G31 in the console and report back what it says?
Can you also send M98 P"config.g" in the console and report back any errors.
-
@phaedrux After changing the G31 z value from 4.31 to 4.5 in the config.g file and then going through the reset, the response from the G31 command is:
Z probe 0: current reading 0, threshold 500, trigger height 4.500, offsets X-29.0 Y-12.0The response from the M98 P"config.g" command is:
HTTP is enabled on port 80 FTP is enabled on port 21 TELNET is enabled on port 23 Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 461C Warning: Heater 0 appears to be over-powered. If left on at full power, its temperature is predicted to reach 325C -
Just to be sure, the config.g file you're editing is located in the system tab in DWC?
Can you check the config.g file on the SD card in a computer to make sure it's not write protected or something?
If you set the G31 offset manually in the console with G31 Z4.31 and then send G31 again, does it show the new value?
-
@phaedrux I am using the DWC.
The SD card is not write protected.
The G31 command shows the new value after is set with the G31 command.
-
If you make any other changes to the config.g are they reflected at startup?
-
@phaedrux I changed the M557 to:
M557 X15:200 Y15:200 S40I then ran a G29 and it did probe only a quarter of the bed as per the changed command in the config.g.
I also remembered that a few weeks ago Thermistor 1 out stopped working and I had to change the hotend thermistor to Thermistor 2. This is long after the issues with the config,g but it might be worth mentioning.
-
@mjimeyg said in Changes to config.g ignored when printing.:
@phaedrux After changing the G31 z value from 4.31 to 4.5 in the config.g file and then going through the reset, the response from the G31 command is:
Z probe 0: current reading 0, threshold 500, trigger height 4.500, offsets X-29.0 Y-12.0Just to recap. You changed the G31 offset from 4.31 to 4.5. Then you reset the board and sent G31 without any parameters and got back the resultant offset as being 4.5 yes? If that is the case, then the changes are not being ignored as per your thread title. I don't use a BLTouch so I'm not best qualified to comment but are you sure it's working properly and consistently? It just seems that the board and firmware are behaving as expected so the issue might be something else.
