3.4.0 Beta6 Crash Detection Problems
-
Hello I have issues with the crash detection in firmeware 3.4.0 Beta6.
Duet3-6HC + 2x Duet3-3HC
3.4.0 beta6 / Duet Web Control 3.4.0-b2
Standalone(The printer type is unusual, so the Axis have unusual Names)
When I configure the detection with M915 V W X Y S4 R3 or M915 P0.1:0.3:0.4:0.5 S4 R3 it does not work at all (tryed S5 to S-50).
It did work fine till firmeware 3.3.
Did I configure something wrong or is this a Bug?Gcode:
G28 M915 P0.1:0.3:0.4:0.5 S4 R3 G1 F30000 G1 Z20.000000 ;LAXER_COUNT:11 ;LAXER:0 G1 X0 G1 X130 G1 X0 G1 X130...
config:
G90 M83 M550 P"3D_HRD" ; Network M552 P192.168.1.112 S1 M586 P0 S1 M586 P1 S0 M586 P2 S0 ; Drives M569 P0.0 S0 M569 P0.1 S1 M569 P0.2 S0 M569 P0.3 S1 M569 P0.4 S1 M569 P0.5 S1 M569 P2.0 S1 M569 P2.1 S1 M569 P1.2 S1 M569 P2.2 S1 M584 V0.3 W0.4 X0.5 Y0.1 Z0.0 A0.2 R0 S0 E1.2:2.0:2.1:2.2 ; set drive mapping M350 V16 W16 X16 Y16 Z16 A16 E8:8:8:8 I1 ; configure microstepping with interpolation M92 V80.00 W80.00 X80.00 Y80.00 Z800.00 A44.00 E201.87:201.87:201.87:201.87 ; set steps per mm M566 V500.00 W500.00 X500.00 Y500.00 Z12.00 A100.00 E200.00:2000.00:2000.00:2000.00 ; set maximum instantaneous speed changes (mm/min) M203 V5000.00 W5000.00 X5000.00 Y5000.00 Z1000.00 A20000.00 E1000.00:1000.00:1000.00:1000.00 ; set maximum speeds (mm/min) M201 V500.00 W500.00 X500.00 Y500.00 Z100.00 A1000.00 E500.00:500.00:500.00:500.00 ; set accelerations (mm/s^2) M906 V1500 W1500 X1500 Y1500 Z2000 A2500 E1500:1500:1500:1500 I30 ; set motor currents (mA) and motor idle factor in per cent M84 S30 ; Set idle timeout ; Axis Limits M208 V0 W30 X0 Y30 Z0 A0 S1 ; set axis minima M208 V145.1 W145.9 X144.4 Y146.3 Z250 A1000000000 S0 ; set axis maxima ; Endstops M574 V2 S1 P"!io4.in" M574 W2 S1 P"!io5.in" M574 X2 S1 P"!io2.in" M574 Y2 S1 P"!io0.in" M574 Z1 S1 P"!io1.in" ; Filamentsensoren M591 D0 P1 C"1.io2.in" S1 M591 D1 P1 C"2.io1.in" S1 M591 D2 P1 C"2.io2.in" S1 M591 D3 P1 C"2.io3.in" S1 ; Heaters M308 S0 P"temp2" Y"pt1000" M950 H0 C"out0" T0 M307 H0 R0.300 C323.4 D16.35 S1.00 V24.0 M140 H0 M143 H0 S120 M308 S1 P"temp0" Y"thermistor" T100000 B4725 C7.06e-8 M950 H1 C"out1" T1 M307 H1 B0 S1.00 M308 S2 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 M950 H2 C"out2" T2 M307 H2 B0 S1.00 M308 S3 P"1.temp0" Y"thermistor" T100000 B4725 C7.06e-8 M950 H3 C"1.out0" T3 M307 H3 B0 S1.00 M308 S4 P"1.temp1" Y"thermistor" T100000 B4725 C7.06e-8 M950 H4 C"1.out1" T4 M307 H4 B0 S1.00 ; Fans M950 F0 C"out9" ;M106 P0 C"Filament0" S1.0 H1 T50 M950 F1 C"out4" M106 P1 C"Kuehler0" S1.0 H1 T50 M950 F2 C"out8" ;M106 P2 C"Filament1" S1.0 H2 T50 M950 F3 C"out7" M106 P3 C"Kuehler1" S1.0 H2 T50 M950 F4 C"1.out7" ;M106 P4 C"Filament2" S1.0 H3 T50 M950 F5 C"1.out6" M106 P5 C"Kuehler2" S1.0 H3 T50 M950 F6 C"1.out8" ;M106 P6 C"Filament3" S1.0 H4 T50 M950 F7 C"1.out3" M106 P7 C"Kuehler3" S1.0 H4 T50 M950 F8 C"2.out0" ;Motorkuehler ; Tools M563 P0 S"0" D0 H1 F0 ; define tool 0 G10 P0 V0 W0 X0 Y0 Z0 A0 ; set tool 0 axis offsets G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C M563 P1 S"1" D1 H2 F0 ; define tool 1 G10 P1 V0 W0 X0 Y0 Z0 A0 ; set tool 1 axis offsets G10 P1 R0 S0 ; set initial tool 1 active and standby temperatures to 0C M563 P2 S"2" D2 H3 F0 ; define tool 2 G10 P2 V0 W0 X0 Y0 Z0 A0 ; set tool 2 axis offsets G10 P2 R0 S0 ; set initial tool 2 active and standby temperatures to 0C M563 P3 S"3" D3 H4 F0 ; define tool 3 G10 P3 V0 W0 X0 Y0 Z0 A0 ; set tool 3 axis offsets G10 P3 R0 S0 ; set initial tool 3 active and standby temperatures to 0C M563 P4 S"Alle" D0:1:2:3 H0:1:2:3:4 F0 ; define tool 4 G10 P4 V0 W0 X0 Y0 Z0 A0 ; set tool 4 axis offsets G10 P4 R0 S60:250:250:220:250 ; set initial tool 4 active and standby temperatures to 0C ;M568 P4 S1 ; enable mixing for tool 4 M567 P4 E1:1:1:1 M563 P5 S"Alle ohne Heatbed" D0:1:2:3 H1:2:3:4 F0 ; define tool 4 G10 P5 V0 W0 X0 Y0 Z0 A0 ; set tool 4 axis offsets G10 P5 R0 S250:250:220:250 ; set initial tool 4 active and standby temperatures to 0C ;M568 P4 S1 ; enable mixing for tool 4 M567 P5 E1:1:1:1; set mixing ratios for tool 4M122:
M122 B1 Diagnostics for board 1: Duet EXP3HC firmware version 3.4.0beta6 (2021-11-06 11:55:50) Bootloader ID: not available Never used RAM 158012, free system stack 4406 words Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,106) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.6%,99) MAIN(running,91.0%,332) IDLE(ready,0.0%,39) AIN(delaying,1.4%,263), total 100.0% Last reset 00:00:20 ago, cause: software Last software reset data not available Driver 0: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 14151, writes 11 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 14151, writes 11 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 201.9 steps/mm,standstill, SG min 0, mspos 16, reads 14147, writes 16 timeouts 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter -1/6, peak Rx sync delay 176, resyncs 0/0, no step interrupt scheduled VIN voltage: min 24.1, current 24.1, max 24.2 V12 voltage: min 12.1, current 12.1, max 12.1 MCU temperature: min 33.8C, current 33.8C, max 33.8C Last sensors broadcast 0x00000018 found 2 57 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 456, send timeouts 0, received 211, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 === Filament sensors === Interrupt 5726621 to 0us, poll 1 to 152us Driver 2: ok 22.11.2021, 12:44:46 M122 B2 Diagnostics for board 2: Duet EXP3HC firmware version 3.4.0beta6 (2021-11-06 11:55:50) Bootloader ID: not available Never used RAM 158716, free system stack 4402 words Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,106) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.6%,99) MAIN(running,91.0%,442) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0% Last reset 00:00:18 ago, cause: software Last software reset at 2021-05-03 17:21, reason: AssertionFailed, available RAM 158940, slot 1 Software reset code 0x0120 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00430000 BFAR 0xe000ed38 SP 0x2000378c Task MAIN Freestk 795 ok Stack: 00000544 0002eb3c 0002614f 42000400 00022387 20001c90 00000001 00000003 20001c8c 20001c7c 0001d30f 00000001 200037e0 00000001 000190a7 3a36d584 41200000 00000000 00026043 20000010 00000001 00000000 11a80200 00000024 a300a5a5 20003c78 00000001 Driver 0: pos 0, 201.9 steps/mm,standstill, SG min 0, mspos 16, reads 4692, writes 16 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 201.9 steps/mm,standstill, SG min 0, mspos 16, reads 4693, writes 16 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 201.9 steps/mm,standstill, SG min 0, mspos 16, reads 4694, writes 16 timeouts 0, steps req 0 done 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0 Peak sync jitter -1/10, peak Rx sync delay 175, resyncs 0/0, no step interrupt scheduled VIN voltage: min 24.3, current 24.3, max 24.4 V12 voltage: min 12.2, current 12.2, max 12.2 MCU temperature: min 33.0C, current 33.0C, max 33.2C Last sensors broadcast 0x00000000 found 0 85 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 273, send timeouts 0, received 254, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 === Filament sensors === Interrupt 5726621 to 0us, poll 1 to 113us Driver 0: ok Driver 1: ok Driver 2: ok 22.11.2021, 12:44:41 M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.0beta6 (2021-11-06 11:38:57) running on Duet 3 MB6HC v0.6 or 1.0 (standalone mode) Board ID: 08DJM-956L2-G43S4-6JTD8-3SS6J-9B7GH Used output buffers: 1 of 40 (21 max) === RTOS === Static ram: 151136 Dynamic ram: 99160 of which 0 recycled Never used RAM 100376, free system stack 200 words Tasks: NETWORK(ready,24.5%,263) ETHERNET(notifyWait,0.1%,174) HEAT(notifyWait,0.0%,320) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,903) CanSender(notifyWait,0.0%,373) CanClock(delaying,0.0%,349) TMC(notifyWait,7.3%,92) MAIN(running,60.6%,1115) IDLE(ready,7.5%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:00:13 ago, cause: software Last software reset at 2021-11-22 12:44, reason: User, GCodes spinning, available RAM 100332, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 125 MCU temperature: min 44.3, current 44.4, max 44.7 Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 12.1, current 12.2, max 12.3, under voltage events: 0 Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0 Driver 0: pos 0, standstill, SG min 0, mspos 392, reads 12167, writes 14 timeouts 0 Driver 1: pos 0, standstill, SG min 0, mspos 376, reads 12166, writes 15 timeouts 0 Driver 2: pos 0, standstill, SG min 0, mspos 8, reads 12167, writes 14 timeouts 0 Driver 3: pos 0, standstill, SG min 0, mspos 136, reads 12166, writes 15 timeouts 0 Driver 4: pos 0, standstill, SG min 0, mspos 760, reads 12166, writes 15 timeouts 0 Driver 5: pos 0, standstill, SG min 0, mspos 264, reads 12167, writes 15 timeouts 0 Date/time: 2021-11-22 12:44:41 Slowest loop: 4.75ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 3.0ms, write time 0.0ms, max retries 0 === Move === DMs created 125, 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 0 -1 -1 -1 -1 -1 -1 -1 -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 SBC is idle in state(s) 0 Daemon is idle in state(s) 0 Aux2 is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty === Filament sensors === Extruder 0 sensor: no filament Extruder 1 sensor: no filament Extruder 2 sensor: no filament Extruder 3 sensor: no filament === CAN === Messages queued 158, received 478, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 5, free buffers 49 (min 48), ts 70/69/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 3.41ms; fastest: 0.02ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions HTTP sessions: 1 of 8 - Ethernet - State: active Error counts: 0 0 1 0 0 Socket states: 5 2 2 2 2 0 0 0 -
@vali3d there was an issue with the stall detection sensitivity that was fixed in b6 for the stepper drivers on the 6HC and 3HC,
Sending M915 with no parameters, does that report the correct settings for those axis?
if you switch back to 3.3 does stall detection works again?
-
@T3P3Tony
M915 is correct. If I switch back ,the stall detection works. I have read about the Problems with b5, so I used the b6.Driver 0.0: stall threshold 1, filter off, steps/sec 200 (4.0 mm/sec), coolstep threshold 234 (4.0 mm/sec), action on stall: none Driver 0.1: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: rehome Driver 0.2: stall threshold 1, filter off, steps/sec 200 (72.7 mm/sec), coolstep threshold 234 (72.8 mm/sec), action on stall: none Driver 0.3: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: rehome Driver 0.4: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: rehome Driver 0.5: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: rehome -
@vali3d which element of the stall detection is not working? if you switch it to pause or log on stall detection does that work? Alos does stall detection work for endstop detection - that is the more common use case so maybe that those having issues before saw that fixed on b6 but using it for rehome is less widely tested.
-
@t3p3tony nothing working
. I switched between log and pause, no response/pause. Then I configured one axis by M915 X R0 F0 and M574 X2 S3 to home by stall detecion, the motor stalled but ist was not detectet. -
@vali3d stall homing is working on my machine using Duet 3 and RRF 3.4beta series, however I have found a reason why stall detection may not be working other than for homing. I will fix this in the next 3.4beta build.
-
@vali3d please try RRF 3.4.0beta7+6 which you can find at https://www.dropbox.com/sh/i5vox3xmkd55gaz/AAC19mI0WEC5GmEjLOBRbKs-a?dl=0. Ignore the .map files. This should fix stall detection when not homing. Stall homing on the MB6HC has been working throughout the 3.4beta series although at one point the sensitivity changed (and was subsequently reverted).
Caution, this is not an official beta release, so be ready to turn off power if something unexpected happens.
-
@dc42 it didn´t fix the rehoming, but I found somting interesting. I experimeted with the R parameter an it does won´t accept R2 or R3. This is the firmeware you gave me.
17.1.2022, 14:27:37 M915 Driver 0.0: stall threshold 1, filter off, steps/sec 200 (4.0 mm/sec), coolstep threshold 234 (4.0 mm/sec), action on stall: none Driver 0.1: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log Driver 0.2: stall threshold 1, filter off, steps/sec 200 (72.7 mm/sec), coolstep threshold 234 (72.8 mm/sec), action on stall: none Driver 0.3: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log Driver 0.4: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log Driver 0.5: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: log 17.1.2022, 14:27:32 M915 V W X Y S4 R1 17.1.2022, 14:27:23 M915 Driver 0.0: stall threshold 1, filter off, steps/sec 200 (4.0 mm/sec), coolstep threshold 234 (4.0 mm/sec), action on stall: none Driver 0.1: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none Driver 0.2: stall threshold 1, filter off, steps/sec 200 (72.7 mm/sec), coolstep threshold 234 (72.8 mm/sec), action on stall: none Driver 0.3: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none Driver 0.4: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none Driver 0.5: stall threshold 4, filter off, steps/sec 200 (40.0 mm/sec), coolstep threshold 234 (40.1 mm/sec), action on stall: none 17.1.2022, 14:27:17 M915 V W X Y S4 R3When it is configured to R1 log, it does log a crash.
On 3.3 I can configure it to rehome. -
undefined vali3d referenced this topic 11 Feb 2022, 10:47
-
@vali3d closing this because it has been fixed in 3.4.0rc2.
-
undefined dc42 marked this topic as a question 4 Mar 2022, 09:21
-
undefined dc42 has marked this topic as solved 4 Mar 2022, 09:21
