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

Can't connect to mount - by: SBPanther

September 7, 2018, 12:09 pm
$
0
0
Hi,
I'm new to using INDI and somehow can't manage to connect via CDC (Client) -> Indi Server -> Indi Driver (EQmod or Synscan) to my mount.

I'm running Mac OS 10.13, CDC 4.0-3575, Indi Server 2.7.0 (1.7.0) and tried EQMod Mount (0.3) and Orion Atlas (1.0)
As HW I have the Orion Atlas EQ-G GoTo, Shoestring's EQDIR and Prolific Technology USB to Serial with installed PL2303 v1.6.1 driver.

HW / Cables are OK as I tried EQMac -> USB2Serial -> EQDIR -> Atlas Mount successfully

My understanding:
To use EQMod driver I connect USB2Serial -> EQDIR -> Atlas Mount directly
To use Synscan driver I connect USB2Serial -> Synscan HC -> Mount

EQMod:
When adding EQMod to the Indi Server it shows yellow in the INDI server app and is not visible in CDC after hitting "Connect and get server list".

SynScan:
Shows green in INDI Server and selectable in CDC. Power up mount and initialize / do alignment via HC. Select PC Direct Mode (also tried w/o this step) and connect Mac via USB2Serial and SynScan Cable to HC. Then I open the INDI gui panel and entered as port /dev/cu.usbserial (alternatively tried with /dev/tty.usbserial as well) and always receive (with debug information active):

CONNECTION CONNECT=ON
[DEBUG] Connecting to /dev/cu.usbserial
[DEBUG] Port FD 9
[DEBUG] Connection successful, attempting handshake...
[INFO] Synscan Mount not responding
[DEBUG] Handshake failed.
[WARNING] Communication with /dev/cu.usbserial @ 9600 failed. Starting Auto Search...
[DEBUG] Trying connection to /dev/cu.Bluetooth-Incoming-Port @ 9600 ...
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[DEBUG] Port FD 10
[DEBUG] Connection successful, attempting handshake...
[INFO] Synscan Mount not responding
[DEBUG] Handshake failed.

If I try to connect a second time w/o changing anything I receive:

CONNECTION CONNECT=ON
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.
[WARNING] Communication with /dev/cu.Bluetooth-Incoming-Port @ 9600 failed. Starting Auto Search...
[DEBUG] Trying connection to /dev/cu.Bluetooth-Incoming-Port @ 9600 ...
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.

Now it is not even trying to connect to /dev/cu.usbserial

What am I doing wrong?

Thanks for you help,
David
↧
Search

Cannot launch KStars through VNC - by: Phil31000

September 10, 2018, 8:54 am
$
0
0
Hello,

I use an Odroid XU4 under Ubuntu 16.04.5 to run KStars (latest release 2.9.8, KDE 5.18.0, Qt 5.5.1). When I launch Kstars from a native display connected to the Linux system, everything works perfectly well (KStars is a beauty on this machine). But when I try to launch KStars through a VNC server, I get the following error (other programs such as PHD2 works perfectly well through VNC):

The X11 connection broke: Unsupported extension used (code 2)
XIO: fatal IO error 22 (Invalid argument) on X server ":1.0"
after 6 requests (6 known processed) with 0 events remaining.
Segmentation fault

The error occurs whatever VNC server I use (TigerVNC, TurboVNC). I tried to use different Window managers (Mate, Xfce4), but it does not change anything, the problem is still here. Going to Ubuntu 18.04 does not solve the problem either. Some googling on the issue did not really help except it might be related to the Qt layer. I am quite frustrated as I really want to be able to use VNC which is quite standard with clients running on many different systems.

Any help on this would be super!

Thanks in advance,
Philippe
↧
↧

Can’t connect to my mount - by: SBPanther

September 10, 2018, 1:01 pm
$
0
0
Hi,
I’m new to INDI trying to connect my Mac to my Orion Atlas EQ-G Goto mount.
Unfortunately I had no success so far.

My assumption:
I can connect via EQMod driver directly to the mount or I can use Orion Atlas driver to connect the the mount’s HC

HW in place:
Orion Atlas EQ-G Goto, PL-2303 USB-to-Serial Cable, Shoestring EQDIR

SW in place:
MacOS 10.13, CdC 4.0-3575, INDI Server 2.7.0 (1.7.0), Orion Atlas driver 1.0, EQMod 0.3, PL-2303 driver v1.6.1

HW (Mount, USB2Serial, EQDIR) seems to be OK, as I was able to connect via EQMac to the mount.

Connect attempt via EQMod Mount driver:
Failing very early as the driver shows a yellow status in the INDI server list. EQMod not showing up after hitting „Connect and get device list“ within CdC

Connect attempt via Orion Atlas driver:
Power up of the Mount —> Initialize & Align Mount via HC —> Activate PC Direct Mode in HC —> Connect Mac via USB2Serial and Orion Serial Cable to HC.
Now I get SynScan to select as telescope in CdC. Within INDI GUI the right port is selected /dev/cu.usbserial (also tried with /dev/tty.usbserial…) leaving all options default (for this post I increased debug information) and try to connect:

CONNECTION CONNECT=ON
[DEBUG] Connecting to /dev/cu.usbserial
[DEBUG] Port FD 7
[DEBUG] Connection successful, attempting handshake...
[INFO] Synscan Mount not responding
[DEBUG] Handshake failed.
[WARNING] Communication with /dev/cu.usbserial @ 9600 failed. Starting Auto Search...
[DEBUG] Trying connection to /dev/cu.Bluetooth-Incoming-Port @ 9600 ...
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[DEBUG] Port FD 8
[DEBUG] Connection successful, attempting handshake...
[INFO] Synscan Mount not responding
[DEBUG] Handshake failed.

If I try to connect agin right away I now receive:

CONNECTION CONNECT=ON
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.
[WARNING] Communication with /dev/cu.Bluetooth-Incoming-Port @ 9600 failed. Starting Auto Search...
[DEBUG] Trying connection to /dev/cu.Bluetooth-Incoming-Port @ 9600 ...
[DEBUG] Connecting to /dev/cu.Bluetooth-Incoming-Port
[ERROR] Failed to connect to port (/dev/cu.Bluetooth-Incoming-Port). Error: Port failure Error: Resource busy. Check if device is connected to this port.

It is not trying to connect to usbserial any longer….

I also tried to connect with Orion Atlas driver directly with EQDIR w/o HC, also w/o success.

What am I doing wrong?
Any help appreciated.

Thanks,
David
↧

How to set a custom initial position instead of north pole INDI - by: Del

September 11, 2018, 2:15 am
$
0
0
Hi everyone! I'm really new to INDI. I'm doing a thesis project in university, and i really need knowing how to set an initial custom position in INDI. I'm using KStars to see the pointing position of the telescope. What i need is a custom initial point when i run INDI driver and server. I tried parking position, but in the simulation it starts always looking at north pole instead of the parked position previously set. :( Sorry if this is not the right place to ask. Thank you for your time, people!
↧

Please explain how,with DSLR, the save,load default config work - by: stash

September 11, 2018, 10:05 am
$
0
0
I am having real problems with the configuration file of my DSLR Indi driver. It seems to have a mind of its own especially altering x,y,um,width,height parameters - this seems to have a knock on effect with the Scheduler in that it knocks Kstars out.

So want do the Save,Load,default options do exactly please and can you have more than one configuration (say I had 2 or more DSLR each diff specifications )

Thanks in advance :-)
↧
↧

Plate solving giving wrong results - by: kengs

September 12, 2018, 5:32 am
$
0
0
I'm running Kstars 2.9.8 on Window 10 64 bit. Platesolving through Ansvr.
My target was NGC6822 (Barnards Galaxy) at (from KStars):
JNow: 19h 45m 58s -14° 45' 45"
J2000: 19h 44m 56s -14° 48' 23"
I get a successful solve and the mount slews. The next solve says it is within acceptable range.
But if I then take an image and solve at nova.astrometry.net it is around 15 arc-minutes off in RA.
Results from nova.astrometry.net (J2000) are:
Center (RA, Dec): (295.932, -14.862)
Center (RA, hms): 19h 43m 43.610s
Center (Dec, dms): -14° 51' 44.593"
Size: 38.1 x 28.8 arcmin
Radius: 0.398 deg
Pixel scale: 1.96 arcsec/pixel
Orientation: Up is 262 degrees E of N
I suspect the conversion of J2000 returned by nova.astrometry.net to JNOW is in the wrong direction. Perhaps as I'm in the southern hemisphere?
Had the same issue with 2.9.6 the other day which is why I upgraded.

Attaching Kstars log and image solved on nova.astrometry.net
↧

subpixel accuracy - autoguiding - by: HelgeMK

September 12, 2018, 7:08 am
$
0
0
Would someone happen to know what "subpixel accuracy" in the context "guiding" means"?

is this a parameter to be set (eg in guide module) or a ratio related to the primary / guding scope or pixel size ccd / guidecam?

I came across the topic as I was wondering about the ideal guide scope (length/aperture) for my 500mm refractor, with ASI120 & ASI071 cams.

many thanks, Helge
↧

iEQ mount issues - by: MilesChatterji

September 12, 2018, 10:35 am
$
0
0
Hello everyone,

I have a few questions regarding kstars and the ekos iEQ driver.

First of all I have a rather noob question about the time settings in kstars. I setup my time site with the setup wizard, and noticed that it did not apply DST. I looked into the altitude and time settings, and noticed that my lat/long are correct, but the DST was set to --, and when I try to set it to yes, it gives me an error that the time site is read only and I need to create a new one. However the error seems to persist no matter how many I setup. Is there a correct operation procedure for getting the DST to stick? Once I manually correct the time, ekos then relays the correct information to my mount.

Second, when I launch ekos, and check the site settings on the INDI control panel for the iEQ mount, it shows my longitude as 272 degrees, my standard longitude is -87 degrees. Is that normal? Is it doing some sort 360 degree translation? I noticed that even with the correct time set, that while the longitude is set to 272 everything happens upside down, and backwards. After setting it manually in INDI control panel to -87 degrees HH:MM, it performs as normal. I've found myself having to do this every time despite saving the configuration. Is there another operating procedure to correct this that I need to be aware of in order to help keep both the time and longitude settings?

Thanks for any help, and sorry if these questions have been asked, I did a search and could not find anything that was exactly similar to what I am experiencing, outside of the FAQ on make sure your time site is correct.

--Miles
↧
Search

Canon EOS M6/M5 - by: silvex

September 12, 2018, 7:43 pm
$
0
0
Hi all,

I am considering either the M5 or M6 for my new all-round daily and vacation camera.

Can anyone give me some good hints why I should choose the M6 over the M5?

The viewfinder in the small body M5 seems like a great one to have.

Otherwise it seems, the specs are more or less the same, right ?

Any recommendations, towards either one of them?

Thanks,
↧
↧

How to visually frame a subject? - by: brenchen

September 13, 2018, 12:00 am
$
0
0
Hi all!

I am trying to find the feature that allows us the visually frame a target and add it into the scheduler. At the moment, all I can do is to acquire/load up an object and it will place it dead center in the frame. What can I do if I want to offset it slightly (rule of thirds it for example) visually? Is there a way to do that?

I have tried looking in manuals, tutorials, videos, googling etc. and can't find anything; maybe I'm looking for the wrong terms. If anyone can shed some light on this that would be very much appreciated!

Thank you!!
Brendan
↧

[WARNING] Can not save Park Status/Position. - by: Del

September 13, 2018, 3:10 am
$
0
0
Hi everyone! I'm making a script that changes DEC & RA coordinates and then write current position data in ParkData.xml. When i run it the GOTO works well, but when it tries to write the file with current position in KStars i get this errors:

[INFO] WriteParkData: can not write file /home/dhell/.indi/ParkData.xml: Too many open files
and
[WARNING] Can not save Park Status/Position.

I tried to change the system limit (i'm on linux) but it doesn't work. i don't really know whats wrong. I know that my commands are right 'cause i tried the single lines of code in a different terminal and it works (i'm just using indi_setprop). Ideas?
↧

QHY9 filter wheel not working anymore on Linux (Mac OK though!) - by: wvreeven

September 13, 2018, 5:56 am
$
0
0
The day before yesterday I dedicated a whole night to color imaging with my QHY9 CCD and filter wheel. I took images of the Dumbbell Nebula and Stephan's Quintet using R, G, B and L filters. Or so I thought. When I processed the images of the Dumbbell Nebula, it looked oddly colorless, apart from the edges of the image due to dithering. Close inspection of the images revealed that they all looked exactly the same, apart from guiding issues due to wind and fainter stars because of clouds passing occasionally.

So I took the camera off the telescope, attached it to the Odroid machine that I use with it and started Kstars. This revealed that the filter wheel does NOT turn and always stays at the first filter. Ekos, however, thinks it does turn because the images were put in directories with the filter name. I also tried on my MacBook and there the filter wheel does turn, suggesting this is a Linux driver issue. Both tests were done with the latest and greatest KStars 2.9.8

I attach log files from my Linux tests but I am afraid they do not show any issue. Tonight I'll image via my MacBook but I would very much appreciate it if this issue could be resolved. I don't mind compiling drivers myself or replacing files on the file system if it helps testing.


Thanks, Wouter
↧

Warn if scheduled jobs have the same name - by: wvreeven

September 13, 2018, 5:00 pm
$
0
0
Hi,

I am working on a mosaic of the North America and Pelican Nebulae and ran into an issue with the scheduler. I added two jobs with exactly the same parameters apart from the coordinates of the center of the FOV. When the first job ended Ekos thought that both jobs had ended because they had the same name. Only when I have the 2nd job a new name Ekos would start it.

Would it be possible to add a popup or other warning when two jobs with the same name get added to the scheduler? Many thanks in advance!


Clear skies, Wouter
↧
↧

QHY163M live streaming - by: DrGkill

September 14, 2018, 1:35 am
$
0
0
Dear,

First of all, I have to say congrats on the great work done here. The stack INDI/Ekos/Kstars is just what I was waiting for since a long time !

I'm just experiencing an issue with the QHY163M and the live preview / streaming.
No error logs, just a black window and no signal.
Taking pictures work like a charm, download time is fast.

Parameters :
- Ubuntu 18.04
- kstars-bleeding version last stable version from PPA (6:2.9.8+201808171225)
- indi-qhy 1.8+201808180714
- USB Traffic to 0
- cam connected with USB 3.0 wire in a USB 3.0 host port

Tried :
- Increase USB traffic
- Increase exposure time
- change USB port
- change USB wire (but this setup works fine with sharpcap)
- All tests were done daylight time so don't think it's a lack of light ;)

Has anybody experienced the same issue ? Find a solution ?
↧

[Fixed] Plate solving giving wrong results with ANSVR - by: kengs

September 12, 2018, 5:32 am
$
0
0
I'm running Kstars 2.9.8 on Window 10 64 bit. Platesolving through Ansvr.
My target was NGC6822 (Barnards Galaxy) at (from KStars):
JNow: 19h 45m 58s -14° 45' 45"
J2000: 19h 44m 56s -14° 48' 23"
I get a successful solve and the mount slews. The next solve says it is within acceptable range.
But if I then take an image and solve at nova.astrometry.net it is around 15 arc-minutes off in RA.
Results from nova.astrometry.net (J2000) are:
Center (RA, Dec): (295.932, -14.862)
Center (RA, hms): 19h 43m 43.610s
Center (Dec, dms): -14° 51' 44.593"
Size: 38.1 x 28.8 arcmin
Radius: 0.398 deg
Pixel scale: 1.96 arcsec/pixel
Orientation: Up is 262 degrees E of N
I suspect the conversion of J2000 returned by nova.astrometry.net to JNOW is in the wrong direction. Perhaps as I'm in the southern hemisphere?
Had the same issue with 2.9.6 the other day which is why I upgraded.

Attaching Kstars log and image solved on nova.astrometry.net
↧
Search

EQMod Telescope: is there any GOTO (Az-Alt) function? - by: Del

September 14, 2018, 7:19 am
$
0
0
Hola a todos! my question is easy. I'm using an EQMod telescope with an Az EQ6 Gt Mount. I know that the drivers in INDI have a GOTO function that uses DEC and RA as parameters. So... is there also a GOTO function that works with ALT-AZ coordinates? I looked in the INDI code and libraries, but nothing. I'm missing something?
↧

Shoestring USB-serial with StellarMate - by: pug916

September 14, 2018, 8:27 pm
$
0
0
Has anyone tested this USB-serial cable with EKOS to control a Skywatcher Mount. I’m using EKOS on a StellarMate.

www.bintel.com.au/product/shoestring-usb2-eq5-interface/

I’ve been using their Bluetooth serial adapter but it just failed after only about 3mths of use. I’m thinking the cable will be more reliable than their BT adapter.

Thanks in advance.
↧
↧

Issue with flat capture - by: rmor51

September 14, 2018, 11:36 pm
$
0
0
I make an update yesterday and I try to make flat with a Canon 1000D and a box led flat.
I choose flat in TYPE field.
In Calibrage I set flat source manual an d flat duration ADU=2500 (correct for a 1000D?)
I set 10 images and save the sequence.
I launch the sequence. Ekos takes one shot (with the exposure set int the screen 1 sec by default) and stop. The status of the sequence is inactive. If I restart this, back to the desktop directely. None image is captured into the flat directory.

I join the log file.

What happens ? Thank you for your help.
↧

Capture settings > 900 seconds are not maintained - by: phomer60

September 14, 2018, 11:51 pm
$
0
0
I have recently started using 1200 second exposures for narrowband.
There are three issues with this...
1) When incrementing the exposure times it jumps from 900 to 3600 seconds - intermediate steps of 1200 and 1800 would be nice and even better if this was configurable.
2) When any value over 900 seconds is set and you go to any other tab and then back to the camera tab it always sets the exposure time back to 900 - this is very annoying.
3) When logging the exposures at the bottom of the window it has started displaying the times in an exponential format.

Further, and I am not sure if this is related, when taking exposures which restart when the guiding exceeds a limit, the exposure counter if being randomly reset back to zero. I have only started seeing this happen when using 1200 second exposures.
↧

Problems with Apogee driver - by: patdut

September 15, 2018, 1:57 am
$
0
0
First problem: can't qactivate logs
Second problem:
2018-09-15T08:50:54: [ERROR] StartExposure() failed. libapogee:/build/libapogee3-QRL7Lz/libapogee3-3.1+~201805251757~ubuntu16.04.1/libapogee/Alta.cpp(278):Invalid image status, 1, for starting an exposure:4.
Unable to take a picture.
Does somebody have tested the driver and found what parameters must be adjusted to make it work ?

Forget all. It works fine.
↧
Viewing all 14088 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>