BYN aborts after first image with 810A

[vbagwell]

Nikon 810a with BYN 2.0.9.  Latest Nikon firmware version C = 1.03.  The 810a release mode dial is set to S - single frame, and exposure mode is set to Manual, Bulb.  BYN is set to Imaging mode.  I can connect fine...tried two different USB cables.  In the capture center, I have (5) five 1-sec exposures, set to Bulb, with a 5 sec pause.  BYN takes the first image, then aborts.  Log file attached.  

Administrator, noted starting new thread.  Per BYN pdf docs, Getting Started, Powering Up... page 18; instructions state to set the release mode dial to S (single shot).  ***Note: this should not be confused with the Mup on the dial which is for mirror up.  Exposure mode is set to M, with shutter speed set to bulb on the camera.  Capture Plan settings: frame type = LIGHT, Cable Support = Camera USB, Save To = PC, Mirror Lock = 0, Delay = 0, Exposures = 5, Shutter = Bulb, Aperture = 5.6, Duration = 1 sec, ISO 200, Pause = 5.

 

logfile-[20180701-16h15m36s342]-[4208]-2018-07-01.txt

[vbagwell]

You nailed it.  In the 810A's Shooting Menu, disabling Long Exposure NR (Noise Reduction) fixed the issue.  Long Exposure NR was the culprit.  High ISO NR had no affect when set to normal.  Appreciate your time, as well as astoman133!  Thank you both!  

[astroman133]

I knew that I had recognized the error that is being generated by the camera (kNkMAIDResult_DeviceBusy). i searched the BYN forum for reports of this error. Over the years there have been several. A couple of reports were traced back to the fact that hacks to the camera's firmware (like the True Dark Current hack) change the camera's behavior to make it incompatible with the Nikon SDK. If this is not the case, you may get some benefit from reading the other threads.

I would also say that updated firmware can cause changes in behavior that require a newer version of the SDK. In fact, it appears that the firmware version 1.03 post dates the release of BYN 2.0.9. BYN 2.0.9 was released in October of 2017 and the 1.03 firmware update was released in February of 2018. It could be that Nikon has once again broken tethered control of their cameras with a firmware upgrade. The last time this happened users were out-of-luck until a new version of BYN with a compatible version of the SDK was released. There was no way for them to back rev the firmware to 1.02.

I am not a Nikon owner so I do not know if there is a newer version of the SDK available that is compatible with the 1.03 firmware. You may just want to download BYN 2.0.10 RC2 to see if that fixes your issue. Guylain may have other suggestions.

[vbagwell]

astroman133 , thanks.  I'm new to BYN this week and was previously on Nikon firmware 1.02.  I was seeing the abort with firmware at 1.02 and WTH upgraded to 1.03 when I checked for newer FW today.

[astroman133]

Still, installing version 2.0.10 RC2 and choosing the most recent SDK at connect time may be worth a shot. I would install it to a different folder, to keep 2.0.9 intact.

[vbagwell]

astroman133, I've installed 2.0.10 and no joy - abort still occurs after first image.  You referenced the "SDK".  Did I miss a prerequisite that needs to be installed with BYN?

logfile-[20180701-19h26m51s147]-[784]-2018-07-01.txt

[astroman133]

No, the Nikon SDK is installed with BYN. You select which SDK to use when you connect BYN with your camera. I can't be more specific than that because I have a Canon camera and the options are different.

[admin]

If you take non-bulb images does it work?

Is mirror lock set to ON on the camera?  If yes turn it off and try again.

 

Here is what I find odd, then camera throws a "busy" error but an image is taken and downloaded.

2018-07-01 19:28:12,874 [CameraTakePictureOnMessageRecieved] DEBUG - TAKE PICTURE ::: Shutter(MANUAL) Cable(CameraUSB) Av(3.5) Duration(1.0) Iso(200) Quality(RAW) Mirror(0) SaveTo(PC)
2018-07-01 19:28:17,220 [CameraTakePictureOnMessageRecieved] ERROR - [kNkMAIDResult_DeviceBusy] (kNkMAIDCommand_CapSet, 33089, kNkMAIDDataType_Boolean, 0)
2018-07-01 19:28:17,220 [CameraTakePictureOnMessageRecieved] ERROR -    at BinaryRivers.Camera.Nikon.Wrapper.NikonTaskQueue.Invoke(Delegate d, Object[] args)
   at BinaryRivers.Camera.Nikon.Wrapper.NikonBase.Set(eNkMAIDCapability cap, Object value)
   at BinaryRivers.Camera.Nikon.Wrapper.NikonDevice.StopBulbCapture()
   at BinaryRivers.Camera.Nikon.CameraModel.<>c__DisplayClass26_0.<DoTakePictureBulb>b__0()
   at BinaryRivers.Common.ProviderInterfaces.Camera.CameraControllerBase.DoWithCameraLocked(Action action)
   at BinaryRivers.Camera.Nikon.CameraModel.DoTakePictureBulb(Boolean start, Single mirrorlockseconds)
   at BinaryRivers.Common.Model.CameraModelBase.TakePictureBulb(Single durationseconds, Single mirrorlockseconds, String progresstext)
   at BinaryRivers.Common.Model.CameraModelBase.<>c__DisplayClass77_0.<CameraTakePictureOnMessageRecieved>b__0(Object state)

...

2018-07-01 19:28:19,426 [11] DEBUG - NIKON EVENT --> OnDeviceOnImageReady(1,type[1]) fired

...

2018-07-01 19:28:20,592 [ProcessOrphan(Normal)] INFO  - Loading image file : C:\Users\vbagwell\Pictures\BackyardTEMP\Download\img_1.NEF
2018-07-01 19:28:20,594 [ProcessOrphan(Normal)] INFO  - DCRaw.exe -c -e -T "C:\Users\vbagwell\Pictures\BackyardTEMP\Download\img_1.NEF"
2018-07-01 19:28:20,807 [ProcessOrphan(Normal)] INFO  - Image resized to : Width 3889 Height 2596 Factor 1.892142
2018-07-01 19:28:21,761 [ExifRead(Normal)] INFO  - C:\Users\vbagwell\Pictures\BackyardTEMP\Download\img_1.NEF
2018-07-01 19:28:21,762 [ExifRead(Normal)] INFO  - ExifRead C:\Users\vbagwell\Pictures\BackyardTEMP\Download\img_1.NEF
2018-07-01 19:28:22,066 [DeleteFile(Normal)] INFO  - Try delete C:\Users\vbagwell\Pictures\BackyardTEMP\exif_args_48a7b5d3-8ec3-4698-90cb-2aa46230c749.txt
2018-07-01 19:28:22,066 [DeleteFile(Normal)] INFO  - C:\Users\vbagwell\Pictures\BackyardTEMP\exif_args_48a7b5d3-8ec3-4698-90cb-2aa46230c749.txt DELETED!!!
2018-07-01 19:28:22,073 [MoveFile(Normal)] INFO  - move: C:\Users\vbagwell\Pictures\BackyardTEMP\Download\img_1.NEF
2018-07-01 19:28:22,073 [MoveFile(Normal)] INFO  -   to: C:\Users\vbagwell\Pictures\BackyardNIKON\IMAGE_20180701-19h28m22s067ms.NEF
2018-07-01 19:28:22,073 [MoveFile(Normal)] INFO  - Try move C:\Users\vbagwell\Pictures\BackyardTEMP\Download\img_1.NEF
2018-07-01 19:28:22,078 [MoveFile(Normal)] INFO  - moved to C:\Users\vbagwell\Pictures\BackyardNIKON\IMAGE_20180701-19h28m22s067ms.NEF
2018-07-01 19:28:22,714 [3] INFO  - IMAGE_20180701-19h28m22s067ms.NEF

 

 

[vbagwell]

Changing the exposure mode from Manual/Bulb to Manual/5 sec and Manual/1 sec was successful in capture plan.  Log attached.

logfile-[20180702-10h02m42s234]-[1532]-2018-07-02.txt

[vbagwell]

...and here's a second log file.  To confirm, my release mode dial is in S (single shot) and NOT in Mup (mirror-lock up).  In the capture plan, I set to shutter to bulb.  Started my plan.  BYN aborts after the first image (yes, it does download this image).  I then changed shutter setting in BYN from bulb to 1 sec.  Started plan again.  BYN shoots the five exposures without issue.  Error at 2018-07-02 10:17:32,060

logfile-[20180702-10h02m42s234]-[1532]-2018-07-02.txt

[admin]

I see no reason why it should not work

Try a factory setting on the camera.  May there is a setting somewhere what creates a conflict.  A factory reset has fixed a few odd behavior in the past.

 

[admin]

Ummm.... it's the end bulb that fails.

 at BinaryRivers.Camera.Nikon.Wrapper.NikonDevice.StopBulbCapture()

 

The end bulb capture does end... and the image is downloaded... but the camera/sdk throws a device busy error immediately after the bulb end command is issued.  What about some sort of in-camera noise reduction?  It seems like some post bulb is cause the error.

[admin]

8 hours ago, vbagwell said:

You nailed it.  In the 810A's Shooting Menu, disabling Long Exposure NR (Noise Reduction) fixed the issue.  Long Exposure NR was the culprit.  High ISO NR had no affect when set to normal.  Appreciate your time, as well as astoman133!  Thank you both!  

Glad you have this resolved now.

[astroman133]

Is there any way to accept LENR or at least fail more gracefully?

[admin]

26 minutes ago, astroman133 said:

Is there any way to accept LENR or at least fail more gracefully?

There should be... but I thought this was working like Canon in that the image is not downloaded before the noise reduction exposure is done.  It looks like Nikon are either setting a property (which I'm unaware of) or they fire the event indicating the image is ready (but is really not) pending the NR exposure is completed.  There could be some other force at play too which I'm may not be aware at this time

[s3igell]

Depending on the Image Processing regimen that you employ, High-ISO Noise Reduction will also have negative impacts on your results.  Most Processing routines expect the Original Data to be RAW Linear Data, as well as to see the "Original Noise Patterns".  Even though one of the Processes invoked will invariably be Noise Reduction, that Action can carefully evaluate the "Total Picture" of Noise across All the included Images - whereas Hi-ISO NR can only apply itself to One Image based on the Pattern in that Image.  Hence, most AP Imagers prefer to have both In-Camera NR Routines turned OFF.

[vbagwell]

s3igell, agreed.  I was kicking myself once NR was floated by Admin.  LENR is a setting enabled when I'm out shooting single-shot nightscapes.  I'll be adding it to my custom menu so I can get at it quickly and confirm its OFF when shooting with BYN and the telescope. :-)

[s3igell]

I can see the utility of LENR while shooting Single-Shot Nightscapes.  In fact, I remember reading somewhere that the High-End NIKONs have a "hybrid" LENR mode where the DSLR will shoot 2-3 Light Exposures before shooting the Dark Exposure if the Shutter is Pressed again within the first several seconds of an already started Dark Exposure.  There are limits, of course.  But "Handy" nonetheless...

 

[jdd54]

I posted this on another question too: I also had the same problem with my D800, would take 1 image and abort. Done a lot of trouble shooting, checked cable, camera settings, tried with and without lens and SD card, nothing helped. Changed setting in BYN from RAW+JEPG to just RAW and it works fine. Hope this helps.