I think that I found a problem in the sequence editor: if you create a sequence with Fits file reference for coordinate for the first target and with no fits file for a second target, but explicit coordinate, after saving and opening again the sequence file, the second target slew to the .fits position of the first target, ruining the sequence.
Step to reproduce:
Create a sequence with a first target with any sequence.
Fill the FITS field with an existing file.
Apply job changes
Clear the FITS field, load the coordinates fields with the actual position of the Kstars
Create a new target with the "+"
Select the two target and verify that the fields are correct (FITS field is filled only for the first target)
Save the sequence with a "test1" name
Check with an editor that the file test1.esl contains the FITS keyword only in the first target
Load the "test1"
Now the FITS file name is present in both target.
Save with a "test2" file name
The FITS file name is now present in both target also on file.
If you run that sequence, on the second target, the mount will slew first to the explicit coordinates, align, and then solve and slew on the FITS coordinates.
Let me know if I'm doing something wrong, I'm quite new of the Kstar/Ekos environment.
(Ive the logs and analyze files available, if needed)
Thanks
Paolo
Read More...
OK I realize that I was compiling from sources Kstars, but not the INDI library. I had to learn how to get the Astromechfoc sources from Git, and compile.
Now I've the 0.2 running and the problem it's solved!
Thanks for the help, and sorry for the mess about the version, but I'm new of the linux environment and still under de-tox after 20 years of Windows...
paolo
Read More...
Somtings wrong here: the version returned from the driver is 1.0....
Anyway the log is attached:
at 22:24:15 I try to change the values, but the GUI was blocked, no editing or focus to the field.
Between 22:24:46 and 22:24:48 I started and stopped the Autofocus.
at 22:25:06 I was able to edit and change the values.
Read More...
I'm running on RPi4 compiling from source, driving an Astromechanics focuser.
After start up the Initial Step Size and the Max Travel in the Guide module are 0 and cannot be changed.
The only way is to start an Autofocus and immediately stopping it (if will fail anyway because the Max Travel is at 0).
Not a big deal, but annoying. Note that with simulator all is OK and the value can be changed at any time.
The log is not reporting anythings strange.
Any suggestion? That's happening with other driver?
Thanks
paolo
Read More...
Hello everybody, new in this embedded "galaxy"...
I'm running the last stable 3.4.3 on a Rpi4 under Raspbian Buster (setted up with AstroPi3) and now I would like to test some new feature available in the nightly build of Ekos.
I've searched but looks like that the installable package are not available for my machine. Is that correct, or there is a ppa that I missed?
If not available, I will jump on the next step and build from sources, but I was trying to delay that step being a little "rusty" on the Linux environment!
Thanks for any help
Paolo
Read More...