Jump to content

Canada's top-tier Telescopes & Accessories

astroman133

Members
  • Content Count

    3,311
  • Joined

  • Days Won

    117

Everything posted by astroman133

  1. BYN Beta and BYE Premium versions can control correctly installed ASCOM-compliant focusers (as well as mounts and filter wheels. Your question asked specifically about USB-connected focusers. That depends on the driver for the device. If the driver supports connection by USB, then the answer is Yes! You need to have the ASCOM Platform installed (preferably the latest release), along with the driver and any additional software that is required by the driver. You can test BYN with the ASCOM Simulator Focuser Driver. BYN and ASCOM won't know the difference. And you can watch the changes that BYN is making by examining the focuser position value in the simulator's popup window.
  2. Your can download the beta from the link in the oldest message in this topic.
  3. In addition to the DSUSB bulb control cable, you also need a USB cable to connect between the PC and the camera.
  4. The change from RAW to RAW+JPG is made because of Settings in BYE. In addition to RAW+JPG there are 3 other settings: RAW, JPG, and In-camera. I hope this helps.
  5. If you connect your camera to the PC and Windows does not recognize it, this is NOT a BYN problem. It is a Windows Plug-and-Play problem. It has nothing to do with BYN, so un-installing BYN and deleting the remaining BYN files and folders will have no effect. You may be able to resolve the problem by finding and deleting the Windows driver for the Nikon camera, but uninstalling and re-installing BYN will not fix an issue with Windows not recognizing and loading the camera driver. However, before deleting anything, I would try re-booting the PC and re-connecting the camera.
  6. Jim, First, there is no "release" yet. There is beta testing of the changes that may be in the next release. While I have not see a list of new features I do not believe that there is any major new functionality intended for version 3.1. There are several "behind the scenes" changes to the way images are handled, however. These are geared to improve usability and performance, and have proven challenging to get right for all cameras and use cases. There are also a few textual changes in labels on the screens, and a few bug fixes. It also uses a newer version of the Canon SDK. This usually means support for newer cameras, but I have not seen anything definitive. There is also an updated user manual. As the release is finalized, it would be typical to see a change log with new fixes and features.
  7. Yes, I am sure. Here is a screenshot. The other RC versions were uninstalled, and RC04 was installed in a clean directory. The same issue does not occur with 3.0.3.
  8. I tried to re-create Ron's issue with BYE v3.1 RC04 and my T5i, but was not able to. I was able to use a mirror lockup delay along with the in-camera long-exposure noise reduction enabled and the in-camera dark was apparently taken and applied. For example, with a 10-second Mirror Lockup delay and a 30-second Bulb exposure it took abut 75 seconds from the start until I saw the image. The mirror lockup, shutter open and shutter close occurred at the correct times. However, when shooting RAW, the displayed image has the same purplish cast as previously reported with RC03. This does not happen when shooting JPG, or in Frame & Focus. Any way for me to troubleshoot this further? Also, I noticed that BYE did not automatically recognize that I had attached a lens while I was already connected. I had to disconnect and reconnect. This may be by design, but I thought that I would mention it. Thanks!
  9. OK, now I get it. When you said that it also occurred for exposures shorter than 30 seconds, I did not realize that you were still using Bulb, since it is typically used only for longer exposures. Guylain is often away with family on the weekends. I am sure that he will respond soon.
  10. OK, so what you are saying is that with mirror lockup enabled, the automatic dark frame is not taken. The conventional wisdom for astrophotography is to turn off High ISO noise reduction because it changes the raw data in ways that you cannot control, and was not meant for astrophotography. The thinking is that you can be a better judge of how to reduce the noise in your images, after you have increased the SNR as much as possible by stacking the raw subs. Long exposure noise reduction (LENR) may help reduce noise in raw images, but it cuts your productivity in half. You will get better results if you take your own darks separately and apply them during image calibration. People may be able to re-produce the behavior that you are reporting, but it probably affects only a very small percentage of users because most people turn off the in-camera noise reduction features. Finally, for long exposures of deep sky objects, whatever vibration may be caused when the mirror flips up is not noticeable in your images because the vibration is very short lived compared to the entire exposure. Conventional wisdom here is to turn off mirror lockup for long bulb exposures. That said, the behavior that you are reporting may not be what Guyain intends and may be something that he can change.
  11. I am confused by your post. What do you mean by "noise reduction is turned on". Do you mean the in-camera noise reduction? Long exposure noise reduction or high ISO noise reduction? Which one? What do you mean by "shutter delay"? Do you mean the Delay control in BYE's Capture Plan Center? That only puts a one-time delay at the start of the capture plan. It does not cause a pause between exposures and it is not supposed to. What do you mean when you say "When I set the shutter to 30 sec (TV) the process is completed as expected"? This is vague because we don't know what you expect to happen. If you turn on Long Exposure Noise Reduction in the camera's menu, the camera will take a dark exposure after each light exposure. This should cause a 30 second exposure to take a bit over a minute to download to the PC from the time the shutter opened at the start of the exposure. This behavior is controlled by the camera, not BYE. BYE starts the exposure, in the case of Bulb, stops the exposure, and waits for notification that the image is ready for download. Please clarify your issue.
  12. As of now, Sept 5th, only beta versions have been released. I believe that the latest beta version is good for a few more weeks.
  13. Look at the topmost, pinned topics in the BackyareNIKON Pre-Release Forum. There is history about Steve's cable, including a photo of what it looks like and how to contact him off-group.
  14. In addition to DSUSB Bulb Control cable, you also need a regular USB cable.
  15. astroman133

    Bulb

    Chris, How do you have your D300 cabled to your PC? USB cable? USB cable & DSUSB Bulb Control cable?
  16. Would the log file show what items are in the f/stop descriptor list?
  17. Mark, I re-read your post and saw that I mis-understood your issue. I think that you have 2 separate problems. The issue with BYE is: Root element is missing. (C:\Program Files (x86)\BackyardEOSv3\BinaryRivers.BackyardEOS.Start.Camera1.exe.user.config) This can be fixed by un-installing BYE, and deleting the folder and the corrupted config file. Then re-installing BYE to a different folder. You also have another issue with a bad sector. From your post, you only found this after running CHKDSK. I believe that this is un-related to your issue with BYE. The file \Windows\winsxs\X86_MI~3.414\mfc90u.dll needs to be repaired and the failed cluster marked as bad. Even so, the data in that cluster may not be recoverable and a repair/install of Windows may need to be done to replace that file after the repair as been performed. Sorry for my confusion.
  18. Mark, When you un-install BYE, it leaves a few configuration files behind. I believe that it is one of those configuration files that is/was in the bad cluster. I would imagine that if you re-install BYE to that same directory it will try to re-use that same (bad) file. This gives you the busted install. If you want to continue to use the drive, you need to scan the disk and fix/repair the bad area(s). Essentially, the repair process marks the area(s) as bad so it/they won't be re-used. There may be no sense in trying to re-install BYE if you can't get a clean scan of the hard drive, since if the failing sectors cannot be marked as bad, they will eventually be re-used by the O/S for some other file. A commercial tool may do a better job with the disk repair than what comes with Windows. I have no recommendation. Once the disk scan shows no errors, you need to un-install BYE and delete the directory with the remaining config files. Finally re-install BYE, to a different directory from where the original was installed. If your disk really clean and error-free, then you should be back in business.
  19. Is is possible to use BYN's flexible file naming convention to mimic the file names of images that are saved to the camera?
  20. I just downloaded Backyard Nikon Beta 2e and it installed and started just fine. Are you installing the 2e version to a clean directory (not over a previous install)?
  21. It seems that you hard drive is flaky. Did you try CHKDSK /f to fix the error(s). If you continue to get disk errors you may want to consider replacing the drive before it totally dies. I would also recommend backing up your data files and making a list of installed applications, and any licensing information that would need to be re-installed on a new drive ASAP.
  22. John, There are 2 possible temperatures that can be displayed by BYE: ambient temperature and internal "sensor" temperature. The ambient temperature comes from the source defined by the Weather Provider section of the Settings page. The "sensor" temperature is read from the EXIF data in downloaded images. I will assume that you are not seeing the "sensor" temperature. The reason that I put the word sensor in quotes is that the temperature is measured by electronics that are internal to the camera, but not necessarily at or near the sensor. Look on the Advanced Settings page and make sure that the "Skip READ Exif data" setting is not checked. You also need to select to download and store your images on the PC. Those two settings should allow BYE to read the "sensor" temperature.
  23. astroman133

    BYE 3.0.3 Docs

    Unk, In case you missed Guylain's post. The PDF manual is included with the BYE installation. Since that is a free download, so is the manual.
  24. BYE 2.0.7 is very old. The upgrade to 3.0 Classic is free. I believe that the timestamp in the file name is created from the time that the downloaded image is written to disk on your PC. It is not directly related to the time that the shutter was opened.
  25. BackyardEOS and BackyardNikon are camera capture programs that are built with lots of features that are particularly useful for astrophotography. It supports a 3rd party interface where another application can request BYE/BYN to take a snapshot, save it to disk, and pass the file path for the image back to the requesting app. None of this is particularly useful for autoguiding, either solar or stellar. Sorry!
×
×
  • 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