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

Mount Control - by: emalabro

$
0
0
Dear all

I'm in trouble with a work I have to do. My idea is the following one: I'd Like to create a GUI in Python, and send variables via socket to a server program on Raspberry Pi. I decided to make the server program in C so i Can importa the various header files.h from of the API. The problem is that, if I want to control a telescope, i Would use for example the inditelescope.h set of functions, but I don't see the related .c program :dry:

Thank you

PyIndi - by: drzippiz

$
0
0
Hello, I am using the PyIndi library to control an SBIG camera for an astronomy project. The best tutorial I could find for the library is here: indilib.org/develop/tutorials/151-time-l...ith-indi-python.html

Right now I need to implement a zero-time exposure, in order to keep this system consistent with our prior system. The current response to this is:

Is there a known way of taking a zero time exposure with this library? Alternately, is anyone aware of more detailed documentation for its use?

Thanks!

Ubuntu on Windows - by: oleg

Drivers for Atik 414EX and Inova PLB-MX - by: patdut

$
0
0
Hello,

Yersterday I wanted to connect to indi the Atik 414EX and the auto-guiding camera Inova PLB-MX of my astro club but i didn't found any drivers for any of both.
(Solved today) Found the driver for Atik on Cloudmakers site: www.cloudmakers.eu/atikdrivers/
(Solved today) For the second I am not sure it exists. Found here: www.inova-ccd.fr/download/E.%20Drivers/Linux/
But the Inova doesn't appears in the cameras list ???

Thanks

Preferred order for chaining indiservers - by: dpoulson

$
0
0
Hi,

I'm just starting my deploy of indi on a raspberry pi for my set up, but I'm starting to think that putting two of them in place would be better, as to reduce cabling and potential tangles of wires as the scope moves. My current idea is:

Pi 1 on scope, with gphoto, V4L2 (Pi cam), and focuser (DIY, when I get the chance)
Pi 2 on mount with an astroeq/eqmod device

My question is, which is best to act as primary? If Pi 2 is the primary, does all network traffic (ie, all those photos) go through from Pi1->Pi2->Ekos? But if I make Pi 1 primary, is there an issue with latency for commands to the astroeq?

I'd be running both of them from their own power source, and possibly wifi connections to remove even more cabling. If I do it this way, only the Dec motor cable runs the risk of any tangles. And everything should be nice and neat.

Or am I over thinking this? Would there ever be a risk of getting cables tangled and its easier to run them all from one Pi?

indi_celestron_gps - Failed to read RA/DEC values - by: davidw

$
0
0
I get this "Failed to read RA/DEC values" error when connecting using KStars to my Celestron AVX mount. I'm running Ubuntu (wily) on a RPi2. Has anyone else experienced this, and/or is this a know issue? Below is the debug log from the session, and software versions are at the end. Any help would be appreciated.

INFO 64.505017 sec : Session log file /tmp/indi_celestron_gps_2016-04-08T18:56:29.log
DEBUG 74.697636 sec : Toggle Debug Level -- Scope Verbose
DEBUG 75.502239 sec : Toggle Logging Level -- Scope Verbose
DEBUG 91.053220 sec : Initializing Celestron using Kx CMD...
DEBUG 91.336533 sec : RES (x#)
INFO 91.336769 sec : Telescope is online.
DEBUG 91.336949 sec : Getting controller version...
DEBUG 91.337010 sec : CMD (V)
DEBUG 91.341731 sec : RES (05 1C 23)
DEBUG 91.341976 sec : Getting controller model...
DEBUG 91.342043 sec : CMD (m)
DEBUG 91.364547 sec : RES (14 23)
WARNING 91.364775 sec : Unrecognized model (20).
DEBUG 91.364844 sec : Getting GPS firmware version...
DEBUG 91.364905 sec : CMD (50 01 10 FE 00 00 00 02)
DEBUG 91.397612 sec : RES (07 0B 23)
DEBUG 91.397896 sec : Getting RA firmware version...
DEBUG 91.397975 sec : CMD (50 01 10 FE 00 00 00 02)
DEBUG 91.430259 sec : RES (07 0B 23)
DEBUG 91.430497 sec : Getting DE firmware version...
DEBUG 91.430568 sec : CMD (50 01 11 FE 00 00 00 02)
DEBUG 91.463149 sec : RES (07 0B 23)
DEBUG 91.464666 sec : CMD (t)
DEBUG 91.469929 sec : RES (02 23)
INFO 91.473475 sec : Mount is unparked.
DEBUG 91.474998 sec : CMD (h)
ERROR 96.477992 sec : Timeout error
SCOPE 96.483676 sec : CMD (E)
ERROR 101.489036 sec : Timeout error
ERROR 101.494879 sec : Failed to read RA/DEC values.
DEBUG 101.497569 sec : CMD (48 0E 39 11 04 08 10 FC 00)
ERROR 106.503074 sec : Timeout error
DEBUG 106.506371 sec : CMD (57 2B 28 0C 00 4F 16 0C 01)
ERROR 111.511745 sec : Timeout error
SCOPE 111.516666 sec : CMD (E)
ERROR 116.522010 sec : Timeout error
ERROR 116.524757 sec : Failed to read RA/DEC values.
DEBUG 116.525114 sec : CMD (50 02 11 24 05 00 00 00)
ERROR 121.529589 sec : Timeout error
ERROR 121.532293 sec : Error setting N/S motion direction.
SCOPE 121.532526 sec : CMD (E)
ERROR 126.537806 sec : Timeout error
ERROR 126.540447 sec : Failed to read RA/DEC values.
DEBUG 126.540816 sec : CMD (50 02 11 24 00 00 00 00)
ERROR 131.546136 sec : Timeout error
ERROR 131.550306 sec : Error stopping N/S motion.
SCOPE 131.550621 sec : CMD (E)
ERROR 136.555965 sec : Timeout error
ERROR 136.561048 sec : Failed to read RA/DEC values.
DEBUG 136.561377 sec : CMD (50 02 10 24 05 00 00 00)
ERROR 141.562059 sec : Timeout error
ERROR 141.564623 sec : Error setting W/E motion direction.
SCOPE 141.564842 sec : CMD (E)
ERROR 146.567569 sec : Timeout error
ERROR 146.570015 sec : Failed to read RA/DEC values.
DEBUG 146.570336 sec : CMD (50 02 10 24 00 00 00 00)
ERROR 151.575576 sec : Timeout error
ERROR 151.580193 sec : Error stopping W/E motion.
SCOPE 151.580414 sec : CMD (E)
ERROR 156.585696 sec : Timeout error

I'm running:
INDI Library: 1.2.0
Code $Rev$. Protocol 1.7.

KStars Version 2.5.0
KDE Frameworks 5.15.0
Qt 5.4.2 (built against 5.4.2)
The xcb windowing system

FLI Atlas Focuser Installation - by: carlosgib

$
0
0
Hi all, I started to installed the FLI focuser and in the pass I never managed to a make work the Robofocus to run automatically, I dont know if I am not understanding its functionality or simply the way the instruction are written. Having acquired the FLI which was the logical approached given that I have the proline, I am concerned about the difficulty that I might encounter. So, I kindly would request if anyone of the forum have had an Atlas in the past or one now, and can give me a few tips of how to better start with the testing or setting up the parameters in order to properly have an autofocusing system.

I have Focusmax or I can use Maxim DL, but first I need the Atlas to be properly installed. I will use it with a Takahashi 106ed initially.

Thanks


Chales

Cannot select ZWO ASI 120MM as guider - by: ultor

$
0
0
I'm currently using Kstars 2.4.0 and INDI 1.2.0.
I would like to use a ZWO ASI 120MM as off-axis guider controlling the mount via the ST4 port and a Canon DSLR as the imaging device.
In EKOS I can select the DSLR as both a guider or CCD, but the ZWO only appears in the CCD list.

This seems a little awkard to me as the ZWO even has a guiding port which the DSLR lacks. Is there any way to use the ZWO INDI device as guider?

BTW, the ZWO was not working at first (even though in windows works like a charm).
I tried almost everything from upgrading Ubuntu to manual compilation of INDI/driver/Kstars. The solution for me was to use the (windows-only) firmware upgrade utility from ZWO to flash the "compatible" firmware. At this point the cam works OK but only if directly connected to the PC, it almost always fails to retrieve the capture when connected through a hub. In this situation the USB traffic slider does not seem to help.

Lacerta MGEN support? - by: chrisvdberge

$
0
0
Is there any way to control the MGEN using EKOS?
Without any communication between EKOS and the MGEN I'm afraid things won't work, so looking for a way to control MGEN with EKOS.

Auto meridian flip in Capture module? - by: mlarsson

$
0
0
Hi!

I'm trying to understand how to use the "meridian flip" setting in the Capture Module. I can check so it makes a meridian flip if the hour angle is above a certain value. What is the value I am to put here? The maximum allowed angle for the capture duration, or what? I've not been able to find a description that I can use...

Magnus

No guiding tab in EKOS with my QHY-6 CCD - by: ASC

$
0
0
Dear all,
I'm using an indi server on RPI (with UbuntuMATE 15.10 and the latest indi software which I get from PPA). Have a QHY-6 connected to it as my guiding cam. The capture module works well with this setup. However, I'm not getting a guiding tab. Attaching a screen shot and a kstars.log file.

Any ideas how to fix that?

Best Regards and thanks in advance
Andy


Altair GPCam support - by: chrisvdberge

Real life testing and a few questions - by: Magnus_e

$
0
0
Hi.

Last night i got to do some testing of my future observatory, and ended up with some questions. My observatory is not yet build, so i carried everything outside and fired up my Odroid with INDI server at the remote location.

Some info on hardware.
CCD = Canon EOS 550d + Equinox 80
GUIDER = QHY (Orion Star Shot Autoguider) + Orion mini guider
Remote server = Odroid C1+
Home Workstation VM with 4 cores 4GB memory
Local network on remote and home location is cabled gigabit.
Remote speed from isp is 300 / 300 Mb/s
Home speed from isp is 75 / 15 Mb/s

As i want to control my telescope from "home" at a "remote" location i opened up a ssh tunnel to home (from the remote location) and opened a vnc session to my linux pc running KStars and Ekos. Then as i normally would do i opened a ssh tunnel from home to remote and started indiserver on the remote odroid. At this point everything worked fine. The vnc session would use mostly upload bandwidth in home, and download in the remote location, so it should not significantly affect the performance of KStars and indiserver.

First thing i did was to slew to m66 group and start the alignment module in Ekos. Note that my settings on the ccd and guider is "upload client"
The alignment module did solve when Ekos got the image, but it took 12 minutes for indiserver to download the image from remote to home.

1# Not sure how it could be that slow? (i did start indiserver -vv, but that cannot be the reason?) Should i not use "upload client"?
Also when the image solved i got the message "Reported focal length is 500mm, but solver calculated it to 625mm"

2# How did this happen? I have a SkyWatcher Equinox 80 APO PRO that is 80 / 500mm. I do have a "non focal reducing field flattener" but it should have no effect on focal length.

At this point i figured that some things would have to be sorted before i could control the observatory from home. I disconnected from home and connected to the indiserver on lan, and tested some more. The only issue i had from this point was getting a guide star. I tried auto select star in the guidemodule and it always selected a spot that seemed void of stars. After some attempts calibration ended in success, but would loose the guide star after a while. I tried selecting a very bright star, but i think it was a white pixel, because the guiding was only using input in one direction and the graph went off the scale. Increasing gain only gave me more noise, mostly rectangular lines. I have guided successfully with this setup before, but using a ST80 as guidescope.

3# So what are sane settings for the qhy? Should gain preferably be as low as possible, and how long exposure can i use when guiding?

A lot of beginner questions here, but have not had many occasions to test this winter. If i dont figure out 1#, i will have to consider having a simple desktop with KStars and EKOS on the remote location, so there will be cabled lan between KStars and indiserver.

KStars/Ekos running out of processor oomph - by: RobMeades

$
0
0
Hi there. I'm running KStars/Ekos [bleeding] as a client on Xubuntu (15.10) on a Dell D830 Latitude laptop but, after about 10 minutes of operation, KStars/Ekos stops responding. I can make windows come into focus but no buttons work and the star display will not move.

The laptop has Intel Core 2 Duo T7100/1.8 GHz processors and 4 Gbytes RAM. The RAM is never more than half used but both processors are maxed out. I am running the correct NVIDIA drivers for the graphics card. Top shows that kstars is using > 90 % CPU, Xorg next at about 15%.

My question is: should this machine spec be sufficient? If so, does anyone have any suggestions as to what I might be doing wrong?

Rob

Pyindi-client wrappers problem - by: emalabro

$
0
0
Dear all

I'm trying to follow the steps on sourceforge.net/p/pyindi-client/wiki/Home/ , but when I try to cmake ../swig-indi-python it returns me the following error:
emalabro@emalabro-VirtualBox:~/libindipython$ cmake ../swig-indi-python
-- Found PythonInterp: /usr/bin/python (found version "2.7.10")
CMake Error at /usr/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:138 (message):
Could NOT find PythonLibs (missing: PYTHON_LIBRARIES PYTHON_INCLUDE_DIRS)
Call Stack (most recent call first):
/usr/share/cmake-3.2/Modules/FindPackageHandleStandardArgs.cmake:374 (_FPHSA_FAILURE_MESSAGE)
/usr/share/cmake-3.2/Modules/FindPythonLibs.cmake:205 (FIND_PACKAGE_HANDLE_STANDARD_ARGS)
CMakeLists.txt:14 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/emalabro/libindipython/CMakeFiles/CMakeOutput.log".

Any suggestion?

CCD camera cooling procedure - by: bilbo-le-hobbit

$
0
0
Hello, I attended this weekend at a star party where I presented the software KStars and especially EKOS. People were quite enthusiastic, impressed with all the features integrated into the software and the variety of hardwares supported by INDI. Most of them are astro-photographers who use softwares under Windows.
However, they have a concern: Is it possible to program the cooling of a CCD camera level by level ? Not having cooled camera, I could not answer them. They explained the importance of the bearings (approximately every 5 degrees) to avoid damaging the camera. The absence of this adjustment would be redhibitory for them to adopt kstars / Ekos.
P.S. In less than a month, I participate in another star-party where I will reintroduce KStars, Ekos, Indi ... ;)

Raspberry Pi2 not sending DSLR data - by: supernov

$
0
0
Wondering if anyone has ever seen this.. suddenly (ofcourse during a clear night, which never happens), I'm having a weird data problem. When I start the GPhoto driver by itself in verbose mode, I get a picture taken and downloaded. But when I start it together with the EQMod and qhy5 drivers, nothing gets through! Does this mean something is suddenly interfering?

Bulb mode isn't supported - by: chrisvdberge

$
0
0
When I try to run INDI with indi_gphoto_ccd and control my Nikon D600 everything works just fine. However, when I try to control my Nikon D7000 I get the error message in the console reading: "Bulb mode isn't supported. exposure limited to maximum camera exposure. "

I found this topic with similar problem from over 2 years ago, but there it states that this issue was solved in the software?
Anything I can check/change to make this work?

Southern Hemisphere parking fail (eqmod) - by: andygn

$
0
0

File Attachment:

File Name: indi_eqmod_telescope_2016-04-08T12:11:50.txt
File Size: 104 KB

Since updating earlier this year to the latest kstars-bleeding, parking is failing reliably. It tries to park upside down for lack of a better term. Slightly alarming when it first happened.

HEQ5Pro
KStars 2.5.0
indi 1.2.0
Linux (x86_64) release 3.19.0-15-generic (xubuntu on a late 2008 MacBookPro)

Unfortunately I seem to have not captured the corresponding kstars log output by mistake. I'll do so in the next few days as this is an easy one to reproduce inside.

Looking at the eqmod log, it looks like it gets rather confused as to the location of the observer with the latitude and longitude being set to 0 at one point.

Dawn / Dusk calculation of the scheduler - by: dokeeffe

$
0
0
I'm just wondering how the scheduler calculates dusk time? It seems a bit later than I expected.
My sunset time (local time) today was 20:31 but the scheduler was saying twilight ends 22:36.
It seems a bit off to me. I had a look at an online calculator and it said twilight ends 21:06

My machine's timezone is IST (Irish Summer Time) Which is UTC+1



Viewing all 14131 articles
Browse latest View live


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