Thanks Jasem, to answer you question:-
1. Lodestar is the new component in this system so initially I tried direct autoguide via ST4 port but it failed and started this whole hunt. Actually I understood it was best to use drivers rather than ST4 autoguide , I got that from PHD best practice, do you recommend ST4 autoguide for indi/ekos? I've been using lx200ss2kpc driver and only asked about lx200 as possible way to test my setup and the lx200ss2kpc driver.

I'll correct my dec backlash by adjusting gears and try all tests again based on your feedback.
Andrew.

ST4 is the recommended way to guide in ALL platforms as far as I know since you are not encumbered by serial port delays. Mount aka pulse guiding should only be used as a last resort.

PHD2 best practices guide recommends pulse-guiding (openphdguiding.org/PHD2_BestPractices.pdf):
• Use ASCOM pulse-guiding instead of ST-4 guiding if mount supports it
• Get the benefits of one less cable and better logging/diagnostics

Serial port delays shouldn't really matter when doing multiple second guide exposures anyway. I've used both, now using pulse guiding to get rid of the extra cable, haven't noticed any particular difference otherwise.

Hi,
I have used a setup of a ss2000pc and an SBIG camera for several years in the past. I've always used an ST4 cable between the camera and the ss2000pc. This worked without problems. I think that the pulse-guiding that is referred to in the openphd documentation is the kind that is build into the controller. The ss2000pc does not support pulse-guiding commands.
Best regards,
Camiel

thanks everyone,

So if I understand the various inputs here :with my setup using the ss2kpc driver will not work since the controller doesn't accept the commands.The only option for guiding is to use the autoguide ST4 port. I'll try this again next clear night.

But why was a ssk2pc driver created if it cannot guide, what advantage does have over say a LX200 driver?

Andrew.

The SkySensor2000 driver is mostly LX200 driver. I just checked the code and only setting date/time and knowing when slew is complete is different, the rest is identical. If you have SkySensor2000 command set that has additional stuff for guiding, please share it with us.

Sorry Jasem I don't have any guiding extras for ss2k, I suppose they could be extracted from ASCOM driver?
Looks clear for tonight so I'll try autoguide ST4 again with a tighened backlash on Dec motor.

Thanks Camiel,
For the moment, with clear sky, I'm back to Windows/ASCOM system (BYEOS and PHD) which is OK, guides very well but lacks the complete suite that INDI offers. BTW - In this setup SS2K supports pulse-guide via the RS232 using ASCOM driver with PHD.

I tried Lin-Guider and it shows I probably do have an issue with my ST4/Rj12 autoguide cable, I tested with multmeter but cannot find fault. I'll probably invest €20 in professional cable and report back since this combination seems perfect with INDI.

Andrew.

Update - my SS2K autoguider function is broken.

So I'd like to contribute to editing SS2K driver to make it work with pulsedrive commands as it does in ASCOM. I only have limited programming skills (fortran, Basic, Python and script) but I see the ASCOM script is in VB and updated fairly recenty 2013 (LaurieY 6.1.7b github), so if somebody could hint were I could start, with a little help and if there is wider demand we might finish it! what do you think?.

Surely if one of the LX200 drivers is using pulseguide is it not just a case of editing that for differences? I notice I can select either Indi_lx200generic, basic or classic and I think even 16 worked, anyhow all partially worked at least enabling calibration and short guide until mount runs away,

Actually a SS2K pulseguide is might last hope to use INDI since below is my last failed test on the SS2K and ST4 autoguiding:-

Andrew.

ST4 failure confirmed

---

I opened the SS2K to check the continuity into the back of the RJ12 socket and it seemed to be OK, I mean no pins were electrically disconnected from the solder board.

There it seems the problem is within the SS2K circuit but I don't have the skills to debug that far. Although I assume the circuit is a fairly simple switch type mimicing the N.S.E.W buttons anyhow for now it's broken.

I tested the whole system again - 1st RS232 with Windows/PHD and Astroart using ASCOM drivers works 100% as per last 10 years. Switching to linux on Raspberry Pi or a PC fails on all SW, OpenPHD/Indi drivers and Sx drivers wil only guide in 2 directions. ST4 fails on Windows and Linux it will only guide in 2 directions.

Pulse Guiding was disabled specifically in the SkySensor2000 driver. If you say it worked for you in LX200, then it should work in SkySensor (it is based on LX200 anyway). It is now re-enabled. So please compile now or wait till tomorrow PPA update and test it. It's the same implementation as the LX200 scopes.

thanks jasem, I'll test on tuesday night and report back, forecast clear all week here
a couple of users on the ss2k group confirmed they guided with lx200 settings (ascom) so hopefully by reactivating it we should have some success - lets see...

UPDATE - with partial solution.
with help from Terry at Starlight Xpress we found that the Skysensor2000pc needed a signal input adjustment to work with Lodestar x2.
I can now confirm it works fully enabling me to autoguide via the ST4 port using Lin Guider, openPHD2 and indi (first night RMS 1" in dec and ra over several hours).

I'd still prefer to use the RS232 option but this still fails with the indi lx200ss2000 driver and as far as I can tell this is a bug and not hardware. I'm happy to try to help resolve this if there is a demand.
Andrew.