Yeah, I have tried having it be the only thing plugged in. I am still going to try to set the port to be the same as my CGE mount, but have had to fight other Stellarmate issues. Maybe this weekend I will make some progress.


Sent from my iPad using Tapatalk

Read More...

Thanks Lenny. I am not on a pc. It does work and connect when I am on a pc - but that is not running Stellarmate/Kstars/Ekos. When I am on the Raspberry pi based Atikbase/ Stellarmate with Kstars and Ekos it doesn’t connect. It reliably connects and operates every time when I plug it into my PC. It has yet to connect with Stellarmate on the Raspberry pi. Powered USB hub or not. Brand new cable, or the old one. Won’t connect. It probably is not identifying the port. Stellarmate/Kstars/Ekos is not auto-recognizing the port for the AVX. It is looking more like a software error or configuration error.

Read More...

A new Celestron AVX mount won’t connect to Atikbase / Stellarmate Kstars / Ekos 3.5.9. Any clues how to get Stellarmate to talk to a Celestron AVX?

The driver does not crash. However it won’t detect or communicate with the AVX mount. I have used two different USB cables. I have put a powered USB hub between the AVX and the Atikbase running Stellarmate. I used different USB ports on the Atikbase. I plug into the bottom of the AVX mount’s hand controller. I did align the mount using a Two-Star alignment. Gotos from the hand control operate fine.

I have verified the cables work by connecting the USB cable to a PC running AstroPlanner. It connects to the mount, reads its position, commands it to go to positions, moves the scope, gets the time/date from the mount without issue.

I went back to the Atikbase / Stellarmate and the AVX, and it still won’t connect. The port listed in the configuration is /dev/ttyUSB0. Should this be something other than the default value of /dev/ttyUSB0? The Atikbase / Stellarmate does connect to and operate my 2006-vintage CGE mount and controls it (I tell Ekos it is a CGEM). I have a separate configuration for using the CGE vs. the AVX. I have not checked the port on the CGE.

I’ve included the log file. I searched the forum using various keywords related to AVX and connection. I read the FAQ on mounts, and thus tried the USB hub. I’ll get new cables and see if the present cables are USB 1.0 cables while 2.0 or 3.0 are required. The same cable that connects to the mount may be moved to connect an Atik 428EX color CCD with Stellarmate / Ekos. It connects and controls the camera and acquires images.

The AVX is a new mount for a smaller lighter imaging system that is more portable than what I have on the CGE. I’ll be switching back and forth between the CGE and the AVX in the future (not simultaneously).

Notes on the log file. There are several trials in the log. One of them did not have the Atik or QHY cameras plugged in. Ignore that part of the log.

Thanks for the suggestion. This worked and fixed the issue. I did have a false start until I realized libindil was really libindi1 (not a lower case L, but the digit 1). Thanks very much.

-Alan.

Read More...

I thought I had a previous post on this. No idea where it went. Apologies if this is a duplicate.

I updated my Atikbase running Stellarmate to use Kstars 3.5.9. Upon launching Ekos the Atik driver crashes. I had been using Kstars 3.5.8 and it was generally working OK. The update to 3.5.9 makes it now not functitonal. A partial log entry is pasted below. Two logs are attached. Can I downgrade back to 3.5.8 (if so, how)? Is there a fix available?

-Alan.

[2022-07-04T15:23:55.041 UTC DEBG ][ org.kde.kstars.indi] - Connection to INDI server is successful
[2022-07-04T15:23:55.043 UTC INFO ][ org.kde.kstars.ekos] - "INDI services started on port 7624."
[2022-07-04T15:23:55.060 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-04T15:23:55: startup: /usr/bin/indiserver -v -p 7624 -m 1024 -r 0 -f /tmp/indififo7d81ee66 "
[2022-07-04T15:23:55.061 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-04T15:23:55: listening to port 7624 on fd 3"
[2022-07-04T15:23:55.061 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: start indi_atik_ccd"
[2022-07-04T15:23:55.061 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "FIFO: Starting driver indi_atik_ccd"
[2022-07-04T15:23:55.061 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-04T15:23:55: Driver indi_atik_ccd: pid=1285 rfd=4 wfd=7 efd=8"
[2022-07-04T15:23:55.061 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-04T15:23:55: Client 5: new arrival from 127.0.0.1:35962 - welcome!"
[2022-07-04T15:23:55.062 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-07-04T15:23:55.141 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-04T15:23:55: Driver indi_atik_ccd: indi_atik_ccd: symbol lookup error: indi_atik_ccd: undefined symbol: _ZThn4768_N4INDI3CCD13GuideCompleteE12INDI_EQ_AXIS"
[2022-07-04T15:23:55.141 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-07-04T15:23:55.144 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-04T15:23:55: Driver indi_atik_ccd: stderr EOF"
[2022-07-04T15:23:55.144 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "2022-07-04T15:23:55: Driver indi_atik_ccd: Terminated after #0 restarts."
[2022-07-04T15:23:55.144 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: ""
[2022-07-04T15:23:55.145 UTC CRIT ][ org.kde.kstars.indi] - INDI driver "indi_atik_ccd" crashed!
[2022-07-04T15:23:55.167 UTC DEBG ][ org.kde.kstars.indi] - INDI Server: "Child process 1285 died"