Posts made by TomasL

@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

config-override.g

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.

@tomasl
Now in generated G-code I get the following unsupported commands

M900 K0.05 ; Filament gcode LA 1.5
M900 K30 ; Filament gcode LA 1.0

@jay_s_uk
Yes I thought so, so the G29 command is not required in the start-up code

@jay_s_uk
Do one need to run a complete mesh compensation before every job.