Jump to content

Canada's top-tier Telescopes & Accessories

astroman133

Members
  • Content Count

    3,666
  • Joined

  • Days Won

    131

Everything posted by astroman133

  1. No, you still misunderstand...If you want BYE to take exposures that are longer than 30 seconds, you MUST connect a serial cable between the remote shutter jack on the camera to the PC (to either a serial port or a USB port via a USB-serial adapter). Just connecting a manual remote shutter or interval timer to the camera will not allow BYE to take long exposures.
  2. Other Nikon users have reported the same error (kNkMAIDResult_ValueOutOfBounds). You should find their posts by searching the forum for the error name. They were able to work around the issue by changing the camera setting to 12-bit mode, or by removing the lens. I do not see any resolution. Guylain asked for more information and the threads went dormant.
  3. According to the Camera Support Grid for BYE, the XTi needs a serial cable, in addition to the USB cable, to control the camera for BULB exposures. You should not need the serial cable for non-Bulb exposures. If you want to do BULB exposures with your XTi then you need to follow the link to the Camera Support Grid and scroll down to the bottom of the page to find the links to 2 different web sites of people who sell the remote shutter serial cables that are compatible with BYE. The cable needs to plug into the remote shutter jack on the camera and into a serial port or with a USB adapter into a USB port on the PC. When the Shutter value in the capture plan is BULB, then BYE controls the opening and closing of the shutter based on the specified duration. If the shutter is set to a value other than BULB, then BYE tells the camera when to open the shutter, but the camera controls when the shutter closes. If the images are not being downloaded to the PC then you need to configure BYE to do that. Change the "Save To" setting in the Capture Plan Center to be PC or PC+Camera.
  4. One of the recurring themes in posts by new owners of BYE/BYN is related to the fact that they have purchased the product but are not able to get the software to connect to their camera because the camera is either too new or too old to be supported, or that support is limited to only 32-bit operating systems. It seems that they do not see the Camera Support Grid pages, or they do not see their just-released camera listed and assume that it is a mistake that it is not in the list. It may help to have a pinned topic under Application Support that contains a link to the Camera Support Grid. It may also be useful to add new, unsupported models (e.g. the T6i) to the grid to indicate that they are not yet supported, but support is expected by some date.
  5. Spencer's solution is to install a large heat sink that conducts heat away from the sensor and dissipates it through the camera frame. It is not powered or liquid fed. I had asked how much that actually helps but got no answer.
  6. I am assuming that since the T6i is not listed as a supported model (see the Camera Support Grid at the bottom of this page) that the Canon SDK that is distributed with BYE does not recognize that model. It usually takes Canon some time, perhaps several months, to release a new version of an SDK with support for new camera models. Then, Guylain has to apply to Canon to get the SDK and finally to test BYE against the new SDK and camera. All this takes time, so you need to be patient.
  7. No, that is not what it means. BYE/BYN will not control your guide camera and does not do autoguiding. The dual camera control is intended to allow you to control 2 imaging cameras simultaneously. Both cameras would be Canon (or Nikon, with BYN) DSLRs. PHD is not used for tracking. Your mount should already be tracking. PHD is used for guiding.
  8. John, Perhaps you could post your suggestion in the Feature Suggestion Box subforum.
  9. You looked at the camera support grid, so you know that some of the older cameras require a 32-bit OS, but you never said what camera you have. I have an i7 system running Win7 x64 with 8GM memory and a 1TB hard drive, and USB 2.0 ports. It handles both image capture and post processing roles very well. I think that you will find that image processing programs will benefit more from a fast, large PC than image capture processes.
  10. I believe that the battery level property is working as expected, since it has been this way for quite a long time. In any case the SDK is "not supported" as far as they are concerned. This means that the SDK user community is forced to take it or leave it and there is no mechanism for reporting SDK-related issues back to Canon. It is not ideal, but it is what it is. Perhaps Guylain could eliminate confusion by displaying the word meanings instead of the values. This may eliminate user confusion as to why the values are not indicative of how much charge is remaining.
  11. astroman133

    Key Length

    You not only re-installed, but you upgraded to 3.1.x. You should follow the upgrade instructions here --> http://www.otelescope.com/index.php?/page/upgrade.html
  12. Everyone sees this. This is another case of BYE being at the mercy of the Canon SDK. BYE can only display the value that is reported by the SDK. I believe that the SDK reports the following values: 255 == on A/C power 80 == Normal 50 == Half 30 == Low 1 == Empty This list may be different for some models and/ with newer (than 2.11) versions of the SDK.
  13. Does LiveView display on the LCD screen when not connected to the PC? Is there some setting that is disabling LiveView?
  14. The design of the Canon SDK prevents multiple applications from connecting to, and controlling, the camera at the same time. The simplest way for the 2 apps to co-reside on the same PC is to figure out how to keep the EOS Utility from automatically launching when it senses the camera. That way you can manually run whichever app you want to use. I believe that this is possible. It has been discussed in other threads in the BYE Forum. It may depend on which version of Windows you have and which version of the EOS Utility. This post may be useful --> http://www.otelescope.com/index.php?/topic/78-eos-utility-interferrence/
  15. So, if you have a D610 you probably won't be able to use LiveView for focusing when using it for astrophotography. You will have to adjust focus by taking a short (5 seconds or so) exposure downloading it, review the FWHM of a target star, adjust the focuser, and repeat. This is what you would need to do anyway with a CCD camera.
  16. You need a DSUSB shutter control cable for Bulb exposures AND a USB cable for all other control functions.
  17. I am a Canon user, not Nikon, but this is how a Canon works... It is not necessary to pause/resume LiveView in order to change the ISO and shutter speed, but you cannot change these settings on the camera, you must change them in BYN. At least with BYE, the settings are not changeable from the controls on the camera while LiveView is active. They are if LiveView is paused or the Imaging screen is active. Depending on the current values of ISO and shutter, small changes to either setting may not make a noticeable difference in the brightness of the display. For example, if the ISO is set at 6400 and you change the exposure from 30 seconds to 10 seconds the display may not noticeably darken. Likewise, if you change the shutter from 1/4000 second to 1 /500 second, you may not see the image brighten at all. Most of the change occurs with shutter values between 1/10 second and 2 seconds. If your setting are changed to the same default values every time you switch to Frame & Focus and this is not the behavior that you want, then you can uncheck the Maximum Sensitivity setting (in the LiveView group on the Settings dialog).
  18. The sensor temperature is only available from the EXIF metadata within a downloaded image. In order for BYE to display that temperature the following conditions must be true: Images must be downloaded to the PC The Advanced Setting "Skip READ Exif data must be UNchecked. You must have taken and downloaded an image. This can be either a Snap image from Frame & Focus or an image from Imaging. LiveView, Planetary, or Drift Align frames do not include the temperature.
  19. Sorry, but even with LiveView you wouldn't likely get 24 images per second downloaded to the PC; especially with the newer large cameras. Sure, if the camera has over temperature protection it may shut down due to extended use. You know that BYE only supports ML as long as ML is transparent to the SDK.
  20. Try LiveView during the day with a lens, instead of at night when connected to a scope. LiveView frames are very short exposures and even the brightest stars are small and dim. If your Nikon is like my Canon you can control the brightness of the LiveView frames to some extent by boosting the ISO and setting the exposure to something around 2 seconds. These parameters brighten the LiveView screen to its maximum. This makes the small stars easier to see. There may also be a "Maximum Sensitivity" setting on the Settings screen that does that for you. Once you have the display brightened as much as you can, aim the scope at Arcturus or Vega (or some other very bright star).
  21. Yes, see previous posts. Search the BYN forum for "zoom".
  22. I am glad that you figured out the issue.
  23. This is just my opinion, but your suggestion does not seem to be astrophotograhy related, which is the stated purpose of BYE/BYN. I would hate to see the software become bloated due to features that are outside of the mainstream workflow of astrophotography, and useful only to a few users. That said, as a software developer it does seem intriguing to try to implement.
  24. You also did not say whether or not you are dithering. If so, I would disable dithering, only as a test, to see if your symptoms change.
×
×
  • 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