Tried the update ..no joy.
I will try the DSI in a friends Laptop with EKos installed.
i will report back.
As you may have guessed i like to build stuff:)
I might just by a Leonardo and have a tinker and see where it leads. At the moment I am torn between Linux INDI and NINA W10. It took me 2 1/2 years to build my dome etc. i have been looking for an all in one solution for observatory/ Astro-photography control. When i discovered INDI it got me interested. I have "converted" my Astro friend to INDI and I would really like to do the same .....the dome control is the stumbling block. If i can overcome the driver issue i will gladly join the INDI Kstars Ekos users!
Thanks for your advice.
I will keep experimenting.
I guess i was suggesting using an Arduino and stepper. I have had experience with this. Built focusers and filter wheels etc. I dont envisage any difficulty with the hardware. i suppose i would like to know is the software and firmware straight forward to implement. I am prepared to experiment.
INDI can control Meade DSI Pro I/II CCDs via the indi_dsi_ccd driver. Under Ubuntu, you can install the driver via:
sudo add-apt-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-dsi
The driver support basic capture and adjustment of gain.
Once you're connected, you can capture images as FITS from the camera.
Some users bug tracking system at SourceForge. (You can log in with a variety of existing accounts, including Google, Yahoo and OpenID.)
Rate this listing
Meade DSI Pro (I/II)
bruce@bruce-Latitude-D430:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
I am under the impression that the Nexdome control software/Drivers etc. is Open Source. It is nice that they have done this for the end users.
My question : I am asking for advice as to whether it is feasible to construct my own diy arduino hardware to control my dome and use the Nexdome software to run it using INDI KStars.
Would this be easy to implement?
i have reinstalled the Meade indi driver again. Still no luck .
bruce@bruce-Latitude-D430:~$ ldd $(which indi_dsi_ccd)
libindidriver.so.1 => /usr/lib/i386-linux-gnu/libindidriver.so.1 (0xb7bfa000)
libusb-1.0.so.0 => /lib/i386-linux-gnu/libusb-1.0.so.0 (0xb7bdf000)
libstdc++.so.6 => /usr/lib/i386-linux-gnu/libstdc++.so.6 (0xb7a59000)
libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xb7957000)
libgcc_s.so.1 => /lib/i386-linux-gnu/libgcc_s.so.1 (0xb7939000)
libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xb775d000)
libnova-0.16.so.0 => /usr/lib/i386-linux-gnu/libnova-0.16.so.0 (0xb73ff000)
libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xb73e0000)
libcfitsio.so.5 => /usr/lib/i386-linux-gnu/libcfitsio.so.5 (0xb71d8000)
libz.so.1 => /lib/i386-linux-gnu/libz.so.1 (0xb71b9000)
libjpeg.so.8 => /usr/lib/i386-linux-gnu/libjpeg.so.8 (0xb7146000)
libfftw3.so.3 => /usr/lib/i386-linux-gnu/libfftw3.so.3 (0xb6f56000)
libudev.so.1 => /lib/i386-linux-gnu/libudev.so.1 (0xb6f35000)
libbz2.so.1.0 => /lib/i386-linux-gnu/libbz2.so.1.0 (0xb6f24000)
libcurl-gnutls.so.4 => /usr/lib/i386-linux-gnu/libcurl-gnutls.so.4 (0xb6e97000)
librt.so.1 => /lib/i386-linux-gnu/librt.so.1 (0xb6e8d000)
libnghttp2.so.14 => /usr/lib/i386-linux-gnu/libnghttp2.so.14 (0xb6e64000)
libidn2.so.0 => /usr/lib/i386-linux-gnu/libidn2.so.0 (0xb6e45000)
librtmp.so.1 => /usr/lib/i386-linux-gnu/librtmp.so.1 (0xb6e25000)
libpsl.so.5 => /usr/lib/i386-linux-gnu/libpsl.so.5 (0xb6e16000)
libnettle.so.6 => /usr/lib/i386-linux-gnu/libnettle.so.6 (0xb6dda000)
libgnutls.so.30 => /usr/lib/i386-linux-gnu/libgnutls.so.30 (0xb6c41000)
libgssapi_krb5.so.2 => /usr/lib/i386-linux-gnu/libgssapi_krb5.so.2 (0xb6bed000)
libldap_r-2.4.so.2 => /usr/lib/i386-linux-gnu/libldap_r-2.4.so.2 (0xb6b91000)
liblber-2.4.so.2 => /usr/lib/i386-linux-gnu/liblber-2.4.so.2 (0xb6b81000)
libunistring.so.2 => /usr/lib/i386-linux-gnu/libunistring.so.2 (0xb6a00000)
libhogweed.so.4 => /usr/lib/i386-linux-gnu/libhogweed.so.4 (0xb69ca000)
libgmp.so.10 => /usr/lib/i386-linux-gnu/libgmp.so.10 (0xb693f000)
libp11-kit.so.0 => /usr/lib/i386-linux-gnu/libp11-kit.so.0 (0xb67f1000)
libtasn1.so.6 => /usr/lib/i386-linux-gnu/libtasn1.so.6 (0xb67dc000)
libkrb5.so.3 => /usr/lib/i386-linux-gnu/libkrb5.so.3 (0xb6700000)
libk5crypto.so.3 => /usr/lib/i386-linux-gnu/libk5crypto.so.3 (0xb66c9000)
libcom_err.so.2 => /lib/i386-linux-gnu/libcom_err.so.2 (0xb66c4000)
libkrb5support.so.0 => /usr/lib/i386-linux-gnu/libkrb5support.so.0 (0xb66b7000)
libresolv.so.2 => /lib/i386-linux-gnu/libresolv.so.2 (0xb669f000)
libsasl2.so.2 => /usr/lib/i386-linux-gnu/libsasl2.so.2 (0xb6681000)
libgssapi.so.3 => /usr/lib/i386-linux-gnu/libgssapi.so.3 (0xb663a000)
libffi.so.6 => /usr/lib/i386-linux-gnu/libffi.so.6 (0xb6631000)
libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xb662c000)
libkeyutils.so.1 => /lib/i386-linux-gnu/libkeyutils.so.1 (0xb6627000)
libheimntlm.so.0 => /usr/lib/i386-linux-gnu/libheimntlm.so.0 (0xb661d000)
libkrb5.so.26 => /usr/lib/i386-linux-gnu/libkrb5.so.26 (0xb657e000)
libasn1.so.8 => /usr/lib/i386-linux-gnu/libasn1.so.8 (0xb64cb000)
libhcrypto.so.4 => /usr/lib/i386-linux-gnu/libhcrypto.so.4 (0xb648f000)
libroken.so.18 => /usr/lib/i386-linux-gnu/libroken.so.18 (0xb6477000)
libwind.so.0 => /usr/lib/i386-linux-gnu/libwind.so.0 (0xb644d000)
libheimbase.so.1 => /usr/lib/i386-linux-gnu/libheimbase.so.1 (0xb643c000)
libhx509.so.5 => /usr/lib/i386-linux-gnu/libhx509.so.5 (0xb63ed000)
libsqlite3.so.0 => /usr/lib/i386-linux-gnu/libsqlite3.so.0 (0xb62ce000)
libcrypt.so.1 => /lib/i386-linux-gnu/libcrypt.so.1 (0xb629c000)
I think I have the correct log for you.
I am using Ubuntu studio on both 32 and 64 bit machine . Both will not connect to the DSI in Ekos using the meade driver int he dropdown list.I have attache the log file.
With the DSI plugged in I then went to the start button in ekos to open my profile. I only have the Meade DSI in my profile.
How do you access the Debug log?
Would the Nexdome software be a viable solution? (open sourced) This would require me to change over to an Arduino rather than the Velleman board. But it could be my only option , at present, to try INDI for my Dome etc... But if the Lesvedome can be used it would be a much better option for me an others like me who (are very happy with and) have successfully implemented Lesvedome . The goal of everyone in our hobby is to have all your equipment reliably working together and have clear skies at the same time!!!
I know it seems odd to be using such an old camera , but I purchased it second hand to do some Photometry and variable star analysis.
The error recieved when trying to connect:
"KStars detected INDI driver indi_dsi_ccd crashed. Please check INDI server log in the Device Manager."
I was wondering if there is an issue with the Meade DSI driver? I have had no success when trying to connect this camera.
020-03-05T11:37:45 Unable to establish:
+ Meade Deep Sky Imager
Please ensure the device is connected and powered on.
2020-03-05T11:37:40 INDI services started on port 7624.
2020-03-05T11:37:40 Starting INDI services...
The Camera driver has been selected from the drop down menu in the profile editor, but will not connect.
Thanks fro any help with this one.
I am not skilled in writing drivers etc. ( i wish i was!) . I have a home built Dome that I control with Lesvedome . Works great on Ascom. I would like to switch to Linux and see the INDI Library as the way to go. the only issue i have is Ekos does not support The Lesvedome DPP Veleman system. for me it would be great if id did, asi could run all my equipment from the one suite of software (INDI Kstars/Ekos). I am impressed with the INDI stuff. my mate has "converted" to INDI and we are both in awe about the relative ease in getting our equipment configured.
If I could only run my Dome from INDI ........?
Any Help in this matter will be greatly appreciated.