I now have 3.1.1 on the Mac and Ubuntu. Both systems still cause my my guidestar to move in a non-random almost linear direction (-3,-3) when dithering. I have it set to dither 3 pixels every three frames. But when I look at my resulting imagines (I did 30 exposures last night) every dither was 3 pixels movement to the upper left. So the whole image was off center by 30 pixels in that straight direction (up and left). I have to aligned my exposures every 30 minutes or so just to keep my target centered. While those few pixels are not huge, after a 3 hour session it is, and objects on the left side of the frame are moved off the frame.
↧
Dither still not moving in random direction - by: PK
↧
Advice re Astrophysics Experimental driver - by: Spartacus
Hi ,
The weather in Queensland, Australia has been terrible this weekend so I have been having another go at an abandoned KStars project.
I am currently using KStars/EKOS with an NEQ6 running EQMod for astrophotography with everything working fine. My son has an AP1100 and has recently left home and lucky for me has left me in charge of the AP1100 mount.
We tried to use KStars with the AP1100 about 12 months ago but gave up after a few months of frustration. This time I have a lot more knowledge and have managed to get it working pretty much perfectly apart from it insists on using DEC co-ordinate as 00:00:00 for Park 3 instead of -90:00:00. This puts the scope at 90 degrees to the mount axis. Generally Astrophysics Park 3 should point directly at the South Celestial Pole e.g. in line with the mount axis. Az co-ord is 180:00:00 for both of these positions so the co-ordinates showing in the park position in INDI is the same as this does not show DEC.
This is not necessarily an issue just a curiosity. Anyone know what I may be doing wrong? Otherwise in use the mount knows where it is and slews correctly and everything else works as expected which is great. I have tried doing a custom park but it always reverts to the DEC 00:00:00 setting.
Cheers
Mike
The weather in Queensland, Australia has been terrible this weekend so I have been having another go at an abandoned KStars project.
I am currently using KStars/EKOS with an NEQ6 running EQMod for astrophotography with everything working fine. My son has an AP1100 and has recently left home and lucky for me has left me in charge of the AP1100 mount.
We tried to use KStars with the AP1100 about 12 months ago but gave up after a few months of frustration. This time I have a lot more knowledge and have managed to get it working pretty much perfectly apart from it insists on using DEC co-ordinate as 00:00:00 for Park 3 instead of -90:00:00. This puts the scope at 90 degrees to the mount axis. Generally Astrophysics Park 3 should point directly at the South Celestial Pole e.g. in line with the mount axis. Az co-ord is 180:00:00 for both of these positions so the co-ordinates showing in the park position in INDI is the same as this does not show DEC.
This is not necessarily an issue just a curiosity. Anyone know what I may be doing wrong? Otherwise in use the mount knows where it is and slews correctly and everything else works as expected which is great. I have tried doing a custom park but it always reverts to the DEC 00:00:00 setting.
Cheers
Mike
↧
↧
novis help - by: adysastro
just getting into linux and indi so bear with me.
trying to set it up but keep getting the v4l2 crash box come up. I have updated the drivers what am i missing thanks
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Welcome to KStars 3.1.0
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Build: 2019-01-10T20:47:33Z
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - OS: "linuxmint"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - API: "x86_64-little_endian-lp64"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Arch: "x86_64"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Kernel Type: "linux"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Kernel Version: "4.15.0-45-generic"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Qt Version: 5.9.5
[2019-03-16T13:32:18.512 WET INFO ][ org.kde.kstars] - Processing "unnamedstars.dat" , HTMesh Level 3
[2019-03-16T13:32:18.512 WET INFO ][ org.kde.kstars] - Sky Mesh Size: 512
[2019-03-16T13:32:18.562 WET INFO ][ org.kde.kstars] - Loaded DSO catalog file: "unnamedstars.dat"
[2019-03-16T13:32:18.562 WET INFO ][ org.kde.kstars] - Processing "deepstars.dat" , HTMesh Level 3
[2019-03-16T13:32:18.562 WET INFO ][ org.kde.kstars] - Sky Mesh Size: 512
[2019-03-16T13:32:18.563 WET INFO ][ org.kde.kstars] - Loaded DSO catalog file: "deepstars.dat"
[2019-03-16T13:32:19.246 WET WARN ][ org.kde.kstars] - "Star HD20794 not found."
[2019-03-16T13:32:19.272 WET WARN ][ org.kde.kstars] - "Star HD98230 not found."
[2019-03-16T13:32:19.297 WET DEBG ][ default] - File opened: "/usr/share/kstars/ngcic.dat"
[2019-03-16T13:32:19.297 WET INFO ][ org.kde.kstars] - Loading NGC/IC objects
[2019-03-16T13:32:20.268 WET DEBG ][ default] - File opened: "/home/adrian/.local/share/kstars/comets.dat"
[2019-03-16T13:32:20.542 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.546 WET WARN ][ org.kde.kstars] - "Object named NGC 6050A not found"
[2019-03-16T13:32:20.546 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Quaoar (2002 LM60) not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Ceres not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Pallas not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Vesta not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Cybele not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Psyche not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Juno not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Themis not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Astraea not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Lumen not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Ida not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Mathilde not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Eros (1898 DQ) not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Hektor (1907 XM) not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Chiron (1977 UB) not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Halley (1982 HG1) not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Quaoar (2002 LM60) not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Ceres not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Pallas not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Vesta not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Cybele not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Psyche not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Juno not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Themis not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Astraea not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Lumen not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Ida not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Mathilde not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Eros (1898 DQ) not found"
[2019-03-16T13:32:20.591 WET WARN ][ org.kde.kstars] - "Object named Hektor (1907 XM) not found"
[2019-03-16T13:32:20.591 WET WARN ][ org.kde.kstars] - "Object named Chiron (1977 UB) not found"
[2019-03-16T13:32:20.591 WET WARN ][ org.kde.kstars] - "Object named Halley (1982 HG1) not found"
[2019-03-16T13:32:20.956 WET DEBG ][ qt5ct] - D-Bus global menu: no
[2019-03-16T13:32:21.702 WET DEBG ][ default] - glibc >= 2.1 detected. Using GNU extension sincos()
[2019-03-16T13:32:35.252 WET INFO ][ org.kde.kstars.ekos] - "Starting INDI services..."
[2019-03-16T13:32:35.387 WET INFO ][ org.kde.kstars.ekos] - "INDI services started on port 7624."
[2019-03-16T13:32:35.495 WET INFO ][ org.kde.kstars.ekos] - Ekos received a new device: Celestron NexStar
[2019-03-16T13:32:36.043 WET INFO ][ org.kde.kstars.ekos] - Ekos received a new device: V4L2 CCD
[2019-03-16T13:32:36.085 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Celestron NexStar is online. "
[2019-03-16T13:32:36.202 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Controller version: 4.21 "
[2019-03-16T13:32:39.603 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] V4L2 CCD Device is online. Initializing properties. "
[2019-03-16T13:32:39.603 WET INFO ][ org.kde.kstars.ekos] - All INDI devices are now connected.
[2019-03-16T13:32:39.807 WET INFO ][ org.kde.kstars.ekos.focus] - "Idle."
[2019-03-16T13:32:39.923 WET INFO ][ org.kde.kstars.ekos.align] - "Idle."
[2019-03-16T13:32:40.073 WET INFO ][ org.kde.kstars.ekos] - "V4L2 CCD is online."
[2019-03-16T13:32:40.255 WET CRIT ][ org.kde.kstars.indi] - INDI driver "indi_v4l2_ccd" crashed!
[2019-03-16T13:32:40.542 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] Found intial Input \"Camera 1\", Format \"Motion-JPEG\", Size 160x120, Frame interval 1/10s "
[2019-03-16T13:32:40.562 WET INFO ][ org.kde.kstars.ekos.align] - "World Coordinate System (WCS) is enabled. CCD rotation must be set either manually in the CCD driver or by solving an image before proceeding to capture any further images, otherwise the WCS information may be invalid."
[2019-03-16T13:32:40.584 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] Setting pixel size to default of 5.60 "
[2019-03-16T13:32:40.586 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] For future autodetection of pixel size, please report the following: Reported Name: 'UVC Camera (046d:08c1)', Common Name (Eg: NexImage 10), Pixel Size to the following thread: www.indilib.org/forum/ccds-dslrs/4392-indi-pixel-size-detectio "
[2019-03-16T13:32:40.591 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[ERROR] Serial read error: Timeout error "
[2019-03-16T13:32:40.605 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount model: Advanced GT "
[2019-03-16T13:32:40.677 WET INFO ][ org.kde.kstars.ekos] - "Celestron NexStar is online."
[2019-03-16T13:32:41.175 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount is unparked. "
[2019-03-16T13:32:41.214 WET INFO ][ org.kde.kstars.ekos] - "Guider port from Celestron NexStar is ready."
[2019-03-16T13:32:41.274 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount UTC offset is 0.00. UTC time is 2019-03-16T13:32:40 "
[2019-03-16T13:32:41.302 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Loading device configuration... "
[2019-03-16T13:32:41.359 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Pulse guiding is enabled. "
[2019-03-16T13:32:41.366 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Device configuration applied. "
[2019-03-16T13:32:41.369 WET INFO ][ org.kde.kstars.ekos.mount] - "Telescope info updated successfully."
[2019-03-16T13:32:41.408 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Saving device configuration... "
[2019-03-16T13:32:41.411 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Device configuration saved. "
trying to set it up but keep getting the v4l2 crash box come up. I have updated the drivers what am i missing thanks
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Welcome to KStars 3.1.0
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Build: 2019-01-10T20:47:33Z
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - OS: "linuxmint"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - API: "x86_64-little_endian-lp64"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Arch: "x86_64"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Kernel Type: "linux"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Kernel Version: "4.15.0-45-generic"
[2019-03-16T13:32:17.533 WET INFO ][ org.kde.kstars] - Qt Version: 5.9.5
[2019-03-16T13:32:18.512 WET INFO ][ org.kde.kstars] - Processing "unnamedstars.dat" , HTMesh Level 3
[2019-03-16T13:32:18.512 WET INFO ][ org.kde.kstars] - Sky Mesh Size: 512
[2019-03-16T13:32:18.562 WET INFO ][ org.kde.kstars] - Loaded DSO catalog file: "unnamedstars.dat"
[2019-03-16T13:32:18.562 WET INFO ][ org.kde.kstars] - Processing "deepstars.dat" , HTMesh Level 3
[2019-03-16T13:32:18.562 WET INFO ][ org.kde.kstars] - Sky Mesh Size: 512
[2019-03-16T13:32:18.563 WET INFO ][ org.kde.kstars] - Loaded DSO catalog file: "deepstars.dat"
[2019-03-16T13:32:19.246 WET WARN ][ org.kde.kstars] - "Star HD20794 not found."
[2019-03-16T13:32:19.272 WET WARN ][ org.kde.kstars] - "Star HD98230 not found."
[2019-03-16T13:32:19.297 WET DEBG ][ default] - File opened: "/usr/share/kstars/ngcic.dat"
[2019-03-16T13:32:19.297 WET INFO ][ org.kde.kstars] - Loading NGC/IC objects
[2019-03-16T13:32:20.268 WET DEBG ][ default] - File opened: "/home/adrian/.local/share/kstars/comets.dat"
[2019-03-16T13:32:20.542 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.546 WET WARN ][ org.kde.kstars] - "Object named NGC 6050A not found"
[2019-03-16T13:32:20.546 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.569 WET WARN ][ org.kde.kstars] - "Object named Quaoar (2002 LM60) not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Ceres not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Pallas not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Vesta not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Cybele not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Psyche not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Juno not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Themis not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Astraea not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Lumen not found"
[2019-03-16T13:32:20.570 WET WARN ][ org.kde.kstars] - "Object named Ida not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Mathilde not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Eros (1898 DQ) not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Hektor (1907 XM) not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Chiron (1977 UB) not found"
[2019-03-16T13:32:20.571 WET WARN ][ org.kde.kstars] - "Object named Halley (1982 HG1) not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Pluto not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Quaoar (2002 LM60) not found"
[2019-03-16T13:32:20.589 WET WARN ][ org.kde.kstars] - "Object named Ceres not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Pallas not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Vesta not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Cybele not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Psyche not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Juno not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Themis not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Astraea not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Lumen not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Ida not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Mathilde not found"
[2019-03-16T13:32:20.590 WET WARN ][ org.kde.kstars] - "Object named Eros (1898 DQ) not found"
[2019-03-16T13:32:20.591 WET WARN ][ org.kde.kstars] - "Object named Hektor (1907 XM) not found"
[2019-03-16T13:32:20.591 WET WARN ][ org.kde.kstars] - "Object named Chiron (1977 UB) not found"
[2019-03-16T13:32:20.591 WET WARN ][ org.kde.kstars] - "Object named Halley (1982 HG1) not found"
[2019-03-16T13:32:20.956 WET DEBG ][ qt5ct] - D-Bus global menu: no
[2019-03-16T13:32:21.702 WET DEBG ][ default] - glibc >= 2.1 detected. Using GNU extension sincos()
[2019-03-16T13:32:35.252 WET INFO ][ org.kde.kstars.ekos] - "Starting INDI services..."
[2019-03-16T13:32:35.387 WET INFO ][ org.kde.kstars.ekos] - "INDI services started on port 7624."
[2019-03-16T13:32:35.495 WET INFO ][ org.kde.kstars.ekos] - Ekos received a new device: Celestron NexStar
[2019-03-16T13:32:36.043 WET INFO ][ org.kde.kstars.ekos] - Ekos received a new device: V4L2 CCD
[2019-03-16T13:32:36.085 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Celestron NexStar is online. "
[2019-03-16T13:32:36.202 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Controller version: 4.21 "
[2019-03-16T13:32:39.603 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] V4L2 CCD Device is online. Initializing properties. "
[2019-03-16T13:32:39.603 WET INFO ][ org.kde.kstars.ekos] - All INDI devices are now connected.
[2019-03-16T13:32:39.807 WET INFO ][ org.kde.kstars.ekos.focus] - "Idle."
[2019-03-16T13:32:39.923 WET INFO ][ org.kde.kstars.ekos.align] - "Idle."
[2019-03-16T13:32:40.073 WET INFO ][ org.kde.kstars.ekos] - "V4L2 CCD is online."
[2019-03-16T13:32:40.255 WET CRIT ][ org.kde.kstars.indi] - INDI driver "indi_v4l2_ccd" crashed!
[2019-03-16T13:32:40.542 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] Found intial Input \"Camera 1\", Format \"Motion-JPEG\", Size 160x120, Frame interval 1/10s "
[2019-03-16T13:32:40.562 WET INFO ][ org.kde.kstars.ekos.align] - "World Coordinate System (WCS) is enabled. CCD rotation must be set either manually in the CCD driver or by solving an image before proceeding to capture any further images, otherwise the WCS information may be invalid."
[2019-03-16T13:32:40.584 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] Setting pixel size to default of 5.60 "
[2019-03-16T13:32:40.586 WET INFO ][ org.kde.kstars.indi] - V4L2 CCD : "[INFO] For future autodetection of pixel size, please report the following: Reported Name: 'UVC Camera (046d:08c1)', Common Name (Eg: NexImage 10), Pixel Size to the following thread: www.indilib.org/forum/ccds-dslrs/4392-indi-pixel-size-detectio "
[2019-03-16T13:32:40.591 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[ERROR] Serial read error: Timeout error "
[2019-03-16T13:32:40.605 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount model: Advanced GT "
[2019-03-16T13:32:40.677 WET INFO ][ org.kde.kstars.ekos] - "Celestron NexStar is online."
[2019-03-16T13:32:41.175 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount is unparked. "
[2019-03-16T13:32:41.214 WET INFO ][ org.kde.kstars.ekos] - "Guider port from Celestron NexStar is ready."
[2019-03-16T13:32:41.274 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Mount UTC offset is 0.00. UTC time is 2019-03-16T13:32:40 "
[2019-03-16T13:32:41.302 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Loading device configuration... "
[2019-03-16T13:32:41.359 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Pulse guiding is enabled. "
[2019-03-16T13:32:41.366 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Device configuration applied. "
[2019-03-16T13:32:41.369 WET INFO ][ org.kde.kstars.ekos.mount] - "Telescope info updated successfully."
[2019-03-16T13:32:41.408 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Saving device configuration... "
[2019-03-16T13:32:41.411 WET INFO ][ org.kde.kstars.indi] - Celestron NexStar : "[INFO] Device configuration saved. "
↧
What File Format for SD Card? - by: werper
I purchased the Stellarmate OS. What file format should I use for my SD card, before I flash the OS to the card?
↧
Adding a new device category? - by: Gregj888
I did quick search, but didn't get a hit.
What's involved with adding a new device category? I can fool the system into supporting an instrument selector by calling it a filter wheel, or by writing a script in EKOS. It would be nice to add it as an actual device though, as it would be less confusing.
Yes, I know none of the clients would initially support a new category, but some might over time.
There are two other instruments that would be nice to automate: an ADC and spectrometer. The spectrometer might be difficult as they can have more moving parts, but a few simple commands might be enough to get moving.
Thx,
What's involved with adding a new device category? I can fool the system into supporting an instrument selector by calling it a filter wheel, or by writing a script in EKOS. It would be nice to add it as an actual device though, as it would be less confusing.
Yes, I know none of the clients would initially support a new category, but some might over time.
There are two other instruments that would be nice to automate: an ADC and spectrometer. The spectrometer might be difficult as they can have more moving parts, but a few simple commands might be enough to get moving.
Thx,
↧
↧
How Do I Chain Two Stellarmates so They're Seen as One by Ekos? - by: werper
I would like to use two Stellarmates to improve performance. One would control a Canon T3i DSLR camera for imaging, the second would control the mount (iOptron iEQ45 Pro) and guiding using a QHY5-II-M camera. I came across instructions on how to do this so Ekos (running as a remote client on a PC) sees both Stellarmate boxes as one, but try as I might, I can't find it again. As I recall, there was a simple command line you key in and you're good to go...???
Thanks in advance!
Tom
Thanks in advance!
Tom
↧
Scheduler - by: hy
Last night the skies were finally clear, but we had guests for dinner. I had never used the scheduler before, and this seemed the perfect time for it.
I have no focuser (yet), and the mount was polar aligned the previous night, so all it had to do was unpark, slew/plate-solve/track, guide, capture and park.
I came home 30 minutes before my guests arrived, wrote the capture and scheduling files, and pushed play. I checked it out late that night after everyone had left...
It worked perfectly! Thanks so much for the very nice software.
Here are a few questions I have regarding the experience:
- I just had one capture job, so I set the scheduler to run the job at 8:30pm, about 90 minutes after sunset. Is there a "start when it gets dark" kind of option?
- I wasn't sure if I was supposed to connect to Indi or not after I pressed play in the scheduler (at 5:30pm 3 hours before the job was to really start). In the end, I chose not to manually connect to Indi, and it worked fine. Should it also have worked if I had left it connected? Hopefully it would work either way.
- I use Phd2 to guide. I started up Phd2 manually when I pushed play on the scheduler at 5:30pm (though it was obviously unconnected to the guide camera, since indi was not running). Is that the normal mode of operation? I suppose I could have written a script to start Phd2, but it seems easier this way.
- The scheduler required me to enter the RA and DEC of my target before it was happy with my job, even though I had entered a fits file to tell it where the target was. Since I didn't know the RA/DEC, I needed to start up the plate solver, solve my fits file, and feed that info into the text boxes. Seems like that's an unnecessary step (e.g. the scheduler could have done that too, or could have just solved it when it ran at 8:30). Is there a way to avoid that?
- I'd like to issue a command that states: "No matter what's happening, shut down and park at 4am" or something like that. The Mount tab has that functionality, but it clearly states not do use that functionality when using the scheduler. How can I make sure my telescope parks before sunrise?
Thanks again,
Hy
I have no focuser (yet), and the mount was polar aligned the previous night, so all it had to do was unpark, slew/plate-solve/track, guide, capture and park.
I came home 30 minutes before my guests arrived, wrote the capture and scheduling files, and pushed play. I checked it out late that night after everyone had left...
It worked perfectly! Thanks so much for the very nice software.
Here are a few questions I have regarding the experience:
- I just had one capture job, so I set the scheduler to run the job at 8:30pm, about 90 minutes after sunset. Is there a "start when it gets dark" kind of option?
- I wasn't sure if I was supposed to connect to Indi or not after I pressed play in the scheduler (at 5:30pm 3 hours before the job was to really start). In the end, I chose not to manually connect to Indi, and it worked fine. Should it also have worked if I had left it connected? Hopefully it would work either way.
- I use Phd2 to guide. I started up Phd2 manually when I pushed play on the scheduler at 5:30pm (though it was obviously unconnected to the guide camera, since indi was not running). Is that the normal mode of operation? I suppose I could have written a script to start Phd2, but it seems easier this way.
- The scheduler required me to enter the RA and DEC of my target before it was happy with my job, even though I had entered a fits file to tell it where the target was. Since I didn't know the RA/DEC, I needed to start up the plate solver, solve my fits file, and feed that info into the text boxes. Seems like that's an unnecessary step (e.g. the scheduler could have done that too, or could have just solved it when it ran at 8:30). Is there a way to avoid that?
- I'd like to issue a command that states: "No matter what's happening, shut down and park at 4am" or something like that. The Mount tab has that functionality, but it clearly states not do use that functionality when using the scheduler. How can I make sure my telescope parks before sunrise?
Thanks again,
Hy
↧
Fedora drivers for Altair CCDs - by: ebessant
Howdo all,
Can anyone tell me if there is a release date for the Altair drivers for the Altair Astro CCDs. I know that they are available for Ubuntu and StellarMate, both of which I have installations, but I really do prefer Fedora as the OS.
Thanks,
E.
Forum newbie
Can anyone tell me if there is a release date for the Altair drivers for the Altair Astro CCDs. I know that they are available for Ubuntu and StellarMate, both of which I have installations, but I really do prefer Fedora as the OS.
Thanks,
E.
Forum newbie
↧
Atlas EQ-G - by: freddylq
Hi guys. I'm trying to connect my Atlas EQ-G mount and seem to be having trouble connecting. I keep getting: [ERROR] Serial read error. Timeout error. I'm sure it's something dumb that I'm not doing correctly. I'm using an Aten UC232A USB to Serial adapter. That is connected to the RS-232 port on my hand controller. Can someone walk me through the proper settings on EKOS. I did set up a Mount Test profile in the Indi manager using the Synscan driver and started the server. I get the same error when I tried Skychart.
↧
↧
Re:How Do I Chain Two Stellarmates so They're Seen as One by Ekos? - by: werper
I would like to use two Stellarmates to improve performance. One would control a Canon T3i DSLR camera for imaging, the second would control the mount (iOptron iEQ45 Pro) and guiding using a QHY5-II-M camera. I came across instructions on how to do this so Ekos (running as a remote client on a PC) sees both Stellarmate boxes as one, but try as I might, I can't find it again. As I recall, there was a simple command line you key in and you're good to go...???
Thanks in advance!
Tom
Thanks in advance!
Tom
↧
Raspberry-Indi web- asi120mc usb2 (old) little problem........ - by: offshore
Greetings to the whole forum! I have a small problem that I hope someone will help me to solve it .... I explain: after a thousand adventures I managed to create a station with my raspberry p3 to control everything, like the mount, a celestron cg5 goto, the focuser made with arduino, the canon 70d camera, and the guide an asi 120mc usb2 (old) .... so .... if I attack everything on the computer (no raspberry) and use Kstars and Ekos ... EVERYTHING works great! I installed indi-web and everything you need to get the command remotely on the raspberry and for a 4-5 times (sessions) everything worked very well .... now I have a problem with the ASI guide .... at start the server recognizes it, loads everything and all the dots are green .... but as soon as I try to make a click with the asi .... time starts and stops at 0.01 blocking everything ... the ball on exposure turns yellow and I have to kill the program to get out and start again ... I'm getting crazy! because before it worked and now it is not going anymore ?? what can I check to get everything back as before? I state that I tried to reinstall ubuntu mate and all the software needed for raspberry 3 times! Help! thanks to those who can answer me!
PS
I am Italian and I do not speak or write in English ... for the translation of this text, Saint Google helped me!
PS
I am Italian and I do not speak or write in English ... for the translation of this text, Saint Google helped me!
↧
Raspberry-Indi web- asi120mc usb2 (old) little problem........ - by: offshore
Greetings to the whole forum! I have a small problem that I hope someone will help me to solve it .... I explain: after a thousand adventures I managed to create a station with my raspberry p3 to control everything, like the mount, a celestron cg5 goto, the focuser made with arduino, the canon 70d camera, and the guide an asi 120mc usb2 (old) .... so .... if I attack everything on the computer (no raspberry) and use Kstars and Ekos ... EVERYTHING works great! I installed indi-web and everything you need to get the command remotely on the raspberry and for a 4-5 times (sessions) everything worked very well .... now I have a problem with the ASI guide .... at start the server recognizes it, loads everything and all the dots are green .... but as soon as I try to make a click with the asi .... time starts and stops at 0.01 blocking everything ... the ball on exposure turns yellow and I have to kill the program to get out and start again ... I'm getting crazy! because before it worked and now it is not going anymore ?? what can I check to get everything back as before? I state that I tried to reinstall ubuntu mate and all the software needed for raspberry 3 times! Help! thanks to those who can answer me!
PS
I am Italian and I do not speak or write in English ... for the translation of this text, Saint Google helped me!
PS
I am Italian and I do not speak or write in English ... for the translation of this text, Saint Google helped me!
↧
SOLVED - Help!!! Anyone Running Two Stellarmates? - by: werper
I'm trying to get two Stellarmates (I bought the OS and have it installed on two identacle Raspberry Pis 3B's) to work together to distribute the load. No matter what I try, i can't seem to get it to work. When I start the camera server, i get a message :address already in use, even though I start it from a fresh system boot.
Here's my rig:
iOptron iEQ45 Pro mount
QHY5L-II-M guide camera
Canon T3i imaging camera
My rpi's are named (and added to each rpi and my remote PC's host file)
Primary: guide
Secondary: camera
Currently, I have the primary server running the guide camera and mount. The secondary server is running the imaging camera, but I don't really care which server does what, as long as it works .
Here are the exact commands / syntax I'm keying in:
1) Start secondary Indi server via MATE Terminal (camera):
indiserver -v indi_gphoto_ccd
(this gives me a message stating: bind: Address already in use) and I'm thinking is the source of my problem.
2) Start primary Indi server via MATE Terminal and chain to Secondary (camera):
indiserver -v indi_ieq_telescope indi_qhy_ccd "GPhoto CCD"@camera:7624
I've tried every possible combination I can think of and have even reversed primary and secondary server's roles with no luck. I have Ekos running on my remote PC and I can easily connect to one or the other server and the attached devices depending upon if I change the Host to guide or camera, but Ekos refuses to see the secondary server regardless of which one I have it set as.
Being a Linux noob, I'm out of ideas to try- I've been following these three posts here on Indilib for instructions but seem to be running in circles now:
indilib.org/forum/general/3788-running-a...o-imaging-setup.html
indilib.org/forum/wish-list/811-connecti...le-indi-servers.html
indilib.org/support/tutorials/159-indi-on-multiple-devices.html
Any idea what I'm doing wrong?
Thank you for any and all help you can offer!
Tom
Here's my rig:
iOptron iEQ45 Pro mount
QHY5L-II-M guide camera
Canon T3i imaging camera
My rpi's are named (and added to each rpi and my remote PC's host file)
Primary: guide
Secondary: camera
Currently, I have the primary server running the guide camera and mount. The secondary server is running the imaging camera, but I don't really care which server does what, as long as it works .
Here are the exact commands / syntax I'm keying in:
1) Start secondary Indi server via MATE Terminal (camera):
indiserver -v indi_gphoto_ccd
(this gives me a message stating: bind: Address already in use) and I'm thinking is the source of my problem.
2) Start primary Indi server via MATE Terminal and chain to Secondary (camera):
indiserver -v indi_ieq_telescope indi_qhy_ccd "GPhoto CCD"@camera:7624
I've tried every possible combination I can think of and have even reversed primary and secondary server's roles with no luck. I have Ekos running on my remote PC and I can easily connect to one or the other server and the attached devices depending upon if I change the Host to guide or camera, but Ekos refuses to see the secondary server regardless of which one I have it set as.
Being a Linux noob, I'm out of ideas to try- I've been following these three posts here on Indilib for instructions but seem to be running in circles now:
indilib.org/forum/general/3788-running-a...o-imaging-setup.html
indilib.org/forum/wish-list/811-connecti...le-indi-servers.html
indilib.org/support/tutorials/159-indi-on-multiple-devices.html
Any idea what I'm doing wrong?
Thank you for any and all help you can offer!
Tom
↧
↧
SOLVED - How Do I Chain Two Stellarmates so They're Seen as One by Ekos? - by: werper
I would like to use two Stellarmates to improve performance. One would control a Canon T3i DSLR camera for imaging, the second would control the mount (iOptron iEQ45 Pro) and guiding using a QHY5-II-M camera. I came across instructions on how to do this so Ekos (running as a remote client on a PC) sees both Stellarmate boxes as one, but try as I might, I can't find it again. As I recall, there was a simple command line you key in and you're good to go...???
Thanks in advance!
Tom
Thanks in advance!
Tom
↧
I'll try again: how do I turn OFF auto debayer. - by: Ron Kramer
With my mono camera it's trying to debayer!!???
I see no off option only method and filter pattern. My MONO camera is giving me random colors. Here's a shot while it's still light out (at the trees)
I had various colors of the stars last night and couldn't turn it off?
![cantdebayer.JPG]()
I see no off option only method and filter pattern. My MONO camera is giving me random colors. Here's a shot while it's still light out (at the trees)
I had various colors of the stars last night and couldn't turn it off?
↧
INDI (kstars 3.0-El Capitan) cannot connect to the telescope mount - by: Fivel
Hello.
Using kstars 3.0 and the INDI control panel, I can get connections to all my other devices, except the telescope mount.
The error I get is "Error reading from device READ ERROR: Resource is temporarily unavailable (-1)".
Here is my setup for the mount and INDI/Ekos.
1. The mount is Losmandy Gemini
2. Connection method is via an Ethernet cable, from my computer, to the Gemini controller.
3. The Device address (IP) is 192.168.0.111
4. I don't know what port to enter, I tried 4030 (SkySafari uses it to connect when stand alone), 9472 and 9624 (SkySafari port via INDI), and 7624 (SkySafari Indi server port).
5. Also, do I use (tried both) TCP or UDP?
SkySafari stand alone can connect with no issues.
I thought I saw a similar post before, but cannot find it.
Please advise.
Thanks.
Fivel
Using kstars 3.0 and the INDI control panel, I can get connections to all my other devices, except the telescope mount.
The error I get is "Error reading from device READ ERROR: Resource is temporarily unavailable (-1)".
Here is my setup for the mount and INDI/Ekos.
1. The mount is Losmandy Gemini
2. Connection method is via an Ethernet cable, from my computer, to the Gemini controller.
3. The Device address (IP) is 192.168.0.111
4. I don't know what port to enter, I tried 4030 (SkySafari uses it to connect when stand alone), 9472 and 9624 (SkySafari port via INDI), and 7624 (SkySafari Indi server port).
5. Also, do I use (tried both) TCP or UDP?
SkySafari stand alone can connect with no issues.
I thought I saw a similar post before, but cannot find it.
Please advise.
Thanks.
Fivel
↧
Pentax K-5 always adds 2 seconds to the selected exposure time - by: djones
Hello,
i am facing a problem with my Pentax K-5 connected to the stellarmate gadget. Every exposure in EKOS (either in the capture, alignment, or focus module) results in a shot with 2s+selected exposure time. So if i want to make an 1s exposure the result is an 2s+1s = 3s exposure. This is quite annoying and makes it impossible to create bias or flat frames and to be honest anything else.
Please see the attached logfile from an 1s and 0.2s exposure
i am facing a problem with my Pentax K-5 connected to the stellarmate gadget. Every exposure in EKOS (either in the capture, alignment, or focus module) results in a shot with 2s+selected exposure time. So if i want to make an 1s exposure the result is an 2s+1s = 3s exposure. This is quite annoying and makes it impossible to create bias or flat frames and to be honest anything else.
Please see the attached logfile from an 1s and 0.2s exposure
↧
↧
I can not disable the automatic mount of my dslr on tinker board - by: lizardman
Hi, I'm new in this forum.
I have a little problem, I use a tinker board (with NAFABox, Ubuntu Mate Bionic, Armhf ) to take pictures with my DSLR (a Nikon D3400 ID: 04b0:043d ) but when I plug my USB cable for connecting the DSLR to my Tinkerboard, the DSLR was automatically mount. But for use Qdslrdashboard or Indi the DSLR should be unmount...
How to disable automout?
Thanks
I have a little problem, I use a tinker board (with NAFABox, Ubuntu Mate Bionic, Armhf ) to take pictures with my DSLR (a Nikon D3400 ID: 04b0:043d ) but when I plug my USB cable for connecting the DSLR to my Tinkerboard, the DSLR was automatically mount. But for use Qdslrdashboard or Indi the DSLR should be unmount...
How to disable automout?
Thanks
↧
Newbie with Canon T1i/500D problem - by: markcasazza
I am using the Astroberry image and I have my EQ-G mount, Meade DSI camera and Rigel nStep working. My Canon T1i is not responding to "preview" requests in CCD Ceil. In playing around I can get the shutter to open and close by pressing the "PC" button in the "output" row of the "settings" tab and close again by clicking "Off" inside the INDI Settings panel. When I go into Debug mode I get a message to "Please update the CCD information in the Image Info section before proceeding" I tried putting my number in and pressing "Set" the numbers disappeared and I still cannot take a test shot. What am I missing? Is there s setup procedure I need to perform?
↧
How to focus in Ha? - by: mlarsson
Hi!
I'm nowadays trying to learn how to do narrowband imaging, instead of using a DSLR. I am using an Atik 383l+. And I experience challenges in focusing in Ha-channel, more so for some objects rather than others. And I do have a quite long focal length, 1000 mm, f/9. The focus modul has dificulties identifying reliable stars, and it often lands out of focus. So I am looking for advice on how to manage this. What is a good strategy? Increasing exposure time makes the focusing more vulnerable to guiding errors etc. Is binning a better idea, or does that degrade the stars so focusing are more imprecise? I've been playing with both strategies, not really finding a good solution. I have also tried full frame focusing, but no improvement there.
Any advice from the rest of you, more experienced with Ha imaging?
Magnus
I'm nowadays trying to learn how to do narrowband imaging, instead of using a DSLR. I am using an Atik 383l+. And I experience challenges in focusing in Ha-channel, more so for some objects rather than others. And I do have a quite long focal length, 1000 mm, f/9. The focus modul has dificulties identifying reliable stars, and it often lands out of focus. So I am looking for advice on how to manage this. What is a good strategy? Increasing exposure time makes the focusing more vulnerable to guiding errors etc. Is binning a better idea, or does that degrade the stars so focusing are more imprecise? I've been playing with both strategies, not really finding a good solution. I have also tried full frame focusing, but no improvement there.
Any advice from the rest of you, more experienced with Ha imaging?
Magnus
↧