Tbar23

Hi - I've been a happy BYE user with my Canon EOS RP for several months. I recently purchased an EOS R7. I tried connecting with BYE and failed. Any chance a pre-release is in the works that would support an R7?

Mystery solved. It looks like it was the Microsoft automatic Windows Update client. I changed settings to say that computer is typically in use from 6p through 8a (as opposed to "normal" business hours). I also set it to ask to do a restart after update rather than automatic. Bummer I didn't investigate more closely earlier this month because it just happened to me again last night!

Thanks. The log file lines I posted were the tail end of the BYE log file. However, I'll track down the Windows Event Log.

So any thoughts on how to troubleshoot an unexpected BYE quit? Looking at the photo files generated, I see one timestamped 00h03m47s and one timestamped 00h01m41s, so the files are getting generated properly.

Last night I started a session around 10p that was supposed to run for about 4.5 hours. Just after midnight BYE quit. The last 25 seconds of log file looked like this: I attached the full log file from that time. I appear to get a bunch of these Parameter=4 and Parameter=7 DEBUG events. Might this be the cause. Any thoughts? Thank you! logfile-[20220604-21h27m22s485]-[2648]-2022-06-05.txt

Just found this post: https://www.otelescope.com/forums/topic/5090-astap-installation-and-use/ Let me try using the Center button. Sorry for asking redundant question.

So I’m still having some trouble understanding how to get Backyard EOS, ASTAP and Stellarium to play nicely together. I have both Stellarium and BYE connected to my mount. I can launch telescope control in Stellarium. I have approximately set the FOV using the ASTAP app. Now I go into Stellarium and using telescope control let it slew to an object. Go to BYE, take an image and click on Advanced Mode. I have the path for ASTAP set. I enter the object name and the coordinates (I can read these right off of the RA and DEC that the mount thinks it is pointing to). Now I click the arrow next to the message that says something about solving the current image. The activity circle in the upper right spins for a bit and then I get a log message that says “Target RA(06h 01m 44s) DEC(+46* 25’ 44”) acquired [now].” However, it isn’t clear that anything happened. At one point when I did this, I thought I got an amount of error or something, but now I just see the message about the target acquired. Do I need to go back to Stellarium to sync the current position? Am I missing a step or steps? Thanks!

Hmm, so that gets me back to wondering why the temp went up so much when my imaging session completed. During the 20 minutes between finishing my first imaging session and the start of a new session for Darks my camera should have just been sitting there in whatever state BYE leaves it in at the end of a capture sequence. LCD closed. Definitely no video and no focusing. And image download happens after each image is taken so that shouldn't have been occurring either. I'll have to do some experiments on a cold night and see what I learn.

I guess the question is what mode is the camera in when BYE finishes a capture? If it defaults to LiveView, then perhaps that is why the temp went back up so quickly.

Last night I was taking photos with my Canon EOS RP and Backyard EOS. The first set of photos showed a temperature that settled out around 12C during an ~75 min session (ambient temp of ~5C). I was watching a movie when the session ended, so it took me about 20 minutes before I got outside, put the telescope lens cap on and then started a series of Darks. What I find odd is that the first Dark photos are up at 21C and drop down to 13C over the next ~20 minutes. What would cause the temp to go up nearly 9C with no imaging session going on?