@terencemuscat P.s. - I fixed the connector by pushing it back in, no changes in wiring.
Posts made by terencemuscat
-
RE: Duet toolboard connector loosened during print,
-
Duet toolboard connector loosened during print,
Yesterday I had an ongoing print, and the CAN connector loosened and thus the toolboard was loosing and regaining connection. When I noticed this I paused the process and emergency stopped.
I fixed the connector but now I can get no connection via CAN.
I tried a different tool distribution board to no availM122 B10/ B121 gives timeout.
M122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.3 (2022-10-05 09:06:36) running on Duet 3 MB6HC v1.01 (SBC mode)
Board ID: 08DJM-9P63L-DJMSS-6J1F0-3S46P-9UFZ8
Used output buffers: 1 of 40 (14 max)
=== RTOS ===
Static ram: 152816
Dynamic ram: 67240 of which 24 recycled
Never used RAM 130592, free system stack 219 words
Tasks: SBC(resourceWait:,0.5%,454) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,943) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,334) TMC(notifyWait,7.8%,91) MAIN(running,87.9%,923) IDLE(ready,3.7%,30), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:16:54 ago, cause: power up
Last software reset at 2023-03-18 00:25, reason: User, GCodes spinning, available RAM 130304, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 134
MCU temperature: min 20.3, current 33.0, max 33.5
Supply voltage: min 23.8, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, under voltage events: 0
Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
Events: 0 queued, 0 completed
Driver 0: standstill, SG min 0, mspos 8, reads 20547, writes 16 timeouts 0
Driver 1: standstill, SG min 0, mspos 8, reads 20547, writes 16 timeouts 0
Driver 2: standstill, SG min 0, mspos 16, reads 20545, writes 18 timeouts 0
Driver 3: standstill, SG min 0, mspos 8, reads 20547, writes 16 timeouts 0
Driver 4: standstill, SG min 0, mspos 8, reads 20548, writes 16 timeouts 0
Driver 5: standstill, SG min 0, mspos 8, reads 20553, writes 11 timeouts 0
Date/time: 2023-03-18 07:46:34
Slowest loop: 1200.74ms; fastest: 0.04ms
=== 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, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], 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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 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 9026, received 0, lost 0, boc 2
Longest wait 0ms for reply type 0, peak Tx sync delay 0, free buffers 50 (min 49), ts 5073/0/0
Tx timeouts 0,0,5071,31,0,3918 last cancelled message type 4514 dest 127
=== SBC interface ===
Transfer state: 5, failed transfers: 0, checksum errors: 0
RX/TX seq numbers: 39474/39474
SPI underruns 0, overruns 0
State: 5, disconnects: 0, timeouts: 0 total, 0 by SBC, IAP RAM available 0x2ad10
Buffer RX/TX: 0/0-0, open files: 0
=== Duet Control Server ===
Duet Control Server v3.4.3
Code buffer space: 4096
Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
Full transfers per second: 19.20, max time between full transfers: 2212.3ms, max pin wait times: 2400.8ms/18.1ms
Codes per second: 0.04
Maximum length of RX/TX data transfers: 3507/764 -
RE: Pausing during printing
@phaedrux same problem with simplify 3D. I noticed it only happens in complicated surfaces, such as rounds.
-
RE: Pausing during printing
@terencemuscat In addition, I also reduced the speed and the problem is still there. Pausing points are almost in the same place but not exactly, meaning not a problem from the Gcode.
-
Pausing during printing
Hello,
I just finished my toolchanger using duet 3 with hemera toolboards. I installed superslicer (latest stable version) and am facing an issue, pausing during printing. I'm trying to print a benchy and im having blops constantly on one side from all the pausing being done during the print. I decreased the processing limit (g1 per second)from 1000 to 150, and the minimum extrusion length up to 0.05 but results remained the same. It's not minimum layer time as I noticed that sometimes it stops multiple times per layer.
Do you know what maybe is the cause?
Thanks,
Terence
-
RE: ToolChanger Toolboard Hemera Motor Not Working
So, i changed the boards and all works perfectly now. Thankyou
-
RE: ToolChanger Toolboard Hemera Motor Not Working
Thanks everyone for the detailed explanation. This evening I will replace the board and will give you an update.
Attached is also an image of the toolchanger should it be of interest. Thanks!
-
RE: ToolChanger Toolboard Hemera Motor Not Working
@dc42 I'm remembering that during assembly I wired + to - and vice versa by mistake, and I heard a popping noise when I switched it on. However I swapped them and powered back on and everything worked (except steppers). Could it be that I fried the drivers?
I will send a picture later today. If I fried them at least I have another 2 I''m not using.
-
RE: ToolChanger Toolboard Hemera Motor Not Working
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-DJMSS-6J1F0-3S46P-9UFZ8
Used output buffers: 4 of 40 (13 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 62540 of which 0 recycled
Never used RAM 140748, free system stack 200 words
Tasks: SBC(ready,5.6%,340) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.2%,93) MAIN(running,87.1%,922) IDLE(ready,0.0%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:03:55 ago, cause: power up
Last software reset at 2021-11-29 06:53, reason: User, none spinning, available RAM 138212, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 127
MCU temperature: min 18.3, current 30.7, max 30.8
Supply voltage: min 24.0, current 24.0, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.1, max 12.1, 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 878, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 878, writes 15 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 882, writes 11 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 878, writes 15 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 882, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 883, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-11-29 07:13:06
Slowest loop: 0.63ms; fastest: 0.04ms
=== 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 2044, received 5040, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 57497, free buffers 49 (min 48), ts 1177/1176/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 1, checksum errors: 0
Last transfer: 3ms ago
RX/TX seq numbers: 6699/6699
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: 4.30, max wait times: 8.0ms/0.0ms
Codes per second: 0.05
Maximum length of RX/TX data transfers: 3856/708 -
RE: ToolChanger Toolboard Hemera Motor Not Working
@terencemuscat maybe @dc42 can help?, I followed your guide in building this. I appreciate all your work. Thankyou very much!
-
ToolChanger Toolboard Hemera Motor Not Working
Hello,
I designed and built a toolchanger using Duet 3 having 2 hemeras with toolboards (tool1lc v1.0). Everything is working successfully but im having trouble getting both extruder motors to work. Wiring is checked and looks fine, and prior to this post I also tried to map the z drive to the extruder motors, but they are still not working. I have no errors in DWC, and honestly do not know what might be the cause. However I think its firmware related since I don't think I managed to ruin both extruders during assembly :D.