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. 🙂
10 Replies
that message can also mean the pi is trying to do too much at a time. You don't have a webcam or anything plugged in?
Did you set your tmc jumper? are the motor wires correct?
https://os.ratrig.com/docs/boards/btt/octopus-11/
its in your log
`Unable to obtain tmc extruder phase´
Solution
if this is all set, try another usb cable for the toolboard
No, i removed them all 😦
I did, motor wires match the diagram. :/ I'll try a new usb cable just in case
Oh wow, thank you @elpoepel, I replaced the USB cable that came with the Octopus board and now I can stepper buzz all-the-things!!! 💜
That's great, happy printing
I think I spoke too soon, I can buzz all the steppers but the moment I try to home any axis it reoccurs 😦
Can you drop your printer.cfg in here? Sounds like the raspi is trying to do too much at a time. But you've got a 4 and you can run it on a 3 so that seems weird
if you try to home you get the error, but do you get it if you just move an axis?
Can you post the new klippy.log?