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. 🙂
Solution:Jump to 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 t...
20 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´
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?
Okay, i have only my mobile. In your klippy log i get this.
[mcu]
serial = /dev/btt-octopus-11
mcu 'mcu': Starting serial connect
mcu 'mcu': Unable to open serial port: [Errno 2] could not open port /dev/btt-octopus-11: [Errno 2] No such file or directory: '/dev/btt-octopus-11'
Are you sure your mcu is right?
yes, pretty sure, checked the STM32 chip is an F446, the board is marked bigtreetech octopus, and dmesg shows:
[ 2.451445] usb 1-1.2: new full-speed USB device number 4 using xhci_hcd
[ 2.563571] usb 1-1.2: New USB device found, idVendor=1d50, idProduct=614e, bcdDevice= 1.00
[ 2.563645] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.563675] usb 1-1.2: Product: stm32f446xx
[ 2.563698] usb 1-1.2: Manufacturer: Klipper
[ 2.563721] usb 1-1.2: SerialNumber: btt-octopus-11
Plus /dev/btt-octopus-11 exists
I removed modemmanager which fixed that error from appearing in the logs but otherwise has had no effect.
I've reflashed klipper on the octopus and despite this confusing message "Version mismatch
The board is running version v0.12.0-296-gcc4ad667 but you your pi is on version v0.12.0-296-gcc4ad6670. If you want to update your board click 'flash again' below"
Nothing's better :/
I have an SD card in the Octopus board if that matters? It was blank FAT32 formatted when I put it in there tho
Update ratos, that truncated version number has been fixed
You can leave the sd card in the Board, like TheTik said Update ratos and Post a new klippy log.
I think it is up to date already 😦
RatOS
v2.0.2-36-g230929e3
Oh, you're on 2.0, not 2.1
That's a weird error message then
Push a fresh klippy log.
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. 🤷♀️
Good progress!
Z-Tilt scared the hell out of me when my 500x500 bed started flying towards my nozzle, I emergency stopped that right away since I'd not even tested z homing
Yeah, make sure that z home sensor is working 😜