What's this ?
..
[2022-12-20T19:26:20.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:20.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:21.301 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:21.301 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:22.301 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:22.301 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:23.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:23.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:24.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:24.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:25.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:25.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:26.301 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:26.301 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:27.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:27.301 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:28.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
[2022-12-20T19:26:28.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Slewing stage...
[2022-12-20T19:26:29.300 CET DEBG ][ org.kde.kstars.ekos.scheduler] - Mount State changed to 2
..
..and the scheduler does not go to the next step !!
Read More...
Same here, scheduler remain in "Rotation" and not switch to Alignment.
I return to solid 3.6.0 version
Read More...
Hi, with last indi git and kstars 3.6.0 beta driver canon crash.
Read More...
Hi, I'm testing the new version 3.5.9
The Scheduler seems to change the name of the directory (object) and always saves the object with name 001 (overwriting itself)
For example, the object is an asteroid (2022 KV) the set name is "asteroid" and set the acquisition of 20 images of 10 seconds
Scheduler make two directory "2022 KV" and "_2022_KV", and save all 20 images captured in directory _2022_KV with same name asteroid_Light_001.fits
Next day test other and save log. For now the night session went bad.
P.S.
Is my problem? have to set other in options?
3.5.8 work ok!!
Read More...
You're right, sorry, the problem occurs both connected via wifi and directly via a network cable (when I have fast asteroids to "capture" I need a fast transfer of the images to the pc and with the network cable it happens in less than a second) otherwise I use wifi, the pc acts as a hotspt and the raspberry connects. In any case via VNC.
I took a powered usb hub and a 5 meter usb cable and it works fine, so I will use this configuration for now.
Thanks bye.
Read More...
Hi, Usually i use kstars from my computer with a usb cable, now i tried to run kstars directly remotely on the raspberry with raspbian OS.
Unfortunately it closes almost immediately to the alignment, if it manages to pass the alignment it closes after a few captured images.
But is it really possible to use Raspberry remotely? Or is it just me crashing all the time? ( I think it's time to switch to stellarmate )
I attach log.
In the next few days, weather permitting, I will do other tests.
Read More...