Automatic Emergency Stop
-
@sculpt-fabricator can you post an output of M122 after the reset?
also a sample file would be helpful -
9/13/2022, 6:59:40 AM m122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3 (2021-06-15 21:44:54) running on Duet WiFi 1.02 or later + DueX5
Board ID: 08DLM-996RU-N85T0-6J1D4-3SJ6K-TAVZR
Used output buffers: 3 of 24 (24 max)
=== RTOS ===
Static ram: 23876
Dynamic ram: 77308 of which 12 recycled
Never used RAM 10364, free system stack 132 words
Tasks: NETWORK(ready,14.2%,225) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,313) DUEX(notifyWait,0.0%,24) MAIN(running,85.7%,441) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:30:38 ago, cause: software
Last software reset at 2022-09-13 06:29, reason: User, GCodes spinning, available RAM 10364, slot 1
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x0c
Aux0 errors 0,1,0
Step timer max interval 0
MCU temperature: min 34.6, current 35.0, max 36.9
Supply voltage: min 22.7, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/14, heap memory allocated/used/recyclable 2048/246/16, gc cycles 0
Driver 0: position 0, standstill, SG min/max 0/0
Driver 1: position 57500, standstill, SG min/max 0/71
Driver 2: position 13866, standstill, SG min/max not available
Driver 3: position 0, standstill, SG min/max not available
Driver 4: position 0, standstill, SG min/max not available
Driver 5: position 0, standstill, SG min/max 0/0
Driver 6: position 0, standstill, SG min/max 0/278
Driver 7: position 0, standstill, SG min/max 0/339
Driver 8: position 0, standstill, SG min/max 0/321
Driver 9: position 0, standstill, SG min/max 0/283
Driver 10: position 0
Driver 11: position 0
Date/time: 2022-09-13 06:59:39
Cache data hit count 4294967295
Slowest loop: 10.52ms; fastest: 0.18ms
I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 20.0MBytes/sec
SD card longest read time 3.9ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, maxWait 3589ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 7, completed moves 7, 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, chamberHeaters = -1 -1 -1 -1
Heater 0 is on, I-accum = 0.2
=== GCodes ===
Segments left: 0
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
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
Daemon is idle in state(s) 0
Autopause is idle in state(s) 0
Code queue is empty.
=== Filament sensors ===
Extruder 0 sensor: no data received
Extruder 1 sensor: no data received
=== DueX ===
Read count 1, 0.03 reads/min
=== Network ===
Slowest loop: 82.42ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 2 of 8- WiFi -
Network state is active
WiFi module is connected to access point
Failed messages: pending 0, notready 0, noresp 0
WiFi firmware version 1.26
WiFi MAC address ec:fa:bc:5b:41:b9
WiFi Vcc 3.38, reset reason Turned on by main processor
WiFi flash size 4194304, free heap 24504
WiFi IP address 192.168.5.101
WiFi signal strength -64dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@sculpt-fabricator i would suggest upgrading to 3.4.1 and seeing if it happens again
-
Ok upgrades to 3.4.1
started a print, it made it 22 min into the print and it Emergency stopped=== Diagnostics === RepRapFirmware for Duet 2 WiFi/Ethernet version 3.4.1 (2022-06-01 21:05:28) running on Duet WiFi 1.02 or later + DueX5 Board ID: 08DLM-996RU-N85T0-6J1D4-3SJ6K-TAVZR Used output buffers: 10 of 26 (26 max) === RTOS === Static ram: 23860 Dynamic ram: 77116 of which 12 recycled Never used RAM 8236, free system stack 174 words Tasks: NETWORK(ready,13.2%,242) HEAT(notifyWait,0.0%,333) Move(notifyWait,0.0%,363) DUEX(notifyWait,0.0%,24) MAIN(running,86.3%,440) IDLE(ready,0.4%,30), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:03:14 ago, cause: software Last software reset at 2022-09-13 09:00, reason: User, GCodes spinning, available RAM 8236, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x04 Aux0 errors 0,0,0 Step timer max interval 0 MCU temperature: min 33.0, current 33.6, max 34.3 Supply voltage: min 23.9, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/14, heap memory allocated/used/recyclable 2048/230/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min n/a Driver 1: standstill, SG min n/a Driver 2: standstill, SG min n/a Driver 3: standstill, SG min n/a Driver 4: standstill, SG min n/a Driver 5: standstill, SG min n/a Driver 6: standstill, SG min n/a Driver 7: standstill, SG min n/a Driver 8: standstill, SG min n/a Driver 9: standstill, SG min n/a Driver 10: Driver 11: Date/time: 2022-09-13 09:03:54 Cache data hit count 4294967295 Slowest loop: 10.23ms; fastest: 0.20ms I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0 === Storage === Free file entries: 10 SD card 0 detected, interface speed: 20.0MBytes/sec SD card longest read time 3.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === AuxDDARing === Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1 === Heat === Bed heaters -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0 === GCodes === Segments left: 0 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 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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: no data received Extruder 1 sensor: no data received === DueX === Read count 1, 0.31 reads/min === Network === Slowest loop: 79.94ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 2 of 8 - WiFi - Network state is active WiFi module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address ec:fa:bc:5b:41:b9 WiFi Vcc 3.38, reset reason Turned on by main processor WiFi flash size 4194304, free heap 24944 WiFi IP address 192.168.5.101 WiFi signal strength -63dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@sculpt-fabricator can you upload the print file?
@dc42 any insight on the reset?
-
@jay_s_uk
I have tried three different print files one of them we printed yesterday. The other two are new files we have not printed. -
@sculpt-fabricator but can you upload a gcode file please
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@sculpt-fabricator oh, and also your config.g
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jay_s_uk
I can get you the step file If you want@dc24 I can reset it from the panel with the M999, rehome etc. and it back
to normal -
@sculpt-fabricator the step file is no use, which is why i have asked for the
gcode -
Config G -
; General preferences_________________________________________________________ G21 ; dimentions in mm G90 ; for X,Y,Z use absolute coordinate values M83 ; for E0,E1,etc use relative coordinate values M111 S0 ; Debug off M555 P2 ; Set output to look like Marlin M575 P0 B57600 S2 ; communication parameters for USB serial M575 P1 B57600 S1 ; Set auxiliary serial port baud rate and require checksum (for PanelDue) ; Network_____________________________________________________________________ M550 P"Big 60" ; set printer name M552 S1 ; enable (S1) networking (WiFi) M586 S1 P1 ;T0 ; enable (S1) FTP (P1) Disable TLS (T0) M586 S1 P2 ;T0 ; enable (S1) Telnet (P2) Disable TLS (T0) ; mode control variables _____________________________________________________ global g_probe_z_trigger = 1.752 ; default - set as appropriate for the Z probe global g_z_home = 5 ; can be used to always move Z to known height global g_z_datum_set = false ; can be used to prevent unneeded setting of Z=0 datum global g_map_mode = "300 point" ; determines which kind of height map is created/loaded global g_probe_mode = "two consecutive" ; determines if z proving used consecutive or averaging global g_level_mode = "4 point" ; determines if 3 or 4 points are used for leveling global g_print_beg_prime = 10 ; default - set desired in filament config.g global g_print_beg_retract = 0 ; default - set desired in filament config.g global g_print_end_retract = 0 ; default - set desired in filament config.g global g_print_end_mode = "heat off" ; determines if heaters are turned off when print is done ; Drives_________________________________________________________________________ ;Main board______________________________________________________________________ M569 P0 S0 ; Physical drive 0 . X1 M569 P1 S1 ; Physical drive 1 . X2 M569 P3 S0 ; Physical drive 3 . Main Extruder M569 P4 S0 ; Physical drive 4 . Secondary Extruder ;Duex5 board_____________________________________________________________________ M569 P5 S0 ; Physical drive 5 . Y M569 P6 S0 ; Physical drive 6 . Z1 (-188 , 656.5) M569 P7 S0 ; Physical drive 7 . Z2 (-188, -35.5) M569 P8 S0 ; Physical drive 8 . Z3 (658.6 , -35.5) M569 P9 S0 ; Physical drive 9 . Z4 (658.6, 656.5) ;Settings_________________________________________________________ M584 X0:1 Y5 Z6:7:8:9 E3:4 P3 ; Driver mapping ;___________________________________________________________________ M350 X16 Y16 I1 ; Configure microstepping with interpolation M350 Z16 E16:16 I0 ; Configure microstepping without interpolation M92 X100.00 Y100.00 Z2000.00 E425:300 ; Set steps per mm M566 X300 Y500 Z100.00 E120.00:120.00 P1 ; Set maximum instantaneous speed changes (mm/min) M203 X18000.00 Y18000.00 Z300.00 E1200.00:1200.00 ; Set maximum speeds (mm/min) M201 X1000 Y1000 Z120.00 E250.00:250.00 ; Set accelerations (mm/s^2) M204 P500 ; Set print and travel accelerations (mm/s^2) M906 X1800 Y1800.00 E1000:1000 I40 ; Set motor currents (mA) and motor idle factor in per cent (E1270 per dyze) M906 Z1800.00 I50 ; Set motor currents (mA) and motor idle factor in per cent M84 S100 ; Set idle timeout - 100 seconds ; Axis Limits M208 X0 Y0 Z-0.5 S1 ; set axis minima M208 X585 Y575 Z630 S0 ; set axis maxima 580;580 ; Endstops M574 X1 S1 P"xstop + e0stop" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin xstop M574 Y2 S1 P"ystop" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin ystop ; Z-Probe ;M558 P9 C"^zprobe.in" H5 F120 T6000 A1 R1 ; set Z probe type to bltouch and the dive height + speeds ;M950 S0 C"duex.pwm5" ; set probe pin M98 P"config_probe.g" M556 S50 X0 Y0 Z0 ; set orthogonal axis compensation parameters woher kommt der test wie wurde der Winkel bestimmt Unklar! M376 H20 ; stop z-leveling after 10 layers ; Heaters___________________________________________________________ M140 H-1 ; disable heated bed (overrides default heater mapping) ;E0_________________________________________________________________ M308 S0 P"spi.cs1" Y"rtd-max31865" A"Main Extruder" ; create sensor number 1 as a PT100 sensor in first position daughterboard M950 H0 C"e0heat" T0 ; create nozzle heater output on e0heat and map it to sensor 0 M307 H0 B0 R2.059 C461.5:461.5 D8.35 S1.00 V23.5 ; PID calibration ;M307 H0 B0 R6.167 C268.6:268.6 D4.07 S1.00 V23.5 M143 H0 S1400 ; set temperature limit for heater 0 to 450C ;E1_________________________________________________________________ M308 S1 P"spi.cs2" Y"rtd-max31865" A"Support Extruder" ; create sensor number 2 as a PT100 sensor in sec position daughterboard ;E4_________________________________________________________________ M308 S1 P"duex.e4temp" Y"thermistor" T100000 B4267 ; configure sensor 1 as thermistor on pin e1temp M950 H5 C"duex.e4heat" T1 ; create nozzle heater output on e4heat and map it to sensor 4 M143 H5 S120 ; set temperature limit for heater 1 to 120C ; Fans & LED___________________________________________________________ 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 on M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned on M950 F2 C"fan2" Q500 ; create air filter fan on fan 2 on pin fan2 and set its frequency M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned on M950 F7 C"!duex.fan7" Q500 ; create LED on pin fan7 and set its frequency M106 P7 S0 H-1 ; Disable fan channel for LED M106 P7 S255 ; remove ";" to set the LED to full brightness by default M950 F3 C"duex.fan3" Q500 ; create fan 3 on pin fan3 and set its frequency M106 P3 S1 H-1 ; set fan 3 value. Thermostatic control is turned on Bed relay to on ; Tools______________________________________________________________ ;T0_________________________________________________________________ M563 P0 S"E0 Main" D0 H0 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets G10 P0 R0 S265 ; set initial tool 0 active and standby temperatures to 0C ;T1_________________________________________________________________ M563 P1 S"E1 Support" D1 H1 F1 ; define tool 1 G10 P1 X0 Y65 Z0 ; set tool 1 axis offsets Y-2 moves filament 2mm to back of machine X-1 moves filament 1mm to the right G10 P1 R0 S265 ; set initial tool 1 active and standby temperatures to 0C ;T2____________________________________________________________________ ;T3___________________________________________________________________ M563 P3 S"CHAMBER TEMP" H5 G10 P3 R0 S40 ; Custom settings__________________________________________________ M950 J0 C"exp.e2stop" M581 T1 P0 S0 R1 M591 D0 P7 C"e1stop" S1 L4.2 E10 R10:1000 M950 J1 C"exp.e3stop" M581 T1 P1 S0 R1 M591 D1 P7 C"zstop" S1 L4.2 E10 R10:1000 ;M591 D0 P1 C"duex.e2stop" S1 ; Regular filament sensor for E0 ;M591 D1 P1 C"duex.e3stop" S1 ; Regular filament sensor for E1 M950 J2 C"duex.e4stop" ; create Input Pin 2 on Zstop for the M581 command. M581 P2 T0 S0 R0 ; Crash Detector [Add-On] M42 P2 S255 ; Start up air filter ; Automatic power saving____________________________________________ M911 S21 R29.0 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; Set voltage thresholds and actions to run on power loss. Power Failure Pause -
@sculpt-fabricator also, does it reset if you simulate the job?
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@sculpt-fabricator and have you always used global variables or have you only recently started to use them?
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
@jay_s_uk I have never run a job simulate. I don't know how to do that ?
-
@sculpt-fabricator right click on the job and simulate
Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is
-
I haven't changed any g-code or any setting in 4 months, printer was working
perfectly sense 3.3 update and getting all the code dialed in. Machine has been
running 24/7 for 4 weeks -
@jay_s_uk
It made it 100% thought simulation. -
@sculpt-fabricator not much we can do now until the reset map is looked at.
-
@sculpt-fabricator said in Automatic Emergency Stop:
Error status: 0x04
Error 0x04 = Output buffer starvation, I think. I'd guess that your SD card is either full or damaged. Please check your SD card by running the commands here: https://docs.duet3d.com/en/User_manual/RepRapFirmware/SD_card#troubleshooting-sd-card-issues
Ian
-
@droftarts
The SD card was really full we deleted everything out of it. I will look into
that more
