Roto Toolboard, no extruder motor motion?

jay_s_uk

@bug2k22 can you post an M122 output for the roto toolboard after you've commanded an extrusion?
Also when and where did you purchase the toolboard?

bug2k22

@jay_s_uk Just powered everything back on, set the hotend temperature and set to extrude 20mm from the paneldue interface. Nothing appears to happen.

M122 B20
Diagnostics for board 20:
Duet TOOL1RR firmware version 3.6.0-beta.2 (2024-11-12 08:12:15)
Bootloader ID: SAME5x bootloader version 2.9 (2023-10-06)
All averaging filters OK
Never used RAM 170600, free system stack 198 words
Tasks: Move(3,nWait 7,0.0%,147) TMC(2,delaying,1.3%,31) HEAT(2,nWait 6,0.1%,114) CanAsync(5,nWait 4,0.0%,66) CanRecv(3,nWait 1,0.0%,73) CanClock(5,nWait 1,0.0%,64) ACCEL(3,nWait 6,0.0%,67) MAIN(1,running,96.5%,320) IDLE(0,ready,0.0%,29) AIN(2,nWait 2,2.1%,211), total 100.0%
Owned mutexes:
Last reset 00:03:32 ago, cause: power up
Last software reset data not available
Moves scheduled 1, hiccups 0 (0.00/0.00ms), segs 3, step errors 0 (types 0x0), maxLate 0 maxPrep 14, ebfmin 0.00 max 0.00
Peak sync jitter -4/4, peak Rx sync delay 181, resyncs 0/0, no timer interrupt scheduled, next step interrupt due in 4279184150 ticks, disabled
VIN voltage: min 23.9, current 24.0, max 24.0
MCU temperature: min 21.4C, current 21.6C, max 21.8C
Driver 0: pos 8000, 400.0 steps/mm, standstill, SG min 0, temp 20.1C, read errors 0, write errors 0, ifcnt 12, reads 28244, writes 1, timeouts 0, DMA errors 0
Last sensors broadcast 0x00000002 found 1 5 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1194, send timeouts 0, received 521, lost 0, ignored 0, errs 0, boc 0, free buffers 38, min 38, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 285, adv 37080/37080
Accelerometer: LIS2DW, status: 00
Inductive sensor: raw value 268435455, frequency 25.00MHz, current setting 13, amplitude error
Integrated filament monitor not present
I2C bus errors 0, naks 0, contentions 0, other errors 0
=== Filament sensors ===
Interrupt 5726621 to 0us, poll 2 to 172us
Driver 0: no data received, errs: frame 0 parity 0 ovrun 0 pol 0 ovdue 0

The board was purchased from E3D November 24
.

Phaedrux

Can you send M98 P"config.g" and report the results here?

bug2k22

@Phaedrux Entering that command to the console at the web interface produces no output.

07/01/2025, 22:13:36 	M98 P"config.g"
07/01/2025, 22:12:21 	M98 P"config.g"
07/01/2025, 20:53:30 	Connection established

Phaedrux

Do you experience the same issue on 3.5.4 stable release?

bug2k22

@Phaedrux I haven't run this configuration with 3.5.4. With the previous setup, upgrading to 3.5.4 broke the setup and the board firmware became corrupt and had to recover with a usb cable. So I upgraded to the latest beta on the board and sbc and all has been working well.

I presume it's not a simple task to downgrade both boards and all the sbc packages to a previous version?

jay_s_uk

@bug2k22 you should be able to run the following

M997 S2 F"stable-3.5"
M997 S2

and that should downgrade you to 3.5.4

bug2k22

@jay_s_uk Does that downgrade the boards and all sbc (pi5) packages too?

jay_s_uk

@bug2k22 yes, it should do
If it only downgrades DSF/DWC you can then issue M997 and M997 B20 to flash the firmware to the mainboard and toolboard

bug2k22

@jay_s_uk The second M997 S2 command did flash up a notice saying it was upgrading, but nothing seems to have changed, restarting the board shows the 3.6.0-beta.2 firmware on all boards and the sbc packages are still on 3.6.0-beta.2.
If I ssh in to the pi, I see that the duet3d.list is now showing "deb https://pkg.duet3d.com/ stable-3.5 armv7" so it is on the stable channel but nothing downgrades.

jay_s_uk

@bug2k22 try running M997 S2 V"3.5.4"

bug2k22

@jay_s_uk Thanks, that did complete the downgrade on all boards and the pi.

Duet 3 MB6HC 	MB6HC 	3.5.4
Duet 3 Expansion TOOL1RR
TOOL1RR 	3.5.4
Duet Software Framework 	DSF 	3.5.4
Duet Web Control 	DWC 	3.5.4

This has not changed the behaviour, still no movement on the extruder motor.
I have just double checked the cable from the toolboard to the motor and connectivity is fine on all pins.

jay_s_uk

@bug2k22 in that case i'll leave you back with @Phaedrux or @droftarts

droftarts

@bug2k22 Can you try moving your M906 (set motor current) to after the M584, for both the XYZ axes and E? See https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m906-set-motor-currents

Order dependency
This command must be later in config.g than any M584 command.

Ian

bug2k22

@droftarts Thanks Ian, it's now working!

I didn't look at M906 as it seems to work with the extruder connected directly to the 6HC even with it early in the config. Something to remember for future installs.

droftarts

@bug2k22 It would have been reverting the currents to the defaults, I think. I'm not sure what the Roto default is, may be 400mA, as it usually expects a Roto extruder, which uses a lower current motor, so might just not had enough current to turn yours.

Ian