Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Everything posted by astroman133

  1. Please be patient. You provided info that admin needed just a few minutes ago. He needs to incorporate those numbers into the program and provide a new pre-release version for you to try. He will post back here when a new version is available for you to test. You are correct about the SDK's non-support for WiFi and the fact that you must turn WiFi off in the camera in order for USB to work. The good news is that a wired connection should be faster and more reliable than WiFi.
  2. astroman133

    Mirror Up

    When doing long exposure AP, the milliseconds of vibration, if there is any vibration, are overwhelmed by the following several minutes of exposure time. This makes mirror up unnecessary for that type of imaging.
  3. astroman133

    Mirror Up

    John, I found the old thread that you referenced. It appears to end with no confirmation that Guylain's changes have solved the issue with Mirror Lock on Nikon cameras. This lack of feedback is likely why the support grid still does not indicate mirror lock support. It is not clear whether the current pre-release supports that capability, but it may be worth trying. If you do try, regardless of the outcome, please report what you have found. While mirror lock is not particularly useful for deep sky astrophotography, there may be other uses where it is beneficial. Even though nobody else volunteered to test the mirror lock support in BYN, other photographers my be looking to utilize it.
  4. astroman133

    Mirror Up

    John, Guylain may have better information, but according to the BYN Camera Support Grid, mirror lock up is not supported for any Nikon cameras. This is likely due to the design of the cameras and/or lack of support by the Nikon SDK that BYN uses.
  5. The Canon SDK uses a Microsoft C++ Run-Time Library (RTL). That piece may be missing from your target system. If so, you will need to install it before BYE will work. Don't wait until you get to the field...Test it at home.
  6. A Windows access denied error is usually due to 1 of 2 causes. Either you do not have read and execute permission on the file or you are trying to act on a file that is locked by another process. You could log off and back on again to ensure that no other process has control of the file. You could also look at the permissions to be sure that you have read & execute permission. You said that "it will not execute". Is it possible that it does execute, but that the installer is failing because it does not have permission to complete the installation?
  7. You can still install on the D:\ drive, just install to a different folder on D:.
  8. I am sure that your info about WiFi usage will be very useful to users with cameras that have that capability. Thanks for sharing! In my experience with BYE, even with a wired connection, what Guylain means with "all bets are off" is that the Canon SDK can lock up which causes BYE to lock up. This requires you to use the Task Manager to kill BYE. I mention this because if you have a Premium license you should keep a saved copy of your capture plan so that you can be up and imaging more quickly after you have restarted and re-connected BYE with the camera.
  9. I believe that for the original M6 that Canon does not support tethered shooting via a wired USB connection, as with all of their previous mirrorless cameras (M1-M5). BYE uses the Canon EOS SDK and only supports cameras that are, or were, supported by that SDK. That said, it seems that Canon may have learned how important tethered shooting is to their users. According to user reports, the M6 Mark II does support tethered control and is supported by the pre-release version of BYE 3.1.18.
  10. I have had BYE ask to re-enter my username when I tried to use it while traveling away from home...I had thought it was due to changing the PC's local time zone. Neat video Aaron! Next time you forget your password, just change it. When logging in, click on "Forgot my password" and it will take you through a process to reset the password. Once complete you can then see your license.
  11. I believe that it is common for the Telescope.AxisRates method to return the rates from slowest to fastest for the requested axis, but you should expect that the rate objects could be in any order. Don't forget that each rate is actually a range of rates from a minimum value to a maximum value. In the case of the rates for the Gemini driver, the min and max values are the same. This means that only 3 rate values are valid. It is possible that the AxisRates for a given axis could be empty. This should only occur if CanMoveAxis for that axis is false. Also, 0.0 is always a valid rate, since calling Move Axis with a value of 0 returns to either sidereal tracking or not, depending on the Tracking flag. The three rates for the Gemini mount are not slew rates; they are for MoveAxis calls, although the fastest speed may also be the rate at which the mount slews. I would be extremely surprised if setting the speed to Center (20X sidereal) would affect the speed at which the mount slewed across the sky to a new target. It does, however, make sense to do frame and focus jog moves at 20X. I really think that it will be confusing for people choose percentage values for the MoveAxis speed when those values can map to invalid axis rates. Giving them only a selection of valid rate values seems likely to cause less confusion. Just my 2 cents.
  12. Right now BYE displays a percentage that is changed via the up and down arrows, but the code could be modified to use a list of valid axis rate values that a user scrolls through with the up and down arrows. The displayed values would be numeric rather than descriptions like Guide, Center, and Slew (which are specific to the Gemini driver). That type of approach could work for all drivers that support MoveAxis calls, BYE would just need to figure out a few valid rates (like a slow rate, a fast rate, and an in between rate) for the user to select from.
  13. BYN uses the Nikon SDK to manage communication with a camera. The Nikon SDK is provided by Nikon. The problem with the 3X00 models is that Nikon does not support them in the SDK. If they did, BYN would most likely also support them.
  14. The tricky part is to make sure that whatever speed is used for calls to MoveAxis is in the list of valid Axis Rates for the driver/mount being used. In a previous post, I described one approach that could be universal to accommodate drivers/mounts with one continuous range of rates, multiple split ranges of rates, multiple discrete rate values. I would suggest that Guylain consider something similar. He just needs to think about it in the context of BYE/BYN.
  15. Yes, that may be why the BYN Supported Cameras grid indicates that none of the Nikon models support the Mirror Lock feature.
  16. You have two identifiers because you created two accounts. You should log in with the account that you used when you purchased your license.
  17. You did not need to remove the Trial copy of BYE since it is all the same software. Just validate the purchased license and replace the trial license from the Padlock button at the upper right of the BYE main window. That message may be due to the fact that BYE only sees an expired Trial license. Just validate the Premium license in place of the expired Trial. You get the Premium license key from your Profile on the web site.
  18. I believe that the license key that automatically appears is the active license. So, if you upgraded from Classic to Premium, it is the Classic license key that is displayed until you replace it with the new Premium license key.
  19. One caution...Never post your license key on this, or any, public forum. Almost all validation errors are because the user has mistyped the license key and/or entered an incorrect identifier. Here are the correct steps: Log onto the O'Telescope web site with the same username that was used to purchase the license and select My Purchases from the menu list. Locate your Purchased license and swipe across the license key to select the entire key and press Control-C to copy the key to the clipboard. Do not try to manually type the license key. Launch BYN and click on the Padlock icon at the right end of the title bar and click on the Edit license... button when the About dialog is displayed. Type Control-V to paste your key into the Licence Key field and type your username (it must be letter for letter the same, including the correct case) as your O'Telescope username. Click on the Validate button.
  20. The model of camera should not matter. Please provide the details of exact steps that you perform to cause the error. A screenshot of the error would also be nice. Thanks!
  21. I seem to remember a limitation where your symptoms would happen with certain memory card configurations. If you have RAW and JPG configured to go to different memory cards, your symptoms may improve if you have both image qualities going to card 1 and only switch to card 2 when card 1 is full. This is discussed in Setting the Image-Recording Quality on page 169 of the 5D Mk IV Instruction Manual. Let us know how this works for you.
  22. astroman133

    Canon 5D Mark II

    The camera model was not in the attached log because Windows is not loading the plug and play driver. How did you see the model?
  23. astroman133

    Canon 5D Mark II

    The original poster of this thread stopped replying several months ago. AFAIK his problem was never solved. He never told us what version of BYE he was using...It could have been an old version that did not support the 5D Mk II. The Canon215 SDK version was dropped since the Canon version supports all the same cameras plus newer models. It appears that the Canon SDK does not see the camera. After the camera has been plugged into the PC and powered on, you should see the camera in the Windows Device Manager. This means that Windows has recognized the new USB device and loaded the low level driver. The low level driver is usually part of Windows. Do you see the camera listed in the Device Manager when it is plugged in and powered on? If not, this is either a bad USB cable or a malfunctioning camera, given that you have made sure that the camera's WiFi capability has been turned off. You could try connecting to the camera from the EOS Utility, but if Windows does not see the camera then the EOS Utility will fail as well. Canon should be able to help you get the camera recognized by Windows and to connect with the EOS Utility.
  24. According to the previous screenshot from the ASCOM Device Hub the Gemini.NET driver only supports 3 discrete rates for use with MoveAxis. Those rates are 796X sidereal, 20X sidereal, 0.5X sidereal. That is it. This is why the percentage value in BYE does not change the speed. It then makes sense that these 3 discrete rates map to the Guide (0.5X sidereal), Center (20X sidereal), and Slew (796X sidereal) radio buttons in the Gemini virtual hand controller as shown in JT's screenshot above. BYE's approach of using a percentage value to alter the MoveAxis speed is fine for a mount that has a broad range of Axis Rates like a Celestron mount where any value between 0 and 5 degrees/sec is valid, but will not work in other cases. Such as when a mount supports only a small number of discrete rates, like the Gemini driver/controller or even when it supports multiple smaller split ranges like the ASCOM Telescope Simulator (see my previous screenshot). When I wrote the Device Hub, I tried to take all types of situations into account. For drivers like the Celestron driver with an Axis Rate range of 0-5 degrees/per second, I arbitrarily chose values of 16X, 64X, and 2 deg/sec. For drivers like the Simulator with ranges of 0-3.33 and 5-10 deg/sec I use the midpoint of each range, so the MoveAxis rates used by DH will be 1.67 deg/sec and 7.5 deg/sec. For the Gemini the user could select any of the 3 discrete rates for MoveAxis. The user selects one of the rates from a dropdown list. I hope this explanation is of help.
  25. eJoe, There is no software difference between the Trial and Premium editions. The only difference is the License. So all you needed to do was to bring up the License Vaidation dialog and paste your new Premium license over the Trial license. No uninstall/re-install was necessary.
  • 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