Syscan issues. about pyindi-client

[rkaczorek]

Clock does not tick in INDI clients either so it is feature not a bug ;-) (it used to tick in the past but this was removed from INDI some time ago). Regarding sync function - can you reproduce it with a command line indi_getprop / indi_setprop?

[SteveBz]

Hi, Yes I just discovered that!! In fact setTime() works perfectly, getTime() does not (for the reason you explain). I suspect it DOES work if you reconnect, so if you really, really want the time, you can disconnect and reconnect() followed by getTime() :).

I love how all just works, even though I made some quite large changes to it. I'll investigate the sync function further and post here.

I'll compare the sync equivalent with Ekos and see how it goes.

Thanks for the fast response.

Steve.

[SteveBz]

OK, next step. Apparently Kstars/Ekos Sync (ie 'set' RA&DEC) doesn't work either. It didn't transfer through to the handset until I had 'tracking on'. I also had to set up a simulated CCD to get rid of an Ekos error, but I don't think that was related to the Sync functioning.

When I moved back to set Sync in my own code, it still didn't work. My code is above. Is the sequence of commands important:

        self.indi.indiclient.sendNewSwitch(pcs)
        self.indi.indiclient.sendNewNumber(p)

?

If I were Indi, I'd sort of want the new coordinates first before I got 'permission to proceed' Ie 'Sync on', or maybe it makes no difference.

I also think that all the stuff around int(base 16)/2**16 is designed to produce a decimal hour (RA) from 0-24 or a decimal degree (DEC) from -90 to + 90 (I rarely drop below 20 because the surrounding trees are so high). So I just pass a decimal number to sendNewNumber(p). Is it any more complex than that?

I'll keep playing.

Although I really like INDI, the only reason for implementing it was to Sync remotely and share my mount with PHD2, so I gain nothing. :(