Jump to content

Canada's top-tier Telescopes & Accessories

Search the Community

Showing results for tags 'api'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Application Support
    • General
    • BackyardEOS
    • BackyardNIKON
    • How-to's
    • Feature Suggestion Box
  • Soutien français (French support)
    • BackyardEOS et BackyardNIKON (français)

Product Groups

  • BackyardEOS
  • BackyardNIKON
  • Shop by Category
    • Telescopes
    • Mounts & Tripods
    • Cameras & OAG
    • Filters & Filter Wheels
    • Eyepieces & Diagonals
    • Flatteners / Reducers & Barlows
    • Focusers
    • Dew Shields & Controllers
    • Bahtinov Masks
    • Solar Astronomy
    • Softwares
    • Weather Stations
    • Cases & Carrying Bags
  • Shop by Brand
  • Outlet


  • BackyardEOS
  • BackyardNIKON
  • BackyardRED
  • API & Documentation
  • Pre-releases

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 4 results

  1. On Astroman133's suggestion of a more detailed query regarding a post I made on the BYE forum I am asking if it is possible to increase the surface area of the BYE API by providing access to more data and functions of the program. I have quite a specific reason which may prove too specific to be of general use so I understand if it is not possible/practical to implement and have thought of a "handraulic" workaround should this prove to be the case. Anyway, here's the situation... I am writing a small piece of software which attempts to codify Roger Clark's thoughts on exposure by calculating the ideal parameters for each exposure in a capture plan and produce the capture plan as well This will allow me to calculate capture parameters easily on-the-fly for changes in lenses, focal length, aperture, f-stop and ambient light pollution while shooting The software is currently in scoping phase (excuse the pun :-) ) I need access to the camera parameters for at least focal length, aperture, f-stop and I suspect I will need the histogram from test shots requested by the software as well (GET calls to BYE, I believe the EOS Utility dll allows the histogram to be provided but not sure on this point) Once linked to BYE I would like my software to be able to react to changes made on camera which would no doubt be captured by the EOS Utility dll which I'm sure is the underpinning of the BYE camera access (EVENTS fired by BYE) Once a capture plan is created I would like to be able to export this seamlessly to BYE (access to RESET, LOAD and SAVE functions in BYE) I don'y know if any of this is possible or practical but I would love to be able to create a seamless workflow between my concept and BYE, one which should optimize image capture. In any event I shall be producing the software and will design it in such a way that should the necessary changes be made to BYE I will be in a position to take advantage. Let me know your thoughts Regards Ian
  2. Hi All I am writing a small application to calculate the required exposure set needed for any given shot and would like to integrate its inputs and outputs with BYE. I had a couple of questions... 1. Does the API give me access to camera parameters such as current focal length, aperture, shutter speed etc such that changes to those parameters are flagged via events or some such method? 2. On calculating/recalculating the exposure set can I set/reset the shot list in BYE? Thanks in advance Regards Ian
  3. Version 2.0


    API Documentation, including sample commands on how to use the API to allow external application to use BackyardEOS or BackyardNIKON for taking pictures. You need the PREMIUM Edition of BackyardEOS or BackyardNIKON to use this API.


  4. Version 2.0


    A sample application calling most of the API functions demonstrating its ease of use. You need the PREMIUM Edition of BackyardEOS or BackyardNIKON to use this API.


  • 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