DWC Error: M32: Cannot set file to print...

Form3DCP

I have been using Duet boards for a couple years now and I have run across this issue on a Duet 3 MB6HC with SBC RPI4 and cannot find anyone else having this issue. Everytime I try to run a print from the DWC it gives this "Error: M32: Cannot set file to print, because a file is already being printed" then changes status from idle to printing and doesn't do anything but stay at 0% progress. I was able to configure and move the machine around and I have printed with this mainboard and sbc with no problems before. Reformatting SD card, reloading firmware, and using different slicers yielded the same result. I am running firmware 3.3 with DWC 3.4. I have no idea what is happening here, please help! Update: I can run prints from the macros directory but this isn't ideal.

M122 Output:

M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-956L2-G43S8-6J1FA-3SJ6Q-1B0AG
Used output buffers: 1 of 40 (12 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 61068 of which 0 recycled
Never used RAM 142220, free system stack 152 words
Tasks: SBC(ready,18.7%,334) HEAT(delaying,0.0%,405) Move(notifyWait,0.0%,241) CanReceiv(notifyWait,0.0%,908) CanSender(notifyWait,0.0%,362) CanClock(delaying,0.0%,339) TMC(notifyWait,7.3%,59) MAIN(running,74.0%,1131) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:59:57 ago, cause: software
Last software reset at 2022-04-29 14:27, reason: User, none spinning, available RAM 139356, slot 0
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 163
MCU temperature: min 40.2, current 40.7, max 40.7
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, current 12.2, max 12.3, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 52090, writes 0 timeouts 0, SG min/max not available
Driver 1: position 0, standstill, reads 52090, writes 0 timeouts 0, SG min/max not available
Driver 2: position 2000, standstill, reads 52090, writes 0 timeouts 0, SG min/max not available
Driver 3: position 0, standstill, reads 52090, writes 0 timeouts 0, SG min/max not available
Driver 4: position 0, standstill, reads 52090, writes 0 timeouts 0, SG min/max not available
Driver 5: position 0, standstill, reads 52089, writes 0 timeouts 0, SG min/max not available
Date/time: 2022-04-29 16:03:12
Slowest loop: 0.45ms; fastest: 0.03ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 14, completed moves 14, 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 = -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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
SBC is idle in state(s) 0
Daemon is idle in state(s) 0
Aux2 is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== CAN ===
Messages queued 1865, received 0, lost 0, longest wait 0ms for reply type 0, peak Tx sync delay 7, free buffers 49 (min 49), ts 1865/1865/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 1, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 44887/44887
SPI underruns 0, overruns 0
Disconnects: 1, timeouts: 1, IAP RAM available 0x2c810
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.4.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 4088.44, max time between full transfers: 24.8ms, max pin wait times: 9.9ms/12.1ms
Codes per second: 0.00
Maximum length of RX/TX data transfers: 2988/64

Here is my configuration.g:

; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Apr 28 2022 14:12:14 GMT-0500 (Central Daylight Time)

; General preferences
G90                                                ; send absolute coordinates...
M83                                                ; ...but relative extruder moves
M550 P"Duet 3"                                     ; set printer name

M569 P40.0 S1 R0 T20:20:20:20

; Drives

M569 P0.0 S0                                       ; physical drive 0.0 goes forwards
M569 P0.1 S0                                       ; physical drive 0.1 goes forwards
M569 P0.2 S0 
M569 P0.3 S0
M569 P0.4 S0
M569 P0.5 S0
M584 X40.0 Y0.0:1 Z0.2:3:4:5                                ; set drive mapping
M350 X16 Y16 Z16 I1                                ; configure microstepping with interpolation
M92 X8.00 Y400.00 Z400.00                         ; set steps per mm
M566 X1000.00 Y800.00 Z60.00                        ; set maximum instantaneous speed changes (mm/min)
M203 X1800.00 Y1500.00 Z500.00                     ; set maximum speeds (mm/min)
M201 X1000.00 Y800.00 Z20.00                        ; set accelerations (mm/s^2)
M906 Y4200 Z4200 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 X700 Y1100 Z650 S0                            ; set axis maxima

; Endstops
M574 X1 S1 P"!io0.out"                          
M574 Y1 S1 P"!io1.out+!io6.out"                              
M574 Z1 S1 P"!io2.out"                               

; Z-Probe
M558 P0 H5 F120 T6000                             
M557 X15:215 Y15:195 S20                           


; Custom settings are not defined

; Miscellaneous

Here is the debug when I try to run a print:

Apr 29 14:19:17 duet3 DuetControlServer[414]: [debug] Waiting for execution of M32 "0:/gcodes/please.gcode"
Apr 29 14:19:17 duet3 DuetControlServer[414]: [debug] Processing M32 "0:/gcodes/please.gcode"
Apr 29 14:19:17 duet3 DuetControlServer[414]: [info] Selected file /opt/dsf/sd/gcodes/please.gcode
Apr 29 14:19:17 duet3 DuetControlServer[414]: [debug] Waiting for finish of M32 "0:/gcodes/please.gcode"
Apr 29 14:19:17 duet3 DuetControlServer[414]: [debug] HTTP: Sent M32 "0:/gcodes/please.gcode", remaining space 1480, needed 56
Apr 29 14:19:17 duet3 DuetControlServer[414]: [info] Starting macro file start.g on channel File
Apr 29 14:19:17 duet3 DuetControlServer[414]: [debug] Completed M32 "0:/gcodes/please.gcode" => Error: M32: Cannot set file to print, because a file is already being printed
Apr 29 14:19:17 duet3 DuetControlServer[414]: [debug] IPC#33: Connection closed
.
.  
.
.
Apr 29 14:19:22 duet3 DuetControlServer[414]: [debug] Completed G28
Apr 29 14:19:22 duet3 DuetControlServer[414]: [debug] Finished codes from macro file start.g
Apr 29 14:19:22 duet3 DuetControlServer[414]: [info] Finished macro file start.g
Apr 29 14:19:22 duet3 DuetControlServer[414]: [debug] File: Disposing macro file start.g
Apr 29 14:19:22 duet3 DuetControlServer[414]: [debug] Requesting update of key inputs, seq 14 -> 17
Apr 29 14:19:22 duet3 DuetControlServer[414]: [debug] Updated key inputs
Apr 29 14:19:22 duet3 DuetControlServer[414]: [debug] Requesting update of key move, seq 39 -> 41
Apr 29 14:19:22 duet3 DuetControlServer[414]: [debug] Updated key move
Apr 29 14:25:20 duet3 DuetControlServer[414]: [debug] IPC#34: Got new UNIX connection, checking permissions...
Apr 29 14:25:20 duet3 DuetControlServer[414]: [debug] IPC#34: Granting full DSF permissions to external plugin
Apr 29 14:25:20 duet3 DuetControlServer[414]: [debug] IPC#34: Command processor added
Apr 29 14:25:20 duet3 DuetControlServer[414]: [debug] IPC#34: Received command ResolvePath
Apr 29 14:25:20 duet3 DuetControlServer[414]: [debug] IPC#34: Connection closed

Form3DCP

This post is deleted!

Phaedrux

Your Pi is running 3.4 but the Duet is only running 3.3.

Have you tried running sudo apt update and sudo apt upgrade on the Pi yet? If so, it appears the firmware update on the Duet was not successfully applied. Try running the update again. If it still doesn't update when you send M115 to check then you'll need to manually initiate the update by sending M997 in the gcode console tab in DWC. If that still doesn't update the Duet3 firmware then you'd need to use the direct USB connection to a PC and use the Bossa software to flash it directly.

Form3DCP

@phaedrux

That worked! Just had to send M997, can't believe it was that simple. Thank you so much! I would've been scratching my head for days.