Toolboard 1LC troubles
-
@Arminas the TDS gives peak value of 0.7A, so I would set it to something from 550 to 600 mA in RRF. If that does not improve its behavior, measure the resistance of both phases; if they differ too much the motor may be toast.
<>RatRig V-Minion Fly Super5Pro RRF<> V-Core 3.1 IDEX k*****r <> RatRig V-Minion SKR 2 Marlin<>
-
@oliof both phases has 4.6 ohms, although it's written that it should be 4.2. Is that an issue?
-
@oliof But if I connect the wire and measure phase on the loose end of wire, one phase is 4.6, another is 4.9
-
@oliof After a few layers extruder starts to skip the steps, and it gets extremely hot, I can't keep my fingers on it. So I guess it's motor fault?
I tried to swap to another motor, will see how it goes.
-
@oliof @droftarts same issue with other motor - during the print, something happened and blower fan started to blow 100% instead of 20% and I got an error "M106 board 121 does not have fan 0".
Here is m122:
m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.4.6 (2023-07-21 14:09:13) running on Duet 3 Mini5plus WiFi (standalone mode) Board ID: U51SX-F396U-D65J0-40KMW-M603Z-ZFNKD Used output buffers: 1 of 40 (24 max) === RTOS === Static ram: 103712 Dynamic ram: 110488 of which 36 recycled Never used RAM 23804, free system stack 118 words Tasks: NETWORK(notifyWait,14.3%,240) HEAT(notifyWait,0.0%,336) Move(notifyWait,1.5%,235) CanReceiv(notifyWait,0.0%,796) CanSender(notifyWait,0.0%,325) CanClock(delaying,0.0%,349) TMC(notifyWait,0.7%,106) MAIN(running,82.5%,417) IDLE(ready,0.1%,30) AIN(delaying,0.9%,263), total 100.0% Owned mutexes: WiFi(NETWORK) === Platform === Last reset 00:47:07 ago, cause: software Last software reset at 2024-04-07 22:10, reason: User, GCodes spinning, available RAM 27692, slot 0 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 2827072, completed 2827071, timed out 0, errs 0 Step timer max interval 1490 MCU temperature: min 28.0, current 35.4, max 37.4 Supply voltage: min 23.5, current 23.9, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/1, heap memory allocated/used/recyclable 2048/12/0, gc cycles 0 Events: 0 queued, 0 completed Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 41, reads 17656, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 41, reads 17656, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 41, reads 17655, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 41, reads 17655, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 41, reads 17656, writes 15, timeouts 0, DMA errors 0, CC errors 0 Driver 5: not present Driver 6: not present Date/time: 2024-04-07 22:58:07 Cache data hit count 4294967295 Slowest loop: 219.05ms; fastest: 0.07ms === Storage === Free file entries: 9 SD card 0 detected, interface speed: 22.5MBytes/sec SD card longest read time 6.4ms, write time 2.1ms, max retries 0 === Move === DMs created 83, segments created 34, maxWait 130698ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 17036, completed 17036, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 2], 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 -1 -1 -1 -1, ordering errs 0 Heater 0 is on, I-accum = 0.2 === 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 41267, received 55885, lost 0, boc 0 Longest wait 2ms for reply type 6026, peak Tx sync delay 6729, free buffers 18 (min 17), ts 14136/14135/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 183.57ms; fastest: 0.00ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) HTTP sessions: 2 of 8 = WiFi = Interface state: active Module is connected to access point Failed messages: pending 0, notready 0, noresp 0 WiFi firmware version 1.26 WiFi MAC address f0:08:d1:03:81:a2 WiFi Vcc 3.38, reset reason Power up WiFi flash size 2097152, free heap 25616 WiFi IP address 192.168.32.177 WiFi signal strength -56dBm, mode 802.11n, reconnections 0, sleep mode modem Clock register 00002002 Socket states: 0 0 0 0 0 0 0 0 -
@Arminas what does M122 B121 report when the fan goes missing?
-
@oliof So I tried to print one more time. This time there is no fan error, but extruder motor started to skip steps and it's over extruding a lot, line width looks at least 2x wider than it should be. Now I am thinking that it skips steps because of the huge over extrusion.
M122 B121:
M122 B121 Diagnostics for board 121: Duet TOOL1LC rev 1.1 or later firmware version 3.4.6 (2023-07-21 14:17:33) Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 2532, free system stack 41 words Tasks: Move(notifyWait,0.2%,99) HEAT(notifyWait,0.5%,83) CanAsync(notifyWait,0.0%,61) CanRecv(notifyWait,0.0%,74) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(notifyWait,3.0%,57) MAIN(running,91.2%,351) IDLE(ready,0.0%,26) AIN(delaying,5.0%,142), total 100.0% Last reset 00:24:55 ago, cause: power up Last software reset data not available Driver 0: pos 1710258, 415.0 steps/mm,ok, SG min 0, read errors 0, write errors 2, ifcnt 78, reads 15080, writes 6499, timeouts 35, DMA errors 0, CC errors 6477, failedOp 0x6a, steps req 2007480 done 2007461 Moves scheduled 6321, completed 6320, in progress 1, hiccups 2, step errors 0, maxPrep 690, maxOverdue 115, maxInc 113, mcErrs 0, gcmErrs 0 Peak sync jitter -3/10, peak Rx sync delay 215, resyncs 0/0, next step interrupt due in 439 ticks, enabled VIN voltage: min 7.7, current 23.7, max 24.3 MCU temperature: min 45.8C, current 67.7C, max 70.7C Last sensors broadcast 0x00000002 found 1 161 ticks ago, 0 ordering errs, loop time 1 CAN messages queued 29964, send timeouts 0, received 19829, lost 0, free buffers 37, min 36, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 537, adv 18383/74651 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 3, other errors 0 -
@dc42 maybe you have any insights?
-
@Arminas is the blower fan that goes to 100% the hot end heatsink fan, or the print cooling fan? If there is a temperature reading error on the hot end then it's normal for the hot end heatsink fan to go to 100%. The firmware does that because it doesn't know what the temperature is, and having the heatsink fan on may prevent the hot end from clogging or getting damaged.
My best guess is that either there is a problem with the temperature sensor, or the temperature reading input on the tool board has been damaged by either a short circuit between the thermistor and heater wires, or by electrostatic discharge. So I suggest you start by checking the thermistor using a multimeter. Check that its resistance at room temperature is as expected, and check that there is no continuity between it and the heater wires. If that looks OK, try using the second temperature connector on the tool board. Make sure that the hot end metalwork is connected to Duet ground, either directly or through a resistor, to prevent static charge from building up.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 it's the blower fan. Temp sensor is good by checking it with multimeter. Is it possible that toolboard temp reading input is damaged and it causes the toolboard to do weird things, like over extrusion and etc.?
What do you mean by checking the continuity between temp sensor and heater wires?
Hot end metalwork is not grounded I guess. How do I do that?
-
@dc42 Same happens with second temperature connector. It just starts over extruding out of nowhere..
idk if this helps, but here is M122 B121:
M122 B121 Diagnostics for board 121: Duet TOOL1LC rev 1.1 or later firmware version 3.4.6 (2023-07-21 14:17:33) Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10) All averaging filters OK Never used RAM 2532, free system stack 31 words Tasks: Move(notifyWait,3.1%,99) HEAT(notifyWait,10.7%,75) CanAsync(notifyWait,0.0%,59) CanRecv(notifyWait,0.8%,74) CanClock(notifyWait,0.5%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,84.4%,57) MAIN(running,22.1%,351) IDLE(ready,0.0%,26) AIN(delaying,138.0%,142), total 259.6% Last reset 28:02:20 ago, cause: software Last software reset data not available Driver 0: pos 7263403, 415.0 steps/mm,standstill, SG min 0, read errors 3, write errors 2, ifcnt 20, reads 18793, writes 6440, timeouts 12343, DMA errors 0, CC errors 6419, failedOp 0x06, steps req 17729885 done 17729885 Moves scheduled 269100, completed 269100, in progress 0, hiccups 13, step errors 0, maxPrep 747, maxOverdue 130, maxInc 67, mcErrs 0, gcmErrs 0 Peak sync jitter -5/13, peak Rx sync delay 225, resyncs 0/0, no step interrupt scheduled VIN voltage: min 20.9, current 23.7, max 24.3 MCU temperature: min 41.9C, current 71.1C, max 76.4C Last sensors broadcast 0x00000002 found 1 157 ticks ago, 0 ordering errs, loop time 1 CAN messages queued 2019442, send timeouts 0, received 1178017, lost 0, free buffers 37, min 34, error reg 110000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 974, adv 15860/74653 Accelerometer: LIS3DH, status: 00 I2C bus errors 0, naks 3, other errors 0 -
@Arminas said in Toolboard 1LC troubles:
MCU temperature: min 41.9C, current 71.1C, max 76.4C
Are you using a heated chamber?
-
@Phaedrux no, this printer is not enclosed. And I have one more RatRig Vcore 400 printer with 1LC, but this one is enclosed and there are no problems
1LC temp readings on enclosed printer are the same:
MCU temperature: min 19.6C, current 72.4C, max 75.2C -
Those temps seem very high for a non-enclosed printer. Can you share some photos of the setup?
-
@Phaedrux Sure, here it is.
-
Can you tell if there are any components on the board getting very hot?
-
@Phaedrux Blue - cold, Red - hot (I don't feel comfortable touching it more than 3 seconds). And extruder motor is very very hot
-
Can you disconnect the motor and anything connected to the IO connectors, and see if it still gets hot?
-
@Phaedrux one of IO is used for BLTouch, I can't start the print without it. Maybe it's not a big deal if I leave this one connected?
-
@Phaedrux @dc42 @oliof Unfortunately, I think I have recreated the main issue with my other printer with exactly the same setup.... I have touched the nozzle with tweezers and I think something shorted due to static discharge. Blower fan immediately started to blow at 100% speed instead of 20%.. And now I have "hotend offline" in my DWC...
"On the v1.3 toolboard the mounting screw holes are all grounded via 100K resistors to provide a path to ground for any static build up in the extruders, assuming the toolboard is mounted to the extruder" - so if any of 1LC mounting bolts touches the extruder motor, I can simply wire a hotend with one of the mounting bolts?
Also, am I right that I can ground hotend to any duet GND pin? I would also ground the hotend of my Modix printers, but there is no toolboard. So I would connect the wire from hotend to Duet2 Wifi ground pin.
