Awesome!! most wanted feature!!!
I was attempting to use pyindi-client to get a specific type of devices from the indi server.
What I'm trying to do is to mount the lsm303d to the telescope OTA, and roughly line up its position pointing to the sky and sync its alt/az to the connected telescope device. So I can speed up the plate-solving by populating the coordinates the telescope is (roughly) pointing to, to the Ekos plate-solving module.
I've found this in the C++ lib but seemed the pyindi-client do not have an interface to it?
bool INDI::BaseClient::getDevices ( std::vector< INDI::BaseDevice * > & deviceList, uint16_t driverInterface )
I was able to see in PyIndi.py that certain enum were defined. But I'm not sure how to use them. Any clues?
INDI_DEVICE_NOT_FOUND = _PyIndi.BaseDevice_INDI_DEVICE_NOT_FOUND
INDI_PROPERTY_INVALID = _PyIndi.BaseDevice_INDI_PROPERTY_INVALID
INDI_PROPERTY_DUPLICATED = _PyIndi.BaseDevice_INDI_PROPERTY_DUPLICATED
INDI_DISPATCH_ERROR = _PyIndi.BaseDevice_INDI_DISPATCH_ERROR
GENERAL_INTERFACE = _PyIndi.BaseDevice_GENERAL_INTERFACE
TELESCOPE_INTERFACE = _PyIndi.BaseDevice_TELESCOPE_INTERFACE
CCD_INTERFACE = _PyIndi.BaseDevice_CCD_INTERFACE
GUIDER_INTERFACE = _PyIndi.BaseDevice_GUIDER_INTERFACE
FOCUSER_INTERFACE = _PyIndi.BaseDevice_FOCUSER_INTERFACE
FILTER_INTERFACE = _PyIndi.BaseDevice_FILTER_INTERFACE
DOME_INTERFACE = _PyIndi.BaseDevice_DOME_INTERFACE
GPS_INTERFACE = _PyIndi.BaseDevice_GPS_INTERFACE
WEATHER_INTERFACE = _PyIndi.BaseDevice_WEATHER_INTERFACE
AO_INTERFACE = _PyIndi.BaseDevice_AO_INTERFACE
DUSTCAP_INTERFACE = _PyIndi.BaseDevice_DUSTCAP_INTERFACE
LIGHTBOX_INTERFACE = _PyIndi.BaseDevice_LIGHTBOX_INTERFACE
DETECTOR_INTERFACE = _PyIndi.BaseDevice_DETECTOR_INTERFACE
ROTATOR_INTERFACE = _PyIndi.BaseDevice_ROTATOR_INTERFACE
SPECTROGRAPH_INTERFACE = _PyIndi.BaseDevice_SPECTROGRAPH_INTERFACE
AUX_INTERFACE = _PyIndi.BaseDevice_AUX_INTERFACE
OK. I've located the problem:
1. I did messed up the FOV - Thanks wvreeven
2. EKOS is not passing parameters to solve-field (well at least at "Load & Slew"). I did point the telescope simulator close to the targets, specifies the FOV. And then I've found from the log that the -3, -4, -5 params are not passed - this caused the solver to do a blind solve. In the options I did find the params are correct. Just somehow it's not being sent to the solve-field command. See screen cap. If I run the same command myself at the shell, by adding the -3, -4, -5, the solver is able to get the result in 90 seconds.
Ubuntu 16.04 on RPI 3
Kstar version 2.9.6
KDE framework 5.18.0
I was trying to use the offline platesolving (astrometry 0.67) with my Raspberry Pi 3 on ubuntu 16.04. I've found the offline platesolver is very very slow and run into timeout. I used a FITS file captured with my Atik 490EX (with Tak 85ED with 0.67 reducer) and load it with "Load & Slew" to test. See below logs.
If I use the online platesolver that's no problem. I saw from other posts saying a RPI3 usually takes 30-60 secs to solve, if it's offline. But you can see from the log it takes a lot of time on certain steps. Is it normal?
2018-10-31T22:52:40 Solver aborted after 360 seconds
2018-10-31T22:49:05 Field 1 did not solve (index index-4209.fits, field objects 1-10).
2018-10-31T22:49:04 Field 1 did not solve (index index-4210.fits, field objects 1-10).
2018-10-31T22:49:04 Field 1 did not solve (index index-4211.fits, field objects 1-10).
2018-10-31T22:48:09 Reading file "/home/ubuntu/Light_005.axy"...
2018-10-31T22:48:04 Reading sort column "FLUX"
Sorting sort column
mmapping input file
Copying table header.
Writing row 0
2018-10-31T22:48:00 simplexy: found 2131 sources.
2018-10-31T22:46:48 Extracting sources...
2018-10-31T22:46:41 Reading input file 1 of 1: "/home/ubuntu/Light_005.fits"...
2018-10-31T22:46:41 /usr/bin/solve-field -O --no-plots --no-verify --resort --no-fits2fits --config /etc/astrometry.cfg -W /tmp/solution.wcs /home/ubuntu/Light_005.fits
2018-10-31T22:46:41 Starting solver...
2018-10-31T22:46:41 Solver iteration #1
Assuming I have captured a FITS file on disk. Can I specify the CCD simulator to load the FITS as simulate the image capturing?
What I'm trying to do is to test the offline platesolving in EKOS.
I have very limited time in image capturing session on the field, so I just want to test the offline platesolving, making sure it would work when I'm on the field.
I have the same issue
I am using Raspbian and I build the Kstars myself from the pi3.
The icons are critical to me. When I focus using the focus frame, I need to zoom in/out, and enable/disable the star circles. Now the screen shows the "text" on the buttons, but the window is not large enough to display all the text. Meanwhile if it's the icon, it's a small square box which I can see the icons without problems.
yes I saw that button, and able to switch it off. Yet I do this in a separate ubuntu, not raspbian. Anyway issue is resolved. Thank you!