thanks that was it!
now i just wonder why the firmware got erased
thanks that was it!
now i just wonder why the firmware got erased
Hi everyone,
this morning I encountered a new error I had not seen yet.
Last week i did 2 30h print with no problem but when i tried to start one this morning I could not connect to duet web control.
i looked at the log from the PI 4 and here is what i get:
I saw it could be a problem with the board but the power looks ok?
I tried updating the pi to the lastest version with no change.
Does anyone have an idea?
@Phaedrux After about 1h of trying to manually level, I made it work,
the BL touch was touching but not triggering,
way harder to manually level this 1x1x1m printer than my 400x400x400mm hahaha
Thanks
Hi everyone,
I have a 1 cubic meterprinter with 4 independent lead screw , its been 2 years, and more than 1000 kg of printed plastic since I converted it to Duet.
I'm having issue with G30 & G32 for the first time
I just changed the tool extension board after the previous one shorted on a piece of metal.
The printer home like normal but when i send G32, i get this :
Error: Probe was not triggered during probing move
then:
Error: Compensation or calibration cancelled due to probing errors
I don't think it is the BL touch since homing works fine but I'm no expert haha
@Phaedrux thank you,i just did the update, i will try to see if it help today on my next print
i did send : M591 D0 P3 C"121.io1.in" S1 E5 L38.45 R0:900
after looking at the calibration
Hi, I am having difficulties with the magnetic filament sensor, I keep having this error:
I'm trying to print some pretty big parts on my 1m3 printer and I have this error every 20 layers or so still have 700 layers to go
here is my config file
config.g
what should i do?
Thank you @phaedrux
M563 D0 was the solution
@phaedrux
Sadly it did not change anything.
@p_a3
Hi, I have added the longer delay, and here are the result.
I'm using the SBC mode.
m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6J9D4-3SD6P-9U4B9
Used output buffers: 1 of 40 (11 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 61636 of which 0 recycled
Never used RAM 141652, free system stack 202 words
Tasks: SBC(ready,7.4%,330) HEAT(delaying,0.0%,331) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.0%,93) MAIN(running,85.3%,1252) IDLE(ready,0.3%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:00:37 ago, cause: software
Last software reset at 2022-02-22 07:59, reason: User, none spinning, available RAM 141608, slot 2
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 174
MCU temperature: min 33.1, current 34.7, max 34.7
Supply voltage: min 23.9, current 23.9, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.2, max 12.2, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Driver 0: position 0, standstill, reads 11833, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 11833, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 11833, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 11833, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 11833, writes 14 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 11834, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2022-02-22 08:00:09
Slowest loop: 0.42ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 not detected, interface speed: 37.5MBytes/sec
SD card longest read time 0.0ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
=== AuxDDARing ===
Scheduled moves 0, completed moves 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, chamberHeaters = -1 -1 -1 -1
=== GCodes ===
Segments left: 0
Movement lock held by null
HTTP* is doing "M122" 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 317, received 468, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 256, free buffers 49 (min 48), ts 188/187/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 2ms ago
RX/TX seq numbers: 1181/1181
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 34.59, max wait times: 21.6ms/0.0ms
Codes per second: 1.52
Maximum length of RX/TX data transfers: 2924/704
M122 B121
Diagnostics for board 121:
Duet TOOL1LC firmware version 3.3 (2021-06-15 16:12:58)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 2624, free system stack 2789 words
Tasks: Move(notifyWait,0.0%,153) HEAT(delaying,0.1%,117) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,2.8%,57) MAIN(running,92.1%,350) IDLE(ready,0.0%,27) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:02:18 ago, cause: power up
Last software reset time unknown, reason: HardFault, available RAM 12648, slot 0
Software reset code 0x0060 ICSR 0x00000003 SP 0x20001998 Task CanR Freestk 94 ok
Stack: 20008000 0000ffff 002d007f 20002084 20000018 0000670b 00005edc 21000000 20007128 20001c14 20001c10 00010bdd a5a5a5a5 20007128 20001c14 20001c10 00021b00 00010d5d a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 a5a5a5a5 00018405 a5a5a5a5 a5a5a5a5 00000000
Driver 0: position 0, 397.5 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 14, reads 3830, writes 14, timeouts 0, DMA errors 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 0/4, peak Rx sync delay 528, resyncs 0/1, no step interrupt scheduled
VIN: 24.3V
MCU temperature: min 15.3C, current 24.7C, max 24.7C
Ticks since heat task active 44, ADC conversions started 138788, completed 138787, timed out 0, errs 0
Last sensors broadcast 0x00000002 found 1 49 ticks ago, loop time 0
CAN messages queued 1454, send timeouts 0, received 1162, lost 0, free buffers 37, min 37, error reg 110000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer detected: yes, status: 00
I2C bus errors 0, naks 0, other errors 0
Thank you!
Hi,
I have installed a duet 3 6HC (sbc) with a Toolboard 1LC on my 3D printer and I can't make the extruder stepper turn. The extrude and retract buttons are greyed out in the Duet Web interface and it doesn't work in g code.
I'm running on version 3.3
Here is my config.g.txt
everything else is working but i can't extrude...