Wonderful! Welcome to spectroscopy.
This subject is "out of topics" in this thread, but tell me if you need any help somewhere.
Yesterday night I've been able to run a new observation, and everything went well.
Thank you again for your help.
Dear Peter and Patrick,
Unbelievable : IT WORKS ! Thank you so much for your help & reactivity.
I did exactly what you mention:
- rename libASICamera2.so.1.25 to libASICamera2.so.1.25OLD,
- copied the libASICamera2.bin (from github.com/indilib/indi-3rdparty/libasi/armv8) and rename it to /usr/lib/aarch64-linux-gnu/libASICamera2.so.1.25
- checked that strings /usr/lib/aarch64-linux-gnu/libASICamera2.so.1.25 | grep 1," gives "1.2" (yes, it does)
... and test Kstars: all ASI cameras work fine.
You're like magicians - thank you so much.
I'm now ready to observe again tonight. One day, I'll show you in detail what I'm doing (spectroscopy with UVEX instrument)...
Many thanks for your reply.
Whoo... new fresh install through compiling Indi... looks to me quite a hard task (I could do it, but I'm afraid it will take long - I'm not familiar enough with compiling). I'd like to observe tonight (;>)
We're talking about the Indi server, right? Not the Kstars/Ekos client (which is not on the same PC, in my case)?
I just looked on my Indi server (running on a Raspeberry Pi4): I've nothing in /usr/local/bin. And the
The command "sudo find /usr -name libASI*" returns:
The command "strings /usr/lib/aarch64-linux-gnu/libASICamera2.so.1.25 | grep 1," returns
1, 25, 0, 0
1, 25, 0, 0
which says, if I understand properly that I still have the faulty lib (should return 1, 22).
Any simple way to only get the 1.22 version?
Again, many thanks for your help.
It looks I'm facing the same issue. ASI driver crashes and restarts continously.
My Indi server is installed on a Raspberry Pi4. Kstars/Ekos is on a remote PC (local network).
The setup ran perfectly until the latest update. I've 4 ASI cameras attached to the server.
I've tried to installed the file given here : code.launchpad.net/~mutlaqja/+recipe/libomegonpro-stable
But no change.
I've tried updating with the nightly builds.
Can you give me a recommandation to make the setup work again?
François Cochard (Shelyak Instruments).
I confirm that Raspberry Pi 4 and Ubuntu 20.04 (desktop version) is amazing. So amazing, that I'm going to adopt it as a "Observatory main PC" !
You know what ? I did choose this setup first because it has a dual HDMI port - and I've two large screens on my desk. It works perfectly - just incredible.
(note : I use t 4Gb version).
Also : I'll work in client - server mode, and the Indi server is in another Raspberry-like module, close to the telescope.
Thank you for the quick reaction. Yes, I did try the latest nightly build - behavior is the same.
I need some help. I've a camera QHY5III 174, used for guiding in spectroscopy.
The camera works fine when connected on a desktop PC (Ubuntu 18.04, Kstars 3.5.0 Beta, and Indilib 1.8.6).
But when I connect the same camera to a Raspberry Pi 4 up-to-date ((Ubuntu 20.04, Kstars 3.5.0 Beta, and Indilib 1.8.6), the camera is not recognized : when I start Ekos, I've a message saying "QHY camera is not connected. Power on ?"
I've the same issue with another system (Odroid RC4, Ubuntu 18.04 & indilib 1.8.6). On this system, when I run the server manually (indiserver indi_qhy_ccd), I can see an error message when trying to connect Ekos : "Driver indi_qhy_ccd: SDK not support this camera now" (I don't see the same error with the Raspberry).
The only difference between working and not-working config is Raspberry vs desktop PC and Ubuntu 18.04 vs 20.04 (by the way, I've read on this forum that the Atik driver may work only with Ubuntu 20.04... and I've another camera - an Atik one - that I must run at the same time ; which means I need the QHY work in Ubuntu 20.04).
Any idea ? Any chance it can work ?
Thank you for all what you're doing - this is amazing.
François (Shelyak Instruments)
Ok, good to know. Thanks.
I will not upgrade my PC shortly, but the Indi server can be elswhere (on an RasPi, indeed). Then, I may work around the problem (I guess the problem with 16.04 is the Indi server, not Kstars - right ?).
I'll tell you if I still have problem. And if you want me to check a change on your side, jut ask.
You're right, I did not give a lot of informations. Sorry.
I'm working on a laptop PC, Ubuntu 16.04.
The test I did is purely local : Kstars running on my PC, and the Indi server as well.
It worked before (few weeks ago, at least), with the same PC. I'm not sure if the problem appeared when I did upgrade to Indi/Kstars new versions, or before.
You did an amazing job, really.
I'm still working to make my observatory work - thanks to the Indi & Kstars ecosystem - wonderful.
I'm facing a problem with the latest versions of Indi lib (1.7.6) and Kstars (3.1.1)
When starting Ekos, I've the following message - if an Atik camera is connected, or not.
KStars detected INDI driver indi_atik_ccd crashed. Please check INDI server log in the Device Manager.
Could you help me ?
I'm working to make my GM1000 mount work remotely - in my garden (ultimately in spectroscopy - I'm the manager of Shelyak Instruments).
I recently discovered Ekos & Kstars (you did an amazing job !), and want to use it with the Indi server on a Raspberry Pi close to the telescope.
All is working fine, but I face a problem with the GM1000 mount Indi driver : I've no access to the 'SLEW RATE' parameter, and can only move the telescope at full speed.
Did I miss something (= is there an alternate way to move the telescope at guiding speed) ?
Is it possible to contact the 10micron Indi driver author (Hans Lambermont, as given in the driver page) ?
Any help would be warmly welcome.