Duet3D/DuetSoftwareFramework

[Bug]: M32 breaks job state

Closed this issue · 0 comments

fragrama17 commented

Duet Forum Discussion Thread

https://forum.duet3d.com/topic/36750/bug-m32-breaks-job-state

Which Duet products are you using?

  • Duet2-Wifi
  • Duet2-Ethernet
  • Duet Expansion Breakout Board
  • Duex2
  • Duex5
  • Duet2-Maestro
  • Maestro Dual Driver Expansion
  • Duet3-6HC
  • Duet3-3HC
  • Duet3-1XD
  • Duet3-1LC
  • Duet3-Tool Distribution Board
  • Duet3-Mini5+
  • Duet3-Mini2+
  • Raspberry Pi or other SBC
  • SmartEffector
  • Magnetic Filament Sensor
  • Laser Filament Sensor
  • PT100 Daughterboard
  • Thermocouple Daughterboard
  • PanelDue
  • Other
  • None

Firmware Version

3.5.3

Duet Web Control Version

3.5.3

Are you using a Single Board Computer (RaspberryPi) with your Duet?

  • Yes I use a SBC.
  • No I do not use a SBC.

Please upload the results of sending M122 in the gcode console.

M122 Report

Please upload the content of your config.g file.

Config.g

Please upload the content of any other releveant macro files.

No response

Details specific to your printer.

No response

Links to additional info.

No response

What happened?

Expected result
M32 code fails because a file is already being printed

Observed result
M32 prints correct error message but sets new file for printing instead of doing nothing

Steps to reproduce

  1. pause current file
  2. run M32 "new-file.g"