Voron 2.4 with 6HC & 3HC

wbrokow1

I am initially setting up my voron . Almost everything works except the extrusion. Using 3.4.5 for boards and dwc. I updated using the web interface. The extrusion motor is plugged into the 3HC. I have verified that it not a dead extrusion motor. Any motor plugged into the board doesn’t work. Any help is appreciated. I am almost there!

T3P3Tony

@wbrokow1 please provide more information:
config.g

and also send M115 Bn where "n" is the address of the 3HC (by default this would be 1).

Phaedrux

@wbrokow1 said in Voron 2.4 with 6HC & 3HC:

except the extrusion

Is the tool selected?

wbrokow1

@Phaedrux

This is what I got with M115 B1

dc42

@wbrokow1 does M122 B1 work?

wbrokow1

@dc42 No, it doesn't. Could the board not be recognized?

wbrokow1

@wbrokow1 oh M122. let me try!

wbrokow1

@wbrokow1 no , m122 says response too long.

dc42

@wbrokow1 try starting the object model plugin. Then look under the "boards" key to see the data for board 1.

I suspect that your 3HC may be running somewhat old firmware. If that's the case:

Upload the version 3.4.4 EXP3HC firmware to the Duet via the Install Update facility;
Power down the system. Set the 3HC switches all off. Then power the system up again. The 3HC should load new firmware from the 6HC. When its Status LED is flashing in sync with the 6HC again, power the system down and reset the switches to address 1.

wbrokow1

@dc42 where is the "Install Update Facility" ?
Thanks

dc42

@wbrokow1 it's on the Setup/Machine Specific page. You can also use the upload facility on the System Files page.

wbrokow1

@dc42 OK, 1 Problem solved. (thank you) Another arises:

I get an error driver 1.0 error phase A shorted to Vin.

wbrokow1

@dc42 ok swapped in another motor directly connected to board and get the same error.
Board issue?

Phaedrux

@wbrokow1 said in Voron 2.4 with 6HC & 3HC:

@wbrokow1 no , m122 says response too long.

response too long means you need to look in the Console tab to see the longer response.

wbrokow1

@Phaedrux OK , I see it thanks. Same error, It was fixed though. Thanks

Phaedrux

Can you send M122 and M122 B1 in the console and then copy and paste the results here please?

wbrokow1

@Phaedrux 3/24/2023, 3:09:16 PM m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.4.5 (2022-11-30 19:35:23) running on Duet 3 MB6HC v1.01 (standalone mode)
Board ID: 08DJM-9P63L-DJ3T8-6JKDL-3SN6Q-KS7BA
Used output buffers: 3 of 40 (14 max)
=== RTOS ===
Static ram: 152760
Dynamic ram: 97332 of which 184 recycled
Never used RAM 100324, free system stack 138 words
Tasks: NETWORK(ready,30.0%,210) ETHERNET(notifyWait,0.1%,561) HEAT(notifyWait,0.0%,328) Move(notifyWait,0.0%,259) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,336) CanClock(delaying,0.0%,339) TMC(notifyWait,8.5%,57) MAIN(running,61.3%,925) IDLE(ready,0.1%,30), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:01:28 ago, cause: power up
Last software reset at 2023-03-24 13:40, reason: User, GCodes spinning, available RAM 100324, slot 0
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Aux0 errors 0,0,0
Step timer max interval 126
MCU temperature: min 23.0, current 35.6, max 35.8
Supply voltage: min 24.1, current 24.1, max 24.3, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.0, current 12.0, 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 1016, reads 31060, writes 16 timeouts 0
Driver 1: standstill, SG min 0, mspos 24, reads 31060, writes 16 timeouts 0
Driver 2: standstill, SG min 0, mspos 1016, reads 31057, writes 19 timeouts 0
Driver 3: standstill, SG min 0, mspos 24, reads 31060, writes 16 timeouts 0
Driver 4: standstill, SG min 0, mspos 130, reads 31057, writes 19 timeouts 0
Driver 5: standstill, SG min 0, mspos 598, reads 31057, writes 19 timeouts 0
Date/time: 2023-03-24 15:09:12
Slowest loop: 16.87ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 4.4ms, write time 0.0ms, max retries 0
=== Move ===
DMs created 125, segments created 3, maxWait 17600ms, bed compensation in use: none, comp offset 0.000
=== MainDDARing ===
Scheduled moves 10, completed 10, 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
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
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 795, received 715, lost 0, boc 0
Longest wait 1ms for reply type 6018, peak Tx sync delay 10, free buffers 50 (min 49), ts 444/443/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 16.54ms; fastest: 0.03ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
HTTP sessions: 1 of 8
= Ethernet =
State: active
Error counts: 0 0 0 1 0 0
Socket states: 5 2 2 2 2 0 0 0
=== Multicast handler ===
Responder is inactive, messages received 0, responses 0
3/24/2023, 3:07:56 PM Connection established
3/24/2023, 2:00:37 PM Connection interrupted, attempting to reconnect...

m122 b1

Diagnostics for board 1:
Duet EXP3HC rev 1.01 or earlier firmware version 3.4.4 (2022-10-14 11:45:56)
Bootloader ID: not available
All averaging filters OK
Never used RAM 158932, free system stack 200 words
Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,108) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.4%,99) MAIN(running,91.2%,407) IDLE(ready,0.0%,40) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:02:28 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 1746.2 steps/mm,standstill, SG min 0, mspos 2, reads 46407, writes 16 timeouts 0, steps req 0 done 0
Driver 1: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 46413, writes 11 timeouts 0, steps req 0 done 0
Driver 2: pos 0, 80.0 steps/mm,standstill, SG min 0, mspos 8, reads 46413, writes 11 timeouts 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 -2/10, peak Rx sync delay 177, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.2, current 24.3, max 24.3
V12 voltage: min 12.3, current 12.3, max 12.3
MCU temperature: min 26.4C, current 31.6C, max 31.6C
Last sensors broadcast 0x00000000 found 0 165 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1216, send timeouts 0, received 1339, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

T3P3Tony

@wbrokow1 what is the issue at this point? I don't see any phase errors from the drivers in those M122 reports and the 3HC is responding to can messages.

wbrokow1

@T3P3Tony thanks for responding. basically the extruder was not extruding. I swapped to the second driver on the 3hc (1.1) and it worked. So I guess I have a bad driver on the 3hc board. Which is disappointing. I thought that spending extra for a quality board like the Duet would be w/o as many headaches as chinese crap.

Phaedrux

Can you setup the extruder motor on that original driver again and try to extrude? Do you get any error messages? After trying to extrude, send M122 and M122 B1 again and copy paste the results here please.

When and where did you purchase the Duet boards? If we can verify the driver has failed and you're within the warranty period and the boards were purchased from an authorized vendor you would be entitled to warranty replacement.