BackyardNIKON v1 BETA 02b is ready for download

[admin]

YEAH... a step closer

 

A lot of testing was done since BETA02 in to order to find and fix the the nagging connection issue several of you have had using previous BETA's.  Most cases have been linked to either .net 3.5 or c++ 2010 redistributable missing on your computer.  BETA 02b will force the installation these package to ensure you no longer get connection issues.

 

*** DOWNLOAD BackyardNIKON v1 BETA 02b ***

http://www.binaryrivers.com/download/setup-BackyardNIKON-v100-BETA02b.exe

*** CHANGE LOG ***

- Camera connection issues; some camera sdk required .net 3.5 while others required c++ 2010 redistributable.  The installer now includes them.

- Significant performance improvement in the background worker process engine.

- Nikon D800E, D300 support added.

- Planetary video encoding using VirtualDub (see this thread)

- A new beta license key good for 60 days.

- Significant testing on XP, Vista, W7, and W8.

 

 

You can refer to this grid for a quick overview.

http://forum.otelescope.com/post/backyardnikon-v1-beta-progress-grid-6857530?pid=1282424740

 

Please report your findings using this thread.

 

As with other beta releases, the setup.exe is pre-packaged with its own tester license.

 

BETA 02b will install side-by-side to other betas, it will not overwrite BETA 02.

 

Thank you for all your support in getting this to a production quality.

 

Guylain & Chris.

 

[admin]

Bulb did not work - on either the D3s or D300. It immediately says ABORTING and nothing happens.

 

Just to confirm, I have both a USB cable and a DSUSB cable connected to the camera. The DSUSB cable is brand new, so I will investigate how to test the cable.

 

Ah... it -should- work with the DSUSB... BUT make sure you select DSUSB in the 'Cable Select' field in BackyardNIKON.  I suspect this is the issue according to you log file.... you did not select  DSUSB (I think).

 

Keep me posted,

 

Turns out the cable is not working on the DSUSB test prog - when I have that solved I will update you.

 

 

Okay, thanks for the feedback.

 

Regards,

[ChanduG]

 

 

The BackgroundWorker is started on demand... I have a feeling I should force it to start when BYE starts and this should resolve it.  I'll run more tests.

 

Thank you,

 

Hi Guylain,

I tried again today and had the same issues. Images do not show up in Image Center the first time I startup BYN. There is no background process "OTelescope.BackgroundWorker.Start" .  When I shut down BYN and restart, then I am able to see captured images in Image Center, and there is a OTelescope.BackgroundWorker.Start  process running. Log files are attached.

 

Thanks

Chandu

after_BYN_restart_logfile-[20140708-22h00m43s354]-backg...0]-2014-07-08.txt

first_attempt_logfile-[20140708-21h49m03s391]-backgroun...2]-2014-07-08.txt

first_attempt_logfile-[20140708-21h49m03s391]-backgroun...2]-2014-07-08.txt

[jerryyyyy]

Thanks, have the right Beta, appears to be same error.

 

Appears to be:  [CameraTakePictureOnMessageRecieved] ERROR - [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 455274580)

 

I found some code that uses this function and it seems to take the argument "5": 

kNkMAIDCommand_CapStart = 5,		// starts capability

 

 

If the function has been fed 33560, might explain the error.

 

 

logfile-[20140708-22h39m45s253]-[9336]-2014-07-08.txt

logfile-[20140708-22h40m25s785]-backgroundworker-[2188]-2014-07-08.txt

[admin]

Thanks, have the right Beta, appears to be same error.

 

Appears to be:  [CameraTakePictureOnMessageRecieved] ERROR - [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 455274580)

 

I found some code that uses this function and it seems to take the argument "5": 

kNkMAIDCommand_CapStart = 5,		// starts capability
 
 

If the function has been fed 33560, might explain the error.  

 

 

 

Thanks Jerry, I'll take a look.

[frits]

Hello,

 

I am testing BackyardNikon with my D90

Most of the options seem to work except Setting shutter time and iso have no effect on the live view.

I can change the dials but nothing happens in the live view window, still the same exposure.

When excessing liveview again shutter speed goes back to 2 sec and iso to Hi-1.0

 

Frits

[admin]

Hello,

 

I am testing BackyardNikon with my D90

Most of the options seem to work except Setting shutter time and iso have no effect on the live view.

I can change the dials but nothing happens in the live view window, still the same exposure.

When excessing liveview again shutter speed goes back to 2 sec and iso to Hi-1.0

 

Frits

Nikon cameras do not allow these settings to be modified while live view is active. Pause live view, change ISO, then resume live view. That should work. Regards,

[admin]

Hello,

 

I am testing BackyardNikon with my D90

Most of the options seem to work except Setting shutter time and iso have no effect on the live view.

I can change the dials but nothing happens in the live view window, still the same exposure.

When excessing liveview again shutter speed goes back to 2 sec and iso to Hi-1.0

 

Frits

Nikon cameras do not allow these settings to be modified while live view is active. Pause live view, change ISO, then resume live view. That should work. Regards,

If you want BYE to not change the speed and ISO automatically go to Settings and unchecked maximum aperture.... I know, bad name. Regards

[frits]

When pause the live view and changing the iso then back to live view then the iso still goes back to Hi-1.0

 

In normal live view you can holdown the little under/over expose button and turn the dial to change the exposure.

 

Frits

 

 

 

[willcarney]

My BYN is working again.  It will do everything except bulb.  The DSUB should control the bulb, it did before.  At least for now the program is closing and working somewhat.  William

[frits]

If you want BYN  to not change the speed and ISO automatically go to Settings and unchecked maximum aperture.... I know, bad name. Regards

 

Yes Thats working. Thanks

 

 

[admin]

If you want BYN  to not change the speed and ISO automatically go to Settings and unchecked maximum aperture.... I know, bad name. Regards

 

Yes Thats working. Thanks

 

 

Cool

 

 

[jerryyyyy]

Thanks, have the right Beta, appears to be same error.

 

Appears to be:  [CameraTakePictureOnMessageRecieved] ERROR - [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 455274580)

 

I found some code that uses this function and it seems to take the argument "5": 

kNkMAIDCommand_CapStart = 5,		// starts capability

 

 

If the function has been fed 33560, might explain the error.

 

 

 

Thanks Jerry, I'll take a look.

 

FYI:

 

https://github.com/dukus/digiCamControl

 

 

[admin]

Thanks, have the right Beta, appears to be same error.

 

Appears to be:  [CameraTakePictureOnMessageRecieved] ERROR - [kNkMAIDResult_ValueOutOfBounds] (kNkMAIDCommand_CapStart, 33560, kNkMAIDDataType_GenericPtr, 455274580)

 

I found some code that uses this function and it seems to take the argument "5": 

kNkMAIDCommand_CapStart = 5,		// starts capability
 
 

If the function has been fed 33560, might explain the error.  

 

 

 

Thanks Jerry, I'll take a look.

 

FYI:

 

https://github.com/dukus/digiCamControl

 

 

digiCamControl does not use the Nikon SDK, I do.

 

Regards,

 

 

 

[jstrickland]

Hi Guylain,

 

I've successfully tested all functions with both a D300S and D700 using a DSUSB.

 

So far I've just done some test shots on my dining room table.

 

I'm spending the next two weeks at a cottage in the Bruce Peninsula and will put BackyardNIKON through its paces with both cameras. I'll share some images when I'm back.

 

Thanks

 

Joe

[whwang]

Hi,

 

I tried 02b with D800 via USB.  Live view works fine.  Taking short exposures is also fine.

However, Bulb doesn't work at all.  I attach the log files.

 

Cheers,

Wei-Hao

logfile-[20140716-10h16m18s939]-[1340]-2014-07-16.txt

logfile-[20140716-10h18m24s735]-backgroundworker-[2568]-2014-07-16.txt

[admin]

Thank you Wei-Hao and Joe.

 

Regards,

[astro_gaz]

my licence has expired for this month, how do i get new licence guys?

[admin]

my licence has expired for this month, how do i get new licence guys?

 

Download the latest BETA 02b and -install- in a separate folder.  Your key will be good until September.

 

Regards,

[astro_gaz]

ah its the separate folder that fooled me thanks 

[admin]

ah its the separate folder that fooled me thanks 

 

Yeah, that is because the key is stored in the application configuration file and that file is folder specific in Windows.

 

Regards,

[astro_gaz]

cheers mate ive had it running perfectly on my D7100, just need a cable for my modded D5100 now then all good

[kalasinman]

Guy, have D5100. Got DUSB and cable from Shoestring. Frame and focus, live view, and test snap in frame and focus all work. Can change quality, ISO ok. Saves a pic ok, but won't run a programmed session. Fails and says busy. Gives serial cable required for bulb mode message. It's like the imaging section isn't connecting properly.

[admin]

Guy, have D5100. Got DUSB and cable from Shoestring. Frame and focus, live view, and test snap in frame and focus all work. Can change quality, ISO ok. Saves a pic ok, but won't run a programmed session. Fails and says busy. Gives serial cable required for bulb mode message. It's like the imaging section isn't connecting properly.

 

Yep... you need to select DSUSB in the cable select field

 

Regards,

[kalasinman]

That was it! seems to work perfect!  Thanks.

[SteveRosenow]

Hi, Guylain!

 

I have recently had a hard drive failure (fortunately I was able to recover most of my data, however I lost the boot sector on it)

Last week I ordered a replacement and it arrived a few days ago, and I've got BackyardNIKON reinstalled. I have since discovered a slight hitch in the giddyup.

There seems to be a slight problem with the current Beta 02B - it's not displaying the images captured in the application window, and seems to be writing them to the TEMP folder instead of the 'PLANS' folder. I've managed to successfully connect the D5100 and a client's MC-DC2_USB cable which I'll be shipping out this afternoon. The cable tests out fine, so there's no problem there. 

Unfortunately, there's also not much in the log files. I've attached the log file from the test session so you can have a look at it, and see if there's something amiss, or if my settings are skewered.

-Steve 

 

logfile-[20140717-13h18m29s762]-[4988]-2014-07-17.txt  

[admin]

Hi, Guylain!

 

I have recently had a hard drive failure (fortunately I was able to recover most of my data, however I lost the boot sector on it)

Last week I ordered a replacement and it arrived a few days ago, and I've got BackyardNIKON reinstalled. I have since discovered a slight hitch in the giddyup.

There seems to be a slight problem with the current Beta 02B - it's not displaying the images captured in the application window, and seems to be writing them to the TEMP folder instead of the 'PLANS' folder. I've managed to successfully connect the D5100 and a client's MC-DC2_USB cable which I'll be shipping out this afternoon. The cable tests out fine, so there's no problem there. 

Unfortunately, there's also not much in the log files. I've attached the log file from the test session so you can have a look at it, and see if there's something amiss, or if my settings are skewered.

 

-Steve 

 

 logfile-[20140717-13h18m29s762]-[4988]-2014-07-17.txt      

 

Hi Steve,
 

It is a known bug which I have fixed for the next BETA.
 

If you start BYN, then go to Settings, then close it, does it work after that?  
 

If yes this confirms the fix I did will solve your problem.
 

Keep me posted please,

[SteveRosenow]

Hi, Guylain!

 

I have recently had a hard drive failure (fortunately I was able to recover most of my data, however I lost the boot sector on it)

Last week I ordered a replacement and it arrived a few days ago, and I've got BackyardNIKON reinstalled. I have since discovered a slight hitch in the giddyup.

There seems to be a slight problem with the current Beta 02B - it's not displaying the images captured in the application window, and seems to be writing them to the TEMP folder instead of the 'PLANS' folder. I've managed to successfully connect the D5100 and a client's MC-DC2_USB cable which I'll be shipping out this afternoon. The cable tests out fine, so there's no problem there. 

Unfortunately, there's also not much in the log files. I've attached the log file from the test session so you can have a look at it, and see if there's something amiss, or if my settings are skewered.

 

-Steve 

 

 logfile-[20140717-13h18m29s762]-[4988]-2014-07-17.txt      

 

Hi Steve,

 

It is a known bug which I have fixed for the next BETA.

 

If you start BYN, then go to Settings, then close it, does it work after that?

 

If yes this confirms the fix I did will solve your problem.

 

Keep me posted please,

 

I went to 'Settings', then closed that dialog to no avail, however I just finished another build and in testing that, everything was working normally. 

 

At least so far!

 

-Steve

[admin]

Hi, Guylain!

 

I have recently had a hard drive failure (fortunately I was able to recover most of my data, however I lost the boot sector on it)

Last week I ordered a replacement and it arrived a few days ago, and I've got BackyardNIKON reinstalled. I have since discovered a slight hitch in the giddyup.

There seems to be a slight problem with the current Beta 02B - it's not displaying the images captured in the application window, and seems to be writing them to the TEMP folder instead of the 'PLANS' folder. I've managed to successfully connect the D5100 and a client's MC-DC2_USB cable which I'll be shipping out this afternoon. The cable tests out fine, so there's no problem there. 

Unfortunately, there's also not much in the log files. I've attached the log file from the test session so you can have a look at it, and see if there's something amiss, or if my settings are skewered.

 

-Steve 

 

 logfile-[20140717-13h18m29s762]-[4988]-2014-07-17.txt      

 

Hi Steve,
 

It is a known bug which I have fixed for the next BETA.
 

If you start BYN, then go to Settings, then close it, does it work after that?  
 

If yes this confirms the fix I did will solve your problem.
 

Keep me posted please,

 

I went to 'Settings', then closed that dialog to no avail, however I just finished another build and in testing that, everything was working normally. 

 

At least so far!

 

-Steve

 

I'll try to release BETA 02c this weekend.  I did change a few things related to this bug and it is no longer occurring in my dev environment.

 

Thank you,

 

 

[cdnpilot]

I had a bad cable - D300 works fine on bulb mode. I did some testing, and it appeared to work - downloaded the files and all was good. Did a test of 5 images.

 

Then an odd problem started - I was doing another test of 5 images at 30 seconds. It took the first image, then went through the waiting period with the counter going from 1 to 30 - then it just hung. It did not download, did not say it was donwloading and nothing showed up. I rebooted the machine, tried a preview shot - worked. Then I did as above with same result. D300 does not have a card in it - but sounds like I may have fat fingered something?

 

Kevin

[admin]

I had a bad cable - D300 works fine on bulb mode. I did some testing, and it appeared to work - downloaded the files and all was good. Did a test of 5 images.

 

Then an odd problem started - I was doing another test of 5 images at 30 seconds. It took the first image, then went through the waiting period with the counter going from 1 to 30 - then it just hung. It did not download, did not say it was donwloading and nothing showed up. I rebooted the machine, tried a preview shot - worked. Then I did as above with same result. D300 does not have a card in it - but sounds like I may have fat fingered something?

 

Kevin

 

How long/old is your regular USB cable (not the DSUSB)?

 

If the image is not downloading and BYN hangs this usually a bad USB cable (or too many devices connected on the UDB hub, if any) or a bad USB connection somewhere.  Do you have a short (about 6 feet) USB cable you can try?

 

Keep use posted,

 

Regards,