↧
Focal length mismatch in plate solving? - by: mgutierrez
↧
collapsed log area - HELP! - by: dmsummers
I managed to get this collapsed accidently. Now I have no message area at the bottom of the display. All I have is 3 dots and they don't seem to re-expand. Can someone clue me in as how to do this? Shouldn't this be fixed permanently so it can't do this?
↧
↧
Auto-generate darkflat sequence after taking flats. - by: Bart
Currently, after taking flats with the automated exposure time setting, I take darkflats which have to have the same integration time.
This integration time then has to be set manually in a new sequence of darks, which is a bit cumbersome, while (I suppose) the sequence for this could easily be generated by EKOS at the end of an automated flats recording session.
Something like a 'generate Darkflats sequence' checkbox in the calibrate menu?
Cheers!
This integration time then has to be set manually in a new sequence of darks, which is a bit cumbersome, while (I suppose) the sequence for this could easily be generated by EKOS at the end of an automated flats recording session.
Something like a 'generate Darkflats sequence' checkbox in the calibrate menu?
Cheers!
↧
Astrobery upgrade problem from rpi3 to rpi4: eqmod cyclically reconnects - by: Dimitrii
Hello there. I have astroberry on rpi3 and it works well with my setup. Trying to upgrade to rpi4 8gb/64 class10 and there is a problem with connection to eqmod mount (I have az-eq6).
I disconnect all equipment including hub etc except mount, connect eqmod cable direct to rpi usb2 port. It connects and after ~30sec goes to reconnect.
I changed different power supplies for rpi4 5v 3a, nothing changed. When I connect to usb3 or another usb2 port ekos doesn't see mount at all. Only one port on rpi works but with cycle reconnect.
Astrberry image is up to date and upgraded/updated. Also added astroberry to dialout group.
Is the problem with rpi4 ports or eqmod cable (it is chinees noname but works great in windows10 and rpi3)?
I'm not fluence in linux, logs attached. Appreciate your advise.
2021-03-14T08:21:55: [INFO] EQMod Mount is online.
2021-03-14T08:21:55: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:54: [INFO] Device configuration saved.
2021-03-14T08:21:54: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Setting UTC Time to 2021-03-14T08:21:08, Offset 3
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration applied.
2021-03-14T08:21:53: [INFO] Setting LED brightness to 255
2021-03-14T08:21:53: [INFO] Inverting Declination Axis.
2021-03-14T08:21:53: [INFO] EQMod Mount is offline.
2021-03-14T08:21:23: [ERROR] Error: Communication failed -> tty read failed, check connection: Timeout error
2021-03-14T08:21:08: [INFO] Setting pulse limits: minimum pulse 10 ms, minimum timer pulse 100 ms
2021-03-14T08:21:08: [INFO] Setting Custom Tracking Rates - RA=0.5 arcsec/s DE=0.5 arcsec/s
2021-03-14T08:21:08: [INFO] Use Backlash : RA: False, DE: False
2021-03-14T08:21:08: [INFO] Setting Backlash compensation - RA=10 microsteps DE=10 microsteps
2021-03-14T08:21:08: [INFO] Observer location updated: Latitude 55:46:00.1 (55.7667) Longitude 37:40:00.1 (37.6667)
2021-03-14T08:21:08: [INFO] updateLocation: long = 37.6667 lat = 55.7667
2021-03-14T08:21:08: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state.
2021-03-14T08:21:08: [INFO] Loading device configuration...
2021-03-14T08:21:07: [WARNING] Can not load HorizonLimits Data File ~/.indi/HorizonData.txt: No such file or directory
2021-03-14T08:21:07: [INFO] updateLocation: long = 0 lat = 0
2021-03-14T08:21:07: [INFO] Mount is unparked.
2021-03-14T08:21:07: [WARNING] Init() : Setting both ST4 guide rates to 0.5x (2)
2021-03-14T08:21:07: [WARNING] Init() : First Initialization for this driver instance
2021-03-14T08:21:07: [WARNING] Init() : Setting default Init steps -- RAInit=8388608 DEInit = 8388608
2021-03-14T08:21:07: [WARNING] Init() : Motors already initialized
2021-03-14T08:21:07: [INFO] Mount has PPEC.
2021-03-14T08:21:06: [INFO] Mount has auxiliary encoders. Turning them off.
2021-03-14T08:21:06: [INFO] EQMod Mount is online.
2021-03-14T08:21:06: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:06: [INFO] Debug is enabled.
2021-03-14T08:21:55: [INFO] EQMod Mount is online.
2021-03-14T08:21:55: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:54: [INFO] Device configuration saved.
2021-03-14T08:21:54: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Setting UTC Time to 2021-03-14T08:21:08, Offset 3
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration applied.
2021-03-14T08:21:53: [INFO] Setting LED brightness to 255
2021-03-14T08:21:53: [INFO] Inverting Declination Axis.
2021-03-14T08:21:53: [INFO] EQMod Mount is offline.
2021-03-14T08:21:23: [ERROR] Error: Communication failed -> tty read failed, check connection: Timeout error
2021-03-14T08:21:08: [INFO] Setting pulse limits: minimum pulse 10 ms, minimum timer pulse 100 ms
2021-03-14T08:21:08: [INFO] Setting Custom Tracking Rates - RA=0.5 arcsec/s DE=0.5 arcsec/s
2021-03-14T08:21:08: [INFO] Use Backlash : RA: False, DE: False
2021-03-14T08:21:08: [INFO] Setting Backlash compensation - RA=10 microsteps DE=10 microsteps
2021-03-14T08:21:08: [INFO] Observer location updated: Latitude 55:46:00.1 (55.7667) Longitude 37:40:00.1 (37.6667)
2021-03-14T08:21:08: [INFO] updateLocation: long = 37.6667 lat = 55.7667
2021-03-14T08:21:08: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state.
2021-03-14T08:21:08: [INFO] Loading device configuration...
2021-03-14T08:21:07: [WARNING] Can not load HorizonLimits Data File ~/.indi/HorizonData.txt: No such file or directory
2021-03-14T08:21:07: [INFO] updateLocation: long = 0 lat = 0
2021-03-14T08:21:07: [INFO] Mount is unparked.
2021-03-14T08:21:07: [WARNING] Init() : Setting both ST4 guide rates to 0.5x (2)
2021-03-14T08:21:07: [WARNING] Init() : First Initialization for this driver instance
2021-03-14T08:21:07: [WARNING] Init() : Setting default Init steps -- RAInit=8388608 DEInit = 8388608
2021-03-14T08:21:07: [WARNING] Init() : Motors already initialized
2021-03-14T08:21:07: [INFO] Mount has PPEC.
2021-03-14T08:21:06: [INFO] Mount has auxiliary encoders. Turning them off.
2021-03-14T08:21:06: [INFO] EQMod Mount is online.
2021-03-14T08:21:06: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:06: [INFO] Debug is enabled.
I disconnect all equipment including hub etc except mount, connect eqmod cable direct to rpi usb2 port. It connects and after ~30sec goes to reconnect.
I changed different power supplies for rpi4 5v 3a, nothing changed. When I connect to usb3 or another usb2 port ekos doesn't see mount at all. Only one port on rpi works but with cycle reconnect.
Astrberry image is up to date and upgraded/updated. Also added astroberry to dialout group.
Is the problem with rpi4 ports or eqmod cable (it is chinees noname but works great in windows10 and rpi3)?
I'm not fluence in linux, logs attached. Appreciate your advise.
2021-03-14T08:21:55: [INFO] EQMod Mount is online.
2021-03-14T08:21:55: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:54: [INFO] Device configuration saved.
2021-03-14T08:21:54: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Setting UTC Time to 2021-03-14T08:21:08, Offset 3
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration applied.
2021-03-14T08:21:53: [INFO] Setting LED brightness to 255
2021-03-14T08:21:53: [INFO] Inverting Declination Axis.
2021-03-14T08:21:53: [INFO] EQMod Mount is offline.
2021-03-14T08:21:23: [ERROR] Error: Communication failed -> tty read failed, check connection: Timeout error
2021-03-14T08:21:08: [INFO] Setting pulse limits: minimum pulse 10 ms, minimum timer pulse 100 ms
2021-03-14T08:21:08: [INFO] Setting Custom Tracking Rates - RA=0.5 arcsec/s DE=0.5 arcsec/s
2021-03-14T08:21:08: [INFO] Use Backlash : RA: False, DE: False
2021-03-14T08:21:08: [INFO] Setting Backlash compensation - RA=10 microsteps DE=10 microsteps
2021-03-14T08:21:08: [INFO] Observer location updated: Latitude 55:46:00.1 (55.7667) Longitude 37:40:00.1 (37.6667)
2021-03-14T08:21:08: [INFO] updateLocation: long = 37.6667 lat = 55.7667
2021-03-14T08:21:08: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state.
2021-03-14T08:21:08: [INFO] Loading device configuration...
2021-03-14T08:21:07: [WARNING] Can not load HorizonLimits Data File ~/.indi/HorizonData.txt: No such file or directory
2021-03-14T08:21:07: [INFO] updateLocation: long = 0 lat = 0
2021-03-14T08:21:07: [INFO] Mount is unparked.
2021-03-14T08:21:07: [WARNING] Init() : Setting both ST4 guide rates to 0.5x (2)
2021-03-14T08:21:07: [WARNING] Init() : First Initialization for this driver instance
2021-03-14T08:21:07: [WARNING] Init() : Setting default Init steps -- RAInit=8388608 DEInit = 8388608
2021-03-14T08:21:07: [WARNING] Init() : Motors already initialized
2021-03-14T08:21:07: [INFO] Mount has PPEC.
2021-03-14T08:21:06: [INFO] Mount has auxiliary encoders. Turning them off.
2021-03-14T08:21:06: [INFO] EQMod Mount is online.
2021-03-14T08:21:06: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:06: [INFO] Debug is enabled.
2021-03-14T08:21:55: [INFO] EQMod Mount is online.
2021-03-14T08:21:55: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:54: [INFO] Device configuration saved.
2021-03-14T08:21:54: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Setting UTC Time to 2021-03-14T08:21:08, Offset 3
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration saved.
2021-03-14T08:21:53: [INFO] Saving device configuration...
2021-03-14T08:21:53: [INFO] Device configuration applied.
2021-03-14T08:21:53: [INFO] Setting LED brightness to 255
2021-03-14T08:21:53: [INFO] Inverting Declination Axis.
2021-03-14T08:21:53: [INFO] EQMod Mount is offline.
2021-03-14T08:21:23: [ERROR] Error: Communication failed -> tty read failed, check connection: Timeout error
2021-03-14T08:21:08: [INFO] Setting pulse limits: minimum pulse 10 ms, minimum timer pulse 100 ms
2021-03-14T08:21:08: [INFO] Setting Custom Tracking Rates - RA=0.5 arcsec/s DE=0.5 arcsec/s
2021-03-14T08:21:08: [INFO] Use Backlash : RA: False, DE: False
2021-03-14T08:21:08: [INFO] Setting Backlash compensation - RA=10 microsteps DE=10 microsteps
2021-03-14T08:21:08: [INFO] Observer location updated: Latitude 55:46:00.1 (55.7667) Longitude 37:40:00.1 (37.6667)
2021-03-14T08:21:08: [INFO] updateLocation: long = 37.6667 lat = 55.7667
2021-03-14T08:21:08: [INFO] Dome Policy set to: Dome ignored. Mount can park or unpark regardless of dome parking state.
2021-03-14T08:21:08: [INFO] Loading device configuration...
2021-03-14T08:21:07: [WARNING] Can not load HorizonLimits Data File ~/.indi/HorizonData.txt: No such file or directory
2021-03-14T08:21:07: [INFO] updateLocation: long = 0 lat = 0
2021-03-14T08:21:07: [INFO] Mount is unparked.
2021-03-14T08:21:07: [WARNING] Init() : Setting both ST4 guide rates to 0.5x (2)
2021-03-14T08:21:07: [WARNING] Init() : First Initialization for this driver instance
2021-03-14T08:21:07: [WARNING] Init() : Setting default Init steps -- RAInit=8388608 DEInit = 8388608
2021-03-14T08:21:07: [WARNING] Init() : Motors already initialized
2021-03-14T08:21:07: [INFO] Mount has PPEC.
2021-03-14T08:21:06: [INFO] Mount has auxiliary encoders. Turning them off.
2021-03-14T08:21:06: [INFO] EQMod Mount is online.
2021-03-14T08:21:06: [INFO] Successfully connected to EQMod Mount.
2021-03-14T08:21:06: [INFO] Debug is enabled.
↧
Sold the observatory content... awaiting new telescope... - by: Gonzothegreat
So today I've sold to a good friend the content of my observatory, as in the pier + HEQ5 pro mount + William Optics Megrez72 + lots of accessories so that he can be setup for visual and astrophotography.
I am keeping the observatory box![:) :)]()
I already have the new mount a CEM25p , purchased a while ago.
Will be moving into a different league of telescope, a Takahashi 130D and a Zwo 183mm pro mono camera.
As clear nights are fewer and fewer, I want to be able to capture the maximum of light in the minimum of time, hence switching a f6/0 to a f3.3 Newtonian Astrograph Reflector.
Will post pictures whenever it arrives... it might take a while...
I am keeping the observatory box

I already have the new mount a CEM25p , purchased a while ago.
Will be moving into a different league of telescope, a Takahashi 130D and a Zwo 183mm pro mono camera.
As clear nights are fewer and fewer, I want to be able to capture the maximum of light in the minimum of time, hence switching a f6/0 to a f3.3 Newtonian Astrograph Reflector.
Will post pictures whenever it arrives... it might take a while...
↧
↧
Add geophraphic (GPS) coordinates to KStars windows - by: djones
At the bottom left position Kstars display the geographic location (e.g. your hometown or "mount location" when location is synced from the mount).
My Ioptron CEM-25P mount has an internal GPS and like the idea of syncing the GPS coordinates from my mount to KStars/Ekos. After Syncing from the Mount KStars displays "Mount Location" but i don´t see the real gps coordinates. At some occasions the synced gps coordinates from my mount where broken and my mount crashed when slewing to my first target.
So adding the actual geographic cordinates after the name would bring a real benefit for a plausibility check.
My Ioptron CEM-25P mount has an internal GPS and like the idea of syncing the GPS coordinates from my mount to KStars/Ekos. After Syncing from the Mount KStars displays "Mount Location" but i don´t see the real gps coordinates. At some occasions the synced gps coordinates from my mount where broken and my mount crashed when slewing to my first target.
So adding the actual geographic cordinates after the name would bring a real benefit for a plausibility check.
↧
[BUG] KStars - Where are the Satellites at times? - by: Poison
I selected all available Satellites in Preferences -> Satellites.
As soon as I select "Only show visible Satellites" there is not a singe satellite on the screen.
I've downloaded the PC Version of KStars 3.5.2 and let it run in Crossover and there is the same behavior.
What I am doing wrong?
De-select "Only visible..."
Select "Only visible..."
As soon as I select "Only show visible Satellites" there is not a singe satellite on the screen.
I've downloaded the PC Version of KStars 3.5.2 and let it run in Crossover and there is the same behavior.
What I am doing wrong?
De-select "Only visible..."
Select "Only visible..."
↧
INDI can't start ZWO 294 - unable to establish . . . - by: fuadramseybass
i'm trying to get my setup working on my Linux Mint 20.1 laptop and Indi can't start my ZWO ASI294mc. I get the following message: KStars Unable to establish: + ZWO CCD Please ensure the device is connected and powered on.
-Yes it is connected, and it has the DC power on.
it works fine with the ASI Studio on this same machine.
I have tried with and without the powered USB3 hub, and all different usb ports on the laptop, but can't it to start up with EKOS/INDI. I also tried it with only the camera and nothing else but no difference.
KSTARS 3.5.3 beta
Cinnamon Version 4.8.6
Linux Kernel 5.4.0-66generic
running the nightly PPA build.
-Yes it is connected, and it has the DC power on.
it works fine with the ASI Studio on this same machine.
I have tried with and without the powered USB3 hub, and all different usb ports on the laptop, but can't it to start up with EKOS/INDI. I also tried it with only the camera and nothing else but no difference.
KSTARS 3.5.3 beta
Cinnamon Version 4.8.6
Linux Kernel 5.4.0-66generic
running the nightly PPA build.
↧
Getting started... - by: SundayAstronomer
Dear all,
I have been reading a few articles and posts, and I think I got a decent idea of how to get started. I'd really appreciate it if you could help me validate my initial plan. I am new to astronomy, and I trust experts will immediately spot any rookie mistake.![:) :)]()
Objective
My 6yo would love to see Saturn up close. I based my research on the specs needed to distinguish Saturn's rings and moons. The plan is to start with that to then dive into astronomy together with my son. Since I am into RPis, and the budget is modest, I would like to make it also a fun, cheap project, adding auto-tracking and astrophotography to the mix.
Hardware
I am eyeing a Celestron NexStar 102 SLT (<£350). I have been advised on a minimum of 3" and 50x, and that model seems to be better. I guess I'll also need an RPi 4 2GB or superior, an RPi HD camera, a 1.25-inch C-mount adapter. Optionally, a touch-screen. I am still trying to understand if there is a mount for the RPi or better off with long cables.
Software
Astroberry or Stellarmate (I am assuming that besides the premium support, they both offer tracking and compatibility with HD camera). I am still unclear how the GPS would work.
How does it sound? Missing anything?
I have been reading a few articles and posts, and I think I got a decent idea of how to get started. I'd really appreciate it if you could help me validate my initial plan. I am new to astronomy, and I trust experts will immediately spot any rookie mistake.

Objective
My 6yo would love to see Saturn up close. I based my research on the specs needed to distinguish Saturn's rings and moons. The plan is to start with that to then dive into astronomy together with my son. Since I am into RPis, and the budget is modest, I would like to make it also a fun, cheap project, adding auto-tracking and astrophotography to the mix.
Hardware
I am eyeing a Celestron NexStar 102 SLT (<£350). I have been advised on a minimum of 3" and 50x, and that model seems to be better. I guess I'll also need an RPi 4 2GB or superior, an RPi HD camera, a 1.25-inch C-mount adapter. Optionally, a touch-screen. I am still trying to understand if there is a mount for the RPi or better off with long cables.
Software
Astroberry or Stellarmate (I am assuming that besides the premium support, they both offer tracking and compatibility with HD camera). I am still unclear how the GPS would work.
How does it sound? Missing anything?
↧
↧
Indy doesn't want to trigger my Pentax camera - by: spica
Hi,
I have problems with my Pentax camera K II Mark 1 with Indi and Elko to take a picture
The camera has been recognized and everything is okay. The frame rate matches the CCD information
Is also green. If I want to change the exposure, an error message appears and the camera does not trigger
According to the hardware list, my K 1 is not supported, but I have the same problem with the K-3. Sorry my english
2021-03-10T22:50:45 CCD capture aborted
2021-03-10T22:50:45 Capture failed. Check INDI Control Panel for details.
2021-03-10T22:50:45 Capturing 1,000-second image...
2021-03-10T21:50:46: [WARNING] Could not wait for event.
2021-03-10T21:50:46: [ERROR] Error starting exposure
2021-03-10T21:50:46: [INFO] Starting 1 seconds exposure.
2021-03-10T21:50:46: [ERROR] Error starting exposure
2021-03-10T21:50:46: [INFO] Starting 1 seconds exposure.
2021-03-10T21:50:46: [ERROR] Error starting exposure
2021-03-10T21:50:46: [INFO] Starting 1 seconds exposure.
2021-03-10T21:50:22: [ERROR] Failed to start streaming.
2021-03-10T21:50:22: [WARNING] View finder widget is not found. Cannot force camera mirror to go up!
2021-03-10T21:48:52: [2021-03-10T21:50:22: [INFO] Starting the video stream with target exposure 0.100000 s (Max theoritical FPS 10)
I have problems with my Pentax camera K II Mark 1 with Indi and Elko to take a picture
The camera has been recognized and everything is okay. The frame rate matches the CCD information
Is also green. If I want to change the exposure, an error message appears and the camera does not trigger
According to the hardware list, my K 1 is not supported, but I have the same problem with the K-3. Sorry my english
2021-03-10T22:50:45 CCD capture aborted
2021-03-10T22:50:45 Capture failed. Check INDI Control Panel for details.
2021-03-10T22:50:45 Capturing 1,000-second image...
2021-03-10T21:50:46: [WARNING] Could not wait for event.
2021-03-10T21:50:46: [ERROR] Error starting exposure
2021-03-10T21:50:46: [INFO] Starting 1 seconds exposure.
2021-03-10T21:50:46: [ERROR] Error starting exposure
2021-03-10T21:50:46: [INFO] Starting 1 seconds exposure.
2021-03-10T21:50:46: [ERROR] Error starting exposure
2021-03-10T21:50:46: [INFO] Starting 1 seconds exposure.
2021-03-10T21:50:22: [ERROR] Failed to start streaming.
2021-03-10T21:50:22: [WARNING] View finder widget is not found. Cannot force camera mirror to go up!
2021-03-10T21:48:52: [2021-03-10T21:50:22: [INFO] Starting the video stream with target exposure 0.100000 s (Max theoritical FPS 10)
↧
Running two identical imaging trains on one mount with one Raspberry Pi? - by: M_Noordman
I call on the wisdom of the community ![;-) ;-)]()
I want to set up a remote, automated, permanent observatory with two scopes and two identical imaging trains, all on one mount and preferably controlled by ekos/Indi on one raspberry pi.
More specifically: 2 x (Atik 383L + Atik FW + ZWO focuser). When I just connect all these devices to my pi today I do see them popping up (Atik + Atik1) but I do not have consistency in which camera is which. I would prefer if they would show up in Ekos as distinct different devices with unique and consistent identifiers. I can then use them as resources to create profiles (e.g. Atik_A main camera and Atik_B guiding and the other way around) that I can then mix in schedules for automation.
I looked into persistent port mapping but that does not help much. When I connect a device, a new file shows up in /dev/bus/usb/001/ (so no ttyUSBx).
When I check the 'serial' attribute of this file, it always gives me the same number. Also, all attributes of the cameras or focusers are equal.
Maybe I can separate the two sets by plugging them into two separate USB hubs that go into two different USB ports in the pi?
Who can help me solve this puzzle?
Best regards,
Marcel

I want to set up a remote, automated, permanent observatory with two scopes and two identical imaging trains, all on one mount and preferably controlled by ekos/Indi on one raspberry pi.
More specifically: 2 x (Atik 383L + Atik FW + ZWO focuser). When I just connect all these devices to my pi today I do see them popping up (Atik + Atik1) but I do not have consistency in which camera is which. I would prefer if they would show up in Ekos as distinct different devices with unique and consistent identifiers. I can then use them as resources to create profiles (e.g. Atik_A main camera and Atik_B guiding and the other way around) that I can then mix in schedules for automation.
I looked into persistent port mapping but that does not help much. When I connect a device, a new file shows up in /dev/bus/usb/001/ (so no ttyUSBx).
When I check the 'serial' attribute of this file, it always gives me the same number. Also, all attributes of the cameras or focusers are equal.
Maybe I can separate the two sets by plugging them into two separate USB hubs that go into two different USB ports in the pi?
Who can help me solve this puzzle?
Best regards,
Marcel
↧
Bleeding edge release unable to find cameras - by: jerry
With bleeding edge versions since about March 12th, I have been unable to see my cameras with KStars, while Phd2 can see the ZWO 224mc directly, Kstars issues the notification...
lsusb shows both cameras as usb devices.
If I run Kstars with internal guiding it notifies that it can't see either camera.
Running the stable 2021-03-1 version works as expected.
I couldn't find an error in any log I inspected that provided more detail than the notification message.
Running on Odroid-N2 using Unbuntu 20.0.4
Perhaps unrelated, I have enabled the Terrain feature in the bleeding edge version and it is working.
Any suggestion on how to debug this?
Thanks
lsusb shows both cameras as usb devices.
If I run Kstars with internal guiding it notifies that it can't see either camera.
Running the stable 2021-03-1 version works as expected.
I couldn't find an error in any log I inspected that provided more detail than the notification message.
Running on Odroid-N2 using Unbuntu 20.0.4
Perhaps unrelated, I have enabled the Terrain feature in the bleeding edge version and it is working.
Any suggestion on how to debug this?
Thanks
↧
INDI/KStars for Windows info - by: PK
I'm a Mac user and connect to INDI that is running on an Ubuntu machine at the scope. Works great!
I know that the Mac can run KStars and connect to equipment directly, as it has an INDi server built in.
But I get a lot of people asking me if KStars and INDi work on Windows. As I have no real wold knowledge of that - please let me know what the current process is.
1- Does Windows need a separate server, like a Stellarmate/RaspPi etc that hosts INDI?
2- Is KStars for Windows as stable as the Linux and Mac versions?
3- Do Windows users need any additional software to make it work well?
Thanks!
Peter
I know that the Mac can run KStars and connect to equipment directly, as it has an INDi server built in.
But I get a lot of people asking me if KStars and INDi work on Windows. As I have no real wold knowledge of that - please let me know what the current process is.
1- Does Windows need a separate server, like a Stellarmate/RaspPi etc that hosts INDI?
2- Is KStars for Windows as stable as the Linux and Mac versions?
3- Do Windows users need any additional software to make it work well?
Thanks!
Peter
↧
↧
Strange autofocus behavior - by: PK
↧
Could not connect Orion Starshoot G3 Mono - by: sirio.negri
Hi all! I'm trying to connect my Orion Starshoot G3 Mono to my Astroberry setup. I tried with Starshootg and SSAG with no results. Anyone know how to connect properly? Is there any incompatibilities?
Thanks for all info
Sirio
Thanks for all info
Sirio
↧
the very new touptek's mono camera ATR3CMOS26000KMA doesn't work at kstars/indi - by: htly9981
is it still not support?
↧
IMX290 - Astroberry and PHD2 - by: ALudB47
Recently set up an Astroberry, all up to date and have it plugged into a Nikon and a IMX290 for the guide cam. However I have had nothing but trouble getting this to work nicely. I have seen posts with the same issues as mine (their pasted logs pretty much match mine) but after a lot of playing around with settings I have managed to get it to work, although only in 680px x 480px. If I move it up any higher it crashes and I have to reconnect. I have even put a fresh Astroberry on recently with no change.
INDI will also will not save the pixel size I specify so on every boot I have to set the 2.9um pixel sizes (and I even hit save configuration). Other configs such as my Nikon settings are saved no problem, it almost seems it looks and overwrites on connecting.
It looks like I have two separate issues here, saving the config I set (in the logs it defaults to 5.6um) and possibly v4l2 driver issues not playing nice with PHD2? The camera works flawlessly as a capture device in VLC and I can take photos no problem in OAControl, which doesn't use INDI.
Would anyone be able to assist?
↧
↧
Stellarmate dont start after update - by: JuergenN
Yesterday I did an update of my stellarmate, running on raspi 4 4GB. As far as I remember the only file updated was stellarmateudevmanager.
Today I want to start stellarmate, but it hangs with blinking cursor just before showing the grey stellarmate screen!
Of course I have a backup of my system. After copiing the backup to my working SSD everything was ok. I tried again the update (see attached screenshot, there were some more files updated since the backup was a little bit older). Result was again hanging with blinking cursor!
The versions of the files which are ok:
stellarmateupdater: 1.0-stable 202009101254
stellarmateudevmanager: 1.5.7-stable 202103031534
Ha sanyone observed the same behaviour?
Today I want to start stellarmate, but it hangs with blinking cursor just before showing the grey stellarmate screen!
Of course I have a backup of my system. After copiing the backup to my working SSD everything was ok. I tried again the update (see attached screenshot, there were some more files updated since the backup was a little bit older). Result was again hanging with blinking cursor!
The versions of the files which are ok:
stellarmateupdater: 1.0-stable 202009101254
stellarmateudevmanager: 1.5.7-stable 202103031534
Ha sanyone observed the same behaviour?
↧
Celestron Focuser connection errors - by: Eamesy
Hi all, well I have been successfully using a Celestron Focuser on an Edge HD 8 on my IOptron CEM60 for some time running on a mount RPI 4 with Astroberry with EKOS. Autofocus was running fine until about a month ago when random connection errors seem to have started and now ruin every session outside. Everything is powered independently either by a Startech hub or direct 12v power so there is no strain on the RPI. It is fully up to date as of today as well with the latest software updates.The focuser always connects first time but if I try to run a focus job it will always disconnect at some point. Calibration routines usually fails and even crashed the Indi driver a few times, if it got that far. The predominant error is always “sendPacket fail tty -2 Write Error: Input/output error, ns 0” which says to me it might be a bad connection…So I have tried 3 different USB 2A to B leads, changed the port it plugs into, plugged it into the back of my ZWO camera as a test, taken it apart and checked for obvious connection issues inside for the cable ribbon off its control board – still the same so am wondering if it is faulty or perhaps a driver issue? Anyone else had this issue and can stop me throwing it against a wall very soon!Oh when I connect it to a laptop via USB directly and use the Celestron utility – it doesn’t seem to fail! Indi logs from tonight attached, I turned on verbose logging for the focuser and mount near the bottom…
When I moved the focuser via Indi panel, it would not report its final position…I also noticed that each time I reconnect via Indi, the serial port moves to the next one i.e. dev/ttyACM3, started on port zero before 1st crash.Any help gratefully received!
When I moved the focuser via Indi panel, it would not report its final position…I also noticed that each time I reconnect via Indi, the serial port moves to the next one i.e. dev/ttyACM3, started on port zero before 1st crash.Any help gratefully received!
↧
Serial read error after meridian flip - by: fuadramseybass
Any idea why I would get a "serial read error" after a meridian flip?
I had my setup on a Linux Laptop (Celestron CGEM/ASI294, ASI120mm mini), guiding and doing an image run. I had meridian flip enabled. It captured half of the images, started a flip and never started again. Hours later I tried to park it and it wouldn't do that. I had to stop and disconnect INDI and restart the software and then parked okay.
Welcome to KStars 3.5.2 Stable
Build: 2021-03-01T11:47:36Z
OS: "linuxmint"
API: "x86_64-little_endian-lp64"
- Arch: "x86_64"
Kernel Type: "linux"
Kernel Version: "5.4.0-67-generic"
Qt Version: 5.12.8
. . .
[2021-03-16T01:42:09.858 PDT DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "12h 19m 54s" ( 12.3318 ) DE: " 14° 19' 00\"" ( 14.3165 )
[2021-03-16T01:42:09.858 PDT INFO ][ org.kde.kstars.ekos.guide] - "Mount is moving. Resetting calibration..."
[2021-03-16T01:42:09.859 PDT INFO ][ org.kde.kstars.ekos.guide] - "Calibration is cleared."
[2021-03-16T01:42:09.863 PDT INFO ][ org.kde.kstars.ekos.mount] - "Meridian flip slew started..."
[2021-03-16T01:42:09.891 PDT DEBG ][ org.kde.kstars.indi] - ZWO CCD ASI120MM Mini : "[DEBUG] Aborting camera exposure... "
[2021-03-16T01:42:09.958 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[INFO] Slewing to JNOW RA 12:19:54 - DEC 14:18:59 SlewOffsetRa 68.8 arcsec "
[2021-03-16T01:42:31.948 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:36.953 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:42.959 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:42.960 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Failed to read RA/DEC values. "
[2021-03-16T01:42:48.966 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:48.966 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Failed to read RA/DEC values. "
[2021-03-16T01:42:54.972 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error ". . .
I had my setup on a Linux Laptop (Celestron CGEM/ASI294, ASI120mm mini), guiding and doing an image run. I had meridian flip enabled. It captured half of the images, started a flip and never started again. Hours later I tried to park it and it wouldn't do that. I had to stop and disconnect INDI and restart the software and then parked okay.
Welcome to KStars 3.5.2 Stable
Build: 2021-03-01T11:47:36Z
OS: "linuxmint"
API: "x86_64-little_endian-lp64"
- Arch: "x86_64"
Kernel Type: "linux"
Kernel Version: "5.4.0-67-generic"
Qt Version: 5.12.8
. . .
[2021-03-16T01:42:09.858 PDT DEBG ][ org.kde.kstars.indi] - ISD:Telescope sending coords RA: "12h 19m 54s" ( 12.3318 ) DE: " 14° 19' 00\"" ( 14.3165 )
[2021-03-16T01:42:09.858 PDT INFO ][ org.kde.kstars.ekos.guide] - "Mount is moving. Resetting calibration..."
[2021-03-16T01:42:09.859 PDT INFO ][ org.kde.kstars.ekos.guide] - "Calibration is cleared."
[2021-03-16T01:42:09.863 PDT INFO ][ org.kde.kstars.ekos.mount] - "Meridian flip slew started..."
[2021-03-16T01:42:09.891 PDT DEBG ][ org.kde.kstars.indi] - ZWO CCD ASI120MM Mini : "[DEBUG] Aborting camera exposure... "
[2021-03-16T01:42:09.958 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[INFO] Slewing to JNOW RA 12:19:54 - DEC 14:18:59 SlewOffsetRa 68.8 arcsec "
[2021-03-16T01:42:31.948 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:36.953 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:42.959 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:42.960 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Failed to read RA/DEC values. "
[2021-03-16T01:42:48.966 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error "
[2021-03-16T01:42:48.966 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Failed to read RA/DEC values. "
[2021-03-16T01:42:54.972 PDT INFO ][ org.kde.kstars.indi] - Celestron CGEM : "[ERROR] Serial read error: Timeout error ". . .
↧