How check if Katapult its installed?

General Discussion
1

Basic Information:

Printer Model: Ratrig vCore 31
MCU / Printerboard: Octopus Max + H36
Host / SBC rpi4
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

Hi,

After installing several updates on the MCU, and after a connection issue with the CAN board (H36 connected via CANbus), I assume it’s due to the difference in Klipper versions between the MCU and CAN board.

So I tried updating the CAN board (Fytsec 36), but I couldn’t.

I want to check what bootloader is installed. I think it might be Katapult, but I can’t remember exactly.

How can I find out what bootloader is installed on the CAN board?

and

And by the way, also check the version of Klipper that I have installed on the Canboard, since I can’t see it through Fluidd (there is no connection to the Canboard)

klippy.log (476.6 KB)

2

Another temporary option…

Is there any way to downgrade Klipper (on the MCU) without KIAUH?
I tried with KIAUH and it didn’t work. I guess why not install Klipper with KIAUH?

3

After several tests, I managed to get it working… I don’t know why it didn’t work, but I’m posting what I did in case you see a reason.

01: I sent “lsusb” through the console and it responded with this

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH
Bus 001 Device 004: ID 1d50:606f OpenMoko, Inc. Geschwister Schneider CAN adapter
Bus 001 Device 006: ID 1d50:614e OpenMoko, Inc. stm32h723xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

CAN adapter worked

02: I have sent by console “ip -s -d link show can0”
and has returned

3: can0: <NOARP,ECHO> mtu 16 qdisc noop state DOWN mode DEFAULT group default qlen 128
link/can promiscuity 0 allmulti 0 minmtu 0 maxmtu 0
can state STOPPED restart-ms 0
bitrate 1000000 sample-point 0.750
tq 62 prop-sec 5 phase-sec1 6 phase-sec2 4 sjw 2 brp 3
gs_usb: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp_inc 1
clock 48000000
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 0 0 0 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 parentbus usb parentdev 1-1.2:1.0
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0

I understood that the CAN0 network was DOWN (stopped… Why?)

03: I sent “sudo ip link set can0 up” through the console to “turn on” the CAN0 network

04: I sent “ip -s -d link show can0” again to check the status of the CAN0 network again, and returned

3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 128
link/can promiscuity 0 allmulti 0 minmtu 0 maxmtu 0
can state ERROR-ACTIVE restart-ms 0
bitrate 1000000 sample-point 0.750
tq 62 prop-sec 5 phase-sec1 6 phase-sec2 4 sjw 2 brp 3
gs_usb: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp_inc 1
clock 48000000
re-started bus-errors arbit-lost error-warn error-pass bus-off
0 0 0 0 0 0 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 tso_max_size 65536 tso_max_segs 65535 gro_max_size 65536 parentbus usb parentdev 1-1.2:1.0
RX: bytes packets errors dropped missed mcast
0 0 0 0 0 0
TX: bytes packets errors dropped carrier collsns
0 0 0 0 0 0

This time the status is UP

I have been able to access Fluidd…

But… Why would he have stopped?