RRC[

Rat Rig Community [Unofficial]•2y ago•

29 replies

Robee

Timer too close on V-Core 3.0 500 with Klipper

I've replaced my Duet board with an Octopus 1.1 and EBB36, plus RatOS, and now in the testing stage. Whenever I run the STEPPER_BUZZ commands, it triggers a timer too close error.

I'm running a Pi4, originally powered by a 3A DC-DC converter off the printer PSU, but even with an official external 3A Pi supply it occurs every time.

Not sure what to check, klippy logs attached in the hope they are some help.

The only things plugged into the Pi 4 are USB-A to USB-C to Octopus, and USB-A to USB-C to EBB36 toolboard. The EBB is powered with 24V from the printer PSU.

Everywhere I google they say it's probably a power issue, but I'm not sure how much more power I can give it.

klippy.log720.88KB

Solution

I have done a few things, so I'm not sure what has helped, and I won't count my chickens until they hatch, but I reformatted the octopus SD card to be blank FAT, reimaged the Pi SD card with the 2.1.0-RC2 image, made sure I updated everything in update manager before going further, began the whole setup again reflashing both the octopus board and EBB36 without any version mismatch warnings this time (it's interesting klipper version seems older in RC2 to what I had?), and so far I can move all the axis without any errors.

Jump to solution