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
ANKulin
I don't recall this having been a problem in the past until I tried updating BYEOS to a newer version. Because of issues with the software on my MS Surface Pro which I use when imaging outdoors (it is nice and light and easier to transport than a laptop), I also loaded ver 3.20 onto my home laptop, and 3.20 exhibits the same issue. I have managed to revert back to 3.1.16 on my MS Surface Pro but have this issue and another one (separate thread).
Here is the problem. If I have camera set to B, and try to take an image that is something like 1/10 s on BYEOS (so not bulb mode inthe software), OR, if my camera is set to M, and I try a Bulb Exposure with BYEOS the following happens, and I don't remember this being the case in the past.
I have attached the log file for troubleshooting. What needs to be done to fix this? As I noted I don't remeber this happening in the past (but I am finding my memory is not what it used to be too, so ...). And is this something that could be fixed in code? Flash a warning to set camera mode to B or M as needed (if not correctly set) before BYEOS tries to take the image and goes into some software twilight zone mode?
Thanks,
Andrew
logfile-[20200404-12h19m54s049]-[15100]-2020-04-04.txt
Link to comment
Share on other sites
Top Posters For This Question
2
2
2
1
Popular Days
Apr 5
4
Apr 4
3
Top Posters For This Question
admin 2 posts
astroman133 2 posts
ANKulin 2 posts
dkerber 1 post
Popular Days
Apr 5 2020
4 posts
Apr 4 2020
3 posts
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.