I'm building a slicer called Kothar, made for Klipper printers first. This week it went from code to real parts on my Voron 2.4 350 (0.8 nozzle, PETG), so here's where it stands.
What's printing now: walls, top/bottom skins, bridges and gap fill.
Test prints, measured with calipers:
- Walls-only tube: wall thickness 2.22-2.29 mm, the toolpath predicted 2.29.
- Closed 20 mm cube: 20.01-20.05 on every face except one corner at 20.19. That turned out to be the seam: every layer started and ended at the same corner and the loop end ran into its own start blob.
- After adding a seam gap, priming on an inner wall and an inward wipe, the latest cube measures X 20.00, Y 20.06. Z was 19.90, which is my Z offset, not the slicer; I'm fixing that now.
- The top surface had a row of tiny beads along the edges where the skin line ends pushed too much plastic into the wall. Tapering the line ends on visible top layers fixed it.
The Klipper side:
- Uses your own PRINT_START / PRINT_END macros, with explicit M190/M109 waits so the heat order is never left to a macro.
- EXCLUDE_OBJECT_DEFINE / START / END, SET_PRINT_STATS_INFO, and M73 progress.
- SET_VELOCITY_LIMIT for separate print and travel acceleration.
- Start steps can depend on the material (my chamber filter fans only run for ASA/ABS).
- Planned: read printer.cfg and its includes through Moonraker (read-only) to fill in the printer profile and check the G-code against the real config, e.g. EXCLUDE_OBJECT used but [exclude_object] missing, or a Z hop faster than max_z_velocity.
Other things that are different:
- Every setting shows where its value came from (built-in, nozzle rule, printer, material, preset or yours), and the G-code header lists them all.
- Speeds are capped automatically by the volumetric flow limit for that material and nozzle; the preview can colour by speed or flow.
- Before a file goes out, a rule-based checker runs on Kothar's own output (heat before extrude, start sequence, bounds, flow, layer time). It refuses to write a file with moves off the bed. An optional local AI model explains the findings but never decides pass/fail, and nothing goes to the cloud.
- It generates its own test parts with a debossed ID and X/Y letters, so I stop mixing up which way a cube sat on the bed.
Next up: infill (grid, lines, gyroid), then cooling and overhangs (material-based min layer time that keeps the outer wall at a steady speed, overhang-aware walls, better bridges), then a proper seam system.
Every work package ends with a real print that I measure before moving on. Not public yet; I'll share more once it prints a proper Benchy. Questions and Klipper-specific wishes welcome.