Duet 3 Expansion 3HC no modement on drivers
-
LEDs lid up in sync with the 6HC.
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (standalone mode)
Board ID: 08DJM-9P63L-DJ3T0-6J1F8-3SD6J-TV0B9
Used output buffers: 1 of 40 (2 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 91892 of which 160 recycled
Never used RAM 111236, free system stack 219 words
Tasks: NETWORK(ready,29.3%,464) ETHERNET(notifyWait,0.0%,117) HEAT(delaying,0.0%,283) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,908) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,351) TMC(notifyWait,7.2%,93) MAIN(running,60.0%,944) IDLE(ready,3.4%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:03 ago, cause: software
Last software reset at 2021-11-12 20:59, reason: User, GCodes spinning, available RAM 111204, slot 2
Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task MAIN Freestk 0 n/a
Error status: 0x00
Step timer max interval 125
MCU temperature: min 44.5, current 45.2, max 45.3
Supply voltage: min 24.1, current 24.1, max 24.2, 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 16623, writes 14 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 16623, writes 14 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 16623, writes 15 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 16626, writes 12 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 16626, writes 12 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 16626, writes 12 timeouts 0, SG min/max 0/0
Date/time: 1970-01-01 00:00:00
Slowest loop: 4.40ms; fastest: 0.05ms
=== Storage ===
Free file entries: 10
SD card 0 detected, interface speed: 25.0MBytes/sec
SD card longest read time 3.1ms, 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 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 23, received 7, lost 0, longest wait 1ms for reply type 6042, peak Tx sync delay 4, free buffers 49 (min 48), ts 16/15/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 0.49ms; fastest: 0.02ms
Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions Telnet(0), 0 sessions
HTTP sessions: 1 of 8- Ethernet -
State: active
Error counts: 0 0 1 0 0
Socket states: 5 2 2 2 2 2 0 2
M122 b1
Diagnostics for board 1:
Duet EXP3HC firmware version 3.2 (2021-01-05)
Bootloader ID: not available
Never used RAM 154848, free system stack 200 words
HEAT 102 CanAsync 94 CanRecv 87 TMC 64 MAIN 299 AIN 257
Last reset 00:00:53 ago, cause: software
Last software reset data not available
Driver 0: position 0, 80.0 steps/mm, standstill, reads 36952, writes 11 timeouts 0, SG min/max 0/0
Driver 1: position 0, 80.0 steps/mm, standstill, reads 36954, writes 11 timeouts 0, SG min/max 0/0
Driver 2: position 0, 400.0 steps/mm, standstill, reads 36958, writes 11 timeouts 0, SG min/max 0/0
Moves scheduled 0, completed 0, in progress 0, hiccups 0
No step interrupt scheduled
VIN: 24.2V, V12: 12.3V
MCU temperature: min 40.2C, current 40.2C, max 40.2C
Ticks since heat task active 47, ADC conversions started 53288, completed 53288, timed out 0
Last sensors broadcast 0x00000000 found 0 50 ticks ago, loop time 0
CAN messages queued 24, send timeouts 0, received 281, lost 0, free buffers 36 - Ethernet -
-
@cando415 said in Duet 3 Expansion 3HC no modement on drivers:
Duet EXP3HC firmware version 3.2 (2021-01-05)
@cando415 said in Duet 3 Expansion 3HC no modement on drivers:
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47)
Your firmware are mismatched.
Upload the full 3.3 zip file and install when prompted.
https://github.com/Duet3D/RepRapFirmware/releases/download/3.3/Duet2and3Firmware-3.3.zip
Then check the expansion firmware again. If it's still not up to date, send M997 B# when # is the can address of the 3HC to force it to update.
-
ok. they dont move at the moment. just shake a bit on
G91
G1 H2 X20 F100 -
Is the shaking new after updating the firmware to match?
Do the motors work if connected directly to the mainboard?
-
Update is done.
Connected to the mainboard it works -
M350 X16 Y16 Z16:16:16:16 E16:16 U16 I1 ; set microstepping M92 X80 Y80 Z400:400:400:400 E426:426 U400 ; set microsteps per mmFor the Z axis you only need to specify the values once. So remove the extra :16:16:16 and :400:400:400
Can you send M98 P"config.g" and post the response?
-
M98 P"config.g"
TELNET is enabled on port 23
FTP is enabled on port 21
Error: Unknown pin name 'bedtemp'
Error: Unknown pin name 'e1temp'
Error: Unknown pin name 'bedheat'
Error: Heater 0 does not exist
Error: Heater 0 does not exist
Error: Heater 0 does not exist
Error: Heater 0 not found
Error: Unknown pin name 'e3temp'
Warning: Sensor number 1 has not been defined
Error: G0/G1: insufficient axes homed -
Well you've got a number of problems, but nothing directly related to motor movement.
Can you post the results of M122 for the 3HC after trying to get it to move?
-
Yes. Just setting up my upsidedown voron.
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 159104, free system stack 4392 words
Tasks: Move(notifyWait,0.0%,126) HEAT(delaying,0.0%,104) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,80) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.2%,63) MAIN(running,91.5%,438) IDLE(ready,0.0%,39) AIN(delaying,1.3%,263), total 100.0%
Last reset 00:08:08 ago, cause: power up
Last software reset data not available
Driver 0: position 800, 80.0 steps/mm, standstill, reads 55361, writes 22 timeouts 0, SG min/max 0/50, steps req 800 done 800
Driver 1: position 0, 80.0 steps/mm, standstill, reads 55362, writes 22 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 2: position 0, 400.0 steps/mm, standstill, reads 55368, writes 17 timeouts 0, SG min/max 0/0, steps req 0 done 0
Moves scheduled 1, completed 1, in progress 0, hiccups 0, step errors 0, maxPrep 23, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
Peak sync jitter -2/9, peak Rx sync delay 180, resyncs 0/0, no step interrupt scheduled
VIN: 24.2V, V12: 12.2V
MCU temperature: min 32.4C, current 33.8C, max 33.8C
Ticks since heat task active 61, ADC conversions started 488849, completed 488849, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 65 ticks ago, loop time 0
CAN messages queued 42, send timeouts 0, received 2471, lost 0, free buffers 37, min 37, error reg 11005e
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 293, adv 36962/36962 -
Can you send M906 and M913 to see what is reported for motor currents?
-
M913
Motor current % of normal - X:100, Y:100, Z:100, U:100, E
100
M906
Motor current (mA) - X:1100, Y:1100, Z:900, U:0, E:0:0, idle factor 30% -
When it was connected to the mainboard and worked, which motor port did you use and how was that port configured?
-
Just connectet it to Drive 3 and moved z
-
I connected an other stepper to Driver0 on the exp. board.
after trying
G1 H2 x10 F3000
the stepper started to spinn wildly. -
@cando415 to test stepper motors, before you send any G1 H2 moves, send G91 to put the firmware in relative mode. Then your G1 H12 X10 F300 command should result in 10mm of movement regardless of where the firmware thinks the position is initially.
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
i did send G91 first. 2-3 times the stepper on X does what he has to. Than starts spinning wild -
@cando415 how far does it move when it spins a lot? please sent eh complete sequence of commands you are sending.
-
I changed the wiring and plugged the X and Y to the mainboard.
Everything works fine. I recognised the noise is reduced extreamly.
Testing a bit. send you some results in abaout 30min -
the X,Y and Z are moving ok. i struggle to get the Extruder moving for testing in Driver1.0.
m302 p1
g1 h2 E50 F2000
don't work at the moment -
i think my extension board is scrap. u axis at 1.2 is moving like the X axis yesterday.
