I am OK on C and C++ but I am an absolute and complete newbie in this environment. 
I want to write a simple client to control a CCD camera on the 'scope.
I am more than happy to base it on the tutorial examples given.
I want to run the client on a Raspberry Pi.
I can successfully compile and run the tutorial examples, on the RPi, but I am struggling at the (rather elementary) point of trying to compile my edited versions of those example cpp files.
Two specific questions.
1. I am currently using the (most helpful) steps described in the web site to compile the whole tutorial set on the RPi in one go, but I am not confident of how to compile just the edited code I have written. It offends me to take the easy way out and do them all every time.
2. Very specifically, to make the tutorials work with my camera (QHY8L) rather than the simulated CCD, where do I look for the right word/name/description to put into the tutorial to make it work with the real camera.  I feel there must be a list of possible names but I have not stumbled up on it. I have tried substituting "QHY CCD" for "Simulated CCD" but that doesn't seem to result in code that works.

Thanks in advance for any help to get this newbie off the starting blocks..
Bev
COAA

 

Welcome to INDI forum.

To get the <strong>existing</strong> properties, simply run indi_getprop and you'll get the device.property.element for whatever is currently connected now to INDI server.

Regarding the client code, I should probably create one standalone example outside of INDI to illustrate how this is done. I'll try to work on it soon.

Hi Jasem

Many thanks fo r the quick reply. Unfortunately, "indi_prop" is not found anywhere on the RPi. I have installed KStars and all the indi development suite but a search for "indi_prop" finds nothing.

Sorry I am so far back!

Regards
Bev
COAA

Sorry my bad it was a typo, it's indi_getprop

Thanks Jasem,

That gets me a little further but "indi_getprop" returns "Connection refused" whatever I try.


Regards
Bev

is INDI server already running? if yes, at port 7624? You can test, run indiserver

indiserver -v indi_simulator_telescope

then from another terminal, indi_getprop

Many thanks for that clarification.
However, if I start the server with that command, indi_getprop only shows me the telescope simulator proprties.
Similarly, if I start the server with, say, tutorial_three, I see the properties of that simulated device.

I had expected, wrongly it would seem, that when the QHY8L was connected, physically, that an appropriate driver would be loaded automatically and would appear in indi_getprop.
Clearly that doesn't happen so it seems that I need to invoke the QHY8L driver by some means that I do not understand.

Sorry to be so helpless!

Regards
Bev

No, indiserver needs to be started. People usually do this from a client (e.g. Ekos), or you can do it from the console indiserver -v indi_qhy_ccd

Thanks Jasem,

You help is very much appreciated. I am making some progress now.

Regards
Bev
COAA