Jump to content

Canada's top-tier Telescopes & Accessories

Leaderboard

Popular Content

Showing content with the highest reputation since 08/21/2021 in Posts

  1. Jim, Scroll to the bottom of this page and click on Supported Cameras under the BackyardNikon column. Then click on the Shoestring Astronomy DSUSB link near the top of the page, just before the table of cameras. Their cable has been tested and proven to work with Backyard Nikon. However, this cable only controls the shutter for BULB exposures. You also still need the regular USB cable for all other functions.
    2 points
  2. You are spot on about how to verify that LiveView causes the camera to heat up. It is not possible to take still photos without interrupting LiveView. The simple fact is that LiveView cannot be causing the sensor to be read out while the camera is in the act of collecting data for an image. With my T5i, I can image while LiveView is active, but the camera interrupts the LiveView display to take the image. Once the image is complete LiveView is automatically resumed. This works with both Tv and BULB exposures.
    2 points
  3. BYN and BYE are limited to the Feature Subset which Nikon and Canon choose to implement and support in their respective SDKs. Often this Feature Set is both rather minimal and lags several years behind the same Features being Introduced in new model DSLR / MILC. Examples are the lack (still) of direct support or acknowledgement of Long Exposure Noise Control (Camera takes and applies an Internal Dark Frame after performing a Bulb Exposure), lack of support for WiFi Connection Setup, lack of support or control of additional In-Camera Focus Modes (Face-modes trip up SDK as do other modes). So
    1 point
  4. That has been fixed a while back. Download the latest and that should do the trick. Keep us posted.
    1 point
  5. The LCD display on the back of the camera is smaller than the camera sensor. This means that the camera has to downsample the image to display it on the LCD display. Using 5X zoom takes part of the full image and displays it on the LCD display at full resolution. The way the Canon software that BYE uses works is to download the same image that would be displayed on the LCD display for Frame & Focus and Planetary imaging. If you put BYE in 5X zoom mode and you see the image magnified, then the camera is in 5X mode. In that case you should not touch the camera to press the Zoom+ button.
    1 point
  6. Unfortunately, this scenario plays itself out a large number of times every night with all sort of DSLR Astro Imagers. They use LiveView in combination with their Capture Software of choice (frequently BYE) in order to perform the Mount Alignment procedures, and the Polar / Drift Alignment, and then when Framing and Focusing on their Target. This often runs up against the LiveView Timeouts of their DSLR. We know - we've been active supporting users on this forum for better than 10 years (Guylain and Rick and I and a few others). Correct, the Sensor is always read in RAW format. But
    1 point
  7. It's not clear where you are getting this information, but it is incorrect. LiveView is NOT the act of Lifting / Holding Open the Mirror. Rather it involves the triggering of the Camera's Video Mode (And Focus and Tracking Logic) activating both the Sensor and the DIGIC 7 Processor and Buffer Memory as well as the extraction of "Frames" from the ROI of that Video Feed and the Queuing of those "Frames" to the USB2 Host Controller and Transmission Hardware - and Energizing the Mirrorbox Lift Solenoid. It is all the Sensor and Controller activity which generates the bulk of the heat, and which
    1 point
  8. astroman133

    Screen stays Red

    Please when you report an issue, always tell us what version of BYE you are using, the version is a 3 part dotted-decimal number like 3.2.2. The BYE splash screen is always black and white. With the main screen you can switch between the selected Daylight color and Night Vision mode with the button that is to the left of the Setting button. If other applications are also in Red and stay red when you exit from BYE, then it is possible that you have launched BackyardRED and that is the purpose of BackyardRED. It turns the entire screen reddish. It has controls to control the opacity of
    1 point
  9. Well, I can tell you that for a T7 the Canon drivers are what you want. Canon210 is for much older, and currently unsupported models. Does the Windows Device Manager see the camera as an Imaging Device? Are you by chance running the Canon EOS Utility. It can be configured to automatically connect to a camera when the camera is first detected. This will prevent BYE from being able to connect with the camera. If the camera has WiFi capability, you need to disable it in the camera's menus and connect the camera to the PC via USB. If Windows is seeing the camera, it may show a
    1 point
  10. 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
  11. Please be courteous when asking for help, no one assumes you're an idiot. We're all here voluntary trying to help. Camera communication with the software is simple, it just needs the USB cable connected to the computer... but... Windows must recognize the camera first. If Windows does not see the camera as an imaging device it can not be seen by any software. It needs to be seen in Device Manager first and if it does not we need to figure out first. s3igell has a few good pointers in his post above.
    1 point
  12. You need to use the Canon drivers, not Canon210 for the T6i. The EdsInitializeSDK() ERROR is an installation error. Reinstall and try again, it should work. Regards,
    1 point
  13. I figured this one out myself and it wasn't BYE's fault, but figured I would post it, as I didn't find anyone else having the exact same issue. Situation: Brand new Rebel T7, ready for its first imaging session Very old (2013-era) small laptop with Windows 10 Enterprise N, build 1809 This laptop used to happily control my old Rebel T2i with BYE 3.1.17 until said T2i's USB port died. Took it out to image last night, and BYEOS wouldn't talk to my Rebel T7. It would error out after selecting the camera as if it wasn't even connected. The computer also didn't re
    1 point
×
×
  • 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