Apologies...I had to satisfy my inner nerd...I think this post did the trick :)

3D Printing
,
1

Apologies…I had to satisfy my inner nerd…I think this post did the trick :slight_smile:
https://sites.google.com/site/321soldersucker/home/random-ramblings/3dprinterusageservicelogging

2

I think this is a good idea but wonder if it could be better if it could inhale the first 20 or so lines of the G-Code file that has the slicer settings and comments for each. Then when you want to repeat something later you could look it up.

3

I think logging is a bit tedious for small prints… Imagine having @OctoPrint ​​ feed data into this! Time, gcode name, failure/not, temps, etc.

4

Yeah I had the same idea actually, but I thought I’d make a simple start like this. I just know that sooner or later I’ll try pulling the data in from Octoprint though.

5

This is one of those fantastic ideas that I’m too lazy to do consistently. Ideally this would by done by host software since it already has alot of pertinent info. It would be awesome to have a complete history of jobs and resettable counters for things like extrusion volume, print time, distance per axis, etc.

6

…Sounds like we need a web app, not a spreadsheet…

7

@Andy_Castille I don’t disagree, this would be ideal, however I don’t have the skills to develop that. What I could do perhaps is interrogate Octoprint via the network or create a simple drag ‘n’ drop in the sheet where the gcode file could be read. Only problem with that would be understanding the various gcode flavours the slicers spit out. I’ll do a bit of research and see what I can come up with. The general consensus seems to be on less manual entry so that’s what I will focus on for the next version.

8

You probably need OctoPrint’s data, not just the gcode. OctoPrint has an API with several events that would be helpful, like PrintDone and PrintFailed.