Thermocouple Error : "String too long" with RRF 3.3 stable
-
Using a Duet 6HC motherboard + Duet 3HC daughter-board, 2 thermocouples connected to the thermocouple board V1.1 on the 3HC
Firmware Version: 3.3 stable June 16Configuration of Thermocouples :
M308 S1 P"1.spi.cs1" Y"thermocouple-max31856" K"k" ; configure sensor 1 as thermocouple on pin sp1.cs1 expansion board 1 M950 H1 C"1.out0" T1 ; create nozzle heater output on 1.out0 and map it to sensor 1 M143 H1 S498 ; set temperature limit for heater 1 to 498C M307 H1 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit M308 S2 P"1.spi.cs0" Y"thermocouple-max31856" K"K" ; configure sensor 0 as thermocouple on pin sp1.cs0 expansion board 1 M950 H2 C"1.out1" T2 ; create nozzle heater output on 1.out1 and map it to sensor 2 M143 H2 S498 ; set temperature limit for heater 2 to 498C M307 H2 B0 S1.00 ; disable bang-bang mode for the nozzle heater and set PWM limit
It worked fine with RRF3.2.2
I switch to RRF 3.3, I get the error message :
M308 S1 P"1.spi.cs1" Y"thermocouple-max31856"
Error: M308: string too longThe heaters switch to error status
Tried with RFF 3.4.0 Beta 4, same error.
Switch back to RRF3.2.2, everything is OK...
What am I doing wrong?
-
@philippe71 thanks, this bug should be fixed in 3.4b5 in the mean time can you try removing the "-" , e.g:
M308 S2 P"1.spi.cs0" Y"thermocouplemax31856" K"K"
This may work.
-
Thank you Tony.
It works with RRF3.4.0 B5 with the "-" removed... -
@philippe71 said in Thermocouple Error : "String too long" with RRF 3.3 stable:
Thank you Tony.
It works with RRF3.4.0 B5 with the "-" removed...Does it work with the - remaining in b5
-
With RRF3.4.0 B5
thermocouplemax31856 > Works
thermocouple-max31856 > does not work -
@philippe71 please check which firmware version you have on the EXP3HC board, by sending M115 B1. That is where the bug was.
-
M115 B1 Duet EXP3HC firmware version 3.4.0beta5 (2021-10-12 13:58:36)
-
@philippe71 thanks, I marked this to be re-visited for the next 3.4 beta or RC.
EDIT: I found and fixed the other bug that was causing this.