Unable to extract params from: query_thermocouple - PT100 CANBUS EBB42

General Discussion
1

Basic Information:

Printer Model: Ender-5 Pro
MCU / Printerboard: SKR Mini E3 V2.0 // EBB42 V1.2 // Octoprint
klippy.log

Fill out above information and in all cases attach your klippy.log file. Pasting your printer.cfg is not needed
Be sure to check our Knowledge Base and in particular this and this post

Describe your issue:

…

CAN-BUS Config PT 100 with EBB V1.2

Parts of klippy.log

...
> CPU Protocol error
> 
> This is frequently caused by running an older version of the
> firmware on the MCU(s). Fix by recompiling and flashing the
> firmware.
> 
> Your Klipper version is: v0.11.0-105-g1e7057e9-dirty
> MCU(s) which should be updated:
> mcu: Current version v0.11.0-105-g1e7057e9
> EBBCan: Current version v0.10.0-557-gf7e29b27
> Up-to-date MCU(s):
> <none>
> 
> Once the underlying issue is corrected, use the "RESTART"
> command to reload the config and restart the host software.
> 
> mcu 'EBBCan': Unable to extract params from: query_thermocouple
> MCU Protocol error
> 
> This is frequently caused by running an older version of the
> firmware on the MCU(s). Fix by recompiling and flashing the
> firmware.
> 
> Your Klipper version is: v0.11.0-105-g1e7057e9-dirty
> MCU(s) which should be updated:
> mcu: Current version v0.11.0-105-g1e7057e9
> EBBCan: Current version v0.10.0-557-gf7e29b27
> Up-to-date MCU(s):
> <none>
> 
> Once the underlying issue is corrected, use the "RESTART"
> command to reload the config and restart the host software.
> 
> mcu 'EBBCan': Unable to extract params from: query_thermocouple

Part of printer.cfg

…
[extruder]
step_pin: EBBCan: PD0
dir_pin: !EBBCan: PD1
enable_pin: !EBBCan: PD2
microsteps: 16
rotation_distance: 33.500
nozzle_diameter: 0.400
filament_diameter: 1.750
heater_pin: EBBCan: PA2
#sensor_type: PT100 AD
#sensor_pin: EBBCan: PA3
sensor_type:MAX31865
sensor_pin: EBBCan: PA4
spi_bus: spi1a
rtd_nominal_r: 100
rtd_reference_r: 430
rtd_num_of_wires: 2

Is there a fault in the wiring of the PT100 on the EBB42 or a fault in the sensor itself. Or can the EBB firmware simply not collect the value (“query_thermocouple”) because the firmware is incorrectly compiled?
Can you try to query the values ​​using a python script?

Thanks!

LeDidier

2

It’s worth reading those links. In your case the 2nd one, point 5. The 3rd links point 4 always should be regarded.

“-dirty” ain’t good!

EBBCan: Current version v0.10.0-557-gf7e29b27
Up-to-date MCU(s):
none

… also.

Good luck, hcet14

3

I’ve used the pre-compiled firmware from BTT for the EBB42. Thats why the Release is 0.10. The new compiled from git pull has the same problem (query_thermocouple)!.
dirty version? Don’t know why. Nothing modificated.

4

Post your klippy.log

5

The log message should be pretty clear:

> This is frequently caused by running an older version of the
> firmware on the MCU(s). Fix by recompiling and flashing the
> firmware.
> 
> Your Klipper version is: v0.11.0-105-g1e7057e9-dirty
> MCU(s) which should be updated:
> mcu: Current version v0.11.0-105-g1e7057e9
> EBBCan: Current version v0.10.0-557-gf7e29b27
> Up-to-date MCU(s):
> <none>

The different “Klippers”, e.g. the part running on the host, the MCU and the CAN attached MCU apparently have different Klipper versions. Make sure to update all to the same version.

For a schematic how Klipper works see: Klipper Architecture / Ecosystem

6

Many thanks for the support.
I solved the problem. SP1a was specified in the specifications of BTT. SP1 then helped me.

Thank You!

Greeting
LeDidier

7

Pretty effectless thread till now. Neither SP1a nor SP1 are mentioned above your last post!
Could you please explain your solution?

1 Like