Posts made by TomasL

@droftarts
Yes I have realized that regarding config override.
However the issue with the message regarding the extruder heater is still there.
The bed heater did not produce any errors.

@Phaedrux When I switch Power on, or press the emergency stop and it reboots.

I might found the problem, last entries in the config override is intended to put the heaters at some middle temperature, in order to speed up the print.
I.E sett both extruder and bed at a standby temperature, however when I removed those lines the message dissapeared.
Obviously something is wrong with those lines

As I understand it

M568 P0 R200 S220 A1
M140 H0 S70 R55
M144

M568 sets the extruder active and standby temperatures, and switches the extruder heater to
standby
M140 sets the bed heater standby and active temperatures.
M144 sets the bed heater to standby.

So obviously there must be something wrong with the M568-line

@Phaedrux 53

@Phaedrux Turned on, or reset

@Phaedrux
Tuned them them with M303 a couple of weeks ago and M500 to save

@jay_s_uk
Here they are
config (1).g

; Configuration file for RepRapFirmware on Duet 2 WiFi
; executed by the firmware on start-up
;
; generated by RepRapFirmware Configuration Tool v3.5.4 on Mon Oct 14 2024 21:24:21 GMT+0200 (Central European Summer Time)

; General
G90 ; absolute coordinates
M83 ; relative extruder moves
M550 P"Frankenstein" ; set hostname

; Accessories
M575 P1 S0 B57600 ; configure PanelDue support

; Network
M552 S1 ; configure WiFi adapter
M586 P0 S1 ; configure HTTP

; Smart Drivers
M569 P0 S0 D2 ; driver 0 goes backwards (X axis)
M569 P1 S1 D2 ; driver 1 goes forwards (Y axis)
M569 P2 S1 D2 ; driver 2 goes forwards (Z axis)
M569 P3 S1 D2 ; driver 3 goes forwards (extruder 0)

; Motor Idle Current Reduction
M906 I30 ; set motor current idle factor
M84 S30 ; set motor current idle timeout

; Axes
M584 X0 Y1 Z2 ; set axis mapping
M350 X16 Y16 Z16 I1 ; configure microstepping with interpolation
M906 X800 Y800 Z800 ; set axis driver currents
M92 X80 Y80 Z400 ; configure steps per mm
M208 X0:200 Y0:200 Z0:200 ; set minimum and maximum axis limits
M566 X900 Y900 Z12 ; set maximum instantaneous speed changes (mm/min)
M203 X6000 Y6000 Z180 ; set maximum speeds (mm/min)
M201 X500 Y500 Z20 ; set accelerations (mm/s^2)

; Axis Limits
M208 X0 Y0 Z0 S1                                       ; set axis minima
M208 X185 Y175 Z150 S0                                 ; set axis maxima

; Extruders
M584 E3 ; set extruder mapping
M350 E16 I1 ; configure microstepping with interpolation
M906 E1000 ; set extruder driver currents
M92 E420 ; configure steps per mm
M566 E120 ; set maximum instantaneous speed changes (mm/min)
M203 E3600 ; set maximum speeds (mm/min)
M201 E250 ; set accelerations (mm/s^2)

; Kinematics
M669 K0 ; configure Cartesian kinematics

; Probes
M558 K0 P9 C"^zprobe.in" H10 F120 T6000 ; configure BLTouch probe via slot #0
G31 P500 X-37 Y0 Z2.82 ; set Z probe trigger value, offset and trigger height
M950 S0 C"exp.heater3" ; create servo #0 for BLtouch
;M307 H3 A-1 C-1 D-1

; Endstops
M574 X1 P"!xstop" S1 ; configure X axis endstop
M574 Y1 P"!ystop" S1 ; configure Y axis endstop
M574 Z1 P"!zstop" S1 ; configure Z axis endstop

; Mesh Bed Compensation
M557 X10:175 Y10:175 S27.5:27.5 ; define grid for mesh bed compensation

; Sensors
M308 S0 P"bedtemp" Y"thermistor" A"Heated Bed" T100000 B3950 ; configure sensor #0
M308 S1 P"e0temp" Y"thermistor" A"Nozzle" T100000 B3950 ; configure sensor #1

; Heaters
M950 H0 C"bedheat" T0 ; create heater #0
M143 H0 P0 T0 C0 S140 A0 ; configure heater monitor #0 for heater #0
M307 H0 R2.43 D5.5 E1.35 K0.56 B0 ; configure model of heater #0
M950 H1 C"e0heat" T1 ; create heater #1
M143 H1 P0 T1 C0 S285 A0 ; configure heater monitor #0 for heater #1
M307 H1 R2.43 D5.5 E1.35 K0.56 B0 ; configure model of heater #1

; Heated beds
M140 P0 H0 ; configure heated bed #0

; Fans
M950 F0 C"fan0" ; create fan #0
M106 P0 S0 L0 X1 B0.1 ; configure fan #0
M950 F1 C"fan1" ; create fan #1
M106 P1 S0 B0.1 H1 T45 ; configure fan #1

; Tools
M563 P0 D0 H1 F0 ; create tool #0
M568 P0 R0 S0 ; set initial tool #0 active and standby temperatures to 0C



; Custom settings
;Injusteringsskruvar
M671 X 95.2:-6.74:201.6 Y 191.7:-8.38:-8.38 P0.5        ; adjusting screws at rear left (-9.8,-18.3), front middle (95.2,191.7) and rear right (200.2,-18.3), thread pitch 0.5mm


; Miscellaneous
M501                                                   ; load saved parameters from non-volatile memory
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

;Bed area
;M557 X10:165 Y0:170 S20 ; probe from X=10 to 190, Y=10 to 190mm with a mesh spacing of 20mm
;G29 S1

config-override.g

; config-override.g file generated in response to M500 at 2024-10-15 00:28
; This is a system-generated file - do not edit
; Heater model parameters
M307 H0 R0.141 K0.318:0.000 D6.32 E1.35 S1.00 B0
M307 H1 R2.020 K0.368:0.000 D4.03 E1.35 S1.00 B0 V12.0
; Workplace coordinates
G10 L2 P1 X0.00 Y0.00 Z0.00
G10 L2 P2 X0.00 Y0.00 Z0.00
G10 L2 P3 X0.00 Y0.00 Z0.00
G10 L2 P4 X0.00 Y0.00 Z0.00
G10 L2 P5 X0.00 Y0.00 Z0.00
G10 L2 P6 X0.00 Y0.00 Z0.00
G10 L2 P7 X0.00 Y0.00 Z0.00
G10 L2 P8 X0.00 Y0.00 Z0.00
G10 L2 P9 X0.00 Y0.00 Z0.00
M568 P0 R200 S220 A1
M140 H0 S70 R55
M144

Every time I star my printer, I get this message:
"Event Notification"
"Heater 1 fault: exceeded allowed temperature excursion: target 220.0°C actual 53.0°C"

After I close the message and reset the nozzle heater everything is as expected.
Duet 2 WiFi 2.5.1
DWC 3.5.1

M122
=== Diagnostics ===
RepRapFirmware for Duet 2 WiFi/Ethernet version 3.5.1 (2024-04-19 14:40:46) running on Duet WiFi 1.02 or later
Board ID: 0JD0M-9P6M2-NW4SD-6J9DL-3S46N-1TNRM
Used output buffers: 1 of 26 (14 max)
=== RTOS ===
Static ram: 23256
Dynamic ram: 73344 of which 12 recycled
Never used RAM 16532, free system stack 184 words
Tasks: NETWORK(1,ready,13.7%,220) HEAT(3,nWait 5,0.1%,280) Move(4,nWait 5,0.0%,359) MAIN(1,running,85.9%,743) IDLE(0,ready,0.2%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:06:51 ago, cause: power up
Last software reset at 2024-10-20 20:26, reason: User, Gcodes spinning, available RAM 14088, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
MCU temperature: min 24.2, current 30.3, max 30.6
Supply voltage: min 11.6, current 11.8, max 12.3, under voltage events: 0, over voltage events: 0, power good: yes
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 1 queued, 1 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: 
Driver 6: 
Driver 7: 
Driver 8: 
Driver 9: 
Driver 10: 
Driver 11: 
Date/time: 2024-11-06 06:17:17
Cache data hit count 4294967295
Slowest loop: 12.22ms; 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.7ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, max steps late 0, min interval 0, bad calcs 0, ebfmin 0.00, ebfmax 0.00
no step interrupt scheduled
Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
=== DDARing 0 ===
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 -1 -1 -1 -1, ordering errs 0
=== GCodes ===
Movement locks 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
Q0 segments left 0
Code queue 0 is empty
=== Network ===
Slowest loop: 15.71ms; fastest: 0.00ms
Responder states: HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
HTTP sessions: 1 of 8
=== WiFi ===
Interface state: active
Module is connected to access point 
Failed messages: pending 0, notrdy 0, noresp 0
Firmware version 1.26
MAC address dc:4f:22:6e:70:65
Module reset reason: Turned on by main processor, Vcc 3.37, flash size 4194304, free heap 25088
WiFi IP address 192.168.10.151
Signal strength -44dBm, channel 0, mode 802.11n, reconnections 0
Clock register 00002002
Socket states: 0 0 0 0 0 0 0 0

I cannot understand why low-side switching is used (Apart from being cheap and easy).
I know it is easier, But High side is safer and, one get a common ground.

@gloomyandy Ok, so I cannot run a common to fans, heaters and the z-probe

Is all the gnd/- terminals common on Duet2.
Thinking of Heaters, Fans etc.
Want to reduce the amount of cabels running to the printer head/extruder assembly.

@jay_s_uk Ok, thats good, what are they using?

Maybe so, but the connections for the extruder heaters are to small.
The design should be sturdy enough so you can tighten them.

The connectors for the heaters and input power needs to be changed to something that does work properly.
With only two solder-point per connector, they tend break.
I had to re-solder all of these connectors, and I am thinking of pouring some epoxy and glue them firmly on the board.

@oliof
I found this row in the "Printer Setting Custom G-codes"

M107 ; turn off fan
{if max_layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+30, max_print_height)}{endif} ; Move print head up
G1 X0 Y200 F3000 ; home X axis

Should it be commented out?

@phaedrux Yes
JusterRatt_0.15mm_PLA_MK2.5_1h25m.gcode
And the STL
JusterRatt.stl

Why cant I upload it as a ZIP-file?

@phaedrux No supports, just two whels for the bed adustment, 20mm in dia and 4 mm high.
It was finished after som 26 layers or so.

@phaedrux RepRap is selected, double checked this, apperantly it is supported in standard RepRap, Duetversion of RepRap is not an option, just standard RepRap

Slized a small thing 20x4mm approx (according to superslicer)
Sliced in Superslicer.

Now in the Web UI it reports 226 layers and oject height of 33,95 mm, as you can se in the screencap.
Now where does this information come from, because it must be wrong.
Is it the Duet that mis-interprets something or is it the slicer that does something

@phaedrux Yes, I know all that, however my question was not answer in those documents.

@tomasl Never mind, found it in the filiament section and commented it out.