incorrect print time estimates (S3D), layer count etc
-
@nhof It's not something that affects my daily printing a lot. The reason for this post is to simply report it to management. I can live with that for a while, it's not a big deal, as long as it is being fixed. I have been experiencing this for years I think, this is why came to report finally. I am not a firmware programmer, so all I see as a consumer is that only duet has this problem for some reason. So, I am here to report the bug. Hope David can have a look or somebody else from Duet3D.
-
I noticed the same issue with my jobs after I added a G1 command to move the print-head up away from the model after printing - the Duet counted the post-print Z move as layers.
There were two solutions I found:
- You can add the character "E" to a comment after any G1 move you don't want counted toward the layer total on the Duet3d, like this:
G1 Z100 ;This move counts toward the layer total.
G1 Z200 ;E This move does not.- You can put any non-print Z moves in a macro and call that with M98. The macro will not be counted in the layer total:
M98 P"macros/pre_print.g" ; nothing in this macro file counts towards layers
; Start of job "object.g
... ; G1 Z moves here count towards layers
; End of "object.g"
M98 P"macros/post_print.g" ; nothing in this macro file counts towards layers. -
Hello @Vlad
I do understand your frustration with the issues you are running into (I have built many industrial automation machines and dealt with my fair share of supplier woes), however I do think your approach towards getting them solved may be less than productive.
For example, posts such as 'Half-assed update...' and others could be considered unprofessional, and might even damage goodwill with both the Duet team and the community here. Even while dealing with trying issues it's good to remember that we're all human, and to try and find professional ways to communicate frustration.
It's also important to keep in mind that this is a public forum and is frequented by people in the 3D printer community and industry (which is surprisingly small). As a business owner yourself, I'm sure you're aware of the importance of maintaining professional image, and that it does not just apply in the context of communicating with your own customers, but also in dealing with suppliers and others. We would hate to see your reputation tarnished by a few trivial comments written in haste.
I don't personally hold ill will toward you or anyone. I'm writing this simply because I made these same mistakes in a past life, and hope that my hard-learned lessons might be of service to a newer player.
-
@vlad said in incorrect print time estimates (S3D), layer count etc:
As a side note, I am sure you have never said "nsufferable twat" any man in person. Right? What a brave man Couch braveman with virtual big balls.
I'm not one to stand down to the likes of you. If you behaved in person the way you've behaved here I'd have said exactly the same thing to your face. If there's anyone acting tough behind a keyboard here, it's you.
I get that you have high expectations, but your inability to communicate with others in a cordial tone is doing you no favours. I and many others have tried to help you and you've shared very little good will in return.
-
@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.
-
Hi vlad, You still not taking the happy pills!
Every thread you start ends in abuse from you> -
@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.
-
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
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
@phaedrux You have the power against these kind of people, the power of silence
-
@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.
-
@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.
-
This post is deleted! -
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
-
@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-alpha2Support 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 -
It would seem relatively straight forward for dc42 to support these codes and use them.
Frederick
-
@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. -
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
-
@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.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@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.
-
@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.
