Jump to content

Canada's top-tier Telescopes & Accessories

astroman133

Members
  • Content Count

    3,275
  • Joined

  • Days Won

    114

Everything posted by astroman133

  1. 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
  2. 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 13.10.30.0. 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!
  3. 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.
  4. 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.
  5. 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.
  6. 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?"
  7. Hmmm, I thought that Debug Assert statements are ignored in release builds.
  8. 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.
  9. Just select Bulb from the Exposure dropdown list and enter the desired exposure length in the Duration column.
  10. 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.
  11. This should be a question in the BYN forum, not in the suggested features forum.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
  16. 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.
  17. Werner, This "support group" is made up of the principal author of BYE and members of the BYE community who volunteer their assistance. You may want to read this post which is pinned near the top of the BYE forum: You may notice that your camera is not yet listed. Not all Canon cameras are or can be. Only those cameras that are supported by the Canon SDK can be supported by BYE. If your camera is supported by the most recent North American version of the Canon SDK then the numbers that you provided will help the authors to add the camera to the support list. Typically, Guylain will provide you with a version of BYE to test with your camera. Once you have said that the camera works with BYE it will be incorporated in a public pre-release version for others to test. Thanks!
  18. No, you need the "additional driver" since it is not part of Windows 10 32-bit! Go to the following link and download the EOS Utility. Installing it should install the necessary driver. https://www.usa.canon.com/internet/portal/us/home/support/details/cameras/support-dslr/eos-digital-rebel-xt/eos-digital-rebel-xt?tab=drivers_downloads Be sure to select Windows XP as your operating system. Also note that the driver is an XP driver, so you may need to actually install XP in your VM, not Win 10. Or buy a new camera.
  19. mozgolator, Even with the latest pre-release version BYE will not work with your camera. You need to provide the numbers as requested in Guylain's previous post. There is no need to do so privately or to mask them as they relate to all 2000D cameras. When Guylain is able to incorporate the model (using the numbers that you provide) into BYE, you will be 1 step closer to getting the camera to work with BYE. If Canon has done their job then it should just work but other newer cameras have required him to do some customization. Here's hoping that it will just work. That said, there may be some camera settings that BYE does not have access to that you may need to modify because they prevent the Canon SDK from fully functioning. They may be: WiFi should be disabled Long-exposure Noise Reduction should be disabled High ISO Noise Reduction should be disabled LiveView Focus Mode should NOT be Face+Tracking There may be more settings that you need to change to be fully compatible with BYE.
  20. According to the Supported Cameras grid, the 350D is a DIGIC II camera that Canon stopped supporting many years ago. There is no Plug and Play driver for this camera that allows it to be tethered on a 64-bit version of Windows. That is why the support grid indicates that a 32-bit version of Windows is required. You figured all of this out which is why you installed a 32-bit Windows VM. Running inside a 32-bit VM should work for you, but you still need that Plug and Play driver. The fact that you don't have one is why you see that "yellow triangle" beside the device in the Device Manager. When the camera was released, Windows XP or Vista did not have the system driver built into the version of Windows. That driver was typically installed from a CD that came with the camera. You can download it from Canon's support archives or find a copy of that CD and install the software in the 32-bit VM. If you can download the EOS Utility from the Canon web site (I would suggest version 2.5.1 circa 2008) and install it in your VM and can get the EOS Utility to connect with your camera, then it is very likely that BYE will also connect.
  21. The authors usually give new users a second trial when requested, but I believe that you do need to download and apply the new trial license to either 3.1.17 or the 3.1.18 pre-release version.
  22. astroman133

    After Years

    Jomanda, You can use your old key to get a new key for a price of $0. Since it is free to upgrade, you should download at least version 3.1.17 or the pre-release version of 3.1.18. Scroll to the bottom of this page and click on "Upgrade instructions" under the BackyardEOS column to go to a page with instructions. Just a word of caution...Never post your license key, either the old key or the new key, in this forum or any public forum.
  23. I got here too late. I believe that TSX needs to run just once in Administrator mode to initialize the TSX scripting engine.
  24. Do you mean that you are trying, but failing, to validate your license and username in BYE? That is not logging in! Try using copy/paste to transfer the purchased license key from your My Purchases area of your profile on this web site. The Identifier should be your username (case sensitive).
  25. Be careful about purchasing a mirrorless camera. Many, especially the early models of both Canon and Nikon mirrorless cameras, do not support tethered control by programs like BYE or BYN. I would make sure that it is supported before you purchase a particular model.
×
×
  • 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