Hi all,

this is the patch that works on my ZEQ25, it's still dirty but it works...
It can update the system date, time, lat and lon, time zone, it can slew the mount and possibly more things.
After unzipping, you can apply it with a "patch -p0 < zeq25.patch" from the directory above your indi-code one, or a "patch -p4 < zeq25.patch" if you put the patch in the indi-code/libindi/drivers/telescope directory.
After compiling, you can overwrite the original lx200 drivers and then use the lx200 classic INDI driver.
Please let me know how it goes for you.

Ciao,
Piero

Thanks tango13;

I'm getting lots of failure messages attempting to run the patch (from inside the telescope directory):

Hunk #1 FAILED at 164.
Hunk #2 FAILED at 184.
Hunk #6 FAILED at 336.
Hunk #7 FAILED at 366.
Hunk #8 FAILED at 395.
Hunk #10 FAILED at 486.
Hunk #11 FAILED at 519.
Hunk #12 FAILED at 554.
Hunk #16 succeeded at 720 (offset 1 line).
Hunk #17 succeeded at 731 (offset 1 line).
Hunk #18 FAILED at 745.
Hunk #19 FAILED at 764.
Hunk #20 FAILED at 787.
Hunk #21 succeeded at 808 (offset -14 lines).
Hunk #22 succeeded at 838 (offset -14 lines).
Hunk #23 succeeded at 876 (offset -14 lines).
Hunk #24 FAILED at 904.
Hunk #25 FAILED at 917.
Hunk #26 succeeded at 922 (offset -8 lines).
Hunk #27 succeeded at 936 (offset -8 lines).
Hunk #28 succeeded at 950 (offset -8 lines).
Hunk #29 FAILED at 985.
Hunk #30 succeeded at 1049 (offset 27 lines).
Hunk #31 succeeded at 1073 (offset 27 lines).
Hunk #32 succeeded at 1102 (offset 27 lines).
Hunk #33 succeeded at 1125 (offset 27 lines).
Hunk #34 FAILED at 1115.
Hunk #35 FAILED at 1149.
Hunk #36 FAILED at 1179.
Hunk #37 FAILED at 1203.
Hunk #38 FAILED at 1243.
Hunk #39 FAILED at 1255.
Hunk #40 succeeded at 1315 (offset 29 lines).
Hunk #41 succeeded at 1354 (offset 29 lines).
Hunk #42 succeeded at 1382 (offset 29 lines).
Hunk #43 succeeded at 1403 (offset 29 lines).
Hunk #44 FAILED at 1410.
21 out of 44 hunks FAILED -- saving rejects to file lx200driver.cpp.rej
patching file lx200driver.h
Hunk #1 FAILED at 47.
1 out of 2 hunks FAILED -- saving rejects to file lx200driver.h.rej
patching file lx200generic.cpp
Hunk #1 FAILED at 743.
Hunk #2 FAILED at 760.
2 out of 2 hunks FAILED -- saving rejects to file lx200generic.cpp.rej

Any thoughts?

--Jon

I'm having similar problems in running the patch.

OK, Got the errors sorted and the patch applied. However, I'm getting the same error setting the longitude with yours as I was with mine. It's trying to set my longitude to:

2015-11-16T23:16:48: Site location updated to Lat 37:33:25 - Long 283:29:38

It should be -076*30:22

I have the error sorted but, for some reason, it tries to set it twice which results in the 283:29:83. BTW, that ~283 value is 360-76...

--Jon

I believe you need to have the original files in place. I had to move my edited files out and replace them with the default ones. You can get the originals from here:

svn://svn.code.sf.net/p/indi/code/trunk/libindi

Hi jonkjon and tango13,
Sry to be a pain but can I have your respective .cpp/.h files and not the patch. I would like to compare/test your approach with mine.
cheers
yabby

That's correct.

I have corrected the code in my patch because the ZEQ treats longitude differently and I've disabled the 360 subtraction so it should be correct.
I too get the longitude set twice, but the second time it's the right one. I haven't had the time to investigate this double longitude, I'll try when I have the chance.

Once you apply the patch you already have mine but no problem, I can send them when I get home.

Ciao,
Piero

Folks, 283:29:83 IS the correct longitude because in INDI the standard is 0-360 EASTWARDS. This is not what gets sent to the mount, this is the value INDI uses for longitude. The actual value that gets sent to the mount is different for each mount depending on what they support.

At any rate, I added ZEQ25 driver from LX200Generic and removed the leading # in lx200driver that appears to be the cause of most issues. Please enable full debug logging in the Options tab _before_ you connect and test the driver. I made it use :SE# to find out if slewing is complete or not, so we'll see if it responds correctly to this command.

So by tomorrow, the PPA will be updated and you will see a new driver "ZEQ25" appear that you can test.

Sounds great!
Thank you very much.

I replaced all of my driver files with the originals and then updated from the ppa. I ran svn up on the libindi/drivers and the new ZEQ25 option appears. I get the message below:

2015-11-17T13:49:38: Error connecting to Telescope. Telescope is offline.

The results of the debug:

INFO 194.699075 sec : Session log file /tmp/indi_lx200zeq25_2015-11-17T13:49:26.log
DEBUG 195.717541 sec : Toggle Logging Level -- Driver Debug
DEBUG 196.405097 sec : Toggle Logging Level -- Scope Verbose
DEBUG 204.361104 sec : Testing telescope's connection using ACK...
DEBUG 214.469109 sec : Failure. Telescope is not responding to ACK!
ERROR 214.469148 sec : Error connecting to Telescope. Telescope is offline.


--Jon

From what I can see by sniffing the serial connection, it seems that the new ZEQ driver still tries to check the connection by sending the 0x06 char, which the ZEQ doesn't know how to reply to.

Opps there was a problem with LX200 initialization with unique_ptr, now resolved. Please try again.