Jump to content

Canada's top-tier Telescopes & Accessories

astroman133

Members
  • Content Count

    3,326
  • Joined

  • Days Won

    118

Everything posted by astroman133

  1. Brian, BYE uses the Canon SDK which does not completely support using WiFi for camera control. However, some people have been able to connect BYE and the Canon SDK with their camera via WiFi after pairing the two devices using the EOS Utility or some other application. Apparently Canon does not provide information to 3rd party developers about how to accomplish this. You may find useful information about how to wirelessly connect a camera to BYE in the archives of this site. If you are using the USB connection, WiFi must be disabled by you via the cameras menus. I will say that a wired USB connection will be faster and more reliable than the wireless connection. The SDK does not tolerate even a momentary connection loss. This loss can cause BYE to hang if it has called an SDK method that never returns. The only way to recover is to kill the BYE process via the task manager and restart.
  2. Did you select the Pegasus Powerbox from the Weather Provider dropdown on the Settings dialog?
  3. I am not sure where you read that Backyard EOS can control a PegasusAstro Powerbox. BYE can control Canon cameras via the Canon SDK and with a Premium license it can control a telescope, a focuser, and/or a filter wheel via ASCOM. BYE is primarily a camera control program, not an observatory automation program like SGP. BYE does not currently support control of switch devices like the Powerbox. The Pegasus Powerbox is on the list of supported weather providers. If there are multiple versions of the Powerbox they should be supported as long as they all use the same API. I do not know how BYE communicates with the PPB. Sorry.
  4. astroman133

    TWO CAMERAS

    Yes, that is how it is designed.
  5. astroman133

    TWO CAMERAS

    BYE can do this if you synchronize the two instances. This is discussed in detail in the user manual. You should know that this only makes sense if both instances of BYE are taking synchronized exposures with the same exposure duration, f/stop, etc. In this case the master instance sends the take picture command to the slave instance(s). So it will only work for you if the exposure parameters will work for both scope/camera combinations. I hope that this helps.
  6. astroman133

    TWO CAMERAS

    So you want to control 2 telescopes/mounts, 2 focusers, and 2 cameras from the same PC? The good news is that BYE is designed to be able to run 2 instances, called Camera 1 and Camera2, on the same PC. The BYE User Manual describes how to run multiple instances of BYE and if required how to slave one instance to the other. This may not be true with control of 2 mounts and 2 focusers or running 2 instances of PHD2 on the same PC. You would need to check with the driver author for the telescopes and focusers regarding whether the driver supports multiple concurrent instances. You would also need to check with PHD2 support about running 2 instances of that application. You should also be aware that if you find that you need a second PC to run the second setup that running BYE in 2 computers at the same time requires a second license. You should read the End User License Agreement (EULA) in the User Manual for confirmation.
  7. <When I am in M, BYE does not appear to be able to set the exposure time to Bulb if the camera is not already set to B in the shutter speed settings, only to the various pre-set times that the camera times internally. > Are you saying that BULB is not available in the Shutter dropdown in BYE's Capture Plan Center on the Imaging screen? If so, then does deleting the cache data on the Advanced Settings screen and restarting BYE with the camera in Manual mode fix it? I am not sure, but perhaps an old bug has crept back into the program.
  8. A better question may be..,What plate solving tools can use BYE. AstroTortilla is pretty much a dead product, at this point.
  9. Please post your request in the Feature Suggestion Box forum. That said, Guylain has said that implementing autofocus functionality is not a high priority (I am paraphrasing him). Some time ago I had asked for the capability to pause an imaging plan to allow switching to Frame and Focus for manual focus adjustment and then returning to Imaging and resuming the imaging plan. To me this is a significant improvement that still supports frequent manual re-focusing. It s valuable for me because where I live we experience 40-50 degree temperature drops during the course of a night.
  10. The Celestron focuser connects through the mount so I would expect that Windows would only see a single COM port created. In your screenshot of the Focuser driver settings, you did not select a COM port.
  11. You should install the latest Celestron ASCOM driver since it supports both the telescope and optionally the focuser. If you want to, you could ask Celestron tech support about what you are trying to do. The Celestron driver that can be downloaded from the ASCOM web site is written by an independent developer and is implemented as a local server so the same executable can be used with both 32-bit and 64-bit applications.
  12. No, you cannot change the default capture plan, but with the Trial or Premium license you can save and re-load capture plans. How to use this feature is discussed in the User Manual. Launch BYE and click on the question mark icon to launch the manual.
  13. What if you temporarily disable your anti-virus software?
  14. This issue may be due to a setting in the camera. If you have Auto Focus set to Face+Tracking, you need to change it to one of the other settings...I would suggest selecting Manual Focus.
  15. Thanks for letting us know.
  16. Please tell us which version of BYE (all three numbers, please) you are using and which model of camera you have the issue with.
  17. It has been several weeks since you started this thread so I went back to read your original post. You said 1. Light / Dark / Flats / Bias : · save to Camera: KO · save to PC: OK · save to PC+Camera: camera OK, PC not OK (picture is in download folder of BackyardTEMP folder). 2. Preview: ok I take this to mean that Save To Camera works as expected and Save to PC works as expected, but when you choose Save To PC+Camera there is a probem. Is it still the case that BYN behaves as expected until you attempt to save to both the PC and the camera? And that the image is saved correctly to the camera and that it is downloaded to the PC, but is only in the BackyardTEMP folder, but not in the Download folder? If so, it would seem that this issue is caused by something in Windows or Backyard Nikon. I say this because if the image is in the BackyardTEMP folder then BYN has controlled the camera to capture the image and has downloaded the image to the PC, but has had an issue when processing, renaming, and moving the image to the Download folder. The BYN log file should provide insight regarding the problem.
  18. Guylain, Happy Holidays. Below is what I see. Notice Browser notifications are disabled, but I still see the box at the bottom of the window. The confirmation is gray, not red. Thanks, Rick
  19. Despite disabling Notifications in the web site account settings I still get a prompt from the Edge browser telling me to turn on Notifications. This is an annoyance. Please allow me to completely disable Notifications and eliminate that prompt.
  20. My impression is also USB related. According to Nikon, the only supported configuration is for the camera to be plugged directly to the PC, not even going through a USB Hub. Connecting to the RPi and using VirtualHere could be affecting the communication timing such that the SDK occasionally loses its connection to the camera. This can cause the Nikon SDK to hang which can cause BYN to hang or crash. Canon has a similar issue with their SDK although they do not have any guidance that prevents connection through a hub.
  21. So you need to log on with the username that matches your identifier to access your license from the account profile. This is where you need to come to upgrade your existing license, should that ever be necessary.
  22. Brendan, Thanks for letting us know that your issue is resolved. The Canon210 version of the SDK is for DIGIC II cameras that are not supported by the current Canon SDK. However it is possible that version 2.10 of the SDK does/did support the 1000D which was released in 2008. It may have a problem today with your camera if the camera's firmware has been updated. The 1000D is supported by the current version of the SDK this is the version that you should use since it would support later firmware versions. I am glad that you are working.
  23. BYE uses the same mechanism as the Canon EOS Utility to communicate with the camera. That is, the Canon EOS SDK. In 99+% of the time, if the EOS Utility is able to communicate with the camera then so will BYE. There are 3 notable exceptions to this. 1) BYE checks to see if the Canon EOS Utility is running. If so, then BYE's default behavior is to fail to connect since both programs cannot be connected at the same time. The default behavior of the EOS Utility is to automatically connect with the camera when you plug the camera USB cable into the PC's USB port and power on the camera. This will prevent BYE from trying to connect. The fix is to find the menu option in the EOS Utility and change it so that it is not launched automatically when Windows sees the camera. If this doesn't work then you will need to uninstall the EOS Utility. 2) BYE offers an option to "Select your camera driver" when you click on the connect button. For the 1000D (Rebel XSi) you need to select the Canon driver option. This is for DIGIC III and later cameras. The Canon210 option is for DIGIC II cameras that are no longer supported by the current Canon SDK. If you select the Canon210 option then BYE will not connect since version 2.10 of the Canon SDK predates the release of the 1000D. 3) For cameras that support WiFi tethering, this option must be disabled in the camera since the Canon SDK does not support a WiFi connection and enabling WiFi automatically disables the USB port. This is not an option with the 1000D since it predates Canon's support for WiFi connections so it cannot be causing your issue. I would also say that you should only connect your astronomy instruments directly to the PC or indirectly through a powered hub. A typical USB port can provide 500 milliamps to power any connected devices. With an unpowered hub that 500 milliamps is shared by all devices that are connected to the hub. Depending on the power requirements of the connected devices, 500 ma may be insufficient. With a powered hub, the hub usually provides 500 ma for each device. You should also not extend the length of your USB cabling beyond 5 meters without using an Active Extension cable. The Active Extension cable is essentially a signal booster that allows transmission over a longer distance (the length of the active extension cable). In any case you should keep your cables as short as you can.
  24. astroman133

    EOS -Ra

    BYE checks if the EOS Utility is running and if so it will not try to connect. I don't even have the EOS Utility installed on my PC so my instructions will be necessarily vague. I believe that there are configuration options in the EOS Utility menus that will allow you to disable starting the EOS Utility automatically when you plug the camera into the USB port. There is also an configuration setting in BYE to skip checking for the EOS Utility. Skipping this check is OK as long as the EOS Utility is running, but not connected to the camera. If you cannot figure that out then I would suggest uninstalling the EOS Utility. This would typically be done through the Programs & Features applet in the Control Panel. I hope this helps.
×
×
  • 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