I've had some time to play around with this the past couple of days and am seeing a few issues.

1. When connecting to the telescope simulator from EKOS, the site longitude gives an error "Property SiteLongitude The property value is out of range " the actual site longitude is -77:32:42 but EKOS uses 282:33:52. I can manually set the longitude in the control panel however. Even after manual correction, the scope crosshairs never move in kStars.

2. The scope simulator never moves when trying to track an object in kStars. i.e. Right click on target and select track and nothing happens.

--Jon

1. When wINDI was developed, definition of the property was "Site longitude, degrees +E" what can be read only as +E/-W. Now it is "Site longitude (0 to 360), degrees +E" what is quite confusing, specifically if probably every other software on the planet (including ASCOM) uses -180 to 180 east positive I'll check it with Jasem...

2. Can you check log on wINDI side to find out what't wrong and what commands are sent from EKOS side?

Peter

The 0-360 +E longitude has been a standard of INDI since 2003, it never changed.

I have attached the log from INDI server for windows as well as kStars log. There is no option in EKOS control panel to enable logging for ASCOM telescope sim....

--Jon

Check this: web.archive.org/web/20130501205631/http:...dard-properties.html :)

Jon, you forgot attachments... Peter

Sorry about that...I have been having some issues with this thread and replies, I don't know what happened...

--Jon

Thank you, I'll check it... Peter

The (0-360) was added the documentation to remove any ambiguity, but as I said before, it was 0-360 from day 1, including all mount drivers.

Jon, this bug was introduced in version 2.2.2 (EOD vs. non-EOD coordinates) and is hopefully fixed. Also driver is now more lenient to longitude value and accepts both 0-360 and +E/-W values without error message. Please try version 2.2.3. Peter

Do you have 32 bit version? The 32 bit link isn't working....Thanks.

--Jon

I did test the 64 bit version and it seems to be working......

--Jon