CapnRon wrote: So here is the real problem: When the equipment is working you can quickly gather more data than you can possibly analyze over the next month!
Welcome to the club Ron! It's lots of fun to capture as much as you can during clear nights and process gathered data while not capturing.
Regarding the crash... well it happens. KStars, Ekos and INDI drivers are under heavy development. The tend to be much stable than they used to be in the past.
Astroberry provides stable releases only. KStars 3.9.9 is stable. You can and you should update because INDI drivers have been updated in the meantime too. There's no easy way to downgrade though
If you really need to write files to remote disk, the approach suggested by @PDB is the way to go. I will add one thing to this - define static mount in your /etc/fstab pointing to your remote location and it will be available as a local directory after each boot. Note that following this route you can even write files to a cloud storage.
@wvreeven is right advising to keep the files as close to camera (actually INDI server) as possible, however if you connect RPi via 1Gb ethernet the latency should be marginal. Connecting via WiFi will introduce major delays during sessions. Feasible but hardly acceptable
Forget TeamViewer, just use AnyDesk
rmor51 wrote: It's OK, thank you. But it's odd that parameters to make dark or flats are taken into account for light images, isn't it?
An another issue. When cooling is on, after a while I have an error message: [ERROR] Cooling Info inquiry failed (3).
Thank for your help.
I do confirm that Atik 460EX throws [ERROR] Cooling Info inquiry failed (3) with indi-atik 2.4 and libatik 2.2.6
This means that you have never got fix from your real GPS. Instead you got fix from virtual GPS.
Are you testing this outside?
Oacapture provides own libraries and AFAIK does not (and did not in the past) use INDI libraries. I have suggested to author to use shared libraries provided by INDI but I don't think it was implemented. So there aocapture does not depend on INDI, and as the result of providing own libraries it conflicts with INDI and it always did eg. QHY libraries. It's not gonna change unless james (the author of oacapture) uses INDI libraries instead providing his own.
While using real GPS you need to disable virtualgps service.
Run in terminal:
sudo systemctl stop virtualgps sudo systemctl disable virtualgps
You only need it if you don't have real GPS connected to your system. If you do GPSD service reads both real and virtual GPSes, which is not what you want.
Dear All, could you please set up separate topics for separate issues?
Discussing each and every issue in a single topic makes it really hard for users to follow certain threads.
It can't be. There is no dependence between the two. This is just coincience
What's your version of astroberry-server-wui? To check it run: apt show astroberry-server-wui
Birthdate08. 05. 1974
About meAstronomy geek. Keen on electronics, new technologies, IoT. Cybersecurity professional. Full time CEO. Conference speaker and post-graduate teacher.
Astroberry Server core developer. Member of INDI development team.