Project Info
This project did not submit a demo video on Devpost.
Inspiration
I've faced numerous print failures (especially since I started with an Ender) over my time printing. A common one if when the printer just stops at a layer - due to power failure, running out of filament, or whatever else is making the printer cranky. Repairing these failed prints often requires manually splitting the CAD model in Solidworks, then slicing the remaing portions, printing them and gluing them back.
What it does
This kit repairs failed FDM 3D print gcodes based on the layer it failed at, to enable direct printing starting from the failed layer. The effect is similar to power loss recovery, but for all kinds of failures involving stopping at a specific layer (and without the blobbing).
How we built it
It first uses OpenCV enabled camera measurement of failed part, or physical measurement. Once a measurement is obtained, it can be sent to a separate Python script that modifies the GCode model directly to enable the printer to restart from that layer.
Challenges we ran into
CV measurements aren't the most accurate Didn't have a physical printer to test/validate Limited time to do especially as 1 man team
Accomplishments we're proud of
Managed to make something (somewhat) functional
What we learned
A lot on OpenCV and CV detection/comparison methods Libraries for STL manipulation Some parts of photogrammetry (that wasn't implemented)
What's next
Will want to build upon this, especially once I'm back at my 3D printer to test it in real life!
GCodeRepair
Script to repair GCode
What it does
This kit repairs failed FDM 3D print gcodes based on the layer it failed at, to enable direct printing starting from the failed layer.
The effect is similar to power loss recovery, but for all kinds of failures involving stopping at a specific layer (and without the blobbing).
How we built it
It first uses OpenCV enabled camera measurement of failed part, or physical measurement.
Once a measurement is obtained, it can be sent to a separate Python script that modifies the GCode model directly to enable the printer to restart from that layer.
Analysis
View
Metric
- 9
Figures cover GitHub contributors during the hackathon window. A co-authored commit counts in full for each author, so per-member totals add up to more than the whole-team figures.
Technology
- PythonIn code
1 of 1 appear in the indexed code.
AI coding agents
No AI coding agent signals were found in this repository.
Detected from committed agent config files and commit authorship. Absence of a signal is not proof an agent was unused.
Codebase size
Source size
35 KB
Source files
7
Counts recognized source files only; vendored directories, binaries and lockfiles are excluded, so this is smaller than the repository on disk.
Repository
yonx30/GCodeRepair
9 files · 34.3 MB · @ 593415c
Structure
Application logic
6 files · 67%Domain rules, services and shared utilities.
Supporting
Layers are inferred from where files sit in the tree, not from reading the code. A project that names its directories unconventionally will read oddly here — open the file browser to check anything the diagram implies.
Languages
- Python98%
- Markdown2%
Share of indexed source by file size. Binary and vendored files are excluded.
This project’s features have not been analysed yet.
Export this project's context (description, README, evidence, key source files) to chat with an AI agent elsewhere.