Jump to content

Canada's top-tier Telescopes & Accessories

Leaderboard

Popular Content

Showing content with the highest reputation since 11/25/2020 in all areas

  1. Try changing your download folder to be in the Windows virtual C drive rather than on vmware-host. The UNC path is causing BYN to report errors in the log like: ERROR - Object must be a root directory ("C:\") or a drive letter ("C"). Although I do not know if that is causing your issue since it worked for a few images. I also wonder whether Windows is going into power saving mode and powering down the USB port.
    1 point
  2. dkerber

    3.2.1 RC2 not saving settings

    It does work! The one I had tried earlier was giving full control to the icon, which didn't help. Changing the permissions on the install directory as listed above did the trick!
    1 point
  3. admin

    3.2.1 RC2 not saving settings

    I'm also an administrator on my PC and I had to change the permission and give write access to "users". This is by no means a permanent solution, but a workaround. I'd be interested to see if it works with write access granted to "users".
    1 point
  4. astroman133

    Dave Livingstone

    Dave, According to the BYE Supported Cameras page the 5D Mk II is fully supported by BYE. Also, BYE is a 32-bit app that runs on both 32-bit and 64-bit versions of Windows. You imply that you have an issue. If you want help, please describe what you do to cause the issue and what you see.
    1 point
  5. astroman133

    connection problems

    You seem to be saying that you are unable to connect BYN's ASCOM Telescope or Focuser control to CPWI to allow you to adjust the telescope pointing and the focuser position from BYN. Do you have the ASCOM Platform installed? This must be installed before CPWI in order for the CPWI ASCOM drivers to be installed. If you can see the drivers in the ASCOM Chooser then this is not your problem. Installing the ASCOM Platform installs other applications like ASCOM Device Hub (Platform version 6.5 or later) and POTH (all previous version of ASCOM, but optional with ASCOM 6.5) that you can try
    1 point
  6. Right click on the application icon and switch to the security/permissions tab. Assign the account you are logged in all the write/read permissions. This should solve the problem, although it should not occur in the first place.
    1 point
  7. The SL3 is a newer camera, and if you are running Windows 10, the low-level Canon driver is already installed with Windows. With older versions of Windows and older cameras, you had to install the driver from the software kit that either came on a CD with the camera or you downloaded from Canon. When users needed to install the CD software in order to get the camera to work with the PC they often chose to install Canon's EOS Utility, which is a general purpose camera control program. The problem is that Windows could automatically launch the EOS Utility whenever the camera is first detected by
    1 point
  8. dkerber

    3.2.1 RC2 not saving settings

    Thanks for the suggestion, but it didn't help. Exactly the same symptoms, even with full control permissions to both the startup link, and the directory itself.
    0 points
×
×
  • 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