hexagon logo

Runtime script with inexplicable results...

I have a function in my scripts to calculate the runtime in seconds for a program, using the Timer value from windows, which returns the current time as seconds from midnight.

The blue code is my script run at the beginning of a part program. The red code is what is run at the end. (I've cut and pasted these sections from the scripts...they are too long.) In the event that a program runs through midnight, I have a section in the red code to correctly calculate runtime. I've tested this code in the excel editor while resetting my computer clock to 11:59 PM and running it through midnight, and it works. Unfortunately, this code does not work when running PC-DMIS through midnight. I get program times of more than 86400.

Any ideas why this is not calculating correctly only when run through PC-DMIS?

[COLOR="Blue"]Sub Main()

Dim BeforeTime As String
BeforeTime = Timer
BeforeTime = CLng(BeforeTime)

End Sub[/COLOR]

[COLOR="Red"]
Sub Main()

Dim Aftertime As String
Aftertime = Timer
Aftertime = CLng(Aftertime)
Dim RunTime As String

If Aftertime < BeforeTime Then
RunTime = (86400 - BeforeTime) + Aftertime
Else
RunTime = Aftertime - BeforeTime
End If

End Sub[/COLOR]
Parents
  • Just as a note....when you start tracking this stuff in-depth, things really start popping out. Things you never thought were a problem. Trends over months can be observed, and you can really start to tweak things to get the CMM running optimally. It's the next leap forward if you have the desire to improve. (And don't have datapage, you cheap bastards...)
Reply
  • Just as a note....when you start tracking this stuff in-depth, things really start popping out. Things you never thought were a problem. Trends over months can be observed, and you can really start to tweak things to get the CMM running optimally. It's the next leap forward if you have the desire to improve. (And don't have datapage, you cheap bastards...)
Children
No Data