Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
- 0
Question
kaymann
Canon 60D firmware 1.1.2
BackyardEOS 3.1.18 Premium Edition
Greetings, I own a 60D just like in your 2 hour video. I can see you keep the camera in M manual mode but use the planner to set the drop down for bulb to what ever time you want. In you video the 60D/BEOS takes it all in stride. When I do exactly what you did I get an error and I am told to turn my 60D to B bulb mode and BEOS is basically a brick (dashed timer signal blinks but abort does nothing). If I go to the camera and then change the mode I still have to red X BEOS to shut it down and start over. Selecting Program or anything other than the Camera Mode setting from the drop down also Bricks BEOS, If I start the camera in B bulb going to manual in the planner also bricks the BEOS. In others match the camera mode and planner drop down it bricks. So the planner can only hold one mode or it will not execute that is perfect as at least it did not brick on me. So I totally understand allowing me to select a different mode than the cameras but instead of briciking up could BEOS tell me to change mode on the camera first before the session locks up? So ultimately I now understand I cannot mix and match B or M in my planner unless I disable the wrong mode until I go outside to the telescope and physically changing the mode dial FIRST.
If all of the above is true: A program change stopping me from bricking the BEOS program until shut down and restart would be fantastic. Also if true I am sorry for the user error and potentially giving someone reservations about BEOS when in actuality I love the program!
If the above is false and I should be able to have my camera in M manual and still select B bulb (or vice a versa) what am I doing wrong. I have cleared the cache and restarted several times with the same results.
BTW Every time you close the program like described above a new background process called "BinaryRivers.BackyardEOS.Start" for each time you do it, is left behind.
I absolutely love BEOS and it's integration with PHD2, dithering, and AstroTortilla. BEOS tying everything together in a fantastic interface is remarkable - thank you.
Thank you for your time and consideration.
Randall
Link to comment
Share on other sites
Top Posters For This Question
4
2
1
Popular Days
Jan 23
6
Jan 24
1
Top Posters For This Question
admin 4 posts
kaymann 2 posts
astroman133 1 post
Popular Days
Jan 23 2020
6 posts
Jan 24 2020
1 post
6 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.