Hi
Perfect. I'm not using the API, I'm on a .NET Core application.
I already have all informations, so I only have to add a method to get the devices that correspond to an interface.
What are the values that can be found in DRIVER_INTERFACE (API doc is currently unavailable) ?
Here are the values I identified :
Telescope : 5,
Focuser : 8,
Filter : 16,
Camera : 22,
Dome : 32,
Weather : 32768
A bit strange, I would have expected the name of the interfaces or an enumeration going from 0 to N.
Julien
Read More...
Hi,
I want to integrate INDI in an existing software. I would like to know how I can get the available devices for a given type (e.g. : telescope, camera).
So far I managed to retrieve all the devices information with the command <getProperties version="1.7"/>. But how can get the list, for example, of all available cameras ? I haven't seen any information in the data returned by getProperties that let me know the type of device.
Regards
Julien
Read More...
knro wrote:
I have understood where was the problem. I'm on a RaspberryPi3 and the kstars-bleeding in version 5803.2569 for the arm architecture were already on the repository yesterday, but not the corresponding kstars-bleeding-data package, which has been upgraded today.
It works now
Read More...
Hi,
I try to install kstars-bleeding on Ubuntu MATE, but a dependency is missing :
kstars-bleeding:
Dépend : kstars-bleeding-data (>=5:16.04+r5803.2569~ubuntu16.04.1) mais 5:16.04+r5799.2560~ubuntu16.04.1 doit être installé
I followed this procedure : indilib.org/download/ubuntu.html
How to solve that ?
Julien
Read More...