USB Cable Issue??

[thogle]

I have a Nikon D60 I used with BY Nikon for the 2017 eclipse. I am trying to duplicate this setup for the upcoming April 8 one. I have set up BY Nikon 2.06 Premium on a Win 10 computer, set the compatibility mode to Win Vista SP2 and selected the D60 in the Nikon 2015 driver set window. When I try to connect, it attempts to do so but is unable to find the camera, giving a list of possible things to try. I tried all of them without success. In the Capture Plan Center the Cable Support button is grayed out and non functional. I can connect to the camera through the OS to download pictures, etc, so the USB cable seems to be working. It is a different physical cable from the one I used in 2017, which I no longer have. I also tried this on an identical installation on a WinXP computer, which was the OS I used in 2017.  I'm unable to determine what to try next.

[astroman133]

Not sure what is going on with your setup, but the D60 is listed as Not Supported on the Supported Cameras page. Are you sure that you have used it with BYN in the past?

The Cable Support option is for BULB shutter control and would typically be grayed out when viewed on the Preview screen while not connected.

 

[admin]

I only support cameras that have are supported on Windows 8/10/11.

Support for the D60 was removed several years ago. 

[thogle]

astroman133 - Thanks for your quick reply. I don't know what the current version of BYN supports (admin says that D60 support was removed years ago). I have only used version 2.06, which I downloaded in 2017 and saved (it does list the D60). I am using the same setup except for a different physical USB cable and computer (then Win7 on HP, now Win10 on Dell and WinXP on very old Toshiba).

I was thinking that perhaps there are issues with some USB cables like there have been in the past with some serial cables not working for certain applications. But I think that has been resolved, and in the USB world you either have a USB data cable or a USB charging cable. It works or it doesn't, and that's it.

I am able to connect the camera to the Win 10 computer with my USB cable and the computer recognizes it and allows me to download images, but doesn't actually assign a drive letter to the camera, as I have seen in previous OS installations.

From your response, it sounds like I have not missed a step, which was my original concern. If you have other suggestions, I'm listening. My fallback, of course, is a totally manual setup, which will mean focusing on the camera rather than enjoying the eclipse experience for a change. Or, heaven forbid, leave the camera at home.

[astroman133]

The camera might have two different connection modes. One is for image download and the other is for remote control. If you set it up for image download then this could cause BYN to not connect.

When Windows first recognizes the camera it should ask you how you want to use the device. What you answer could affect whether BYN can connect. I would suggest that you try the "Take No Action" option.

Let us know how it goes.

[thogle]

The Default configuration when the D60 is turned on is to open a browser window in both Win7 and 10. In Control Panel Devices and Printers D60 Change general settings, the default when connecting is Browse files, as you mentioned. Unfortunately, the box to change this is grayed out in Win 10, so I don't know how I can change it to "Take No Action". This option is available in the setup I did on my Win 7 desktop, but changing it does not fix the problem. 

On a related note, I see that in each of the BYN log files, there is the following error messages that I don't understand at all - they may or may not relate:

2024-04-04 11:41:56,820 [Main] INFO  - 8 CPU(s), Processor Affinity is not SET
2024-04-04 11:42:00,657 [Main] ERROR - Input string was not in a correct format.
2024-04-04 11:42:00,657 [Main] ERROR -    at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
   at System.Convert.ToInt32(String value)
   at BinaryRivers.Common.Extensions.StringExtensions.ConvertToInt32(String int32String, Int32 defaultvalue, Boolean verbose)
 

The messages are similar in my Win7 set up except that Affinity is set to 2.

 

[astroman133]

There was an issue that was fixed several years ago that showed up for users outside of North America who used a comma character as their decimal separator. I am wondering if a workaround to your issue could be to change your Windows Region settings to English (United States), at least for imaging during the eclipse.

I hope this helps.

[thogle]

Tied everything I can think of and what you have suggested. No joy. I will have to go manual.

[thogle]

But thanks for all your help trying to get me up for the automated system.

[astroman133]

I almost hesitate to mention this, but a BackyardNikon user who was using the latest pre-release got the same error and it appears to related to an issue with some computers with an AMD chipset. His solution was to connect the camera through a USB hub.

If you have a spare hub, it couldn't hurt to try it.

[thogle]

Well,good idea, but since I am half way across Texas on my way from SoCal and it’s pretty barren out here, I’m not sure where I might find a hub. As I recall, the instructions for BYN say not to use a hub. But I’ll see if I can snag one.

[astroman133]

Yes, Nikon says not to use a hub. But folks do use hubs without any problem. The issue with the BYE users was some apparent incompatibility with the AMD chiipset that was masked when the camera was NOT directly connected to the PC.