Quantcast
Channel: Recent Topics - INDI Forum
Viewing all 15748 articles
Browse latest View live

instability in the newest version? - by: mbhaynie

$
0
0
Greetings;

tldr;  I think I see a new instability in the most recent Ekos version, possibly tied to the dynamic image stacking feature; Plausible? Known? Next steps?

I've been using KStars/Ekos/indilib via astroberry on an RPi 4 for the past year or so, to good effect.  While it's been a steep learning curve, I've always been able to identify *my* problem thanks to the documentation or this forum or occasionally blind luck stumbling onto the right setting to change and learning a new term at the same time, at least until now.

Within the past couple of weeks, I was motivated to upgrade to a newer version (to support the Canon Ra, but I think that's a side issue).  I started with the newest stable image (2.0.3), and applied the recommended upgrade commands: "sudo apt update && sudo apt upgrade && sudo apt dist-upgrade". Once I did that, I started seeing a crash in Ekos, or occasionally all of KStars after taking 10 images or so in the photograph sequence tab.  There didn't seem to be any such trouble with e.g. the plate solving tab.  Not seeing any missing patches and also not having support for the Canon Ra in that most recent astroberry version, I picked up stellarmate;  Good news! The Canon Ra is supported!  Bad news!   It's crashing in the same way after 10 images or so (the number isn't entirely consistent, but it's small).

Given that I'm seeing the same behavior in both the astroberry distro and stellarmate OS, I'm inclined to point my finger at one of the recently introduced features.  In each session, as I'm watching the images in the preview pane being stacked, I can see some artifacts in the image (almost like frost on a lens -- made me check my lenses each time -- no frost) that become more pronounced until the crash.  Purely circumstantial evidence.

I have not collected logs yet -- I'll do that on my next session (Friday night, if the weather holds), now that I know how.

As to versions; I've done the update as of today, so the versions are the current stable ones for astroberry, and the stellarmate OS install is equally current, no updates available as of this post.

Thanks in advance.

 

Struggling with an ASI224MC - by: SundayAstronomer

$
0
0
Dear all, 

I have Stellarmate OS on a RPi 4, connected to a NexStar 6SE and an ASI224MC, and I access both via VNC and the iOS app.
I am feeling a bit stupid as I cannot find how to focus the image on the camera. I take a preview pic and I can only see some blurry lights. Is there a "live" view of the camera that I can use to focus the image before taking a pic?

Align issue after meridian Flip - by: peppuccio

$
0
0
Hi guys,
I'm running last version of Kstars/ekos on a raspberry PI4. Since a few sessions, I have a big issue after meridian flip, all images after flip are showing elongated stars
just like this one
  
This night a put verbose logs to see what is going on.
The meridian flip goes well, and after flip motion, an align action starts. After a large number of  solve and slew it ends whit a failure. The scheduler stars guiding and capture begins. 
In my understanding of logs, my next photo should be a portion of the sky not aligned with my object but with round stars.... 
If needed I can attach a portion of the logs (35 mo).

Thanks for you suggestions.
Joseph

QHY CCD problem with frame dimensions - by: GeoLek

$
0
0
Greetings, I have a problem with my QHY CCD camera. I try to submit the camera's frame dimensions (width and height) but whatever I try,it wont take the values I submit and I always get a red sign at the left of the frame box. I attach some photos and logs. My QHY works fine with my raspberry (I think with Kstars 3.4) but I encounter this problem with my Ubuntu 20.04 laptop with Kstars 3.5.2. Is there any problem with QHY driver at 3.5.2? Thank you very much for your time.

    

File Attachment:

File Name: log_17-17-02.txt
File Size: 69 KB
 

Astroberry 2.0.3 headless installation problem - by: KevinS

$
0
0
I installed Astroberry 2.0.3 on Raspian OS using APT. It rebooted, started its own SSID Astroberry xxx which I joined. 
The http desktop loads but will not connect to the Astroberry server.
I need to get in via SSH or VNC. This is a headless installation. (There is no mini hdmi connector available to me for days.)
Any help would be welcome. thanks
 

Setting FITS image as CCD Simulator's image? - by: NuTek

$
0
0
Is there any way to select an existing image (FITS?) so the CCD simulator will pass that along as the image it takes?
I want to try debugging my plate solving setup by passing a previously solved image I took into the Align module.
I know the "Load and Slew" options exists but that seems to be reading the RA/DEC off the FITS header and I want it to use my solver instead.

Thanks
NuTek

How to enter DEC offset in EQMOD driver? - by: Gorden

$
0
0
Hi, community.
I recently got an EQ8 and plan to run it with two side-by-side scopes. Due to the double mount, the DEC axis has an offset of 90 degrees. In the hand controller, I can enter that offset after the home position is found. Is there a similar setting in the INDI EQMOD driver? Has that to be considered at all?

Thank you for helping me with that.
Best,
Gorden

unable to install pyindi-client on Ubuntu 20.04 - by: Gonzothegreat

$
0
0
I got the requirements (I think) and running python 3.8

/# dpkg -l | egrep "swig|libz3-dev|libcfitsio-dev|libnova-dev|libindi-dev"
ii  libcfitsio-dev:arm64                   3.470-3                                   arm64        library for I/O with FITS format data files (development files)
ii  libindi-dev                            1.8.9~202103011149~ubuntu20.04.1          arm64        Instrument-Neutral Device Interface library -- development files
ii  libnova-dev:arm64                      0.16-4                                    arm64        development files for libnova astronomical library
ii  libnova-dev-bin                        0.16-4                                    arm64        development config tool for libnova astronomical library
ii  libz3-dev:arm64                        4.8.7-4build1                             arm64        theorem prover from Microsoft Research - development files
ii  swig                                   4.0.1-5build1                             all          Generate scripting interfaces to C/C++ code
ii  swig4.0                                4.0.1-5build1                             arm64        Generate scripting interfaces to C/C++ code
/#


However running the following command fails and I cannot figure it out
/# pip3 install pyindi-client

/# pip3 install pyindi-client
Collecting pyindi-client
  Using cached pyindi-client-0.2.7.tar.gz (5.5 kB)
Building wheels for collected packages: pyindi-client
  Building wheel for pyindi-client (setup.py) ... error
  ERROR: Command errored out with exit status 1:
   command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-ii9madax/pyindi-client/setup.py'"'"'; __file__='"'"'/tmp/pip-install-ii9madax/pyindi-client/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' bdist_wheel -d /tmp/pip-wheel-1_qkhxr5
       cwd: /tmp/pip-install-ii9madax/pyindi-client/
  Complete output (50 lines):
  running bdist_wheel
  running build
  running build_ext
  building '_PyIndi' extension
  swigging indiclientpython.i to indiclientpython_wrap.cpp
  swig -python -v -Wall -c++ -threads -I/usr/include -I/usr/include/libindi -I/usr/local/include/libindi -o indiclientpython_wrap.cpp indiclientpython.i
  Language subdirectory: python
  Search paths:
     ./
     /usr/include/
     /usr/include/libindi/
     /usr/local/include/libindi/
     ./swig_lib/python/
     /usr/share/swig4.0/python/
     ./swig_lib/
     /usr/share/swig4.0/
  Preprocessing...
  Starting language-specific parse...
  /usr/include/libindi/baseclient.h:39: Warning 322: Redundant redeclaration of 'MAXRBUF',
  /usr/include/libindi/indibase.h:8: Warning 322: previous declaration of 'MAXRBUF'.
  /usr/include/libindi/baseclient.h:270: Warning 325: Nested struct not currently supported (BLOBMode ignored)
  /usr/include/libindi/basedevice.h:29: Warning 322: Redundant redeclaration of 'MAXRBUF',
  /usr/include/libindi/indibase.h:8: Warning 322: previous declaration of 'MAXRBUF'.
  /usr/include/libindi/indiwidgettraits.h:37: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
  /usr/include/libindi/indiwidgettraits.h:48: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
  /usr/include/libindi/indiwidgettraits.h:59: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
  /usr/include/libindi/indiwidgettraits.h:68: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
  /usr/include/libindi/indiwidgettraits.h:82: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
  /usr/include/libindi/indiproperty.h:94: Warning 321: 'apply' conflicts with a built-in name in python
  /usr/include/libindi/indiproperty.h:94: Warning 321: 'apply' conflicts with a built-in name in python
  /usr/include/libindi/indiproperty.h:94: Warning 321: 'apply' conflicts with a built-in name in python
  /usr/include/libindi/baseclient.h:61: Warning 403: Class 'INDI::BaseClient' might be abstract, no constructors generated,
  /usr/include/libindi/indibase.h:86: Warning 403: Method INDI::BaseMediator::newDevice(INDI::BaseDevice *) might not be implemented.
  /usr/include/libindi/basedevice.h:146: Warning 512: Overloaded method INDI::BaseDevice::getProperties() const ignored,
  /usr/include/libindi/basedevice.h:145: Warning 512: using non-const method INDI::BaseDevice::getProperties() instead.
  /usr/include/libindi/indiproperty.h:94: Error: Non-optional argument '' follows an optional argument.
  /usr/include/libindi/indiproperty.h:94: Error: Non-optional argument '' follows an optional argument.
  /usr/include/libindi/indiproperty.h:94: Warning 509: Overloaded method INDI::Property::apply(char const *,...) effectively ignored,
  /usr/include/libindi/indiproperty.h:94: Warning 509: as it is shadowed by INDI::Property::apply(char const *).
  /usr/include/libindi/indiproperty.h:94: Error: Non-optional argument '' follows an optional argument.
  /usr/include/libindi/indiproperty.h:95: Error: Non-optional argument '' follows an optional argument.
  /usr/include/libindi/indiproperty.h:95: Error: Non-optional argument '' follows an optional argument.
  /usr/include/libindi/indiproperty.h:95: Warning 509: Overloaded method INDI::Property::define(char const *,...) effectively ignored,
  /usr/include/libindi/indiproperty.h:95: Warning 509: as it is shadowed by INDI::Property::define(char const *).
  /usr/include/libindi/indiproperty.h:95: Error: Non-optional argument '' follows an optional argument.
  Processing types...
  C++ analysis...
  Processing nested classes...
  Generating wrappers...
  error: command 'swig' failed with exit status 6
 


  ERROR: Failed building wheel for pyindi-client
  Running setup.py clean for pyindi-client
Failed to build pyindi-client
Installing collected packages: pyindi-client
    Running setup.py install for pyindi-client ... error
    ERROR: Command errored out with exit status 1:
     command: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-ii9madax/pyindi-client/setup.py'"'"'; __file__='"'"'/tmp/pip-install-ii9madax/pyindi-client/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-a3hmepjg/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.8/pyindi-client
         cwd: /tmp/pip-install-ii9madax/pyindi-client/
    Complete output (49 lines):
    running install
    running build_ext
    building '_PyIndi' extension
    swigging indiclientpython.i to indiclientpython_wrap.cpp
    swig -python -v -Wall -c++ -threads -I/usr/include -I/usr/include/libindi -I/usr/local/include/libindi -o indiclientpython_wrap.cpp indiclientpython.i
    Language subdirectory: python
    Search paths:
       ./
       /usr/include/
       /usr/include/libindi/
       /usr/local/include/libindi/
       ./swig_lib/python/
       /usr/share/swig4.0/python/
       ./swig_lib/
       /usr/share/swig4.0/
    Preprocessing...
    Starting language-specific parse...
    /usr/include/libindi/baseclient.h:39: Warning 322: Redundant redeclaration of 'MAXRBUF',
    /usr/include/libindi/indibase.h:8: Warning 322: previous declaration of 'MAXRBUF'.
    /usr/include/libindi/baseclient.h:270: Warning 325: Nested struct not currently supported (BLOBMode ignored)
    /usr/include/libindi/basedevice.h:29: Warning 322: Redundant redeclaration of 'MAXRBUF',
    /usr/include/libindi/indibase.h:8: Warning 322: previous declaration of 'MAXRBUF'.
    /usr/include/libindi/indiwidgettraits.h:37: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
    /usr/include/libindi/indiwidgettraits.h:48: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
    /usr/include/libindi/indiwidgettraits.h:59: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
    /usr/include/libindi/indiwidgettraits.h:68: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
    /usr/include/libindi/indiwidgettraits.h:82: Warning 325: Nested struct not currently supported (UpdateArgs ignored)
    /usr/include/libindi/indiproperty.h:94: Warning 321: 'apply' conflicts with a built-in name in python
    /usr/include/libindi/indiproperty.h:94: Warning 321: 'apply' conflicts with a built-in name in python
    /usr/include/libindi/indiproperty.h:94: Warning 321: 'apply' conflicts with a built-in name in python
    /usr/include/libindi/baseclient.h:61: Warning 403: Class 'INDI::BaseClient' might be abstract, no constructors generated,
    /usr/include/libindi/indibase.h:86: Warning 403: Method INDI::BaseMediator::newDevice(INDI::BaseDevice *) might not be implemented.
    /usr/include/libindi/basedevice.h:146: Warning 512: Overloaded method INDI::BaseDevice::getProperties() const ignored,
    /usr/include/libindi/basedevice.h:145: Warning 512: using non-const method INDI::BaseDevice::getProperties() instead.
    /usr/include/libindi/indiproperty.h:94: Error: Non-optional argument '' follows an optional argument.
    /usr/include/libindi/indiproperty.h:94: Error: Non-optional argument '' follows an optional argument.
    /usr/include/libindi/indiproperty.h:94: Warning 509: Overloaded method INDI::Property::apply(char const *,...) effectively ignored,
    /usr/include/libindi/indiproperty.h:94: Warning 509: as it is shadowed by INDI::Property::apply(char const *).
    /usr/include/libindi/indiproperty.h:94: Error: Non-optional argument '' follows an optional argument.
    /usr/include/libindi/indiproperty.h:95: Error: Non-optional argument '' follows an optional argument.
    /usr/include/libindi/indiproperty.h:95: Error: Non-optional argument '' follows an optional argument.
    /usr/include/libindi/indiproperty.h:95: Warning 509: Overloaded method INDI::Property::define(char const *,...) effectively ignored,
    /usr/include/libindi/indiproperty.h:95: Warning 509: as it is shadowed by INDI::Property::define(char const *).
    /usr/include/libindi/indiproperty.h:95: Error: Non-optional argument '' follows an optional argument.
    Processing types...
    C++ analysis...
    Processing nested classes...
    Generating wrappers...
    error: command 'swig' failed with exit status 6
   
ERROR: Command errored out with exit status 1: /usr/bin/python3 -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-install-ii9madax/pyindi-client/setup.py'"'"'; __file__='"'"'/tmp/pip-install-ii9madax/pyindi-client/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' install --record /tmp/pip-record-a3hmepjg/install-record.txt --single-version-externally-managed --compile --install-headers /usr/local/include/python3.8/pyindi-client Check the logs for full command output.
/# 

Having issues - focusing in scheduler. - by: gilesco

$
0
0
perhaps tell me why I'm not able to focus here:

INDI and the Ascompad - by: Dredger

$
0
0
Hello,
I am using INDI on a Linux OS (Astrel 183-x) and also experimenting with planetariums such as Kstars and CdC for mount control.  I am able to connect and slew my EQMod mount well enough, however I am having trouble fine tuning where the scope is pointing.

Before when using an Windows OS, I was able to fetch the Ascompad to move the mount here and there for fine adjustment.  Is there a way to get the Ascompad from the INDI library?

USB stick disappeared - any way to easily fix? - by: maxthebuilder

$
0
0
Hello,
I think what happened was:
I used a USB stick for storage (SM on RPI4) and it worked.
Then I decided to see how RPI boots from USB - copied the SD card content to that USB stick.
It booted.
Then I decided not to boot from USB until I get a faster device and use the USB stick as the storage again.
Now my RPI doesn't see/recognize that stick.
It's OK if I plug it into a Windows PC.
If I plug a different stick into RPI - it's recognized and mounted.
But this particular stick (which formerly worked fine) RPI/SM refuses to see/mount.

Some sort of Linux thing.
Any way to make it work again?

Thanks!
 

RST-135 mount - what are the best practices? - by: maxthebuilder

$
0
0
I am about to pull the trigger and buy an RST-135.
What are the best practices to use it with SM/KStars/Ekos?
I know, there's a mega thread about it on CN but maybe here I could get some coherent advice.
Thanks!
 

indi_gphoto and focus module issue since V3.0 and Astroberry - by: luggiduggi

$
0
0
Hi, 
I need some help...
I have two RaspberryPIs, one running a kstars-ekos combination which was mostly compiled from source, and one with Astroberry upgraded to latest version. Both run kstars 3.5.2 stable, but the Astroberry version has gphoto 3.0 vs. the gphoto 2.9 from the hand-compiled Raspi. This is the one having the issue:
If I connect my Canon DSLR, and I set the target to save the images to "SDCard" rather than "RAM" (because I like to have the pictures on card), the focus module cannot find the pictures anymore and reports failed exposures. This works fine with gphoto 2.9 on the compiled-from-source Raspi.
I also noted, that on the Indi Control Panel of Kstars, on the "Canon DSLR EOS 1000d" tab (where I also set the preference to RAM or SDCard) under the tab "imgsettings", the value for "imageformatcf" shows "unknown_value 400". Also under the tab "capturesettings", the value for "bracketmode" also shows "unknown_value 0000".
Both of these variables show fine under version 2.9 (as "RAW" and two values 0 and 0 respectively).
On a side note - the capture module works fine and displays the pictures, even when they are saved to SDCard. Only the focus module has an issue with this.
<strong>Here are my questions: </strong>Could there be a problem with the newer 3.0 version of gphoto or am I doing something else wrong? Can I downgrade the gphoto driver to 2.9 on the Astroberry and how can I do that (where would I find source code for 2.9)? 
Please help - The alternative of saving into RAM is really cumbersome with the Astroberry since it requires extra work to get it off there and on my main picture editing machine.
Thanks for any help.
Stephan

Flags location accuracy on starmap - by: rbarberac

$
0
0
I was trying to plan ahead a good composition for some clumped field of galaxies on Virgo. Centering any of the galaxies will give me a not balanced composition, so I want to center my fields on an empty place. I've tried to add a flag on this location so, I can see it on the next maps and I'll have someplace to goto. But I have discovered that with 3.5.2 is almost imposible to place a flag where I want.

On the next sequence you can see the popup menu that appears as I press on right button over the center of the intended field. Then I chose add a flag and fill the information. As you can see on the third screen shot the flags never land on the clicked coordinates.

 
 
 

I'm used the last 3.5.2 release on macOS and Raspberry PI with the same outcome.

Regards

IndI Server - Any success? - by: FragiLimbel

$
0
0
Hi folks,Firstly, thanks to Intercipere, Clutchplate and everyone who has contributed to this fantastic project!I've had the OpenAstroTracker printed, built and working from an Arduino Mega with the LCD panel.But my main reason for building it was to get it working via AstroBerry, which gives you a linux desktop environment with all the normal Linux astro software like PHD2, KStars, and to control it all, INDIServer - I guess its the linux equiv of the ASCOM ecosystem.Now, I've tried a number of ways of getting it working, using both serial over usb from an Arduino Mega (Using the LX200 Classic INDI driver), and wifi via an ESP-12f (using the lx200 Basic INDI Driver).But, whatever I do, I can't get the mount to actually move via serial or ethernet comms.Has anyone else had any success using OAT with INDI at all? and if so what INDI driver did you use, and was it wifi or serial?I'm open to trying anything at the moment, cos I'm out of ideas.Thanks

Clipping or loss of data in RAW capture to FITS? - Canon 5D MK II Fits File - by: p7ayfu77

$
0
0
Hi all I've just recently come back to using my DSLR and noticed an oddity with the FITS images produced by KStars/EKOS.
Compared to the CR2 file the FITS image produced seems to have lost some data in the conversion somewhere between the camera and landing on my disk through EKOS.

When captured as "Native" it come out as expected. However in FITS its has all turned green!
Yes I have turned of auto stretch and checked all my settings, RAW format and image dimensions. See attached images when pull into PixInsight below.
The FITS has been debayered in PixInsight with VNG and CFA GBRG and represents exactly what I see in the EKOS/KStars Fits Viewer.
This is a link to the raw files for comparison on OneDrive: 1drv.ms/u/s!AvWEkn9Anb_NgU5r_vS7LLTTDgeS?e=xFcXtZ

I figure some update to gphoto2 or some regression on how kstars/indi/ekos interprets the raw stream from the camera?

Any ideas would be appreciated. Thanks.

 

Astroberry Help - by: zjc26138

$
0
0
Hi all,


I'm new to using astroberry and raspberry pi. I recently purchased a Pi 4 b. Once received I flashed a micro sd with astroberry  And below are my observations / questions / frustrations with it so far.  I am using a windows 10 pc. Eventually I want astroberry to control imaging and mount functions. Also my mount is within range of my homes wifi.

-Initially I was able to connect via astroberry wifi and astroberry.local/.  The program itself seemed to lag as I navigated it, however I was able to connect and use my Canon 60da. I was happy so I called it a night.

-Went to connect last night so I could use astroberry over my home wifi instead of the astroberry wifi. I could not for the life of me find the astroberry hotspot on my computer or my iphone.  So I plugged the Pi into the ethernet directly. Still no luck. The Pi would not connect to astroberry local or 10.42.0.1.

So I reflashed the micro sd with astroberry. Still had the problems not finding the astroberry hot spot with either my phone, my wifes laptop, or my desktop.

I plugged back into the ethernet and I was finally able to reach the connect screen on the astroberry server.  However it would not connect, and it kept saying "Service Not Available"

So any possible solutions to my issues? Could my Pi unit be bad?  From what I understand the astroberry wifi should be easy to find. And it should be easy to witch to my homes wifi network once everything is running, but at this point I can't even get the astroberry server to show up.


Thanks for your help,

Zach


 

Re:Sorting Out Some Issues With Ekos - by: Chaz007

$
0
0
Hello!

A few weeks ago I began controlling my rig with a raspberry pi4 configured with Astroberry/Kstars. I almost have everything working perfectly, but there are a few issues I have not been able to figure out.

The most pressing issue has to do with the meridian flip. I have the auto meridian flip box checked, and it is set to flip once the hour angle passes 0 degrees. When the flip first initiates, the dialog box says it is flipping. However, after a few seconds it says the flip failed and that it will try again in 4 minutes. I think it slews a little because after the failure ekos begins the plate solving procedure. This cycle repeats itself until I abort the imaging plan. I've tried manually reslewing to the target in kstars, but it does not flip. Only until I park the scope and completely restart ekos does it flip. So far I have tried:

updating everything on the pi
enabling daylight savings on the hand controller
updating the location on the hand controller
disabling auto meridian flip on the hand controller

For clarification, my mount is a skywatcher EQ35, and it is connected to the pi via a serial port connected to the hand controller, which is set to pc direct mode. I ran this same setup but with my PC and different imaging software(APT and then NINA) for over 2 years with absolutely no problems, so I don't suspect the problem lies in hand controller settings on the mount.

I'm also trying to nail down good autofocus settings. Looking at my frames, it is clear that sometimes the autofocus procedure does not produce a perfect focus, and the stars are noticeably larger until the next focus. My settings:

Exposure:20 seconds
Full field is the only box checked on the settings page
Annulus from 0 to 100%
Settle time of 2 seconds
SEP detection
kernel size: 3
sigma:1.5
polynomial algorithm
backlash of 100 steps

I am using the ZWO EAF, and switching to SEP and the polynomial algorithm made a large improvement, but there is still definitely room to improve.

I'm also wondering about the twilight settings. I have it set to park the scope once twilight begins, which I love. However, this setting also forces me to delay imaging until well after the sun is down. Maybe at a dark site twilight lasts until 9 PM, but with the amount of light pollution I deal with, it's as dark as it's going to get by 8. Maybe I'm just not seeing the setting, but is there a way to allow imaging to start sooner using the twilight limits?

And then finally, I'm wondering how to warm the CCD after parking. I see there's a setting to do this upon job completion, but I never finish a job in a given night, and the scope parks due to the twilight settings I mentioned above. However, this just pauses the job and the ccd cooler stays on until I manually turn it off in the morning. I want this camera to last for many years, so I'd like to limit the amount of time the cooler is on, especially once summer comes around.

Thanks!

Question about polar alignment module - by: mgutierrez

$
0
0
Hi all,

The PAA routine suggests to put the mount in home position and point to the ncp OR any point in the meridian. A couple of questions about this. How do I perform the slews, specially if I want to point to any position in the meridian? Manually or with gotos? If the latter, do I need to align the mount previously? My assumption is, in fact, that I need to align and slew the mount with ekos, to let the solver know where is pointing to approximately. Otherwise, the solver may fail due to the huge difference between the real and supposed coordinates. Tonight, in fact, I've suffered many "solver failed" while trying to polar align, but I'm not sure if it's been due to this.

m

[ERROR] cannot change format while streaming/recording - by: rafaelschlegel

$
0
0
I have a Problem with the latest nightly build.
With my Altair 183C ProTec, i cannot change the Format to RAW.

[ERROR] cannot change format while streaming/recording

I just switch back to stable Version and it works again.
But I read in another post that there is a problem with the last stable version and my Altaircam. 
www.indilib.org/forum/ccds-dslrs/9059-fi...3c-kstars-3-5-2.html

Should i stay with the stable version and hope i won't have any problems tonight?

 
Viewing all 15748 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>