what was the settings you used to create this file?
what do you mean by
I was building the firmware.bin file myself, per the klipper install instructions and details noted at the top of printer-anycubic-kobra-plus-2022.cfg
.
Ref:
https://www.klipper3d.org/Installation.html#building-and-flashing-the-micro-controller
The configuration in the notes of the cfg file noted the micro-controller and communication interface to select when running make menuconfig
, but not anything else (such as the ‘Clock Speed’. So I kept everything else the default. This set a clock speed of ‘168 MHz’.
This was giving me the Timer too close
error I noted when homing, and in digging around I noticed that the Mainsail interface showed the MCU had a freq of 200 Mhz. So I re-built the firmware.bin setting the ‘Clock Speed’ to match that, and that fixed the timer error.
That said, I’ve also begun getting the OvertempWarning!
on stepper_z now too…
So I figured out that the problem with OvertempWarning!
seems to be that the fan controlling the MCU board is tied to the heater bed temp in the default config.
[heater_fan controller_fan]
pin: PA14
heater: heater_bed
heater_temp: 45.0
So the fan cooling the control board would only kick on if the bed was at 45+. For me, this explains why I was only encountering OvertempWarning!
when I wasn’t printing but the stepper motors were still on (so idle, basically).
On some other’s advice I replaced that section of the config with this.
[controller_fan electronics]
pin: PA14
heater: heater_bed, extruder
shutdown_speed: 0.0
And haven’t had an issue now.
did you solve the leveling problem? I have the same problem
i cannot get the .bin file to work it just stays on the anycubic logo
orry if this question has already been answered, where can I find a step-by-step video on how to configure the sonic pad on the kobra max.
SAme here stuck…
You are a hero mate. This file saved me. was stuck on line 21 error. Cheers ! beers on me
I have new board where the resistor is in the correct spot. I used your .bin file but still can’t connect any help? I am using the pad7.
I have never used a pad 7. Does it see your printer? I used lsusb, ls /dev/serial/by-path/*, etc to find the mcu by SSH into the Pi.
I am getting msu error currently
I can get the ID but after that it won’t work
What ID do you receive and what MCU errors do you get?
did the same changes, but i do have a newer board, any ideas why it did not work
Did you enter the mcu in the printer.cfg?
Yes, I can try again
how do you know the baud rate?
[mcu]
serial: /dev/serial/by-path/platform-3f980000.usb-usb-0:1.3:1.0-port0
restart_method: command
#baud: 250000
baud rate is 250000 but I left it commented out.
platform-5200000.ehci1-controller-usb-0:1.3:1.0-port0