[3.4.0b7] Firmware update changes 1LC temp

[rjenkinsgb]

@serge said in [3.4.0b7] Firmware update changes 1LC temp:

Have you try the semi automatic calibration ?

Yep, I mentioned I had done that and the output from it was the first insert above.

[dc42]

@rjenkinsgb said in [3.4.0b7] Firmware update changes 1LC temp:

I have just loaded the beta7-1 toolboard firmware and power cycled the machine; no change.

Do you mean beta7+1 ?

If you are certain that your PT1000 is reading correctly (which depends on how accurate your multimeter is), you can adjust the M308 L parameter manually to correct the PT1000 reading at low temperatures.

[rjenkinsgb]

@dc42 said in [3.4.0b7] Firmware update changes 1LC temp:

Do you mean beta7+1 ?
If you are certain that your PT1000 is reading correctly (which depends on how accurate your multimeter is), you can adjust the M308 L parameter manually to correct the PT1000 reading at low temperatures.

Yes, that's the version; I was not paying attention - though I should have seen it in the M122 output...

OK on the M308 - but what's the likelihood of it being significantly off at working temperatures?

I do trust the meter, it's a calibrated Fluke 187.

[oozeBot]

@dc42 I'll add to the mystery as I just updated 3 machines - all in SBC mode with a 6hc and a toolboard.

The first is an older machine with a Slice thermistor on temp0 (and temp1 is not utilized). It reported "Heater 1 fault: failed to read sensor: sensor open circuit" after upgrading to 3.4b7. Manually upgrading the toolboard to 3.4b7+1 resolved the issue and the temp reported by toolboard temp0 is equal 3.4b6.

The second machine is using a Slice PT1000 on temp0 and a thermistor on temp1. After upgrading to 3.4b7, both temps remained equal to 3.4b6. The temps remained the same after upgrading to 3.4b7+1.

The third machine is identical to the second machine - the only difference is the Raspberry Pi image has been upgraded to Bullseye for testing. After upgrading to 3.4b7, temp0 rapidly fluctuated between 9-15c (where it should read ~22c). Temp1also rapidly fluctuated between 18-22c (where it should read ~25c). Manually upgrading to 3.4b7+1 resolved the issue for both temp0 and temp1.

[Alex.cr]

@dc42

To add another data point. Similar to my original post. I went ahead and updated to beta 7+2 to see if it fixed a heating issue on my 1LC and the temp dropped to about 4C at ambient again. Switching bat to 7+1 reverts the temp to normal(18C) ambient values.

[dc42]

@alex-cr thanks for that. Something strange is happening, possibly related to the alignment of a particular piece of code that reads the ADC. Unfortunately all the tool boards I have here don't show any difference between firmware versions, so I can't reproduce this.

[PCR]

@dc42 have you tried it with the HT thermistors?

Best

[rjenkinsgb]

I've cheated with my PT1000:
I now have it set as a thermistor, so I can adjust the parameters.

This appears to work, though I've not tried a print with that tool again yet:

M308 S1 P"20.temp0" Y"thermistor" A"T0" T1070 B-416

[dc42]

@alex-cr and anyone else getting incorrect readings using 3.4.0beta7+2, please post a M122 B# report where # is the tool board number.

[dc42]

@pcr said in [3.4.0b7] Firmware update changes 1LC temp:

@dc42 have you tried it with the HT thermistors?

I've tried to day using a 470K resistor, to simulate a high temperature thermistor. I get the same range of readings (fluctuating over a range of about 1.5C) using RRF 3.4b6, 3.4b7, 3.4b7+1 and 3.4b7+2.

[Alex.cr]

@dc42

As requested!

m122 b20
Diagnostics for board 20:
Duet TOOL1LC rev 1.1 or later firmware version 3.4.0beta7+2 (2021-12-30 22:07:52)
Bootloader ID: SAMC21 bootloader version 2.3 (2021-01-26b1)
All averaging filters OK
Never used RAM 2552, free system stack 2788 words
Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.2%,111) 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:02:00 ago, cause: power up
Last software reset time unknown, reason: AssertionFailed, available RAM 3392, slot 0
Software reset code 0x0120 ICSR 0x00000000 SP 0x2000415c Task  Freestk 129 bad marker
Stack: 00000544 00022ffc 00019b65 20003134 00016cff 20003134 000163d1 20000ed0 00000000 00000001 00008275 200071c8 200071c8 200071e0 00000000 20000f50 00011647 000223b8 00022474 00021ac8 00019b05 200071c8 200071c8 20000f50 000083ed 200071d8 000009c7
Driver 0: pos 0, 406.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 12, reads 60259, 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/9, peak Rx sync delay 204, resyncs 0/0, no step interrupt scheduled
VIN voltage: min 24.2, current 24.3, max 24.3
MCU temperature: min 37.4C, current 37.4C, max 38.0C
Last sensors broadcast 0x00000004 found 1 77 ticks ago, 0 ordering errs, loop time 0
CAN messages queued 2427, send timeouts 0, received 1575, 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

[leobg]

@dc42 said in [3.4.0b7] Firmware update changes 1LC temp:

@alex-cr and anyone else getting incorrect readings using 3.4.0beta7+2, please post a M122 B# report where # is the tool board number.

Latest I found reference is 7+1, where is 7+2 linked? Another threat? What changed between +1 and +2 btw?

[Alex.cr]

@leobg
Linked in a different thread, copied here for your convivence:

@dc42 said in Expansion boards not working on 3.4b7?:

@theolodian please try the files at https://www.dropbox.com/sh/cx760ysonlzzkjd/AACfsVfX4olHipuqmbWut5EKa?dl=0. If the problem persists, please power the system off for several seconds and then on again, wait for startup to complete, and post the result of sending M409 K"boards" again.

[dc42]

@alex-cr thanks, the "All averaging filters OK" was what I wanted to see, to eliminate a possible cause.