Steeper over heater waring unable to emergency stop
-
@phaedrux
If i change to spread cycle, wont that stop the sensorless homing working? -
what do these numbers mean " SG min 14" in the M122 under Driver
-
Voltage OK : 23.9
4/23/2022, 7:32:13 PM Leadscrew adjustments made: -1.753 -2.356 2.344, points used 3, (mean, deviation) before (-0.607, 2.099) after (0.000, 0.000)Voltage OK : 23.9
4/23/2022, 7:31:56 PM Error: Driver 0.4 error: over temperature shutdown
4/23/2022, 7:31:55 PM Error: Driver 0.4 error: over temperature shutdown
4/23/2022, 7:31:53 PM Error: Driver 0.4 error: over temperature shutdown
4/23/2022, 7:31:49 PM Error: Driver 0.4 error: over temperature shutdown
4/23/2022, 7:31:29 PM G28
Warning: Driver 0.4 warning: over temperature warning
4/23/2022, 7:30:59 PM Emergency stop, attemping to reconnect...
4/23/2022, 7:30:50 PM Connection established
4/23/2022, 7:30:43 PM Connection interrupted, attempting to reconnect...
4/23/2022, 7:30:34 PM Emergency stop, attemping to reconnect...and here is the M122 after the above issue
4/23/2022, 7:34:59 PM M122
=== Diagnostics ===
RepRapFirmware for Duet 3 Mini 5+ version 3.4.0 (2022-03-15 18:59:15) running on Duet 3 Mini5plus WiFi (standalone mode)
Board ID: 3R9YY-6T9RL-D65J0-40KMN-2UW2Z-RHYT0
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 103684
Dynamic ram: 111008 of which 12 recycled
Never used RAM 24008, free system stack 132 words
Tasks: NETWORK(ready,14.9%,258) HEAT(notifyWait,0.0%,340) Move(notifyWait,0.0%,292) CanReceiv(notifyWait,0.0%,942) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,337) TMC(notifyWait,1.1%,114) MAIN(running,83.0%,428) IDLE(ready,0.1%,29) AIN(delaying,0.8%,264), total 100.0%
Owned mutexes: WiFi(NETWORK)
=== Platform ===
Last reset 00:03:58 ago, cause: software
Last software reset at 2022-04-23 19:30, reason: User, GCodes spinning, available RAM 24368, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
MCU revision 3, ADC conversions started 239108, completed 239108, timed out 0, errs 0
Step timer max interval 751
MCU temperature: min 30.4, current 33.1, max 37.5
Supply voltage: min 23.8, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/216/216, gc cycles 0
Events: 5 queued, 5 completed
Driver 0: standstill, SG min 14, read errors 0, write errors 1, ifcnt 117, reads 21655, writes 18, timeouts 0, DMA errors 0, CC errors 0
Driver 1: standstill, SG min 12, read errors 0, write errors 1, ifcnt 128, reads 21653, writes 20, timeouts 0, DMA errors 0, CC errors 0
Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 69, reads 21664, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 69, reads 21663, writes 9, timeouts 0, DMA errors 0, CC errors 0
Driver 4: standstill, SG min 14, read errors 0, write errors 1, ifcnt 99, reads 21659, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 5: standstill, SG min 16, read errors 0, write errors 1, ifcnt 99, reads 21659, writes 14, timeouts 0, DMA errors 0, CC errors 0
Driver 6: standstill, SG min 14, read errors 0, write errors 1, ifcnt 99, reads 21658, writes 14, timeouts 0, DMA errors 0, CC errors 0
Date/time: 2022-04-23 19:34:58
Cache data hit count 431811813
Slowest loop: 7.18ms; fastest: 0.07ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 22.5MBytes/sec
SD card longest read time 1.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 6, maxWait 30432ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 33, completed 33, 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, chamber heaters 2 -1 -1 -1, ordering errs 0
Heater 1 is on, I-accum = 0.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
=== CAN ===
Messages queued 2147, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 18 (min 18), ts 1194/0/0
Tx timeouts 0,0,1193,0,0,952 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 17.11ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
HTTP sessions: 1 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.25
WiFi MAC address f0:08:d1:02:a1:0b
WiFi Vcc 3.34, reset reason Power up
WiFi flash size 2097152, free heap 25512
WiFi IP address 192.168.0.19
WiFi signal strength -57dBm, mode 802.11n, reconnections 0, sleep mode modem
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0
- WiFi -
-
@moth4017 said in Steeper over heater waring unable to emergency stop:
i could not access the "emergency stop " button to stop printer crashing into the extruder
Could you provide a little more detail about the above statement? What control interface are you using (DWC? On a desktop or mobile?), what was it that was stopping you from pressing the emergency stop button? There may be two problems here, the first being the overtemp error, the second a possible problem with the user interface. It would be nice to understand both issues.
-
Hi problem 1
DWC desktop Pc.
Core XY
so the error messages were coming up in DWC " Driver 0.5 error: over temperature shutdown" while the error messages were popping up the motors were still moving and crashing into the end stops while all the error messages were popping up i could not click on the "Emergency stop" button.Also if i check the temperature of the Nema 17 and also the Drivers on the Duets + mini 5 they were only just warm
-
Sorry I missed that you are trying to use sensorless homing on multiple Z motors.
Does normal homing work?
Is the 3zhome macro the same as what you use for homeall/homez?
What do you have in bed.g?Do you get the over temp warnings immediately at startup or only when trying to do the auto leveling?
-
@phaedrux
using the homing buttons in DWC always work fine ,Home all from DWC has issues when there has been a previous "Driver 0.5 error: over temperature shutdown" as when you do a home all the homing direction of X or Y ( which ever i choose to be first) goes in the opposite direction to what it should do ( if set to home High it will try to home in the low direction)
3Zhome macro only used to set bed to Z max for pre setup.
the Driver 0.5 error: over temperature shutdown" either homing all or doing a bed mesh leveling.
; bed.g
; called to perform automatic bed compensation via G32
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Thu Dec 30 2021 11:07:38 GMT+1300 (New Zealand Daylight Time)
M561 ; clear any bed transform
G29 ; probe the bed and enable compensation
G28 ; home
G1 H2 Z25 F12000 ; lower Z again
;M401 ; deploy Z probe (omit if using bltouch)
G30 P0 X20 Y0 Z-99999 ; probe near a leadscrew
G1 H2 Z25 F12000
G30 P1 X270 Y0 Z-99999 ; probe near a leadscrew
G1 H2 Z25 F12000
G30 P2 X125 Y250 Z-99999 S3 ; probe near a leadscrew and calibrate 3 motors
G1 H2 Z25 F12000
;M402 ; retract probe (omit if using bltouch);The value of the S parameter on the final G30 command in bed.g must equal the number of Z motors.
Note just an update , ive just had the home in the wrong direction without the error?
Also noticed that when i do true bed leveling (G32) from the drop down options , the first Z movement a 0,0 the stepper motor sounds "harsh" the next measurement point (60,0) the stepper motor is quite again .
and throws these errors
4/24/2022, 11:47:48 AM Warning: Driver 0.6 warning: over temperature warning
4/24/2022, 11:47:47 AM Warning: Driver 0.6 warning: over temperature warning
4/24/2022, 11:47:46 AM Error: Driver 0.4 error: over temperature shutdown
4/24/2022, 11:47:44 AM Warning: Driver 0.6 warning: over temperature warning
4/24/2022, 11:47:44 AM Warning: Driver 0.5 warning: over temperature warning
4/24/2022, 11:47:43 AM G32
Warning: Driver 0.4 warning: over temperature warning -
@dc42 @Phaedrux @alankilian @gloomyandy
Thanks for all your help, i have now found a solution so i hope it help others
Duet 3 + mini 5 , core x y with 4:1 gearbox on the Z axis.; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"Valkyrie 3030 V002" ; set printer name M669 K1 ; core xy ; Network M552 S1 ; enable network M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; Drives M569 P0.0 S1 D2 ; physical drive 0 goes forwards M569 P0.1 S1 D2 ; physical drive 1 goes forwards M569 P0.2 S1 ; physical drive 2 goes forwards ( blown needs replacing) M569 P0.3 S1 ; physical drive 3 goes forwards (extruder M569 P0.4 S1 D2 ; physical drive 4 goes forwards D3=stealthchop M569 P0.5 S0 D2 ; physical drive 5 goes backwards M569 P0.6 S1 D2 ; physical drive 6 goes forwards M584 X1 Y0 E3 Z0.4:0.5:0.6 ; set drive mapping FL,FR,RC M350 X16 Y16 I1 ; configure microstepping with interpolation M350 Z16 E16 I1 M92 X80.00 Y80.00 Z320.00 E260.00 ; set steps per m M566 X500.00 Y500.00 Z100.00 E100.00 P1 ; set maximum instantaneous speed changes (mm/min) jerk M203 X24000.00 Y24000.00 Z4000.00 E400.00 ; set maximum speeds (mm/min) M201 X1000.00 Y1000.00 Z100.00 E250.00 ; set accelerations (mm/s^2) M906 X1000 Y1000 Z500 E600 I10 ; set motor currents (mA) and motor idle factor in per cent M84 S20 ; Set idle timeout ; Axis Limits M208 X-20 Y-11 Z0 S1 ; set axis minima "Travel Area" M208 X300 Y300 Z405 S0 ; set axis maxima "Travel area" ; Endstops M574 X1 S4 ; configure sensorless endstop, 1 = low end, 2 = high end. S4 multipule motors M574 Y2 S4 ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io1.in M574 Z2 S4 ; configure sensorless endstop for high end on Z, 1 = low end, 2 = high end. S4 multipule motors M671 X-20:300:150 Y0:0:280 S25 ; leadscrews at front left,front right, rear Center s= max correction factor must be in same order as M584 M558 P8 C"!io3.in" H10 F600 T12000 R0 A4 S0.03 ; set Z probe type to unmodulated and the dive height + speeds G31 P500 Z0.6 ; set Z probe trigger value, offset and trigger height bigger the posative number the closer to the bed G31 P500 X27 Y-11 ; set x,y trigger value, offset and trigger height M557 X10:290 Y10:290 S90 ; define mesh grid ; Heaters M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed T °C" ; configure sensor 0 as thermistor on pin bedtemp M950 H0 C"out0" T0 Q10 ; create bed heater output on bedheat and map it to sensor 0 M307 H0 R0.140 K0.103:0.000 D43.19 E1.35 S0.90 B0 ; PDI info for 8mm aluminium bed 700w Heater NTC 100K 3950 M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C M308 S1 P"temp1" Y"thermistor" T100000 B4267 A"Extruder T °C" ; configure sensor 1 as thermistor on pin e0temp (104gt2) M950 H1 C"out1" T1 ; create nozzle heater output on e0heat and map it to sensor 1 M307 H1 R3.435 K0.348:0.274 D6.64 E1.35 S1.00 B0 V23.9 ; disable bang-bang mode for heater and set PWM limit M143 H1 S280 ; set temperature limit for heater 1 to 280C ; Custom code ;M308 S2 P"temp2" Y"thermistor" T300000 B4562 A"Chamber T °C" ; configure sensor 1 as thermistor on pin e0temp (104gt2) M308 S2 P"temp2" Y"thermistor" T100000 B4138 A"Chamber T °C" ; configure sensor 2 as thermistor on pin temp2 M950 H2 C"out5" T2 ; create chamber heater output on 1.out0 and map it to sensor 2 M307 H2 B0 S1.00 ; disable bang-bang mode for the chamber heater and set PWM limit M141 H2 ; map chamber to heater 2 M143 H2 S100 ; set temperature limit for heater 2 to 280C M950 F0 C"out4" Q500 C"Part Fan" ; 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"out3" Q500 C"Extruder Fan" ; create fan 1 on pin fan1 and set its frequency M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on ; Tools M563 P0 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 T0 ; Custom settings are not defined ;M98 P"/macros/home_max_Z";; homex.g M400 ; make sure everything has stopped before we make changes G91 ; relative positioning M569 P0.0 S1 D3 V10 ; set to stelth chop M569 P0.1 S1 D3 V10 ; set to stelth chop M915 P0.0:0.1 S1 F0 R1 H200 ; Configure Z-Axis Stall Detection M906 X400 Y400 ; Lower motor current M574 X1 Y2 S4 ; Configure Z-Axis stall detection homing M400 ; make sure everything has stopped before we make changes G1 H1 X-0.2 F3000 ; move a little for cal of sensorless homing / not stalled G1 H1 Y-0.2 F3000 ; move a little for cal of sensorless homing / not stalled M400 ; make sure everything has stopped before we make changes M569 P0.0 ; Check status in console M569 P0.1 ; Check status in console G1 H1 X-350 ; Home Z-Axis actuators independently M400 ; make sure everything has stopped before we make changes G90 ; absolute positioning G1 X150 F6000 ; move to center of bed ;revert back M906 X1000 Y1000 ; Reset motor current M569 P0.0 S1 D2 ; reset motors back to spread cycle, M569 P0.1 S1 D2 ; reset motors back to spread cycle, M569 P0.0 ; Check status in console M569 P0.1 ; Check status in console; homey.g M400 ; make sure everything has stopped before we make changes G91 ; relative positioning M569 P0.0 S1 D3 V10 ; set to stelth chop M569 P0.1 S1 D3 V10 ; set to stelth chop M915 P0.0:0.1 S1 F0 R1 H200 ; Configure Z-Axis Stall Detection M906 X400 Y400 ; Lower motor current M574 X1 Y2 S4 ; Configure Z-Axis stall detection homing M400 ; make sure everything has stopped before we make changes G1 H1 X-0.2 F3000 ; move a little for cal of sensorless homing / not stalled G1 H1 Y-0.2 F3000 ; move a little for cal of sensorless homing / not stalled M400 ; make sure everything has stopped before we make changes M569 P0.0 ; check status in console M569 P0.1 ; check status in console G1 H1 Y350 F6000 ; Home Z-Axis actuators independently M400 ; make sure everything has stopped before we make changes G90 ; absolute positioning G1 Y150 F6000 ; move to center of bed ;revert back M906 X1000 Y1000 ; Reset motor current M569 P0.0 S1 D2 ; reset motors back to spread cycle, M569 P0.1 S1 D2 ; reset motors back to spread cycle, M569 P0.0 ; check status in console M569 P0.1 ; check status in consoleparking Z platform at base
; home_max_Z M400 ; make sure everything has stopped before we make changes G91 ; relative positioning M569 P0.4 S1 D3 V10 ; set to stelth chop M569 P0.5 S0 D3 V10 ; set to stelth chop M569 P0.6 S1 D3 V10 ; set to stelth chop M915 P0.4:0.5:0.6 S0 F0 R1 H50 ; Configure Z-Axis Stall Detection M906 Z700 ; Lower motor current by 50% M574 Z2 S4 ; Configure Z-Axis stall detection homing M400 ; make sure everything has stopped before we make changes G1 H1 Z-0.2 F3000 ; move a little for cal of sensorless homing / not stalled M400 ; make sure everything has stopped before we make changes G1 H1 Z350 ; Home Z-Axis actuators independently M400 ; make sure everything has stopped before we make changes G92 Z290 ; set a Z height G90 ; absolute positioning ;revert back M906 Z1000 ; Reset motor current M569 P0.4 S1 D2 ; reset motors back to spread cycle, M569 P0.5 S0 D2 ; reset motors back to spread cycle, M569 P0.6 S1 D2 ; reset motors back to spread cycle, M84 ; turn off motors -
What did you change exactly?
-
@phaedrux said in Steeper over heater waring unable to emergency stop:
What did you change exactly?
In thort: We had a talk about this yesterday and we wondered if there was a way to ensure stealthchop mode while homing but spreadcycle when travel and printing. His steppers never seem to get out of stealthchop after homing so we wanted to test defining the steppers to be in spreadcycle as default, then in the homing files set it to stealthchop before home and back to spreadcycle after home
So the change was (Moth can probably go deeper on this but should be somewhat correct)
; in config.g
M569 P0 S1 D2 ; define drive 0 to be in spreadcycle
M569 P1 S1 D2 ; define drive 1 to be in spreadcycle; Then in home(xy).g
; before homing
M569 P0 S1 D3 V10 ; define drive 0 to be in stealthchop while homing with V parameter low so it does not change to spreadcycle
M569 P1 S1 D3 V10 ; define drive 0 to be in stealthchop while homing with V parameter low so it does not change to spreadcycle
............
; after homing
M569 P0 S1 D2 ; define drive 0 to be in spreadcycle
M569 P1 S1 D2 ; define drive 1 to be in spreadcycle/roy
