Jump to content

Canada's top-tier Telescopes & Accessories

astroman133

Members
  • Content Count

    3,854
  • Joined

  • Days Won

    144

Posts posted by astroman133


  1. The short answer is No.

    Cameras do not support the ability to download a capture sequence from a PC and then operate autonomously. BYE is designed to control the camera exposure by exposure. There is tremendous advantage to being able see the captured images and to have the the program available to re-focus as necessary.

    To see the differences between the Premium and Classic versions, click on the Compare Editions link in the page footer.


  2. Try downloading the installer again.

    The authors recognize that the weather and personal schedules don't always cooperate to give you enough time to work with BYE during the trial period and have been very generous about providing a second trial upon request.

    Also understand that you can do quite a bit of testing with a laptop with BYE and your camera at the kitchen table.


  3. I understand about classic Windows privileges, but this is the first time since I started using BYE that I have had a settings issue. Also, I have Full Control of the settings subfolder, just as I have for previous versions.

    Again, this did not happen with 3.2.0, installed to a different folder, but with the same privileges (Full Control) of the Virtual Store subfolder. To me, it seems to be something else!


  4. There could be a problem with the J2000 to JNow coordinate transforms in the ASCOM Platform version 6.5. This is fixed in SP1 which has not yet been released.

    The symptoms are that if you perform multiple transformations with the same Transform instance, the calculated values are not recalculated so you get the same transformed coordinates as were calculated from the first transformation. If you are interested in a workaround....just create a new Transform object for each transformation.

     


  5. This is still happening to me with BYE 3.2.1 RC3 where the programs starts with default settings every time I launch it. The initial settings are different from what is in the user config file. Also the modified file timestamp does not change when settings changes are saved.

    I was trying to help a friend with a new EOS R6. He needs the latest pre-release to support the R6 but is experiencing the same settings issues.

    Any progress on fixing this?

    Thanks!


  6. OK, so I installed BYE 3.2.1 RC3 into a new folder and I have the same symptoms as dkerber is reporting.

    I even manually created a folder under VirtualStore\Program Files (x86) with the same folder name as  the BYE program folder and copied the BYE 3.2.0 config files into it. 

    The issue still persisted.


  7. I was curious and went trolling to look for where the configuration information is being stored. I had thought that user configuration files were in the directory with the program, but apparently that is just the default copy. That kind of makes sense since MS locks down program files to prevent one program from corrupting another.

    I ended up finding my configuration files in AppData\Local\VirtualStore\... I have full control over VirtualStore and child sub-folders. 

    I hope this helps.


  8. It is possible that this is a bug in the Transform class of the ASCOM.Astrometry. dll. This bug was introduced in ASCOM 6.5. It will be fixed with the Service Pack 1 release that is due out very soon.

    The symptoms are that if the client is re-using the same Transform object to perform, for example, J2000 to JNow transformation, that the Transform object will continue to report the previous coordinates instead of the new coordinates.

     


  9. The issue is with the RA and DEC in the filename. They have periods in the values. I was correct that the file names are legal Windows names and the fact that Nebulosity cannot tolerate them is due to a problem with Nebulosity. You can remove those fields from your template to workaround the problem. You should also provide the example file name to Nebulosity so they can fix their app. The calibration frames probably do not have the RA and DEc fields in the name. That is why they are tolerated by Nebulosity.

     


  10. Please provide an example of a file name with parentheses in the extension. BYE should only create image files with .CR2, .CR3, .JPG, or .TIF extensions. Do you have periods in your filename template? If so, perhaps you could replace them with underscores.

    That said, there is nothing illegal about a windows file extension that contains parentheses, so maybe Nebulosity has an issue.


  11. Sorry, no Device Hub does not have Focuser presets. 

    I put target focuser positions for different setups into a text document. For me the actual position will vary by as much as 100 steps, depending on the ambient temperature.

    When I wrote Device Hub, resource usage was a concern. It uses <0.1% of the CPU while connected to the ASCOM Simulated Focuser and reading the focuser position and temperature every few seconds.

    When I am out in the field I do not rely on the laptop's battery. I power my setup with 2 deep cycle 12V marine batteries. One is for the laptop and the other is at the mount for everything else.


  12. Long exposure noise reduction is a setting that you can change in the camera's menus.

    If you had a lens on the camera when you got the endless "busy" indication, was the lens set to Manual Focus? If not, it could be that the camera was trying, unsuccessfully, trying to focus the lens and never taking the picture.


  13. This forum is for questions about the BackyardEOS and BackyardNikon software for DSLR astrophotography.

    The Celestron 127eq is an OK entry-level telescope and mount for visual use, but is not suitable for astrophotography because it is totally manual and does not track to follow objects across the sky nor can it be computer controlled.


  14. BackyardEOS only works with EOS DSLR cameras that are listed as being supported in the Supported Cameras list at the bottom of this page.

    PowerShot camera models have a completely separate Canon SDK.

×
×
  • 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