I talked to Howard @ AP and I know how to fix the CP2 guide rate issue you encountered - I'll have a PR today hopefully.
I think I understand time errors we're seeing but that will take a little more time to fix.

Excellent, I was sure you would get a better understanding from Howard. Correct me if I am wrong, but I think having the guide rate setting in the INDI driver control panel as you have recently implemented will give you the reference for resetting the guide rate when needed.

Will the guide rate in the INDI control panel interact in the EKOS guide module (guide rate setting) the same way other settings in INDI control panel do with various EKOS modules?

If you can remember any time you use the 'virtual' hand controller in Ekos/INDI at center speed 12x or 64x to go into the INDI Control Panel and set the guide speed back then it ought to work as it is now. Remember, if for example, 0.5x is shown selected and you want to set it to 0.5x you need to select a different speed and reselect 0.5x again.

The proper fix is what I'm working on which will be to detect the firmware version and if 'E' or earlier than restore the guide speed after every use of the MoveNS() or MoveEW() methods at a speed of 12x or 64x.

I don't use the Ekos guide module so I can't really answer questions about it.

Very good, once the time format errors are fixed, hopefully I will be able to connect to my mount and run this through some tests. Thank you for all your help!

Could you remind me - are logs available for the time format crash?

Yes, I included log files on this post where I ran some tests while encountering the time format error:
www.indilib.org/forum/mounts/2819-wrong-...l?limitstart=0#20998

There are two log files there - one for each version of the software I was testing. The log for the 2.8.7 version software should show something as that is the version where I encountered the error. My original post as linked above has the description.

I just committed some fixes and should be available tomorrow in the PPA.

Thank you Jasem! You and Mike have been great help in getting these issues sorted. I will download and test when the updates are ready in PPA (tomorrow). I'll report my results here when I have them.

Please let us know. INDI 1.6.0 is planned for release in less than 2 weeks and I hope these bugs are squashed before the official release.

I downloaded the latest updates from the PPA this afternoon on my Raspberry Pi 3 (KStars/Ekos 2.8.8 ). I have Ekos setup with the AP900 mount (connected via an FTDI USB to serial converter cable) and the camera and focus simulators just for the indoor testing. I have enabled logging and attached the results to this reply. When I start INDI and connect from Ekos I get the following message that the indi_lx200ap driver crashed:



I hope the logs have some further details about the driver crash. There appears to be at least some initial communication with the mount, however, after the driver crash there appears to be no other communication or feedback, I did try a "warm" connect to the mount just to see if it connected but it appears not.

You are getting the 'stack smashing detected' around 15:26:33.228 again. I'm guessing that is an ARM arch thing?

Mike,
Correct, and the same error occurs a bit earlier in the log as here (1st connection attempt I believe, red added for emphasis):

[2017-12-04T15:24:28.405 EST DEBG ][ org.kde.kstars.indi] - INDI Server: "2017-12-04T20:24:28: Driver indi_lx200ap: *** stack smashing detected ***: terminated"
[2017-12-04T15:24:28.406 EST DEBG ][ org.kde.kstars.indi] - INDI Server: "2017-12-04T20:24:28: Driver indi_lx200ap: stderr EOF"
[2017-12-04T15:24:28.406 EST DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 1847 died"
[2017-12-04T15:24:28.406 EST DEBG ][ org.kde.kstars.indi] - INDI Server: "2017-12-04T20:24:28: Driver indi_lx200ap: restart #1"
[2017-12-04T15:24:28.406 EST DEBG ][ org.kde.kstars.indi] - INDI Server: "2017-12-04T20:24:28: Driver indi_lx200ap: pid=1858 rfd=4 wfd=13 efd=16"
[2017-12-04T15:24:28.406 EST DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2017-12-04T15:24:28.407 EST CRIT ][ org.kde.kstars.indi] - INDI driver "indi_lx200ap" crashed!
[2017-12-04T15:24:28.456 EST DEBG ][ org.kde.kstars.indi] - INDI Server: "2017-12-04T20:24:28: Driver indi_lx200ap: initializing from Astrophysics device..."
[2017-12-04T15:24:28.457 EST DEBG ][ org.kde.kstars.indi] - INDI Server: "2017-12-04T20:24:28: Driver indi_lx200ap: Initializing from Generic LX200 device..."

I did an internet search on the 'stack smashing detected' error and found that in the C/C++ development environment this indicates a buffer overrun. I am, as yet, unfamiliar with the development environment for INDI/KStars/Ekos, however I am sure that Jasem or some other developers may know how that error applies.