Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
PLEASE READ ==> If you get a StructureMap or EdsInitializeSDK() error please RE-INSTALL before posting in the forum <==
  • 0
adelacruz

60 sec, 60.1 sec, 60.2 sec and 60.3 sec

Question

2 answers to this question

Recommended Posts

  • 0

0.3 seconds is a 0.5% variance, so not particularly significant. It would be even less if a 600 second exposure was actually 600.3. That is not bad for an exposure that is started and stopped by a program (BYE) running on a multi-tasking operating system like Windows.

I tested my Windows 10 Pro desktop PC with BYE 3.2.0. I took 5 60 second exposures and examined the EXIF data in the captured images. The recorded times were 60.1, 59.9, 60.1, 60.0, 60.0. The only other manually launched programs that were active were an email program and an analog clock widget that I wrote.

I would suggest running the same test on your system with a minimal number of other apps running. If you see less variation in the recorded durations, then that may tell you to minimize the extraneous apps when imaging.

Share this post


Link to post
Share on other sites
  • 0

"Tv" / "Manual" exposures under 30sec are requested by the Camera and Timed by the Camera.

"Bulb" exposures over 30sec are Triggered and Timed by the PC (or Bulb Remote / Intervalometer).  In the case of PC-triggered Exposures, not only does the PC need to Time the Length of the Exposure but it needs to separately Request that the Camera Terminate the Exposure.  This means variables in the instantaneous CPU Load, the Reaction Time of the USB Drivers and Hardware, and the Camera CPU, and even the Granularity of the Camera's Internal Clock Timer; each of these can contribute to minor variances in Reported Exposure Duration.

In terms of the Exposure, as Rick pointed out above, the few additional Photons Captured or Infinitesimal Sensor Noise Accumulated will be very insignificant - less so than any tiny thin cloud that might have drifted through your FOV.

Please advise if we've missed some critical element - perhaps you are running some Astrometry processes that make Timing more critical.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use