Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Everything posted by astroman133

  1. Guylain, Happy Holidays. Below is what I see. Notice Browser notifications are disabled, but I still see the box at the bottom of the window. The confirmation is gray, not red. Thanks, Rick
  2. Despite disabling Notifications in the web site account settings I still get a prompt from the Edge browser telling me to turn on Notifications. This is an annoyance. Please allow me to completely disable Notifications and eliminate that prompt.
  3. My impression is also USB related. According to Nikon, the only supported configuration is for the camera to be plugged directly to the PC, not even going through a USB Hub. Connecting to the RPi and using VirtualHere could be affecting the communication timing such that the SDK occasionally loses its connection to the camera. This can cause the Nikon SDK to hang which can cause BYN to hang or crash. Canon has a similar issue with their SDK although they do not have any guidance that prevents connection through a hub.
  4. So you need to log on with the username that matches your identifier to access your license from the account profile. This is where you need to come to upgrade your existing license, should that ever be necessary.
  5. Brendan, Thanks for letting us know that your issue is resolved. The Canon210 version of the SDK is for DIGIC II cameras that are not supported by the current Canon SDK. However it is possible that version 2.10 of the SDK does/did support the 1000D which was released in 2008. It may have a problem today with your camera if the camera's firmware has been updated. The 1000D is supported by the current version of the SDK this is the version that you should use since it would support later firmware versions. I am glad that you are working.
  6. BYE uses the same mechanism as the Canon EOS Utility to communicate with the camera. That is, the Canon EOS SDK. In 99+% of the time, if the EOS Utility is able to communicate with the camera then so will BYE. There are 3 notable exceptions to this. 1) BYE checks to see if the Canon EOS Utility is running. If so, then BYE's default behavior is to fail to connect since both programs cannot be connected at the same time. The default behavior of the EOS Utility is to automatically connect with the camera when you plug the camera USB cable into the PC's USB port and power on the camera. This will prevent BYE from trying to connect. The fix is to find the menu option in the EOS Utility and change it so that it is not launched automatically when Windows sees the camera. If this doesn't work then you will need to uninstall the EOS Utility. 2) BYE offers an option to "Select your camera driver" when you click on the connect button. For the 1000D (Rebel XSi) you need to select the Canon driver option. This is for DIGIC III and later cameras. The Canon210 option is for DIGIC II cameras that are no longer supported by the current Canon SDK. If you select the Canon210 option then BYE will not connect since version 2.10 of the Canon SDK predates the release of the 1000D. 3) For cameras that support WiFi tethering, this option must be disabled in the camera since the Canon SDK does not support a WiFi connection and enabling WiFi automatically disables the USB port. This is not an option with the 1000D since it predates Canon's support for WiFi connections so it cannot be causing your issue. I would also say that you should only connect your astronomy instruments directly to the PC or indirectly through a powered hub. A typical USB port can provide 500 milliamps to power any connected devices. With an unpowered hub that 500 milliamps is shared by all devices that are connected to the hub. Depending on the power requirements of the connected devices, 500 ma may be insufficient. With a powered hub, the hub usually provides 500 ma for each device. You should also not extend the length of your USB cabling beyond 5 meters without using an Active Extension cable. The Active Extension cable is essentially a signal booster that allows transmission over a longer distance (the length of the active extension cable). In any case you should keep your cables as short as you can.
  7. astroman133

    EOS -Ra

    BYE checks if the EOS Utility is running and if so it will not try to connect. I don't even have the EOS Utility installed on my PC so my instructions will be necessarily vague. I believe that there are configuration options in the EOS Utility menus that will allow you to disable starting the EOS Utility automatically when you plug the camera into the USB port. There is also an configuration setting in BYE to skip checking for the EOS Utility. Skipping this check is OK as long as the EOS Utility is running, but not connected to the camera. If you cannot figure that out then I would suggest uninstalling the EOS Utility. This would typically be done through the Programs & Features applet in the Control Panel. I hope this helps.
  8. astroman133

    EOS -Ra

    Is the camera in Manual mode?
  9. I doubt that your issue is due to the image size since a 5 second RAW and a 5 minute RAW are about the same size. It would be more of a problem if BYN could not download RAW images to the PC. This is the most common operating method for deep sky astrophotography. I am a Canon owner and it is only very rare and special cases that I would connect my camera with my PC and control it with BYE, but not save the images to the computer. I want to see the images while I am imaging so that I can adjust focus, or change the imaging plan to take more or fewer images.
  10. astroman133


    Also, by default, the Canon SDK does not use a wireless connection. So you must disable Wi-Fi in the camera and connect a USB cable between the camera and the PC. If you search this forum you may find other folks who have been able to pair the camera to the PC via a wireless connection outside of BYE and then BYE and the Canon SDK can connect wirelessly.
  11. However, the downside of saving to the camera is that you don't get to view them on the PC as they are being taken. It should take about 10 seconds to download an image from the D800 to the PC. That is reasonable given the size.
  12. I am not a Nikon owner, so I apologize for not mentioning this sooner. The D800 has 2 memory card slots; an SD card slot and a CF card slot. The camera can be configured to use those cards in different ways. I would suggest testing BYN with different memory card settings. I would select choosing the SD card as the primary card and use the Overflow option so that both RAW and JPG images are saved to the SD card until it is full. I would also make extra sure that neither card is write protected. In other words try each configuration without the camera being connected to the computer. If you get it to work, please come back here and let us know what configuration(s) worked and what configuration(s) didn't work.
  13. So just to recap...With your D800 and BYN 2.0.10 you are unable to save RAW BULB exposure images to the camera. Guylain may ask for a log file where it fails to do that. It is best to delete the old logs then start BYN and go through the steps to take a bulb image with save to camera selected. Then follow the instructions at the link below to send the log without posting it here.
  14. There is a similar request in the Feature Suggestion Box Forum for short exposures of arbitrary length, timed by the PC not the camera. The use case is for eclipse photography. It should be possible because other programs offer similar functionality. Here is the post from the Suggestion Box: I don't know about repeatability of very short exposures (eg < 1 second), but you should be able to use a high resolution timer (.NET Stopwatch class or the Win32 performance counters that are in kernel32.dll) for repeatable exposures of 1.8 seconds as has been requested. It is worth investigating and perhaps putting out as a pre-release feature to see what users think of it.
  15. Does BYN fail the same way when you save your images to the PC? I believe that there are some BYN issues when saving to the camera. Or perhaps I am mis-remembering and it is with saving both RAW & JPG. In any case it is simple to try saving RAW only to the PC.
  16. Do you perhaps have Long Exposure Noise Reduction turned on in the camera? If so, this doubles the exposure time because it causes the camera to take the dark frame after each light frame. BYN does not know this and will fail if the camera does not report that it is ready for the next exposure in a timely manner. Conventional wisdom is to turn off LENR when doing astrophotography, as this automatically doubles your productivity, and take your dark frames separately.
  17. Thanks for letting us know that you have a solution.
  18. Be sure to download the latest pre-release version of BYE.
  19. Scroll to the bottom of this page and click on Download below BackyardEOS. Then at the bottom of the list on the right side of the page, click on Pre-releases.
  20. If you have an autofocus lens on the camera with the lens in AF mode, you should be able to drive lens in small increments from BYN. Then once critical focus has been achieved you need to tape the lens in place and switch it to Manual Focus so that the camera will not try to focus at the start of the exposure. At least this is how it works with my Canon. The advantage of using BYN, rather than the camera's LCD display for focusing, is that BYN measures the diameter of the stars and provides a numerical measure of how good your focus is (FWHM or HFD). LiveView frames are shown very quickly. I don't know how you could adjust any faster or better by using the small LCD display on the camera. The 2 second delay in BYN's capture plan goes before the start of the first exposure in your capture plan. It is not a mirror up delay. BYN does not support Mirror up delay for any camera; at least according to the Camera Support Grid on this web site. I believe that the authors are working to try to support this feature. If you are doing long duration deep sky imaging then mirror lock is totally unnecessary anyway. Not sure where you are seeing exposure times that include the 2 second delay. Please explain. The camera has no concept of a dark frame (except for Long Exposure Noise Reduction) and does not allow you to take dark frames by keeping the shutter closed. It is up to you to prevent light from reaching the sensor. This is usually accomplished by covering the lens, or removing the lens and replacing it with the body cap.
  21. 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.
  22. 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.
  23. 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.
  24. 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.
  • 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