MAgnificent! That worked on first sight! Explanation?
I am facing an serious issue with Indi EQMOD and KStars. I have a Atlas EQ-G Mount using a EQDirect bluetooth adapter and IndiServer. Software Versions are Indi Library 1.6.3, KSTars 2.9.3. I use the current version 1.04 on my mount (motor driver).
After connecting to the IndiServer using KStars on /dev/rfcomm0 to my mount with EQMOD, I get a successful connection. Mount clicks and shows all relevant infomration. After approx 30 secs the bluetooth disconnects shwoing ttywrite and read errors. Slewing and change of park position is not possible. The same hardware setup has been working for over a year now. Only Linux and Indi/ Kstars has been updated. The effect can be seen using a remote machine as well as a laptop (Indi running localhost). I do get the following messages from KStars:
018-02-28T20:28:05: [ERROR] Error: -> tty write failed, check connection: Erro$
2018-02-28T20:28:04: [ERROR] Error when disconnecting mount -> tty write failed$
2018-02-28T20:28:04: [ERROR] Error: -> tty write failed, check connection: Erro$
2018-02-28T20:28:04: [INFO] Setting Eqmod Goto RA=1.44945 DE=60.3303 (target RA$
2018-02-28T20:28:04: [INFO] Aligned Eqmod Goto RA=1.44945 DE=60.3303 (target RA$
2018-02-28T20:28:04: [INFO] Starting Goto RA=1.44945 DE=60.3303 (current RA=13.$
2018-02-28T20:28:04: [INFO] EQMod Mount is offline.
2018-02-28T20:28:04: [ERROR] Error: -> tty read failed, check connection: Timeo$
2018-02-28T20:27:47: [INFO] Device configuration saved.
2018-02-28T20:27:47: [INFO] Saving device configuration...
2018-02-28T20:27:47: [WARNING] Can not load HorizonLimits Data File ~/.indi/Hor$
2018-02-28T20:27:47: [INFO] Mount is unparked.
2018-02-28T20:27:47: [WARNING] Init() : Setting both ST4 guide rates to 0.5x (2$
2018-02-28T20:27:47: [WARNING] Init() : First Initialization for this driver in$
2018-02-28T20:27:47: [INFO] EQMod Mount is online.
2018-02-28T20:27:47: [INFO] Successfully connected to EQMod Mount.
2018-02-28T20:27:42: [INFO] Debug is enabled.
2018-02-28T20:27:42: [INFO] Auo search is disabled.
I checked the following:
- exchanged bluetooth transceiver from mount --> no change
- exchanged bluetooth dongle on machine --> no change
- used another machine(laptop) --> no change
- software update on Mount --> no change
- used synscan controller with indi_synscan and eqmod in PC direct mode --> works
- permissions for device /dev/rfcomm0 checked on booth machines --> ok
- I checked the connection to the bluetooth device using screen --> no problem
- Power supply with 12 V Battery and AC/DC Power adapter 2250mA --> both the same effect
Attatched you can find the log file from KStars.
I really hope that someone can help me out here. It worked so good for so long on the identical hardware, that I am really frustrated right now.
confused. When I check the version on indiserver I get the version for the indilibrary as 1.4.1. Not sure what is going on...?!
sorry! I have to correct myself:
I found the file in the usr/lib/x86_64-linux-gnu AND in the ZIP from the Sources link here on the website.
I post here also the file if it helps: please remove the txt.
Hmm.. I did the following sequence:
- Uninstalled KStars, PHD2 and all Indi Drivers and Library
- Downloaded indi Sources from this website (Ver. 1.3.1)
- cd ed into libindi directory
- used the commands in the README to cmake libindi
- installed PHD2 and KStars bleeding from the repositories (via apt install)
--> both work now
but I am surely not an expert and moreover I cannot find any libindi.so.1 on my system anymore
Recognized this too. PHD2 refers to the same indi shared files obviously. After buiding indi from the sources provided here: both worked.
Thanks. Couldn't wait of course installed Indi from sources. Afterwards it worked. Looking forward to get back to the standard libraries though.
thanks. Can I rebuild the older indi drivers from sources somewhere?