I'm disappointed in the standardization of INDI. I found now totally 4 standardization problems between library 1.2.0 (Linux) and wINDI (MSWindows) while trying to connect to the telescope simulators. To activated the scope simulators, I gave the following commands to the server:
SendMessage('<newSwitchVector device="'+INDI_telescope_name+'" name="CONNECTION"> <oneSwitch name="CONNECT">On</oneSwitch> </newSwitchVector>'); {connect to telescope}
SendMessage('<newSwitchVector device="'+INDI_telescope_name+'" name="ON_COORD_SET"> <oneSwitch name="TRACK">On</oneSwitch> </newSwitchVector>');{telescope tracking on}
.I get the following responses:
Linux INDI 1.2.0:
<setSwitchVector device="Telescope Simulator" name="CONNECTION" state="Ok" timeout="60" timestamp="2016-06-11T22:41:56">'#10' <oneSwitch name="CONNECT">'#10'On'#10' </oneSwitch>'#10' <oneSwitch name="DISCONNECT">'#10'Off'#10' </oneSwitch>'#10'</setSwitchVector>
wINDI:
<defSwitchVector device='ScopeSim Telescope' name='CONNECTION' label='Connection' group='Main Control' state='Idle' perm='rw' rule='OneOfMany' timeout='0' timestamp='2016-06-11T22:58:00.6'>
<defSwitch name='CONNECT' label='Connect'>Off</defSwitch>
<defSwitch name='DISCONNECT' label='Disconnect'>On</defSwitch>
Maybe I make an judgement mistake or crucial mistake, but I conclude that four things are differently:
1) Single versus double apostrophe
2) <defSwitchVecto versus <setSwitchVector
3) <oneSwitch name="CONNECT">'#10'On'#10' </oneSwitch> versus <defSwitch name='CONNECT' label='Connect'>Off</defSwitch>
4) And finally line feed characters in Linux. requiring a trim commando.
Can anybody comment, if I'm wrong???
I have Ekos running and the telescope simulator with the command: indiserver indi_simulator_telescope. For wINDI I use the ASCOM simulator for NET.
Kubunti isn't a very pleasant release for me. Resizing gives a black screen requiring a restart (in VMWare). Application Plasma crashes regularly. Responsiveness is poor. Windows popup too slow.