Can't get (used) SV08 to print

Sovol SV08
1

I just bought a used SV08. This is my first 3d printer, so I’m a complete n00b here. The previous owner installed a filament runout sensor, 32GB EMMC, and upgraded extruder. It does not have a touchscreen, just the small LCD with click wheel.

After setting it up, leveling, etc, I dropped a model into Orca Slicer and generated a g code file using default SV08 settings. Then I dropped the g code onto a USB stick and tried to print. I’m using PLA Pro filament from Amazon.

The print head moved to the center of the bed, dropped down to touch the bed 2 or 3 times, and then moved to the front left corner of the bed and stopped. No preheating, no real attempt to print, nothing.

I figured I must have messed something up with the slicer settings, so I tried printing some g code the previous owner had left in the internal memory. Same result.

What am missing here? The nozzle and bed both heat up when I select Preheat on the control, and everything seems to move fine. It feels like I must be missing some small but crucial step. Please help!

2

I’m far from a Klipper savant..but I do know that with these changes, you will have to make changes in Klipper.

@cardoc @MikeHides @Liberty4Ever

3

Pardon my ignorance, but what does that mean? The printer was working for the last guy, with the mods in place. Do you mean I need to use different slicer settings?

4

@JDBrown

@cardoc / @Liberty4Ever are much better with debugging deeper.

For the interim, do you see any error messages posted to the Device console in Orca slicer?

image
image2284×550 58.6 KB

Also you can try this for a basic printing test.

  1. Start a new project.
  2. Select your printer
  3. Select your filament
  4. On the picture of the build plate right click and “add a new privative” select '“cube”
  5. That will place a 15mmx15mmx15mm cube to print.
  6. Select “slice”, then select “print”, or if you are sneaker netting, change to “Export G-Code” and copy the exported gcode of the cube to your USB stick, and follow the same steps you are already doing for the gcode file..

Can you get the cube to start printing?

Cheers,
-Mike

5

Okay, here we go — welcome to Klipper, Sovol‑style.

The first thing to understand is that the SV08’s mainboard actually contains two systems on one board:

  1. The Host (Linux computer)

    • Runs Linux, Klipper software, Mainsail/Fluidd, and KlipperScreen.

  2. The MCU (motion controller)

    • Drives the steppers, heaters, fans, and sensors.

Every Klipper setup has one Host and one or more MCUs. The SV08 has two MCUs (one for motion, one for the toolhead).

Why your printer won’t start a print:
Because the SV08 is a Klipper machine, the knob LCD cannot configure or fix anything. It can’t edit system files, macros, or printer.cfg. To diagnose anything, you must connect to the web interface (Mainsail or Fluidd).

Step 1 — Get the printer on your network
You need either:

  • Wired Ethernet (strongly recommended), or
  • WiFi, which must be configured manually.

If you can plug in Ethernet:
Do that first. Once connected, you can configure WiFi from the web interface and unplug the cable later if you want.

If Ethernet is not an option:
Download Sovol’s WiFi instructions from their wiki. You’ll place a config file on a USB stick and hope the system picks it up on boot.

Fallback method (always works):
Plug in an HDMI monitor or TV, plus a USB mouse and keyboard. The SV08 will boot into KlipperScreen.

By default, KlipperScreen hides the mouse cursor because it expects a touchscreen. You’ll need to move the mouse around until you open Settings → Interface and enable the mouse pointer. Once you can see the cursor, you can configure WiFi directly in KlipperScreen.

Step 2 — Access the Web Interface
Once the printer is on your network:

  • Open a browser on your PC.
  • Enter the printer’s IP address.

Do NOT use Orca’s device tab — Orca cannot download logs or manage the printer.

You should now see Mainsail or Fluidd.

Step 3 — Get the logs
Inside Mainsail/Fluidd:

  1. Go to Machine.
  2. Find klippy.log.
  3. Download it.
  4. Upload it here.

That log will tell us exactly why the printer is probing and then stopping instead of heating and printing.

1 Like
6

@cardoc Thank you for the help so far. I now have the printer connected to wi-fi, failed to print the benchy that came on the USB stick, and was able to download the log file. Unfortunately, I’m too new of a user to be able to upload it, so I’ll paste what I assume is the relevant portion here. Something about ‘dict object’ has no attribute ‘BED’. I tried Googling what to do about this issue, but the results I found talked about manually editing config files in the printer, so I think I’ll wait to see what you have to say about it before diving into that.

===== Config file =====
=======================
Loaded MCU 'extra_mcu' 112 commands (v0.12.0-40-g77619e91-dirty-20240229_121540-chris-virtual-machine / gcc: (15:10.3-2021.07-4) 10.3.1 20210621 (release) binutils: (2.38-3ubuntu1+15build1) 2.38)
MCU 'extra_mcu' config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi3=PB4,PB5,PB3 CLOCK_FREQ=72000000 MCU=stm32f103xe PWM_MAX=255 RESERVE_PINS_USB=PA11,PA12 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1
Configured MCU 'extra_mcu' (1024 moves)
Loaded MCU 'mcu' 112 commands (v0.12.0-40-g77619e91-dirty-20240301_104656-chris-virtual-machine / gcc: (15:10.3-2021.07-4) 10.3.1 20210621 (release) binutils: (2.38-3ubuntu1+15build1) 2.38)
MCU 'mcu' config: ADC_MAX=4095 BUS_PINS_i2c1=PB6,PB7 BUS_PINS_i2c1a=PB8,PB9 BUS_PINS_i2c2=PB10,PB11 BUS_PINS_spi1=PA6,PA7,PA5 BUS_PINS_spi1a=PB4,PB5,PB3 BUS_PINS_spi2=PB14,PB15,PB13 BUS_PINS_spi3=PB4,PB5,PB3 CLOCK_FREQ=72000000 MCU=stm32f103xe PWM_MAX=255 RESERVE_PINS_USB=PA11,PA12 STATS_SUMSQ_BASE=256 STEPPER_BOTH_EDGE=1
Configured MCU 'mcu' (959 moves)
Args: ['/home/sovol/klipper/klippy/klippy.py', '/home/sovol/printer_data/config/printer.cfg', '-I', '/home/sovol/printer_data/comms/klippy.serial', '-l', '/home/sovol/printer_data/logs/klippy.log', '-a', '/home/sovol/printer_data/comms/klippy.sock']
Git version: 'v0.12.0-0-g02eeceb-dirty'
Modified files: klippy/__pycache__/msgproto.cpython-310.pyc, klippy/__pycache__/msgproto.cpython-38.pyc, klippy/chelper/__init__.py, klippy/chelper/compiler.h, klippy/chelper/itersolve.c, klippy/chelper/itersolve.h, klippy/chelper/kin_cartesian.c, klippy/chelper/kin_corexy.c, klippy/chelper/kin_corexz.c, klippy/chelper/kin_delta.c, (+187 files)
Branch: master
Remote: origin
Tracked URL: https://github.com/Sovol3d/klipper
CPU: 4 core ?
Python: '3.9.2 (default, Feb 28 2021, 17:03:44) \n[GCC 10.2.1 20210110]'
webhooks client 281472939314096: {'program': 'Moonraker', 'version': 'v0.8.0-209-g4235789-dirty'}
=============== Log rollover at Mon Mar 23 05:15:49 2026 ===============
Running Command {get_ip}...:
Command {get_ip} timed out
Running Command {get_ip}...:
Command {get_ip} timed out
Starting SD card print (position 0)
Error evaluating 'gcode_macro START_PRINT:gcode': jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'BED'
Traceback (most recent call last):
  File "/home/sovol/klipper/klippy/extras/gcode_macro.py", line 61, in render
    return str(self.template.render(context))
  File "/home/sovol/klippy-env/lib/python3.9/site-packages/jinja2/environment.py", line 1090, in render
    self.environment.handle_exception()
  File "/home/sovol/klippy-env/lib/python3.9/site-packages/jinja2/environment.py", line 832, in handle_exception
    reraise(*rewrite_traceback_stack(source=source))
  File "/home/sovol/klippy-env/lib/python3.9/site-packages/jinja2/_compat.py", line 28, in reraise
    raise value.with_traceback(tb)
  File "<template>", line 3, in top-level template code
  File "/home/sovol/klippy-env/lib/python3.9/site-packages/jinja2/filters.py", line 779, in do_int
    return int(value)
jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'BED'
Error evaluating 'gcode_macro START_PRINT:gcode': jinja2.exceptions.UndefinedError: 'dict object' has no attribute 'BED'

Exiting SD card print (position 0)
7

Put the log on OneDrive, Google Drive, dropbox or similar. Set to share and post link here.

Did you get a USB <> EMMC dongle and/or the original EMMC with the printer. Your best course of action may be to reinstall from scratch. Be sure to download EVERY file in the config directory before you wipe the EMMC.

Debugging what the last guy did to the start print macro could be difficult. Without knowing the start G-code their slicer was using it could be hard to get working

Look in the “jobs” tab of mainsail/fluid. Are there g-code files from the last user? The first 200 lines would let us figure out the start g-code that worked.