This is a small command line tool to analyse gcodes (control codes for 3D printers, CNC,...). It calculates various print details like -print time -used filament -yx move distance -print object dimension -average print speeds -number of layers -layer details -speed distribution -weight and price of the printed object ... I used it to optimize my slicer settings and print times for my reprap printer. Tested mostly with slic3r generated gcodes.
I just ran a few of my gcode files through GCodeInfo and the Overall Time estimates don't seem to match up.
The output for one such job is as follows:
Overall Time (w/o Acceleration): 0:14:56 (895.73sec)
Overall Time (w/ Acceleration): 0:17:09 (1028.5654sec)
Should the "w/o acceleration" time be 0:17:09 instead of 0:14:56?
GCodeInfo is making a guess that the material used in my gcode files is ABS but I'm using PLA which weighs slightly more thus the estimates for the weights a off by a little bit. I would be nice to be able to set the value of this to force another material.
Also, can the price per unit be set as an argument as well so that I can specify my cost / unit of material?
First thank you for your product it seems from first point that it's exactly what I need.
I want to attach laser wire melting assembly on 3d printer. There is a need to control additional stepper motor, and I hope you can get the control possibility through your SW - GCODE simulator and printer.
For more info how assembly should work check this topic on metalbot forum:
I'm running your app on a small Denver Pad, I have around 50k mem to use when I have loaded the App.
I loaded a G-code file with 222414 lines of G-code. The first 50% goes fast and then it slows down alot. But the file loaded into mem.
How ever, 2 hours into the print, the Pad crashed.
I was wondering if it was possible to read the G-code 10 - 50 lines at a time from the disk, instead of loading it all into mem at once.
I have also tried to load larger files, but they error out at line 270001 for some reason.
Not supported Gcode:M101
Not supported Gcode:M103
Not supported Gcode:M101
Not supported Gcode:M103
Not supported Gcode:M101
Not supported Gcode:M103
Not supported Gcode:M101
Not supported Gcode:M103
Not supported Gcode:M101
Not supported Gcode:M103
Not supported Gcode:M103
Not supported Gcode:M113
Detected 84 error(s) during parsing of Gcode file. Results might be wrong.
Hi, I'm running simulator free with a Mendel90 printer and I have a problem where the Z-axis will move up past the endstop, causing damage to the Z-axis bracket. This does not happen when using the move buttons using pronterface. Any idea why the endstop signal would be ignored when controlling the printer via Gcodesimulator? Is this is bug or a configuration issue? Thanks!
I tried using a gcode file generated with MakerWare (using Miracle Grue as the slicer) but GCodeInfo stopped with this error:
Unknown Gcode 1: M136 (ENABLE BU....
Unknown Gcode 2: M73 P0....
Unknown Gcode 3: G162 X Y F2000(....
Unknown Gcode 4: G161 Z F900(HOM....
Exception in thread "main" java.lang.NumberFormatException: empty String
at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
at java.lang.Float.parseFloat(Unknown Source)
at de.dietzm.GCode.parseSegment(GCode.java:539)
at de.dietzm.GCode.parseGcode(GCode.java:432)
at de.dietzm.Model.loadModel(Model.java:489)
at de.dietzm.Model.loadModel(Model.java:476)
at de.dietzm.GCodeUtil.main(GCodeUtil.java:51)
I assume this is because MBI has modified some of the commands used in a standard gcode file but I was hoping support for this could be added.
Hi,
I'd like to use your software for my printers (I'm a manufacturer) but unfortunately the device will not connect. I'm connecting via USB-OTG and have tried 4 different tablets now. Not many seem to have OTG support for CH340, however the Aoson M751S does. 3D Fox software works well, but has left out too many important features. I'd love to give your software a chance, but unfortunately it will not connect. The tablet fails to connect after a window pops requesting permission to access the USB device. The device is discovered. The same hardware and software works if the arduino has the atmel comm chip instead of CH340.
Thanks,
Jared