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*
  • 0

Occasional issues with D5600 and BYN



Hi all,

As per the topic having occasional issues where the camera does not want to capture. I am getting a few instances where the camera times out and either the application crashes or i have to close it and then will not reconnect the camera until i restart the PC. Is there any logs that BYN creates that i could look into to see what the issue might be?

Secondly i am having troubles with an error message of set dial to M and the image session being cancelled. The camera is definitely set to that mode and the dial works perfectly if i look at the interface on the camera. Camera is about 4 months old. Not sure if its software, my hardware or BYN. I can have this happen once then reload and the imaging session is fine, other times ill do it and restart, get 5 or so captures and it will do it again.

PC is running windows 10, firmware is up to date on the camera as of about 2 months ago.

The only thing i am doing differently to some is i am running via a USB sharing program called virtualhere. I have a Raspberry Pi running VirtualHere and the camera plugged in via USB on the Pi (the Pi Also runs my guide camera and my controller). Both the PC and the Raspberry Pi are plugged in via network cable.


Link to comment
Share on other sites

  • Answers 2
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

2 answers to this question

Recommended Posts

  • 0

As I was ready you post I thought that this looks like it could be a USB cable issue... and then towards the end of your post you mention that the only thing you are doing differently is USB related.  Coincidence?  It's hard to tell, but it does point into that direction.

How long is your USB cable?  

My best guest is that the camera looses momentarily usb connect for just a millisecond or so, and once this happens all bets are off... the NikonSDK requires absolute 100% uptime usb connection.

A quick test you can do in-house is run BYN without the virutalhere program and the camera plugged directly into the computer.  If this works, and continues to fail with virtualhere afterwards it would look like your issue is virtualhere or related to it anyways.


Link to comment
Share on other sites

  • 0

My impression is also USB related. According to Nikon, the only supported configuration is for the camera to be plugged directly to the PC, not even going through a USB Hub.

Connecting to the RPi and using VirtualHere could be affecting the communication timing such that the SDK occasionally loses its connection to the camera. This can cause the Nikon SDK to hang which can cause BYN to hang or crash.

Canon has a similar issue with their SDK although they do not have any guidance that prevents connection through a hub.

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.

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