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

Why D5300 is not connected with BYN 2.0.9


daravuthseng
 Share

Question

I just purchased BYN 2.0.9, but it seems is not connected with my D5300.

It used to work fine with the trial version. Do you know what is the version of the 30 days trial software.

The snap shot images are always out of focus when comparing with the live images. I am not sure because of

my camera or it caused by the latest version. Also, the bulb mode is always aborted after first picture taken.

Any helps are highly appreciated.

Link to comment
Share on other sites

  • Answers 7
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

7 answers to this question

Recommended Posts

  • 0

"Trial" is not the version. Trial, Classic, and Premium are the licenses. Versions are 3 part decimal numbers, like 2.0.9.

So you download version 2.0.9, install it and validate your free Trial license. Then when you have a purchased license, you apply that license to the same installation of BYN to activate the features that come with that license. The version number of the software that you have installed is displayed in the title bar of the main window when the program is launched.

So, you have a D5300 that used to connect, but now it does not connect. is that correct?

It would be best to solve the connection issue before talking about other issues.  Does Windows see the camera when you plug the USB cable to the PC and power the camera on? If not, then there is no way that BYN will be able to connect with the camera. Also, you need to be sure that you select the correct SDK for your camera when you attempt to connect. If you choose the incorrect SDK BYN will be unable to connect with the camera.

However, regarding your other issues, I would say that  BYN does not alter the images coming from the camera so it is unlikely that LiveView images are in focus but snap images are out of focus. No other users have reported an issue similar to this! Also, when you are taking Bulb exposures, be sure that they are being downloaded to the PC, not saved to the camera's memory card, and that your anti-virus software is not preventing them from being displayed. Also the camera must be in Manual mode to take BULB exposures.

 

Link to comment
Share on other sites

  • 0

I am a beginner and very new to BYN. I appreciate very much for kindly explanation and help.

On trial BYN, I had no problem at all to connect my D5300. After switching to Premium-BYN, suddenly it kept rejecting my connection.

Anyway, after I took SD card out from the camera. It's connected fine. It seems it solve my problem now.

Thanks again.

 

Link to comment
Share on other sites

  • 0

First, as Guylain has said. The only difference between a Trial license and a Premium license is that the Trial license terminates after 30 days. The software is exactly the same and all the features are active for both licenses.

If there are many images on the SD card, this is what is causing your connection issue. When the Nikon SDK (Nikon software that is used by BYN) first establishes a connection with a camera it attempts to build a catalog of all the images on the SD card that is in the camera. This can take several minutes and appear to prevent connection. The solutions are to use an SD card that is nearly empty, or to remove the SD card, as you did.

 

Link to comment
Share on other sites

  • 0

I have 64GB and only using 760MB. It still has a lot of empty space.

With the trial BYN, I had never touched SD card at all. Everything was on the spot  for both my D5300 and D810 connection.

I still believe there are bugs in premium BYN. It it's allowed, I prefer trial BYN rather than Premium one.

Link to comment
Share on other sites

  • 0

I will say again that you are incorrect.

The capabilities of the software are determined by the version number (2.0.9). The license only activates the features that the user has paid for. The Trial license activates all the features, but terminates after 30 days. The Premium license activates all the features, but with no termination date. The Classic license activates some of the features and has no termination date. So the only difference between the Trial and Premium licenses is the termination date. There is something else different between when you used the Trial license and when you used the Premium license. It could be a camera setting that BYN cannot or does not control or something like you are now using a different memory card.

The connection issue that relates to images on the memory card has nothing to do with free space on the card. It has to do with the number of image files that are stored on the card. The greater the number of images, the longer it takes the SDK to build a catalog of them. You can confirm this by downloading all of the images and erasing the memory card. Then connect BYN to your camera. Or you could use an empty memory card. Or you could move the memory card to the other camera to see that it then has the same connection issue.

Also, there are hundreds of users of BYN that have either a D5300 or a D810/810a. None of them are reporting similar behavior, where BYN works with a Trial license but not with a Premium license.

Link to comment
Share on other sites

  • 0
2 hours ago, daravuthseng said:

I have 64GB and only using 760MB. It still has a lot of empty space.

With the trial BYN, I had never touched SD card at all. Everything was on the spot  for both my D5300 and D810 connection.

I still believe there are bugs in premium BYN. It it's allowed, I prefer trial BYN rather than Premium one.

There is absolutely NO DIFFERENCE with the purchase editon and trial edition.  It is the SAME executable file.

If you are stuck believing they are different I'm afraid you are self-diagnosing the issue and you'd be 1000% wrong.  The are the same so we need to look at this pragmatically and not based on false assumption.

It looks however that you may have found the culprit when you removed the SD card.

 

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.

 Share


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