Hi, I am using the indi_lx200classic driver connected to my home-build LX200 kind of compatible mount. The problem I have is that when I use a software like skychart, it does not update the position of my telescope. Even when I run indi_getprop like:
indi_getprop "LX200 Classic.EQUATORIAL_EOD_COORD.*"

I get the last value I synced the mount to. But it does not update continusly. I read somewhere else in the forum that INDI is only event-driven, but surely the mount driver (info_lx200classic) should frequently ask the mount for its current position and update the internal state. Can anyone help?

Regards, Lars

Are you getting data from other program? Also, you'd probably want to use LX200 Basic and not Classic unless you also implemented the classic subset commands. Try using minicom and see if you're getting data from it.

Thanks, but the basic does not even have motor controls. I need that for my astro photographig.
With the Basic I can't even sync my position in skycharts.

Its an arduino so using the serial monitor I can talk to it according to the LX200 command ref. The thing is, why isn't something inside INDI polling for the position regularly, i would think it should do that. Since the LX200 does not actively pushes updated information as far as I know..

Also, trying to manually set the position for the "LX200 Basic", I get no response at all.
I.e. doing:
bash$ indi_setprop "LX200 Basic.EQUATORIAL_EOD_COORD.RA;DEC=12;40"

I see no activity in the indiserver as well when I do that, started as:
bash$ indiserver -v indi_lx200basic

Regards, Lars

It should be polling the mount about every second. Run INDI server with full verbose and see if it is sending updates to the client:
Then connect to it and ask it to slew any where and check the output of the INDI server. You can also enable Logging in the driver, go to Options --> Enable Debug --> Log to File

Nope, its silent. I started a slew from skycharts and this is what I see with a lots of -vvvv:
2016-09-02T19:33:46: Driver indi_lx200classic: queuing responsible for <newNumberVector device='LX200 Classic' name='EQUATORIAL_EOD_COORD'>
2016-09-02T19:33:46: Driver indi_lx200classic: sending msg copy 1 nq 2:
<newSwitchVector device="LX200 Classic" name="ON_COORD_SET">
<oneSwitch name="TRACK">
Off
</oneSwitch>
<oneSwitch name="SYNC">
Off
</oneSwitch>
<oneSwitch name="SLEW">
On
</oneSwitch>
</newSwitchVector>

2016-09-02T19:33:46: Driver indi_lx200classic: sending msg copy 1 nq 1:
<newNumberVector device="LX200 Classic" name="EQUATORIAL_EOD_COORD">
<oneNumber name="RA">
0.1545928120613
</oneNumber>
<oneNumber name="DEC">
29.1827068328857
</oneNumber>
</newNumberVector>

2016-09-02T19:33:46: Driver indi_lx200classic: read setSwitchVector LX200 Classic ON_COORD_SET Ok
TRACK='Off'
SLEW='On'
SYNC='Off'
2016-09-02T19:33:46: Client 0: queuing <setSwitchVector device='LX200 Classic' name='ON_COORD_SET'>
2016-09-02T19:33:46: Client 0: sending msg copy 1 nq 1:
<setSwitchVector device="LX200 Classic" name="ON_COORD_SET" state="Ok" timeout="60" timestamp="2016-09-02T19:33:46">
<oneSwitch name="TRACK">
Off
</oneSwitch>
<oneSwitch name="SLEW">
On
</oneSwitch>
<oneSwitch name="SYNC">
Off
</oneSwitch>
</setSwitchVector>

2016-09-02T19:33:46: Driver indi_lx200classic: #:Sr 00:09.2# Successful
2016-09-02T19:33:46: Driver indi_lx200classic: #:Sd +29*10# Successful
2016-09-02T19:33:46: Driver indi_lx200classic: read message LX200 Classic 'Slewing to RA: 0:09:17 - DEC: 29:10:58'
2016-09-02T19:33:46: Client 0: queuing <message device='LX200 Classic' name=''>
2016-09-02T19:33:46: Client 0: sending msg copy 1 nq 1:
<message device="LX200 Classic" timestamp="2016-09-02T19:33:46" message="Slewing to RA: 0:09:17 - DEC: 29:10:58"/>



Then it is silent...

Please send log file with full verbose scope log.

Coming here. Started:
indiserver -l logs -vvv indi_lx200classic

Then connected the serial port and connected the telescope.

THhen from skychart i synced the telescope to M31 and then slewed to M33.
After some minutes I disconnected skychart.

The first file is stdout + stderr from indiserver, the second is the generated log-file

I forgot to say that I set the serial port and connected using indi_setprop commands.

No I meant the driver log as described in the Read Before you Post Any Support Request

Well, that file generated only contained these two lines:
INFO 50.722717 sec : Session log file /tmp/indi_lx200classic_2016-09-02T23:25:31.log
DEBUG 61.192506 sec : Toggle Logging Level -- Driver Debug


But !, I am using the mutlaqja-ppa source, but still I only have libindi-bin version 0.9.7, I did do apt update and upgrade, strange. Is linux mint fixing the version to 0.9.7 perhaps. I need to check this more.

Ah, I see. The official PPA does not have compiled versions for "trusty", the package files are empty for trusty. That was confusing.
I will compile the code myself then.

Yep, now it is working with latest 1.2 compiled. Perhaps the official repo should not look like it has versions compiled for trusty, people can easily be fooled if they are not experts in the apt-system (i am more of a yum/RPM guy).
Thanks for the help.