After updating to 3.4.0beta2: faulty heater 1, -273.1C.

[dc42]

@serge thanks, that error is one for @chrishamm.

[Serge]

@dc42
Thanks, i have to send him the bug ?

[dc42]

@serge said in After updating to 3.4.0beta2: faulty heater 1, -273.1C.:

@dc42
Thanks, i have to send him the bug ?

No, I have asked him to look at your post.

[dc42]

@juliann, to help me diagnose this, please can you reload the new tool board firmware, then send M308 S1 with no further parameters, and report the response.

[juliann]

@dc42 said in After updating to 3.4.0beta2: faulty heater 1, -273.1C.:

M308 S1

After reloaded the new 3.4b2 firmware on the toolboard the behaviour changed. The reading is not good but now the heater is active instead of faulty (and temp should be around 25C).

M308 S1:

M308 S1
Sensor 1 type Thermistor using pin 20.temp0, reading 7.4, last error: sensor not ready, T:500000.0 B:4723.0 C:1.20e-7 R:2200.0 L:-5 H:-9```

[dc42]

@juliann thanks. I am looking into it.

[Serge]

@juliann Yes, exactly the same issue i have.

[Serge]

@dc42 Same for me.

And after a very long time idle, the sensor temp works around the bed sensor temp but is very unstable :

Enregistrement d'écran 2021-08-03 à 17.53.47.mp4

[juliann]

@serge said in After updating to 3.4.0beta2: faulty heater 1, -273.1C.:

@juliann Yes, exactly the same issue i have.

Yes @Serge I think you are correct, it seems we have exactly the same issue now.

[Serge]

Rolling back the toolboard firmware to 3.3, and no issue than 6° higher for the hotend than the bed sensor. But stable.

[empi00]

I can confirm also a kind of this bug.

Before the update I had around 29°C on the HotEnd.

M308 S1 P"121.temp0" Y"thermistor" A"HotEnd" T100000 B4725 C7.06e-8

[empi00]

@empi00
Flashing back to 3.3 and:

PS: Using Duet3 with SBC and Toolboard 1.1

[dc42]

@empi00 I am wondering whether it just needs different calibration. Please can you:

1. Send M308 S1 (assuming the tool board thermistor is Sensor 1) and record the result, in particular the H and L values.
2. Send M122 B121 and record the reported VIN value
3. Switch the tool board firmware to 3.4beta2.
4. Send M308 S1 again, check that it reports the same H and L
5. Send M122 and check tna the reported VIN value is the same as before
6. Run the calibration procedure described at https://duet3d.dozuki.com/Wiki/Calibrating_thermistor_and_PT1000_readings on the tool board thermistor input. If it's tricky to do the short-circuit calibration test, just do the open-circuit calibration, which should be sufficient to correct the reading at room temperature.
7. Send M308 S1 again to see the new H and L values
8. Check whether the readings are now correct.

I am assuming that you do not have H and L parameters in your M308 commands in config.g, so it will use the values stored in NVRAM.

[chrishamm]

@serge said in After updating to 3.4.0beta2: faulty heater 1, -273.1C.:

NullReferenceException

If you manage to reproduce this, please open a Linux console and send journalctl -u duetcontrolserver -e --no-pager and send me the output. It should contain the stack trace of the underlying exception, which should make it easier for me to fix.

[uneumann36]

Hey guys.
So i am not an expert in programing stuff.

I change a lot on my modified Ender5 in the last week.
Try different hotends (THC-01 , Cyclops+ original , Cyclops fake , 2 in 1 out)
Update to capacitive sensor........

Everytime i got bad printing results. Lot of stinging and so on.

Today, i swop back to firmware 3.3.0 and print the same stinging test what was on the sd cart.
I am supprised!
Have a look on the picture yourself.
I do not know if it has to do with the firmware...
But i only change the firmware.

Don´t understand me wrong, i like duet products, and this should only help you.

[dc42]

@uneumann36 hanks for your feedback. It would be helpful if you could run the tests that I asked for in my response to @empi00, which is about 3 posts before this one.

[empi00]

@dc42
I will.
But i can only do it wednessday earlierst, as I am out with my family the next days!

[dc42]

BTW I am running two tool boards in one of my machines, and I don't see this issue. I've already reviewed all the code changes twice looking for changes that might be relevant.

[pixelpieper]

If you need an other datapoint: it also happens with PT1000.

(Duet 3 Mini5+ / Duet 1LC V1.1)

[dc42]

@pixelpieper thanks for that. It looks like something is affecting the ADC accuracy. It may be just a timing issue affecting the calibration, which is why I would like users who experience this issue to measure the H and L values that are set by the calibration process. Version 1.1 tool boards are calibrated during manufacture using firmware 3.3.