There is a setting in Kstars/indi preferences that lets you choose which way updates go and we usually set it to update the mount time and position stored in the pc. You might check that setting if it's not updating the mount time.

Park position is stored in the xml file at ~/.indi/indi_OnStep_config.xml when you save the form and loaded at connect when the system is set to update the mount. Saving with park at the default (north) home position should fix that to a reasonable figure and is recommended for most portable mount users.
Hope this helps.
Cheers,
Ray

@ Chris

"In the case where mount was parked before power off, then OnStep restarts showing as pointing to north pole but when unpark, the scope show pointing at parking position"
Yes this is the expected behaviour, not under control of the driver but default Indi. May be this could be changed.

Correct while the date and time of the OnStep is from the time of powering off. Starting the OnStep and having indi-configuration time and location update set to, Mount is updating KStars, Kstar shows the sky it was during powering down
Seetings => Configure Kstars => Indi => Kstar Updates All Devices | Mount Updates KStars | GPS Updates KStars
I have no GPS so I cannot test

Chris
Ps. What are the functions of Cold Start and Init Home under the site tab (this one is red in my case)
The two buttons serve restectively to slew to home or to reset to Home. Status changes from Red to idle when one button pushed. You're right, behaviour could be changed, I have to note it

@ Blueshawk

I just issued a pull request for the version 1.4. There is a ci Test failing but not from my side I guess. So I am stuck as long the issue is not solved, maybe tomorrow.

Hi Alain,

Happy New Year to you too!
It is great news that you will be sending a pull request.
I did some very basic testing on a bench of latest code in your branch and it works with stable OnStep controller.

Alex

I am happy to annouce version 1.4 has passed the pull request this morning.
Don't expect a lot of new features, rather I tried to fix some errors and provide a better integration with Ekos.
Many thanks to those that helped to test, debug and propose changes.

Majors things that changed:
Alignment:
everything is now on a dedicated tab, up to 9 stars align, works with Ekos plate solving
Focuser
The First focuser is now recognized by Ekos and autofocus is working
Telescope Status
switch between Tracking, Parked, Slewing ... is now synchron with Ekos

ToDo:
For sure many cosmetic fixes like buttons / status lights
Library Tab is not working and could be removed in my opinion
Input / Outputs for custom functions like heaters ...

Now it is time for testing and bug collecting

Woot! (brandishes bug net)
I agree about the library. Since we're usually tied to planetarium software(kstars, ccdiel) it does seem unneeded.
It will be a while before I can test outside again. I have a long list of chores delayed by all the rain and snow we've had. Also waiting for parts as usual. I'll certainly put it on my schedule though. I may try to have it running as a secondary project in time for the lunar eclipse in a few weeks, which will be sure to uncover any bugs ten minutes before the good bit.

@Blueshawk,

no hurry, Rome didn't built in one day
Lucky you, you have snow, we have just fog. Even no real rain so that it is not good for astronomy, nor fo agronomy

Thanks Alain for this work (and all previous and future work too, there will be lots ...)

Yes, the Library stuff should go away. No need for the clutter.

Alain


Thanks for your answers


Chris

Thank you so much Alain and everyone else for all the work on this release!
I built the latest code from the master repository and did some testing with real equipment.
Basic things are working. I am getting some messages in the log which do not seem to impact anything:
*******
Align Updated
Align Error Updated
*******
Not sure they are errors or just regular messages. Keep in mind that my controller has about 4 months old stable firmware.

I tested focuser with Kstars (works) and CCDCiel (does not work).
I contacted Patrick from CCDCiel and he identified issue with INDI driver: the driver does not advertise its focuser capability. He suggested a patch and I implemented it and now both Kstars and CCDCiel can use the focuser.

Here is the patch:

diff --git a/libindi/drivers/telescope/lx200_OnStep.cpp b/libindi/drivers/telescope/lx200_OnStep.cpp
index 0312a9da..0dc8d52d 100644
--- a/libindi/drivers/telescope/lx200_OnStep.cpp
+++ b/libindi/drivers/telescope/lx200_OnStep.cpp
@@ -276,6 +276,8 @@ bool LX200_OnStep::initProperties()
IUFillText(&OnstepStat[7], "Error", "", "");
IUFillTextVector(&OnstepStatTP, OnstepStat, 8, getDeviceName(), "OnStep Status", "", STATUS_TAB, IP_RO, 0, IPS_OK);

+ setDriverInterface(getDriverInterface() | FOCUSER_INTERFACE);
+
return true;
}


Based on my successful testing, he will be submitting a PR. Please let me know if anyone has concerns with this change.

Alex

FYI, I fixed something I missed in the recent patch. LX200Generic should not have HIGH_FREQ_TRACK that was defined. so it was removed from there. Please check the updated code for any issues.

@ Jasem,

First all Happy new Year and good Health to you.

Thank you for the fix. No issue noted. I runs as expected.

Regards

Thanks avarakin,

Patrick's patch is allready merged and I tested it. Not complains at a first glance.
I simply wonder why it was recognized by KStars and not by CDC.
Which platform / Version are you using?
Would be interesting how you use Focuser with CDC

Thanks