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

D5100 disconnected after 4 hours of successful imaging


Saltcod

Question

Good morning Guylain,

 

Last night I was out imaging from 10:30 to 2:30,exposures ranging from 15 to 30min.,at the end of my session,I decide to take some 1min. exposures,it took the first one but hung up on image download..could not abort,camera disconnected.It was late went to bed.This morning,started the computer,and camera was not found...I disconnect everything,reconnect after reboot,now D5100 found:).went to capture plan and executed a successful session.Like you stated before,it's probably Windows going to image download mode instead of camera control mode.I also noticed that it wouldn't connect with PHD2.Sorry for loading you with all these log files but here they are in case you need them, thanx Richard

 

________________

 

CelestronAVX mount

Sky-Watcher 150mm reflector

Orion autoguider w/short tube 80

Nikon D5100

 

Windows 8.1

BackyardNIKON beta01d

PHD2.2.2

Orion autoguider driver ver. 04

-everything works on either usb 2.0 or 3.0

logfile-[20140531-22h59m30s599]-[5112]-2014-06-01.txt

logfile-[20140601-02h38m26s530]-[3584]-2014-06-01.txt

logfile-[20140601-10h02m51s057]-[3956]-2014-06-01.txt

Link to comment
Share on other sites

  • Answers 4
  • Created
  • Last Reply

4 answers to this question

Recommended Posts

Good morning Guylain,

 

Last night I was out imaging from 10:30 to 2:30,exposures ranging from 15 to 30min.,at the end of my session,I decide to take some 1min. exposures,it took the first one but hung up on image download..could not abort,camera disconnected.It was late went to bed.This morning,started the computer,and camera was not found...I disconnect everything,reconnect after reboot,now D5100 found:).went to capture plan and executed a successful session.Like you stated before,it's probably Windows going to image download mode instead of camera control mode.I also noticed that it wouldn't connect with PHD2.Sorry for loading you with all these log files but here they are in case you need them, thanx Richard

 

________________

 

CelestronAVX mount

Sky-Watcher 150mm reflector

Orion autoguider w/short tube 80

Nikon D5100

 

Windows 8.1

BackyardNIKON beta01d

PHD2.2.2

Orion autoguider driver ver. 04

-everything works on either usb 2.0 or 3.0

 

That is what beta testing is all about, don't be sorry or reporting issues.  I need to hear about them sooner rather than later.  I can only try to fix issues that I'm aware of :)

 

Since it required a reboot for Windows to see the camera again this looks the classic Windows/Nikon drivers not behaving again.  If windows does not see the camera BYN won't either.  I have a feeling this will be my biggest issue with BackyardNIKON and sadly it looks like there is not much I can do because the issue resides in the Windows driver itself as far as I can tell <_>

 

Send me the log files at support@binaryrivers.com and I'll take a look for the PHD2 thingy.

 

Regards,

Link to comment
Share on other sites

Hey Guylain,it happened to me again Friday and Saturday night.It happened relatively early in the session,although it didn't seem like the camera was disconnected,it started the image capture,counted down but I didn't hear the shutter being released...tried to abort but program had froze again.On both nights,I simply rebooted only once and everything was fine from then on,continued imaging for awhile.Sent the files...

 

Richard

logfile-[20140627-21h59m39s677]-backgroundworker-[1328]-2014-06-27.txt

logfile-[20140628-22h16m12s455]-backgroundworker-[3476]-2014-06-28.txt

logfile-[20140628-22h48m06s651]-[2348]-2014-06-28.txt

logfile-[20140628-22h48m16s215]-backgroundworker-[1060]-2014-06-28.txt

logfile-[20140628-22h54m03s075]-[4156]-2014-06-29.txt

logfile-[20140628-22h54m14s690]-backgroundworker-[4800]-2014-06-29.txt

Link to comment
Share on other sites

Thank you Scott,

 

I will look at the log files for sure.

 

I will not hide my disappointment in the Nikon SDK's inability to either see/connect to the camera -OR- loosing a connection after several hours of imaging.

 

This connection issue keeps coming back time and time again for several models if not all models at one point or another.  I'm tempted to explore other connection protocol in lieu of using the Nikon SDK altogether.  This would set back the release of BackyardNIKON by several months... maybe even 1 year... but I can not in good conscience release something that can't even connect to a camera reliably.  This is just not the quality standard I aim.

 

I'm on the fence with continuing using the Nikon SDK <_>

 

Regards,

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


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