Minor bug on print duration....

[dkightley]

Here's an amusing but very minor bug .......

Sliced a part....and look at the build time!

Capture.PNG (7.39 KiB) Viewed 3509 times

I wonder.......could this be why print estimates have been calculated wrong - there's not 60 seconds in a minute in the S3D world !!!

[wirlybird]

Interesting. If it is like something in one of my systems it won't show an hour until it goes past one hour!

[dkightley]

Printing three of the same model sequentially.....and another strange time:

Capture.PNG (18.17 KiB) Viewed 3505 times

[dkightley]

My guess is a programmer has rounded the floating point sum of the time to execute all the gcode commands to an integer in the wrong place......possibly like this (written in generic VB style code):

Code: Select all

if Time > 360 then
    Hours = int ( Time / 360 )
    Time = Time - Hours x 360
end if
if Time > 60 then
    Mins = int ( Time / 60 )
    Time = Time - Min x 60
end if
Seconds = round ( Time)

.....rather than like this:

Code: Select all

Time = round ( Time)
if Time > 360 then
    Hours = int ( Time / 360 )
    Time = Time - Hours x 360
end if
if Time > 60 then
    Mins = int ( Time / 60 )
   Seconds = Time - Min x 60
end if

Simple logic.....

[wirlybird]

Could be. My thought was it isn't an hour until it goes to 61 minutes. That's how one of my routines works.

[Heutinck]

should it not be:

If time => 360 Seconds then

[dorsai3d]

should it not be:

If time => 360 Seconds then

Might be - if you have no seconds display, what do you show at 359 seconds? What about 330?

[Heutinck]

I was only pointing out that you would need to check for an equal to 360 seconds as well. of course you would have to display the seconds as well.

[dorsai3d]

Simplify3D doesn't show seconds in the time estimate. There's no point in them showing seconds on their print estimate anyways, considering you're lucky if it's within an hour; as far as I can tell, they just take feedrate and distance to calculate time, ignoring acceleration altogether.