After update issue

[Peurif]

Basic Information:

Printer Model: Vcore 31
MCU / Printerboard: Octopus Pro + EBB42(USB)
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:

Yesterday the printer was working fine, but this morning after updating I get this error…

I have updated the firmware of the MCUs, both Octopus and EBB42. But I still get this error.

and…

It seems to be related to the Zprobe (Beacon)

What could it be?

[Peurif]

mmm…

After rebooting… I NO LONGER get that error. But Fluidd can’t connect to Klipper…

I’m going to do some tests

[SergeiDubovsky]

It’s the Beacon. It will auto-update and error will go away

[Peurif]

I update with new information.

I still can’t connect to Klipper, but with some changes.

I have updated the EBB42 Firmware with the help of a PC, and the most important change occurs now.

When I connected the EBB42 to the rPi, I followed this procedure:

01 - Via console, I sent the command “lsusb”, which resulted in:

pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 1d50:614e OpenMoko, Inc. stm32f446xx
Bus 001 Device 004: ID 04d8:e72b Microchip Technology, Inc. Beacon RevH
Bus 001 Device 003: ID 1d50:6177 OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d50:614e OpenMoko, Inc. stm32g0b1xx 1d6b:0002 Linux Foundation 2.0 root hub

With this I check that Rpi “sees” the 3 boards:

Octopus Pro on Bus 001 Device 006
Beacon on Bus 001 Device 004
EBB42 on Bus 001 Device 003

02 - I check the name of the USBs for Klipper, for this I send the command “ls /dev/serial/by-id/”, with the result of: (I separate it in lines so that it can be “read” better, but the response in the console is in 1 line

usb-Beacon_Beacon_RevH_A0BB93794E5737374D202020FF093421-if00
usb-katapult_stm32g0b1xx_47001A001650415833323520-if00
usb-Klipper_stm32f446xx_33000B000E50315939343520-if00

*This is where the biggest change is, after updating the firmware with the PC on the EBB42, its name has changed from ( /dev/serial/by-id/usb-Klipper_stm32g0b1xx_47001A001650415833323520-if00) to (usb-katapult_stm32g0b1xx_47001A001650415833323520-if00)

I have updated the name in the Klipper configuration…

03 - Reboot and now the error is another one, I attach the screenshot and klippy.log.

This error. Is it possible that it occurs because I have everything that I had connected to the Canboard (Ebb42) disconnected?
Why has the name of the Ebb42 changed from “usb-Klipper…” to “usb-Katapult…”? (this is just curiosity)

Dia02 klippy.log (32.2 KB)

[Peurif]

After looking at the log again… it seems that the error is here:

Extruder max_extrude_ratio=0.266081
mcu 'mcu': Starting serial connect
Loaded MCU 'mcu' 125 commands (v0.12.0-207-g6cd17420 / gcc: (15:12.2.rel1-1) 12.2.1 20221205 binutils: (2.40-2+18+b1) 2.40)
MCU 'mcu' config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_i2c3=PA8,PC9 BUS_PINS_sdio=PC12,PD2,PC8,PC9,PC10,PC11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi2a=PC2,PC3,PB10 BUS_PINS_spi3=PB4,PB5,PB3 BUS_PINS_spi3a=PC11,PC12,PC10 BUS_PINS_spi4=PE13,PE14,PE12 CLOCK_FREQ=180000000 MCU=stm32f446xx PWM_MAX=255 RESERVE_PINS_USB=PA11,PA12 RESERVE_PINS_crystal=PH0,PH1 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1
mcu 'EBBCan': Starting serial connect
webhooks client 548526513744: New connection
webhooks client 548526513744: Client info {'program': 'Moonraker', 'version': 'v0.8.0-379-g346a3d7'}
mcu 'EBBCan': Timeout on connect
mcu 'EBBCan': Wait for identify_response
Traceback (most recent call last):
  File "/home/pi/klipper/klippy/serialhdl.py", line 68, in _get_identify_data
    params = self.send_with_response(msg, 'identify_response')
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/klipper/klippy/serialhdl.py", line 262, in send_with_response
    return src.get_response([cmd], self.default_cmd_queue)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/pi/klipper/klippy/serialhdl.py", line 319, in get_response
    self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
  File "/home/pi/klipper/klippy/serialhdl.py", line 254, in raw_send_wait_ack
    self._error("Serial connection closed")
  File "/home/pi/klipper/klippy/serialhdl.py", line 61, in _error
    raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu 'EBBCan': Serial connection closed

I don’t understand it much, but it seems as if there was some failure in the communication with EBB42…

But which? Maybe something related to the name change of the new firmware?

[Sineos]

Where is the mandatory klippy.log?

@Peurif

katapult_stm32g0b1xx_47001A001650415833323520-if00

This means your board is in the Katapult Bootloader mode. This mode is only used to program the board with a new firmware.
If the board constantly boots into this mode, then it means no Klipper firmware is installed.
If a Klipper firmware is installed and the board is reset / rebooted then it needs to return to Klipper_stm32g0b1xx_.... naming.

[Peurif]

thanks…

@Sineos

Where is the mandatory klippy.log?

I have uploaded the log in the previous messages, in this post I upload the updated one… But yes, I often forget

I have uploaded the log in the previous messages, in this post I upload the updated one…

I have installed the klipper firmware on the “normal” CanBoard, but the latest version…

And the errors from the beginning are reproduced, a similar error message…

I have been looking at the log, and I think it is related to Beacon3d… but I don’t understand in what sense. I seem to understand that the version of the firmware installed in Beacon is not the correct one… but I DON’T understand it

Dia02 klippy_afterupdate.log (605.0 KB)

Could someone tell me what to try?

EDIT: its possible thats, It may be a problem caused by Beacon, I just checked their discord, and at least one user is experiencing the same thing…

[Peurif]

Solved…

Confirm that, in my case, was a Beacon Issue…

I have find the solution in Beacon Channel in Discord.

Force update via console…

and now everything works again

Thanks for putting me on the right path