@diy-o-sphere Huh, yeah that ain't right

@fcwilt I'm currently re-running the autotuning with the removed T, B, and C values from the config

@fcwilt it included M307 commands that were generated from the autotuning and saved using M500

@fcwilt Affirmative

@fcwilt Yes, all 3 faulted (nearly) simultaneously, when heating is initiated simultaneously

@fcwilt "Print will be terminated if a heater fault is not reset within 10 minutes"

The thing that keeps confusing me is that this is a very standard-issue setup. Running all standard E3D + Duet hardware, and running a stable release of the firmware.

@fcwilt Yes, toolboards are at the addresses assigned

@phaedrux Ask and you shall receive

@fcwilt It's a printer with 4 tools, just so happened that the 4th tool continued heating to ~120C before faulting (different M307 parameters). All 4 tools have the issue

Why would an Emergency Stop yield different results than a config save or a power on startup?

@jay_s_uk Yes

@kevinmar
For some bizarre reason, "Emergency Stop"-ing the machine works, and all the sudden the driver seems to be found by the machine when trying to move that axis. Why would this be?

I've been using the same config for about a month, and recently moved. During my first startup after 2 weeks of no printing, my printer said 1 of the drivers was not found. This was very strange because zero changes were made to the wiring or the firmware. I checked to see if my 3HC expansion board (address 2) was being found, and it was; the driver appeared to be showing up properly.
So I tried to send the M584 command in the console, to see if it would still return the error. Of note, all axis are linear, including "A" which is on 2.2

Running 3.4B3

I'd like to confirm that this beta fixed an issue I had with a tool board reading very erratic thermistor values which spiked up and down constantly.

Thanks!

I own 8 V1.1 tool boards, and all except one show the accelerometer is present.

That particular board is on a machine running 3.4.0b2, and the board is confirmed to be running that firmware.

Is there a way to 'wake up' the accelerometer? Or is it just a defective unit?

@fcwilt Yes, I've tried disabling the fan.
The heater that took longer to fault had different M307 parameters at that time

@fcwilt

m122
=== Diagnostics ===
RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
Board ID: 08DJM-9P63L-DJ3T8-6JKDD-3SD6M-9V4Z9
Used output buffers: 1 of 40 (16 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 63832 of which 12 recycled
Never used RAM 139444, free system stack 200 words
Tasks: SBC(ready,5.3%,298) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,302) CanReceiv(notifyWait,0.1%,799) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.4%,93) MAIN(running,87.0%,922) IDLE(ready,0.1%,29), total 100.0%
Owned mutexes: HTTP(MAIN)
=== Platform ===
Last reset 00:01:48 ago, cause: software
Last software reset at 2021-08-20 13:46, reason: User, none spinning, available RAM 139444, slot 1
Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
Error status: 0x00
Step timer max interval 134
MCU temperature: min 38.9, current 39.3, max 39.4
Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
12V rail voltage: min 12.1, current 12.1, max 12.2, 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 14442, writes 16 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 14442, writes 16 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 14443, writes 15 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 14447, writes 11 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 14443, writes 15 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 14445, writes 14 timeouts 0, SG min/max 0/0
Date/time: 2021-08-20 13:48:32
Slowest loop: 60.53ms; fastest: 0.04ms
=== 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 ===
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
Heater 0 is on, I-accum = 0.2
=== 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 1033, received 5285, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 7, free buffers 49 (min 48), ts 545/544/0
Tx timeouts 0,0,0,0,0,0
=== SBC interface ===
State: 4, failed transfers: 0, checksum errors: 0
Last transfer: 1ms ago
RX/TX seq numbers: 3860/3860
SPI underruns 0, overruns 0
Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
Buffer RX/TX: 0/0-0
=== Duet Control Server ===
Duet Control Server v3.3.0
Code buffer space: 4096
Configured SPI speed: 8000000Hz
Full transfers per second: 35.84, max wait times: 5.8ms/0.0ms
Codes per second: 1.10
Maximum length of RX/TX data transfers: 6116/716

@phaedrux The Hemera tool and V6 hotend are assembled correctly.
There is no adjustability to the fan duct, but the ducting is aimed down to the nozzle. It's a fan duct by Rene Jurack, evaluated by an aerodynamicist at BMW

@fcwilt It's a printer with 4 tools, just so happened that the 4th tool continued heating to ~120C before faulting (different M307 parameters). All 4 tools have the issue