VzBoT AWD + BTT Kraken config problems
I'm building a All Wheel Drive VzBoT with a BTT Kraken board, sensorless homing, and a Beacon RevH and wants to use RatOS, but since both machine and board are not supported, I had some hardtime figuring out how to do it properly without damaging the core functionality of RatOS.
My question is, which printer should I choose as a baseline to mod it to fit my AWD VzBoT(with single Z motor, 2 for X, and 2 for Y), and what else should I be aware of during my installation.
I've installed Mainsail and Klipper manually before on my Voron 2.4 so I've got some experiences, but RatOS seems to be another world with everything so optmized that I couldn't understand it with my past exp.
21 Replies
The board is supported in RatOS 2.1 (i very much recommend you install 2.1.0-RC2 instead of RatOS 2.0)
About the machine, good question, i'm not too familiar with the details of the VzBot machines, only some parts of them. But i would pick a v-core closest in size, then manually add x1 and y1 drivers and steppers in printer.cfg (just copy x and y from RatOS.cfg - assuming RatOS 2.1 - and put a 1 afterwards, then fix the pins).
Wait, vzbot doesn't have 3-point leveling does it? In that case, you probably want to base it on the V-chonk instead.
remember to modify the limits (they're laid out for you for easy modification in printer.cfg)
Thanks for your reply! I'll try that out and report if I find anything worth noticing.
I've herd of RatOS will update it's config file automatically, from the newest release video, will I need to modify my file everytime to change it back then?
It updates RatOS.cfg - you're not supposed to edit that one (and you don't need to). Just write your configuration in printer.cfg.
Klipper merges subsequent sections and parameters into the preceding ones
So you can override everything by just adding the stuff you want to change to printer.cfg (after [include RatOS.cfg] which is at the very top)
I see, I still have one question, how do I disable Z1 motor, to my understanding I can add and overwrite but not delete, is that right?
Yes, that's why i asked about the 3-point leveling. Base your config on the v-chonk.
Oh that one does have 2 z's defined
V0 then 😅
I see, I'll try out Voron V0.1 to see if that works, thanks!
Fun thing I found out, NOT related to RatOS though, while setting up CPAP control signal (require 2~50KHz PWM):
BTT Kraken only allow hardware PWM pin to be used with those that went through a buffer IC, so only for all the heater pins, and the fan pins.
And due to PCB designs, only those for heaters & 4-wire fan (Fan6's PA6 & Fan7's PE8) are available for actual hardware PWM "output", nowhere else is available.
Just in case if someone is doing the samething as I am, there you go.
while tuning sensorless homing, it kept failing, and I found out that the G28 X is just performing a G1 move with accel and decel with the length of ~150mm and after movement it just call it homed, why??
got it, RatOS will try to center toolhead after homing, I got all of my motors reversed and implemented klipper_tmc_autotune, now things works... to some degree...
Sensorless homing? False triggering, needs tuning
If you're using klipper_tmc_autotune, make sure to pick the
Generic stepper for your steppers in the hardware configurator, so RatOS doesn't apply tuning settings.
sensorless parameters are configured in the sensorless-homing-*.cfg filesI want to install Mellow USB LIS2DW accel_chip but it kept saying "Section 'lis2dw' is not a valid config section"
it now says this
but I just flash it via ssh
it's
lis2dw
Ah, you got it here, good
You didn't flash it, it's running a really old version of klipper as you can see
I did flash it using the command:
cd ~/klipper/
make menuconfig
make
cd && cd ~/klipper/
make flash FLASH_DEVICE=2e8a:0003
I did it several times and every time is succeed but mainsail showed me the same error message, I tried git pull to manually update klipper via command line, and flash again, succeed and the same error message.
Tried flashing RatOS entirly and did the samething but without updating klipper via command line, same result.
My problem is how can it be a old version after flashing with newest version of klipper installed, is it some problem of the board? Cause Mellow is notorious with their board quality
make flash FLASH_DEVICE=2e8a:0003That's not how you flash an RP2040 that already has klipper on it. Use the serial path
I did it several times and every time is succeed but mainsail showed me the same error messagI don't think so, show me the console output. This is not a RatOS issue 🙂
use this as
FLASH_DEVICE
And make sure you haven't left the chipid set for whatever was compiled last in
make menuconfig or you'll get USB conflicts.
12345 like your current one is flashed with is fine