Jump to content

Canada's top-tier Telescopes & Accessories


Popular Content

Showing content with the highest reputation since 12/21/2014 in Posts

  1. 3 points

    Plate Solvers for BYE

    Yes that would be one place to put it. As for charging for it... nope, nada, ziltch One way I have been able to differentiate myself from other commercial package is my free upgrade path and UI simplicity. I prefer to give free upgrades, including new features, big or small, as part of the free upgrade. My business case is linear... free upgrade = more users = more user generated word of mouth = free marketing = more new net sales. In other words I think free upgrades for new releases generates more revenue in the long by selling to new users rather than up selling new features to exiting and loyal customers. I may be the odd ball here compared to other commercial package where they try to squeeze another $20 or so from their customers with upgrade cost. I prefer to acknowledge my customer's loyalty by saying thank you... here's a free upgrade. I'm not saying I will always follow this path. Up until now I have been able to offer free upgrades and I have no plans to chance this any time soon. Thank you for the offer to pay a bit extra but a plat solving feature, I appreciate the gesture. Regards,
  2. 3 points

    ASCOM 64bit only driver

    I would offer a slight correction to your statement...BYE does not "launch" ASCOM like one program can launch another program. The ASCOM Platform is referenced by and used within BYE. The Windows "bitness" rules are somewhat confusing. Here is a summary: A 64-bit version of Windows can run both 32-bit and 64-bit applications, but a 32-bit version of Windows can only run 32-bit applications. This works because 64-bit versions of Windows include a 32-bit subsystem. There is no 64-bit subsystem for 32-bit versions of Windows. A 32-bit application can only use 32-bit DLLs and a 64-bit application can only use 64-bit DLLs; with one qualification....NET code (applications and libraries) are interpreted. This type of code is built into and distributed as "intermediate language". This code is then converted from intermediate language to machine language when the code is executed. This means that if .NET DLLs are correctly built, they can be loaded into and run from either 32-bit or 64-bit applications. This is accomplished by building them for "Any CPU". The DLLs that make up the ASCOM Platform are built for Any CPU. This allows the ASCOM development team to distribute only a single version of each DLL with each release. There is no such thing as a 32-bit version of ASCOM or a 64-bit version of ASCOM. ASCOM drivers different from the ASCOM Platform. That said, some drivers are distributed with the ASCOM Platform, but most are distributed separately, by equipment vendors or independent driver authors. The bitness of drivers is a function of how the driver author created them. Some drivers are DLLs and some are EXEs. The DLLs load into the memory space of the application that is consuming them. Therefore they must be capable of cooperating with that application's bitness. BYE is a 32-bit application. It must be so because it uses the Canon SDK which is a 32-bit unmanaged (non-.NET) DLL. This works for the ASCOM Platform because it is built for Any CPU and is perfectly happy to work as part of a 32-bit program. ASCOM DLL-based drivers that are 32-bit only will work fine with BYE. ASCOM DLL-based drivers that use .NET and are built for Any CPU will work fine with BYE. Only ASCOM DLL-based drivers that are built only for 64-bit will not work with BYE. That said, if BYE were a 64-bit application, the ASCOM Platform would continue to work well with it and the Sesto Senso 64-bit driver would also work with it, but the 32-bit driver would not work with it. EXE-based ASCOM drivers run as separate processes from ASCOM client programs like BYE. This means that they can have different bitnesses. If, for example, the 64-bit version Sesto Senso driver was designed, built and distributed as an EXE file, BYE would easily be able to interoperate with it. Also, if the Sesto Senso driver were developed from one of the skeleton project templates that are provided by the ASCOM Initiative it could have been built for Any CPU and therefore the same DLL would work on either 32-bit or 64-bit versions of Windows and under 64-bit Windows would work with either 32-bit or 64-bit applications. This would eliminate the need to distribute multiple versions of the driver. Here is a problem with the Sesto Senso driver that you may encounter at some point in the future...What if you need both the 32-bit version of the driver to work with BYE AND the 64-bit version of the driver to work with some other 64-bit application. Unless the two versions of the driver are designed to operate side-by-side, you would have to choose which version is more important to you. This would be inconvenient for you, but addressable by the authors of the driver in a couple of ways. They could either convert the driver to .NET and release it for Any CPU or they could convert the DLL to an EXE and release a 32-bit only version that would work with either a 32-bit or a 64-bit client application. There are two main benefits for a 64-bit version versus a 32-bit version of an application. One is performance and the other is size. A 32-bit application has a 2 GB memory limit that is eliminated for a 64-bit application. However, I would be extremely surprised if a focuser driver needed either the performance or size increase that a 64-bit version provides. I hope this helps.
  3. 3 points

    Another Request to Add FITS Option

    FITS is a "manufactured / generic" Format, designed originally to facilitate Data Interchange from all sorts of Scientific Equipment (much not even Cameras). To convert a Camera's output from RAW (whether CR2 or NEF) to FITS means that you will be dependent on and subject to Guylain's choices of Conversion Parameters. This is usually something which most AP Imagers wish to have sole control over...
  4. 3 points

    Eclipse Experiences

    I viewed the eclipse from Ramkota Hotel parking lot in Casper, Wyoming. There was a huge influx of eclipse chasers into Wyoming in general and Casper in particular for the event. I arrived in Casper a week before the eclipse to attend the annual convention of the Astronomical League (ASTROCON 2017). ASTROCON ran from Wednesday through Saturday and featured a large vendor area with talks and workshops. I had the opportunity to talk with folks from Celestron, Meade, Stellarvue, and Astro-Physics, as well as several others. I attended their Star-B-Que on Friday evening and the Gala Awards Banquet on Saturday evening. I was able to see some old friends and make some new friends throughout the event. As the week wore on, more members of my Arizona club arrived in the Casper area. Several other club members chose sites in Idaho, Oregon, and elsewhere in Wyoming from which to view and image the eclipse. My hotel reserved a viewing area for us in their parking lot and we did some solar viewing on Friday, Saturday, and Sunday before the eclipse. The sun was more active than we had any right to expect, with multiple sunspot groups and several prominences visible. It was a treat for many locals and visitors who happened by. We had several dozen pairs of eclipse glasses to give away, but most folks already had theirs. There was quite an international contingent in Casper for the eclipse. We met people who had traveled from New Zealand, Taiwan, Japan, Hong Kong, South Korea, Canada, Spain, England, Norway, and Italy. I hope that I didn't forget anyone. My niece and her husband, who live in Ohio and work at NASA, were on vacation in Montana and drove down for the event, bringing their new Celestron Nexstar Evolution HD scope. On Monday morning I was outside at 4 AM to set my gear up and get a good polar alignment before sunrise. Gradually, I was joined by the rest of my friends. The hotel hosted a Pancake Breakfast with adult beverages beginning at 6 AM. Tequila Sunrise, anyone? As the sky brightened we saw mostly clear skies with some light clouds off in the distance. These clouds proved to be troublesome as the eclipse progressed. Around 8 AM I was interviewed by the Casper ABC affiliate about the eclipse and my travels to attend the event. That evening I looked for the interview on their web site but was not able to find it. First contact was at 10:22 am MDT. My imaging plan must have been off by a couple of seconds because none of the 5 images that were centered around that time showed any contact, but we were off and running. I took an image every 5% of ingress between 1st and 2nd contact. As ingress progressed we got slowly, but noticeably darker and cooler. We recorded a 19 degree temperature drop between 1st contact and totality. Shadows on the ground beneath some nearby trees began to look odd at the 80% ingress point. When we got to 90% I used LiveView to see how much the sun had drifted. It was close enough that I decided that re-centering was not necessary. Focus also looked good. I also set up a GoPro camera on a tripod in the back of a friend's pickup truck to capture a video of our group during totality. I have some decent images of the Diamond Ring and totality, but they are not processed yet. About a mile from our hotel, up on a hill, there was a crew from Time magazine. They put up a drone to shoot video of the area during totality. I later saw the sped-up video which included our hotel in the frame. During egress, the clouds thickened and I don't have much hope for those images. I have not even looked at some of them yet. Once 4th contact had passed, I tore down my gear. As usual, since I have the most complicated setup, I was the last person to finish tearing down. During Monday evening we heard horror stories of the traffic snarls on I-25 between Casper and Denver, including people who ran out of gas because of the delays and had to push their vehicles off the road. I left Casper on Tuesday morning with 2 long days of travel back to Arizona. I got home and my air conditioner had quit and the grass was knee high. The A/C is now working and about half my yard has been mowed. I will post more, with links to my images, as they become available. I have already been looking at where I might go in Texas for the April 2024 eclipse. I hope the rest of you BYE and BYN users had as enjoyable eclipse event as I did.
  5. 3 points

    Solar Eclipse ?

    Link to the recorded Live Stream. Watch me get mesmerized and forget to take the solar filter off the telescope ...
  6. 2 points

    Saving captured images

    There is also a setting that will save snaps that you take while in frame & focus mode, if you wish to do so, but the default is not to save them.
  7. 2 points

    BYE Pre-release 3.20

    I just finished uploading 3.2.0 RC2 with the ability to acquire RA/DEC from the connected telescope.
  8. 2 points

    Mirror Up

    When doing long exposure AP, the milliseconds of vibration, if there is any vibration, are overwhelmed by the following several minutes of exposure time. This makes mirror up unnecessary for that type of imaging.
  9. 2 points

    ISS Transit

    Guylain, Wanted to say thanks again. I was able to capture a ISS Lunar Transit using Planetary in BYE. Zoomed in nicely and had it running at ~15 fps a few minutes beforehand. My daughter actually saw it on the screen and then I was able to look in the capture folder (I was saving JPGs instead of AVI) where I ended up being a little disappointed when I saw a small black dot cross. Turns out it was only a bird (my daughter told me it was not where she saw it). Only wish we could get RAW but I understand the limitations of the liveview method. Had only one glitch. When first booting up the laptop after set up, BYE asked me to validate my license. Never had done this since many moons ago I was stumped. I panicked after it didn't take my password(s). My daughter even set up a wifi hotspot and I tried to find the password on the website. I finally READ THE DIRECTIONS and typed in my username (DUH) where it let me in. Then it wouldn't connect to the 700D. I shut down. Waited 10s. Restarted BYE and then it connected and we were in business. Didn't keep the logs (I think). Weird behavior but I luckily had 15 minutes to spare. See attached animation.
  10. 2 points

    Licence fault error

    You will also want to use a Powered Hub at the PC-end of this Active Cable (especially if PC is a Laptop - most are rather short on USB Power). If you are also connecting to the Mount and/or the AutoGuider via USB, move the Powered Hub to the Mount-end of this configuration (in order to fully power the AutoGuider Camera). If the AutoGuider Camera is a ZWO, you will need to remember to "Throttle USB Throughput to 40-50%" in that Camera's Control Settings (they are notorious for running "full speed" without buffering for other USB Traffic). Else you should run a 2nd Active Cable all the way back to the Laptop (which necessitates a 2nd USB Hub - or other Guide Camera powering arrangement). Yes, it gets more complicated once you start to look to "Remote" your Imaging Rig...
  11. 2 points

    TheSkyX Configuration for BYN

    Thank you too, Rick and Guylain. It looks like you have to be very fast to be at the head of the que with advice here! Again, I am impressed with the kind assistance and look forward to some basic imaging and learning about BYN tonight. Having a beer already to celebrate! Best, Mike
  12. 2 points

    premium edition

    Scroll to the bottom of this page and click on the "Upgrade Instructions" link for your product (either BackyardEOS or BackyardNIKON) then select the link for instructions on how to upgrade from Classic 3.1 to Premium 3.1.
  13. 2 points
    It seems that people are routinely (at least every month) unable to find the information about which camera models are supported by BYE and BYN and to explain the possible reasons why a particular model is not listed. This causes a bad experience when they assume, without further research, that their camera is supported when in fact it is not, or that they only need a single cable and their camera requires a DSUSB cable for Bulb exposures along with the regular USB cable.. Perhaps the site navigation in the Store could benefit from more prominent placement of the Camera Support Grid for each of the products. It could boldly state that not all camera models are supported by the product and the reasons why. It could also boldly state that some cameras need 2 cables while most need only 1 cable and describe how to read the Grid to determine the cabling requirements. One way to make the support grid more visible is to display it on a page of its own that the user must navigate through to get to the product order page and get the user to agree that they have read and understand the page contents as related to their camera model. If they are unsure of the requirements for their camera they could be directed to the Support area to seek clarification. Another option could display the camera models in a dropdown list, instead of the entire grid, which brings up the support info in a separate panel that the user can read and dismiss.
  14. 2 points
    I just uploaded BYE 3.1.18 RC1 in the pre-release download section. There are few changes in the capture section itself... perhaps the most prominent and useful one is the ability to have a mixed of LIGHT/DARK/FLAT/BIAS image in the same image run. You will be prompted to cover/uncover the scope as required. https://www.otelescope.com/files/category/24-pre-releases/ Regards.
  15. 2 points

    Licence fault error

    Ben, It should not be necessary to uninstall and re-install BYE just to replace a cable. Keep in mind that the authors limit how many times a license can be registered. I assume the reason is to prevent unscrupulous people from sharing their license key with friends. If uninstalling and re-installing BYE causes re-registration then definitely do not uninstall and re-install it for no good reason. I would suggest replacing the cable and try your existing installation of BYE. If it fails to connect or operate correctly then post your symptoms back with this group for advice. The only reason to re-install is if your current software is broken or the installation was incomplete or corrupted. If a new version of BYE is released, you can choose to install it over the old version, without uninstalling the old version, or you could choose to install it in parallel to test the new version while keeping the old version as a fallback.
  16. 2 points

    ASCOM 64bit only driver

    How old is the driver? .NET-based ASCOM drivers can be built for "Any CPU". This means that they will work with either a 32-bit or a 64-bit app. 64-bit only drivers are very rare because most astronomy applications are still 32-bit. BYE must be a 32-bit application, because it uses the Canon SDK which is a 32-bit unmanaged DLL. The following from the Sesto Senso Focuser manual indicates that there is a 32-bit version of their driver. NOTE: SESTO SENSO comes with both 32 and 64 bit version of ASCOM drivers. You have to choose the version based on your Windows operative system and the third party software you want to use. For example, if you have Windows 64 bit we suggest 64 bit versions but some softwares, like MaximDL, request the use of 32 bit version ASCOM driver. If you have problems connecting SESTO SENSO to your third party software, please install the other version of ASCOM driver.
  17. 2 points

    Not Saving Config Settings

    Running in admin mode causes a cascade of other issues. The best solution is to NOT run in admin mode. We need to help you solve your original issue about saving BYE's settings. I suggest 1) upgrade to BYE 3.1.17 and 2) re-install BYE to a different folder. Installing to a different folder has helped others with the same issue.
  18. 2 points

    Modified (cooled) Canon 80D

    Just wanted to share that I took the modified 80D out last night for a trial run. It was on a Hyperstar on a Celestron 14" Edge SCT. I normally run a Lodestar x2 guide camera in a ES 80mm triplet, but didn't do any guiding for this first trial. The 80D performed flawlessly and although the cooler isn't really required yet, it functioned very well also. BYEOS works so well and when I add PHD2, I'll be able to get multiple frames quickly now, without the heat buildup on the camera sensor. As you can see in the upper left, the Orion Neb & Crab were shot at 40 sec, 1600 ISO; the Horsehead for 60 sec @ 1600 ISO.
  19. 2 points
    OT: I hope this was a Spell-Checker Auto-Correct error, as Home ASTROLOGY has surely (hopefully) shrunk in the past few decades of "Enlightenment"... :^)
  20. 2 points
    BYE and BYN have support for several device types (Telescope, Focuser, Filter Wheel), but adding support for ASCOM Observations for reading ambient temperature would be a good feature for many users. You may even find additional ambient values that could be incorporated into the Backyard metadata.
  21. 2 points

    Canon 200D

    EnderBoy, Please create a new thread for your issue. It is unrelated to Ckevin's old post. Creating a new post for each issue makes it easier for future readers to make sense of what issues people are having and how they got fixed. When you create a new thread, please let us know what version of BYE you are using (for example 3.1.16), what license you have (Trial, Classic, or Premium), and the details of the steps to re-create the issue. That said, according to another thread you need to download BYE 3.1.17 RC2 from the Pre-release area to get support for the 200D/SL2. Thanks!
  22. 2 points
    I believe that the amount Guylain pays for web hosting this content increases according to the size of the site. He discourages uploading log files by attaching them to posts. You should delete all the log files and create a new file that contains entries that were written when you had your issue with TSX and BYN. Then take just that file, zip it up, and send it to Guylain privately. See this post for instructions. It is also pinned near the top of the How To's Forum.
  23. 2 points
    I cannot duplicate it on my T5i. Same EXIF parameter, translated to degF shows up in my Camera Information Center after the image is downloaded and stored. By chance to you have the "Skip READ Exif data" option checked on the Advanced Settings screen? If so, BYE will not read the data and so cannot display the value. BTW, I typically leave both the Skip READ and Skip WRITE options unchecked.
  24. 2 points

    not working

    So, I am assuming that you have a valid license. You need to log onto the OTelescope web site using the same username as you used to get/purchase your license. Go to your My Purchases area and find the applicable license. Swipe across the license key and copy it to the clipboard. Note that the identifier is the case-sensitive username. Install BYN and launch it. Click on the padlock at the upper right and then select Edit License. Paste in the license key and enter your O'Telescope username (NOT your email address) as the identifier. You should be good to go. astroman133
  25. 2 points

    BYE not capturing images with T5i

    If BYE is not creating log files or downloading images, then it could be that Windows Update caused a change to file permissions that is preventing BYE from saving images or creating logs. This has happened to other BYE users with Windows 10 computers. You could try removing BYE and re-installing it to a new folder.
  26. 2 points

    Delay after image capture

    The behavior that you are reporting could be due to having Long Exposure Noise Reduction (LENR) enabled in the camera. Turn it off and the problem should go away.
  27. 2 points

    Installing on a new laptop

    Follow the link in the previous post to the BYE Product Page. Click on the Upgrade tab below the 3 large license buttons. Find the instructions that are appropriate for the version of BYE that you are upgrading from and click on that link to see the upgrade details. Follow the displayed steps to purchase a new license. Note if you are upgrading from 3.0 Classic to 3.1 Classic or 3.0 Premium to 3.1 Premium the cost is $0, but you still need to go through the purchase process to get a new license. That license will be maintained on the OTelescope web site, so you no longer have to safeguard the license yourself. It is always available on this site in the My Purchases area after you have logged on. I hope this makes sense.
  28. 2 points
    I have to apologize. I just retested it, and BYN was not responsible for changing the RAW size. It was either another piece of software or my stupidity. MP
  29. 2 points
    Hi Guylain. On a future release, is there a possibility of making Telescope as default window rather than Filterwheel on start-up? For those of us not using a Filterwheel (which I suspect would be the majority as we are mostly using OSC cameras) it would be a convenience. Cheers, Gord
  30. 2 points
    Alexey, You should create a post in the Feature Suggestion Box forum to suggest a change in behavior to preserve the values in a capture plan row when the exposure count is set to 0. Your use case seems valid to me. I have the Premium license and always save my capture plan after a change as a work around for exactly that situation.
  31. 2 points

    BYN with INDI Server

    The INDI environment has expanded to include Windows, so being a .NET Program does not necessarily set a barrier for BYE/BYN. However, BYE/BYN neither provides an ASCOM Output Interface such as would allow the Image Data to be streamed to an INDI Device or to allow BYE to be Controlled Remotely via an INDI Interface. Nor does BYE/BYN have the ability to manage an ASCOM Camera such as could be augmented with INDI support to allow BYE to be that Remote Controller. These have simply not been the uses which Guylain has designed BYE/BYN to fill. Instead, users have had great success using their choice of Remote Control Software to manage BYE running at a Mount-side PC (or in some cases found USB2-to-Ethernet Extension Cables to move the BYE PC into the House).
  32. 2 points
    A 50mm Guider (usually 160mm Focal Length) is far too little Focal Length for a 2000mm Imaging Focal Length: the Rule-of-Thumb is the Guiding Pixel Resolution needs to be at least 1:5 the Imaging Resolution. You were attempting more like 1:20 Resolution-Ratio, and would need to mount an 80mm f/8 Guide Scope or else use OAG (which also has its challenges). Mounting a C11 with all the gear (Camera, Guider, Losmandy Dovetail) will weigh near the top-end of what a well-maintained NEQ6 can readily handle, but you likely were fighting other Issues than Weight. Unless your C11 is actually an EdgeHD11, you lack the Mirror Locks which would address Focus Sag and Collimation concerns. That is going to be your biggest nemesis for successful Guiding of your C11. The solution is to move to an OAG Guiding Rig (Off-Axis Guider - prism-based Pick-off rig which mounts the Guide Camera perpendicular to the Optics train behind the Focuser, where it performs Guiding at a point AFTER Focuser/Mirror Sag and Collimation occur). Sorry, but if you experience noticeable Drift, then your PA is at best "nominal". PoleMaster is only spec'd to get one "an accuracy of up to 30 arc seconds" (per qhyccd.com) - an accuracy that you can easily exceed by either All-Star Polar Align or Drift Align routines. (And 30 arcsec accuracy is exacerbated by the long 2000mm Focal Length. Unfortunately, Focal Length has it's drawbacks...) You are correct... Long Focal Length AND Slow Focal Ratio (f/-ratio) add up to making a C11 a Challenge. You mention "dropping to 700mm" - which will totally change your Experience... But, whichever Scope (and combo of gear), keep at it... AP Imaging is Doable and Rewarding.
  33. 2 points
    If you are using a 50mm finder to try to guide a 2800mm imaging scope, that could be part of your problem. You might find that your guiding would be improved if you used a guide scope that has a longer focal length, say around 400mm. Switching your imaging scope to a shorter focal length refractor will make a world of difference. You may even be able to guide through the finder. I believe that you can use the PHD History graph to how far you are dithering.
  34. 2 points
    the 2 camera with dithering works just fine....remember that the Master camera will control all the settings on the slave camera so you will have identical settings in terms of exposure, f stop, iso etc. Even if you set the slave camera with different settings they will default to the Master.
  35. 2 points

    Remote laptop

    No additional license is necessary. You can install and use BYE on multiple computers, just only on one at a time. This is in your End User License Agreement. So just install the same license on your remote laptop.
  36. 2 points
    First, you should upgrade your version of BYE (3.1.1, per your post) to the latest release (3.1.16). There is no sense trying to troubleshoot software that is 15 releases out of date. Have you read the section of the BYE user manual that describes how to configure and test the serial cable? What user manual, you say? Click on the ? icon at the upper right of the main window to launch it. The serial cable instructions are not extensive, but the process is not too involved, especially if you are using a cable from Shoestring Astronomy. The cable vendor should also provide software to allow you to test the cable outside of BYE. You should use this software to ensure that the cable is functioning correctly, before attempting to connect with BYE. If the vendor's software will not operate the cable to open and close the shutter, then you should contact the cable vendor, not this group. Do not assume that it is plug-and-go, because it likely is not.
  37. 2 points

    5x mode problems in 3.1.16

    Sorry, I am not able to duplicate your issue. 5X zoom for me with BYE 3.1.16 and my old EOS Rebel XS. It works fine for me. However, others have had LiveView issues with 5X zoom because of the default setting of LiveView autofocus mode. You should find this setting in the camera's menus and try a different setting. I looked for the old emails that solved this issue, but could not find them. If memory serves me, you need to change from "Face+Tracking" to a different setting. Sorry that I could not be more helpful.
  38. 2 points
    I believe I have finally came across the solution. In this instance it is two fold. In my D810 I had "Rotate Tall" turned off. It turns out this is only for display. Another setting "Auto Rotation" was turned on and as the telescope tracked throughout the night the camera was interpreting even a slight shift as a rotation. The second problem was occurring in PixInSight, as suggested by Ron. When trying to stack images PixInSight was rotating again some photos and not others. Again, the solution to this problem came from Ron in the form of telling PixInSight to ignore rotation information in the RAW file. Thanks all for your help.
  39. 2 points

    BYEOS and Astro Tortilla

    Astroman gave you most the mechanics of how AT works. But to answer your question: "How do you use AT to successfully Point to M33?" Find an existing Image of M33 - either from a past Imaging Session or from the Web In AT, select Tools/Goto Image - select that Image Let AT Slew and then Image/Solve/Repeat until it has moved the Scope into the Position of that Image
  40. 2 points

    ATIK camera version?

    I would have thought that you would have an entire dogsled team by now! <BG>
  41. 2 points

    Eclipse Experiences

    I started my planning about one year ago, and included an eclipse day in the northern Rockies, followed by a few days of fly fishing. After some research on locations, weather patterns, access, and some conversations with a few fishing friends I settled on Rexburg ID for the eclipse and a four day fishing tour with Mile Lawson's angler's shop in Island Park ID, about 45 miles north of Rexburg. Knowing what lodging would soon be a problem we booked a week (Sunday 8/20 to Saturday 8/28) at the Elk Creek Lodge, also in island Park last December. We left our home base in Albuquerque on Friday 8/18 and reached Rexburg on 8/20 in the afternoon. A few weeks before I did a more detailed review of the area and discovered a little-known wildlife refuge known as the Cartier Slough, located about 5 miles west of Rexburg. We recce'd the area on Sunday and found the place essentially deserted, with miles of quite passable dirt roads through the refuge and the surrounding BLM public lands. Driving down south from island Park on Monday morning traffic on US 20 was surprisingly light, and we set up by about 0800 local. The weather was excellent, eith only a few clouds around the horizon and little to no wind. Along the one mile of the road from the pavement to our location there were only 5 other observers. I used local coordinates and a compass to rough align my Celestron CGEM II equatorial mount, and attached my Canon 6D with a Canon F2.8/200mm lens with a solar filter. After booting up the Backyard EOS 3.1.14 I used the sun as a reference and fine-tuned the alignment. My pre-total program was one sub every 180 seconds at 1/2000, F8 and ISO 400, and for totality is sequenced 1/2000, 1/1000, 1/250, 1/60, 1/30, 1/15, 1/8, 1/4 and 1 second, all at F8 and ISO 400. I was lucky to get 8 of these sequences, and am now in the midst of processing the RAWs. Here is a preliminary version of the last 1/4 shot, showing a beautiful diamond ring.
  42. 2 points

    Eclipse Experiences

    We started our Eclipse Experience by meeting up with friends in Heber Springs, Ar. and stayed at the Stoneflower Fay Jones Cottage on Eden Isle, Greers Ferry Lake. Bats in the loft ran us to a motel after the first night. Next we made our way to Belle, Mo. where we met up with son and daughter-in-law at a Lakeside French Chateau on 25 acres overlooking some amazing Ozark scenery to the northwest all downhill. I was hoping to view the shadow onrush. The video does not show it. The weather prospects did not looks good early Monday morning and we looked at moving to near Carbondale. Vote was to stay put. The nasty storms and clouds to our west and northwest appeared to be moving northeast and would most likely skirt away from us. That's what happened. I was unable to acquire the right cable in time to use BYN and had to use the camera bracket & interval timer to get eclipse images. First timer errors caused focus issues and not being set on the right mid exposure to get what the camera was capable of doing itself. I did capture an amazing audio recording of all six of us reacting to the beginning of totality and the full experience. The images are with a 300mm Nikkor at f/8 near start, mid and end of totality. all automated by camera. Time of Exposure in U.T. 1113 18:14:15 1245 18:15:27 1325 18:16:40 I watched the full total with 7x35 binoculars. Tuesday morning the weather turned simply awesome. Clear and 53 degrees with fog hanging over the Gasconade River. A beautiful trip in so many ways Kenneth Drake, Willis, Texas
  43. 2 points

    Eclipse Experiences

    I went down to my cousin's in the Smokey Mountains of southwest NC. Forecast the week prior was looking spotty with 50-50 shot of clouds and rain. Didn't matter since I was going anyway to visit my 95-year old grandmother before trekking north on Tuesday to drop off my oldest for her freshman year at Va Tech! Leading up to the weekend, the forecast improved to a 20% chance of clouds/rain. My hopes were high! Set up my camera piggybacked on my telescope. Instead of BYE (Sorry, Guylain) I ran a Magic Lantern script from another user so I couold run automatically without having to worry about the equipment - a definite plus for the experience. I also had my webcam set up on my PST for the partials. Had the darnedest time getting it to align in a new location the night before. Next morning finished my setup and was tracking the sun all morning. Then, the clouds started rolling in. Got many shots of the pre and post partials. Totality was nearly a washout and I assumed I got nothing. Was my first TSE so I wasn't really worried since I had a great time. Loved hearing the crickets chirping and the birds going to roost. A truly neat experience. Made it totally worth running the camera on automatic with the script. Left afterwards and a 4.5 hour drive turned into 6 hours with the tourist traffic leaving SC and heading north then mixed in with the TN traffic heading north. After college move in the next morning, the drive home was not better with a 4.5 hr drive turning into 6.5 hr due to a bad accident. Once I finally got back home, I was able to view the images stored on the SD Card. Amazingly, I did get some of the totality and if I enhance some of my shots, I even got the diamond ring and Baily's Beads. Now I am processing the videos from the webcam to see if I can see additional details through the Ha filter.
  44. 2 points
    DH, Any Luck? I was able to get my PST couple with my T3 using a basic 2xBarlow. I think I had to direct screw it into the Canon t-adapter to shorten up the focal length but I did get some decent images (see attached). This was my first attempt back in February. Aaron
  45. 2 points

    D610 Problems

    I am sure that the issue matters to Guylain. It is a matter of priority, in advance of the eclipse. Since your issue has a workaround, it would be a lower priority than an issue where a feature is broken with no workaround.
  46. 2 points

    Solar Eclipse

    I read the same advice about using a serial cable to speed up the lag between exposures. After some experimentation I decided to ignore it. I tested with my T5i and found that I got acceptable performance without the serial cable, especially when saving to the camera's memory card. My lag without the serial cable is less than 2 seconds. That allows me to capture everything that I want, especially just before, during, and after totality. Based on my performance I decided to forego the purchase of a serial cable that would likely only be used for the eclipse. The serial cable is primarily for older cameras that do not support control of BULB exposures via USB. I do not know whether it is possible to configure BYE to use the serial cable for short exposures. That will need comment by Guylain or someone else who is using it in that way. You may also be able to test by configuring BYE to use the DSUSB cable; set BYE up to take short exposures; unplug the serial cable from the camera and start the capture plan. If the plan fails it is trying to use the serial cable. If it succeeds then it is sending the take picture command via the regular USB cable. There is another issue with variability in the actual exposure duration because the computer is multi-tasking. Controlling short exposures in the camera does not suffer that variability which would be more important for short exposures. My exposure plan uses a range of exposures from 1/4000th to 2 seconds. I did not want to try to have the PC control those very short exposures.
  47. 2 points

    zoom box 5x not centered

    You need to upgrade to the latest version of BYE. You are seeing an old bug that was fixed several months ago.
  48. 2 points
    Forget what I said about the setting dialog, I made it a lot more simpler and more coherent with the load/save capture plans. ... and note the Suspend=True on seq #3 Type=LIGHT SaveTo=PC Mirror=0 Target=Q1 Filter= Delay=0 TvValues=BULB AvValues= IsoValues=100|400|800|1600 Seq=1|Exposures=1|Tv=BULB|Duration=1|Iso=1600 Seq=2|Exposures=1|Tv=BULB|Duration=1|Iso=1600 Seq=3|Exposures=1|Tv=BULB|Duration=1|Iso=1600|Suspend=True Seq=4|Exposures=1|Tv=BULB|Duration=1|Iso=1600 This should do the trick And the next logical enhancement for this feature (not now but in the future) would be to move the Image type down into the sequencer and allow a mix of LIGHTS/DARKS/FLATS and force a suspend in between those items to allow the user to put the cap on for DARKS of the light source for FLATS. Regards,
  49. 2 points
    You can enter filter names, separated by spaces, into the Filter List on the Setup screen.
  50. 2 points
    Windows XP, BYEOS, Canon 450D XSi, ED127ES, .7 reducer, various post-processing programs -- thanks, Guylain!
  • 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