firmware 3.4 Rc1 Heater Fault
-
the wiring is fine the mechanics and thermal side are fine is an unresolved problem of the firmware, this defect was previously not there. I had pointed out copme other users the problem already in version 3.4 beta 7 the only thing maybe is the different sensor the pt1000 of e3d.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.0rc1 (2022-02-09 10:28:13) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJMSS-6J9DD-3S46N-TVFH8
Used output buffers: 1 of 40 (22 max)
=== RTOS ===
Static ram: 150984
Dynamic ram: 95712 of which 164 recycled
Never used RAM 103548, free system stack 142 words
Tasks: NETWORK(ready,26.4%,229) ETHERNET(notifyWait,0.1%,168) HEAT(notifyWait,0.0%,238) Move(notifyWait,0.0%,262) CanReceiv(notifyWait,0.0%,944) CanSender(notifyWait,0.0%,356) CanClock(delaying,0.0%,333) TMC(notifyWait,8.1%,58) MAIN(running,65.3%,925) IDLE(ready,0.0%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:14:15 ago, cause: power up
Last software reset at 2022-02-07 21:11, reason: User, GCodes spinning, available RAM 100532, 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
Aux0 errors 0,0,0
Step timer max interval 131
MCU temperature: min 24.6, current 39.4, max 39.5
Supply voltage: min 16.2, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.2, 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
Events: 0 queued, 0 completed
Driver 0: pos 192000, standstill, SG min 0, mspos 583, reads 54286, writes 23 timeouts 0
Driver 1: pos 0, standstill, SG min 0, mspos 617, reads 54286, writes 23 timeouts 0
Driver 2: pos 33603, standstill, SG min 0, mspos 649, reads 54286, writes 23 timeouts 0
Driver 3: pos 0, standstill, SG min 0, mspos 1, reads 54295, writes 14 timeouts 0
Driver 4: pos 0, standstill, SG min 0, mspos 1, reads 54296, writes 14 timeouts 0
Driver 5: pos 0, standstill, SG min 0, mspos 8, reads 54299, writes 11 timeouts 0
Date/time: 2022-02-10 12:52:42
Slowest loop: 5.17ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 5.6ms, write time 0.9ms, max retries 0
=== Move ===
DMs created 125, segments created 11, maxWait 377072ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 29, completed 29, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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
=== CAN ===
Messages queued 7701, received 0, lost 0, boc 0
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 50), ts 4280/0/0
Tx timeouts 0,0,4279,0,0,3420 last cancelled message type 30 dest 127
=== Network ===
Slowest loop: 18.71ms; 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 0 0 0
Socket states: 5 2 2 2 2 0 0 0
10/2/2022, 12:51:58 Auto tune starting phase 3, measuring
10/2/2022, 12:49:54 Auto tune starting phase 2, settling
10/2/2022, 12:47:20 Auto tune starting phase 1, heating up
10/2/2022, 12:47:15 M98 P"0:/macros/Tuning T0"
m115
FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.0rc1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2022-02-09 10:28:13; Configuration file for Duet 3 (firmware version 3.3)
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.3.10 on Fri Dec 31 2021 12:22:58 GMT+0100 (Ora standard dell’Europa centrale); General preferences
M575 P1 S1 B57600 ; enable support for PanelDue
G90 ; send absolute coordinates...
M83 ; ...but relative extruder moves
M550 P"Duet 300X Dual" ; set printer name
M955 P0 C"spi.cs3+spi.cs2"
M669 K1 ; select CoreXY mode; Network
M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP
M586 P0 S1 ; enable HTTP
M586 P1 S0 ; disable FTP
M586 P2 S0 ; disable Telnet; Drives
M569 P0.0 S1 ; physical drive 0.0 goes forwards
M569 P0.1 S1 ; physical drive 0.1 goes forwards
M569 P0.2 S0 ; physical drive 0.2 goes forwards
M569 P0.3 S0 ; physical drive 0.3 goes forwards
M569 P0.4 S0 ; physical drive 0.4 goes forwards
M584 X0.0 Y0.1 Z0.2 E0.3:0.4 ; set drive mapping
M350 X128 Y128 Z128 E128:128 I1 ; configure microstepping with interpolation
M92 X640.00 Y640.00 Z5171.72 E3367.10:3367.70 ; set steps per mm
M566 X800.00 Y800.00 Z60.00 E120.00:120.00 ; set maximum instantaneous speed changes (mm/min)
M203 X12000.00 Y12000.00 Z500.00 E1200.00:1200.00 ; set maximum speeds (mm/min)
M201 X2000.00 Y2000.00 Z20.00 E250.00:250.00 ; set accelerations (mm/s^2)
M906 X1000 Y1000 Z1000 E800:800 I30 ; set motor currents (mA) and motor idle factor in per cent
M84 S30 ; Set idle timeout
M593 P"zvd" F70; Axis Limits
M208 X-18 Y-5 Z0 S1 ; set axis minima
M208 X305 Y305 Z260 S0 ; set axis maximaM671 X10:295:295:10 Y280:280:5:5 P0.5
M591 D0 P5 C"e0_stop" R40:120 E3.0 S0; Endstops
M574 X1 S1 P"io1.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin io1.in
M574 Y1 S1 P"io2.in" ; configure switch-type (e.g. microswitch) endstop for low end on Y via pin io2.in
M574 Z1 S2 ; configure Z-probe endstop for low end on Z; Z-Probe
M950 S0 C"io7.out" ; create servo pin 0 for BLTouch
M558 P9 C"^io7.in" H5 F500:100 T6000 A5 R0.1 ; set Z probe type to bltouch and the dive height + speeds
G31 P500 X12.5 Y-20 Z1.493 ; set Z probe trigger value, offset and trigger height
M557 X15:295 Y15:300 S25:20 ; define mesh grid; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor 0 as thermistor on pin temp0
M950 H0 Q10 C"out0" T0 ; create bed heater output on out0 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 S130 ; set temperature limit for heater 0 to 120C
M308 S1 P"temp1" Y"pt1000" ; configure sensor 1 as PT1000 on pin temp1
M950 H1 C"out1" T1 ; create nozzle heater output on out1 and map it to sensor 1
M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H1 S400 ; set temperature limit for heater 1 to 400C
M308 S2 P"temp2" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 2 as thermistor on pin temp2
M950 H2 C"out2" T2 ; create nozzle heater output on out2 and map it to sensor 2
M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
M143 H2 S280 ; set temperature limit for heater 2 to 280C; Fans
M950 F0 C"out4" Q500 ; create fan 0 on pin out4 and set its frequency
M106 P0 S0 H1:2 T45 ; set fan 0 value. Thermostatic control is turned on
M950 F1 C"out5" Q500 ; create fan 1 on pin out5 and set its frequency
M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off; Tools
M563 P0 D0 H1 F1 ; define tool 0
G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets
M563 P1 D1 H2 F1 ; define tool 0
G10 P1 X25 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
; Miscellaneous
M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
T0 ; select first tool
M150 X0 ; set LED type to NeoPixel and set SPI frequency to 3MHz
M150 B255 P128 S65 F0
M501 - Ethernet -
-
@massimilianoconti said in firmware 3.4 Rc1 Heater Fault:
M303 T1 S270 Y3
how does the tuning look when you run it?
-
when I start tuning takes too long something in the algorithm must be changed. if I put 3 as hysteresis comes to completion for example. something needs to be changed in the tuning procedure. my hotend is geometrically excellent, it is designed to perform every temperature and material
-
@massimilianoconti do me a favour and run the tuning and post the results here.
-
10/2/2022, 13:29:16 Warning: heater behaviour was not consistent during tuning
Auto tuning heater 1 completed after 3 idle and 50 tuning cycles in 2520 seconds. This heater needs the following M307 command:
M307 H1 R2.558 K0.275:0.103 D6.31 E1.35 S1.00 B0 V23.9
Send M500 to save this command in config-override.g
10/2/2022, 13:05:33 Warning: heater behaviour was not consistent during tuning
Auto tune starting phase 4, measuring with fan on -
@massimilianoconti said in firmware 3.4 Rc1 Heater Fault:
my hotend is geometrically excellent
Can you give us some details about it?
-
my hot end is Phaetus dragonfly bmsBMSÕ«×Õ+⵿íÕ×ï.stl BMS Wireframes (7).pdf
-
That's a lovely hotend. What power is the heater? Are you using the sock? Do you have a part cooling fan and duct? Can you share an image of the temperature graph from the tuning?
-
@massimilianoconti said in firmware 3.4 Rc1 Heater Fault:
M307 H1 R2.558 K0.275:0.103 D6.31 E1.35 S1.00 B0 V23.9
Have you tried bumping up the "deadtime" D6.31? I bumped mine up to D8.31 and the heat faults have gone away.
-
I try thanks
-
you have the silicone socks I'm reviewing everything as soon as I perform a new test I attach it
-
hello as soon as I have the data I attach them. I wanted to know what compiler you need to open the source code to change the firmware... from the asset I downloaded in zip the purge code but you need a compiler ...
-
