Motors unresponsive via 3HC
-
Hello,
I have connected 3HC to the Main 6HC board which runs my IDEX wonderfully till now. I would like to work with 8 drivers in total to suit my new printer design
I have followed and read any information I could find regarding the issue .I can see both LEDs on the mainboard and the expansion board flushing simultaneously. I have successfully updated the firmware on the expansion board to suit the one installed on the main board - 3.4.1.
After that, I made a quick update to config.g in order to control two motors via the expansion drivers.
But the motors are not responsive to any command.
Your assistance is highly appreciated.M122 B1 Diagnostics for board 1: Duet EXP3HC rev 1.01 or earlier firmware version 3.4.1 (2022-06-01 21:15:27) Bootloader ID: not available All averaging filters OK Never used RAM 158932, free system stack 178 words Tasks: Move(notifyWait,0.0%,160) HEAT(notifyWait,0.0%,88) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) CanClock(notifyWait,0.0%,71) TMC(notifyWait,7.3%,99) MAIN(running,91.3%,399) IDLE(ready,0.0%,40) AIN(delaying,1.3%,263), total 100.0% Last reset 01:01:44 ago, cause: software Last software reset data not available Driver 0: pos 0, 80.0 steps/mm,standstill, SG min n/a, mspos 8, reads 51180, writes 0 timeouts 0, steps req 0 done 0 Driver 1: pos 0, 80.0 steps/mm,standstill, SG min n/a, mspos 8, reads 51180, writes 0 timeouts 0, steps req 0 done 0 Driver 2: pos 0, 80.0 steps/mm,standstill, SG min n/a, mspos 8, reads 51179, writes 0 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 -3/11, peak Rx sync delay 181, resyncs 0/0, no step interrupt scheduled VIN voltage: min 24.0, current 24.0, max 24.0 V12 voltage: min 12.1, current 12.1, max 12.1 MCU temperature: min 29.4C, current 30.6C, max 30.9C Last sensors broadcast 0x00000000 found 0 51 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 19793, send timeouts 0, received 22238, lost 0, free buffers 37, min 37, error reg 0 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 M122 === Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.4.1 (2022-06-01 21:09:01) running on Duet 3 MB6HC v1.01 or later (standalone mode) Board ID: 08DJM-956BA-NA3TN-6J1FL-3SN6K-998AU Used output buffers: 3 of 40 (21 max) === RTOS === Static ram: 151000 Dynamic ram: 98048 of which 0 recycled Never used RAM 101552, free system stack 190 words Tasks: NETWORK(ready,26.1%,270) ETHERNET(notifyWait,0.0%,168) HEAT(notifyWait,0.0%,321) Move(notifyWait,0.0%,267) CanReceiv(notifyWait,0.0%,772) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.9%,92) MAIN(running,65.9%,1083) IDLE(ready,0.0%,30), total 100.0% Owned mutexes: === Platform === Last reset 00:42:04 ago, cause: software Last software reset at 2022-09-12 13:21, reason: User, GCodes spinning, available RAM 101440, 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 131 MCU temperature: min 33.3, current 34.0, max 34.3 Supply voltage: min 23.7, current 23.8, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 11.9, 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 8, reads 61641, writes 11 timeouts 0 Driver 1: standstill, SG min 0, mspos 8, reads 61637, writes 15 timeouts 0 Driver 2: standstill, SG min 0, mspos 8, reads 61638, writes 14 timeouts 0 Driver 3: standstill, SG min 0, mspos 8, reads 61638, writes 14 timeouts 0 Driver 4: standstill, SG min 0, mspos 8, reads 61642, writes 11 timeouts 0 Driver 5: standstill, SG min 0, mspos 8, reads 61639, writes 14 timeouts 0 Date/time: 2022-09-12 14:04:06 Slowest loop: 20.94ms; fastest: 0.05ms === Storage === Free file entries: 10 SD card 0 detected, interface speed: 25.0MBytes/sec SD card longest read time 2.9ms, write time 0.0ms, max retries 0 === Move === DMs created 125, segments created 3, maxWait 27465ms, bed compensation in use: none, comp offset 0.000 === MainDDARing === Scheduled moves 1, completed 1, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 1], 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 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 === Filament sensors === Extruder 0 sensor: ok === CAN === Messages queued 22740, received 20262, lost 0, boc 0 Longest wait 2ms for reply type 6024, peak Tx sync delay 388, free buffers 50 (min 49), ts 12624/12623/0 Tx timeouts 0,0,0,0,0,0 === Network === Slowest loop: 3.04ms; 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 0 0 0 ; General preferences M575 P1 S1 B57600 ; enable support for PanelDue G90 ; send absolute coordinates... M83 ; ...but relative extruder moves M550 P"IDEX" ; set printer name ; ; Network M552 P0.0.0.0 S1 ; enable network and acquire dynamic address via DHCP M586 P0 S1 ; enable HTTP M586 P1 S0 ; disable FTP M586 P2 S0 ; disable Telnet ; ; Drives M569 P0.0 S1 ; physical drive 0.0 M569 P0.1 S1 ; physical drive 0.1 M569 P0.2 S0 ; physical drive 0.2 M569 P0.3 S1 ; physical drive 0.3 M569 P0.4 S0 ; physical drive 0.4 M569 P0.5 S1 ; physical drive 0.5 M569 P1.0 S1 ; physical drive 1.0 M569 P1.1 S1 ; physical drive 1.1 ;M584 X0.0 Y0.1 Z0.2 E0.3:0.5 U0.4 ; set drive mapping M584 X1.0 Y0.1 Z0.2 E0.3:0.5 U1.1;0.4 M350 Z16 E16 I0 ; configure microstepping without interpolation M350 X16 Y16 U16 I1 ; configure microstepping with interpolation M92 X80.00 Y80.00 Z400.00 E400.00 U100.00 ; set steps per mm M566 X300.00 Y300.00 Z60.00 E3000.00 U300.00 ; set maximum instantaneous speed changes (mm/min) M203 X12000.00 Y12000.00 Z2400.00 E60000.00 U12000.00 ; set maximum speeds (mm/min) M201 X5000.00 Y5000.00 Z200.00 E5000.00 U5000.00 ; set accelerations (mm/s^2) M204 P3000 ; set accelerations (mm/s^2) M906 X1600 Y1800 Z3000 E500 U1600 I20 ; set motor currents (mA) and motor idle factor in per cent M84 S120 ; Set idle timeout 
Thank you -
@elad what commands are you sending?
you only appear to have driver 1.1 mapped in your config -
X is mapped to 1.0 and U is mapped to 1.1
M584 X1.0 Y0.1 Z0.2 E0.3:0.5 U1.1
I sent G1 X### F#### -
@elad you need to home an axis before you can move it
-
@ELAD
@jay_s_uk said in Motors unresponsive via 3HC:@elad you need to home an axis before you can move it
... or send
M564 S0 H0to allow movements without homing. See M564 in the Gcode dictionary.Ian
-
Thank you but I think this is not the issue. I sent M564 H0 S0 before. See the Output from M122 B1 - Driver 1: pos 0, 80.0 steps/mm
This is not according to the config.g M92 U100 So I believe it is something else -
@elad I suspect that the EXP3HC hasn't started up when the motor commands in config.g are executed. If this is the case then if you run M98 P"config.g" the motors should move after that.
To resolve this:
-
Add a delay command early in config.g to give the EXP3HC time to start up. This is documented for the TOOL1LC board but not yet for the EXP3HC (we will add it). See https://docs.duet3d.com/en/Duet3D_hardware/Duet_3_family/Duet_3_Toolboard_1LC#startup-time.
-
Your EXP3HC board is running an old bootloader version, which may be extending the required startup time. Please update the bootloader on that board. See https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_bootloader.
-
-
@dc42 Thank you very much ! It fixed it !
-
undefined dc42 marked this topic as a question 12 Sept 2022, 13:16
-
undefined dc42 has marked this topic as solved 12 Sept 2022, 13:16