Jump to content

Canada's top-tier Telescopes & Accessories

s3igell

Members
  • Content Count

    1,285
  • Joined

  • Last visited

  • Days Won

    22

s3igell last won the day on April 18

s3igell had the most liked content!

About s3igell

  • Rank
    Nuclear Fusion

Profile Information

  • Gender
    Male
  • Location
    Arid-zona

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Please see the STICKY Post labeled "BackyardEOS camera support grid, is my camera supported?" at the head of this Forum.
  2. That is a very good Saturn image, probably about the best you can expect from a 6" SCT. You can clearly see the Cloud-top Banding, and the Rings show Details including the A & B Rings and the Cassini Division!! Given the limited Aperture and the Central Obstruction, that's Very Good!!
  3. Hi David, While many of us have Motorized Focusers in use with BYE/BYN, we need to remember: The BYE Focuser Control is only intended to be a direct and simple interface to the ASCOM Focuser Object. This means that the Control is truly dependent upon what the ASCOM Driver AND your Equipment Driver provide Drivers are allowed to implement their own interpretations of all the related ASCOM Interfaces - or to not even do so (ie: support Multiple Speeds or Absolute Position) The Developer - Guylain (who will surely provide more of his own input shortly) has repeatedly indicated that his Design Intentions are to keep the BYE Interface as Straightforward as possible and leave most ancillary functions to the various Equipment Providers Don't let this discourage you, as every Vote for a Feature may indeed convince Guylain to make it his Next Feature project.
  4. The Issue would seem to be between Canon's Implementation of the Custom Shooting Modes and Canon's SDK, as BYE doesn't interface directly with the Camera but only with the SDK.
  5. Remember that even though the 7D is an older model than the T7i, the 7D is also in a higher Product Class (Semi-Pro vs Prosumer) that often means better quality Electronics. Or, it can also be simple Environmental Factors such as running the 7D on a Colder Evening than the T7i. Or you spent longer in LiveView on the T7i just before the Imaging Run. (In either case: Warmer Sensor means More Noise)
  6. You can probably benefit by Searching the Forums (BYE and BYN) for references to the other Windows Emulators (Parallels, Wine, etc), for posts by users who succeeded in setting up their systems. As Rick posted above, the usual culprit is the USB Hardware Support configuration of the Emulator. The Windows Environment needs to have full access to the Emulated Hardware.
  7. s3igell

    Nikon 810a

    Yup, with any DSLR it is a balancing act between keeping your Sensor as Cold as possible for Noise Reduction and Warm enough for Proper Operation. Your's must have gotten pretty cold to quit working. I've imaged with my Canon 60D at about -10F on several Cold occasions...
  8. An INDI Driver for NIKON Lenses?? Or a generic INDI Focuser Driver?? Your first step would be to identify which INDI Component and then ask that Developer whether they are using the NIKON SDK or something else. If the INDI Developer has found a "Trick with the SDK", then there might be hope that Guylain can use that same Trick.
  9. This won't be a "Fix", but rather a "Feature Request". It'd be best if you posted to the "Feature Request" forum group.
  10. If you look at Used Canon DSLRs, avoid the T4i and the M series. As always, check for compatibility and supported features on the Supported Cameras page.
  11. OK, while I don't read Chinese, I get the idea that the Video was detailing a method of performing "Long-Exposure Time-lapse Video" by Stacking Individual Frames. This is actually a rather common Activity - usually performed on a Photographer's Tripod and NOT on a GOTO Mount. Most Nightscape Imagers will use Non-Tracking Images, usually adhering to the "Rule of 500" - whereby you limit your Individual Exposures to no more than "500 divided by the Lens Focal Length". So, for a 17-35mm Lens at 17mm one can Expose for about 500/17=30sec. And at 35mm for 500/35=15sec. And given a "Fast" Focal Ratio of f/2.8, one can capture quite Bright Milkyway at those Exposures (and rather bright Light Pollution, too). Give it a try... Note: The idea of using GOTO Tracking and then "Return to Original Position" wouldn't work with a GOTO Mount, anyway. The "Original Position" of ANY Mount is in Absolute Celestial Coordinates, and NOT in Local Geographic Coordinates. So, The Camera would Follow the Milkyway - NOT the Foreground Composition.
  12. Yes, that was understood. Tracking of the Stars and Milkyway is accomplished by allowing the Mount Tracking to continue while taking multiple Long Exposures. Exposures of the Foreground (the "composition" as you put it) are taken with the Tracking turned OFF (as in a standard Photography Tripod). Then, in Post-Processing, the Star Exposures are Stacked and then Merged with the Foreground Composition using an Image Mask.
  13. Regardless whether BYE/BYN can support your proposed routine, that routine is quite different than the usual Tracking Long Exposures. Can you explain why you propose "Close Tracking" and "Goto Original Position"?? Most of us leave Tracking ON across all of the Exposures taken of a specific Target; counting on the capability of the Mount to keep the Imaging Rig correctly pointed to the Target. (And we add AutoGuiding if we need additional Tracking accuracy...) If, during your Long Exposure, there is enough travel in the Tracking that you feel the need to reposition the Mount before starting a second Exposure, then there will surely be Star Trailing in the Images taken. That would indicate problems with your Tracking equipment (Motors, Gearing, Stiction, etc) which should be addressed at the source.
  14. This sounds like a task which can be performed by a combination of a Planetarium program such as Stellarium or SkySafari plus a Plate-Solve program such as AstroTortilla (which BYE/BYN supports).
  15. The time a specific Mount is going to take to successfully Settle is going to be more a function of the characteristics of the Mount itself than any of the settings exposed in BYE. Backlash and Stiction, and the PHD Settings to control those issues; RA-Only as well as Random vs Spiral Dither Settings; and the Physical Environmental elements such as Balance and Seeing Depending on the general Guiding Performance of your Mount, the lower Settle values may be more than you can expect from your Mount. Remember: BYE/BYN only tells PHD When to Dither, How Aggressive to Dither, and How Patient to be about Post-Dither Settling. Dithering, like Guiding, is configured and controlled by PHD and you will find much greater support over on the OpenPHD.org forums.
×
×
  • 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