Exception in flush_handler

General Discussion
1

Basic Information:

Printer Model: Voron 2.4 R2 - Voron TAP - ERCF v2 12 channel - Custom Dryboxes
MCU / Printerboard:

  • MCU: Octopus Pro v1.1 (STM32H723ZET6)
  • MMU: MMB CAN V2.0 (STM32G0B1RET6)
  • EBB36: EBB36 (STM32G0B1)
  • keb_db_right: SKRAT v1 (STM32G0B1)
  • keb_db_left: SKRAT v1 (STM32G0B1)
    Host / SBC: Super Micro X13SAV-LVDS
    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:

Got “Exception in flush_handler“ given you are currently focused on those modules. Figured this would be helpful.

klippy (23).zip (3.7 MB)

2

Can you determine the issue is not generated by one of these extras?

Git version: 'v0.13.0-320-gc80324946-dirty'
Untracked files: klippy/extras/led_effect.py, klippy/extras/mmu_encoder.py, klippy/extras/mmu_espooler.py, klippy/extras/mmu_led_effect.py, klippy/extras/mmu_leds.py, klippy/extras/mmu_machine.py, klippy/extras/mmu_sensors.py, klippy/extras/mmu_servo.py

In other words: Have you tried with a genuine Klipper setup (The "dirty" Flag and the Team's Position)?

3

Hi @JesNoFear ,

Please make sure you’ve updated Happy Hare to the latest version with:

cd ~/Happy-Hare
./install.sh

There were some relatively recent updates to make it compatible with the new Klipper updates.

4

Mind you, I am functional. This does seem to be a low rate error that is occuring currently at the beginning of a print. Was just proving feedback in case othere are experiencing issues, or feedback / details on how the new code is working.

I’ve been reading the change logs, there was a fair amount of work on this module.

5

Update your Klipper installation. Kevin recently pushed a patch that fixes potential stepcompress errors.

6

As mentioned above, the upstream Klipper repository had an error (commit b60804bb - applied on September 15th) that was recently fixed (commit c49dbb5a - applied on October 4th). The error could result in sporadic “step compress errors”. It is recommended to update to the latest code to avoid the issue.

-Kevin