On ARM64, KStars version is always the 3.6.6 and not 3.6.7 is thi normal? libqhy is dated 08-2023 but ii see that is present a new SDK on ther site dated 23.09.06.
I was unable to find this new file naming option
Read More...
On ARM64, KStars version is always the 3.6.6 and not 3.6.7 is thi normal? libqhy is dated 08-2023 but ii see that is present a new SDK on ther site dated 23.09.06
Read More...
Packages are for bullseye, RaspbianOS 64 bit is bullseye version, the new bookworm is not officially released, just take a look at the official RaspbianOS site
www.raspberrypi.com/software/operating-s...spberry-pi-os-64-bit
Read More...
ok but TSL237 sensor is not compatible with esp32, you can use TSL2591, that i not the same as precision
Read More...
If you are using a gued focal of 800mm, a pulse of 1000 is too high. Setting must be adapted to the guide setup not to the imaging one.
Also increase the Max interation to 7, and in the Calibration tab configure the RA aggressive to 0.70 and DEC to 1.00
Read More...
The problem is not limitaed only to Stellarmate but I have the same on my Raspbian. Date and time is only updated in KStars, but not in the system
Read More...
Actually I do not have under my hands my 183M to check what I see, but my camerta works with latest version. I do not rember if the udev rules has been deprecated or not.
The goal is that now you have all working
Read More...
sorry, after the -D must be specified the $env{DEVNAME}. Actually I do not remebere how is the format.
I have only MTP related warning but it is normal
Read More...
Try to execute manually the command /sbin/fxload -t fx3 -I /lib/firmware/qhy/QHY268.img -D
Also look at the correct path of fxload and firmware folder.
Probably there is a qhyccd.rules that recal this command and path are not correct, for example my fxload is located at usr/bin/fxload.
For the wifi .... i do not know how but there could be problems with interferences. When I connect the USB3.0 i lost the GPS fix
Read More...