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

Help Required! Polar Alignment Experiment - by: knro

$
0
0
Introduction

So after a few failed random trials by some users with the PAA tool, I really want to get to the bottom of this. From what I gathered this morning after giving it more thought is it is <em>most likely</em> caused by image orientation/rotation.

Currently, Ekos sets the correction vector as following:

<code>
correctionVector.setP1(celestialPolePoint);
correctionVector.setP2(RACenterPoint);
</code>

The vector starts from the location of the celestial pole to the location of the RA center of rotation. The idea is by adjusting the Alt/Az knobs on your mount, you move the mount RA center of rotation to coincide with the celestial pole.



The above is using the Simulators with a polar error of 00:06:21

To make this easier, the user selects a star they can move to achieve this:



Now by adjusting the mount knobs, the star in the <strong>image</strong> is moved to the Right/Bottom. The mount RA axis therefore is moving toward the Left/Top. When solved, astrometry.net reports the field parity for the simulator as Negative. So I'd like to collect some data by asking our lovely forum users to run an experiment with the PPA tool. <strong>Please make sure to enable Verbose Logging to File and select the Alignment module.</strong>

Data Required

1. Mount Type
2. Telescope Type (or PoleMaster)
3. Hemisphere: North or South.
4. Is the camera aligned with the telescope? If not, what's the angle of the rotation with respect to the telescope?
5. Please record how the image SHIFTS when you adjust the azimuth/altitude knobs:
5.1. Right Azimuth knob: When locking the RIGHT Azimuth knob, how does the image shift in the camera?
5.2. Altitude knob: When lowering the mount (Decreasing Altitude), how does the image shift in the camera?
6. PAA successful or not? Was PPA able to close the gap or it made things worse?
7. Logs

KStars v3.0.0 is released! - by: Gonzothegreat

Message in mailbox which cant be load wi - by: calberts

$
0
0
Hallo moderator

I have message in my indilib mail box wich cant be load an cause daily an alert in my mail that i have message
Can this message be deleted i can dothis

Thanks

Chris

Paramount MyT connects to Ekos but not to PHD2? - by: airscott

$
0
0
Trying to use PHD2 to guide Paramount MyT under Ubuntu 18.04, KStars 3.0.0.

Of course I have TheSkyX running first, with IP server port 3040.

INDI and Ekos can then see and control the mount, slew, image, etc.

But I can't get PHD2 to connect to the mount at all, either through INDI or through AUX Mount (ports 7624 and 3040).

All I get is a "connection timeout" message, and then "Failed to connect to mount."

Also, I'm trying to guide using "Direct Guide" not relays on the mount.

Perhaps I'm confused as to whether PHD2 is controlling the mount via Ekos/INDI (port 7624), or via port 3040 to TheSkyX, or both?

Can anybody help with this?

200km Remote location Setup, - by: calberts

$
0
0
I have general question. I looking for example setups with indi and kstar to build a remote Observatorium about 200km distance. I have now backyard one now;-)
the internet connection on remote location is poor the idea is to create 4G connection. The internet speed on location on this moment is 4Mbps down and 0.47 Up.
I have now the impression that the Indi setup is more for backyard use or High speed connected network setup
I was wondering how the application perform with taking in account the latency of the network 200km remote setup.

So how to use indi in this kind of setups

Example auto guiding the picture must be send to the client and calculate the differents and sending back the correction command the correction can be to late and can cause guiding errors i expect.

How to to deal with the high resultion images (Big files) etc etc. during day i can setup an transfer but i dont want that during the capturing session i only need preview
etc. Are persons in this forum who have kind of setup and like to share how Indi is used (share setup drawing) or do you always use VNC /Team view in this kind of setups
and is indi/kstar local ( backyard setup)


Thanks on forhand.

Chris

indi_astrometry: Corrupt JPEG data - by: Gonzothegreat

$
0
0
As there is no much to do while you have 24h/24h 100% cloud cover.... you go and test a few things... Astrometry, for example.

$ indiserver -v indi_simulator_ccd indi_simulator_telescope indi_simulator_guide indi_astrometry
Starts Kstars 3.0.0 (Osx), connect to indi server, then Align > Load&Slew (I select my h.jpg file) | Solver: remote
Options: -O --no-plots --no-verify --resort --downsample 2 -3 2.54167 -4 59.2583 -5 30

While trying to solve an image which I know is solvable, I get the following:

2018-12-23T09:45:07: Driver indi_astrometry: jpegtopnm: WRITING PPM FILE
2018-12-23T09:45:07: Driver indi_astrometry: Corrupt JPEG data: premature end of data segment
2018-12-23T09:45:07: Driver indi_astrometry: Unsupported marker type 0x6b
2018-12-23T09:45:07: Driver indi_astrometry: Command failed: jpegtopnm /tmp/ccdsolver.fits > /tmp/tmp597Lqf.pnm
2018-12-23T09:45:07: Driver indi_astrometry: augment-xylist.c:589:backtick Failed to run command: /usr/bin/python -m astrometry.util.image2pnm --infile /tmp/ccdsolver.fits --uncompressed-outfile /tmp/tmp.uncompressed.MDUZvN --outfile /tmp/tmp.ppm.gycMPt --ppm --mydir /usr/bin/solve-field
2018-12-23T09:45:07: Driver indi_astrometry: ioutils.c:567:run_command_get_outputs Command failed: return value 255



The interesting thing is that the image I used is a jpeg, and it is not corrupted.

heidenrod@heidenrod-obs:~/test_solve$ file h.jpg
h.jpg: JPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, baseline, precision 8, 1536x1152, frames 3
heidenrod@heidenrod-obs:~/test_solve$ jpegtopnm h.jpg >h.ppm
jpegtopnm: WRITING PPM FILE
heidenrod@heidenrod-obs:~/test_solve$ file h.ppm
h.ppm: Netpbm image data, size = 1536 x 1152, rawbits, pixmap
heidenrod@heidenrod-obs:~/test_solve$


If I use the ccdsolver.fits from the /tmp folder then yes it is corrupted.
$ cp /tmp/ccdsolver.fits .
$ jpegtopnm ccdsolver.fits > ccdsolver.ppm
jpegtopnm: WRITING PPM FILE
Corrupt JPEG data: premature end of data segment
Invalid JPEG file structure: two SOF markers





# dpkg -l | grep astrometry
ii astrometry.net 0.73+dfsg-1 armhf Astrometry plate solver
ii libastrometry0:armhf 0.73+dfsg-1 armhf Astrometry plate solver (shared lib)
ii libnova-0.16-0:armhf 0.16-2 armhf celestial mechanics, astrometry and astrodynamics library
ii python-astrometry 0.73+dfsg-1 armhf Astrometry plate solver (Python package)

Post 3.0 thanks and one issue - by: Lead_weight

$
0
0
First, a big thanks to everyone who's been involved in working on this software. As a Mac user, there are only a few programs that can fully automate a nights sessions, and EKOS has been really great. All the new additions to 3.0 have been wonderful.

I ran multiple schedules over the last two nights and I never had to intervene in any way, nor did the software crash or get caught in any kind of loop. To me, this is showing good progress.

Despite several flawless runs, I did have one issue. It came down to the focusing routine. Multiple times it grabbed double stars or stars that were really large, so the fine focus never got there. Despite the flawless runs, I had an average FWHM of 5.6, which is pretty blurry. Is there any way to tweak the algorithm or settings to avoid large stars and doubles? I was imaging on an RC, so the large star had spikes, which I don't think the focus routine knew how to deal with. I did notice one time it grabbed a double, and the focus routine failed, but then picked another star. I was happy with that fallback, but I've seen it regularly pick that double on this specific subject (IC410).

eqmod crashes at startup - by: alacant

$
0
0
Latest nightly build. Logs attached.
**It's a really clear night here. Is there a quick fix?
Cheers

nightly builds - by: Gonzothegreat

$
0
0
I'm curious to know why people use the nightly builds. According to this post from Jasem they are not supposed to be used in production. So what's the deal exactly with nightly builds?

Selecting dark for focus or alignment. - by: phomer60

$
0
0
I have a QSI 683 camera with inbuilt shutter.
When I select - use dark - for focus and alignment it prompts me whether the camera has a shutter.
It should already have access to this information - so why does it ask?
Also, on the alignment module, after selecting to use a dark, the images displayed are dark - you cannot see the object. Deselecting 'dark' and it works again.
Paul

Updates - by: Astrosnoesky

$
0
0
When i read about new developments, nightly builds, in EKOS do i manually have to upgrade my software or is it done automatically whit the upgrades of Ubuntu?

driver for home made DSC - by: anomer

$
0
0
I am new to Indi.
I have a home made DSC connected to a Raspberry Pi, which can emit RA and Dec when asked.
I have hooked it up to Sky Safari using a Python script which responds to the command "Q" on a TCP port.

What is is the easiest way for me to connect it to Kstars? Can I connect using the indi_dsc_telescope driver?
What is the protocol used by indi_dsc_telescope? Is there any other easier way? I would prefer a python solution,
listening on a TCP port, which would be easy for me, just add more commands to my script.

Any links/documentation to read would be helpful.

thanks

Start of fresh installed KStars failed because of citydb.sqlite - by: starhopper

$
0
0
Hello Forum,
I installed KStars bleeding on my new notebook. Starting KStars failed with this error:



This is german , it means that citydb.sqlite was not found and the installation is broken. I found a forum post to repair this: www.indilib.org/forum/general/3782-kstar...in-mint19.html#28721

I installed KStars from PPA, maybe there is a fault?

Just to inform

HEQ5 pro hypertune - by: Gonzothegreat

$
0
0
As the observatory is out of actions for the time being (mainly atik 314 + PA), I will take this opportunity to take the mount back home for some "hypertuning".
When I installed the Rowan belt kit, I did notice something odd, the DEC wasn't going round and round in a nice smooth fashion.
It was smooth smooth then it got harder to turn then got very very smooth like almost no resistance at all....

They are kits available out there, and also companies doing it (at a price). I will be doing this myself.
Lots of link available
www.astro-baby.com/heq5-rebuild/heq5-m1.htm
stargazerslounge.com/topic/253097-hyper-tuning-my-heq5-pro/
stargazerslounge.com/topic/237281-rebuild-of-heq5-pro/


Stay tuned for more updates....

DYI Focuser with high resolution and ekos (nor the kstars indi interface) issues - by: luca.gervasi

$
0
0
Hi,
I have built a dit focuser using a nema17 + planetary gear with a ratio of 29, having roughly a 0.00041 mm per step. I'm using the moonlight driver. With this setup, i reach focus at ~ 70500 steps (~ 20.11mm focuser outward). I found that It's impossible to use such a number in ekos/kstars as it has an hard limit on 65535 steps and an interface limit to 60000 (strange number tho...).
I'm not proficient enough to create a pyindi interface and test if the problem is in the driver itself or in the kstars/ekos interface. What do you suggest? At the moment i'm moving to 50000, then set position as 0 and then move again, but this is not a good solution imho.
FYI:
Kstars 3.0.0 and indi 1.7.6

Thanks
Luca

Focus tab - by: hy

$
0
0
I've started using indi/ekos/kstars on an RPi and things have been going reasonably well. Thanks!
I would like to better understand the focus tab.

I've been using it to manually focus--e.g. I usually click auto-select star, sub-frame, full-field and then framing.
I look at the plot and hfr number, and turn the focus knob to try and minimze the hfr (ie get the plot points to a minimum).
This seems to work ok, though a little noisy (I assume that's just variation in seeing).

My questions. What do the values on the plot mean? Is this an ensemble hfr or a single star's value?
Even if I try and select the star myself, and view the hfr on the mouse-hint, the values in the hfr text-box and the values on the plot don't seem to correspond to the star I selected.
Or, if I click auto-select-star, also the hfr for that star doesn't seem to correspond to the plot.

Also, is this the recommended way of doing manual focus? Should this work better than trying to center a Bahtinov pattern, or should I just stick to that?

Finally, I'm not sure I understand how to use the relative profile display. What are the two (red and green) plots in there, and how should I interpret the results?

Thanks!

Problems with autoguider an mount - by: Michael

$
0
0
I hope somebody out there can help me.
I was running my scope pc on windows but that wasn't working well so I changed to ubuntu.
Now I am having all sorts of troubles with mount and autoguider.
Autoguider in Ekos rebularly gives me a Exposure timeout and warnings and errors of a failed communication. My Guider is a Toupcam.
Also I am not able to connect my mount probably due to my need of a RS232 to USB adapter and missing driver under Linux.
If anybody can help me: please let me know.

kstars/Ekos ver. 3.0 capture module Custom Properties button does not work - by: Fivel

$
0
0
After reading topics in this forum, for setting camera (ZWOasi 185mc) Gain, Offset, Bit depth, debayer etc., I cannot access these settings.
I am running the newest version of this app on an iMac with El Capitan.
My camera is recognized and connects just fine. I can see a preview of the camera in the Fits viewer.
Also, is it possible to add the features to save the OSC capture in TIFF and PNG formats?
It would save the steps required to get the color from the saved captures.

Thank you for your help.

Fivel

Vixen Starbook driver - by: not7cd

$
0
0
Hi,

In past month I have battled with INDI and Vixen Starbook to develop driver exploiting Starbook's HTTP API.
So if you know someone who has this quirky oversized gameboy , or Starbook S or Starbook TEN, then give them a shout out.
Packages are ready in ppa:mutlaqja/indinightly , now in version 0.1, and 0.2 ready to go.

More instructions in the repo github.com/indilib/indi/tree/master/3rdparty/indi-starbook

And don't trust this driver before it hits 1.0. Starbook can be easily hung up, so expect manual restarts sometimes. Why I develop this right now? In our observatory we are stuck with New Vixen, so I hope that with INDI support we will bypass Starbook awful interface.

Good luck.

INDIGO controls the 2meter RC telescope at NAO Rozhen (Bulgaria) - by: rumen

$
0
0
I am glad to announce that INDIGO ( www.indigo-astronomy.org ) is fully in to the professional astronomy. After the Andor driver now we have ASCOL driver (the protocol used to control several 1 and 2 meter telescopes modernized by ProjectSoft). Now our 2m RC equipped with two Andor iKonL and one Andor Newton can be controlled with INDIGO. Please see some attached screenshots and picture of the Telescope :)

yours,
Rumen

Viewing all 14088 articles
Browse latest View live


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