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

Nikon D80 connection


johnorris
 Share

Question

I must be doing something wrong.  I have a Nikon D80, firmware v1.01 (both A and B).  The camera USB is configured for PTP, not MASS STORAGE.  I'm using the latest version of Backyard Nikon Premium (v2.0.8), with a USB cable and a Shoestring Astronomy DSUSB interface cable.  I turn on the camera, select CONNECT>NIKON2015 drivers>D80.  I seem to connect OK (ref attached log), or at least I don't get the buzzing sound and "can't connect" error message if I try to connect with the D80 powered OFF.  But, I'm left with the mostly greyed out screen (ref screenshot) where only CONNECT and PREVIEW are active.  PREVIEW seems to be for use when a camera is not connected.  Hence my confusion.  I've tried alternant USB ports (no hub is being used), connecting USB cables before/after Backyard Nikon is started, etc, with no luck.

So I am stumped!  Any assistance would be greatly appreciated.  Thanks!

Screen after camera is connected.jpg

log history.txt

Link to comment
Share on other sites

  • Answers 17
  • Created
  • Last Reply

Top Posters For This Question

17 answers to this question

Recommended Posts

  • 0

Thanks for the suggestion to change the camera setting to Mass Storage.  This is where I started, and the connect issue is even worse (ref screenshot).  WIth Mass Storage, I get the buzzing sound indicating an error and "can't connect" error message.

Good try, but I'm still not connecting for some reason.  Could it be the very old camera firmware rev?

With camera USB set to MASS STORAGE.jpg

Link to comment
Share on other sites

  • 0

It does not seem likely that the firmware rev is the cause of your issue. I do not recall an instance where a firmware upgrade fixed someone's connection issue.

BTW you attached the abbreviated log history file to your original post. It shows which SDK you selected, but does not indicate that you successfully connected.

Does Windows recognize the camera? If so, it should show up as a device in the Windows Device Manager after the camera is plugged into the PC and powered on.

Do you hear the crackle sound immediately after clicking on the Connect button or does it take several seconds? If so this could be caused by having many images on the camera's memory card. This is because the Nikon SDK wants to build an internal list of the image names. You should either remove the memory card or remove all the images on it.

 

Link to comment
Share on other sites

  • 0

The PC recognizes the camera as a D80 Nikon DSC D80.  There are no images on the SD card, I deleted them prior to installing BYN.  When the camera USB is configured as PTP, there is no crackle sound.  When configured as Mass Storage, the crackle sound occurs ~4 seconds after the Connect button is pressed.  The BYN icon is configured to run in Windows Vista (Service Pack 2) compatibility mode (ref attached picture).

Thanks again for your suggestions.  Hopefully we'll get there!

BYN Configuration.jpg

Link to comment
Share on other sites

  • 0

I am not a Nikon owner so am not familiar with the SDK options in BYN. In BYE, when you click on the Connect button you are presented with 3 options. Each of those options corresponds with a different version of the Canon SDK. If you are not presented with options then you may need to go into the Advanced Settings and select the "Ask for camera drivers" option.

Performing a firmware upgrade to the camera might require that a newer version of the SDK would need to be specified.

Over time Nikon adds and drops SDK support for some cameras. This means that your camera may work with more than one SDK. The D80 is 11 years old, so I would start with the oldest SDK, and work my way the the next oldest, etc.

If one connects BYN with the camera then I would do further testing with that verson.

Link to comment
Share on other sites

  • 0

BYN has 2 choices after CONNECT is pressed (see attached screenshot).  This is true with the "Ask for camera drivers" option as well.  There is no SDK button in either of the 2 choices.  Is there a way to add the SDK option?  I have downloaded the D80 SDK from Nikon, but I have no idea what to do with it.

Perhaps of interest, when Nikon2015>D80 is selected, the green LED on the back of the camera does briefly illuminate, so the computer is doing something with the camera.  But BYN doesn't seem to finish the connection, or my camera is dropping the ball.  Is there any additional information that might help determine what's going on?  Or is there something I can do with the SDK download?

Thanks.

BYN Driver Selections.jpg

Link to comment
Share on other sites

  • 0

This screen *IS* the sdk options.

Take a look at this post where a user made his D80 work. He did set the connection to MTP/PTP though.  I'm perplexed because I know that PTP is not how BYN communicates to the camera.

Do a factory reset on your camera; this may reset a setting that for some reason is preventing the connection.  I've seen this fix quite a few connection issues in the past from different users.

 

 

Link to comment
Share on other sites

  • 0

When you install BYN you get the SDK files that it is compatible with. There is no need to download SDK files for your camera, since you already have them with BYN.

It appears that the D80 status was changed to "supported" as a result of the guy above, but that it really doesn't completely work!

Guylain, in that message thread you changed the status to supported based on the log file provided by that OP. Which SDK version did he use to get it to work? Can you tell if it really was in PTP mode?

Link to comment
Share on other sites

  • 0

I factory reset the camera, and started BYN with Nikon2015 selected.  Same problem.  I've attached the log files.  I hope you can find the problem, and I appreciate the great level of support you have given me.  Thanks.

logfile-[20171010-21h12m24s372]-backgroundworker-[7480]-2017-10-10.txt

logfile-[20171010-21h12m01s019]-[7452]-2017-10-10.txt

logfile-[20171010-21h12m21s986]-backgroundworker-[7116]-2017-10-10.txt

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