Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Everything posted by astroman133

  1. astroman133

    Frame & Focus

    Live View exposures are very short, on the order of 10 milliseconds long. Only the brightest stars will show up at all at prime focus. BYE has a Maximum Sensitivity setting. Be sure to select that before using Live View for focusing. Then point at the brightest star available, like Vega or Arcturus. If you have a lens on the camera then even the Maximum Sensitivity setting may not show stars because they are so small at the shorter focal lengths. In that case you will need to use Snap images for focusing. These should work even with exposures that are only a few seconds long.
  2. I believe that some Nikon cameras have a problem when saving to both the PC and the camera's memory card. So if it works when saving only to the PC you may be stuck. Have you tried doing a factory reset on the camera? This sometimes fixes a setting that BYN cannot read or change but interferes. If you are trying to take a picture with a lens on the camera, make sure that the lens is in Manual Focus mode since the camera will want to be sure that the scene is in focus before taking the picture. If the lens cap is on the camera or if you are shooting a dark sky, autofocus is not possible.
  3. astroman133

    USB hub

    Please also understand that I am only affiliated with O'Telescope as a long-time BYE user and in no way do I speak for the authors of BYE or BYN, so my comments are in no way a commitment that Guylain will address or even investigate what is causing BYN to fail when the camera is connected through a hub. I only state what is likely obvious to all which is that if BYN is able to support that type of hardware setup that there may be several existing and future customers that would be delighted. I used to use a guide camera that worked just fine as long as it was connected directly or through a powered USB hub, but when I connected it via a Cat 5 USB extender would not connect with PHD. When I contacted the manufacturer about this, they indicated that it was likely some kind of timing issue, but my configuration was enough of an edge case that they would not be likely to investigate or make changes to the driver to make it work for me. I put that camera on the shelf and have not used it since, even though I no longer use the Cat 5 extender. I mention this so that if other BYN users have a similar issue to KevW and their workaround is less than ideal, it would be to their advantage to speak up now. The fact that multiple users are potentially affected may make Guylain's investigation of the issue a higher priority. Who knows... If Guylain is able to rally enough SDK users to get Nikon's attention they may be able to change the SDK so that USB port management is more tolerant of the camera being connected via a hub so that it works for all models of camera in all connection situations the same way.
  4. In the future, if you have a question or issue with BackyardEOS, it is more appropriate to post it to the BackyardEOS Forum rather than the General Forum. When BYE is started, the only main buttons that are enabled are labelled Connect and Preview. The buttons labelled Frame & Focus, Planetary, and Drift Align are grayed out (disabled). When you click on the Connect button, BYE begins the connection process. If the camera is plugged into the PC, has been powered on and recognized by Windows the driver selection dialog should appear. For your T4i (650D) you need to choose the Canon drivers. This tells BYE to use the most recent version of the Canon EOS SDK. The Canon 210 version is for very old camera models that are no longer supported by the newest SDK. If the connection process succeeds, the label of the Connect button should say Disconnect, the Preview button is replaced by the Imaging button, and the remaining buttons become un-grayed (enabled). I hope this helps.
  5. astroman133

    USB hub

    KevW, Your question was "Any chance BYN will ever play nice with a hub or is it an issue that is likely to remain?". You seem to be saying that since APT and BYN both use the Nikon SDK for control of the D7000 and since APT works when the camera is connected through a hub and BYN does not work with the same setup, that BYN is doing something wrong. The problem is that for most users and most setups, there is no problem like you are seeing. Complicating this is the fact that while Nikon tells their users not to tether their cameras through a hub, but not why. Notice that I said "for most users and most setups". Some people have had similar issues but perhaps fixed them in different ways...changing their cabling, changing their camera, etc. They have not always told the community how they fixed the issue that they were seeing. Changing BYN's behavior to attempt to overcome this type of problem is likely to take assistance from the community-at-large. Your experience has been different in that you also use APT and have seen different behavior. My comment was that USB port management is handled in the SDK and that BYN does not know that the camera is connected via a hub. Guylain even confirmed this. The same would be true with APT. So how, then, does APT work but BYN fail? I can pretty much guarantee that if Guylain were convinced that he could make a change to BYN to improve its ability to work with additional setups, including USB hubs, that he would surely do so. If you are willing, you can help him to begin this investigation. Your description of the issue is that "Found out quickly that BYN doesn't like a hub". Can you elaborate on this? Please re-describe your setup, in detail, and describe a specific set of steps that consistently causes BYN to fail. This would include the specs for your laptop, the version of Windows that you are running, the USB devices that are connected when the failure occurs, as well as the software that is accessing those devices and what that software is doing. For example, PHD2 version 2.6.6 is connected to a guide camera (ZWO ASI 224) and mount via the ST-4 cable and that guiding is active with 4 second exposures. It would also be important to know that when replacing BYN with APT and keeping the rest of the hardware and software the same, that APT never fails to communicate with the camera. Since BYN distributes the Nikon SDK that it uses, I assume that APT does the same. Can you tell which version of the SDK is being used by APT? Providing this type of detail is the only way that Guylain can begin to investigate and craft a solution. It was also suggested that you only use a powered USB hub to concentrate USB devices into your PC. Did you do this? Did it change the symptoms that you are seeing? Thanks for your patience!
  6. I am not sure what you are using for your Filename Template, but if you add <timestamp> as the unique identifier portion, then sorting by file name is the same as sorting by the file creation time.
  7. In the future please choose a topic that is descriptive of your issue. In this case "D800 does not connect" is a better topic than your name. It helps other D800 users learn from this thread. And in addition to s3igell's questions...Does Windows recognize the camera when it is plugged in and powered on? Is it listed in the Device Manager? If not, then BYN will not be able to connect to it. Perhaps it is due to a faulty cable or connector, but we need more information. Thanks,
  8. astroman133

    USB hub

    KevW, I forgot to mention the following caution is taken from page 180 in the Nikon D7000 manual regarding cabling the camera to the computer: "Connect the camera directly to the computer; do not connect the cable via a USB hub or keyboard."
  9. astroman133

    USB hub

    A USB port usually provides 500 ma. When an unpowered hub is connected to the PC that is what the PC provides. This means that the unpowered hub can only provide a max of 500 ma to all ports. A powered hub can provide 500 ma to each port. So whether a given setup works or not depends on the power actually available to the hub, and how much data is being pushed through it. Again, it is not BYN that does not like to communicate through the hub, it is the Nikon SDK.
  10. eYes, please provide the version of BYE that you are using. Also, some of the newer cameras have LiveView autofocus functionality can interfere with the 5X zoom. I believe that the 6D Mk II is one of those models. Check the camera's menus. If LiveView autofocus is set to Face+Tracking, change it to one of the other modes and then retry BYE's 5X zoom feature.
  11. Yes, as Guylain has said, please report the complete version number of BYE that you are using. The newest pre-release is BYE 3.1.18 RC 11. If you are using a version that is older than 3.1.17 then please update to 3.1.17 or the pre-release before trying to re-create your issue. You specify where the image files are placed by BYE by setting the Download folder on the Settings screen, as well as specifying which, if any, sub-folder organization to use. The specified Download folder should be on a drive that exists and that you have write access to. Also remember that by default Windows hides file extensions for known file types, so the file may be in the specified location, but not be displayed with the .CR2 extension. If all this appears to be the case, please follow the instructions at the following link to post a log file (just one log file, not all of them) of your issue. For future reference, this post is pinned near the top of the How-To's Forum.
  12. Bret, How long are the exposures that are out of order? Where are you getting the time from? The image file name, the image metadata, or from the images file's Properties? Is the BYE Background Worker enabled (on the Advanced settings screen)? I used BYE 3.1.18 RC11 with my T5i and was unable to recreate what you are reporting. I tried with a sequence 1 second exposures and a sequence of 10 second exposures. I made two capture runs; one run did not use the Background Worker and the other did use the Background Worker. In all cases the RAW and JPG images have the same name, including the timestamp portion of the file name. The only difference was with the file extension. This was all as expected. None of the images appeared out of order when viewing the Download folder in Windows Explorer, either when sorted by File Name or by Date.
  13. Bret, If you are sometimes not getting JPG when both RAW+JPG are selected, you should follow the procedure in the previous post of this thread to send the log file to the authors.
  14. Hmmm, I one more suggestion and that is to temporarily disable your anti-virus software while validating your license. It may also take the admins to verify that their license server is up and running.
  15. Use copy/paste to transfer the license key from your "My Purchases" area of this web site to the license validation dialog in BYE. Also make sure that your username is entered correctly...Uppercase letters are significant. Also make sure that your PC is connected to the Internet whenever the Trial version of BYE is started up. This is to allow BYE to validate that your 30-day trial has not expired.
  16. Upon reflection, I may have been a bit harsh in suggesting that the RP may unsuitable for astrophotography. The main use of a temperature measurement of the internal camera temperature is to support removal of noise with temperature-matched dark frames. However the newer cameras do additional processing in the camera, even for RAW frames, they can eliminate much of the thermal noise. So, perhaps Canon is saying that with the DIGIC 8 processor that dark frames are no longer necessary. So if you already have a DIGIC 8 camera it may be worth investigating whether calibration with dark frames actually provides any benefit.
  17. Well, it appears that the EOS RP does not record the camera temperature in the EXIF data. This is very unfortunate and would seem to make this model of camera unsuitable for astrophotography.
  18. Please follow the instructions in the linked post to submit log files.
  19. In order for the temperature to be added to the file name, a temperature value must be put into an image's EXIF data by the camera. You must also give BYE permission to read the EXIF data to pull out the sensor temperature. You give BYE permission to read the EXIF data by unchecking "Skip READ Exif data" on the Advanced Settings screen. Then BYE should read the value of the "CameraTemperature" parameter from the EXIF data and display it in the Camera Information Center portion of the main BYE window as well as substibute it into the image's file name in place of the <temperature> placeholder. If this is not working with the RP then perhaps Canon changed the name of the parameter. You should be able to take an image that is downloaded to your PC and view the EXIF data. If you are unsure how to do this you should read the applicable section of the User Manual.
  20. astroman133

    USB hub

    Kevin, The problem with using a hub with your Nikon camera occurs in the Nikon SDK's communication with the camera. Since BYN relies on the SDK, this means that BYN is at the mercy of the limitations of the SDK. In short, if a fix comes it will be due to Nikon "fixing" their SDK to eliminate the hub limitation. Certainly this seems possible since their main competitor (Canon) has no such limitation. In the meantime, you could try to use only Microsoft certified cabling and high-quality, powered hubs to try to try to find a combo that works. Also make sure to pay particular attention to keeping the cable lengths shorter than the USB specification and no longer than is necessary.
  21. Sorry, but you need to provide more information...What version of BYE are you using? Please provide the complete version number, like 3.1.17 or 3.1.18 - RC6, along with the steps to recreate the error and any error messages that you are seeing. The 4000D is a new model that is not in the list of supported cameras. Perhaps you are the first BYE user to try to connect with that model. Thanks,
  22. Bright stars can be saturated without the image being over-exposed.
  23. With BYE 3.1.18 RC6 connected to a T5i I basically confirmed what the OP reported OP's Item 1) a) Added rows do not have a column for Aperture while the original rows do. b) When the Aperture column is present the shutter column is too narrow to completely display the selected value. This makes it inconvenient to confirm the selected speed since both 1/10 and 1/4000 display the same data "1/…". Also as the OP posted Bulb is displayed as "B...". The column widths do not appear to be re-sizable nor does it appear possible to resize that panel by making the Image Center narrower and the Capture Plan Center wider. c) When I have added rows to the Capture Plan Center and I reset the capture plan, the data in the added rows is reset, but no Aperture column is added when a lens is attached to the camera. OP's Item 2) When no image is loaded, the Zoom- button changes the zoom factor to the same percentage as the Zoom Fit button. The Zoom+ button provides a higher, but nonsensical value. There do not appear to be tooltips for the Zoom+ or Zoom- buttons as well as the Rotate 180, Flip Horizontal, or Flip Vertical buttons. Mouse wheel behavior is inconsistent with regard to Zoom+ and Zoom- functionality. Rolling the mouse wheel away from the palm causes the zoom factor to grow by increments of 10%, but rolling the wheel toward the palm causes it to immediately grow to the Zoom- value. Another issue with the zoom factor. Clicking on the 100% button and then rotating the mouse wheel toward me changes the zoom factor to 75%, 50% and then 25%. At this point the image is both shorter and narrower than the available space. Clicking on the Fit Zoom causes the image to fit to the available space, while keeping the aspect ratio intact. The image grew significantly larger to fit the available height, but the zoom factor dropped from 25% to 24%. My item 3) BYE is not restoring the window size at startup. It remembers the previous session's window location, but not the size
  24. Housemaster0630, Your question is for a different camera,. In the future please create a new post for a new question that includes the camera model in the title so that others can find it. BYE 3.1.18 RC6 includes a version of the EOS SDK that was released in North America in August 2019. That is It does not support the M50. Perhaps it will be supported in the next release. The M50 requires SDK version 13.11.0 or later. Please be patient. Canon does not provide a release schedule and often has widely different release dates for different geographical regions. The BYE developers are in Canada and can only incorporate North American releases of the SDK in their products. Thanks!
  • 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