Re: Some confusion concerning INDI device names
|
Hello, Please see section ?I will paraphrase here. The INDI Control Panel doesn't "know" what it's doing. Since INDI is a self-describing protocol, XEphem?can show all properties and allow you to interact with them in a generic fashion. You as the user know what a "Set" button does, but XEphem just dutifully sends the property as strings without knowing what is happening. But the Sky marker and GoTo control needs to be told exactly what properties to use for sending and receiving this information. This is done in the INDI Configuration panel. Here you enter the complete device.property.element tuple for each of the different situations, and enable the ones desired. In addition, you must enter scaling and offset values to convert to/from XEphem's internal coordinates (always radians) and the coordinates?expected by the telescope property (perhaps degrees, hours etc). You can determine the proper tuples by examining?the communications logged in the top section of the Control Panel but you must determine the scaling by knowing how your particular INDI telescope driver works. Hope this helps. Thanks for using XEphem and INDI. Elwood On Sun, Feb 6, 2022 at 10:01 AM M. Collins <aegle_observatory@...> wrote: ? I have an Ubuntu-20 system running INDIGO server connected to a Losmandy GM8/Gemini mount. INDIGO provides legacy support for INDI devices, and XEphem connects to the emulated server at localhost:7624 without any issues. I've found that I can run both the INDIGO and XEphem control panels simultaneously, and any actions initiated in one place are reported correctly in the other. In the XEphem panel, if I enter celestial coordinates then click SET, the mount will slew to that region of the sky as intended. It's clear that data are moving correctly in both directions between the emulated server and XEphem. |