Warning: M500: No M501 command was executed in config.g

Phaedrux · 10 Sept 2021, 22:42

@dave-parry said in Warning: M500: No M501 command was executed in config.g:

"Warning: M500: No M501 command was executed in config.g" even though there is one there.

Can you please provide the results of M122 and M98 P"config.g" and post your config.g?

Dave Parry · 11 Sept 2021, 11:17

M122

=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.0beta3 (2021-08-24 13:56:10) running on Duet Ethernet 1.02 or later
Board ID: 0JD0M-9P6M2-NWNS4-7J1DA-3SJ6M-TA2ZK
Used output buffers: 3 of 24 (22 max)
=== RTOS ===
Static ram: 23940
Dynamic ram: 69944 of which 0 recycled
Never used RAM 18196, free system stack 190 words
Tasks: NETWORK(ready,26.4%,247) HEAT(notifyWait,0.0%,310) Move(notifyWait,0.0%,364) MAIN(running,73.4%,445) IDLE(ready,0.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:45 ago, cause: software
Last software reset at 2021-09-11 12:12, reason: User, GCodes spinning, available RAM 18196, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 0
MCU temperature: min 40.1, current 40.5, max 40.8
Supply voltage: min 24.1, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 34640, standstill, SG min/max not available
Driver 1: position 34640, standstill, SG min/max not available
Driver 2: position 34640, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0
Driver 6: position 0
Driver 7: position 0
Driver 8: position 0
Driver 9: position 0
Driver 10: position 0
Driver 11: position 0
Date/time: 2021-09-11 12:13:03
Cache data hit count 1743212367
Slowest loop: 10.26ms; fastest: 0.16ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.2ms, write time 2.8ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0
USB is idle in state(s) 0
Aux is idle in state(s) 0
Trigger is idle in state(s) 0
Queue is idle in state(s) 0
LCD is idle in state(s) 0
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty
=== Network ===
Slowest loop: 31.65ms; fastest: 0.04ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
Interface state active, link 100Mbps full duplex

M98 P"config.g"
HTTP is enabled on port 80
FTP is disabled
TELNET is disabled
Error: No power fail script provided
Error: G0/G1: insufficient axes homed

; Configuration file for Duet 0.8.5 (firmware version 1.21)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.2 on Thu Sep 02 2021 19:22:19 GMT+0100 (British Summer Time)

; General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"MiniKossel" ; set printer name
M665 R105.6 L217.29 B85 H243.1 ; Set delta radius, diagonal rod length, printable radius and homed height
M666 X-26.2 Y-26.2 Z-26.4 ; put your endstop adjustments here, or let auto calibration find them

; Network
M540 PBE:XX:XX:XX:XX:XX ; set custom MAC address
M552 P192.X.X.XX S1 ; enable network and set IP address
M553 P255.255.255.0 ; set netmask
M554 P192.X.X.X ; set gateway
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 S1 ; physical drive 1 goes forwards
M569 P2 S1 ; physical drive 2 goes forwards
M569 P3 S1 ; physical drive 3 goes forwards
M584 X0 Y1 Z2 E3 ; set drive mapping
M92 X80.00 Y80.00 Z80.00 E683.5 ; set steps per mm
M566 X1200.00 Y1200.00 Z1200.00 E1200.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 E1000.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E450 I60 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout

; Axis Limits
M208 Z-0.1 S1 ; set minimum Z

; Endstops

M574 X2 S1 P"xstop" ; X min active high endstop switch
M574 Y2 S1 P"ystop" ; Y min active high endstop switch
M574 Z2 S1 P"zstop" ; Z min active high endstop switch

; Z-Probe

M558 P1 C"zprobe.in" H8 F120 T2400 ; set Z probe type to switch and the dive height + speeds
G31 P500 X-0 Y-0 Z1.371; this Z offset is just above the bed, I fine tune with my Z offset routine.

; Bed Mesh
M557 R130 S20 ; probe within a radius of 130mm from the centre with a mesh spacing of 20mm

; Heaters

M308 S0 P"bed_temp" Y"thermistor" T100000 B3950 ; define bed temperature sensor
M308 S1 P"e0temp" Y"thermistor" T100000 B4388; define E0 temperature sensor
M950 H0 C"bed_heat" T0 ; heater 0 uses the bed_heat pin, sensor 0
M950 H1 C"e0heat" T1 ; heater 1 uses the e0heat pin and sensor 1
M140 P0 H0 ; map heated bed to heater 0

; Fans

M950 F0 C"fan0"
M950 F1 C"fan1"
M106 P0 S0 I0 F500 H-1 C"Part Clg" ; set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned off
M106 P1 S0 I0 F500 H-1 C"Bed Clg" ; set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off

; 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

; Power Failure
M911 S21.0 R23.0 G91 M83 G1 Z3 E-5 F1000"

; Miscellaneous
T0 ; select first tool
M501

Dave Parry · 11 Sept 2021, 11:38

Dont know if its relevent but I just tried G29 S0 and all I get is response too long and console shows
Warning: Skipping grid point X=-80.0, Y=60.0 because Z probe cannot reach it for all points.

It does save a file to card but Hieght map says invalid

jay_s_uk · 11 Sept 2021, 11:55

@dave-parry heightmap invalid was a bug in version 3.2 of the DWC so you need to update the version of DWC you're running

Dave Parry · 11 Sept 2021, 13:09

This post is deleted!

dc42 · 11 Sept 2021, 13:15

@jay_s_uk said in Warning: M500: No M501 command was executed in config.g:

@dave-parry heightmap invalid was a bug in version 3.2 of the DWC so you need to update the version of DWC you're running

Not actually a bug, it's because the height map file format was changed to support axes other than X and Y, and older DWC versions don't know about the new format.

Dave Parry · 11 Sept 2021, 13:22

Ok Updated to 3.3, but don't have time just at the mo to see if that has fixed it. Will try later this afternoon

Dave Parry · 9 Nov 2021, 17:15

I am getting a height map now. I think the warnings were for additional points on the command outside my print bed diameter. But still have the original problem.
Also get the following

11/09/2021, 18:11:46 G32
Error: Auto calibration failed because probe point P0 was unreachable using the current delta parameters. Try a smaller probing radius.
11/09/2021, 18:10:34 M500
Warning: M500: No M501 command was executed in config.g

Phaedrux · 9 Nov 2021, 19:11

@dave-parry said in Warning: M500: No M501 command was executed in config.g:

; Power Failure
M911 S21.0 R23.0 G91 M83 G1 Z3 E-5 F1000"

You're missing a double quote mark on this line and I think that's messing up the rest of the lines after it.

Here's my line as comparison:

 ; POWER LOSS RECOVERY
;
M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-1 F500"  ; Configure automatic saving on power loss

Dave Parry · 12 Sept 2021, 08:53

Thanks for reply but still getting error message "Warning: M500: No M501 command was executed in config.g"
here's what I have at the end of config.g now

; Power Failure
;
M911 S21.0 R23.0 G91 M83 G1 Z3 E-5 F1000"

; Miscellaneous
T0 ; select first tool

M501

SIam · 9 Dec 2021, 09:10

@dave-parry said in Warning: M500: No M501 command was executed in config.g:

as @Phaedrux said, here is your mistake

M911 S21.0 R23.0 G91 M83 G1 Z3 E-5 F1000"

change this to:

M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"

Dave Parry · 9 Dec 2021, 09:16

@siam said in Warning: M500: No M501 command was executed in config.g:

M911 S21.0 R23.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000"

Thanks Slam that seems to have fixed it.
Just have to recalibrate it now.
Have to say this hasn't been as easy a transition from a legacy duet to a duet 2 has I had hoped.
Thanks to all for their help.

	; POWER LOSS RECOVERY
	;
	M911 S21 R23 P"M913 X0 Y0 G91 M83 G1 Z3 E-1 F500" ; Configure automatic saving on power loss