[3.4.0b7] Firmware update changes 1LC temp

[Fumble]

@dc42
After installing that firmware and rebooting everything it gave the correct temperature

Checked I loaded the firmware ok as I'm not the best on linux

[jay_s_uk]

@dc42 I can confirm that the modified firmware also works for me

M308 S1
Sensor 1 type Thermistor using pin 20.temp0, reading 20.6, last error: sensor not ready, T:100000.0 B:4725.0 C:7.06e-8 R:2200.0 L:0 H:0

m122 b20
Diagnostics for board 20:
Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0beta7+1 (2021-12-18 13:47:42)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 3624, free system stack 2788 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(delaying,3.0%,57) MAIN(running,91.9%,293) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:01:28 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 397.5 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 37, reads 44066, writes 13, timeouts 0, DMA errors 0, CC errors 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 11/15, peak Rx sync delay 196, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 27.0, current 27.0, max 27.0
MCU temperature: min 34.2C, current 35.0C, max 35.0C
Last sensors broadcast 0x00000002 found 1 198 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 1743, send timeouts 0, received 1132, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: none
I2C bus errors 4509, naks 4509, other errors 4509

[dc42]

All, thanks for trying the new version. It's somewhat annoying to me that it works, because all I did was to add some extra M122 debug! So I'm no nearer finding the cause.

[OwenD]

@dc42
Not sure if it's related but for some reason last night I started having an issue where my Duet 2 wiFi would reboot after trying to use the input shaping plugin.
M122 showed last restart reason was something like HeatStuck (don't remember exact words)
I saw no stack errors or other obvious issues.
After several attempts reinstalling the plugin and restarting the duet2 from DWC, I did a cold restart (turned off power) and the problem disappeared.

[Marshal]

@dc42 I know that feeling

i case you are wondering.
going back to 3.4.0b7 will come up with low temperature again.

m122 b20
Diagnostics for board 20:
Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0beta7 (2021-12-16 12:25:01)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
Never used RAM 3648, free system stack 2788 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(delaying,3.0%,57) MAIN(running,91.8%,351) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:00:47 ago, cause: software
Last software reset time unknown, reason: AssertionFailed, available RAM 4592, slot 1
Software reset code 0x0120 ICSR 0x00000000 SP 0x20003cac Task  
 Freestk 130 bad marker
Stack: 00000544 00023174 00019cb5 20003044 00016e33 20003044 00016505 20000ed0 00000000 00000001 0000828d 200071c8 200071c8 200071e0 00000000 20000f50 000116b3 00022530 000225e8 00021c40 00019c55 200071c8 200071c8 20000f50 00008405 200071d8 000009c6
Driver 0: pos 0, 419.2 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 24, reads 23875, writes 12, timeouts 0, DMA errors 0, CC errors 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 4/9, peak Rx sync delay 579, resyncs 0/1, no step interrupt scheduled
VIN voltage: min 24.2, current 24.2, max 24.3
MCU temperature: min 29.2C, current 31.4C, max 31.4C
Last sensors broadcast 0x00000002 found 1 65 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 919, send timeouts 0, received 437, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: none
I2C bus errors 4509, naks 4509, other errors 4509

[Serge]

Hi, same issue with me
20/12/2021, 14:25:59 M122 B20
Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7+1 (2021-12-18 13:47:42)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2576, free system stack 2788 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,115) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) ACCEL(notifyWait,0.0%,61) TMC(delaying,3.0%,57) MAIN(running,91.9%,351) IDLE(ready,0.0%,26) AIN(delaying,4.9%,142), total 100.0%
Last reset 00:05:17 ago, cause: software
Last software reset data not available
Driver 0: pos 0, 830.0 steps/mm,standstill, SG min 0, read errors 0, write errors 1, ifcnt 35, reads 27864, writes 12, timeouts 0, DMA errors 0, CC errors 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 1/5, peak Rx sync delay 214, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.6, current 24.7, max 24.7
MCU temperature: min 30.6C, current 30.7C, max 30.8C
Last sensors broadcast 0x00000002 found 1 184 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 6288, send timeouts 0, received 2853, lost 0, free buffers 37, min 37, error reg 0
dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
Accelerometer: LIS3DH, status: 00
I2C bus errors 0, naks 3, other errors 0

[Serge]

@serge
20/12/2021, 14:29:43 M308 S1 H999
Measured H correction for port "20.temp0" is -6

[Serge]

@serge After reboot, same temp values.
It seems the hotend temp value is correct, but not the bed temp than i have to calibrate.

[dc42]

@serge which temperature input on what board is the bed thermistor input connected to?

[Serge]

@dc42 Hi, the temp input for the bed is directly on the Duet 6.
; Heaters
M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed" ; configure sensor 0 as thermistor on pin temp0
M950 H0 C"out1" T0

[dc42]

@serge do you get a more accurate bed temperature reading if you revert to older main board firmware?

[Marshal]

@dc42
No issue with bed thermistor here:

M308 S0 P"0.temp0" Y"thermistor" T100000 B4725 C7.06e-8

[Serge]

@dc42 Hi, no, don't get more accurate.

[Serge]

@marshal Here is the documentation from RatRig

[A Former User]

This post is deleted!

[dc42]

@serge thanks, so this is not an issue with firmware 3.4.0beta7 in particular.

Have you run temperature input calibration on input temp0 of the main board (where the bed heater is connected)?

[Serge]

@dc42 No, i don't.
Did you think i have to modify the B3950 to B4725 ?
I don't know what thermistor is for B3950.

[dc42]

@serge try running ADC calibration on that input, see https://duet3d.dozuki.com/Wiki/Calibrating_thermistor_and_PT1000_readings#Section_Semi_automatic_calibration.

[Serge]

@serge I made the modification to the B4725, and the bed temperature seems to be much more real now.

I think i will try whith this value now.

[Serge]

@serge