xBuddy firmware source?
Got my new mk4s set up and working, it's great though a bit disappointing I can't reuse my octoprint pi (from my old FF Creator Pro). Might look into putting a usb camera in.
I was trying to look for information regarding possibly connecting over ssh to the printer, however now I'm realizing I can't even find the xBuddy firmware on https://github.com/orgs/prusa3d/repositories
The buddy firmware is on there for the mk4 and similar but not xBuddy... Is the source code for the firmware intended to be public, but just delayed, or something?
Additionally, is there a way to get a console, over ethernet ideally, or over usb, into the embedded board, or is the only thing available the PrusaLink API and status port? I'm curious to see the computer specs of the board.
RE: xBuddy firmware source?
I'm not sure of what you are looking for. The xBuddy board is the mainboard, and its firmware is there https://github.com/prusa3d/Prusa-Firmware-Buddy .
It's a common codebase across all the 32-bit printers, MK4/XL/CORE One... It's an embedded software, not linux based like RPi. The MCU is an STM32. So no SSH console.
Why can't you reuse your OctoPi? It should be work-ish, but really not the best way to connect tough as it slow down the print.
RE: xBuddy firmware source?
My bad, I thought there were differences with the mk4 and mk4s that would make the firmware source incompatible (and the readme on the repo doesn't seem to be updated to include the newer models).
As for octopi, I had it connected to the creator pro over usb (and all the gcode on it is in makerbot flavor so it probably would be incompatible with the mk4s), connecting it would be a matter of using an A to C cable now that I think of it. I used octolapse with the old printer which had a lit enclosure, so I'd have to figure out lighting without an enclosure (for now) if I want to set up timelapses again. Maybe use octopi for structural single material prints, and on device for fast and multi material prints (unless octopi supports the MMU3)
Thanks for the info!
RE: xBuddy firmware source?
Regarding the MMU3, it is purely managed through gcodes, should work as-is.
The point to check maybe is the compatibility with .bgcode files. If not then you'll need to uncheck this feature from PrusaSlicer to get old uncompressed .gcode file.
The issue using UART connection (through USB here) is that it is too slow to feed the printer's buffer. The motion planner can't see future gcodes far enough in time and needs to decelerate because it can't anticipate the n-th movement. For old slow printers this wasn't an issue, but now we have rocket printers. 😄