Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/fabbaloo.com/httpdocs/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/vhosts/fabbaloo.com/httpdocs/wp-includes/functions.php on line 6114
Why Use a Free GCODE Analyzer? « Fabbaloo

Why Use a Free GCODE Analyzer?

By on August 11th, 2017 in Service

Tags: ,

 The free GCODE analyzer shows statistics about 3D print jobs
The free GCODE analyzer shows statistics about 3D print jobs

There are tons of free utilities available on the internets, and one of them is a free GCODE viewer. 

GCODE are the machine instructions that drive 3D printers. They are a very long sequence of primitive commands to move the axes, heat up the nozzle and so forth. GCODE is the output from 3D print slicing programs that convert a 3D model into an executable sequence of instructions. 

The programs that generate GCODE very often provide plenty of information about the print job represented by the GCODE. And there are many things a 3D printer operator may wish to inspect, such as the actual toolpath: is it optimum? Does it cover all parts of the 3D model as intended? 

Other deeper questions are also possible: how strong might an elbow structure or thin section be? Will the print sequence provide sufficient material for a reliable first layer? How fast will the print speed be on critical zones requiring more accuracy? What is the cost of material for the print?

Often these questions are answered at the time of slicing by the slicer you are using, but more often than not there are missing bits of information. A given slicing program may not provide all the detail required for a complete inspection of the GCODE. 

Hereā€™s a very common scenario: Slic3r, one of the more commonly used open source 3D print slicing programs, for some reason does not report the estimated print time for a newly sliced 3D model! There is no way to know how long the print might take until you start printing it, where your printer may report or hint at the expected elapsed time. 

How do you solve such situations? Itā€™s easy – just head over to the free GCODE Analyzer. 

This utility operates in a very straightforward manner: just drag and drop your sliced GCODE file onto the web page, and it will upload for analysis. The results of the analysis are quickly displayed and provide a plethora of information for your review. 

 Another view from the free GCODE Analyzer, showing 2D views of each layer of 3D print jobs
Another view from the free GCODE Analyzer, showing 2D views of each layer of 3D print jobs

Here you can see the ā€œ2Dā€ view, where you can scroll through the layers to see every movement made through the toolpath. The color of the lines indicates the speed of that particular extrusion. 

At top you can see some overall statistics for a print job, including a calculated material price as well as the elusive print time estimate. 

Not everyone will need such a utility, but for those that have slicing programs that are even slightly deficient in reporting, the GCODE Analyzer will be most welcome. 

Via GCODE Analyzer

By Kerry Stevenson

Kerry Stevenson, aka "General Fabb" has written over 8,000 stories on 3D printing at Fabbaloo since he launched the venture in 2007, with an intention to promote and grow the incredible technology of 3D printing across the world. So far, it seems to be working!