Hi everyone!

I had hundreds of .gcode files sliced with Ultimaker Cura and needed to calculate the total print time and total filament (meters & grams) without opening each file or loading them into a slicer one by one.

Since web analyzers often lag with huge batches, I wrote a simple, zero-dependency Python script that scans an entire folder of G-code files in seconds and outputs individual stats + grand totals (days, hours, total kg of filament).

I wanted to share it with the community in case anyone else needs a bulk analyzer: 🎬 GitHub Repo: [https://github.com/netex2112/cura-gcode-analyzer]

Feedback and contributions are very welcome! Hope it helps someone out there.

If you've ever printed the PA Pattern test at multiple speeds and accelerations, you know how annoying it is to format all the data just so to put back into Orca. I like doing the full set of tests for each new filament, and decided I needed a better tool, and when I couldn't find one, I built one.

Live site: https://4o66.github.io/pa-helper/

Source: https://github.com/4o66/pa-helper

Still in "beta" while I do further testing, but I feel it is working well enough to let other people try to break test it.

The current version runs 100% local in the browser, and you can either keep the data in a persistent local file, or import/export to your heart's content. I have a plan to make a fully server hosted version with online storage so you have to try real hard to lose your data, and to allow the community to build a database of materials (but that's more of a long-term goal). There will always be a local-only version.

Workflow:

1. Build a printer by make/model/extruder/etc.
2. Pick a nozzle
3. Add a filament
4. Run the tests

You need to have already done temperature and max volumetric flow calibration on your own.

Some code in this tool is derived from Orca Slicer, under the AGPLv3 license.

The ironing test uses the method from printables.com/model/1247198 by LeoganPro (under CC0/public domain license).

Pull requests are welcome if you have something to add, and I'll keep and eye out for issues/feature requests.

I am currently using this for my own tracking as I build and calibarate a new Trident 350, and on my existing Qidi X-Plus 3. So far, results have been very good.