@dc42 FWIW, I don't even need to home the printer, just move any axis, wait and then move any other axis. Doing this now, my MCU Temperature was around 25C and, as best I can measure with an infrared thermometer, the drivers themselves never went above around 23C. When I'm not trying to measure temperature, the board has a 120mm fan blowing on it with exhaust holes out the side which seems to very effectively cool the drivers (as reported by the MCU as a proxy).
Posts made by crpalmer
-
RE: Did I kill my stepper driver (duet maestro)?
-
RE: Did I kill my stepper driver (duet maestro)?
@phaedrux When I said "all stepper drivers", I meant that I will get short-to-ground for whatever motor I have just driven. For example:
- G92 X100 Y100
- X +10
- wait a minute
- Y + 0.1
- short-to-ground: y drivers
- X + 0.1
- short-to-ground: x driver, y drivers
I just added this on to the end of it:
- G92 Z100
- Z +0.05 (a bunch of times to see if I really had to wait any appreciable amount of time)
- wait a minute (I did have to wait)
- Z +0.05
- short-to-ground: x driver, y drivers, z drivers
This made me think it was related to idle hold, so I commented out the M84 line of my config.g but that didn't seem to change the behaviour. With that line removed, I can still replicate the same behaviour.
-
RE: Did I kill my stepper driver (duet maestro)?
I do find it strange that this is affecting all stepper drivers, not just the one that was partially unplugged. Originally, I was trying the x axis but this is also the case:
- G92 Y100
- Y +0.1 from the dashboard
- wait 30 seconds
- Y +0.1
causes it to start reporting short-to-ground for both of my y steppers.
-
RE: Did I kill my stepper driver (duet maestro)?
@phaedrux I don't see any obvious damage to the drivers (or anything else) on the board. To rule out somehow having damaged the stepper that was partially unplugged, I connected a different stepper in its place. That didn't change anything. Here's the M122 output after successfully moving an axis:
=== Diagnostics === RepRapFirmware for Duet 2 Maestro version 3.3 (2021-06-15 21:47:01) running on Duet Maestro 1.0 Board ID: 08DGM-95762-FD3TD-6J1F8-3S86S-KS8MF Used output buffers: 3 of 24 (22 max) === RTOS === Static ram: 23556 Dynamic ram: 67012 of which 144 recycled Never used RAM 21928, free system stack 178 words Tasks: NETWORK(ready,28.1%,270) HEAT(delaying,0.1%,345) Move(notifyWait,0.1%,343) TMC(notifyWait,2.2%,117) MAIN(running,69.5%,493) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:00:31 ago, cause: power up Last software reset at 2021-12-06 19:06, reason: User, GCodes spinning, available RAM 21752, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 484 MCU temperature: min 21.0, current 22.0, max 22.3 Supply voltage: min 24.2, current 24.3, max 24.4, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, gc cycles 0 Driver 0: position 16000, standstill, read errors 0, write errors 0, ifcnt 9, reads 5227, writes 2, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, read errors 0, write errors 0, ifcnt 7, reads 5229, writes 0, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, read errors 0, write errors 0, ifcnt 9, reads 5226, writes 2, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, read errors 0, write errors 0, ifcnt 7, reads 5228, writes 0, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, read errors 0, write errors 0, ifcnt 9, reads 5226, writes 2, timeouts 0, DMA errors 0 Driver 5: position 0, standstill, read errors 0, write errors 0, ifcnt 9, reads 5226, writes 2, timeouts 0, DMA errors 0 Driver 6: position 0, standstill, read errors 0, write errors 0, ifcnt 7, reads 5228, writes 0, timeouts 0, DMA errors 0 Date/time: 2021-12-07 05:03:34 Slowest loop: 3.89ms; fastest: 0.13ms 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: 15.0MBytes/sec SD card longest read time 0.5ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 20325ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 6, completed moves 6, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 7.39ms; fastest: 0.04ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 Interface state active, link 100Mbps full duplex
And after letting it sit and then moving the axis 0.1mm with stepper errors:
Error: short-to-ground reported by driver(s) 0 12/7/2021, 5:06:45 AM m122 === Diagnostics === RepRapFirmware for Duet 2 Maestro version 3.3 (2021-06-15 21:47:01) running on Duet Maestro 1.0 Board ID: 08DGM-95762-FD3TD-6J1F8-3S86S-KS8MF Used output buffers: 3 of 24 (23 max) === RTOS === Static ram: 23556 Dynamic ram: 67012 of which 144 recycled Never used RAM 21928, free system stack 178 words Tasks: NETWORK(ready,27.8%,270) HEAT(delaying,0.1%,345) Move(notifyWait,0.1%,343) TMC(notifyWait,2.2%,117) MAIN(running,69.9%,493) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:03:41 ago, cause: power up Last software reset at 2021-12-06 19:06, reason: User, GCodes spinning, available RAM 21752, slot 2 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a Error status: 0x00 Step timer max interval 548 MCU temperature: min 21.8, current 24.0, max 24.4 Supply voltage: min 23.9, current 24.3, max 24.5, under voltage events: 0, over voltage events: 0, power good: yes Heap OK, handles allocated/used 99/0, heap memory allocated/used/recyclable 2048/4/4, gc cycles 0 Driver 0: position 15984, short-to-ground, standstill, read errors 0, write errors 0, ifcnt 11, reads 51996, writes 2, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, read errors 0, write errors 0, ifcnt 7, reads 51998, writes 0, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, read errors 0, write errors 0, ifcnt 10, reads 51998, writes 1, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, read errors 0, write errors 0, ifcnt 7, reads 51999, writes 0, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, read errors 0, write errors 0, ifcnt 10, reads 51998, writes 1, timeouts 0, DMA errors 0 Driver 5: position 0, standstill, read errors 0, write errors 0, ifcnt 10, reads 51998, writes 1, timeouts 0, DMA errors 0 Driver 6: position 0, standstill, read errors 0, write errors 0, ifcnt 7, reads 51998, writes 0, timeouts 0, DMA errors 0 Date/time: 2021-12-07 05:06:45 Slowest loop: 7.99ms; fastest: 0.16ms 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: 15.0MBytes/sec SD card longest read time 4.8ms, write time 0.0ms, max retries 0 === Move === DMs created 83, maxWait 186941ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 7, completed moves 7, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.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 Daemon is idle in state(s) 0 Autopause is idle in state(s) 0 Code queue is empty. === Network === Slowest loop: 6.02ms; fastest: 0.04ms Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions HTTP sessions: 1 of 8 Interface state active, link 100Mbps full duplex
-
RE: Did I kill my stepper driver (duet maestro)?
Sounds like I've probably killed something related to the stepper drivers. It just occurred to me to try using only the y axis to see if the problem was specific to the x axis or just a general problem with the board. I homed the printer and then periodically kept moving just the y axis and had something similar happen after a few minutes.
-
Did I kill my stepper driver (duet maestro)?
While working on my printer (with the power off), I accidentally partially unplugged the cable from a stepper. It was about 50% plugged in and 50% unplugged.
I homed my printer with no problems and then started a print. After waiting for the bed and hotend to reach temperature, the job tries to home the printer causing that motor to stutter and I see "short-to-ground" errors on a bunch of drivers. If I power the printer off for a while (not just a few seconds), I can home that axis and drive it just fine. If I then let the printer sit for several minutes then homing that axis now causes the stuttering and a flurry of short-to-ground errors. Between the time that homing succeeded and the time that it failed, the printer didn't move and nothing was touched. In concrete steps, I did:
- Power on
- Home X
- G1 X200
- Home X
- G1 X200
- wait for a bit
- Home X
- bad things happen!
These steps seem to be reproducible. I've repeated the procedure three times in a row now and the couple of times when I homed and then started the print.
I'm guessing that this is a sign that I should upgrade to a Duet 3 board, but I wanted to check that there isn't any obvious reason why I would be seeing this behaviour?
Thanks!
Chris -
RE: Tevo LM recent conversion and z step issues
@the_gibson Your original config of the steps:
M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
M92 X80.00 Y80.00 Z80.00 E403.00 ; set steps per mm'is probably better than what you have now. I think interpolation only works at 16 steps/mm which was a mistake in my old config.
Did you ever print a small cube to see what it looked like?
-
RE: Tevo LM recent conversion and z step issues
@the_gibson I think that your steps/mm are right for x/y/z. If they were wrong you'd get a calibrated height that was well off of 530 because the calibration also calibrates how high it can go. Also, mine was running back in its stock days with the same value.
Is your first layer actually a little too close? You could print a cube and see if you have "elephant foot" at the bottom indicating it is too close.
If not, are you extruder steps/mm correct and have you calibrated the flow rate? Dragging could also be over extrusion.
-
RE: Tevo LM recent conversion and z step issues
@the_gibson The steps/mm look right for stock. Can you post the output of
M665
M666after you run G32 until it seems to converge (aka, the last deviation seems to stop getting smaller when you run the calibration)? I'm curious to see what corrections it ended up making.
-
RE: Tevo LM recent conversion and z step issues
@the_gibson That's never going to print well. The fact that the deviation is so high means that effectively the software is unable to compensate for whatever the hardware is doing. My TLM has many mods that make my current configuration useless to you. The last stock configuration I had was from 2018. You can look at it here in case it helps:
-
RE: Tevo LM recent conversion and z step issues
@the_gibson What does the console report when you run the calibration. It should tell you what kind of error it measured and how well it corrected it. Here's from my last print on my tlm:
Calibrated 6 factors using 13 points, (mean, deviation) before (0.031, 0.033) after (0.000, 0.032)
You want to have the last number (deviation after calibration) to ideally be less than 0.04 for good prints.
Are you really running the bed.g calibration when each probe point takes about 15 seconds to probe from 30mm up? That's what you config.g says.
-
RE: Tevo LM recent conversion and z step issues
@the_gibson Have you run a G32 to do the delta calibration? If so, what does your bed.g look like and what's the result of running a G32? If not, you should do so and then post your bed.g and the output of the G32 command.
FWIW, I have a G32 in my start.gcode so that I ensure it's always calibrated. I'm pretty sure that you aren't doing that because you have:
M558 H30 ;*** Remove this line after delta calibration has been done and new delta parameters have been saved
still in your config.g which means it would be probing at 2mm/sec from 30mm up for each point and that would get boring to watch.
-
RE: M303 T1 + thermostaticfan + 3HC does not turn on the fan
@phaedrux, thanks!
The M563 F2 was indeed the problem. I missed that because I haven't actually hooked up a part cooling fan yet....
-
RE: M303 T1 + thermostaticfan + 3HC does not turn on the fan
m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus Ethernet (SBC mode) Board ID: VPY0D-V296U-D65J0-40KMW-JU03Z-Z5Q1H Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 102724 Dynamic ram: 93340 of which 0 recycled Never used RAM 47640, free system stack 200 words Tasks: SBC(ready,384.6%,321) HEAT(delaying,1.6%,373) Move(notifyWait,4.8%,338) CanReceiv(notifyWait,1.9%,773) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.6%,338) TMC(notifyWait,54.3%,106) MAIN(running,7734.9%,566) IDLE(ready,0.1%,29) AIN(delaying,66.6%,264), total 8249.4% Owned mutexes: HTTP(MAIN) === Platform === Last reset 01:36:36 ago, cause: software Last software reset at 2021-08-17 16:35, reason: User, none spinning, available RAM 47508, slot 1 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 5796936, completed 5796935, timed out 0, errs 0 Step timer max interval 770 MCU temperature: min 26.5, current 26.8, max 28.9 Supply voltage: min 24.1, current 24.2, max 24.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 Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 64, reads 42934, writes 12, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 64, reads 42934, writes 12, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 64, reads 42933, writes 12, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 67, reads 42933, writes 12, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 67, reads 42934, writes 12, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-08-17 18:12:01 Cache data hit count 4294967295 Slowest loop: 2.09ms; fastest: 0.08ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, 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, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === 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 52186, received 69562, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 482, free buffers 17 (min 16), ts 28985/28984/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === State: 4, failed transfers: 0, checksum errors: 0 Last transfer: 3ms ago RX/TX seq numbers: 5329/5329 SPI underruns 0, overruns 0 Disconnects: 0, timeouts: 0, IAP RAM available 0x10b00 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.84, max wait times: 9.5ms/0.0ms Codes per second: 0.01 Maximum length of RX/TX data transfers: 3284/752 m122 b1 Diagnostics for board 1: Duet EXP3HC firmware version 3.3 (2021-06-15 16:12:41) Bootloader ID: not available Never used RAM 158632, free system stack 4382 words Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,1.0%,94) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.2%,82) CanClock(notifyWait,0.3%,71) TMC(notifyWait,311.8%,63) MAIN(running,3904.2%,347) IDLE(ready,0.0%,39) AIN(delaying,56.0%,263), total 4273.6% Last reset 01:37:43 ago, cause: software Last software reset data not available Driver 0: position 0, 830.0 steps/mm, standstill, reads 20616, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0 Driver 1: position 0, 160.0 steps/mm, standstill, reads 20617, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0 Driver 2: position 0, 160.0 steps/mm, standstill, reads 20617, writes 17 timeouts 0, SG min/max 0/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 -5/13, peak Rx sync delay 181, resyncs 0/0, no step interrupt scheduled VIN: 24.3V, V12: 12.2V MCU temperature: min 29.4C, current 29.6C, max 32.0C Ticks since heat task active 76, ADC conversions started 5864095, completed 5864093, timed out 0, errs 0 Last sensors broadcast 0x00000004 found 1 80 ticks ago, loop time 0 CAN messages queued 70382, send timeouts 0, received 52789, lost 0, free buffers 37, min 37, error reg 110000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 8/17/2021, 6:12:02 PM m122 === Diagnostics === RepRapFirmware for Duet 3 Mini 5+ version 3.3 (2021-06-15 21:46:11) running on Duet 3 Mini5plus Ethernet (SBC mode) Board ID: VPY0D-V296U-D65J0-40KMW-JU03Z-Z5Q1H Used output buffers: 1 of 40 (13 max) === RTOS === Static ram: 102724 Dynamic ram: 93340 of which 0 recycled Never used RAM 47640, free system stack 200 words Tasks: SBC(ready,384.6%,321) HEAT(delaying,1.6%,373) Move(notifyWait,4.8%,338) CanReceiv(notifyWait,1.9%,773) CanSender(notifyWait,0.0%,371) CanClock(delaying,0.6%,338) TMC(notifyWait,54.3%,106) MAIN(running,7734.9%,566) IDLE(ready,0.1%,29) AIN(delaying,66.6%,264), total 8249.4% Owned mutexes: HTTP(MAIN) === Platform === Last reset 01:36:36 ago, cause: software Last software reset at 2021-08-17 16:35, reason: User, none spinning, available RAM 47508, slot 1 Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00000000 BFAR 0xe000ed38 SP 0x00000000 Task SBC Freestk 0 n/a Error status: 0x00 MCU revision 3, ADC conversions started 5796936, completed 5796935, timed out 0, errs 0 Step timer max interval 770 MCU temperature: min 26.5, current 26.8, max 28.9 Supply voltage: min 24.1, current 24.2, max 24.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 Driver 0: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 64, reads 42934, writes 12, timeouts 0, DMA errors 0 Driver 1: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 64, reads 42934, writes 12, timeouts 0, DMA errors 0 Driver 2: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 64, reads 42933, writes 12, timeouts 0, DMA errors 0 Driver 3: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 67, reads 42933, writes 12, timeouts 0, DMA errors 0 Driver 4: position 0, standstill, SG min/max 0/0, read errors 0, write errors 1, ifcnt 67, reads 42934, writes 12, timeouts 0, DMA errors 0 Driver 5: position 0, assumed not present Driver 6: position 0, assumed not present Date/time: 2021-08-17 18:12:01 Cache data hit count 4294967295 Slowest loop: 2.09ms; fastest: 0.08ms === Storage === Free file entries: 10 SD card 0 not detected, interface speed: 0.0MBytes/sec SD card longest read time 0.0ms, write time 0.0ms, max retries 0 === Move === DMs created 83, 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, chamberHeaters = -1 -1 Heater 1 is on, I-accum = 0.0 === 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 52186, received 69562, lost 0, longest wait 1ms for reply type 6018, peak Tx sync delay 482, free buffers 17 (min 16), ts 28985/28984/0 Tx timeouts 0,0,0,0,0,0 === SBC interface === State: 4, failed transfers: 0, checksum errors: 0 Last transfer: 3ms ago RX/TX seq numbers: 5329/5329 SPI underruns 0, overruns 0 Disconnects: 0, timeouts: 0, IAP RAM available 0x10b00 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.84, max wait times: 9.5ms/0.0ms Codes per second: 0.01 Maximum length of RX/TX data transfers: 3284/752 m98 P"config.g"
(nothing else printed with the config.g, no errors or warnings)
-
M303 T1 + thermostaticfan + 3HC does not turn on the fan
It seems like I may have hit a bug with running firmware 3.3. I searched the forum and looked at github and I didn't see anything similar but it's possible this is already known or I have a stupid configuration issue...
I am running a Duet 3 Mini 5+ and a 3HC expansion board attached via the can bus. There are 2 tools defined, T0 is using heater, thermistor and fan ports on the Duet 3 Mini and T1 is using heater, thermistor and fan ports on the 3HC expansion board.
When either of those heaters is enabled / disabled, the thermostatically controlled fan turns on and off as expected.
The thermostatically controlled hotend fan is also enabled correctly when running all three of the following PID tuning requests:
M303 H1 P1 S255
M303 T0 S255
M303 H2 P1 S255but when I run:
M303 T1 S255
the thermostatic controlled fan does not turn on and by around 150C, I end up triggering an emergency stop to abort the tuning.
Here's my config.g:
; General preferences G90 ; send absolute coordinates... M83 ; ...but relative extruder moves ; Drives M569 P0 S1 D3 ; physical drive 0 goes forwards, stealthchop M569 P1 S0 D3 ; physical drive 1 goes backwards M569 P2 S0 D3 ; physical drive 2 goes backwards M569 P3 S0 D3 ; physical drive 3 goes backwards M569 P4 S0 D3 ; physical drive 4 goes backwards M569 P1.0 S0 D3 ; physical drive 1.0 goes backwards M569 P1.1 S1 D3 ; physical drive 1.1 goes forwards M569 P1.2 S1 D3 ; physical drive 1.2 goes forwards M584 X0.2 Y0.1:1.2 u1.1 E0.0:1.0 Z0.3:0.4 ; set drive mapping M92 X160.00 Y160.00 U160.00 Z800.00 E830 ; set steps per mm (should be e415, tlm had e398.1,i though 404.5?)*2(0.9degree stepper) M350 X16 Y16 U16 Z16 E16 I1 ; set microstepping to 256 interpolation M566 X600.00 Y600.00 U600.00 Z18.00 E1000.00 ; set maximum instantaneous speed changes (mm/min) (bondtech) M203 X24000.00 Y24000.00 U24000.00 Z360.00 E3600.00 ; set maximum speeds (mm/min) (bondtech) M201 X500.00 Y500.00 U500.00 Z100.00 E1000.00 ; set accelerations (mm/s^2) (bondtech) M906 X700 Y700 U700 Z800 E700 I30 ; set motor currents (mA) and motor idle factor in per cent (bondtech) M84 S30 ; Set idle timeout ; Z drive M671 X175:175 Y-35:385 S2 ; motor order: front, back ; Axis Limits M208 X10 Y0 Z0 U-50 S1 ; set axis minima M208 X350 Y350 Z420 U290 S0 ; set axis maxima ; Endstops M574 X2 S1 P"^0.io5.in" ; configure active-high endstop for high end on X M574 Y2 S1 P"^0.io6.in+^1.io0.in" ; configure active-high endstop for high end on Y M574 U1 S1 P"^1.io2.in" ; configure active-high endstop for high end on U ; Z-Probe M950 S0 C"io1.out" ; servo pin definition M558 P9 C"^io1.in" H5 F100 T2000 G31 X0 Y55 Z1.30 P25 ;M557 X5:200 Y5:200 P7 ; define mesh grid ; Fans (tool 0) M950 F0 C"out5" Q250 ; create fan and set its frequency M106 P0 S0 H-1 ; set fan value (off). Thermostatic control is turned off M950 F1 C"out6" Q500 ; create fan and set its frequency M106 P1 S1 T45 H1 ; set fan value (on). Thermostatic control is turned on ; Fans (tool 1) M950 F2 C"1.out6" Q500 ; create fan and set its frequency M106 P2 S1 T45 H2 ; set fan value (on). Thermostatic control is turned on M950 F3 C"1.out7" Q250 ; create fan and set its frequency M106 P3 S0 H-1 ; set fan value (off). Thermostatic control is turned off ; Bed Heater M308 S0 P"temp0" Y"thermistor" T100000 B4092 ; configure sensor M950 H0 C"out0" T0 ; create bed heater output and map it to sensor 0 M307 H0 R0.272 C349.6 D8.37 S1.00 V23.7 M140 H0 ; map heated bed to heater 0 M143 H0 S120 ; set temperature limit for heater 0 to 120C ; tool 0: e3dv6 40w M308 S1 P"temp1" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor M950 H1 C"out1" T1 ; create nozzle heater output and map it to sensor 1 M307 H1 B0 R2.593 C211.1:173.4 D5.20 S1.00 V24.1 ; tuned (new) at 255 10mm off the bed with the part cooling fan M563 P0 S"E3Dv6" D0 H1 F0 ; define tool 0 G10 P0 X0 Y0 Z0 ; set tool 0 axis offsets ; tool 1: e3dv6 40w ;M308 S2 P"1.temp2" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor ;M950 H2 C"1.out2" T2 ; create nozzle heater output and map it to sensor 2 ;M307 H1 B0 R2.508 C225.2 D5.67 S1.00 V24.1 ; tuned 255 10mm off of the bed with the part cooling fan ;M563 P1 S"E3Dv6" D1 H2 F2 ; define tool 1 ;G10 P1 X0 Y0 Z0 ; set tool 1 axis offsets ; tool 1: e3dv6 volcano 30w M308 S2 P"1.temp2" Y"thermistor" T100000 B4725 C7.06e-8 ; configure sensor M950 H2 C"1.out2" T2 ; create nozzle heater output and map it to sensor 2 M307 H2 B0 R1.666 C251.2 D4.48 S1.00 V24.3 ; tuned 255 no part cooling fan M563 P1 S"volcano" D1 H2 F2 ; define tool 1 G10 P1 X0 Y0 Z10 ; set tool 1 axis offsets ; Tool (common) G10 P0 R0 S0 ; set initial tool 0 active and standby temperatures to 0C G10 P1 R0 S0 ; set initial tool 0 active and standby temperatures to 0C ; MCU DOES NOT WORK ON THE DUET 3 MINI 5+, DON'T CONFIGURE: ; M912 P0 S-12.5 ; Calibrate MCU temperature ; Miscellaneous T0 ; select first tool
-
RE: Smart effector 2.0 vs. 1.3 ?
Thanks for the detailed reply. And I'm glad to hear that it sounds like 1.3 will be fine for me (e3d fan + 24v 30W heater).
-
RE: Mesh compensation not working on Tevo Little Monster
I had moved to fsr sensors and after removing the glass I did this: https://www.thingiverse.com/thing:2785213
I don't only print large objects in pla and rarely to the edges of the bed (most get wider higher up) so I wasn't in the least bit motivated to get the edges to heat well enough to melt my mounts...
-
RE: Mesh compensation not working on Tevo Little Monster
@giostark The glueing of the glass is amazingly bad. I cut the glass out of the aluminum frame and that was the single best single quality improved I made.
-
Smart effector 2.0 vs. 1.3 ?
Hi,
Is there a list of (significant) changes between these 2 versions of the smart effector? I just bought one and it's 1.3 and I wanted to know if I was going to be missing out on anything important?
The only difference I (think I) can see from the documentation are that the position of the thermistor connector moved and that a micro-fit connector was added for the hotend.
Thanks!
Chris -
RE: M906 and very large current value?
@Phaedrux thanks, but not a huge deal. It was just a Creality motor and I've replaced it with a slightly better Tevo motor from the scrap pile and it works better than ever now!