Jump to content

Canada's top-tier Telescopes & Accessories
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

ISS Transit


AaronSmall

Question

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.

iss-transit_Tv140s_100iso_960x640_20191113-21h01m45s_004243_pipp.gif.d3bd43741a2f8e4e280b30f15842ad1f.gif

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 0

I have had BYE ask to re-enter my username when I tried to use it while traveling away from home...I had thought it was due to changing the PC's local time zone.

Neat video Aaron!

Next time you forget your password, just change it. When logging in, click on "Forgot my password" and it will take you through a process to reset the password. Once complete you can then see your license. 

Link to comment
Share on other sites

  • 0

Thanks, guys.  The re-entering of the username is what threw me.  I thought it was asking for password, not Username.  Now I know.  Glad to hear it is a typical Windows update issue. My former college roommate works for MS.  Gives me a reason to blame him.

With all of the comments about camera not connecting, trial reissuance, etc., I thought I would post something on what BYE can do, rather than can't.  I didn't even consider my other cameras even though they have a faster frame rate.  BYE was just so much easier from connection, focus, then imaging.

Processing was simple:  convert to mono, stretch, and then assemble to the GIF.  All in PIPP.  I'll see if it works as well for my Mercury Transit shots (didn't use BYE because of using my cmos cameras, Guylain - hint hint 😉).

Link to comment
Share on other sites

  • 0
1 hour ago, AaronSmall said:

Thanks, guys.  The re-entering of the username is what threw me.  I thought it was asking for password, not Username.  Now I know.  Glad to hear it is a typical Windows update issue. My former college roommate works for MS.  Gives me a reason to blame him.

With all of the comments about camera not connecting, trial reissuance, etc., I thought I would post something on what BYE can do, rather than can't.  I didn't even consider my other cameras even though they have a faster frame rate.  BYE was just so much easier from connection, focus, then imaging.

Processing was simple:  convert to mono, stretch, and then assemble to the GIF.  All in PIPP.  I'll see if it works as well for my Mercury Transit shots (didn't use BYE because of using my cmos cameras, Guylain - hint hint 😉).

Yes, have fun with it and blame him, lol. 

The underlying issue is that W10 updates will often replace the entire windows install folder (or a large majority of it) and this triggers the "this is not the same computer" event in the licensing schema and it causes the license key to be re-validated.

Link to comment
Share on other sites

  • 0
On 11/17/2019 at 1:29 PM, admin said:

Yes, have fun with it and blame him, lol. 

The underlying issue is that W10 updates will often replace the entire windows install folder (or a large majority of it) and this triggers the "this is not the same computer" event in the licensing schema and it causes the license key to be re-validated.

Yep.  Definitely Peter's fault. 🤣

Link to comment
Share on other sites

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.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

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