It looks like doing a search for "libindi" on my system shows what version is installed.
I found a couple of files with the version number when doing that search.
How do I tell what version of INDI I am running? I'm running Astroberry on my Raspberry.
I know some people have issues when using two ZWO camera at once. I get this now and then and want to eliminate that from my setup.
I'm trying to find the most stable platform and have been using Astroberry and Stellarmate, and a laptop on Mint. -The Pi4 will be my go to though.
I use a 294mc as my main camera and an ASI 120mm mini to guide. Any recommendations for a reliable guide camera that will not cause trouble with the 294?
I see the Loadstar is recommended but 600 bucks is a lot.
I also have a ASI224mc that I can use, but haven't tried.
In Ekos under the capture module, you can try "Live Video" it may or may not work with your camera.
Any idea why I would get a "serial read error" after a meridian flip?
I had my setup on a Linux Laptop (Celestron CGEM/ASI294, ASI120mm mini), guiding and doing an image run. I had meridian flip enabled. It captured half of the images, started a flip and never started again. Hours later I tried to park it and it wouldn't do that. I had to stop and disconnect INDI and restart the software and then parked okay.
Welcome to KStars 3.5.2 Stable
- Arch: "x86_64"
Kernel Type: "linux"
Kernel Version: "5.4.0-67-generic"
Qt Version: 5.12.8
. . .
[2021-03-16T01:42:09.858 PDT DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "12h 19m 54s" ( 12.3318 ) DE: " 14° 19' 00\"" ( 14.3165 )
[2021-03-16T01:42:09.858 PDT INFO ][ org.kde.kstars.ekos.guide] - "Mount is moving. Resetting calibration..."
[2021-03-16T01:42:09.859 PDT INFO ][ org.kde.kstars.ekos.guide] - "Calibration is cleared."
[2021-03-16T01:42:09.863 PDT INFO ][ org.kde.kstars.ekos.mount] - "Meridian flip slew started..."
[2021-03-16T01:42:09.891 PDT DEBG ][ org.kde.kstars.indi] - ZWO CCD ASI120MM Mini : "[DEBUG] Aborting camera exposure... "
[2021-03-16T01:42:09.958 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[INFO] Slewing to JNOW RA 12:19:54 - DEC 14:18:59 SlewOffsetRa 68.8 arcsec "
[2021-03-16T01:42:31.948 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:36.953 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:42.959 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:42.960 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Failed to read RA/DEC values. "
[2021-03-16T01:42:48.966 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:48.966 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Failed to read RA/DEC values. "
[2021-03-16T01:42:54.972 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error ". . .
Tunafish post=68758 wrote: I grabbed the Celestron driver fixes from github and built them against INDI 1.8.9 and guider calibration is now working for me on my AVX.
Welcome to my lesson learned. Same thing here. My ZWO cameras are not found but work in ASI software.
You need to revert to the stable INDI.
I tired the nightly Because I wanted the Celestron 3.6 driver to fix pulse guiding. After I updated I couldn't get my cameras going.
Switching back to stable fixed that. I ST4 guiding right now with my ASI 120mm mini on my CGEMII with a ASI224 and it's working great.
Now I know, baby steps and BACKUP!
Cool, reverted back to stable 3.5.2
All devices are found and run!
This version still has Celestron driver 3.5, but I need 3.6 to fix the pulse guiding rate but at least I can guide ST4 and know how to get back, and do testing now.
Thanks so much everyone!
Spartacus post=68725 wrote: both were using a locked in nightly build from about 2-3 weeks ago and both set ups performed perfectly. I will try to find out the details of the nightly that I am using. I have not updated since.
Thanks for the update. I'll go back to the non nightly and see if that works. I had to try this because an update messed up my guiding with the CGEM. I got the latest driver, but now ZWO CCDS seem to be hurting from the nightly. -or my combo . . .
Maybe it's just my bad beginners luck with INDI . . . I'm just trying to find the most stable working setup for me with my Celestron CGEM, and ZWO ASI 294 and my ASI120mm mini guider.
I'm trying Astroberry, Stellarmate, and now laptop Linux Mint. So far Astroberry seems the most stable to remote into (have everything run locally), but the latest INDI update with the Celestron 3.5 driver messed up the guiding. That's been fixed, so that's why I was trying the nightly builds.
I guess it's a good time to Hypertune my mount!
i'm trying to get my setup working on my Linux Mint 20.1 laptop and Indi can't start my ZWO ASI294mc. I get the following message: KStars Unable to establish: + ZWO CCD Please ensure the device is connected and powered on.
-Yes it is connected, and it has the DC power on.
it works fine with the ASI Studio on this same machine.
The Celestron driver has been updated to version 3.6. That shows up on my Linux Desktop running mint, but my Astroberry is still on version 3.5 even after I tried switching over to the Nightly unstable builds. Don't know if I needed to uninstall something first, since Linux is still new to me. I'd rather test on my Astroberry, but I guess I can pull out the laptop ( I runn everything locally on the Astroberry and VNC into it).
I ran this in Astroberry:
sudo apt-add-repository ppa:mutlaqja/indinightly
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding gsc
I saw what it looked like a successful update, but I still see 3.5 Celestron driver in INDI in EKOS on the Astroberry?
Maybe I need to wait a few more days? Is there a way to confirm I'm getting Nightly builds after doing this?