CodeFaux

I did mention that I'm using the same setup with the onboard Serial0 (which is shared with the serial-to-USB chip) so I know the level converter and RPi are working...

Okay so here's some fun. Serial data shows up properly until it's hooked up. I'm using bidirectional level converters because that's what I had on hand, which - paired with...

More or less, yes they are. A weak one, weak enough that the MCU itself can overcome it to idle low with pullups disabled. I'm as surprised as you are...

Any chance anyone could pay attention to this one? I'm also using Klipper, multi-extruder, multi-MCU (so it HAS TO BE Klipper) on a printer I've just prototyped from scratch and...

I don't feel it's a non-issue at this time. Implementing as such requires the user to do a ton of work to manually add/edit/change Klipper's G-Code macros system to support...

> Klipper uploading is supported: Just select OctoPrint target. Klipper firmware is supported: Just select Marlin legacy firmware and follow Klipper manual. That's unintuitive. I assume it's also well documented?

> Velocity and acceleration related g-codes available for marlin from Prusa Slicer are not compatible with Klipper though. We need implementations of g-code output for the equivalent klipper functionality for...

> Most likely we will implement Klipper support to PrusaSlicer 2.6 I'm very glad to hear that, but I believe we have some questions. Respectfully; - Do you plan to...

> what were the issues? OK, sorry this took a bit - wanted to dedicate the proper time, which turned out to be about two hours. I apologize if I...

> did some git archaeology Thanks for the dive and explanation, that helps me come to about the same place as you; > I personally consider it an abomination ....