Jump to content

Canada's top-tier Telescopes & Accessories

AndrewS

Members
  • Content Count

    8
  • Joined

  • Last visited

About AndrewS

  • Rank
    Stellar Nebula

Profile Information

  • Gender
    Not Telling
  1. Maybe the One Shot selection is the key. I'm in AI Focus mode. I did test it to make sure, before posting, as it had been a while since I had used a lens with BYEOS. I actually worked with the Canon SDK to debug an issue I was having with camera disconnects, with TheSkyX Pro. I thought there were different commands in the SDK regarding whether to attempt autofocus when shooting, but I could be misremembering. Actually, I just found my code, and yes, there is an SDK call, CameraCommand_ShutterButton_Completely_NonAF. According to the developer I was working with at Soft
  2. I believe the 2 above points depend on the camera and lens. With my 7D Mark II and my 70-200mm f/2.8 lens I can be in auto or manual focus and I'm able to adjust the focus via BYEOS. In either mode, taking an image via BYEOS does not change the focus. On the other hand, if I use my 55-250 f/4-5.6 lens, I can't control the focus in manual focus mode, only in AF mode, as you stated. However, the focus still does not change if I take an image with BYEOS.
  3. Hey Aaron, I do already have a Pegasus focusing system. I started doing my own with a Raspberry Pi, but gave up as I didn't have the patience and/or skill to craft a way to mount it to my SCT. The Pegasus system is definitely not cheap, but I am happy with it, other than the eternity it takes to change gross focusing position (e.g removing focal reducer, etc). As it's a stepper, the position is reported to (and adjustable through) BYE via ASCOM. I don't recall, at the moment, if you can type in an absolute position to go to, but I'm sure it's part of the instructions that BYE
  4. I initially had times around 30 seconds. I ran the original 3.1.17 before installing the release candidate, and it was around 21 seconds. I'm not sure why it was quicker, today, other than I've probably rebooted since then. I tend to have a lot of things running, and way too many tabs open in Chrome. As I said, the RC was 7 seconds, but after exiting and running again, it's now taking about 4 seconds. My laptop is quite a bit slower than my desktop PC, but I have not doubt this will also be a huge improvement, there. I appreciate the detailed explanation of the changes. I'm
  5. I would find it handy to have an indicator of the focuser position when using FWHM. I.e. when a new low is established for the FWHM, it is kept for reference. It would be nice to also keep the position of the focuser when that new low FWHM is found. I realize there are other factors to consider (at least with SCTs), such as approaching the focus from the same side, but I still think it could be handy. As I'm always mentally noting the position when trying to find focus, it would be convenient to have it on-screen. A step further would be the ability to return to that position.
  6. I haven't had a chance to try it on my laptop, but the desktop startup time is substantially reduced. It takes about 7 seconds, now. Thanks again, Guylain!
  7. Okay. Thank you, Guylain. Just wanted to make sure my system wasn't the problem.
  8. Did these changes make it into 3.1.17? I'm still getting at least a 30 second boot time to the main window on a desktop with Windows 7 Pro with and i7-4770 and 16GB, running from SSD. It is (not surprisingly) slower on my imaging laptop.
×
×
  • 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