Heater fault but not accurate

wdenker

First reboot the temp shows N/A second reboot finally shows the proper temps. Went and updated to latest release 3.3 and now is stuck showing n/a for the temp on my hotend. Any ideas?

wdenker

 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 (standalone mode)
Board ID: 08DJM-956L2-G43S8-6J9F8-3S86R-9B3AF
Used output buffers: 3 of 40 (12 max)
=== RTOS ===
Static ram: 150904
Dynamic ram: 92348 of which 476 recycled
Never used RAM 110464, free system stack 202 words
Tasks: NETWORK(ready,27.1%,270) ETHERNET(notifyWait,0.1%,124) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,799) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.6%,93) MAIN(running,64.5%,924) IDLE(ready,0.5%,29), total 100.0%
Owned mutexes:
=== Platform ===
Last reset 00:00:23 ago, cause: software
Last software reset at 2021-06-23 15:08, reason: User, GCodes spinning, available RAM 110464, 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
Step timer max interval 128
MCU temperature: min 39.6, current 40.1, max 40.3
Supply voltage: min 23.9, current 23.9, max 24.0, 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 61613, writes 15 timeouts 0, SG min/max 0/0
Driver 1: position 0, standstill, reads 61614, writes 15 timeouts 0, SG min/max 0/0
Driver 2: position 0, standstill, reads 61615, writes 14 timeouts 0, SG min/max 0/0
Driver 3: position 0, standstill, reads 61615, writes 14 timeouts 0, SG min/max 0/0
Driver 4: position 0, standstill, reads 61618, writes 11 timeouts 0, SG min/max 0/0
Driver 5: position 0, standstill, reads 61618, writes 11 timeouts 0, SG min/max 0/0
Date/time: 2021-06-23 15:09:34
Slowest loop: 5.59ms; 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
Heater 0 is on, I-accum = 0.2
=== 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 221, received 106, lost 0, longest wait 2ms for reply type 6031, peak Tx sync delay 246, free buffers 49 (min 48), ts 116/115/0
Tx timeouts 0,0,0,0,0,0
=== Network ===
Slowest loop: 2.08ms; 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

wdenker

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 4400 words
Tasks: Move(notifyWait,0.0%,160) HEAT(delaying,0.0%,118) CanAsync(notifyWait,0.0%,69) CanRecv(notifyWait,0.0%,82) 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:01:07 ago, cause: software
Last software reset data not available
Driver 0: position 0, 80.0 steps/mm,  standstill, reads 64796, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 1: position 0, 80.0 steps/mm,  standstill, reads 64797, writes 11 timeouts 0, SG min/max 0/0, steps req 0 done 0
Driver 2: position 0, 80.0 steps/mm,  standstill, reads 64797, writes 11 timeouts 0, SG min/max 0/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 -2/10, peak Rx sync delay 177, resyncs 0/0, no step interrupt scheduled
VIN: 24.0V, V12: 12.2V
MCU temperature: min 35.6C, current 35.6C, max 35.8C
Ticks since heat task active 64, ADC conversions started 67687, completed 67687, timed out 0, errs 0
Last sensors broadcast 0x00000000 found 0 69 ticks ago, loop time 0
CAN messages queued 25, send timeouts 0, received 619, lost 0, free buffers 37, min 37, error reg 10000
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0

wdenker

Was a mismatched version on the expansion board. Need to update the how to update firmware wiki as it doesn't mention M997 B1 for the expansion board I had to find it in the depths of getting started with duet 3.

Phaedrux

How did you perform the firmware update?

I think 3.4 is supposed to have improvements to automate the update on expansion board firmware update process.

I'll see about adding a note to the firmware update wiki regarding M997 B1

wdenker

@wdenker now my E drive isn't honoring the microstepping and steps per mm.

Phaedrux

Can you share your config.g?

wdenker

@phaedrux I had to load the firmware into the new firmware folder then M997 B1 but even the getting started documentation shows that it should be in the sys folder. I am guessing the firmware folder is just that new since none of my other machines have it yet.

wdenker

@phaedrux config (16).g

Phaedrux

Yes the firmware folder is new as of 3.3 and was added in an effort to tidy up the /sys folder now that there are many firmware files for all of the expansion boards, etc.

Phaedrux

@wdenker said in Heater fault but not accurate:

@wdenker now my E drive isn't honoring the microstepping and steps per mm.

If you send M92 and M350 by themselves in the gcode console, what do they report as? How are they not being honored?

Can you also send M98 P"config.g" and report any errors?

wdenker

@phaedrux I lost the 120 hour print on it and rebooted and now it is all working as expected.