Thank you Eric. This would be a nice-to-have feature so I won't accidentally slew my mount (especially to some wierd position like pointing under the horizon) after platesolve.
Or may be in the UI, consider adding "Ask Me what to do", so this would pops-up, ask the user to make sure it only applies to the UI interactions.
Thanks for considering my suggestions!
Read More...
Hi everyone,
Can I set the default "Solver Action", like as "Sync" in the Solver module in Ekos?
The reason I'm doing this is that I mostly perform platesolve and sync where the telescope to point to, and then perform a goto to the target.
I was hoping I can set the "Sync" and save it as the default so every time I start Ekos it would start as "Sync" instead of "Slew To".
Thanks!
Read More...
Guys
I'm still stuck with the horizontal lines in the captured image on my 490ex. I tried to experiment a little bit using different OS and drivers: RPI3, RPI4, Ubuntu 16, 18, 19, Raspbian buster, etc.
Found only when I use cloudmakers Atik driver 1.17 (which is pretty old already) there're no horizontal lines.
When I use Cloudmakers 1.30, libatik (the new driver) both having the horizontal lines, at different position s though.
Short captures like 10 sec the lines are visible after autostretch. At long exposures like 300 sec the lines are not visible but I didn't stack them so I don't know if that'd affect the final output or not.
Can someone help please?
Stephen
Read More...
there's an FAQ in Atik website about the horizontal lines saying it's the USB transfer problem. I'm not sure if this is due to the USB in RPI4 causing this.
I tried ubuntu 19.10 kstars, raspbian. All same in RPI4.
www.atik-cameras.com/question/seeing-occ...lines-image-causing/
Read More...
Guys
I've installed the cloudmakers driver and note the differences on the lines. Two lines instead of 3.
I tried to see if this is a general problem by connecting to ZWO ASI camera and there're no lines in the image when it's taken from ZWO ASI
Read More...
Sorry for cross-posting
There found a few horizontal lines appearing in the images taken by the latest atik driver:
www.indilib.org/forum/ekos/5864-horizont...-indi-3rd-party.html
Read More...
I've compiled indi 3rd party from the source code and found that the captured image from my Atik 490ex contains 3 horizontal lines. See screen. This didn't happen in Artemis software nor the ppa distribution.
T
Any clues?
Read More...
Thanks I did went to the thread - yet it's kind of long. I managed to build the drivers and make the EKOS works.
I have to build indi-core from source too. Simply apt-get indi-bin would not work - some shared libraries/headers were not installed for building the 3rd party drivers.
Few basic tests: Looping frames in focus module with my Atik, no problem. Connect to Temma2, no problem.
Yet I've found there're 4 horizontal lines at the captured image of my Atik - It may be the driver problem.
Read More...
To solve the issue I also build and install indi-core from the source, then build the 3rd party drivers again.
Read More...
Hi everyone,
I was trying to build the 3rd party indi drivers in raspbian buster but I've encounter following errors:
error: ‘ccdBufferLock’ was not declared in this scope
Can somebody help?
pi@raspberrypi:~/Projects/build/indi-atik $ make -j4
[ 25%] Building CXX object CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o
[ 75%] Built target indi_atik_wheel
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp: In member function ‘bool ATIKCCD::grabImage()’:
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:10: error: ‘unique_lock’ is not a member of ‘std’
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~~~~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:10: note: ‘std::unique_lock’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:30:1:
+#include <mutex>
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:10:
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~~~~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:27: error: ‘mutex’ is not a member of ‘std’
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:27: note: ‘std::mutex’ is defined in header ‘<mutex>’; did you forget to ‘#include <mutex>’?
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:40: error: ‘ccdBufferLock’ was not declared in this scope
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~~~~~~~~~
/home/pi/Projects/indi-3rdparty/indi-atik/atik_ccd.cpp:843:34: error: ‘guard’ was not declared in this scope
std::unique_lock<std::mutex> guard(ccdBufferLock);
^~~~~
make[2]: *** [CMakeFiles/indi_atik_ccd.dir/build.make:63: CMakeFiles/indi_atik_ccd.dir/atik_ccd.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:110: CMakeFiles/indi_atik_ccd.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
pi@raspberrypi:~/Projects/build/indi-atik $
Read More...