Print Stopping As 100% Complete When iPad Sleeps
Aaron_Nall last edited by Aaron_Nall
I just experienced a very strange phenomenon. I was printing a 30 layer file that was supposed to take ~25 minutes. I decided to hop in the shower and figured the print would be complete when I was done showering.
Well, when I woke up the iPad (from it's sleep state) that I was using to monitor the web interface, the interface reported that the print was complete. However, the print head had stopped at the location I assume it was in when the iPad went to sleep. There was no return to home. The extrusion continued briefly until the extruder chamber pressure equalized with the atmosphere, so there was a small button of material that the nozzle was seated in. The heaters shut off. The print stopped on layer 14. I counted the layers with a viewing loop.
What would ever cause the Duet 2 Wifi board to halt all operation and report the print was completed aside from reaching the end of the gcode file that's on the card?
This is the third or fourth time I have had this issue and I assumed it was related to bad gcode file export from the slicer, but in the file the code clearly continues past layer 14. So, maybe there is a bug where sleep causes an emergency stop and reports print complete?
Any insight would be great, and appreciated.
Were you able to get the results of M122 after it had stopped before rebooting?
Can you tell us what firmware version and DWC version you are using?
Also post your config.g
Yes, with no success in tracing a cause. As well as reading a thread from 2018 with same event description, and following the suggestion to use M122 to debug any apparent actual problem, there was no reset event or any red flag information that would explain the event in M122 data. Last reset was 4 hours prior noted as startup. I will run several tests on a small print tomorrow to see if I can reliably create a circumstance that repeats the false finish event, but so far all investigation points to random bug of some sort that isn't producing an error.
Aaron_Nall last edited by Aaron_Nall
This post is deleted!
The web interface is whatever comes inside Duet2and3Firmware-3.1.1.zip as that's the package I used to install the latest firmware that I could find.
FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet WiFi 1.02 or later FIRMWARE_DATE: 2020-05-19b2
; Configuration file for Duet WiFi (firmware version 3) ; executed by the firmware on start-up ; ; generated by RepRapFirmware Configuration Tool v3.1.3 on Tue Jun 23 2020 15:03:13 GMT-0700 (Pacific Daylight Time) ; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Ender 3 Modified Monster" ; set printer name M918 P1 E4 F2000000 ; configure direct-connect display ; Network M551 P"xxxxxx" ; set password M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0 S1 ; physical drive 0 (X) goes forwards M569 P1 S0 ; physical drive 1 (Y) goes backwards M569 P2 S1 ; physical drive 2 (Z) goes forwards M569 P3 S1 ; physical drive 3 (E0) goes forwards M584 X0 Y1 Z2 E3 ; set drive mapping M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E93.00 ; set steps per mm M566 X1200.00 Y1200.00 Z24.00 E300.00 ; set maximum instantaneous speed changes (mm/min) M203 X9000.00 Y9000.00 Z180.00 E6000.00 ; set maximum speeds (mm/min) M201 X500.00 Y500.00 Z100.00 E5000.00 ; set accelerations (mm/s^2) M906 X500 Y500 Z500 E700 I50 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 X0 Y-12 Z0 S1 ; set axis minima M208 X235 Y220 Z250 S0 ; set axis maxima ; Endstops M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop M574 Z1 S1 P"zstop" ; configure active-high endstop for low end on Z via pin zstop ; Z-Probe M558 P0 H5 F120 T6000 ; disable Z probe but set dive height, probe speed and travel speed M557 X15:200 Y15:200 S20 ; define mesh grid ; Heaters M308 S0 P"bedtemp" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 B1 S1.00 ; enable bang-bang mode for the bed heater and set PWM limit M140 H0 ; map heated bed to heater 0 M143 H0 S550 ; set temperature limit for heater 0 to 550C M308 S1 P"e0temp" Y"thermistor" T100000 B3950 R4700 ;C1.739356e-7 configure sensor 1 as thermistor on pin e0temp M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit ; Fans M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create fan 2 on pin fan2 and set its frequency M106 P2 S1 H1:0 T45 ; set fan 2 value. Thermostatic control is turned on ; Tools M563 P0 S"Extruder 1" 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 M143 H1 S550 ; Miscellaneous M912 P0 S-11.5 M501 ; load saved parameters from non-volatile memory M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
I've been trying to replicate the event all day by letting the iPad sleep at 2 min intervals. So far not getting a repeat. I even tried logging in on Windows 10 and letting them both fall asleep.
You can check the DWC (Duet Web Control, i.e. the web interface) version in the settings tab. Just want to make sure you're on 3.1.1 to match the firmware.
If it does fail a print again try to get a M122 result as soon as you can and post it here, that may give a clue about what happened. Without that it's quite hard to say.