Step 13.41 — Make the Voron printer profile and slice the cube¶
Step 41 of 54 · Chapter 13 — Initial startup
(no image — see text)
Parts:
- the laptop with PrusaSlicer 2.9.6 · tool
- the
Voron_Design_Cube_v7.stlfile · tool
Do:
- Save the CORE One HF0.4 profile as
Voron 2.4 350: bed 350 × 350, height 330, Klipper. Untick binary G-code, auto temperatures. - Start G-code below, End
PRINT_END. Physical printervoron.local; Test. - Slice the cube: 260/110, compensations off, seam rear.
PRINT_START BED=[first_layer_bed_temperature] EXTRUDER=[first_layer_temperature] CHAMBER=0 FILAMENT={filament_type[initial_tool]}
Check
The export is a .gcode file starting PRINT_START BED=110 EXTRUDER=260 CHAMBER=0 FILAMENT=ASA, no M190/M109 before it. No supports, seam at the rear, physical-printer Test passed.
What you're looking at
Voron_Design_Cube_v7 is a 30 mm test cube that batch B00 already printed on the Prusa. Everything sliced so far used the Core One+ profile. The Voron profile is four things: the 350 mm bed, the Klipper flavour, a start G-code calling PRINT_START, and a physical printer.
Where things are: Printer Settings → Save as… from Prusa CORE One HF0.4 nozzle, bed origin 0, 0; G-code flavor: Klipper under General → Firmware, then OK its dialog; Supports binary G-code under General → Firmware in Expert mode; Emit temperature commands automatically under Custom G-code. The Start and End G-code each replace everything in their box. The physical printer is the icon next to the printer preset → Add physical printer, no API key.
The flavor dialog switches Machine limits → How to apply limits to Use for time estimate, because Klipper takes no machine limits from G-code. The Core One preset ships binary G-code ticked, and Klipper reads only plain .gcode. Unticking the automatic temperature commands stops PrusaSlicer prepending M104/M190 before PRINT_START, which would heat the hotend before homing and home Z on the nozzle-probe pin through hot ooze. FILAMENT= passes the filament type, so PRINT_START runs the Nevermore only for materials that need it. Saving as a copy keeps the Prusament ASA and STRUCTURAL presets from print/00-slicer-setup.md compatible with it. Extruder 1: nozzle 0.4 stays; leave retraction at the copied value and tune it in Ch 14 (verify on bench).
The cube is Voron_Design_Cube_v7.stl, the same file batch B00 printed on the Prusa, exactly 30.000 × 30.000 × 30.000 mm. Slice it at hotend 260 °C, bed 110 °C, XY size compensation 0, shrinkage compensation 0 %, no supports, seam to the rear: the same overrides the Prusa profile uses, so the two cubes are comparable. Chamber temperature is not a slicer setting on this machine yet: the Prusa filament profile's chamber values emit M141/M191, which this config does not define (Klipper answers Unknown command, harmless); the chamber is CHAMBER= on PRINT_START, kept at 0, a timed soak, until Ch 14 has measured what the closed chamber reaches.
Caution
Export refused with "Machine limits cannot be emitted to G-Code when Klipper firmware flavor is used": set How to apply limits back to Use for time estimate. A .bgcode file instead of .gcode: Supports binary G-code is still ticked.
Caution
The Voron slicer guide's own starting point is 240 °C / 100 °C / 92 % flow for ABS. Use 260/110 here anyway: it is the Prusament ASA figure, and it is what makes this cube comparable with the B00 reference you caliper it against at Ch 14 Step 14.11.
Tip
Host type Moonraker if your PrusaSlicer lists it, else OctoPrint: Moonraker answers OctoPrint's upload API through [octoprint_compat].
Source: Voron-2 STLs/Test_Prints/ · Voron docs — first print · Voron docs — slicer setup · Moonraker configuration § octoprint_compat · Ch 12 Step 12.36