BYN buzzing at me!

[skycamper]

I tried to get my side by side telescope going with my two D5300's  unfortunately I could not get them to connect correctly.  Ive attached log files for what I think are the connection problems if thats in there.

BYN would only buzz at me when I attempted to connect.  Does this generate a log file I can send you?  The camera is on, AC power, no USB hub, 1 meter USB cord,  latest BYN 2.09.  Windows 10 with 8 GB Ram. Ive never used BYN with this camera, this was my first time.  I think I saw in BYN where it says camera connected!  a message about at SDK error.  

The other camera ive shot with plenty using BYN,  but now the downloads are super slow similar to my recent EOS problem that was solved with the reinstall of C++ programs.  I dont have any obvious errors    In either case , no other programs I know are running and I have no USB hubs.  I tested this camera before I took it outside and it was fine even while using snap images..... I dont get it.  I have a new laptop with more memory thats waiting for me but this older Dell has been working fine until a few weeks ago starting with my EOS connection problems. Now this!

logfile-[20180319-23h03m55s173]-[10316]-2018-03-19.txt

logfile-[20180319-23h04m33s850]-[5944]-2018-03-19.txt

logfile-[20180319-23h15m38s184]-[3052]-2018-03-19.txt

logfile-[20180319-23h35m40s354]-[228]-2018-03-19.txt

[skycamper]

In these log files I think are  where my regular use D5300 just stalls out and does a "takes forever download or does not download at all and there is no error other than BYN telling me that its taken longer than 60 or however many seconds to download. Not sure.  I wish I were more helpful here but Im not great with computers.    

I see Im a long way off from getting two cameras to capture data for me in a side by side situation. Hopefully these are not hard fixes and maybe just need some updates or firmware. 

logfile-[20180319-22h47m11s934]-[13148]-2018-03-19.txt

logfile-[20180319-22h47m11s934]-[13148]-2018-03-20.txt

logfile-[20180319-23h04m33s850]-[5944]-2018-03-20.txt

logfile-[20180319-23h10m12s520]-[8044]-2018-03-20.txt

[admin]

I'm a bit confused here.  What are you trying to do?  You mention BYN (which means Nikon) and then you mention EOS (which means Canon).

You also mention 2 cameras, side-by-side.  Please confirm that both cameras do work by themselves before bringing up any side by side issue.... this will help to find the cause and/or understand what the issue is.

[skycamper]

Sorry, I'm only having problems with my nikon and BYN. Not EOS.

I never made both cameras work at the same time as camera 1 and camera 2 and I never attempted to since I could not make them work individualy.   

I want to use them as camera 1 and camera 2 but since I couldent even connect the first one.  As mentioned in my post above.

Sorry for the confusion,  let me know if this is still not clear.  

 

[admin]

Okay, BYN is the only issue for now and only on the new computer, correct?

[astroman133]

It sounds like you have multiple cameras and multiple computers with multiple issues. It will be confusing to try to deal with more than one issue at the same time, so please pick one hardware combo (camera and PC) and describe your issue only with that set of hardware.

Thanks!

 

[skycamper]

Not exactly guys,  

I have two cameras boths are D5300's .    I have one computer that Im using as described above with Win 10 8GB Ram, no usb hubs.  I have acess to a new laptop though but have NEVER used it.  Im NOT using multiple computers.

One camera does not connect at all,  and the one that ive been using and now only recently am having slow downloads with to the point its not usable. However, on this particular camera I tested it in my house before taking it outside and it was fine.  Its performance is not consistent.

[astroman133]

Ok, so the second computer is not relevant, except perhaps to use for troubleshooting.

For now, set aside the camera that won't connect at all.

First, let's talk about the camera with inconsistent performance. It works fine when bench testing, but is very slow when field testing. What is different? Same PC, same camera, same cabling? Any PC updates between testing sessions? Anti-virus software running in both cases?

Looking at one of the log files I can see where you are taking a 5 second RAW image and that BYN is timing out after not being able to download the image. This could be due to your anti-virus software preventing the image download. I would suggest temporarily disabling the anti-virus software and trying the capture plan again.

Now, the camera that won't connect...Does this camera have newer firmware? If so, then you would likely need to choose a newer version of the SDK when connecting.

[skycamper]

Thanks for the fast response!    On the camera that wont connect, yes the field test has same everything. No updates between bench and field, anti virus software was running in both cases.  I dont have Norton, or AVG or anything like that, in fact I have not installed any antivirus software, the only thing that I have is windows firewall or whatever runs in the background of win 10.  

Should I try disabling windows antivirus as you suggest?

Yes the camera that wont connect has a slightly newer firmware 2.01 , I do remember trying both SDK's with that camera and they did the same thing (BYN makes a buzzing sound)  

 

[admin]

Try a factory reset on the camera.

[skycamper]

Ok some progress, factory reset both cameras but it didn't do anything different , then I turned off windows 10 antivirus  I was able to connect both cameras individually.  One takes the newer SDK and the other one is the older SDK.   

Unfortunately, bench testing them individually and both do the same thing, I can go into live view and begin looping snap images and I cant even get the first photo to download with it timing out.  Here are some screen shots of my anti virus protection status and permissions, is this correct?  and the log files of the time outs.

Is it time to move to the newer laptop or is there something else to try?  

Again, no USB hubs, 3 foot usb cord,  Win 10, 8GB ram.   Not using any SD cards,   Both my connection cords work.

logfile-[20180321-22h00m26s456]-[4648]-2018-03-21.txt

logfile-[20180321-22h07m11s869]-[3368]-2018-03-21.txt

logfile-[20180321-22h12m16s575]-[5412]-2018-03-21.txt

[astroman133]

I can see that you have a lens attached to the camera when bench testing. This is from the first log file:

2018-03-21 22:03:19,707 [8] DEBUG - TAKE PICTURE ::: Shutter(MANUAL) Cable(CameraUSB) Av(1.8) Duration(0.0) Iso(Hi-1.0) Quality(JPEG Fine) Mirror(0) SaveTo(PC)
2018-03-21 22:03:21,582 [8] DEBUG - Device Busy trying to start picture sequence
2018-03-21 22:03:21,582 [8] ERROR - [kNkMAIDResult_OutOfFocus] (kNkMAIDCommand_CapStart, 17, kNkMAIDDataType_Null, 0)
2018-03-21 22:03:21,582 [8] ERROR -    at BinaryRivers.Camera.Nikon.Wrapper.NikonTaskQueue.Invoke(Delegate d, Object[] args)
   at BinaryRivers.Camera.Nikon.Wrapper.NikonBase.Start(eNkMAIDCapability cap, eNkMAIDDataType dataType, Int32 data)
   at BinaryRivers.Camera.Nikon.CameraModel.<>c__DisplayClass27_0.<DoTakePicture>b__0()
   at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.DoWithCameraLocked(Action action)
   at BinaryRivers.Camera.Nikon.CameraModel.DoTakePicture(Single mirrorLockSeconds)
   at BinaryRivers.Common.Model.CameraModelBase.<>c__DisplayClass79_1.<TakePicture>b__0(Object state)

Is it possible that you also have the lens cap covering the front of the lens? Or some other reason why the camera is not able to autofocus?

If I am reading the log file correctly, the camera never starts to take the picture because it is trying to autofocus. Does it work better if you put the lens in Manual Focus? On Canon cameras, there is also an in-camera menu setting that moves the autofocus operation from the shutter to a different button so that it does not try to autofocus when the shutter is pressed.

I am glad that you got the other camera to connect!
 

[skycamper]

I thought about that but no there's no difference. The camera with no lens and just the body cap behaves the same, I did put the switch on the lens to manual and there was not a difference.   Still timed out.  Not sure if the cap was on but I know it was not in focus.  

[admin]

2 hours ago, skycamper said:

I thought about that but no there's no difference. The camera with no lens and just the body cap behaves the same, I did put the switch on the lens to manual and there was not a difference.   Still timed out.  Not sure if the cap was on but I know it was not in focus.  

Not possible, if you have no lens the camera should never throw the out of focus error.  Some Nikon cameras also have an AF button on the camera body, set that to manual focus too.

Let's remove the lens out of the mix.  Then repeat your test and send me those log files.

[skycamper]

I can do that but the other camera didn't have a lens attached and it was performing in the same fashion.  One of the log files above might show that but I'll try again and send it over.  

[astroman133]

The log snippet in my previous post was from the first file. This one is from the last file and apparently the other camera was used.

2018-03-21 22:13:23,771 [11] DEBUG - TAKE PICTURE ::: Shutter(MANUAL) Cable(CameraUSB) Av(--) Duration(2.0) Iso(Hi-1.0) Quality(JPEG Fine) Mirror(0) SaveTo(PC)
2018-03-21 22:13:31,713 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2018-03-21 22:14:28,913 [CameraTakePictureOnMessageRecieved] ERROR - Image download timeout, process terminated after 59 seconds
2018-03-21 22:14:28,913 [CameraTakePictureOnMessageRecieved] ERROR -    at BinaryRivers.Common.Model.CameraModelBase.WaitForImageToDownload(Single durationseconds, Boolean isbulb)
   at BinaryRivers.Common.Model.CameraModelBase.TakePicture(Single mirrorlockseconds, String progresstext)
   at BinaryRivers.Common.Model.CameraModelBase.<>c__DisplayClass77_0.<CameraTakePictureOnMessageRecieved>b__0(Object state)
2018-03-21 22:14:28,944 [CameraTakePictureOnMessageRecieved] INFO  - Imaging session cancelled
2018-03-21 22:14:28,960 [CameraTakePictureOnMessageRecieved] INFO  - Image download timeout, process terminated after 59 seconds
2018-03-21 22:14:28,960 [CameraTakePictureOnMessageRecieved] ERROR - Image download timeout, process terminated after 59 seconds
2018-03-21 22:14:28,960 [CameraTakePictureOnMessageRecieved] ERROR -    at BinaryRivers.Common.Model.CameraModelBase.WaitForImageToDownload(Single durationseconds, Boolean isbulb)
   at BinaryRivers.Common.Model.CameraModelBase.TakePicture(Single mirrorlockseconds, String progresstext)
   at BinaryRivers.Common.Model.CameraModelBase.<>c__DisplayClass77_0.<CameraTakePictureOnMessageRecieved>b__0(Object state)

This shows BYN timing out because no image is available from the camera. This is the same error that I saw in the first group of logs that you posted. It appears to be a 2 second Snap image from Frame & Focus and it does not appear that you have a lens attached. I am at a loss to explain why the camera is not providing an image.

Does it behave the same way if you execute your capture from the Imaging screen and download a RAW image?

[admin]

Did you changed any of the advance parameters in BYN?  If yes go back and set them to default.  

Also, is it possible that you have mirror lock enabled?  If yes disable it and try again.

[astroman133]

Do you mean the in-camera mirror lock setting?

[skycamper]

No mirror lock is off, but I might have changed an advanced setting.  I'll make it default again.   

[admin]

10 minutes ago, astroman133 said:

Do you mean the in-camera mirror lock setting?

yes, sorry.

[skycamper]

Here are my settings, the camera Force Read Properties was checked. But that was the only thing that changed when defaults were restored.   Camera still stalls though.  Heres the screenshot and the log.

logfile-[20180322-07h26m55s117]-[12356]-2018-03-22.txt

[admin]

I'm sorry but there was no attempt to actually connect the camera in that latest log file.

To remove all confusion... delete all the log files... all of them.

Then start the application and connect the camera and take a single image in "Image Capture"

Close the app and send me that log file.

[astroman133]

What about settings in the camera? like mirror lock?

[skycamper]

I deleted all logs per your request............Mirror says off in BYN.   I dont have LENR on or anything like that.     AND NOW the problem seems to have been fixed on the camera with the newer SDK.  Here is the log file.   Snap images went smoothly and I did a 20 photo capture plan without any hang ups.  Awesome.   Im going to test the other camera now and if it works ok I'll test them together as duel cameras.

logfile-[20180322-15h18m32s149]-[5920]-2018-03-22.txt

[skycamper]

Heres the log file on the one with the older SDK which for some reason only connected to the default SDK BYN version.   I bench tested it and did not find an issue. Here is that log file.     Now I'll test them both.

logfile-[20180322-15h35m41s230]-[2188]-2018-03-22.txt

[skycamper]

Ok, so with one camera on and connected and ready to insert data capture plan info......I plug the other camera into another dedicated USB port and click the button  "duel camera"  and come to this screen.  What now?    It shows spots for three cameras!   Im lost again!

Thanks!

[astroman133]

Even though the feature is called "dual camera" you can really control up to 4 cameras. This is described in the User Manual. It tells you how to configure the master instance and the slave instance(s).

 

[admin]

Page 47 in the user manual as Rick said... very good description on how it works.

[skycamper]

This  is great guys I appear to be all set I really appreciate this thank you

[admin]

Just now, skycamper said:

I can do that but the other camera didn't have a lens attached and it was performing in the same fashion.  One of the log files above might show that but I'll try again and send it over.  

Ok, stop right there!

Dual camera ASSUMES similar setup.  If you have a camera with and lens and one without all bets are off.  Don't do that.

Dual camera tries to send the same camera command from the master instance to the slave instances, so if the master does not have a lens and the slave does and it won't know what to do with the aperture.

You need to have similar setup.

[astroman133]

If you have two cameras with different setups, For example, one camera at prime focus to a telescope and a second camera piggybacked with a lens, then you do not want to use the Dual camera feature. The basic idea of dual camera is to have the master and slave synchronized so that they start and finish each image at the same time. That way the master instance can dither the mount between exposures. This won't work unless the master and slave have the similar optics, so the same exposure values (duration, f/stop, & ISO) can be used for both cameras.

If you have different setups (one with a scope and one with a lens) you can use the camera1 and camera2 instances of BYN, but not tie them together as master and slave.