A simple G-code parser & viewer lib with 3D printing in mind. Written in Typescript.
Join us on discord
Click to see the interactive demo:
npm install gcode-preview
import * as GCodePreview from 'gcode-preview';
const preview = GCodePreview.init({
canvas: document.querySelector('canvas'),
extrusionColor: 'hotpink'
});
// draw a diagonal line
const gcode = 'G0 X0 Y0 Z0.2\nG1 X42 Y42 E10';
preview.processGCode(gcode);
Check the full API documentation at https://gcode-preview.web.app/docs
There's a Vue.js example that has a Vue component to wrap the library.
@Zeng95 provided a React & Typescript example that has a React component to wrap the library.
There is a Svelte example with a Svelte component.
GCode files that were sliced for a multi-tool system can be previewed as such. Assign an array of colors to the extrusionColor
property, where the index in the array corresponds to the index of the tool: T0..T7.
example:
extrusionColor: ['hotpink', 'indigo', 'lime']
Here, T0 is hotpink, T1 is indigo and T2 is lime.
Supported systems include:
renderTubes : true
Thanks to @Sindarius arc commands are now supported, which means gcode processed by ArcWelder should be rendered correctly.
Thumbnail previews as generated by PrusaSlicer are detected and parsed. In the gcode these are found in comments, enclosed between 'thumbnail begin' and 'thumbnail end'. The images are encoded as base64 strings but split over multiple lines. These are now parsed and patched back together, but still kept a base64. This allows easy use in the browser for us as data urls.
Thumbnail Preview as generate by PrusaSlicer
The thumbnails can be accessed like this:
gcodePreview.parser.metadata.thumbnails['220x124']
Thumbnails have a .src
property that will create a usable data url from the base64 string.
See an example in the demo source.
The build volume will be rendered if the buildVolume
parameter is passed. It has the following type:
buildVolume: {
x: number;
y: number;
z: number
}
example:
To develop on gcode-preview run:
npm i && npm run dev
This runs the demo app which is fairly complete in using the libs features.
If you don't need the demo app, just run npm run dev:watch
.
Both build a dev bundle in the dist
directory.
Note the dev bundle:
Before submitting a PR run:
npm run build
for a production buildnpm run test
for unit testsnpm run typeCheck
for typescript typingsnpm run lint
for code style and formattingnpm run build && npm run test && npm run typeCheck && npm run lint
To auto-fix simple issues:
npm run lint:fix
or npm run prettier:fix
For working on production builds you can use:
npm run demo
which does a prod build and launches the demo app using local servernpm run build
or npm run build:watch
If you have found a bug or if have an idea for a feature, don't hesitate to create an issue on GitHub or talk to us on Discord.
It would be great if you want to help! Maybe you'd like to help out with:
Jump to the CHANGELOG
This is caused by the device recognition shield in Brave. By changing the setting for "Device Recognition" in Shield settings to "Allow all device recognition attemps" or "Only block cross-site device recognition attemps" you should not get this error. https://github.com/mrdoob/three.js/issues/16904
A big thanks to these sponsors for their contributions.
If you want to show gratitude you can always buy me beer/coffee/filament via ko-fi or PayPal ^_^
This project is licensed under the MIT License.