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

Insane number of dialogue boxes asking to power on camera.... - by: universalmaster

$
0
0
Hi!

I was trying kstars/Ekos tonight and noticed that if my QHY camera is not connected or if the driver for some reason does not find it, Ekos (I think....) will open a dialogue box stating "No QHY cameras detected. Power on?" and I can press OK. Often it will just keep opening these dialogues until I kill kstars or it located the camera. The title of the window is "Indi server message".

Anyway to avoid this? :)

Best Regards,
Søren

ZWO Camera ASI 120MM Mini Mono with StellarMate? - by: stefanr

$
0
0
Have any of you ever used "ZWO Camera ASI 120MM Mini Mono" successfully with StellarMate?
I bought one but I have some issues making it work and it looks like there are no compatible firmware to that can be used to fix the issue.
Now I am thinking about returning it since I cannot make it work and I have found other topics on this forum regarding issues with compatibility.

But what should I get instead?
I have looked at these:
- ToupTek Camera G-1200-KMB Mono Guider
- Omegon Camera GUIDE 1200 M Mono

A quick search reveals that the ToupTek camera may have the same issues. But the compatibility list here on indilib.org claims that all ToupTek cameras are supported...
Omegon is not on the compatibility list here on indilib.org but the sales page of the camera claims that it is fully INDI compatible...
See this link. Can I trust that claim?
www.astroshop.eu/astronomical-cameras/om...-1200-m-mono/p,61035

I am really happy with my StellarMate and it works great with my CEM25P mount, but I have not had much luck with cameras yet.
So I hope you can help :-)

QHY 16200A connects and works but cooling does not - by: mpfjr

$
0
0
Cooling power always shows or actually +00.00 and if I for example ask it to cool to -15 the fan is at quiet/slow barely audible and the temp goes down a little and then stalls. For example I just tested my ASI and it cooled down to -15 no problem and the fan speed went fast and slow depending on what was needed. The QHY went from 24.00 to 17.56 and then stalled there. Can't get any cooler than that. if i move the fan speed slider to 100 (manual) the fan does not go any faster nor does the fan speed % change from +00.00.

As I was typing this the temp is actually now 17.72+


My ZWO 294 cooled has zero issues and works as it should.

Obviously a driver issue and one that I have been having a hard time for over a year. Anyone with this camera have this experience?

Driver version 2.5
interface 22

Issues with software update - by: duncankitchin

$
0
0
Brand new Stellarmate user - just got the unit. Looking for some assistance...

Going through the startup instructions, and when I got to the app connection screen (on iOS) and it says that it cannot continue because the version of the OS is out of date and needs to be updated.

So I went to the Stellarmate instructions for updating software, and connected to the unit using VNC. I ran the software updater from the desktop as suggested, and it failed with an error. Not much in the way of diagnostics; there is something visible in the "details" window but it auto-closes almost immediately and is replaced with a dialog that just says "package install failed". I checked at that point to see if I could connect with the app, but it still says that the software version is out of date.

Following that, I tried the command line version of the update, but I still get the same failure message. At least this time it stays around so I can read it. It says:

dpkg: error processing archive /var/cache/apt/archives/linux-firmware-raspi2_1.20190215-0ubuntu0.18.04.1_armhf.deb (--unpack): trying to overwrite '/lib/firmware/brcm/BCM43430A1.hcd', which is also in package bluez-firmware 1.2-4+rpt1~bionic1.0
dpkg-deb: error: paste subprocess was killed by signal (Broken Pipe)

can anybody help? I really have no idea how to proceed here. Any suggestions much appreciated.

eqmod communication error - by: alacant

$
0
0
Hi everyone
My eq6 connects and slews fine but at the end of the slew, the mount disconnects:

[2019-10-06T06:14:29.167 CEST INFO ][ org.kde.kstars.indi] - EQMod Mount : "[ERROR] Error: Communication failed -> tty write failed, check connection: Error: unrecognized error code "

Limits are not set and I've cleared the mount model. Earlier in the evening the mount had been fine for several hours as it had for the last year or so.
Can anyone help?

Log attached.

TIA,
Steve

DMK41 AU02.AS : How to configure it with INDI ? - by: bilbo-le-hobbit

$
0
0
Hello, two years proud owner of a DMK41 camera AU02.AS, one thing I miss: I've never been able to make it work under Linux. I yet have to go through a Windows virtualization, while the rest of my astronomical equipment is well recognized and operational with the INDI protocol under linux.
But yesterday I found a topic on the Imaging Source forum explaining a method for the camera to be recognized via v4l2. I reproduced the same method without frankly understand, but it works! I can now open guvcview and connect the DMK, the video is displayed!
Nice! I can try with Kstars ... The camera is well recognized with v4l2, but the picture is completely buggy

I've taken the same image with guvcview and kstars

What is wrong with the settings?

Ekos & INDI Development Thread - by: knro

$
0
0
I'll use this thread to post development updates for Ekos. Please feel free to share your thoughts & suggestions!

ToupTek GCMOS Driver - by: feilimb

$
0
0
Hello, I am looking into a purchasing my (first ever) guiding camera which will be used in a 50mm mini guide scope. My indi server is running on an Odroid U2 ARM device with Ubuntu Mate 16.04.

I was wondering if anyone has had any success or know of any Indi driver development for the following camera:
ToupTek GCMOS ( www.touptek.com/product/showproduct.php?lang=en&id=137 )

I have read fairly good things about them, and they use the same sensor as in the ASI120MM but are available for a lower cost.

ToupTek provide Linux drivers and an SDK (see: www.touptek.com/download/showdownload.php?lang=en&id=28 ), although their current driver appears to be for x86 / x86_64 architectures so I'm not sure whether ARM support is out of the question (for eg. Raspberry Pi, Odroid variants).

Otherwise, can anyone recommend an alternative guiding camera which has Indi driver support on ARM architectures (Raspberry Pi & Odroid) ?

Many thanks for any advice!

Capture & Solve -> Slew to Target... - by: maudy

$
0
0
Good news is that RPI3 is doing good with the imaging capture. I hope someone can help me some more. I have a couple of other posts related to this align/slew-to-target, and I am trying again to see if someone can help me understand how to improve the Slew to target.

The symptom is the Slew to target cannot work without some sort of manual intervention for me: nudging to get close enough framing for multiple night imaging sessions.

Slew to target can get my CGEM within 2'. If it works 3-4 more times it can get near 1'. After this, the accuracy is never to 30" save 2 three times in past six months.

It is not clear if I am expecting too much of the CGEM DX, if there is something I can do to improve the CGEM DX, or if there is something to do in process that can make this work better.

GOAL: use scheduler to pick target and let the RPI3 control the equipment for session on 1 or 2 targets, and also reslew close enough to the target after meridian flip. Then repeat on another night to collect more images

QUESTION: when at the sub minute level is there a way to have ekos nudge the mount instead of slewing again? It is this nudging I end up doing manually. If Ekos could nudge the mount, plate solve, and determine how much more to nudge, then this could be perfect.

Background:
- I am imaging with my C11 at f/10, so 2800mm focal length (perhaps slew to target is asking too much of CGEM?)
- The good: image capture is beautifully easy, focuser just works, control via skysafari great.
- The okay: does plate solve okay, it is not as fast as a more powerful PC.
- I need help: slew to target and time/date sync (for another day)

Meridian flip - when active and when inactive? - by: mlarsson

$
0
0
Hi!

A question about the Meridian Flip, that is now in the mount tab in Ekos (and very much clearer!): I notice that it sometimes is "inactive" and sometimes it seems active and says when there will be a MF. What makes it active and inactive? I belive I do te same things... And I'd much like it to be active, but don't see how I change inactive to active.

Magnus

Celestron CGE Pro - Ekos/Indi Won't Track - by: mesavista

$
0
0
I'm relatively new to Indi and EKOS and I'm having an odd problem. When I align my CGE Pro mount and then start Indi through EKOS, the mount connects, but I get an error stating "ERROR: Failure reading RA/DEC coordinates. Expected 18 characters, received 1. " If I power up and don't align the mount, I get the expected warning that the mount isn't aligned and that I need to align it first, then restart Indi.

I've tried every type of alignment, from a simple solar system align, to a 1-star align, to a StarSense alignment. The telescope tracks fine without Indi engaged after these alignments are complete, but the second I start Indi and the above error is reported, it stops tracking.

Equipment: CGE Pro Mount (latest firmware)
Hand Controller: StarSense (latest firmware)
Indi: Runs on Stellarmate - all other devices - cameras, focusers, etc connect and operate fine.

I do have an older NexStar+ HC that I can try, but haven't given that a shot yet. I wanted to see if I'm doing something wrong first.

Driver OnStep (LX200 like) for INDI - by: dragonlost

$
0
0
Hello.

I would like to use the project "Onstep" to control my mount (GP2 vixen). I have already built a control card and I use a card Arduino Mega 2560 (but you can also use a teensy 3.2 for improved performance).

Onstep uses language LX200:
www.stellarjourney.com/index.php?r=site/software_telescope

The developper website identifies very well the controls.
There is an ASCOM driver for Onstep and a software which exploits all the functionality that has create the developer ( "planetarium sky").

I do not need a driver who operates every possibility (driver ethernet, wifi, bluetooth and usb).

I need a driver that connects via USB and has the following functionality:

hand control:
- connection
- On set
- abort
- Parking (park, unpark and set park position)
- Tracking (on and off)

motion control:

- Motion N / S (north and south)
- Motion W / E (West, East)
- Slew rate (guide, centering, find, max)
- Slew Target
- Tracking mode (sidereal, solar, lunar, custom)
- Tracking frequency

Site management:
- As "LX200 Autostar"

Guide:
- As "LX200 Autostar"

Firmware_data:
- As "LX200 Autostar"

I try using the driver "LX200 Autostar", "LX200 Classic", "LX200 GPS". The card that connects (with sudo chmod uga+rwx /dev/ACM0). I even manage to send it to precise position. But once possible to park unpark.

But that's what does not work:

- Sends the UTC time at start
- Sends the latitude and longitude
- The "unpark" (the "park" function works)
- No button to activate the tracking
- Tracking mode does not work
- So "firmware_data", "full" does not.

If we take the driver "LX200 Autostar" should be deleted:

Hand control:
- alignment
- Use pulse cmd

- The menu "Focuser"

It must be added:
- A button on / off tracking
- A set button sets the park position = Parking position this location

This must be corrected:

Hand control:
- unpark
- Connection (wrong order for the latitude and longitude).

Motion control:
- Correct the tracking mode

Site management:
- Correct latitude and longitude control ( "*" instead of a ":")

Firmware_data:
- Correct reading of the order to "full"


To test all this it just sufficed to have an Arduino Mega and inject the code of the branch of -alpha github onstep: github.com/hjd1964/OnStep/tree/Arduino-Mega2560-Teensy3.1-Alpha

Here I hope someone can help me!
It'll be cool Indi compatible with Onstep !!!!

Afterwards we can add features but the features above sity Suffice to good use Onstep.

Thank you in advance for any help you could give me.
Where can I get a tutorial to start working on this change?

I have the basics in Python and C.

Canon 6D captures, but only after failing 1st or 2nd capture - by: jnowat

$
0
0
I have a Raspberry PI 3 running as server- updated religiously, connected by wireless or LAN (used both)
I use either a laptop or desktop with KStars.

The Canon 6D connects, shutter works, but each capture fails during a first attempt- sometimes even during a second or third.

I have tried 1.0s, 5.0s, 10.0s, 60.0s, and 420.0s exposures, as well as a combination of delays up to 60s. The issue persists. I have perused the forums here in search of a solution, and cannot find much. Will uploading logs be different between using the Pi locally versus using a client like my desktop or laptop?

This is my first post, but judging from some of the errors I've run into, I will be posting often. Very impressed by EKOS, KStars, and INDI- only frustrated by these issues and eager to solve them.

Best,

Jacob Nowatzke

From 5s exposure flow; the first 5s capture (or 420s- whichever length of exposure is set) finishes, but then is restarted after failure.

Re:Unexpected shut down of KStars and Ekos, but not Indi server - by: Avocette

$
0
0
Running KStars/Ekos/Indi on my Raspberry Pi 4 headless as a WiFi hotspot, and linking in through VNC Viewer on an iPad. Most of the things I want to do work well (better not say ‘perfectly’!) but there are occasional crashes. Specifically in Polar Alignment I have been struggling to better see the reference star against the cross hairs at the end of the correction vector. I tried the ‘zoom to fit’ button in the Alignment Vector window, and this shut down KStars and Ekos, leaving behind ‘an Indi Server’ still running. Of course this means Parking the mount and running the process again.
I subsequently located the ‘full screen’ button in the main Alignment window, and found that this does change the size of the Alignment Vector window, but not the size of the image within it, although tapping a couple of times on the ‘zoom in’ button makes the Alignment Vector window content a good size for the adjustment operation.

I’m not sure if there’s a further bug in the way the Ekos ‘minimise window’ button also minimises the main KStars window?

Many thanks to the authors for this great software!

Kstars FITS viewer keep popping up when phd2 looping. - by: TomAstro


Does ZWO EAF work with ekos? - by: Jantje

$
0
0
I am thinking of buying the zwo EAF, but my question is does it work smoothly with ekos.
do I need to install a driver for INDi?

1st imaging "session" question - by: khobar

$
0
0
Last night, my main task was figuring out the polar alignment and focus procedures, and then get a feel for the tracking of my mount. When all was said and done, I shot some pics of M42. Even with mere 30s exposures, the Fits view showed the the arms, etc. Even though everything was out of focus, I wanted to stack what I had. I only have DSS, and it reported "no stars" regardless of threshold, and loading one of the pics revealed a most black pic with a handful of blurry dots - not what I'd seen with kstars fits viewer. Gimp showed the same. But Kstars shows the files very differently. Why?

These are horribly out of focus as I was unable to get the focus part figured out. (I previously used BackyardNikon and my Bahtinov mask). In fact, to me, they don't even look like the same source picture. It's like one is flipped/upside down.

Here is what DSS/Gimp shows:


And this is what Kstars/Paint shows:


Thanks!

Canon DSLR issues - by: rankinstudio

$
0
0
Latest Kstars, Ekos, Indi

Using a canon 6D. When shooting, it is opening up the shutter for what seems like too long. It then throws this out.

Set to local only

2019-10-08T00:38:52: [INFO] Image saved to /home/rock64/temp/Light/Light_001.fits
2019-10-08T00:38:39: [INFO] Starting 1 seconds exposure.
2019-10-08T00:38:39: [ERROR] Exposure failed to save image... Unspecified error
2019-10-08T00:38:27: [INFO] Starting 1 seconds exposure.
2019-10-08T00:38:27: [INFO] Upload settings set to local only.

Set to client only ( log)
[2019-10-07T18:11:52.426 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Job requires 1.000-second images, has 0/1 frames captured and will be processed."
[2019-10-07T18:11:52.428 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Capturing 1.000-second image..."
[2019-10-07T18:11:52.518 US Mountain Standard Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 6D : "[INFO] Starting 1 seconds exposure. "
[2019-10-07T18:12:03.741 US Mountain Standard Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 6D : "[ERROR] Exposure failed to save image... Unspecified error "
[2019-10-07T18:12:03.784 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Capture failed. Check INDI Control Panel for details."
[2019-10-07T18:12:03.785 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Restarting capture attempt #1"
[2019-10-07T18:12:03.787 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Capturing 1.000-second image..."
[2019-10-07T18:12:03.831 US Mountain Standard Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 6D : "[INFO] Starting 1 seconds exposure. "
[2019-10-07T18:12:18.753 US Mountain Standard Time INFO ][ org.kde.kstars.indi] - "FITS" file saved to "C:/Users/David/Desktop/Light/Light_001.fits"
[2019-10-07T18:12:18.909 US Mountain Standard Time INFO ][ org.kde.kstars.fits] - Loading FITS file "C:/Users/David/Desktop/Light/Light_001.fits"
[2019-10-07T18:12:19.573 US Mountain Standard Time WARN ][ default] - QTableView::setSpan: single cell span won't be added
[2019-10-07T18:12:19.573 US Mountain Standard Time WARN ][ default] - QTableView::setSpan: single cell span won't be added
[2019-10-07T18:12:19.573 US Mountain Standard Time WARN ][ default] - QTableView::setSpan: single cell span won't be added
[2019-10-07T18:12:19.573 US Mountain Standard Time WARN ][ default] - QTableView::setSpan: single cell span won't be added
[2019-10-07T18:12:19.574 US Mountain Standard Time WARN ][ default] - QTableView::setSpan: single cell span won't be added
[2019-10-07T18:12:19.661 US Mountain Standard Time INFO ][ org.kde.kstars.fits] - Loading FITS file "C:/Users/David/Desktop/Light/Light_001.fits"
[2019-10-07T18:12:19.663 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.capture] - "Received image 1 out of 1."
[2019-10-07T18:12:24.439 US Mountain Standard Time DEBG ][ org.kde.kstars] - Reporting new timestep value: 60


It is saying the exposures failed, then sending the images?

It also wont capture an image with foucs or framing.

(log)
[2019-10-07T18:14:07.766 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.focus] - "Capturing image..."
[2019-10-07T18:14:07.812 US Mountain Standard Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 6D : "[INFO] Starting 0.5 seconds exposure. "
[2019-10-07T18:14:19.066 US Mountain Standard Time INFO ][ org.kde.kstars.indi] - Canon DSLR EOS 6D : "[ERROR] Exposure failed to save image... Unspecified error "
[2019-10-07T18:14:54.418 US Mountain Standard Time INFO ][ org.kde.kstars.ekos.focus] - "Capture aborted."

Running Win10 as client.

Any ideas?

Thanks

kstars 3.3.6 crashes when trying to change histogram from liner to log scale - by: suvowner

$
0
0
the crash happens on Mac OS , and running mate 1.4.4 on the pi4.

I tried to submit a bug report but not sure I did it correctly

RoboFocus bring-up on StellarMate - by: duncankitchin

$
0
0
I'm in the process of bringing up my devices one at a time on a brand new StellarMate device. I have a lot of devices that I've accumulated over the years, but all have previously been running on Windows/ASCOM, and I have never used INDI before, so I'm just feeling my way around INDI/Ekos/KStars and powering up one device at a time and checking everything out.

Latest to bring up is a RoboFocus controller. This was previously plugged in to a Windows 10 stick PC and fully calibrated and configured. Connected to it via INDI and... connected right away, found all the settings and still knows what the focus position is. Pretty impressive. Didn't even have to tell it which virtual serial port to look for.

I can set the absolute focus position through the INDI dialog without any problem, but for some reason I get errors whenever I try to set the relative position. Is this expected? I'm not sure what the behavior of the UI is supposed to be for this. I'm assuming this won't matter, since I'm expecting the focus tool to use absolute positioning (I'm just setting everything up indoors for now, so I'm not able to test) but I'd be interested to know if anybody has any thoughts on this.

I'm also getting occasional "TTY timeout" errors in the log. Not very frequent; about every 20 seconds or so. It doesn't seem to impact the operation at all. I'm assuming this is just the serial port losing a bit and tossing the request or response, but again, I'd be interested to know if this is typical.

Any pointers or feedback would be much appreciated...
Viewing all 14131 articles
Browse latest View live


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