OctoPrint on Raspberry Pi 4 connected to Sovol3D SV06 ACE?

Get Help Electronics
1

What is the problem?

  • I have a Sovol3D SV06 ACE: Sovol SV06 ACE High Speed Auto Leveling 3D Printer – SOVOL
  • I've enabled UART3 on my Raspberry Pi 4, and can see /dev/ttyAMA1 now
  • I've connected the RX/TX/GND on the RPi4's UART3 to the RX/TX/GND "debug" pins on the MCU ( it's the black header right next to the red switch: SV06 ACE 3D Printer Mainboard Kit – SOVOL ), and I've also tried RX/TX to TX/RX (respectively)
  • OctoPrint is unable to make a successful connection, it times out without any response from the printer
  • I'm not even sure the debug pins are supposed to work for this purpose, but I've contacted Sovol3D to try to figure this out
  • if folks have any ideas for things I can test or change it'd be very much appreciated <3

What did you already try to solve it?

Have you tried running in safe mode?

  • not yet, I don't have any extensions installed and this is a fresh flash of OctoPi on this RPi4

Did running in safe mode solve the problem?

  • N/A, but I'll try this when I have more time
2

Hello @jokeyrhyme !

For it appears that the SV06 ACE runs on a preinstalled Klipper, it is not possible to connect to the printer like to Marlin: Information on pre installed Klipper on 3D-Printers according to OctoPirnt

grafik

Please also take a note on this: 3D Printers with Preinstalled and Modified Klipper Versions - Knowledge Base - Klipper

3

Thanks! That's very helpful!

I'm still holding out hope I can get just enough information from Sovol3D's support to make use of the debug pins, but for now I'll probably just run Octo4a on an old phone and at least monitor jobs visually via the camera :slight_smile:

4

The serial connection to the printerboard is occupied by Klipper. You can't bypass that, because Klipper is a firmware that runs on two hardware sections:

  1. The printerboard/MCU as hardware driver/interface
  2. The main SBC where the calculations are performed.

You can't connect to the printerboard, you have to connect to Klipper on the SBC. And that is only possible via a virtual serial interface.

For further information on how Klipper works: Klipper Architecture / Ecosystem - Knowledge Base - Klipper

5

Amazing, that's exactly the information and level of detail I needed, even though it's not the answer I wanted :smiley:

So, the best I can probably come up with is something like this then:

                                                                 
 ┌────────────────────┐          ┌─────────────────────────────┐ 
 │                    │          │                             │ 
 │   home network     │          │        printer network      │ 
 │                                                             │ 
 │    ┌─────────┐  ┌────────────────┐  ┌────────────────────┐  │ 
 │    │         │  │                │  │                    │  │ 
 │    │  phone  │  │  raspberry pi  │  │  Sovol3D SV06 ACE  │  │ 
 │    │         │  │                │  │                    │  │ 
 │    └─────────┘  └────────────────┘  └────────────────────┘  │ 
 │                                                             │ 
 │   ┌───────────┐    │          │                             │ 
 │   │           │    │          │                             │ 
 │   │  desktop  │    │          │                             │ 
 │   │           │    │          │                             │ 
 │   └───────────┘    │          │                             │ 
 │                    │          │                             │ 
 └────────────────────┘          └─────────────────────────────┘
  • broadcast a new WiFi network from the Pi, connect the printer to that network
  • connect the Pi to my home network via ethernet
  • I'd have connections from printer to my home network and/or the internet disabled except when doing a firmware update
  • the Pi can proxy HTTP requests from my home network to the printer
  • I can share the serial devices on the printer across its network to the Pi, so that OctoPrint, etc can connect to a serial device
6

As long Klipper is running on that printer board: you can't.

7

Ah, of course

Sorry for making you repeat yourself (and thanks for being so patient)

Cheers!