Random stop mid-print
camason last edited by
I'm having an intermittent issue which I'm struggling to diagnose. It has happened randomly over the past few weeks.
The printer will suddenly stop moving, the web interface disconnects, and the BLTouch sensor deploys (hitting the part a couple of times, and then flashing red as it can't extend fully). The fans all remain on. It's as if an emergency-stop was triggered.
There seems to be nothing specific I can do to replicate it. I have to power-cycle the printer to get a connection.
I tried to run M122 but accidentally typed M112 first, so unsure if this diagnostic output is correct. I have not yet attempted updating firmware / web interface. I've only started experiencing this problem recently (past few weeks).
=== Diagnostics === Used output buffers: 3 of 32 (23 max) === Platform === RepRapFirmware for Duet 2 WiFi/Ethernet version 1.21 running on Duet WiFi 1.02 or later Board ID: 08DDM-9FAM2-LW4S4-6J9D6-3SD6J-12S7X Static ram used: 16152 Dynamic ram used: 100408 Recycled dynamic ram: 2224 Stack ram used: 1224 current, 4512 maximum Never used ram: 7776 Last reset 00:00:28 ago, cause: power up Last software reset at 2018-11-27 14:44, reason: User, spinning module GCodes, available RAM 7888 bytes (slot 0) Software reset code 0x0003 HFSR 0x00000000, CFSR 0x00000000, ICSR 0x0441f000, BFAR 0xe000ed38, SP 0xffffffff Error status: 0 Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest block write time: 0.0ms MCU temperature: min 35.2, current 35.4, max 35.7 Supply voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0, over voltage events: 0 Driver 0: standstill, SG min/max not available Driver 1: standstill, SG min/max not available Driver 2: standstill, SG min/max not available Driver 3: standstill, SG min/max not available Driver 4: standstill, SG min/max not available Date/time: 2018-12-07 10:00:25 Slowest main loop (seconds): 0.172815; fastest: 0.000112 === Move === MaxReps: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm 240, MaxWait: 0ms, Underruns: 0, 0 Scheduled moves: 0, completed moves: 0 Bed compensation in use: mesh Bed probe heights: 0.000 0.000 0.000 0.000 0.000 === Heat === Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 === GCodes === Segments left: 0 Stack records: 1 allocated, 0 in use Movement lock held by null http is idle in state(s) 0 telnet is idle in state(s) 0 file is idle in state(s) 0 serial is idle in state(s) 0 aux is idle in state(s) 0 daemon is idle in state(s) 0 queue is idle in state(s) 0 autopause is idle in state(s) 0 Code queue is empty. === Network === Responder states: HTTP(1) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0) HTTP sessions: 1 of 8 - WiFi - Network state is running WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.21 WiFi MAC address 60:01:94:73:61:88 WiFi Vcc 3.29, reset reason Turned on by main processor WiFi flash size 4194304, free heap 15992 WiFi IP address 192.168.0.18 WiFi signal strength -36dBm, reconnections 0, sleep mode modem Socket states: 2 0 0 0 0 0 0 0 === Expansion ===
dc42 administrators last edited by
I suggest you upgrade the firmware to version 2.01. If it happens again, run M122 again without resetting the printer or running M122 first.
camason last edited by
I may have found the culprit - a loose connector on the 230v in supply (mid-cable connector).
I'll re-wire and also update firmware.