Jump to content

Canada's top-tier Telescopes & Accessories


  • Content Count

  • Joined

  • Days Won


Posts posted by admin

  1. Using 2 cameras with BackyardEOS is a Premium Edition feature.

    If you have BackyardEOS 3.1.5 or BackyardNIKON 1.0.3 Premium Editions this feature is a built-in; you do not need anything else.  If you have the Classic Edition or an earlier version you can still achieve dual camera support.  Please read below if this is your case.  


    In order to use 2 cameras with BackyardEOS you need to start 2 instances, each camera will connect to its own BackyardEOS instance.  Using this method ensures that each instance will have its own application configuration separate from one another.

    This is not possible with BackyardNIKON as the Nikon SDK does not allow for 2 cameras to be connected/operated at the same time.

    Setting it up...

    1. Go to the BackyardEOS install folder and create a shortcut of the ...camera2.exe executable on your desktop.
    2. Start this camera2.exe and enter your license key.


    Now you have the standard BackyardEOS icon and a second BackyardEOS icon pointing to the camera2.exe; use this second for the second camera.

    Connecting both cameras...


    1. Start BackyardEOS instance 1 using the regular BackyardEOS icon on your desktop.
    2. Start BackyardEOS instance 2 using the icon created earlier which points to the camera2.exe executable file.
    3. Connect both cameras to your computer and turn them on.
    4. Using each instance of BackyardEOS connect your camera as you normally would.
    5. BackyardEOS will display a window with both cameras connected to your computer for you to choose from; select one camera using BackyardEOS instance 1 and select the other camera using BackyardEOS instance 2.

    You now are ready to use 2 cameras :)

    The implementation does have it's limitation however.  You can not dither for instance if you have both cameras mounted on the same mount.  This is because both instances are insular from one another, meaning one is unaware of the other one.  So if instance 1 is dithering instance 2 has no clue that this is occurring and instance 2 will continue imaging just the same.

    Hope this helps,


  2. Hi Guylain,

    Thanks, yes, that makes sense. Like you said this is not an issue when one is shooting lights or darks - I only found out about this when I was shooting bias frames and that too when the queue reached 3 and the program does not proceed with the next exposure until one of the files is processed. 


    I guess one solution would be for me to upgrade my netbook :). Or I could use a different program to acquire bias frames, since I have not seen this behavior elsewhere. But thanks for the detailed explanation, I will try the processor affinity option. 


    Hi there,


    BackyardNIKON should absolutely proceed to the next exposure regardless of how many images are in the queue... if not this is a bug.


    Can you please confirm that that is the case, or not?  With and without processor affinity.  Remember that you must restart BYN when you change the processor affinity setting for it to take effect.



  3. The How-to forum is a place for moderators and admins to post common and useful how-to do this and and how-to do that using either BackyardEOS or BackyardNIKON.

    As a member of O'Telescope forums you can post replies to existing how-to's to further contribute to its content but you can not create new how-to's.  The reason for this restriction is because we want to create a simple yet very informative set of knowledge articles that are extremely easy to follow for the beginner, yet powerful enough to satisfy the seasoned astrophotograper.

    If you have an idea for the How-to forum please submit it to support@otelescope.com.

    Thank you

  4. Logs sent.


    Pretty much the same situation last night. No crash. I guess I may have turned off PHD2 before a complete (or multiple complete) images were taken however.




    Thanks for reporting back.





  5. Hi,

    Here are the logs from last evening. Let me know if there is a specific action you'd like me to execute and capture a log. Thanks for looking into this.



    Okay, so I have looked at your log files and now know what is happening :)


    1) The 100% utilization is not a major issue because it is the background worker process that was using it... and it runs in a very low priority thread... meaning that if your computers needs more power it will take it.  This is okay.


    2) The 100% utilization is caused by reading the enormous .NEF file.  This takes about 28 seconds on average on your computer according to the log files.  I'm using GdPicture, a commercial library, to read the NEF files.  It is a bit slow, okay very slow, on your computer for sure.  In comparison it takes about 4 seconds on my computer.


    This is typically not an issue doing long exposure photography because we take pictures > 60 seconds 99% of the time.  Which means all that work is done in a very low priority thread while the UI is running in a normal/high priority thread taking the next picture.


    I see you have selected NEF only image format.  If you select NEF + JPG you will get the impression that things are going much, much faster.  This is because when a JPG is taken I actually load the JPG immediately after download and display it right then and now... then I send the NEF file to the background worker to process it.


    To confirm this, take a preview picture (which is JPG only) and notice how faster it is.  The same can be said for snapping a picture in Frame&Focus.


    I will continue to look at GdPicture to see if there is a parameter somewhere that I can use to make it faster.  But like I said, it's all done in a low priority background thread and if you take NEF + JPG images you will get the illusion that everything is much faster.


    Does this make sense?



    EDIT: I see you have a dual core computer.  To mitigate the 100% CPU utilization a little bit, you can go to Settings -> Advance Settings and enable the "Processor Affinity" option, then restart BYE.  This will instruct BYE user interface to run on a single CPU core and force the the Background Worker Process to run on another CPU core.



  6. Anyway, was looking at the Beta 02 status grid and footnote *3 for the D800 caught my eye.  So I fired up Beta02 and in the Capture Plan Center punched into Line 1, Exposures=4, Bulb, Aperture=4, Duration=1, ISO 100, and Pause=1.  Clicked Start Capture and got 4 images of my den just fine.  Then I add the same into Line2 and shot again.  Got 8 new images of my den just fine.


    Do I need a more complicated exposure or shooting plan to make this bug show up?


    That footnote should not apply to you since you are using a serial cable for BULB with your D800E.


    I will update the grid.


    So I think you are good to go as-is :)





  7. Hey Guylain, OK, much joy here!  Your troubleshooting guide said remove any hubs - so that's why I thought I was screwed.  Anyway, I had one of these as part of my SP2 travel kit:




    Connected everything up and, Houston, I have a connection.  :)  The connection log says you need the following information:


    Device (D800E) Module (Type0006) found!


    Anything else you need or is there anything you want me to test out?  Nice to know I'm the first D800E, finally 1st in something  ;)


    BTW, did NOT install the C++ package




    The C++ is only for some models I believe.


    No hub... in your case it's your only alternative given you only have 1 port on your computer.  Just try to not overload it with unnecessary devices.


    I'll use the information above to make sure I register all supported functions for the D800E.  I may need to send you a new download link next week.





  8. BYEOS crashed on me last night. Is there a log file or something I should send? I looked in the program folder, my documents, and AppData and didn't see anything.


    It was a C++ runtime error. I forgot to capture a screen cap of the dialog but it was generic.


    BYEOS was running (unattended) a capture plan and dithering PHD2. The DSO being tracked went behind a tree and PHD2 lost its guide star. Could that cause a crash?


    Windows 7 64 bit. BYEOS current pro version. PHD2 2.2.2a.


    AstroTotilla was also connected to BYEOS but wasn't in use at the time of the crash.


    FYI I'm running everything through a 10M active USB 2.0 cable. It's been fine so far. I can do planetary or live view at the same time I'm doing PHD2 guiding, so I'm not perceiving a cable bandwidth/latency issue. I've imaged with that setup 4 or 5 times so far without any problems.




    C++ runtime error... BackyardEOS is a .net application, not C++ so the error must have originated elsewhere.  Could be inside the Canon SDK which I don't control.


    Send me the log files at support@binaryrivers.com.  They are in "My Document\BackyardTEMP\logs".



  9. Well, I'm screwed.  I'm running a Surface Pro 2 with only 1 USB 3.0 port.  If I have to use 2 USB cables and I can't use a USB hub, I'm dead in the water if I want to use my SP2 (and I do since it's my travel computer).  Thanks




    The DSUSB cable is a serial cable, nothing more... and that cable connects to the SHUTTER port on your camera, not the normal USB connector port.  It is meant to open and close the shutter only... and that is the only thing is was design for and the only thing it can do.


    Get yourself a 2.0 USB powered hub and you will be fine... something like this :)





  10. Yikes, no.  I've not seen anywhere in my hours of reading where both cables are needed.  Kind of a surprise actually as it means the 10' extension I got for the DSUSB is useless.  OK, I'll try it and the C++ package and report back.  Thanks




    Then that is the root cause.


    The DSUSB cable is ONLY for bulb.  The camera USB cable is for everything else.


    You are the first one connecting a D800E :)





  11. Hi Guylain, 


    Just downloaded and installed Beta02 but having basic "Camera not found" problem.  Using Nikon D800E and Shoestring Astronomy DSUSB.  Checked everything and am stumped.  Here's the checklist:


    1). Camera is on

    2). Camera mode set to Manual, focus to Manual

    3). Shutter speed set to Bulb

    4). Connection with D800 via DSUSB checked with DSUSBcheck.exe and all functions confirmed.

    5). Battery is full

    6). Camera firmware is up-to-date with A1.10/B1.10

    7)  Using Windows 8.1 Pro


    Hmm, am I missing something really basic?  Do I need to install a license key?  Thanks for your help!




    Hi Bob, me again.


    I see no mention in your steps above regarding the regular camera supplied USB cable.  You are connecting both cables, right?  The camera supplied USB cable -AND- the DSUSB cable?





  12. Hi Guylain,

    I tested the BETA 02 on my D5100 last night and ran into one issue - once an exposure is completed (regardless of exposure length), the image goes into a processing "queue" and for the image to be downloaded and displayed from the queue it takes almost a full minute. During this time my processor utilization is at 100%. I use an old netbook for image capture and this might be part of the problem, but I never had performance issues with BYE (in fact I dont think BYE even has a queing feature). Is there any option I can turn off to make this go faster? Yesterday, it took more than 10 mins to capture 20 bias frames. 




    Would you happen to have AVG anti-virus or McAfee BTW?


    This looks like the anti-virus software acting up.  Disable your antivirus and try again to confirm (or not) that this issue is your antivirus software.





  13. This is the correct formula, and it IS a "one size fits all" equation that directly accounts for the Pixel Size of the Camera...

    (see the "pixel size [um]" factor in the center of the equation...)


    And, why are you taking me to task ??  I suggested that the user can surely do this simple math with Calc, as well as anything which Guylain might offer to add to BYE...




    Sorry I was not trying to take you to task. I was just trying to use the formula as reference.

    and show its not as easy to program something with variable inputs (and this formula has 2) over the large audience that this program has, as some may think.



    I already know which camera is connected so I already have the pixel size.  The user would only need to supply focal length of their optical train.





  14. Hi,


    The problem on D800 seems even larger in beta 02.

    Previously Bulb is fine, but it doesn't take multiple Bulbs in beta 01c and 01d.

    (D610 seems to have this problem too.)

    Now in beta 02, even just taking one bulb is not possible.


    The logs are attached.





    Thanks Wei-Hao.


    I have not addressed any bulb issues for the D610 and D800 in BETA 02...  In fact there is no difference between BETA 01d and BETA 02 for these models.  Which has me wonder why you get to different behavior <_>





  15. My T3 is also not connecting. Maybe wrong communication setting, but where in the camera do I find those settings?




    Please try connecting your T3 with EOS Utility.  If it does not work the issue is with the camera or usb cable.  If is does work the issue is with BackyardEOS.


    I have over 1,000 users with a T3 and this model has been tried and tested.





  16. Planetary AVI recording can be an intense and CPU hungry process.

    The native planetary recording in BackyardEOS and BackyardNIKON uses a commercial encoder to create the AVI movie files.  However, the encoder may prove to be to much on some computer configuration and in some cases may not even complete the video encoding <_<

    BackyardEOS and BackyardNIKON both have a built-in alternative which takes less CPU.  This alternative is VirtualDub

    VirtualDub is free!

    I'm not able to -package- VirtualDub part of the BackyardEOS and BackyardNIKON installers due to it's GNU General Public License.  However, if you download VirtualDub yourself and follow the instructions below, the planetary recording feature in both BackyardEOS and BackyardNIKON will use VirtualDub instead of its native commercial encoder.

    1) Download VirtualDub 32-bits (x86).
    2) Open the VirtualDub ZIP folder.
    3) Copy VirtualDub.exe and VDub.exe files in your BackyardTEMP download folder.  The default location is "My Pictures\BackyardTEMP\download\".
    4) That is it.  You are now using VirtualDub to encode your AVI.

    Hope this helps,

  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use