Filename time stamp discrepency

[johnastro.info@gmail.com]

We are part of a citizen science project in collaboration with the UK government to assist them in tracking space debris. Specifically they have asked us to track the Remove Debris satellite that was launched this week from ISS. Camera lenses and hence DSLRs are ideal for measuring their position, but very accurate time data are required.

Problem: The filename timestamp lags the shutter open time by up to half a second

At some point, this time stamp was changed to reflect the shutter open time rather than the file write time. Thanks. However, in the latest versions of both BackyardEOS and BackyardNikon, the time stamp can be anything from 0.3 seconds to 2.0 seconds out, depending on the speed of the PC. This is still much better than the file write time, but ideally we need the accuracy to be 0.1 seconds or better.

We would be very grateful if the timing accuracy could be improved.

We tested the accuracy of the time stamp by photographing a clock displaying milliseconds. I wrote a Java app that displays the seconds and milliseconds. To run the program on Windows 10, unpack the zip file and double click on the clock.exe. All the required Java run time files are supplied in the correct relative directories. To uninstall after using, simply delete the folders you unpacked. 

https://drive.google.com/file/d/1ZbdxBuLQIGoz6pQw6GwsYCYGfKjH9V_R/view?usp=sharing

Alternatively, if you have a fast android device, the app: AtomicClock provides a millisecond output.

We would really appreciate your help. We believe it to be a very worthwhile project.

Thanks, John