i use the latest github src. When i want to update data (comets or asteroids) i receive the message below : Error downloading asteroids data: Data verification failed
what's the pi model ? I'm use since 2 (or 3)years a pi (3 and now 4) for controlling mount, camera, focuser, gps, ... without problem. But always through the ethernet connection (with a cpl box). I controlling my mount with Bluetooth.
I noticed with my pi3, that the wifi connection wasn't very speed and is for this reason i didn't used. I suggest you, in the fist time, to test directly with an ethernet cable.
you could use the cmake directive -DUSE_SYSTEM_LIBINDI=1 like this :
cmake -DCMAKE_INSTALL_PREFIX=/usr/local -DCMAKE_BUILD_TYPE=Release -DOPENSOURCE_ONLY=1 -DUSE_SYSTEM_CFITSIO=1 -DUSE_SYSTEM_LIBUSB=1 -DUSE_SYSTEM_EIGEN3=1 -DUSE_SYSTEM_LIBINDI=1 ..
Make sure you have define in LDFLAGS the complet path to the libindi (ex : export LDFLAGS="-L/usr/local/lib").
I just tested, and that work fine (i only tested with indi simulator).
i just see that wcslib and cfitsio are been updated. I tested kstars with and seam to work fine.
I just had a Datyson T7 color (asi 120 MC clone). Like most people know now, we must "flash" with a compatible firmware for working on linux. I downloaded form ZWO website the fwupdate program. But, sadly, for an unknown reason, the program crash (code dumped). I try to launch with root, but i have the same issue. I checked the libs inside the program with ldd for verifying that is use the good libs.
If anyone had the fwupdate program, could you test it ?
I am on ubuntu 20.04.02, kernel 5.4.0-77
i would like to know if anybody meet the same issue.
in my understanding of the local meridian placement, he must go from north to south passing through north pole. But when i look into the kstars sky map my meridian is misplaced and the transit time of stars doesn't match with the cross line. I have mean 90 seconds of shift.
i'm playing with the polar aligment routine (with indi simulator). Sometime that work, sometime not (kstars crash). I played with some configurations (essentially with 1-FastSolving and 7-MidSizedStars).
I attached the console capture (with the crash) and the separate astrometry log file.
I updated the stellarsolver lib this morning and kstars yesterday.
i just tested with astap (fresh installation) your image and all it's ok (it's ngc7000 region). Have you installed the V17 stars database ?
also, check the parameters in the alignment tab.
I have a the API documentation. Very poor but she has the credit to exist.
I will try to work on the ROI implementation.
I seen your code and seriously he is clean.
Also, Do you think it's a good idea to propose all behavior of the camera that are "forced" to be programming by users ?
good new ! the drivers work fine for me now. I had a problem with cfitsio. I removed the last cfitio from my /usr/local/lib for use the "official" package.
if you need help for coding or others things, i'm ready for help.
i quick feedback :
- compilation : ok
- launching : ok
2020-06-22T18:28:34: startup: indiserver -v ./indi_sv305_ccd indi_simulator_telescope
2020-06-22T18:28:34: Driver ./indi_sv305_ccd: pid=4571 rfd=3 wfd=6 efd=7
2020-06-22T18:28:34: Driver indi_simulator_telescope: pid=4572 rfd=4 wfd=9 efd=10
2020-06-22T18:28:34: listening to port 7624 on fd 5
2020-06-22T18:28:34: Driver indi_simulator_telescope: HaAxis: TrackRate 1, trackingRateDegSec 15.041067 arcsec
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on GPS Simulator.GEOGRAPHIC_COORD
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on GPS Simulator.TIME_UTC
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_PARK
2020-06-22T18:28:34: Driver indi_simulator_telescope: snooping on Dome Simulator.DOME_SHUTTER
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: Camera(s) found
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.EQUATORIAL_EOD_COORD
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.TELESCOPE_INFO
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.GEOGRAPHIC_COORD
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Telescope Simulator.TELESCOPE_PIER_SIDE
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Rotator Simulator.ABS_ROTATOR_ANGLE
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Focuser Simulator.ABS_FOCUS_POSITION
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on CCD Simulator.FILTER_SLOT
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on CCD Simulator.FILTER_NAME
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on SQM.SKY_QUALITY
2020-06-22T18:28:36: Driver ./indi_sv305_ccd: snooping on Focuser Simulator.FOCUS_ABSOLUTE_POSITION
but, i cannot see the sv305 driver into kstars if i start indi in local mode. But, i see it if i launch in remote on localhost. but when i try to shoot a picture, the counter decrease to 0 abs kstars crash. I tested with phd2 and i have the same behavior.
Do you have a idea ?