If you are using machine control panel in S3D to print ignore this post (think about why do you risk using non dedicated machine to control a long running real time process but anyhow ignore this post it's not relevant for you)
If you are using OctoPrint you know that it can't properly estimate the print time of your G-Code file
You are on this forum so you are using S3D and you know it can't properly estimate print time fo G-Code it's generating... also, you know S3D can't directly shoot the G-Code file to OctoPrint...
2 things that can help, both of course open source and free..
* gcodestat - https://github.com/arhi/gcodestat - can shoot files directly from s3d to octoprint + can preprocess files embedding M117 codes into them with exact time to finish values
* gcodestatEstimator - https://github.com/arhi/OctoPrint-gcodestatEstimator - a plugin for octoprint that reads embedded M117 codes and uses that data so octoprint can display proper (now correct) time to finish values (note that this plugin requires octoprint 1.3.9 or newer, 1.3.9 is not yet out, you can build it yourself, should be available soon depending on how quickly Gina can fix few remaining issues)
I'm making this "separate topic" 'cause while in number of topics about wrong time estimates data about gcodestat, how to set it up, use .. exist, they are spread trough the forum and are hard to follow, so if anyone have any questions (ideas, suggestions..) better put them here