@smoki3 the SBC version uses /machine/status and not rr_status

Just for confirmation:
It's fixed!👍

@oliof That'll be because you haven't selected a tool. If you only have a single tool, then the simplest thing to do is put T0 somewhere in your config.g file. If you have multiple tools, put T(n) at the start of you slicer gcode to select whichever tool it is that you want to use.

Trying to increase the temp while also turning on the cooling fan is a pretty good way to trip the protection.

If possible, stagger the fan coming on until after the temp change.

@TypQxQ said in RRF 3.2RC1 - SPI task faulted on abort comand:

Thanks, I can confirm that. It will be fixed in RC2.

Good to hear that 😄
Thank you for the support

@Stephen6309 said in Wanting to try out new features.:

sudo rm /etc/apt/sources.list.d/duet3d.list

Thanks.
I did complete that step, but didn't mention it above (and probably should have).
My Duet3 has been has been on the non stable release for a few days now. Just updated to RC1. Have other things to work out before I can start printing again.... (need a new heating mat for the bed).

all working in RC1

Looks like this was a hardware issue after all, the crimp inside the hotend heater connector had gone bad so it was loosing conntact sporadicly.

Redid the crimps and no error's or issues so far😲

Please upgrade to RC1 and check if the problem persists.

I spent quite a while investigating this today. As it happens, a change in the firmware earlier this week caused an almost identical symptom on Duet 3 MB6HC, even with the F parameter corrected to Q! Without your report I would not have tested it. Anyway, it's fixed now.

@GTech It might also be worth getting a fresh Duet Pi image and redoing the Pi SD card and updating it from there, especially if you're using the same Duet Pi build that came on the card originally.

Thanks for reporting this, I've just fixed it in the upcoming RRF/DSF versions.

You may wish to try moving the Z motors and endstops to the mainboard to test.

Still no crash after 2 days.

Here are the services I disabled:

sudo systemctl disable lightdm sudo systemctl disable cups sudo systemctl disable wpa_supplicant sudo systemctl disable alsa sudo systemctl disable alsa-state sudo systemctl disable bluealsa sudo systemctl disable apt-daily-upgrade.timer sudo systemctl disable apt-daily.timer sudo systemctl disable bluetooth

@dc42 said in Toolboard extruding wrong direction after restart:

Try adding a G4 S1 command in config.g, somewhere near the start

That worked so far, tested it multiple times.

Thank You!

Yep, that fixed it. Thank you!

I must have copied the new format from the example in the config upgrade guide and forgot to change the 1 -> 2's.

Edit - unless something is obviously wrong in the M122, please dismiss for now. I've rerun this several times and have not been able to reproduce.

@chrishamm @dc42 - this just occurred (or something like it) on 3.2B4.1.

I received the following error:

Error: M280: Response timeout: CAN addr 20, req type 4012, RID=1163 289 points probed, min error -0.065, max error 0.470, mean 0.162, deviation 0.079

M122

=== Diagnostics === RepRapFirmware for Duet 3 MB6HC version 3.2-beta4.1 running on Duet 3 MB6HC v0.6 or 1.0 (SBC mode) Board ID: 08DJM-956L2-G43S4-6J1DD-3SJ6S-TB62H Used output buffers: 1 of 40 (40 max) === RTOS === Static ram: 123292 Dynamic ram: 138720 of which 148 recycled Never used RAM 130032, free system stack 128 words Tasks: Linux(ready,83) HEAT(blocked,297) CanReceiv(blocked,837) CanSender(blocked,344) CanClock(blocked,352) TMC(blocked,18) MAIN(running,669) IDLE(ready,19) Owned mutexes: HTTP(MAIN) === Platform === Last reset 00:43:58 ago, cause: software Last software reset at 2020-12-09 08:22, reason: User, GCodes spinning, available RAM 130032, slot 0 Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0xffffffff Task Linu Error status: 0x04 MCU temperature: min 29.2, current 40.4, max 40.5 Supply voltage: min 1.5, current 24.2, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes 12V rail voltage: min 0.2, current 12.1, max 12.2, under voltage events: 1 Driver 0: position 30480, standstill, reads 51957, writes 38 timeouts 0, SG min/max 0/982 Driver 1: position 0, standstill, reads 51973, writes 22 timeouts 0, SG min/max 0/0 Driver 2: position 1030, standstill, reads 51958, writes 38 timeouts 0, SG min/max 0/1023 Driver 3: position 0, standstill, reads 51949, writes 48 timeouts 0, SG min/max 0/474 Driver 4: position 0, standstill, reads 51976, writes 22 timeouts 0, SG min/max 0/0 Driver 5: position 0, standstill, reads 51950, writes 48 timeouts 0, SG min/max 0/1023 Date/time: 2020-12-09 09:06:06 Slowest loop: 999.73ms; fastest: 0.08ms === 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 === FreeDm 375 (min 370), maxWait 446390ms, bed compensation in use: mesh, comp offset 0.000 === MainDDARing === Scheduled moves 2007, completed moves 2007, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 5], 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 = 2 -1 -1 -1 Heater 0 is on, I-accum = 0.5 Heater 1 is on, I-accum = 0.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 15276, send timeouts 44, received 37057, lost 0, longest wait 2ms for reply type 6031, free buffers 47 === SBC interface === State: 0, failed transfers: 0 Last transfer: 18ms ago RX/TX seq numbers: 34609/34610 SPI underruns 0, overruns 0 Number of disconnects: 0, IAP RAM available 0x209ac Buffer RX/TX: 0/0-0 === Duet Control Server === Duet Control Server v3.2.0-beta4 Code buffer space: 4096 Configured SPI speed: 8000000 Hz Full transfers per second: 38.07

M122 B20

Diagnostics for board 20: Duet TOOL1LC firmware version 3.2-beta4.1 (2020-12-03) Bootloader ID: SAMC21 bootloader version 2.1 (2020-11-03b2) Never used RAM 4208, free system stack 72 words HEAT 50 CanAsync 89 CanRecv 83 TMC 54 MAIN 216 AIN 64 Last reset 00:44:32 ago, cause: power up Last software reset data not available Driver 0: position 0, 830.0 steps/mm, standstill, SG min/max 0/0, read errors 0, write errors 0, ifcnt 12, reads 25496, writes 12, timeouts 0, DMA errors 0 Moves scheduled 0, completed 0, in progress 0, hiccups 0 No step interrupt scheduled VIN: 24.2V MCU temperature: min 32.5C, current 56.5C, max 58.1C Ticks since heat task active 237, ADC conversions started 2661831, completed 2661830, timed out 0 Last sensors broadcast 0x00000002 found 1 241 ticks ago, loop time 0 CAN messages queued 37596, send timeouts 0, received 28817, lost 0, free buffers 36