I've spent some time recently trying to perform some basic telescope mount control using XEphem, INDI lib and the LX 200 Classic driver. The mount is a Losmandy G-11 with a Gemini I controller. I encountered no difficulties building v0.9.7 under Debian "wheezy". After a lot of experimentation, I've made some progress but can't get everything to work correctly. What I'm primarily struggling with, I think, is a lack of documentation related to the driver. Despite my best efforts, I've been unable to find any documentation which describes the properties supported by this driver. In private communication with Elwood Downey, it appears that at least one reported error is likely due to an attempt to modify a read-only property. Even for the properties which appear to have been configured correctly, it was a matter of trial and error (combined with a lot of on-line search effort) to guess the correct names.
Is there a repository for documentation which lists the properties supported by each driver, the range of value which apply to each property, and whether a property is writable? If not, is there someone who could help me identify these characteristics for the LX200 drivers? Apologies in advance if there is such documentation available and I've just not been able to find it -- I'm generally pretty good at finding information on the 'net, but in this case I've just not been at all successful.
No, there is no user-level documentation for LX200 Classic. You can find some documentation for some drivers in the Devices section of the website. But there is no detailed description for properties, their ranges,...etc. Can you please let us know what kind of problems are you exactly facing with your setup? Usually, depending on the client, it's simply a matter of clicking of an object and selecting "Track". But if you want to use INDI scripting, then yes, you have to know the property details.
Most properties are self-explanatory, and you can get all the details you want if you run INDI server with -vvv, as it will display the whole XML output.
Excellent - this has been very helpful. I'm now able to configure XEphem so that everything appears to be working correctly. I'll know for sure when I can run some tests under a dark sky.
I have a couple of additional questions:
1. I'm using "EQUATORIAL_EOD_COORD.RA" and "EQUATORIAL_EOD_COORD.DEC" as the properties for writing and reading coordinates to the driver. I believe these are correct (assuming EOD stands for Equinox Of Date). Is there a corresponding set of properties for J2000?
2. What is the purpose of the "ON_COORD_SET" properties? All three options, "Track", "Slew" and "Sync" are reported as False in the driver diagnostic output. The mount continues to track after slewing to an object, so I don't believe there are any issues, however I'd like to be sure I'm not missing something.
Thanks for the informative and prompt reply. After several hours of unsuccessful effort last weekend, I was able to get everything working within half an hour today.