to resume:
currently putting togehter a vzbot235 based custom printer
order a fancier board for it but it’s going to take a while to arrive
that said, decided to get it working with a creality 422 board i had at hand
turned it on for the first time today
used a e3v2 config base
already changed most parameters to fit the printer, everything working fine so far
but, i’m having issues with my probe (bl touch clone) already tried changing wiring position a dozen times, trying changing the pin prefixes (^/!), tried running the regular testing steps on the klipper website
so far the most progress i’ve made is:
the probe responds to pin up and down commands, when homing, it deploys, bed starts rising but as soon as something touches the deployed probe, it stows, starts blinking really fast and doesn’t deploy back down, then an error pops up
(i explain it better on the video files bellow, together with my printer.cfg, wiring and latest klippy log)
excuse the english, btw, not native
-vzbot235 custom build
-422 board with 303 chip
-bigtreetech pi v1.2 stock klipper config via kiauh
no ‘‘custom configs’’, barebones/troubleshooting configs using the stock e3v2/422 board printer.cfg from the klipper gtihub
ah, due to it being from a sonic pad right? fair enough.
but, if i re-do all configs, klipper and firmware setup using a bttpi, supposing i get the same error, would it be acceptable?
well, everything from the host side is brand new, stock, up-to-date klipper/fluidd/moonraker install, however i havent updated the board’s firmware from some of the last tests, ill do so now and come back here, tks for the attention