Jump to content

Canada's top-tier Telescopes & Accessories

astroman133

Members
  • Content Count

    3,307
  • Joined

  • Days Won

    117

Everything posted by astroman133

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. I got here too late. I believe that TSX needs to run just once in Administrator mode to initialize the TSX scripting engine.
  6. 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).
  7. 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.
  8. Ron, Have you thought about setting the exposures individually instead of trying to use bracketing? I like the idea of BYE being able to do short, high-precision exposures via a shutter release cable, but recognize that high-precision timing with Windows can be tricky. Still, as you say, others claim to have done it.
  9. The likely reason that the DSUSB solution is priced at that level is that the cables are hand-made in small volumes and are mostly needed for older cameras where the vendor (Nikon) does not support BULB exposures over the regular USB cable. As people upgrade their cameras, the demand for DSUSB cables is declining since virtually all of the new Canon and Nikon cameras support BULB via the regular USB cable.
  10. Use of BYE does not require logging in. Are you talking about validating your license?
  11. I have a friend who swears by QHY's PoleMaster software, though I have never used it. I mostly image from my observatory and use PHD2's drift align functionality to tweak my PA, when needed.
  12. AstroTortilla can be slow, if not optimally tuned. For example, if you have installed ALL of the astrometry data files and have set a Search radius of 180 degrees and set a large Scale Maximum value then you have not given AT any hints about the image scale in the picture or where in the sky the object may be. By removing the unneeded data files (I just move them to a different folder on the same drive), connecting AT to my scope, and setting the some of the parameters wisely it takes me about 20 seconds to solve an image. The most important parameters to change are: Set ScaleMax to 2 times my field width Set Search radius to 6 degrees Raise the sigma value to reduce the number of stars to match With a 5 second exposure a sigma value of 250 gives between 100 and 150 stars to match.
  13. astroman133

    Dithering

    There are no dithering settings that are right for everyone. The resolution of the guide camera and the resolution of the imaging camera must be taken into account when determining the optimum settings for your equipment. Some of the settings for dithering are set in PHD2, and some are passed to PHD from BYE. There is a post in the How-To's Forum about Debunking Dithering. Have you read it?
  14. I believe that "others" means other camera models. The fact that you are unable to download both RAW and JPG for the same image could have multiple causes. Camera cause...SDK cause...BYE cause. Guylain will have to work his magic to determine what is going on and where the error could be. One thing that you can help to sort out is why the image does not display when you configure BYE to download RAW+JPG. One possibility is that BYE bypasses displaying the image if both downloads do not occur, even though it actually does have an image to display. The way to test this is to choose RAW only as the image type to download. Does the image display in BYE's imaging window? If it does not, then your comment that BYE 3.1.18 RC4 is working with the EOS R is incorrect as the authors intend that the image be displayed after it is downloaded from the camera.
  15. Based on past evidence, the best advice is to NOT upgrade the camera's firmware unless you are experiencing a problem that the upgraded firmware addresses. Doing so can break the ability to operate the camera while tethered to a computer. This is due to the possibility that Canon will need to update the software that is used for tethering (the Canon EOS SDK) before tethering will once again be possible.
  16. According to the provided screenshot you chose the Canon210 drivers (SDK). That is for the very old cameras. You should choose Canon drivers instead.
  17. You can download the manual from the MBox web site. I'm glad that it is working.
  18. According to the MBox Manual there may need a USB driver for the device. The manual gives a link to the FTDI download page. However, the manual seems to indicate that this is only needed for older version of Windows. When you look in the Windows Device Manager do you see any unidentified USB devices? If so it likely means that Windows was unable to find an already-installed driver for the FTDI chipset on your system. You could install an FTDI driver to see if it works or you could contact MBox for advice, or perhaps wait to see if Guylain has any advice. I hope this helps.
  19. astroman133

    Avi + jpeg

    Sorry, but please be more specific. "The Latest" will mean something different another user with a similar issue who may read this thread a year from now. Please tell us the full version number. Also, have you played the AVI file? Does it seem reasonable?
  20. astroman133

    Avi + jpeg

    I am using BYE 3.1.18 RC1 with my T5i. In Planetary mode I select AVI+JPG and shoot 50 frames at both 1X and 5X zoom factors. I see the AVI file and a folder with all 50 JPG files, although it does take a few seconds before the JPG folder is visible. How is your setup different from mine? Which BYE version and camera are you using?
  21. Andy, Not only will declination need to be found manually at the start of a imaging session, but declination will need to be re-adjusted periodically during an exposure plan. This is because polar misalignment causes the field of view to drift in dec. In any case, you should post questions about autoguiding your SkyGuider via PHD2 with either or both the PHD2 support group and the iOptron SkyGuider support group. BYE's only overlap with autoguiding is providing a means to dither the field of view between exposures. BYE can also be configured to provide AstroTortilla with images for plate solving, however since the SkyGuider cannot slew in declination, it would seem that this cannot be done automatically. Again, a group that supports the SkyGuider may be able to provide advice.
  22. I may be too late, but I apologize if my comments and questions in any way caused the frustration that you vented in the reply that you posted. I did read your post and I felt that it did not completely describe your issue. Nowhere in your post did you indicate that you were attempting apply your version 3.0 license to version 3.1 of BYE. This is a topic that has been discussed numerous times in this forum. The correct steps for how to use your existing license to get a new, no cost license are also available on the Upgrade area of this web site. Still, it seems that a few are not able to find the instructions. From what I read, you were attempting to copy your existing version of BYE onto a new PC and could not get the license to validate. This should have been easily achievable. I then realized that it was possible that you were attempting to apply a very old license to a new version of BYE as part of an upgrade. My comments described how you should proceed if that was your situation. Those of us in the BYE and BYN community who try to help new users on this forum are not professionals in customer service. We are simply users, like yourself, who volunteer our time and expertise to try to help new users to overcome the learning curve with using the application. I am sorry my reply to your question provoked such an angry reply. That was not my goal.
  23. Not sure what you mean by "pro version". BYN versions have multi-part numbers (as in 2.0.11 RC3). BYN licenses are Trial, Classic, and Premium. Versions and licenses are independent since new versions can use your existing license. You can purchase a BYN license and apply it to the pre-release RC3 product. I would imagine that the pre-release will become the release version when 1) the authors have implemented all the new features on their list and 2) that the newly-supported cameras work well. That date may not yet be set.
  24. Sorry, no problem. Usually Guylain replies as to whether he found any issues when reviewing the log file. BTW, the Log History is only a partial log of what BYE is doing. The full log is written to a file that is stored in the BackyardTEMP\Logs folder.
×
×
  • 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