How to monitor G-Code stage of print?  

RE: How to monitor G-Code stage of print?

Hi, this feature is not present. I am finally aware of what "Give us a gcode viewer" might look like and I think you are very close to a realistic solution.
The good news is that time to filament change is coming, but that's the only one from the requested features. I'll try to advocate for something like this in the future tho. Thanks for the feedback and sorry I've missed it.

RE: How to monitor G-Code stage of print?

One of the challenges is that the time estimates in octoprint require me to predict how long will the layer take. If I don't want to simmulate this on the zero, i'll have to interpolate between the slicer estimates. That might work better than having nothing tho

RE:

Hi

I get what your saying, the We have a Zero v1 (no cam or plugins) even with huge prints (well over 70mb) the G-Code viewer and it tracking live print it was fairly accurate, however i get a feeling some of that was being done by monitoring WHEN the G-Code was being spit to the printer from the Pi, rather than a calculation... so i agree another method for time would be required i think... Each layer time doesnt concern me too much, BUT it is nice to have, some prints at 3 hours, had 30 mins on the first layer, it was nice as you had an idea you could go and do something else and know the printer would be ok for at least 30 mins (as there was a color change on later 2).

My goal here is to have something more granular than an over all percentage, and OctoPrint allowed me that with the G-Code viewer, i look forward to seeing what you come up with (needs to work locally, not too worried about cloud, if it works there as well, great, even if its just what layer the printer is on (as there is a time delay between cloud and local with much local and WAN network congestion, timing will be an issue).