I tryed instaling last kstars/ekos from source , and last 2.0.4 and all fails, so eq3-2 goto kit , DON't WORK in ekos not with eqmod driver, nor other skywatcher drivers.
Read More...
Only for test, i tried in other computer with indi and eqmod Debian's 12 versions (1.9.9), and also failed.
Read More...
hi Juergen
Yes i'm using 2.0.3 with kstars 3.6.2 because when i tried to use the indi libraries that comes with debian nothing worked, no cams no mounts, so i tried to install again from sources, but the indi version was 2.0.3, also i installed the thirdparty drivers.
I'm not sure if it'll work well, I mean installing last kstars version, because i must install not for the Debian repository, using flatpak or source, not sure it'll work well.
But anyway, i don't understand why driver could work in 1.9.8 and not in 2.0.3
regards,
Read More...
In one month, no answers? nobody knows? can't believe that i'm the only one that uses a eq3-2 goto kit with indy before and now it doesn't work.
Read More...
Hello,
I was using indi previous version for a long time, i recently updated to 2.0.3 version, and now, kstar/ekos don't connect to my eq3-2 mount (with kit goto), this mount worked fine with eqmod driver in the previous version, but in this is not working , neither other skywatcher drivers.
my indi versión is the latest, 2.0.3 running in linux debian 12 , with kstar/ekos 3.6.2
This is the log of eqmod driver.
DEBUG 101.131667 sec : Connecting to /dev/serial/by-id/usb-FTDI_USB_Serial_Converter_FT91PLA5-if00-port0 @ 9600
DEBUG 101.132284 sec : Port FD 4
DEBUG 101.132325 sec : Connection successful, attempting handshake...
COMM 101.132358 sec : dispatch_command: ":e1", 4 bytes written
COMM 101.332626 sec : read error, will retry again...
COMM 101.332778 sec : dispatch_command: ":e1", 4 bytes written
COMM 101.533041 sec : read error, will retry again...
COMM 101.533112 sec : dispatch_command: ":e1", 4 bytes written
COMM 101.733376 sec : read error, will retry again...
COMM 101.733454 sec : dispatch_command: ":e1", 4 bytes written
COMM 101.933718 sec : read error, will retry again...
COMM 101.933791 sec : dispatch_command: ":e1", 4 bytes written
COMM 102.134062 sec : read error, will retry again...
COMM 102.134157 sec : dispatch_command: ":e1", 4 bytes written
COMM 102.334451 sec : read error, will retry again...
COMM 102.334531 sec : dispatch_command: ":e1", 4 bytes written
COMM 102.534800 sec : read error, will retry again...
COMM 102.534885 sec : dispatch_command: ":e1", 4 bytes written
COMM 102.735152 sec : read error, will retry again...
COMM 102.735230 sec : dispatch_command: ":e1", 4 bytes written
COMM 102.935353 sec : read error, will retry again...
COMM 102.935428 sec : dispatch_command: ":e1", 4 bytes written
DEBUG 103.135721 sec : Handshake failed.
DEBUG 108.727662 sec : Connecting to /dev/ttyUSB0 @ 9600
DEBUG 108.728051 sec : Port FD 4
DEBUG 108.728085 sec : Connection successful, attempting handshake...
COMM 108.728122 sec : dispatch_command: ":e1", 4 bytes written
COMM 108.928403 sec : read error, will retry again...
COMM 108.928472 sec : dispatch_command: ":e1", 4 bytes written
COMM 109.129002 sec : read error, will retry again...
COMM 109.129155 sec : dispatch_command: ":e1", 4 bytes written
COMM 109.329705 sec : read error, will retry again...
COMM 109.329793 sec : dispatch_command: ":e1", 4 bytes written
COMM 109.530400 sec : read error, will retry again...
COMM 109.530489 sec : dispatch_command: ":e1", 4 bytes written
COMM 109.731179 sec : read error, will retry again...
COMM 109.731247 sec : dispatch_command: ":e1", 4 bytes written
COMM 109.931861 sec : read error, will retry again...
COMM 109.931937 sec : dispatch_command: ":e1", 4 bytes written
COMM 110.132471 sec : read error, will retry again...
COMM 110.132539 sec : dispatch_command: ":e1", 4 bytes written
COMM 110.333147 sec : read error, will retry again...
COMM 110.333229 sec : dispatch_command: ":e1", 4 bytes written
COMM 110.534558 sec : read error, will retry again...
COMM 110.534638 sec : dispatch_command: ":e1", 4 bytes written
DEBUG 110.735236 sec : Handshake failed.
any ideas?
Read More...
As I said, my version is 3.4.3 that's the one that came with Debian 11, I saw that newer versions got it resolved.
But I finally solved it, i found this page astro.vanbuitenen.nl/cometels with a list of comets that includes C/2022 E3 ZTF , i followed the instructions and downloaded it in $HOME/.local/share/kstars/comets.dat and problem resolved, now i've the list renewed and he comet C/2022 E3 ZTF appears.
BR,
Read More...
When i tried to update the comets data, it always return an error, (data verification failed) and if i try to add it manually it crash again,
How can i include this comet in Kstars? so ekos can platesolve it?
ah my configuration, Debian 11 , Kstars 3.4.3
Regards,
Read More...