Look on way of indilib installation on fresh Ubuntu 16.04 (64 bit):
cd ~
cd /usr/bin
ls indi*

There are no links in that URL, they're commands you run to download and install the package. As it says, only packages for Ubuntu 15.10 and above. Also, the client never requests a telescope position, it is sent by the driver (property EQUATORIAL_EOD_COORD) via the server to the client. There is no request/response mechanism in INDI.

You can get latest code and build it yourself as well on INDI GitHub

Okay no library 1.2.0 in my Trisquel edition. Still would be nice to have binaries to download. Compiling did not work for me in an other Linux edition. Too many errors and missing files.

>>polakovic wrote:
>>*_COORD_REQUEST properties are not used anymore, *_COORD and read/write now.
>>Mount can report coordinates by EQUATORIAL_COORD, EQUATORIAL_EOD_COORD

I understood the coordinates where read/write. So read only. Confusing. No problem can live with that

I tested the java server &simulator. Noticed again different message after (<getProperties version="1.7"></getProperties>) . The only way to reliable detect devices is the look for device="Telescope Simulator" The label='Name'> doesn't show up in the java response. I hoped to have a clear XML syntax but that is now fading.

Han

It can be done as a side effect of redefinition request (page 8 in INDI protocol spec) by

<getProperties version="1.7" device="XXX" property="EQUATORIAL_EOD_COORD"/>

but it is wrong approach, THERE IS NO REQUEST/RESPONSE MECHANISM IN INDI!!!


Sorry, I don't understand. What does it mean to access the device driver directly?


No, this is correct way how to do it. If client will be developed using INDI standard, it will work. Server can update coordinates anytime it wants or needs and wINDI wants to send them every second, that's all. THERE IS NO REQUEST/RESPONSE MECHANISM IN INDI!!!


The syntax is correct and any INDI client should understand it. IMHO the only reliable way to do anything is to implement INDI protocol parser instead of catching random strings in the stream Sorry, Peter

Hello Peter,

>>Sorry, I don't understand. What does it mean to access the device driver directly?

Connection directly between client and device without a server. See page 2 white paper:
INDI Architecture, The diagram below represents the simplest possible INDI configuration: one Client connected to one Device: So working without a server.

>>The syntax is correct and any INDI client should understand it
Slew and read the telescope position is easy. The only problem was to detect the devices available in the server. The Java server didn't responded with label='Name'>Driver Name< I was using that to find the available devices.

Han

You can use wINDI only over TCP, there are no drivers you can access directly. Peter

Okay but in which language and communication channel is the server talking with the device driver(s)? According the white paper he is talking INDI. I assume the interface is not open since as it is run as:
indiserver indi_simulator_telescope
So theoretical, I could access the driver similar as the server does but the communication channel is for sure not TCP.


>>but it is wrong approach, THERE IS NO REQUEST/RESPONSE MECHANISM IN INDI!!!
I have now just made a connection with Java telescope simulator en server. I don't get any RA/DEC message! My users will complain. They have just connected to their expensive telescope and they can't see where the thing is pointing at. They can try to move a little but they don't want the whole thing rotate suddenly 180 degrees. I will try the
<getProperties version="1.7" device="XXX" property="EQUATORIAL_EOD_COORD" </getProperties>.
for initialization only if the server/device doesn't tel me where the telescope is pointing.

Han

wINDI uses INDI network protocol on client side and ASCOM API on driver side. It uses ASCOM drivers, not INDI drivers!

I can't help you with java indiserver server, it is not my code. But if it didn't reported RA/DEC it probably means, that you missed something again. I repeat once again, this is completely wrong approach and you are just wasting time. Implementation of full INDI parser is not an overkill, it is a must. Peter

Oleg, great that works! . I only had to copy the files to /usr/bin but now it is reporting version 1.2.0. Only I have 400 mbytes more , I probably will uninstall soon.


Found the simple reason. It works only once at the very first time! In Java the telescope driver stays CONNECT=On all the time. Also after disconnecting the server. So after reconnecting the server, it is already "On" and it will not report the position after connection Telescope simulator !!! Simple as that.

I can't switch the Telescope Simulator to CONNECT=Off. Same in wINDI and library 1.2.0. Also SkyChart has the same problem. If you you switch the Telescope Simulator Off in the INDI control panel, the Telescope Simulator just keeps working !!. This happens both in Java and wINDI using Skychart. Skychart is using the following command:
<setSwitchVector device='ASCOM Simulator Telescope' <oneSwitch name='CONNECT'>Off</oneSwitch> <oneSwitch name='DISCONNECT'>On</oneSwitch></setSwitchVector> What is going on here?

I will no longer bother. The HNSKY INDI implementation works fine with three servers and it is time to focus on some other more urgent things. Tonight I will probably release hnsky_linux beta1. All major functions including dss2 downloading are working fine.

Thanks for the support and feedback.
Han

p.s. the command <getProperties version="1.7" device="XXX" property="EQUATORIAL_EOD_COORD"/> work only with wINDI but not with Java sever. I will not use it.



.

Han, I'm afraid, that this is correct, driver should not disconnect when the client closes the connection. You should send getProperty message to get updated values.


This XML can't work, property name is missing.

Peter,
>>this is correct, driver should not disconnect when the client closes the connection. You should send getProperty message to get updated values.

If I disconnect from the wINDI server, the ASCOM telescope simulator window is gone. After reconnecting the ASCOM simulator has lost it last RA/DEC value. So this behavior is not ideal?

It would be also be nice to have the ASCOM equinox parameter ".EquatorialSystem " included in the next wINDI edition.

>>This XML can't work, property name is missing.
Help me here. Which property name is missing? How to instruct the device to connect=off correctly.

Han

Try to disconnect device before disconnecting client.


<setSwitchVector device='ASCOM Simulator Telescope' name='CONNECTION'><oneSwitch name='CONNECT'>Off</oneSwitch><oneSwitch name='DISCONNECT'>On</oneSwitch></setSwitchVector>