Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Posts posted by astroman133

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. Did you read this thread which is just below your post on the Backyard EOS main menu?


    It asked the same question. The authors answered that it is supported in the latest BYE pre-release version.

    The EOS-Ra (mentioned in the title of your post) will not be supported until Canon releases a version of the EOS SDK that includes support for that model. SDK releases are totally at Canon's discretion and may not occur for several months after a new camera model is available. For more information you should read the following post that is pinned near the top of the forum.

    Typically, models are not added to the Support Grid until they are in a Release version of BYE.

  8. I made the suggestion to use the ASCOM Device Hub to see the allowed axis rates because while some applications may use the driver's AxisRates values for MoveAxis calls, few apps display them. Since Device Hub does display them, this may provide information that can help Guylain make improvements to how the ASCOM telescope control in BYE/BYN works. Unfortunately each mount can have its own sets of valid rates. Only someone with a Gemini II controller can provide this information to Guylain. That said, I understand that you do have a solution that works for you and so do not want to install something else. Best of luck!

  9. Each ASCOM Telescope driver provides a list of valid ranges of rates that can be used by client applications that use MoveAxis calls. Each axis has a separate set of valid rates. For example, the ASCOM Telescope Simulator supports any rate in the range of 0-3.33 degrees per second and 5-10 degrees per second for both the primary (RA) and secondary (Dec) axes. My Celestron mount supports any rate from 0-5 degrees per second for both axes. Some mounts only support discrete rate values like 16X sidereal, 64X sidereal, 1.0 degrees per second and 5.0 degrees per second for each axis.

    I do not know what the valid axis rates for your Gemini driver. I also do know how BYE translates its percentages into valid rates in all cases.

    If you download my ASCOM Device Hub application and install it from the ASCOM GitHub site (https://github.com/ASCOMInitiative/ASCOMDeviceHub/releases) and then connect it to your telescope, the valid axis rates are displayed on the Telescope Capabilities tab.

  10. You have two choices for in the driver selection dialog Canon or Canon210. Neither is a default. You must choose one or the other. Canon210 is for very old cameras that are no longer supported by Canon but can be made to work with BYE. You should choose Canon since your 6D is a DIGIC V camera that is currently supported by Canon.

    If the Daylight/Night Vision button says Daylight with a light bulb icon and your BYE window colors are not a white/gray/black color scheme then you can go to the Settings dialog, in the General area, and change the Daylight color to White.

    If clicking on the Setting button causes an unhandled exception message then it is likely that you have non-standard permissions in your Windows Registry that are preventing BYE from accessing the area of the Registry where current settings values are stored. Which version of BYE are you using? The full version number is displayed on the title bar (across the top of the BYE main window). For example my copy of BYE reports "BackyardEOS 3.1.18 - RC11". Some Windows 10 users have suffered from incorrect permissions due to changes made by Windows Update. I do not know of a fix for these permission errors.


  • 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