BackyardNIKON v1 BETA 01d is ready for download.

[admin]

YEAH... a step closer

 

*** DOWNLOAD BackyardNIKON v1 BETA 01d ***

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

 

*** CHANGE LOG ***

- Change BULB sequence for D600, I'm hoping this will fix the bulb sequence not ending.

- Added Russian translation.

- New user guide, click the '?' icon in BackyardNIKON upper right corner.  It still needs attention but it will be 100% complete for production release.  The format is now a CHM help file instead of a PDF.

- Image loader bug when dragging images from Windows into imaging mode image area.

- Debug logging enhancements.

- A few other minor fixes here and there.

- A new beta license key good for another 30 days.

 

 

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 01d will install side-by-side to other betas, it will not overwrite BETA 01c.

 

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

 

Guylain & Chris.

[karambit27]

My images do not seem to be downloading to the laptop using a D5100. The laptop is running Windows XP and works fine with Backyard EOS V3.03. It downloads the first 3 or so then they keep queuing up until eventually the laptop locks up. There are several BinaryRivers.BackgroundWorker processes running (7+) using large amounts of CPU. Log attached.

 

 

 

Send me the background worker process logs as well.  This is new stuff and I need to find out why they are blocking.  These additional log files may help.

 

Guylain

 

Where are these located. I don't see anything labelled like that in the Logs folder just the log file I attached.

[admin]

My images do not seem to be downloading to the laptop using a D5100. The laptop is running Windows XP and works fine with Backyard EOS V3.03. It downloads the first 3 or so then they keep queuing up until eventually the laptop locks up. There are several BinaryRivers.BackgroundWorker processes running (7+) using large amounts of CPU. Log attached.

 

 

 

Send me the background worker process logs as well.  This is new stuff and I need to find out why they are blocking.  These additional log files may help.

 

Guylain

 

Where are these located. I don't see anything labelled like that in the Logs folder just the log file I attached.

 

They are in the same BackyardTEMP\logs folder

 

[karambit27]

There are not any files like that in the BackyardTEMP/Logs folder only ones like the one I attached.

[admin]

Looks like there is a bug trying to build a path.

 

2014-05-21 21:07:05,384 [36] ERROR - Error opening arg file C:\Documents

2014-05-21 21:07:05,384 [8] ERROR - File not found: and

2014-05-21 21:07:05,384 [8] ERROR - File not found: Settings/phil/My

2014-05-21 21:07:05,384 [8] ERROR - File not found: Documents/My

2014-05-21 21:07:05,384 [8] ERROR - File not found: Pictures/BackyardTEMP/exif_args_0ff2faa2-1b61-4066-864c-7850f3806335.txt

 

This should by one line containing the entire path, instead it seams to split it when a space is present <_>

 

I'll try to reproduce.

 

In the meantime, if you change your BackyardTEMP folder to c:\backyatdTEMP, restart BackyardNIKON.  Do you still have the same issue?

 

Guylain

[admin]

Okay, something went very wrong.

 

 

2014-05-21 22:03:34,900 [backgroundWorker(MessageSendQueue)] ERROR -    at System.IO.Pipes.NamedPipeClientStream.Connect(Int32 timeout)

   at BinaryRivers.BackgroundWorker.Client.PipeClient`1.StartServer()

 

 

Can you reproduce this if your close and restart BackyardNIKON?

[karambit27]

Yeah I shutdown and restarted the laptop as well as BackyardNIKON. It seems to happen anytime I try and do more than a single exposure. I have connected the camera to a separate newer laptop running Windows 7 and it appears to be working fine so far. The laptop running Windows XP would start acting up after the second or third exposure. I am on exposure 10 on the Win 7 laptop with no issues and there is just a BackgroundWorker.Start.exe process and BackyardNIKON.Start.Camera1.exe process whereas on the Windows XP laptop I had several BackgroundWorker processes that kept spawning until it locked up. I am however not seeing any log files containing background in the name on the Win 7 laptop like you posted earlier. Is this normal?

[admin]

Yeah I shutdown and restarted the laptop as well as BackyardNIKON. It seems to happen anytime I try and do more than a single exposure. I have connected the camera to a separate newer laptop running Windows 7 and it appears to be working fine so far. The laptop running Windows XP would start acting up after the second or third exposure. I am on exposure 10 on the Win 7 laptop with no issues and there is just a BackgroundWorker.Start.exe process and BackyardNIKON.Start.Camera1.exe process whereas on the Windows XP laptop I had several BackgroundWorker processes that kept spawning until it locked up. I am however not seeing any log files containing background in the name on the Win 7 laptop like you posted earlier. Is this normal?

 

Your W7 laptop appears to be running normally.

 

Your XP not so much.  You can have up to 3 background worker thread for each instance of BackyardNIKON; one for high priority tasks, one for normal priority tasks, and one for lower priority tasks.  Each worker thread is suppose to leave a separate log file.

 

The worker threads are automatic, they start when they have a task to run.  According to your log files on XP the receiving thread in the app itself failed... meaning it could no longer receive messages from any of the background worker, usually a success message or an error message.  Without this receiver the application is never notified when a background task is complete.  In your case the user interface kept waiting for a response but it never came. 

 

If this is a one shot deal on one computer only I'm not too worried, but it is still cause for concern.  This is the new background working engine I have implemented in BackyardEOS v3.1 (not released yet) so if there is a general bug I need to address it pronto... but because I can not recreate the issue at my end it is difficult to debug <_>

 

 

[karambit27]

I will try to do some more testing tonight if I have time and let you know. If there is anything you want me to try specifically let me know.

[whwang]

Hi,

 

I am using a different computer to connect to Nikon D800.

(The same D800 that was previously OK for everything, except for continuous Bulb shooting.)

This time, BYN cannot see D800.

 

Here is some more information.

computer: MacBook Air (previously it was MacBook Pro)

OS: Win7 running under MacOS with Parallel Desktop (same as the previous one)

connection: USB3.0

 

The same camera and Win7 works fine under digicamcontrol.  So I suppose the 

problem has something to do with BYN 01d.

 

The log file is attached.

 

Cheers,

Wei-Hao

logfile-[20140523-14h03m02s332]-[1428]-2014-05-23.txt

[Shelster1973]

First post and want to say a mahoosive big thanksyou for getting this off the ground and running.

 

Was pulling my hair out trying to get control over my Nikon and felt like as a Nikon owner I was being classed as a second class citizen for not using a Canon

 

Am new to astrophotography and astronomy in general, so have very little experience to draw on.

 

Only issue I have seen so far is that it can take several attempts to connect to my D7100.  Have had this on two seperate computers, 1 desktop crazy uber machine and the other a low end laptop, both of which are running different OS's (W8.1 64 and Vista 32 respectively)

 

Also have noticed that a sequence I was running last night (20 x 20s lights) dropped of and stopped, but not sure if that was down to the laptop going into screensaver mode and closing ports.

 

Will report back anything else I find as I use it more and once again a very big than you

[admin]

First post and want to say a mahoosive big thanksyou for getting this off the ground and running.

 

Was pulling my hair out trying to get control over my Nikon and felt like as a Nikon owner I was being classed as a second class citizen for not using a Canon

 

Am new to astrophotography and astronomy in general, so have very little experience to draw on.

 

Only issue I have seen so far is that it can take several attempts to connect to my D7100.  Have had this on two seperate computers, 1 desktop crazy uber machine and the other a low end laptop, both of which are running different OS's (W8.1 64 and Vista 32 respectively)

 

Also have noticed that a sequence I was running last night (20 x 20s lights) dropped of and stopped, but not sure if that was down to the laptop going into screensaver mode and closing ports.

 

Will report back anything else I find as I use it more and once again a very big than you

 

Remove your SD card (or remove images on it) and try again.  The Nikon SDK performs a full image index on the cord before connecting.  If you have hundreds of pictures on your SD card this may take a while.

 

Does this make sense?

[Shelster1973]

Remove your SD card (or remove images on it) and try again.  The Nikon SDK performs a full image index on the cord before connecting.  If you have hundreds of pictures on your SD card this may take a while.

 

Does this make sense?

 

Makes perfect sense.  WIll do my shooting with a 'Clean' card in in the future.

 

Am guessing size of card wil not matter as all files are transfered directly to the host computer for storage (if my understanding from last night is correct???)

[admin]

Remove your SD card (or remove images on it) and try again.  The Nikon SDK performs a full image index on the cord before connecting.  If you have hundreds of pictures on your SD card this may take a while.

 

Does this make sense?

 

Makes perfect sense.  WIll do my shooting with a 'Clean' card in in the future.

 

Am guessing size of card wil not matter as all files are transfered directly to the host computer for storage (if my understanding from last night is correct???)

 

That is correct.

[karambit27]

Will this support 3rd party programs like Astrotortilla and PHD from the start or will you have to incorporate those later?

[admin]

Will this support 3rd party programs like Astrotortilla and PHD from the start or will you have to incorporate those later?

 

It's already there... and working just as BackyardEOS is.

 

In AT choose BackyardEOS for camera connection, I kept the same communication interface so it is a 100% match.

 

Dithering via PHD works.

 

BackyardNIKON -is- the same as BackyardEOS except that it connects to Nikon cameras instead of Canon cameras.

 

 

[karambit27]

Will this support 3rd party programs like Astrotortilla and PHD from the start or will you have to incorporate those later?

 

It's already there... and working just as BackyardEOS is.

 

In AT choose BackyardEOS for camera connection, I kept the same communication interface so it is a 100% match.

 

Dithering via PHD works.

 

BackyardNIKON -is- the same as BackyardEOS except that it connects to Nikon cameras instead of Canon cameras.

 

 

Excellent that is what I figured just wanted confirmation

[radman8]

Hi.  I'm having problems connecting to PHD2.  I have double checked that "Enable Server" is checked in PHD2.   BYN is reporting that the "PHD connection failed".  I've included a screen grab.  As you can see, I haven't touched the default settings for dithering.  Any ideas?  Thanks

 

P.S. Forgot to mention that I'm running PHD2 in simulation mode tonight since it's cloudy and I can't guide on a real star.  

 

 

 

[radman8]

I'm also running into a bug that crashes BYN but inconsistently when doing the following:

 

(1) Start BYN

(2) Connect to D7000 (through a regular USB cable)

(3) Physically pressing the shutter release on the camera. 

 

Thanks

[admin]

I'm also running into a bug that crashes BYN but inconsistently when doing the following:

 

(1) Start BYN

(2) Connect to D7000 (through a regular USB cable)

(3) Physically pressing the shutter release on the camera. 

 

Thanks

Did you accept the firewall warning in PHD when you set the enable server settings in PHD? Guylain.

[radman8]

I'm also running into a bug that crashes BYN but inconsistently when doing the following:

 

(1) Start BYN

(2) Connect to D7000 (through a regular USB cable)

(3) Physically pressing the shutter release on the camera. 

 

Thanks

Did you accept the firewall warning in PHD when you set the enable server settings in PHD? Guylain.

 

 

Hi, yes, I believe so.  Here is a screen shot of the firewall settings.  It looks like it's in order...

 

 

 

[admin]

I'm also running into a bug that crashes BYN but inconsistently when doing the following:

 

(1) Start BYN

(2) Connect to D7000 (through a regular USB cable)

(3) Physically pressing the shutter release on the camera. 

 

Thanks

Did you accept the firewall warning in PHD when you set the enable server settings in PHD? Guylain.

 

 

Hi, yes, I believe so.  Here is a screen shot of the firewall settings.  It looks like it's in order...

 

Okay, but why are you pressing the shutter release manually?  I mean it should work (I'll run a few more tests pressing the shutter release myself, but this is not necessary for PHD dithering.

 

Can you clarify the issue?  Is it that it crashes when you press the shutter release OR is it that PHD dither not working... or both.

 

Regards,

[radman8]

I'm also running into a bug that crashes BYN but inconsistently when doing the following:

 

(1) Start BYN

(2) Connect to D7000 (through a regular USB cable)

(3) Physically pressing the shutter release on the camera. 

 

Thanks

Did you accept the firewall warning in PHD when you set the enable server settings in PHD? Guylain.

 

 

Hi, yes, I believe so.  Here is a screen shot of the firewall settings.  It looks like it's in order...

 

Okay, but why are you pressing the shutter release manually?  I mean it should work (I'll run a few more tests pressing the shutter release myself, but this is not necessary for PHD dithering.

 

Can you clarify the issue?  Is it that it crashes when you press the shutter release OR is it that PHD dither not working... or both.

 

Regards,

 

 

Hi, I'm using an external intervalometer to release the shutter.  I'm on a budget and don't want to purchase the special USB cable required to connect the D7000 to get exposures longer than 30"... for the time being at least.   The intervalometer allows me to shoot 5 or 10m subs, etc. but I think the inability to dither using PHD and the inconsistent crashing of BYN when I release the shutter are probably two different things.

 

Is there anything I can do to get dithering working?  Are there any settings that I may have overlooked on my end?

 

Many thanks

[admin]

I'm also running into a bug that crashes BYN but inconsistently when doing the following:

 

(1) Start BYN

(2) Connect to D7000 (through a regular USB cable)

(3) Physically pressing the shutter release on the camera. 

 

Thanks

Did you accept the firewall warning in PHD when you set the enable server settings in PHD? Guylain.

 

 

Hi, yes, I believe so.  Here is a screen shot of the firewall settings.  It looks like it's in order...

 

Okay, but why are you pressing the shutter release manually?  I mean it should work (I'll run a few more tests pressing the shutter release myself, but this is not necessary for PHD dithering.

 

Can you clarify the issue?  Is it that it crashes when you press the shutter release OR is it that PHD dither not working... or both.

 

Regards,

 

 

Hi, I'm using an external intervalometer to release the shutter.  I'm on a budget and don't want to purchase the special USB cable required to connect the D7000 to get exposures longer than 30"... for the time being at least.   The intervalometer allows me to shoot 5 or 10m subs, etc. but I think the inability to dither using PHD and the inconsistent crashing of BYN when I release the shutter are probably two different things.

 

Is there anything I can do to get dithering working?  Are there any settings that I may have overlooked on my end?

 

Many thanks

 

Dithering will never work with an intervalometer.  Dithering is part of the running active session plan and since you are using an intervalometer to take the exposures the capture plan is not running therefore dithering and any other benefits resulting from a capture plan are not executed.

 

As for taking images with an intervalometer it should work.  Please send me your log files at support@binaryrivers.com and I'll take a look.  Log files are located in "My Pictures\BackyardTEMP\logs"

 

Regards,