The Problem

Builders of high‑speed Cartesian printers need a complete, community‑driven source of mechanical drawings, PCB layouts, and firmware configuration. Without a single repository that bundles CAD, PCB gerbers, and ready‑to‑use Klipper configs, teams must piece together disparate files, increasing error risk and setup time.

What This Does

LH‑Stinger delivers the full hardware definition for a 235 × 235 × 200 mm Cartesian printer. The mechanical geometry lives in CAD/ (e.g., CAD/Printer/LH Stinger.f3d and its STEP zip), while the printed‑circuit‑board assets and manufacturing outputs sit under PCB/ (Gerbers, KiCad schematics, 3D footprints). Firmware‑level settings are provided in Config/Klipper_Config/ – the primary printer.cfg together with motor, sensor, and macro files (adxl.cfg, steppers.cfg, etc.). Theme assets for Fluidd and Mainsail are also included, enabling a drop‑in UI experience.

How It Is Wired

The repository contains no executable source; the control flow is external to the repo:

  1. Klipper firmware runs on the Octopus Pro board and reads the configuration files from Config/Klipper_Config/.
  2. printer.cfg defines the MCU ([mcu]), stepper definitions ([stepper_x], [stepper_y], …), sensor pins, and the TMC2240 driver settings.
  3. Macro files (mymacros.cfg, mymacros_code.cfg) are included by printer.cfg and expose G‑code commands for bed probing, PID tuning, etc.
  4. UI themes (Config/Fluidd_Theme/, Config/Mainsail_Theme/) are consumed by the respective web front‑ends; they do not affect runtime logic.
  5. The mechanical parts (CAD, STL, DXF) are static resources; they are not executed and therefore have no call graph.

No internal code base exists to map; the only “hub” is printer.cfg, which pulls in all other Klipper fragments. Changing a hardware dimension requires updating the CAD file, re‑exporting the STEP, and adjusting the relevant stepper_ or bed_mesh sections in printer.cfg.

How To Use It

# Clone the repository (preserve large files if LFS is enabled later)
git clone https://github.com/moses-y/LH-Stinger
cd LH-Stinger

# Optional: install Git LFS and pull large binaries
git lfs install
git lfs pull   # fetch .f3d, .step, .xlsx, etc.

# Flash Klipper to the Octopus Pro board (outside this repo)
# Follow Klipper docs to compile and flash the firmware.

# Copy the Klipper config to the controller
scp Config/Klipper_Config/*.cfg pi@printer:/home/pi/klipper_config/

# Restart Klipper
ssh pi@printer "sudo systemctl restart klipper"

# Load UI theme (Fluidd example)
scp -r Config/Fluidd_Theme/ pi@printer:/home/pi/.fluidd/

The repository does not contain a build script; all steps rely on external tools (KiCad, Fusion 360, Klipper) whose installation is assumed.

Real‑World Use

A maker team can clone the repo, print the listed parts from the STL files, fabricate the PCBs from the Gerbers, and then drop the printer.cfg suite onto a Raspberry Pi running Klipper. After flashing the Octopus Pro board, the printer is ready for high‑speed prints (400‑600 mm/s) with the provided motion‑system tuning.

# Example: start a print with the supplied config
START_PRINT FILE=sample.gcode

Code Health & Issues

  • Tests – present (15 test files) but not tied to any CI pipeline.
  • CI – none detected (.github/ absent).
  • Dockerfile – none.
  • License – LICENSE.md included.
  • Lockfile – none (no package manager manifest).
  • Secrets – none found.

Medium – Large binary assets (e.g., CAD/Printer/LH Stinger.f3d 80 MB, LH‑Stinger_Fan_Grill-LED.step 47 MB, Toolhead 2510 - Dragon UHF - Sherpa Mini.step 46 MB) inflate clone size and impede diff‑based workflows. Recommended to track these with Git LFS or store them in external object storage and fetch during build/setup.

The Bottom Line

LH‑Stinger aggregates everything needed to fabricate and run a high‑speed Cartesian printer, with clear Klipper configuration and complete hardware documentation. The repo lacks automation (CI, Docker) and contains several multi‑megabyte binaries that should be moved to LFS. It is well‑suited for hardware engineers and advanced makers who are comfortable handling external firmware builds and PCB fabrication.