Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Everything posted by astroman133

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Please follow the instructions in the linked post to submit log files.
  6. 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.
  7. 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.
  8. 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,
  9. Bright stars can be saturated without the image being over-exposed.
  10. 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
  11. 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!
  12. That seems hopeful. S3igell, your post seems contradictory...in that it says that the camera has a USB-C port, but later it says "There is NO External Remote Control Port" So what is the USB-C port for, if not remote control? I read some articles about using the EOS Utility with the M6 Mk II and a USB connection so it does seem possible. However, it may be many months before Canon releases an SDK in North America with support for the camera.
  13. I would also say that there are applications that overlay a visible timestamp on the image, rather than in metadata or the Windows file time. BYE does not currently provide that functionality. Doing so would be tricky. What time would be displayed? the time when image capture started? the time when image capture ended? the time when the image becomes available on the PC? Such functionality may need to support multiple use cases, i.e. use the time at different parts of the capture process.
  14. That said, there are time service applications that keep the PC time very accurate. The accurate time is provided by a network of terrestrial NTP servers, rather than from GPS satellites. I have used the Meinberg NTP service available here --> https://www.meinbergglobal.com/english/sw/ntp.htm#ntp_stable I used this time service to keep my PC time accurate for shooting the 2017 solar eclipse. It worked well. Your post may be of interest to others, but unless you provide a descriptive name for the title, nobody is likely to find it. Also, there are multiple timestamps in the EXIF data for an image. Some are put there by the camera, and some by BYE. In addition, you can have BYE put a high resolution timestamp in the name of the file, which I believe is related to the time that the Take Picture command was sent to the camera. The image file timestamps that are available by reviewing the image's properties are based on the system time when the image file was created by the Windows File Manager. You should experiment to find which of the timestamps is most useful for your application. You also need to have an accurate time in the camera. You must set this manually as BYE cannot change the camera's time.
  15. It should not matter how the SDK communicates with the camera (wired USB, Bluetooth, or WiFi), in should only matter that the SDK does support the camera for remote tethered shooting. So a telltale question is "Does the EOS Utility support the camera?"
  16. Hmmm, I thought that Debug Assert statements are ignored in release builds.
  17. astroman133

    SDK error

    First, with the 50D you need to use the Canon SDK (drivers). The Canon210 SDK is for very old models. I recently installed BYE on a new laptop. I got the same error that I fixed by changing the permissions on the parent folder that contains the BackyardTEMP and Download folders and all its children. I gave full control to authenticated users.
  18. Just select Bulb from the Exposure dropdown list and enter the desired exposure length in the Duration column.
  19. PLEASE READ AND REPLY. When asking a question or reporting an issue state the full 3-part numeric version number of BYE, as displayed in the BYE title bar. This information provides context to help in answering your post. It is very important. For example, you have 3 cameras that were released by Canon at 3 different times. If you are trying to connect to a camera that was released after your version of BYE was released then that would be the most likely reason for a connection failure with that camera but not the others.
  20. This should be a question in the BYN forum, not in the suggested features forum.
  21. Why couldn't you take the laptop, camera, and cable into the house to launch BYE (twice, if necessary), validate the license and connect. Then carry all the gear out to the scope? Or you could also test BYE's ability to connect and control the camera entirely in the house with a lens on the camera and once you have verified that BYE is operating as designed, purchase a license that does not require the Internet connection.
  22. I believe that you have bumped up against a limit with how many times a Trial license can be validated. This may have occasionally happened to users in the past. The authors may be able to address this. Once you can validate the license I would suggest that you use the Trial license to test BYE with your camera at the kitchen table rather trying to test it without Internet access. Since your 350D does not have LiveView you won't need to test the Frame and Focus, Planetary, or Drift Align functionality that uses LiveView. Most of what you will want to test will be shooting BULB exposures with a remote shutter (DSUSB) cable. Once you are sure that it works as advertised and is compatible with your camera, you can eliminate the need for revalidation by purchasing a Classic or Premium license.
  23. There may be a compatibility restriction of you are using a very old camera. BYE attempts to allow users of DIGIC II cameras to use them with BYE. However since Canon no longer supports them, they have not provided drivers for modern 64-bit versions of Windows. Therefore if you have one of those models, it can only run on 32-bit versions of the O/S.
  24. You need to copy the licence key and the identifier exactly as they are displayed on the My Purchases screen and enter them into the license validation dialog in the BYE or BYN. The best way to do that is to swipe across each of the text strings and copy the data to the clipboard then immediately paste the data into the correct field of the validation dialog. Do not try to manually type them.
  25. You should be able to exceed the 5 meter max length limit if one of the cables is an active extension cable and neither of the cables are more than 5m in length. That is the purpose of the active extension cable.
  • 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