Problem with V0.12

General Discussion
1

I will describe the problems I encountered after switching to the new Klipper version 0.12.
My config:
Voron V2R4 350x350 LDO,
Stealthburner,
Neopixel chamber,
BARF neopixel stealthburner,
BTT Manta M8P ( mcu CANbus connection)+CB1,
BTT EBBcan SB2209 STM32G0 mcu (CAN connection),
BTT HDMI7.

Problems:

  1. Flashing mcu Manta M8P is not possible via CanBoot, CB1 does not see mcu even if stop Klipper services.
  2. communication breakdown with mcu and EBBcan during printing randoml - Timer too close.

What I did in order:

  1. Flashing mcu Manta M8P via microSD
  2. After flashing mcu Manta M8P to version 0.12, you need turn on the printer, go to SSH terminal, stop Klipper services, press RST button on EBBcan board, then you can reflash the Stealthburner board via CanBoot
  3. After switching to version 0.12, I faced the problem of randomly communication failure with mcu and there was no particular pattern or any clues in the Klipper log file. Only one thing was confusing - high load of EBBcan compared to mcu. After digging through the whole 30Mb log file I noticed the neopixel Led-effect warning. I decided to disable BARF on my Stealthburner. After disabling it, EBBcan load became the same as mcu load. Random failure “timer too close” went away.

Bottom line: Everything works except BARF neopixel Led-effect. Very inconvenient upgrade, so if you decide to upgrade to clipper version 0.12 make sure you have access to the board to reflash the mcu via microSD.

Post scriptum: I ask developers to think about new bootloader for CAN, also I recommend to go to CYPHAL and Kocherga - very interesting projects and no timer too close problem.

2

Update:
Hey, everybody!
My actions with BARF and neopixel did not help. After 5 hours of printing again failure. This failure used to happen after 30-40 minutes.
Before upgrading the whole system I was running only on v0.10 with no crashes and decided to finally upgrade. Better not do it :slight_smile:

3

Build file /home/biqu/klipper/klippy/…/out/klipper.dict(7876): Thu Feb 1 11:23:11 2024
Last MCU build version: v0.12.0-102-g9f41f53c
Last MCU build tools: gcc: (15:8-2019-q3-1+b1) 8.3.1 20190703 (release) [gcc-8-branch revision 273027] binutils: (2.35.2-2+14+b2) 2.35.2
Last MCU build config: ADC_MAX=4095 BUS_PINS_i2c1_PA9_PA10=PA9,PA10 BUS_PINS_i2c1_PB6_PB7=PB6,PB7 BUS_PINS_i2c1_PB8_PB9=PB8,PB9 BUS_PINS_i2c2_PB10_PB11=PB10,PB11 BUS_PINS_i2c2_PB13_PB14=PB13,PB14 BUS_PINS_i2c3_PB3_PB4=PB3,PB4 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 CANBUS_FREQUENCY=1000000 CLOCK_FREQ=64000000 MCU=stm32g0b1xx PWM_MAX=255 RECEIVE_WINDOW=192 RESERVE_PINS_CAN=PB0,PB1 RESERVE_PINS_crystal=PF0,PF1 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1
Build file /home/biqu/klipper/klippy/…/out/klipper.elf(1061664): Thu Feb 1 11:23:22 2024
mcu ‘mcu’: Wait for identify_response
Traceback (most recent call last):
File “/home/biqu/klipper/klippy/serialhdl.py”, line 68, in _get_identify_data
params = self.send_with_response(msg, ‘identify_response’)
File “/home/biqu/klipper/klippy/serialhdl.py”, line 261, in send_with_response
return src.get_response([cmd], self.default_cmd_queue)
File “/home/biqu/klipper/klippy/serialhdl.py”, line 318, in get_response
self.serial.raw_send_wait_ack(cmds[-1], minclock, reqclock,
File “/home/biqu/klipper/klippy/serialhdl.py”, line 253, in raw_send_wait_ack
self._error(“Serial connection closed”)
File “/home/biqu/klipper/klippy/serialhdl.py”, line 61, in _error
raise error(self.warn_prefix + (msg % params))
serialhdl.error: mcu ‘mcu’: Serial connection closed

4

These information is really important! Without that, you’ll get no helpful answer!

klippy.log

Please post your log!

Good luck, hcet14

1 Like
5

I also had quite a lot of trouble after updating from v0.10 to v0.12, you can see the whole story and the solution here.

After all it was a mistakenly compiled firmware I uploaded to my MCU.

I’m still unsure if something changed in the default presets for compiling the firmware, since in earlier versions it worked out of the box.

6

Hi!
It
It is latest log file.
klippy (9).log (7.2 MB)

7

See Mcu: Serial connection closed / Timeout on connect / Wait for identify_response

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.