Basic Information: Printer Model: Homebrew coreXY, heavily based on HevOrt MCU / Printerboard: BBT Octopus 1.1 klippy.log Hi, i’m new here, this is my first topic, english is not my mother language, so I’d like to ask for your patience. My issue started with an update of MCU Firmware, coming…

It looks like you recently compiled and flashed your main mcu with an incorrect clock frequency. The code is reporting that the main mcu was compiled for 180Mhz, but the host is detecting that it is actually running at 270Mhz. This can lead to all sorts of issues (and makes it very hard to debug o…

[image] LifeOfBrian: I’m now waiting for my new bed to arrive… … hmm, what is coming up there if you already have this: [image] LifeOfBrian: I had a 10 mm cast aluminum bed made me curious …

[image] limefrog: but I’m afraid the game for my Octopus seems to be over. What bothers me a bit: “Timer too close” is an error more related to the host than to the board. Of course, some interaction between the board and host can apparently also be causing this, but still more host related.

I understand, but why are my neo pixels gone? That is only related to the board, right?

This is just to exclude all possibilities. In fact (and with pretty much everything in Klipper) the updating of the LEDs with new color information etc. is done on the host and then send to the board for execution.

Can the timer too close result from the 256 microsteps? The NoName is upgraded to triple Z and therefor the old bed was too big and could not be used in its entirety anyway.

[image] LifeOfBrian: Can the timer too close result from the 256 microsteps? The 256 microsteps are history, I’m already running with 32 microsteps with interpolation on every stepper (XY+Z+E) since you mentioned that. [image] LifeOfBrian: Check with 32 msteps for X and Y. On the othe…

[image] Sineos: …is done on the host and then send to the board for execution. O.k. RPi is head, Octopus is hand. So, head tells hand to do something, hand does (XY-axis) or fails (pixel) but don’t give feedback to head, so head thinks: “forget about it” and tells me: “Timer too close”. And…

[image] Sineos: Strip the config of all things unnecessary to print, i.e. [neopixel Neopixel] [temperature_fan Octopus_01] [temperature_sensor PI_3B+] [temperature_sensor Bauraum] [mcu rpi] [adxl345] [input_shaper] Done - no change

[image] Sineos: Check power supplies for both board and RPi under load Power supply is done with a benchtop power supply capable to deliver 10A set to 24V and feeds the octopus, while the RPi is fed with 5V directly from the Octopus (J26). When homing is running on Z-axis (three Motors) the …

Strange behavior on XY-movement after update

General Discussion

Sineos January 29, 2024, 8:59pm 49

The error for generating too many steps would be Rescheduled timer in the past

Topic		Replies	Views
"Can not update MCU 'mcu' config as it is shutdown" Error When Setting Up Octopus V1.1 Board General Discussion	0	1547	September 10, 2021
MCU 'mcu' shutdown: General Discussion	47	2067	December 16, 2024
Unable to read tmc uart 'stepper_y' register IFCNT General Discussion	22	853	July 8, 2025
V0.13.0-549 on Flsun Super Racer, no joy (and much pain) General Discussion	34	734	March 22, 2026
Klipper Internal error on command:"G1" General Discussion	33	806	May 4, 2025

Strange behavior on XY-movement after update

Related topics