| Firmware base & current version (Klipper fork / Marlin fork / proprietary) | Klipper fork, base 0.12.0 (released 2023-11-10). Sovol's user-facing OTA numbering is separate: dumped image version=2.0; latest documented V19.0 | 1 source- sovol/klipper/docs/Releases.md (newest entry "## Klipper 0.12.0"); sovol/printer_data/build/.version.cfg (version=2.0); wiki.sovol3d.com/en/SV06ACE (Firmware Update Log: · 2026-08 · local
|
|---|
| Source code availability (repos, GPL compliance status, last update date) | Source at github.com/Sovol3d/SV06-ACE. Partial / stale compliance: created 2024-10-31, last push 2024-11-01, one commit, never updated in ~21 months while shipping firmware advanced to V19.0. No repo-level LICENSE (license: null); Klipper's GPLv3 COPYING exists only inside the klipper subtree. Ships a 1.2 MB precompiled binary blob src/libdev_hx711.a whose source is withheld. Linux kernel config missing (open issue #3). Two further gaps found: (a) the release contains only ONE MCU build config — sovol/klipper/.config with CONFIG_MCU="stm32f103xe", i.e. the toolhead; there is no build config anywhere for the GD32F425 mainboard MCU (find over the whole sovol/ tree returns only two Kconfig files, klipper/.config and klipper/.config.old — the third.config hit is sovol/.config, a directory), so you cannot reproduce the mainboard firmware from this release; (b) the repo ships two prebuilt, opaque MCU binaries — sovol/klipper.bin (32 464 B) and sovol/extra_mcu.bin (36 772 B), both file → "data" | 1 source- api.github.com/repos/Sovol3d/SV06-ACE (pushed_at 2024-11-01, license: null); firmware/SV06-ACE/ git log = single commit b8b1275; sovol/klipper/src/libdev_hx711.a (file → · 2026-08 · local
|
|---|
| Root/SSH access: possible? official or community method | Yes. SSH as user sovol / password sovol; sudo available → effective root. Provenance (revised by Pass 2): the *capability* (a sovol account with working sudo) is; the *credential pair* is, not — TH3D authenticated with it live on camera against a stock retail unit, which is a reproducible third-party test, and two independent write-ups state the same pair | 1 source- sovol/.bash_history (sudo apt-get update, sudo apt-get install python3-tk, sudo dpkg --configure -a, su, sudo reboot); sovol/printer_data/start.sh (runs nohup sudo apt-ge · 2026-08 · local
|
|---|
| Moonraker / Mainsail / Fluidd or other open API available (stock vs after mods)? | Stock out of the box. Moonraker on 0.0.0.0:7125, trusted_clients = all RFC1918 + loopback + link-local + FE80::/10, cors_domains incl. my.mainsail.xyz / app.fluidd.xyz; [octoprint_compat], [history], [timelapse] enabled. Mainsail 2.12.0 bundled; Moonraker reported as 0.9.0 | 1 source- .../kiauh-backups/configs/240724-0417/printer_data/config/moonraker.conf; sovol/mainsail/.version (v2.12.0); sovol/printer_data/systemd/moonraker.env; sovol/printer_data/ · 2026-08 · local
|
|---|
| Notable community firmware/mods (names, repos, what they add) | Mainline Klipper conversion (alkalint/Mainline-Klipper-for-the-Sovol-SV06-ACE, May 2026) — Katapult + ST-Link SWD reflash of both MCUs; KlipperScreen port (R8CEH/klipperscreen_sovol_sv06_ace); HelixScreen (prestonbrown/helixscreen, needs "rotate": 180); KAMP; Kalico [load_cell_probe] replacing [hx711]+[smart_effector] | 1 source- github.com/alkalint/Mainline-Klipper-for-the-Sovol-SV06-ACE (fetched README); klipper.discourse.group/t/.../25656 (garethky's [load_cell_probe] sensor_type: hx711 sclk_pi · 2026-08 · local
|
|---|
| Firmware update mechanism (OTA/USB) & update cadence history | OTA over WiFi from the touchscreen: Settings → check network → System → Device Information → OTA (red dot = update available) → OK → auto-reboot. A separate USB/image recovery path exists via a Rockchip image-flashing tutorial. Cadence: only V17.0 and V19.0 documented, without dates | 1 source- wiki.sovol3d.com/en/SV06-ACE-OTA-firmware-upgrade (fetched via curl); wiki.sovol3d.com/en/SV06ACE (Firmware Update Log) · 2026-08 · local
|
|---|
| G-code flavor & notable custom G-codes/macros | Klipper flavour ("gcode_flavor": "klipper"). Custom macros: START_PRINT, END_PRINT, CLEAN_NOZZLE, CANCEL_PRINT, PAUSE/RESUME (with STATE=filament_change), M600, _LOAD_FILAMENT/_UNLOAD_FILAMENT/_CONTINUE_LOAD_FILAMENT, _IDLE_TIMEOUT, _ALL_FAN_OFF, _global_var. M109/M190 are overridden into TEMPERATURE_WAIT wrappers with a ±(−1/+2) °C window. G2/G3 arc support added in V19.0 | 1 source- .../FactoryConfig/Macro.cfg (full file); firmware/orcaslicer_profiles/Sovol_SV06_ACE_0.4_nozzle.json; wiki.sovol3d.com/en/SV06ACE (V19.0: "Added support for G2/G3") · 2026-08 · local
|
|---|
| Root shell: exact method (official setting toggle / vendor-documented / community exploit / none). Is root persistent across OTA firmware updates, or wiped each update? | Vendor-shipped SSH login as sovol/sovol with working, apparently passwordless sudo → effective root. No exploit, no touchscreen toggle, no vendor documentation — it is simply left on. Direct root login is rejected (no known root password) and su also fails; sudo -i is the route in. Persistence across OTA: not established. Demonstrated end-to-end on a stock retail unit on camera | 1 source- youtube.com/watch?v=NKwYF9zIPO8 (TH3D, live: "do they expose SSH on it … SSH is open. I'm just trying root and root for the password, it didn't take it" → then, with the · 2026-08 · local
|
|---|
| Userland: OS base (Debian/Ubuntu/Buildroot/OpenWrt/busybox-only), package manager present (`apt`/`opkg`/`ipkg`/none), CPU architecture (armv7 / aarch64 / mips / x86), and free space on the writable partition. A busybox/no-apt rootfs with a few MB free is a red flag — say so. | Debian 11 "bullseye" (or a Rockchip/Armbian BSP rootfs built on it), systemd, apt/dpkg present. aarch64 (RK3308B quad Cortex-A35), kernel 5.10.160 #54 SMP PREEMPT Mon Aug 5 22:22:56 CST 2024 (Rockchip BSP). ~512 MB RAM. 8 GB soldered eMMC with ~2.7 GB free. Not busybox — full userland with python3.9, /usr/bin/ffmpeg, virtualenv and KIAUH v4.0.0 pre-installed | 1 source- Distro pinned by Pass 2 from firmware artifacts : sovol/.local/share/virtualenv/wheel/3.9/image/1/CopyPipInstall/ containing pip-20.3.4, setuptools-44.1.1, wheel-0.34.2 a · 2026-08 · local
|
|---|
| Native Tailscale feasibility: can `tailscaled` run persistently on-device? Cite concrete evidence — community guides, wiki entries, forum posts, or repos of people actually doing it on THIS model. Note whether it needs `/dev/net/tun` (kernel TUN support) and whether the kernel provides it, plus whether userspace-networking mode is the only option. Distinguish "someone did it" from "should theoretically work." | Plausible but UNVERIFIED — still zero documented instances of Tailscale running on an SV06 ACE, or on any Sovol printer. Prerequisites present and now better evidenced: aarch64 + Debian 11 + apt + systemd + passwordless sudo + ~2.7 GB free + persistent writable home (N9, N12). Blocker unchanged in status but worse in expectation: the platform's stock kernel config does not build TUN. Sovol never published its kernel config (issue #3, open since 2025-02-19, unanswered), so /dev/net/tun on a real machine remains unconfirmed — but Rockchip's own linux-5.10 BSP defconfigs for this SoC family contain no CONFIG_TUN at all | 1 source- api.github.com/repos/Sovol3d/SV06-ACE/issues; forum.armbian.com/topic/57569 (no TUN/VPN mention anywhere in the thread); new evidence fetched by Pass 2: rockchip-linux/ke · 2026-08 · local
|
|---|
| SSH daemon: present by default or must be installed/enabled? Default credentials if documented. Does an OTA update disable it or reset the password? | Present and running by default on port 22 — no toggle, no install step. Credentials sovol/sovol, demonstrated authenticating on a stock retail unit (so the credential pair is, not merely community lore). Whether OTA resets the password or disables sshd: undocumented and untested | 1 source- youtube.com/watch?v=NKwYF9zIPO8 (TH3D probes and then logs in live on stream: "SSH is open" … "yeah I'm in I'm boom there we go"); forum.armbian.com/topic/57569 ("ssh sov · 2026-08 · local
|
|---|
| Filesystem persistence: is the rootfs read-only or overlay-mounted? Do user-installed binaries and init/systemd services survive reboot and survive firmware updates? Is there a supported place to persist customizations? | Writable, persistent, ordinary filesystem — not read-only, no overlay evidence. The shipped image proves persistence: it contains the user's.bash_history, apt/dpkg state, KIAUH backups dated 240710 and 240724, and Klipper SAVE_CONFIG output written into printer.cfg. Services are standard systemd units driven by env files in ~/printer_data/systemd/. Survival across OTA: not established | 1 source- sovol/.bash_history; sovol/kiauh-backups/configs/240710-0715/, 240724-0417/;.../FactoryConfig/printer.cfg L318-325 (SAVE_CONFIG persisted); sovol/printer_data/systemd/{kl · 2026-08 · local
|
|---|