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

Solving fails - by: chrisvdberge

April 20, 2016, 2:15 pm
$
0
0
I'm having trouble with the offline solver.
Here is what I did and know so far;

- Installed the indexes 4203 and up from indilib.org/about/ekos/alignment-module.html
- used sudo dpkg -i astrometry-data-*.deb to install them
- adjusted astrometry.cfg to point to the right folder containing the indexes
- put in the correct settings in Image Info to make sure the resolution is correct
- the FOV in 'Solution Coordinates' states the correct value
- I'm using the default Options.
- I know the coordinates are within 3 degrees of the actual position. (radius is set to 30)
- I keep getting the 'Solve failed' message after the solver runs succesfully through the index fits
- I can solve the image successfully through nova.astrometry.net

Any things I could check? Some more settings somewhere?


edit: one more thing I now notice is that often the solver will go to field objects 91-100 and then stop and simply state the solve failed. But now I'm running it again and it is going to 121-130 (and still running)
Could it be due to this that it is failing? Is it simply not running long enough somehow? (limited by processor time?)
↧
Search

Running ekos on debian, without ppa - by: lock42

April 21, 2016, 10:10 am
$
0
0
Hello everyone.

I need your help. I'm running on debian testing and in consequence I do not use ppa.
I cloned git://anongit.kde.org/kstars.git to get last sources of kstars but I cannot find ekos in Tools menu.
Could you give me help on how to proceed ? Must I compile sources ? I don't find it.

Regards,
Cyril
↧
↧

Linguider and colour SX cameras - by: rumen

April 23, 2016, 9:24 am
$
0
0
Hi,
I am one of the core developers of lin_guider.
I want to add colour support for Starlight Xpress cameras to lin_guider.
In order to do it I need some help from the owners of the colour SX cameras.
I can not figure out from the documentation how the camera reports different
colour pattens and i have only mono camera for development. That is why
I need some test code to be executed on a linux box with colour SX
camera connected to it. Please help!

To run this code you need g++ and libusb-1.0 development installed.

To install them on Ubuntu/Debian/Mint:
$ sudo apt-get install g++ libusb-1.0-0-dev

To compile the code run:
$ make

To run the test tool (The SX camera should be connected):
$ sudo ./sx_test 1

The output should look something like this:
=== CUT ===
sxList: 'LodeStar' [0x1278, 0x507] found

Camera params:
name: LodeStar MONO (model:70 FW:0x1000a)
image: 752 x 580 (16 bpp)
pix_size: 8.60 x 8.30 um
color_matrix: 0x0fff
extra_caps: 0x05

Starting Exposure 1.00s...
Saving Image: LodeStar-MONO-752x580-16-0x0fff-1.00s.fits
=== CUT ===

Please Point the camera to something meaningful and choose
appropriate exposure time (for example 0.1 s) and run it again:
$ sudo ./sx_test 0.1

Open the produced fits file with your favorite fits viewer and
if it looks ok. Please send the output of the program and the
saved fits file to: This email address is being protected from spambots. You need JavaScript enabled to view it.

The images should not be Astro images, any image should
do as long as there are some details on it and I can guess
the correct colours :)

Thank you!
Rumen Bogdanovski

File Attachment:

File Name: sx_test.tgz
File Size: 9 KB
↧

setting permissions in virtualbox ekos bleeding - by: lynxsky

April 23, 2016, 2:51 pm
$
0
0
I installed ekos bleeding on mac using virtualbox. My imager is recognized and will load on indiserver but my mount is not recognized and it tells me I need both read/write permissions on my port , I am using the prolific USB to serial converter and have been successful in the past having indiserver recognize the lx200austostar at least after i set permissions and joined dialout group from the command line. I don't know how to do anything from the command line in virtualbox ekos install and I don't know other than the modify filter from device settings of virtualbox how to make it recognize anything other than the prolific adapter itself. What is the next step to getting ekos virtualbox bleeding to see my lx200autostar mount? thanks.
↧

Starizona MicroTouch - by: marcopeters

April 24, 2016, 11:30 pm
$
0
0
Hello everyone,

first of all, thanks for the awesome INDI framework.
What is the current support for the Starizona Microtouch Focuser. I have seen a kernel commit to add the vendor and id information to the linux kernel. Does this mean, that someone is working on an INDI driver ?

Thanks and clear skies,

Marco
↧
↧

kstars crash in remote usage with vnc - by: patdut

April 30, 2016, 9:28 am
$
0
0
Hello all
I am trying something different today.
Just a remark I made a recent update of kstars-bleeding (the last one I guess). In my memories kstars worked through vnc before (but I am not truly sure).
So...
My first idea was to use indiserver on a remote device and kstars on my laptop. This work is still ongoing and works quite fine. I have just some improvements to do.
The second idea is to try to workaround some difficulties I meet with the first idea: trying to run all kstars/ekos/indi on the remote device and use vnc viewer on my laptop.
Vnc works fine but when I try to launch kstars on the remote device I get a message about a core dump (I don't know where is the core file)
I tested kstars locally on the remote device connecting screen, keyboard and mouse to it. All works fine.
So I guess this is a X server issue but I don't know how to confirm it neither how to fix it.
Any idea is welcome.
Patrick
↧

Newbie trying to test a camera - by: chexmix

April 30, 2016, 7:41 pm
$
0
0
Hi all --

I am completely new to astrophotography, almost new to VMs, and no stranger to Linux (user since 1999). I'm sitting on my couch with my new ZWO ASI120MC-S, trying to test the camera out using Ekos.

So far I've experienced no happiness. There are or appear to be multiple places to get devices connected in KStars.

If I follow Tools->Devices->Device Manager, go down the list to 'CCD' and then pick 'ZWO CCD' and click 'Run service', I get the following

2016-05-01T02:15:51: startup: /usr/bin/indiserver -v -p 7624 -m 100 -f /tmp/indififo99bc1dc9
2016-05-01T02:15:51: listening to port 7624 on fd 3
FIFO: start indi_asi_ccd -n "ZWO CCD"
With name:
FIFO: Starting driver indi_asi_ccd with name (ZWO CCD)
2016-05-01T02:15:51: Driver indi_asi_ccd: pid=1371 rfd=4 wfd=7 efd=8
2016-05-01T02:15:51: Client 5: new arrival from 127.0.0.1:38242 - welcome!

... which, yup, looks pretty good. Now, if I go over to the Tools->Ekos screen, I select 'Local' for Indi mode, 'ZWO CCD' under 'Select Devices' and ... wait, there's a button to 'Start INDI'. Didn't I already do that? If I click this button anyway, I get a popup saying

Ekos detected an instance of INDI server running. Do you wish to shut down the existing instance before starting a new one?

I answer 'Yes', get the message "Connection to INDI host at localhost on port 7624 lost. Server disconnected." and KStars closes (or crashes).

If I try to get things started by going to the Ekos screen FIRST ... I pick 'ZWO CCD' and nothing else, hit 'Start INDI' and get

2016-05-01T05:30:43 Unable to establish:
+ ZWO CCD
Please ensure the device is connected and powered on.
2016-05-01T05:30:37 INDI services started on port 7627. Please connect devices.
2016-05-01T05:30:37 Starting INDI services...

The port number has changed ...

If I then go BACK to 'Devices', I am able to 'Run service' again (on port 7628 this time) with no messages about INDI already running, but there are also no changes on the Ekos screen: only "Stop INDI" and "Options" are available. And that's as far as I've gotten.

What am I doing wrong or possibly not doing at all? It seems the port numbers should be the same, for one.

Thanks,

Glenn Becker
↧

indi_temma no longer listed in Devices page - by: giorgio_ne

May 1, 2016, 1:19 pm
$
0
0
I've noticed that indi_temma is no longer listed in the Devices pages under Telescopes. What is the reason? Has support been dropped?
↧
Search

How to set park position - by: chrisvdberge

May 1, 2016, 2:46 pm
$
0
0
Sorry if this is documented somewhere obvious, but I couldn't find how I can define the park position for the scope.
Last time I hit the park button I had to do an emergency stop since the mount was slewing to some weird position and the scope was almost hitting the pier :(
So, how do I define the park position?
↧
↧

I am giving this a try - question about developmen - by: perfrej

May 1, 2016, 11:58 pm
$
0
0
Hi all,

I have decided to write an INDI driver for 10Micron GM-series mounts and for two special hardware units that I have designed and written ASCOM drivers for (I also wrote a popular ASCOM driver for 10Micron mounts).

My intention is to test Ekos as scheduler and controller of my remote observatory in Southern France. I have downloaded the new VM and simply like to know which compiler and development packages I need for this venture. I am not unfamiliar with Linux, but have written very little for it. I did, however, write stuff for Unix in the early 80's B).

So, would someone be kind enough to kick-start me with a list apt-gets for compiling the INDI Library and my coming drivers? Another companion question would be whether there are ready made TCP connection stuff that work sort of like the standard serial ports. 10Micron mounts have both serial and TCP connection possibilities.

All the best,

Per

I will, of course, make all drivers available when they are reasonably stable.
↧

DEBUG(F) undefined symbol, linking problems? - by: Magnus_e

May 2, 2016, 4:00 am
$
0
0
Hi.

So i'm updating my custom roof / power relay driver, and thought i would swap from IDLog to DEBUGF(INDI::Logger::SESSION.. and now i get a undefined symbol in runtime.


When i run
i get

I have tried googeling for similar errors, i think its the "std::__cxx11::basic_string<char,std::char_traits<char>" that's a clue to the issue? Some solutions i found was adding -D_GLIBCXX_USE_CXX11_ABI=0 to CMAKE_CXX_FLAGS. This gives me on compile time, so the issue lies elsewhere

Am i missing some import / library linking here?
I am compiling with


Have also tried

In cmake_modules i have FindINDI.cmake

In .cpp file that uses DEBUG(F) i have #include <libindi/indilogger.h>
In .h file #include <libindi/indidome.h> and class USBRelay2 : public INDI::Dome {

Would appreciate any help.
↧

Canon 350D suddenly no exposure? - by: mlarsson

May 2, 2016, 11:50 am
$
0
0
Hi!

I've run into a odd problem with my EOS 350D. I use a serial shutter release with it. Camera as well as everything else is connected to a Raspberry Pi, and controlled remotely (well, from indoors) from a laptop.

Before, it worked nicely. Now, however, after an upgrade to lateste indi (and a short period of using another camera, 70D), it simply does not expose - shutter is not released. I try with and without shutter release, no change - no exposure.

Funny thing, is that if I connect it directly to my laptop, it works nicely - with the serial shutter release.

I do have a USB-hub at the R-pi. I've tried connecting directly to the R-PI, no change.

Attached is two log files. The driver log contains to attempts, copied in. One with and one without shutter release But thers is nothing in them Actually, nothing happens in the INDI window when I press Preview in the capture module, but the capture module says it is taking an exposure.

What can I check or try to understand this?

Update: to clarify: I recently updated indilib on the R-pi - before that it worked. I updated again now, to the very latest (as of today). However, my laptop is also updated, so it should be same version (I guess), but it works with the laptop, so maybe it has nothing to do with indilib version.....

indi-gphoto version on the raspberry pi:
$ dpkg -l | grep indi-gphoto
ii indi-gphoto 1.4 armhf INDI GPhoto (DSLR) Camera Driver.

Magnus
↧

Hard day's night... - by: bilbo-le-hobbit

April 17, 2016, 5:39 am
$
0
0
Bad night last night ... The EQ6 altitude adjustment screw breakage (hopefully, i have also an heq5), cable problems, and EKOS that crashes when I want to access the directories or save a sequence. I'll try to arrange the rest, but to EKOS, what can I do?
I made screencasts of the bug that I could reproduce in simulation:
ekos save seq. crash
ekos change directory crash

I'm on ubuntu 15.10 64 bits, gnome-shell, last version of kstars/ekos, nomadic installation (no observatory)
↧
↧

Canon 350D suddenly no exposure? - by: mlarsson

May 2, 2016, 11:50 am
$
0
0
Hi!

I've run into a odd problem with my EOS 350D. I use a serial shutter release with it. Camera as well as everything else is connected to a Raspberry Pi, and controlled remotely (well, from indoors) from a laptop.

Before, it worked nicely. Now, however, after an upgrade to lateste indi (and a short period of using another camera, 70D), it simply does not expose - shutter is not released. I try with and without shutter release, no change - no exposure.

Funny thing, is that if I connect it directly to my laptop, it works nicely - with the serial shutter release.

I do have a USB-hub at the R-pi. I've tried connecting directly to the R-PI, no change.

Attached is two log files. The driver log contains to attempts, copied in. One with and one without shutter release But thers is nothing in them Actually, nothing happens in the INDI window when I press Preview in the capture module, but the capture module says it is taking an exposure.

What can I check or try to understand this?

Update: to clarify: I recently updated indilib on the R-pi - before that it worked. I updated again now, to the very latest (as of today). However, my laptop is also updated, so it should be same version (I guess), but it works with the laptop, so maybe it has nothing to do with indilib version.....

indi-gphoto version on the raspberry pi:
$ dpkg -l | grep indi-gphoto
ii indi-gphoto 1.4 armhf INDI GPhoto (DSLR) Camera Driver.

Magnus
↧

Canon 350D suddenly no exposure? - by: mlarsson

May 3, 2016, 7:37 am
$
0
0
Hi!

A little bit of an update:
I've been experimenting with this problem, and there simply is no way that I can make the raspberry pi take an exposure with the 350D. The same camera works without problems on my laptop, running kubuntu 15.10. And the raspberry pi works nicely with a 70D, so it is not a general problem with indi or the gphoto driver, but seems specific to the 350D.
Driver indi_gphoto version 1.4, interface 10, both on laptop and on raspberry pi. (but the package in the kubuntu laptop is slightly differently named, see post above)
USB-hub or no USB-hub makes no difference.

And there is not much of a logfile produced by indi-gphoto. The only thing is this in the INDI-window:

2016-05-03T14:30:32: Driver indi_gphoto_ccd: snooping on Losmandy Gemini.EQUATORIAL_EOD_COORD
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='Losmandy Gemini' name='TELESCOPE_INFO'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: snooping on Losmandy Gemini.TELESCOPE_INFO
2016-05-03T14:30:32: Client 0: sending <setTextVector device="GPhoto CCD" name="ACTIVE_DE
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_SLOT'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <getProperties device='CCD Simulator' name='FILTER_NAME'>
2016-05-03T14:30:32: Driver indi_gphoto_ccd: read <defTextVector device='GPhoto CCD' name='SHUTTER_PORT'>
2016-05-03T14:30:32: Client 0: queuing <defTextVector device='GPhoto CCD' name='SHUTTER_PORT'>
2016-05-03T14:30:32: Client 0: sending <defTextVector device="GPhoto CCD" name="SHUTTER_P

I note that this ends in a truncated manner, as if the driver crashes.

Anyone got any ideas on this? My May project, depending on this modified camera, seems to be in serious troubles....

Magnus
↧
Search

Indi driver for "SPOX" spectroscopic automation - by: djibb

May 4, 2016, 4:27 am
$
0
0
Hi all,

I've just received to beta test a SPOX module :
github.com/uranos498/Spox

This module allow to command from a computer Flat/calib/dark module for Shelyak spectroscops. It is base on arduino (see github page).
My aim is to build an indi driver but I'm very very new to this (driver write), but I know well SPOX module, components and arduino code inside. (we can change it)

If someone is interested in helping me...
There's 2 repositories (due to difficulties to use gitlab on windows) :
github.com/uranos498/SPOX
and
gitlab.com/ashashiwa/spox

I can help you to mount a "SPOX like Box" (2 LEDs, 2 switches, an arduino...) and there is a multiplatform GUI to command it :
gitlab.com/ashashiwa/spox/tree/master/Ar...ted/pySpox/pyspox_ui (only tested on linux but... may be works under windows.... don't know... it's python/Qt... has to work ;) )

Thanks ;)

JB
↧

Status display - by: NickK

May 4, 2016, 5:35 am
$
0
0
Hi, hot on the heals of getting the C2 ATIK drivers working.. I'm trying out the idea of using the ODroid SHOW2 TFT screen as a status screen on the scope. Literally this will be attached to the scope in the box with the C2.

Is there anyway I can get the guider images being taken, the focus FHWM, the RA & DEC, focus, connection state etc from the components on the INDI system?

I've included a test image - using a real open phd 60x60 guider star image just to demonstrate. I'll then want to create a C/C++ component that sits on the C2 and through a connection with INDI accesses the current state of the system.

I'm thinking of ideas such as disconnects to cause the screen to flash red for example so it's happily running I don't need to do anything.. infact it could cycle around including displaying the last sub taken (scaled), the current focusing image etc. IF it can get to the info!

↧
↧

ODroid C2 IR control for slew/focus - by: NickK

May 4, 2016, 5:53 am
$
0
0
The Odroid C2 has an IR sensor. I have an Apple IR remote control. It has up/down/left/right/select pad then menu and play buttons.

I'm thinking that it's possible to provide control for manual movement/focus using the IR control.

I know there's a joystick control - can that do focus too?
↧

Canon 7D/7D mkII bulb exposure with mirror lock - by: hoxca

April 14, 2016, 7:56 am
$
0
0
Hello,

I recently dig into INDI with a Raspberry PI3.
I got 2 Canon camera and try to get it work with the indi_gphoto_ccd driver.

In ekos, i get into a lot of trouble for bulb exposure with the Canon 7D Astrodon
my Canon 7D mkII work pretty out of the box but i cannot manage the mirror lock funtion and this one is not modded.

For investigation, i switch to gphoto2 command line trying to find a solution.
After a lots of testing, i find the "fiat lux" incantation for gphoto !

Both camera with the rotary dial set to B

gphoto2 --set-config imageformat=RAW --set-config autoexposuremode=Bulb --set-config capturetarget=0 --set-config eosremoterelease=2 --set-config eosremoterelease=4 --wait-event=10s --set-config eosremoterelease=2 --wait-event=65s --set-config eosremoterelease=4 --set-config eosremoterelease=0 --capture-tethered=2s --wait-event-and-download=2s

I think that it's pretty generic for Canon device,
Is it possible to leverage this into indi_gphoto_ccd driver and ekos ?
↧

New drivers profiles in Ekos - by: knro

May 4, 2016, 1:03 pm
$
0
0
If you update KStars tomorrow, all your prior drivers selection will be gone! But do not despair, there is now a driver profile editor similar to the profiles in INDI Web Manager.

By default, there is the Simulators profile, and you can add as many profiles as needed, both local and remote. If you encounter a bug in the new profiles, please met know.
↧
Viewing all 14131 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>