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

BLOB Property - by: joxda

$
0
0
Hello,

I would like to experiment with writing a driver that snoops incoming fits data from a CCD and that has a BLOB property which in itself stores fits data that a client should be able to display.
While I found the tutorial_three, I did not find it too instructive for my purposes and I did not find any other examples. Could anyone give me any pointers?

Many thanks,

Joachim

ZWO EAF: Reverse Motion not working - by: DerPit

$
0
0
I mounted my EAF on a new telescope. For it, the normal motion 'Focus in' will move the camera outwards. So I selected 'Reverse Motion -> Enable'. No error, and 'Enable' gets highlighted. But the camera continues to move outwards with 'Focus in'. I made sure 'Enable' is highlighted, saved the configuration, dis- and re-connected to the unit, which set Reverse Motion back to 'Disabled'.

Seems something's broken there?

This is latest git (yesterday) for both INDI and KStars.

Astroberry Server 2.0.1 is available now! - by: Kaczorek

$
0
0
Astroberry Server image minor update has been just released.

This version features:
- Updated Raspbian Buster system
- KStars 3.4.0
- Libindi 1.8.4
- virtualgps if you don't use hardware GPS
- phdlogview for viewing PHD2 logs
- indiwebmanagerapp application as an alternative to INDI Web Manager
- chrony for time synchronization with GPS
- gwenview for viewing FITS
- number of bugfixes and improvements

The new image of the system can be downloaded from www.astroberry.io/distro/
Reflashing of your SD card is not necessary but recommended for current users. If you do not reflash you can get new version with regular update & upgrade procedure.

Re:Re:Scheduler and variable stars - by: joschi

$
0
0
Hi there,
and agai
when I have a job in the scheduler with let's say four variable stars which I want to observe throughout the whole night, it is only done once no matter what I've marked in the job completion conditions section (because this affects only the sequences). Is there a chance, that it could run for several hours? Var1 --> Var2 --> Var3 --> Var4 and again form the beginning and again and again. Hope you understand what I mean.

Greetings,
Jörg!

Re:BLOB Property - by: joxda

$
0
0
Hello,

I would like to experiment with writing a driver that snoops incoming fits data from a CCD and that has a BLOB property which in itself stores fits data that a client should be able to display.
While I found the tutorial_three, I did not find it too instructive for my purposes and I did not find any other examples. Could anyone give me any pointers?

Many thanks,

Joachim

PHD2: Some windows unreadable due to font color - by: limburg11

$
0
0
Hi,
PHD2 under Astroberry works like a charm, and most of the GUI is perfectly readable. But some messages are hardly readable (e.g. calibration warnings appear as white text on an orange background), and some windows are almost completely unreadable like this drift align tool window:

I tried different color themes of Raspbian, but it seems themes change only window title bar colors (and corresponding text colors). Is there a way to customize PHD2's colors? Or customize Raspbian's colors?
CS, Bernd

MI CCD capture abort - by: tcm75

$
0
0
Hi guys.

Me again with new problems out of nothing...

ATM working on a Stellarmate.

Since some days my Moravian G2 8300 colour starts to "abort capture" out of nothing...

Yesterday it happened right after starting a 240 Pictures night. Problem after the first picture... I had a look if it works, then the first picture was taken so i thought ok, i´ll go to bed. and when i got up today i had to see, that it was the only picture taken.

I can stop kstars the, and restart, but the MI CCD won´t connect annymore.

What i have to do is to stop indiservers, end kstars, take out power of the mi ccd, wait some time, put power back, start indi webserver and kstars and reconnect, and not even this is a 100% guarantee that it works.

So i took some flats today in the morning. 7 Flats were taken, and then the same fault again.
I tokk 20 Darks whixh worked fine and after that i wanted to take 100 bias.
51 were taken, then capture aborted...

This is quite frustrating...

You can find logs here...

Ideas?

www.dropbox.com/sh/h995vipyemaqbwr/AABNX...ivN9YpUDYo1X5Va?dl=0

Greets
Niki

Deep sky imager - by: StarD

$
0
0
Hi guys,

I hope you can help me here. I purched a second hand DSI (I) which I want to use as a guiding cam.
I`m running ekos and stellarmate with indi. Kstars remote from my laptop.
My gear is:
Meade LXD 75
ZWO asi 120mc
autostar (controlled by the stellarmate)
Everything works fine. Stellarmate can see and use the camera. But I only get a white screen when exposing.
So I installed the good old autostar suite on my W10 laptop to see if the camera functions and id did.
I also noticed that when playing with exposure time, shadows etc the image would turn white fast.
So my guess is that in Ekos, I should do the same.
Unfortunaly, I can change gain en compensation, but the image stays white. Again, no errors occure.
Can you help me solve this problem? I think I`m close but I just don`t seem to find it.

Thanks

StarD

( In the images, you can see the result with changing the Gain)

How to create Horizon Data without using IPhone? - by: luca.gervasi

$
0
0
Hello,
lurking in the forum's topics I found that many of you are using an App in the Apple phones to create horizon data to feed to Ekos. I find it really useful so I'd like to do it too to have my backyard horizon well traced. Could you suggest some way to do it using tools commonly found in normal houses? (maybe a compass, at top) ?

Thanks

Luca

DSLR Indi Sensor size and Max height and Width values query. - by: stash

$
0
0
For my curiosity I would like a explanation on why entering Pixel X & Pixel Y size in MM works when it appears that it should be in UM.

Example my Canon 100d has a Pixel Size in UM of 4.3 which I duely set up but I input 22.3 x 14.9 (UOM of MM) into the Pixel Size X & Y field


The Docs say "The image info tab contains information on the resolution of the CCD (Maximum Width & Height) in addition to the pixel size in microns" !

Its not a criticism I just hate loose ends and not understanding why my approach works.

Note please keep the explanation as simple as possible :-)

Many Thanks in Advance.

Side-of-pier problem - bug? - by: mlarsson

$
0
0
Hi!

I'm using a Losmandy G11, and have experienced something that I think is a bug in the side-of-pier identification by the driver. At least that is what Patrick Chevallier suggests in the longer discussion here:

groups.google.com/forum/#!topic/open-phd-guiding/s2TVIS3_K_Y

What happens is that the mount reports a shift in side-of-pier when I slew from southwest to northwest, as the mount crosses the azimuth 270 degrees. THis then causes PHD2 to run amok. As I get it, it is better if the driver uses hour angle.

I am relying on Patrick here. But the issue really causes troubles for my standard 20-variable job that crosses the 90 - 270- degree azimuth line several times.... and PHD2 runs amok.

I don't attach a log for the moment because I do not have one. But look at the discussion in the link for more details.

Best,

Magnus

Canon EOS M6 won't capture - by: info@sevenwatt.com

$
0
0
Hi all,

I am new here and new with kstars/ekos/indi. I have some success with connecting an old Meade ETX105EC and a ZWO CCD. I am now trying my EOS M6 and that fails to capture images through INDI. My older EOS 450D worked first time, but that is a large mirror shake for the small ETX.

I believe that the issues might by in libgphoto2 with bulb mode. The is a lot of intended communication going on between INDI and the M^. Only capture fails. I have set my camera to dail: M, shutter time to BULB and focus to manual focus.

Now my question is:
Is there a way to avoid using BULB mode in INDI? As capture with gphoto2 works if I do not select bulb=1.
Maybe my attempts not to use bulb have failed due to other settings?

I already have submitted an issue at libgphoto2: github.com/gphoto/libgphoto2/issues/493

I have made detailed loggings from kstar/indi of failure scenario's. I will attach more soon.

Astrometry image won't solve - by: jdain

$
0
0
I took an image to solve last night at 500mm on my d7200 and it solved no issue. I changed my settings, added a 2x teleconverter to my setup and took a photo but the Solver couldn't solve it. I uploaded it to Astrometry.net and tried to solve and it came back solved against a index file I have. My FOV was 83.2 x 55.5 arcmin and I was pointed near M101. I have attached the JPG. Help?

canon 6d set up file time issue - by: dalbaugh

$
0
0
Help with set up for canon 6d. Set up and everything is working great, auto focus, plate solving. however when I went to stack images deep sky stacker registers 120 second images as 1 second images. Also the resolution does not seem any where near what I was seeing with BackYard EOS. Any help would be appreciated. Has to be a set up issue

All Sky camera software driven by INDI - by: Lead_weight

$
0
0
I'm looking to make an all sky camera with Pi setup and a ZWO ASI224MC camera I'm not using currently. Is there any INDI software that could control the camera to stream this over my network? Thanks!

issues with getting started for the night - by: xsnrg

$
0
0
Greetings, all set up here and ready for some darkish skies.

The first is kstars always crashes the first time I connect with Ekos. Need to turn more logging on, but have not yet as it is easy enough to restart and keep moving.

The next problem is the Ekos window wants to be on the top of everything. Clicking into anything that would pop up a dialog window makes the window pop below the Ekos window. I am running kstars bleeding on Fedora, but it has been this way for a few releases now. I have two monitors, so I just juggle things around, and know how to work around it, but it would be nice to have Ekos not locked to always on top.

The second problem is a little more painful. I am using a ZWO 1600 mono, and flipflat. Everything works fine, auto-focus, alignment, focus, etc, until I go to the CCD tab. Every time I want to do a preview after starting fresh, I get the message:



I do not have Auto Dark checked on the CCD tab, so do not know why it says it needs a flat or dark cap device. Even so, the controls for the flipflat work just fine when I go run it manually. Usually, am able to do a combination of setting up a sequence job, starting, stopping it, removing it, or some iteration of to get past the flat or dark cap error, and it will work fine the rest of the evening.

I really think I need to record a video of this, but here are my steps to reproduce:

focus, 2-star align, go to object, sync on it for a 3rd point, go to CCD tab, hit preview. This is when I get the error the first time. After this, Ekos behaves very strangely until it gets away from this error. By strange, it does this:

Create a sequence.
Start the sequence, the same error appears. The CCD tab has the spinner that just sits there until you hit the square stop button.



Tonight I cannot figure out how to get beyond this and am stopped.

Logs coming.

Ekos seg.faults / crashed constantly on RP4 - not able to start - by: andefeldt

$
0
0
Hi,

Two nights ago everything ran smoothly without problems. I'm running Kstars 3.4.1 (build using rlancaste's AstroPi3 script a week or two ago) on my RP4 4GB unit.

Last night I had experienced something I've never experienced before with Ekos. I started Kstars/Ekos as usual and connected. I tried focusing, but that failed to find a star. I tried the polar alignment routine, but that failed to plate solve due to a blank image. I tried capturing a 30s light frame but that just came out blank as well (and yes, my lens cap was removed :) ).
I then tried rebooting my RP4 unit, started Kstars and then opened Ekos. I selected my usual profile but just after that Kstars/Ekos crashed (segmentation fault) - it just managed to open the Indi control panel before the crash. When re-opening kstars and starting Ekos I was told that the indiserver was already running. I shut that down and tried again with the same result - seg. fault. I tried some debugging with just the mount and my ccd camera in a profile. That worked and everything started.... BUT when capturing a light frame as a test it was just blank. Also slewed to other places in the sky resulted in blank frames.

I always start kstars from the command line. I got these messages last night:


I looked at my Indi settings for my camera and noticed that most of the settings had been reset to default, except gain, offset and WB settings. Everything else had been reset.

I disconnected and tried adding my focuser (DeepSkyDad AF3) to my profile again with a seg. fault as my result...

I ran 'gdb --ex run --args kstars' and got this:


As a last resort I tried running kstars as "root" using 'sudo kstars'. This started a brand new instance of kstars and I had to set up my devices etc. again but that worked. Actually it ran better than ever - I've never had the Polar Alignment routine run as smoothly as this time as the refresh just smoothly refreshed the image every second. When running this normally it's sometimes a bit clunky in refreshing. Also the focusing was running like a dream and very fast. I then tried disconnecting my profile, shut Ekos/Kstars down and opened again. Selecting my profile and.... seg. fault! Tried just the CCD and that worked but everything in the settings was back to default again?!

I gave up! It was one of the clearest nights in a very, very long time and I couldn't capture anything. Very, very frustrating.

What's going on?

Arduino Field rotator - by: porkyhttp

$
0
0
Hi,
do you know an Arduino project that is compatible with INDI? I found most but all are ASCOM based

Issues or general comments of the new Raspbian Based Stellarmate 1.5.0 - by: AstroNerd

$
0
0
Any issues or general comments of the new Raspbian Based 1.5.0 Stellarmate, please post here.... :)

INDI Install from Astroberry.io fails on RPi4 with Buster - by: SmackAstro

$
0
0
Hi,

I attempted to follow the instructions here to install INDI server on a Raspberry Pi 4 with Buster but ran into problems. First when executing



The following was displayed in the terminal:



Control did not return to the command prompt. There didn't seem to be an error but the sudo thing seems odd. I wasn't prompted for a my password.

Anyway, I hit ctrl-C and ran the next command. No error messages.

Then I executed



And I received the following error (among other messages):



I assume step 1 didn't work so I made sure I'd entered sudo password before running the wget command and then everything worked fine. It seems that these instructions won't work for users that have sudo password enabled. This likely should be clarified in the instructions.

Thanks,

Steve
Viewing all 15748 articles
Browse latest View live


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