I've got some code that plays a sound (and also logs a message to a file) based on processing ticks that eSignal presents to my EFS code. I've noticed that the times associated with the ticks seem to be off by anywhere from 1 second to as many as 13 seconds.
For example, eSignal presents my code with a tick, and then my code logs the time to a file and then plays a 1-second sound. I copy down the time that eSignal is displaying when the sound starts. That time is almost always 2 seconds, and some times 10+ seconds, later than the time written to the file.
I realize there can be delays writing to a file, but this seems extreme. So I'm wondering if the time associated with the tick accounts for it. That is, eSignal presents me with a tick, and the eSignal time associated with the tick (from seconds(0)) is, say, 10:00:32 seconds. Now, if the actual clock time is 10:00:37, that could be the time difference I'm seeing.
Does anybody have any experience with this? Does anybody have a feel for how current or fresh tick data is in real-time mode? Any suggestions?
Thanks.
For example, eSignal presents my code with a tick, and then my code logs the time to a file and then plays a 1-second sound. I copy down the time that eSignal is displaying when the sound starts. That time is almost always 2 seconds, and some times 10+ seconds, later than the time written to the file.
I realize there can be delays writing to a file, but this seems extreme. So I'm wondering if the time associated with the tick accounts for it. That is, eSignal presents me with a tick, and the eSignal time associated with the tick (from seconds(0)) is, say, 10:00:32 seconds. Now, if the actual clock time is 10:00:37, that could be the time difference I'm seeing.
Does anybody have any experience with this? Does anybody have a feel for how current or fresh tick data is in real-time mode? Any suggestions?
Thanks.
Comment