incorrect print time estimates (S3D), layer count etc

zapta

@phaedrux said in incorrect print time estimates (S3D), layer count etc:

Do they also give you 3 ways to estimate the file completion?

Estimations are like weather forecasts, we need just one

DWC is a great board but when it comes to progress and estimations, it's lacking compare to some other 8 bit boards. Here for example it ranges from 1:18H to 7:45H. https://i.imgur.com/yWE0ZQC.png

I wish I could display only one of those and have it also controlling the progress bar.

chas2706

Hi vlad, You still not taking the happy pills!
Every thread you start ends in abuse from you>

dragonn

@zapta what other 8 bit boards? As far I am aware no 8-bit board have any kind of progress and time es terminations. They only have a file progress bar when printing from SD-card.

fcwilt

@zapta

Hi,

Can you show us an example of an "accurate" 8 bit board?

Before settling on the Duet family I tried many other boards - I don't recall any with an "accurate" display of time remaining.

Frederick

whosrdaddy

@phaedrux You have the power against these kind of people, the power of silence

deckingman

@whosrdaddy said in incorrect print time estimates (S3D), layer count etc:

@phaedrux You have the power against these kind of people, the power of silence

Yup - that works for me.

zapta

@phaedrux You have the power against these kind of people, the power of silence

Different strokes for different folks. Sometimes it's useful to call out bullies and rude behavior.

zapta

This post is deleted!

zapta

Can you show us an example of an "accurate" 8 bit board?

@fcwilt (and @dragonn), yes, my other printer, Flashforge Creator Pro, 8 bit Mighty Board with Sailfish firmware. It uses the percentage marks that S3D includes in the file in form of M73 commands. Simple and effective.

This is how the code looks like

https://github.com/jetty840/Sailfish-MightyBoardFirmware/blob/4d8456e54c537dd32775095ed2715d41f5961e6c/firmware/src/MightyBoard/Motherboard/Command.cc#L2144

https://github.com/jetty840/Sailfish-MightyBoardFirmware/blob/4d8456e54c537dd32775095ed2715d41f5961e6c/firmware/src/MightyBoard/Motherboard/Command.cc#L2019

Phaedrux

@zapta Is that using file remaining percentage, or is it based on a path planner estimate of what the actual print moves will take to complete?

Slic3r PE also supports M73 time estimates, but it bases the estimate on a very accurate print time estimate based on using the marlin path planner for actual print times.

From the Slic3r PE 1.41 Alpha 2 release notes:
https://github.com/prusa3d/Slic3r/releases/tag/version_1.41.0-alpha2

Support for the "Time to end of print" G-codes
Starting with this release, the time estimator emits a new M73 code for the Marlin firmware flavor at minute intervals, informing the firmware about the time to end of print in both normal and silent mode. Since the 3.3.0 release, the Prusa i3 MK3 firmware is able to display the accurate estimate of the time to the end of print by interpreting this new M73 code.

The format of the new M code is the following:
M73 Pxxx Qxxx Rxxx Sxxx
where P is the percentage of the total time already printed in normal (aka full power) mode, R is the time remaining for normal mode in minutes, Q is the percentage of the total time printed in the stealth mode, and S is the time remaining to the end of print in the stealth mode.
Suppressed for gcode flavors other than Marlin

fcwilt

@phaedrux

It would seem relatively straight forward for dc42 to support these codes and use them.

Frederick

dragonn

@zapta said in incorrect print time estimates (S3D), layer count etc:

Can you show us an example of an "accurate" 8 bit board?

@fcwilt (and @dragonn), yes, my other printer, Flashforge Creator Pro, 8 bit Mighty Board with Sailfish firmware. It uses the percentage marks that S3D includes in the file in form of M73 commands. Simple and effective.

Sorry but that has complete nothing to do with you board, ale the have lifting is doing by the slicer.
But I vote also for implementing M73 into Duet.

zapta

Sorry but that has complete nothing to do with you board,...

Well, that 8 bit board does interprets the M73 commands and the Duet board doesn't

A side note, currently simplify 3D doesn't generate M73 for reprap machines since reprap doesn't support it but I found this workaround using the [progress] macro of S3D (the article has a type, use [progress], not [ progress ]).

https://adrian.siemieniak.net/portal/how-to-add-progress-bar-to-your-3d-printer-with-simplify3d/

M73 P [progress]

I inserted it in the layer change script but I can't see why it cannot injected in the retraction script to get more accurate percentage changes.

Cura seems to have a plugin that inject M73's but I didn't try it and don't know how it computes the percents. https://www.thingiverse.com/thing:1220006

dc42

@nhof said in incorrect print time estimates (S3D), layer count etc:

It might be possible to change the parser to look for the last 'Layer xxx, Z = yyy' comment instead as it might provide a more reliable object height value, but I'm not sure how easy it would be to implement.

That's exactly what I already have on my work list. According to the GCodes wiki at reprap.org. M532 is only supported by Repetier firmware, and I've never see it generated by a slicer. OTOH most slicers do generate layer start comments. The option to skip some objects that has been requested by more than one user also requires comments to be parsed, to identify which object is being printed.

zapta

@dc42, I wonder, board developers like you and slicer developers like Cura, S3D and Slic3r are on both ends of the same gcode protocol. Are there forums or communication channels between the two groups? For example, to discuss standard representation of estimation metadata that slicers can pass to the boards.

dc42

@zapta said in incorrect print time estimates (S3D), layer count etc:

@dc42, I wonder, board developers like you and slicer developers like Cura, S3D and Slic3r are on both ends of the same gcode protocol. Are there forums or communication channels between the two groups? For example, to discuss standard representation of estimation metadata that slicers can pass to the boards.

If there are any such channels, I am not aware of them. Every slicer seems to use different metadata keywords, and they often change.