MCU configuration question - SV06 Plus Ace

General Discussion
1

Basic Information:

Printer Model: Sovol SV06 Plus Ace
MCU / Printerboard: Main MCU RK3308, toolhead MCU STM32F103
Host / SBC
klippy.log

Fill out above information and in all cases attach your klippy.log file (use zip to compress it, if too big). Pasting your printer.cfg is not needed
Be sure to check our “Knowledge Base” Category first. Most relevant items, e.g. error messages, are covered there

Describe your issue:

…I have a general question about the Sovol SV06 Plus Ace’s config.

I see “mcu”, “extra_mcu” and “mcu rpi”.

“extra_mcu” is likely the one on the toolhead - here is the config snippet:

mcu extra_mcu

serial:/dev/serial/by-id/usb-Klipper_stm32f103xe_52FF6E067167485743451787-if00

restart_method: command

“mcu rpi” is (as I understand) a virtual MCU within the RK3308:

mcu rpi

serial: /tmp/klipper_host_mcu

So - what is “mcu” here?

mcu

serial: /dev/ttyS1

restart_method: command

I see no further reference to it in the config. Is this just unused?

2

Hi @drmbkt ,

Since you didn’t upload your klippy.log (which includes the full config), here’s my best guess as to what’s happening:

mcu is typically the board driving your steppers and bed heater. Unlike other MCU’s, the main mcu doesn’t have a prefix in front of its pin names. For example:

# completely random pins, just as an illustration
[stepper_x]
step_pin: PA0
dir_pin: PA1
enable_pin: !PA2

The pins PA0, PA1, and PA2 are on mcu, but they aren’t prefixed with mcu:

On ther other hand, for steppers on different MCU’s like your extra_mcu:

# again, completely random pins
[extruder]
step_pin: extra_mcu:PA0
dir_pin: extra_mcu:PA1
enable_pin: !extra_mcu:PA2

These pins are prepended with extra_mcu: to tell Klipper to look on extra_mcu for those pins.

TL;DR

Even though your config doesn’t explicitly mention mcu on pins, it’s still using it wherever there’s a pin name without a xxx: prefix

3

@3dcoded thank you for looking at this. log attached.

klippy.log (448.7 KB)

So - based on your response, do I have this config?

  • Host: RK3308
    • with Virtual MCU as “mcu rpi”
  • mcu
  • extra_mcu

so in effect - three places where klipper.bin would need to be flashed?

4

Too slow…

But it seems the bed accelerometer is connected to the H616 SOM not the MCU.

[lis2dw bed]
cs_pin: rpi:None
spi_bus: spidev1.0
axes_map: x,y,z

Yes you need to update klipper.bin 3 places. The Rpi is just writing a file to a folder so “flash” may not the the best word.

5

For this, you need to follow this doc: RPi microcontroller - Klipper documentation