M226 not working for me 3.2b3.2 duet2wifi standalone

Adrian52

Pause and resume works fine from dwc, but pausing a print using M226 in gcode doesnt work. Printer pauses, console says 'resume state saved', but head stays on print, suggesting that pause.g is not running. Console is then generally unresponsive, so print will not resume. Can reset with M999. M122 gives

22/11/2020, 21:28:40 	m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.2-beta3.2 running on Duet WiFi 1.0 or 1.01
Board ID: 08DAM-999TL-MQ4SD-6J9FD-3SJ6J-K593W
Used output buffers: 3 of 24 (12 max)
=== RTOS ===
Static ram: 24108
Dynamic ram: 100388 of which 40 recycled
Never used RAM 5512, free system stack 116 words
Tasks: NETWORK(ready,183) HEAT(blocked,308) MAIN(running,422) IDLE(ready,20)
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:14:29 ago, cause: software
Last software reset at 2020-11-22 21:14, reason: User, GCodes spinning, available RAM 5512, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
Error status: 0x00
MCU temperature: min 31.2, current 34.3, max 34.3
Supply voltage: min 24.1, current 24.3, max 24.6, under voltage events: 0, over voltage events: 0, power good: yes
Driver 0: position 63212, standstill, SG min/max 0/210
Driver 1: position 64922, standstill, SG min/max 0/1023
Driver 2: position 64018, standstill, SG min/max 0/1023
Driver 3: position 0, standstill, SG min/max 0/272
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: 2020-11-22 21:28:40
Cache data hit count 1368115331
Slowest loop: 133.29ms; fastest: 0.13ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 8
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 1.0ms, write time 10.1ms, max retries 0
=== Move ===
Hiccups: 6(0), FreeDm: 169, MinFreeDm: 139, MaxWait: 208783ms
Bed compensation in use: mesh, comp offset 0.000
=== MainDDARing ===
Scheduled moves 2033, completed moves 2033, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 0, StepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== Heat ===
Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.4
Heater 1 is on, I-accum = 0.5
=== GCodes ===
Segments left: 0
Movement lock held by File
HTTP is idle in state(s) 0
Telnet is idle in state(s) 0
File is idle in state(s) 0 21, running macro
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: 206.94ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 of 8
- WiFi -
Network state is active
WiFi module is connected to access point 
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.24
WiFi MAC address 5c:cf:7f:2c:24:6b
WiFi Vcc 3.37, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 25064
WiFi IP address 192.168.1.16
WiFi signal strength -53dBm, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
=== Filament sensors ===
Extruder 0: pos -0.66, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

Adrian52

Have now done some rolling back and forwards. M226 pause from gcode works for me in 3.1.1 and 3.2b2, but not in 3.2b3 or 3.2b3.2. Pause and resume working from dwc in all versions.

Adrian52

A further piece of information, retesting 3.2b3.2 - a pause induced by deliberate triggering of my laser filament monitor worked properly, and allowed an appropriate resume. An embedded M226 later in the same print caused the freeze seen before, which I have only been able to recover from by resetting.

Could someone else test M226 on 3.2b3.2.

dc42

Yes, it's broken, stuck on "pausing". I will fix it in the next beta.

Adrian52

@dc42 thank you