Hi Claude - are you able to see the devices on the astroberry? Are you plugging it in directly or into a powered hub/astropowerbox? If you open a terminal and type "sudo lspci -t" you should be able to see if it's recognized by your computer. If you are running astroberry on a rpi4, try plugging it into the blue tabbed USB port (USB3).
I don't want to interfer with your discussion with Claude, but on my Rpi3 with astroberry intalled, (issue with an ASI294 MM not reconnized by Ekos ) I try your command "sudo lspci -t" which has not been reconised by my system ...This command is reconnized by Rasbian Buster ?
I have done some acquisition with the ASI294MM last night and I get systematic crach of KStar after some acquisition (from 3 or more up to 8...) ..(! aftrer reintalling the complet Buster + Astro berry) . I remove all equipement excepted this camera+EFW Filter and skysafari+ LX200 GPS.
My System is configured as ( Rapberry / Astro berry , Card =16Go) . On the 16Go , 2.3 are still available.
Is there any sombody that experiment aqcuisition on such configuration ?
Hi just found apparently in the FITS/Configurer - KSTAR the solution... When I made trial, I discovered a veery strange behaviour of the FITS image, there were zooming every time a acquistion was occuring...Exepted when I set the bining in4X4... At the same times, I have seen that in the FITS/Configurer - KSTAR, one option called "Adaptive Sampling " is used when the ressource of the system is reducing. So I uncheck this option and... no more crash over 50 acquisition ( 10R/10B/10G/10L)... Hoping this is the solution up to the next bug...
Hello JCastro - this sounds familiar to my early days with Astroberry. For me, it turned out to be a combination of a known hardware conflict between the USB3 chip and the 2.4GHz radio for wifi on my rpi4 (I know you're rpi3) and also that I was not using a decent powered USB hub (I had plugged everything into my 4 ports on the rpi).
Have you turned on your debugging logs in EKOS? The devs in this forum are quite good at reading these and discovering configuration conflicts or bugs.
Also you could look through your system logs to see if there are excessive USB resets or conflicts/timeouts. From a command prompt you could type "sudo dmesg | grep -i usb" (the vertical line is a pipe symbol usually shift + \ it's not the letter "i")
Hi Hank, The drivers I had originally, from years ago, did not include the new Camera I had bought (ASI294MM Pro). When I updated the Indi drivers, everything fell into place. I am not using Astroberry. I did a custom install of the Indi server on a Raspberry Pie 4 and I use the built in Wifi to connect remotely using SSH. I have a dedicated USB Hub and a dedicated Power supply for the Pie 4. I run the whole remote setup from a marine 12V battery. So everyone (Pie 4, mount, camera, guide scope, focuser, heaters, etc..) has plenty of power.
Hi Hank, sorry for my very late replay. Concerning the stability of the Astroberry set, I am thinking that the system have to be given for any set running well. Personnaly I get a Rpi3+ with 16Go that perharps is not enough, and the first feeling thta I get is a lot of adjustement to be done not to get crash of theINDI server.
Actualy, the best that I get is a 60 pictures in one sequence done without crash. When I try to restart the sequence, after some shoot the Indi crash...I have aslo notice that using ASTAP before a sequence, is if the solver failed some times, crash of the Indi sever is also frequent..
Perharps on windows the Indi systeme is more robust.. I didn't not try and will be of course interreseted to have your feed back on this setup.