I figured out the magic formula to key in RA values to work around this bug with the Flag Manager. Enter the hour, min and sec values each multiplied by 15. For example, "150 300 450" will create an entry of "10d 20m 30s" for RA. No change is needed for DEC. A screen shot is attached.
Read More...
I get a similar issue with the Flag Manager, attached pics shows an example. Only the RA field seems to generate the wrong value. I noticed this issue after I upgraded astroberry on my RPi4 on 2022-09-02.
Image1 shows the RA value of "21 14 1.8" keyed in, and when the add button is clicked the resulting value is "01h 24m 56s" (image2) which isn't close. I tried other formats such as "21h 14m 1.8s" and "21.23383" but also produced the same incorrect result. Clicking on the recorded entry causes the input fields to be refreshed, and that results in the same erroneous RA value of "01h 24m 56s" being displayed (image3). At this point, it is not possible to create flags.
Thanks, David W
Read More...
There was also a question about editing FITS headers...
I use the free bulk header editor F4W2HDU from astroshed.com
Read More...
I see the same issue, here's additional info if it helps.
The FITS header is correct for my guide camera & scope
PIXSIZE1 = 3.750000E+00 / Pixel Size 1 (microns)
FOCALLEN = 3.00E+02 / Focal Length (mm)
APTDIA = 3.00E+01 / Telescope diameter (mm)
SCALE = 2.578750E+00 / arcsecs per pixelThe FITS header is INCORRECT on 3 out of 4 values for my main camera & scope
PIXSIZE1 = 2.400000E+00 / Pixel Size 1 (microns) <= this is correct
FOCALLEN = 3.00E+02 / Focal Length (mm) <= should be 1260mm
APTDIA = 3.00E+01 / Telescope diameter (mm) <= should be 200mm
SCALE = 1.650400E+00 / arcsecs per pixel <= should be approx 0.4 arcsec per pixAttached is a screenshot of the Ekos telescope panel showing the correct scope values (focal length and aperture), and the Ekos debug log.
Read More...
Has the fix been pushed to other environments as well? I'm seeing this issue for a fresh build of RPi2 running Ubuntu Mate 15.10.1 (more details below)
Thanks, David
root@ubuntu15rpi2:~# apt-cache showpkg kstars-bleeding
Package: kstars-bleeding
Versions:
5:16.04+r5904.2598~ubuntu15.10.1 (/var/lib/apt/lists/ppa.launchpad.net_mutlaqja_ppa_ubuntu_dists_wily_main_binary-armhf_Packages) (/var/lib/dpkg/status)
GDB output
Program received signal SIGSEGV, Segmentation fault.
0x76ad591c in QSqlDatabase::open() ()
from /usr/lib/arm-linux-gnueabihf/libQt5Sql.so.5
root@ubuntu15rpi2:/etc# uname -a
Linux ubuntu15rpi2 4.1.15-v7+ #830 SMP Tue Dec 15 17:02:45 GMT 2015 armv7l armv7l armv7l GNU/Linux
Read More...
FYI...I opened #PKB-613-80090 with Celestron on Apr 19 about the 'h' command not working. No feedback yet.
Read More...
I decided to download the INDI code in an attempt to debug what the underlying issue might be. celestrondriver.cpp appeared to be the code for gathering the mount info and, with the help from a NexStar Communication Protocol doc, I identified the driver commands.
For the first message:
DEBUG 91.342043 sec : CMD (m)
DEBUG 91.364547 sec : RES (14 23)
WARNING 91.364775 sec : Unrecognized model (20).For the 2nd message:
DEBUG 91.474998 sec : CMD (h)
ERROR 96.477992 sec : Timeout errorThe only alternative I could think of was to remove the "h" command call from the code, and use the hard coded simulation values as the returned time/date. Doing this allowed the mount to be controlled, I was able to use the slew buttons to engage the mount motors, as well as choose objects in KStars and have the mount motors engaged to move to them. RA/Dec values were returned, though keep in mind this was only a test in my basement. I'm not sure what effect changing the code this way will have as far as the overall INDI code goes.
Read More...
I have VNC already running which I can set up to pass through my FW, is that good enough?
Read More...
Hummm, I have not used TeamViewer before. Let me check it out and see if I can get it working on the RPi.
Read More...
Hi, yes I see the same error each time I connect. Do the errors refer to date/time, or RA/DEC? And once I get these errors, the mount hand control freezes and I have to power cycle the mount to connect again. I do set the date/time in the initialization process when the mount is powered on, then start the connection with KStars.
Read More...