Monomod D600 and BYN -> Error

[Herra_Kuulapaa]

EDIT: OK, noticed that this was addressed partly already, original message shortened. Please move this to existing thread.

 

These are the errors I receive:

11:20:45  [kNkMAIDResult_UnexpectedError] (kNkMAIDCommand_CapGet, 33342, kNkMAIDDataType_UnsignedPtr, 351002708)

11:21:36  [kNkMAIDResult_DeviceBusy] (kNkMAIDCommand_CapSet, 33089, kNkMAIDDataType_Boolean, 1)

11:23:09  [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 471263628)

11:25:08  [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 276162092)

 

Battery change to DC adapter doesn't help. Download seems not to proceed and storing image in camera results timeout. Also a serial port trigger won't make any difference.

 

br,

HK

[admin]

What version of BYN?

[astroman133]

The errors are several seconds apart. What are you trying to do when you get those errors? Did you extract only the errors from the log to paste into your post?  If so, they are out of context for what BYN was trying to communicate to the camera. Some errors may be normal when BYN is initially trying to determine your camera's capabilities.

 

Is the camera connected to a telescope at prime focus or does it have a lens attached?

 

Only the latest version of BYN (1.0.2) has the ability to download images to a PC AND save image to the camera's memory card.  And, this capability only works for some cameras due to irregular support from Nikon.

 

Do you have mirror lock disabled in the camera?

 

You should not need a serial cable for BULB.

 

Providing more information will help you get a quicker reply/resolution of your issue!

[Herra_Kuulapaa]

What version of BYN?

 

It's the latest one (1.0.2)

[Herra_Kuulapaa]

The errors are several seconds apart. What are you trying to do when you get those errors? Did you extract only the errors from the log to paste into your post?  If so, they are out of context for what BYN was trying to communicate to the camera. Some errors may be normal when BYN is initially trying to determine your camera's capabilities.

 

Is the camera connected to a telescope at prime focus or does it have a lens attached?

 

Only the latest version of BYN (1.0.2) has the ability to download images to a PC AND save image to the camera's memory card.  And, this capability only works for some cameras due to irregular support from Nikon.

 

Do you have mirror lock disabled in the camera?

 

You should not need a serial cable for BULB.

 

Providing more information will help you get a quicker reply/resolution of your issue!

 

"Providing more information will help you get a quicker reply/resolution of your issue!" Wow, now that's a proper corporate IT help desk type of response Just being sarcastic as I consider this more like a friendly astrophotography community

 

 

Yes, errors were picked from the message log to shorten the initial post. Errors were resulted different permutations.

Camera was operated with only body cap on it - 60 sec exposures, 10 times, 10 sec pauses. Saving was tested both to either PC and card. No mirror lockup. Serial cable and USB shutters were both tested to isolate the error source, seem not the be related to neither of them.

 

11:18:31  Nikon drivers initialized.

11:19:11  Attempting to connect camera...

11:19:12  D600 CONNECTED!

11:19:42  Imaging session started.

11:20:45  Imaging session cancelled

11:20:45  [kNkMAIDResult_UnexpectedError] (kNkMAIDCommand_CapGet, 33342, kNkMAIDDataType_UnsignedPtr, 351002708)

11:20:45  Camera SHUTDOWN!

11:20:46  Imaging session cancelled

 

11:20:55  Attempting to connect camera...

11:20:56  D600 CONNECTED!

11:21:35  Imaging session started.

11:21:36  Imaging session cancelled

11:21:36  [kNkMAIDResult_DeviceBusy] (kNkMAIDCommand_CapSet, 33089, kNkMAIDDataType_Boolean, 1)

11:21:37  Imaging session cancelled

11:21:40  Camera SHUTDOWN!

 

11:21:53  Attempting to connect camera...

11:21:54  D600 CONNECTED!

11:22:05  Imaging session started.

11:23:09  Imaging session cancelled

11:23:09  [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 471263628)

11:23:10  Imaging session cancelled

11:23:25  Camera SHUTDOWN!

 

11:23:59  Attempting to connect camera...

11:24:00  D600 CONNECTED!

11:24:04  Imaging session started.

11:25:08  Imaging session cancelled

11:25:08  [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 276162092)

11:25:09  Imaging session cancelled

11:26:19  Camera SHUTDOWN!

[admin]

Try with BYN 1.0.1. It could be that the new setting to save to card is not properly supported in the SDK for this model and trying to set it causes an error.

 

Also, send me the full log file at support@otelescope.com.

 

Regards,

[admin]

I just looked and error 33560 is "kNkMAIDCapability_TerminateCapture".

 

It looks like the camera is not responding to terminate capture.  As Rick mentioned, do you have mirror lock up enabled?

 

Try removing the battery for a few minutes to power cycle the camera, just a guess here.

 

Regards,

[s3igell]

"Providing more information will help you get a quicker reply/resolution of your issue!" Wow, now that's a proper corporate IT help desk type of response Just being sarcastic as I consider this more like a friendly astrophotography community

 

And just to rise to Rick's (Astroman133) defense:  Rick is NOT affiliated with BYE/BYN's "Corporate IT Help Desk" in any fashion beyond being one of the most responsive and helpful of the legion of BYE Users.  

Because the "Corporate IT Help Desk" is the same Guylain Rochon who is also the "Lead Developer" and "CEO/Owner" and pretty much "Jack-of-all-Trades" for BYE/BYN, a small number of us Users (myself included) tend to Speak Up and provide at least "Initial Responses" that Share our Understanding and Experiences with the Software.  

That is our contribution to a "Friendly AP Community" here on the BYE/BYN Support Forum

[Herra_Kuulapaa]

And just to rise to Rick's (Astroman133) defense:  Rick is NOT affiliated with BYE/BYN's "Corporate IT Help Desk" in any fashion beyond being one of the most responsive and helpful of the legion of BYE Users.  

Because the "Corporate IT Help Desk" is the same Guylain Rochon who is also the "Lead Developer" and "CEO/Owner" and pretty much "Jack-of-all-Trades" for BYE/BYN, a small number of us Users (myself included) tend to Speak Up and provide at least "Initial Responses" that Share our Understanding and Experiences with the Software.  

That is our contribution to a "Friendly AP Community" here on the BYE/BYN Support Forum

 

No offense meant by any way. I just had a vivid flashback of times talking to my day job IT support guys I'm Sorry Rick, I really value all the support from all of you.

 

Anyway, Guylain, no mirror lock up enabled. I'll run some tests later today and let you know the results.

[admin]

Can you also make sure the camera is set to manual where bulb is allowed.

 

Can you take time value shutter images or is it just bulb that fails?

 

Do you have a lens on?

 

Regards,

[Herra_Kuulapaa]

Hi Guylain,

 

I sent you the complete log file with many different variations.

Yep, bulb is on, no lens, just a body cap. I suspect it to be related to true dark current mod. Although, my D5100 with same mod works just fine.

 

br,

HK

 

Ps. I ran some sequences with Digicamcontrol and that seems to work even tough the camera has a modified software.

[admin]

Digicamcontrol does not use the NikonSDK, it uses PTP protocol.  I wonder if the NikonSDK detects something and fails

[Herra_Kuulapaa]

Dark current hack >< Nikon SDK, hmmm, I could put my money on that..

[admin]

Yes, that could be it.  Let me look at your second set of log files.

[SXBB]

Hi Guys,

 

I'm also having the same problem when I capture on my D5100 with the True Dark Current enabled.  I just read on the Nikon Hacker site that the file format of the True Dark Current output is at this point incompatible with BYN.  Any progress on this?  It seems like a  really important feature to have to maximize image quality for astrophotography.

 

Thanks

 

SXBB

[admin]

There is nothing I can do with this mod. BYN gets the image form the Nikon SDK.

 

The issue is not BYN per say, the hack simply does not play nice with the Nikon SDK way of accessing the image, maybe it should... but then again maybe it can not.

 

What I do know is that if the Nikon SDK is unable to read the image for download then BYN will in turn is unable to download the image

 

As [er Herra's note above, using a serial cable for bulb may solve the issue.

 

Regards,

[s3igell]

@SXBB, @Herra - perhaps you should post to the Nikon Hacks Dev Team to ask them to Test / Ensure that their True Dark Current Hack is Compatible with the current NIKON SDK.

 

It would seem that you should place Responsibility for "Not Breaking The Standard SDK" onto those who are doing the Hacking...

[Herra_Kuulapaa]

Hi Guys,

 

I'm also having the same problem when I capture on my D5100 with the True Dark Current enabled.  I just read on the Nikon Hacker site that the file format of the True Dark Current output is at this point incompatible with BYN.  Any progress on this?  It seems like a  really important feature to have to maximize image quality for astrophotography.

 

Thanks

 

SXBB

Hi,

 

I did fully working exposures for two nights long with my D5100 monotec and a serial cable so that should be working also in your case.

 

Don't know what they can do with hack though. Idea of the dark current mod is to disable all the RAW processing and to be nonstandard in this sense, which then seems conflict with some SDK functions, more with D600 than D5100. But let's see..

 

br,

HK

[admin]

To force the use of a serial cable in BYN for cameras that can do bulb over USB you need to go to settings -> advance settings and check the force serial cable option.  Then select your serial cable in the capture plan.

 

Regards,

[s3igell]

Don't know what they can do with hack though. Idea of the dark current mod is to disable all the RAW processing and to be nonstandard in this sense, which then seems conflict with some SDK functions, more with D600 than D5100. But let's see..

 

Its quite likely that the "conflict with some SDK functions" is more a case of "collateral damage" than "needful conflict/breakage".  If the True Dark Current Hack actually works by "Skipping the Code that performs some amount of In-Camera Image Processing" then it's possible that the Hackers simply "skipped a bit too far ahead" in the Code and missed the execution of a piece of code critical to the SDK - such as raising the Notification of "Exposure Completed" or "Image Ready for Download" or some such.

If the True Dark Current Dev Team are made aware of their issue, its likely that they can improve their Hack such that it retains the bits of Code necessary for SDK support.

 

Otherwise, it appears that some of you have found a Work-Around in Mandatory Use of the Serial Cable Interface (a bit of extra Cabling and Cost and Complication that could be avoided if the TDC Hack were to be improved).

[nastyacidnoise]

Hi all.  I'm brand new to this forum, so I'll start by saying thanks Guylain for this fantastic software.  Thanks also to Herra for your adventurous spirit with DSLR modifications.  I am currently trailing BYN with my D600 and have run up against Herra's problem when the TDC hack is loaded.  Apologies if this has been solved for the D600 in another thread, but I couldn't find it if that's the case.  I see above that controlling the D5100 via 'forced serial' is a work around for that model, and the inference seems to be that the same can work with the D600.  Is there really a way to control the D600 via serial?  

[admin]

The hack is NOT supported because it does not play nice with the Nikon SDK.

[nastyacidnoise]

Thanks for the quick response Guylain.  It sounds like you may be tired of discussing this hack!  I understand that it is not and cannot be supported.  My question was regarding the work around that seems to work with the serial-controlled D5100; but no matter.  I'm happily evaluating BYN regardless.  I've found that I can still take single bulb exposures with the hack enabled if the files are saved to the camera only (I just have to exit BYN to download and view them on the PC).  So I will try framing/focusing, etc before loading the TDC hack, and then take individual exposures with manual dithering.  A bit more labor intensive, but it will be interesting to compare the results with those from a fully automated 'no TDC hack' work flow.

[admin]

The work around is not really meant for that for if it worked for one model it may work for another model.  The 'force serial cable' advance setting will ensure BYE/BYN uses the serial cable (instead of the regular usb cable) for bulb images... even if a camera is able to perform bulb over usb.

 

Regards,