[3.4.0b7] Firmware update changes 1LC temp
-
@gixxerfast Downgrading I only updated the one toolboard. While I realise it might not be able to collect data using different firmware versions, I would have expected M122 to detect it ok
-
@dc42 Oh, mine is working fine with the v1.1 toolboard with a generic pt1000 and b7. I'm just butting in because it's interesting as I have the same setup and it's working fine ...
-
@dc42 I notice Alex-cr is running SBC+6HC+1LC as am I while Gixxerfast is Mini5
-
@dc42 said in [3.4.0b7] Firmware update changes 1LC temp:
please can you try connecting the thermistor or PT1000 to temp1 on the tool board, change config.g appropriately, and see whether the problem persists.
@dc42 I have confirmed that moving the PT1000 to temp1 did not resolve the issue. The problem persists.
-
@dc42
Additional issues are occurring now. Once I performed a new heater tuning on this extruder to test the new algorithm I cannot get the heater to turn on.The M303 completed correctly and I updated my M307 command in my config. Now when I use DWC, G10,M568, or M109/M104 commands the heater will just sit there and not heat.
Sending an M105 command confirms that the temps were requested.
If I send the appropriate M303 command the system will heat/tune and act correctly. Reuploading B6 to the 1LC restores the ability to use the heater. -
I can confirm the erratic temperature reading after upgrading to B7 with 1LC v1.1. SBC + 6HC + 1LC. Flashing back to B6 returns thermistor readings to normal. Slice Engineering Hight Temp thermistor (450C).
-
@dc42 same here. Dyze 450€ thermistor temp0 on toolboard. Reports open circuit after upgrade
-
Thanks. Please can those of you with the problem try the following:
-
Install the modified beta7 tool board firmware from https://www.dropbox.com/sh/5ubjszy9fmlvzwu/AAAeOMGP-Yi-Gn9LZwQoPfita?dl=0.
-
Check that the temperature reading is still incorrect.
-
Send M122 B# where # is the CAN address of the tool board.
-
Send M308 S# where # is the sensor number of the thermistor or PT1000 on the tool board.
-
Post the M122 and M308 responses here.
-
-
@dc42 Hi,
for me beta7+1 fixed the issue.
(theres a small typo in your post - 3. Send M121 B#)config.g - not changed
M308 S1 P"20.temp0" Y"thermistor" T100000 B4725 C7.06e-8
[3.4.0b7]:
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:02:33 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 10980, 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 5/8, peak Rx sync delay 213, resyncs 0/0, no step interrupt scheduled VIN voltage: min 24.2, current 24.2, max 24.3 MCU temperature: min 33.2C, current 35.9C, max 35.9C Last sensors broadcast 0x00000002 found 1 97 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 3054, send timeouts 0, received 1386, 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
M308 S1 Sensor 1 type Thermistor using pin 20.temp0, reading 13.5, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:2200.0 L:0 H:0
Readings:
[3.4.0b7+1]:
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 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(notifyWait,3.0%,57) MAIN(running,91.8%,341) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0% Last reset 00:04:12 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 51, reads 60503, writes 11, 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 214, resyncs 0/1, no step interrupt scheduled VIN voltage: min 24.2, current 24.2, max 24.3 MCU temperature: min 37.2C, current 37.6C, max 37.6C Last sensors broadcast 0x00000002 found 1 137 ticks ago, 0 ordering errs, loop time 0 CAN messages queued 4866, send timeouts 0, received 2276, lost 0, free buffers 37, min 37, error reg 50000 dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0 Accelerometer: none I2C bus errors 4509, naks 4509, other errors 4509
M308 S1 Sensor 1 type Thermistor using pin 20.temp0, reading 25.5, last error: success, T:100000.0 B:4725.0 C:7.06e-8 R:2200.0 L:0 H:0
Readings:
-
@dc42
After installing that firmware and rebooting everything it gave the correct temperatureChecked I loaded the firmware ok as I'm not the best on linux
-
@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
-
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.
-
@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. -
@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
-
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
20/12/2021, 14:29:43 M308 S1 H999
Measured H correction for port "20.temp0" is -6 -
@serge After reboot, same temp values.
It seems the hotend temp value is correct, but not the bed temp than i have to calibrate. -
@serge which temperature input on what board is the bed thermistor input connected to?
-
@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 -
@serge do you get a more accurate bed temperature reading if you revert to older main board firmware?