Unable to make first print, Error: M32:

Rushmere3D

I would add a T0, to the end of your config.g. Depending on the slicer it might not be adding/selecting a tool at the start of the gcode file.

fcwilt

@burtonenator

What code do you execute at the start of a print?

Frederick

burtonenator

@rushmere3d

I do have a T0 in the Gcode, it doesn't seem to even matter where, I tried moving it to the beginning of the file, no change.

burtonenator

@fcwilt very simple beginning code on the gcode, but even if I have a completely empty gcode file and tell it to run, it gives the same "file is already being printed" error. I don't believe any of it being run at all.

G90
M82
M106 S0
M140 S60
M190 S60
M104 S190 T0
M109 S190 T0
G28 ; home all axes
G32
; process Process1
; layer 1, Z = 0.200
T0
G92 E0.0000
G1 E-1.0000 F1800

fcwilt

@burtonenator

What version of the firmware are you using?

Frederick

burtonenator

@fcwilt

Board: Duet 3 MB6HC (MB6HC)
DSF Version: 3.4.0
Firmware: RepRapFirmware for Duet 3 MB6HC 3.3 (2021-06-15)

I can now confirm it will print if I upload the Gcode as a Macro, just not as a "job"

fcwilt

@burtonenator

I am still using 3.3.0 so there may be a problem with 3.4.0 that I am not aware of.

Frederick

resam

@burtonenator just to sanity check: you are running RRF 3.3 but using DSF 3.4? I would recommend upgrading/downgrading to the same version for both - having such a mix might cause weird issues.

burtonenator

@resam
I did the update on the pi, is there more I should do, everything seems to imply all I have to do is:

sudo apt update
sudo apt upgrade

resam

@burtonenator yes, thats the usual way - but if your system is reporting two different versions for RRF and DSF, then something went wrong.

burtonenator

@resam

Yes!, that seems to be it I got the board to upgrade to 3.4 and now its accepting a file, thank you.

geon han_Kang

@resam

The same problem occurred to me.
Do you happen to know how to downgrade 3.4 to 3.3?
I don't know how to do it.

Phaedrux

@geon-han_kang In this case they had a mismatch between DSF version and Duet firmware version.

burtonenator

@geon-han_kang I had to upgrade the duet3 to 3.4, there is a script that can help you downgrade the DSF, but I didn't use it, I wanted something from 3.4 anyways.

https://github.com/DanalEstes/DuetVersions

geon han_Kang

@burtonenator
Thank you.
I try that