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

After update noVNC does't work - by: rafacastill0

February 29, 2020, 2:05 am
$
0
0
Hi all! After an update with

sudo apt-get update && sudo apt-get -y upgrade

Web http://stellarmate:6080/vnc.html does't connect to vnc server.

Screenshot_20200229-105524_Chrome.jpg


What will be the issue? I guess that is a chain of troubles:
x11vnc server is not running because there is not any X desktop (display) running.

Any idea?

Thank you in advance.
Regards
Rafa
↧
Search

ZWO ASI6200MC Pro failing to capture images using SM1.5 + Kstars 3.4.1 - by: astrocookbook

February 29, 2020, 4:08 am
$
0
0
Hi,
I'm trying to get my ZWO ASI6200MC Pro working with my SM 1.5 setup. Kstars is currently 3.4.1.

stellarmate@stellarmate:~/.ZWO $ dpkg -l | grep kstars
ii kstars-bleeding 6:3.4.1-stable~202002231946 armhf desktop planetarium for KDE
ii kstars-bleeding-data 6:3.4.1-stable~202002231946 all data files for KStars desktop planetarium
ii kstars-bleeding-dbg 6:3.4.1-stable~202002231946 armhf debug information for the desktop planetarium for KDE

stellarmate@stellarmate:~/.ZWO $ dpkg -l | grep asi
ii bsdutils 1:2.33.1-0.1 armhf basic utilities from 4.4BSD-Lite
ii indi-asi 1.6-stable~202002231611 armhf INDI Driver for ZWO Optics ASI cameras
ii indi-asi-dbg 1.6-stable~202002231611 armhf INDI Driver for ZWO Optics ASI cameras
ii libasi 1.3-stable~202002231549 armhf Library for ASI Cameras, Filter Wheel, Focuser and ST4
rg.kde.ksta‘+%


Debug output of loading, starting and capturing:


The key line preventing this seems to be

org.kde.kstars.indi: INDI Server: "2020-02-29T11:57:59: Driver indi_asi_ccd: No INumber 'Gamma' in ZWO CCD ASI6200MC Pro.CCD_CONTROLS"
org.kde.kstars.indi: INDI Server: ""

I'm assuming this may not be a warning and can be ignored, so something isn't able to process what it needs to.

The ZWO ASI6200MC Pro is powered and works under Windows based environments (NINA, SharpCap Pro, etc)
↧
↧

is there a topical list of available INDI driver names - by: wbirk

February 29, 2020, 7:27 am
$
0
0
hi!
after developing a full INDI client for my telescope controller project TSC (which uses INDI for direct control of cameras for guiding and astrometry), i have a question. i start the INDI server on the raspberry that does the telescope control, and i use it as a remote INDI server subsequently. for this purpose it would be nice to start also drivers that are not directly needed by the controller - is there a list of all available driver names in text/html format. i honestly speaking don’t want to pick each name from the Devices-pages here :D
yours wolfi
↧

Display bug ... - by: Marc2b

February 29, 2020, 7:52 am
↧

QHY5 old version, now working with latest Stellarmate 1.5.0.... :) - by: AstroNerd

February 29, 2020, 7:53 am
$
0
0
Just a FYI, I got an old style QHY5 mono camera a few months back, as was upset to find it no longer works with INdI / ekos, without a lot of messing about with the driver code...but I just decided to try it again last night, no idea why, but it works straight away, without any modifying of any code, with the latest SM 1.5.0..... Jasem has said he has not knowingly changed anything....but hey ho... very happy... :) just hope it continues to work in future updates...
↧
↧

Camera Guide problem with Ekos - by: Max13

January 22, 2020, 1:13 pm
$
0
0
Hello Everyone, it is my first experience with INDI system and I have a problem with guide camera (ASI120MM-S).
When the mount (CEM40) is connected the guide camera doesn't work, if I disconnect the mount the camera work.
Now, to resolve the problem I'am using the guide camera with PHD2, but I would use the the guide inside INDI system.
Do you have advice ?
Thanks in advance and Clear Skies.

Massimo
↧

KStars Mac DMG 3.4.0 beta testing needed - by: rlancaste

January 26, 2020, 10:56 pm
$
0
0
I just built a DMG based on the latest KStars and INDI source. There are a couple of drivers missing due to a couple of minor issues, RTLSDR, LIMESDR, and I think INDI Webcam. These should be resolved before 3.4.0 is actually released.

Please test it thoroughly and let me know if there are any Mac specific issues.

Thanks,

Rob

www.indilib.org/jdownloads/kstars/beta/kstars-3.4.0.dmg
↧

New Pentax Driver Testing - by: karlrees

January 16, 2020, 6:51 am
$
0
0
Since the current Pentax (gphoto2) driver in Indi is almost entirely useless (at least for my camera), I've been working on a new Pentax driver using the Ricoh Camera SDK. I think I'm at a point where it's ready for testing.

Here's the highlights:

- The SDK *officially* supports the Pentax K-1, Pentax K-1 Mark II, Pentax KP, and Pentax 645Z. However, it also supports other unlisted cameras, such as the Pentax K-70 I have been testing with. Please let me know if it works for other models as well.
- The camera must be in PTP mode (i.e. opposite of gphoto2).
- Live View works, at least for the K-70.
- Driver supports whatever pre-defined shutter speeds, ISO settings, etc. are available in your current Exposure Program (so typically set to Manual).
- Allows selection of image resolution (by changing the quality).
- Bulb mode does not work, at least not for the K-70. So the maximum exposure is 30 seconds.

Code is in my fork:

github.com/karlrees/indi-3rdparty

The driver is indi-pentax, and you need to build/install libpentax as well. This is my first original driver for Indi, and quite frankly the most coding I've done in a long time. So I'm bound to be doing something wrong, and I appreciate any feedback.

Also, I'm curious to see what the demand is for bringing in pktriggercord into the mix. The basic idea is that the driver would use the Ricoh SDK if the camera is in PTP mode, and switch to pktriggercord when the camera is in MSC. The main advantages to the pktriggercord mode would be (theoretically): 1) bulb mode / arbitrary exposure length support; and 2) possibly wider camera support. However, pktriggercord does not support live view, and from my initial testing appears to be somewhat slower and perhaps a bit less reliable.

Karl
↧
Search

Frames are not downloading with QHY367C - by: tompfe

January 21, 2020, 11:32 pm
$
0
0
Hi

I have the following devices connected to my MacBook Pro (with macOS Catalina):
- Astro-Physics Mount connected to INDI (USB-Serial)
- Focuslynx connected to INDI (USB-Serial)
- QHY367C connected to INDI (USB)
- QHY5-IIL connected to INDO (USB)
All devices are connected to two USB hubs which are connected to the Mac's Thunderbolt 3 connectors.

Starting Ekos is fine but then connecting the devices is always a bit of a lottery. The mount mostly is connected immediately, the focuser doesn't connect since a few days (but this is not the problem of this topic), the QHY5II-L connects mostly without problems, but the QHY367C makes problems. I usually have to disconnect the devices, restart Ekos and connect again. In 1 out of 10 tries, the QHY367C is connecting successfully.

I did not find a pattern to connected the QHY367C correctly. I assume it is a matter of where the camera is connected (on which USB Hub, with which other devices on the same hub), but as said, I didn't find a pattern yet.

The last two nights I have run into a new problem. Besides the usual connection problems, I cannot download anymore frames from the QHY367C. I took a 1s frame, the remaining exposure time field counted down to zero, the spinner next to the remaining exposure time doesn't stop spinning and the frame is not downloading. The FITS viewer never opens.
In the attached log file you see the log entries for the QHY367C. Theres is a message "Exposure timeout. Restarting exposure..." which points to the problem but I have no idea what creates the problem and how to solve it.
I noticed that as soon as I unplug the USB cable from the QHY376C, the FITS viewer opens immediately and the frame is displayed.

Does someone else has a similar problem and found a solution for it?

Thomas

File Attachment:

File Name: QHY376C-LOG.rtf
File Size: 10 KB
↧
↧

Don't understand EQMOD parking, please help! - by: universalmaster

January 22, 2020, 8:09 am
$
0
0
Hi!

I can't seem to get parking working with my eq6. I need to park my scope to a custom position. Sometime it works sometime it does not....

Here is what I tried to do, which I do not understand why it is not working:

1. Start indi, kstars, and ekos.
2. Unpark mount. kstars shows it is pointing near polaris. The mount does not, it points north and slightly down.
3. Turn on tracking. Right-click sync on some star which is currently north and slightly below the horizon. Kstars now show this correctly as the location of the mount. Not perfect, but likely OK for plate solving.
4. Go into indi control panel, find eqmod driver and under "site management" I press "current" under "park options" followed by "write data".
5. Then I press "park" in ekos.
6. Then I disconnect everything, closes kstars, closes indi and turns off power.

The next time I start up and unpark the mount, kstars shows it near polaris agan. So park/unpark is not working.

I don't get it. What am I doing wrong?

Best Regards,
Søren
↧

Getting old packages - by: eliot

February 29, 2020, 2:51 pm
$
0
0
The last time my QHY174M worked with INDI was around the start of January. Now whenever I update the temperature it kills the camera connection. So I think it might be related to github.com/indilib/indi-3rdparty/commit/...7037c83cc86a28b7c105 which was released after the last good build I had running.

The prove this, and get my camera running, I'm trying to revert the indi-qhy and libqhy packages on Ubuntu bionic amd64.

Specifically:
  • indi-qhy - 2.6~201911160119~ubuntu18.04.1
  • libqhy - 6.0.5+stable~201911152326~ubuntu18.04.1

However only the last 3 packages are kept on the update site, and there have been 4 updates since.

How might I get these packages?

Thanks,

Eliot
↧

ZWO EFW crashes EKOS/Kstars - by: stuartspink86

February 29, 2020, 3:17 pm
$
0
0
Apparently every time I tell EKOS to connect to my ZWO electronic filter wheel it crashes EKOS/Kstars. I can connect to all other devices just fine but when I add the filter wheel the whole program shuts down. I attached a log from EKOS. Any help is greatly appreciated!

-Stuart

File Attachment:

File Name: log_17-07-26.txt.tar.gz
File Size: 2 KB
↧

Problem Canon 6D and QHY5 - by: Astrofriend

February 29, 2020, 3:45 pm
$
0
0
Hi,
Two years ago I tried to use the Rasberry with Ubuntu Mate. I got it to work but a bit slow. I hade the KStar installed and run from the Rasberry direct. I gace up.

Now I try to do this once again but with KStar on the client PC Windows10. And this time I use Astroberry which looks great.

My Raspberry is the old Pi B v1.2 with 1GB RAM, when I know this will work I buy the new new Pi 4 with 4GB RAM.

A lot of nice people has alrady helped me. Problem 1 and 2 almost solved, still problem 3 and 4 left.

Problem 1:
Connect to USB-focuser, just a bit confusing with USB1 and ACM0 etc, it works now.

Problem 2:
I have rebuilt my spur gear with a belt drive with custom gear ratio. EQMod can not be setup with custom gear ratio. I have got help how to rewrite the EQMod driver and compile it. Difficult for me but with enough time Ithink I can handle it.

Now the problem I don't have a solution to.

Problem 3:
Canon 6D, if it's powered ant installed to the USB port when I start Astroberry it works fine. But if the camera do a power down it impossible to connect to it agian. When I used Ubuntu Mate two years ago the problem was that it installed the camera to the desktop, I unmounted it and it worked. Maybe this is the same problem, but there is no Camera installed on Astroberry desktop.

What I did in Ubutntu Mate was to use the tool dconf and disabled the automount. The problem with Astroberry, I don't have that tool and the file structure is different so I can't find the file where this setup is stored.

It must be others who have had this problem, how did you solve it ?

Problem 4:
As a guide camera I plan to use my old QHY5, I have read in this forum that it's problem with that camera. Should I keep or buy a new ? And not buy a QHY, a ZWO instead because of problem with drivers or ?

When I plug in the USB cable to Astroberry/Rasberry I get some crash and have to restart Raspberry.

That's all !

I'm a Windows guy, not Linux and that's make it difficult, so much strange things !

Astroberry is very great I think, it has evolved a lot since last time I tried to get a working Rasbarry server.

/Lars
↧
↧

StellarMate/EKOS - EQM-35 Pro guiding issues (brilliant start but then...) - by: naugustin

March 1, 2020, 12:03 am
$
0
0
Hi together,
I tried to find solutions in the forum but arrived at the end of my knowledge or rather out of ideas what to try next...

I´m running a EQM-35 Pro mount via WiFi remoted StellarMate (RasPi 3). Main camera is a ASI294MC Pro and guide camera is a QHY 5L-IIc. All cameras and scope configurations are loaded fine and all gear is reacting as it should be. The mount is connected via the StellarMAte and I have no ST4 cable connected and use pulse guiding. Polar alignment was made with the EKOS alignment tool. After slewing and plate solving to my target, I see some good guide stars in the QHY 5L-IIc frames (gain 8-10, 2 sec, 2x2 bin) but I have some issues with the reliability of the guiding. Maybe someone here faced similar or comparable issues and can give some advice.

After running the calibration and guiding started it looks all very good. Guiding in both axes is "spot on" with very little corrections made. So basically the moment you would smile, start imaging and lean back.
However, after a little while and out of the sudden the guiding is completely off, the little dots in the drift plot jump from the green/center area right into the yellow or even red and it takes a little while in recovering from that. The images of course get double stars or trails.
I tried many many different settings but nothing really stopped this behavior. Sometimes the message comes up saying "Delta RMS threshold value exceeded" - what I tried to google but could not really find any explanation. Then a new star gets picked (even if I deactivated Auto Star) annd guiding continues well for a wile again. Same problem often occurs after dithering quite often so that I have to stop guiding manually and just restart).

I have the feeling it maybe has something to do with the way the guide star but my options are limited. I tried to play with the camera settings to get better stars (gain, darks) and the box sizes but that did not solve it. Also it seems to be unpredictable - sometimes its fine for 10-15 min including dithering, and then it´s just good for a couple of minutes. Also tried alternatively the SEP algotythm instead of SMART but in general that made no difference.

The gude module main settings I´m using are:
Exposure 2s
Bin 2x2
Box 32 (tried 16 and 64 too)
Guiding Rate 0.5 (tried 1.0 too)

Calibration I do with Pulse 3000, Iterations 3 (with lower pulse the DEC calibration fails)

Guide settings:
Algorithm SMART or SEP (not much difference seen)
Lost Star Timeout 60 s
Max Delta RMS 10.00 arc sec (tried 15 arc sec too but did not change on the problem)

Dither 2.5 pixels
Frequency 1-3 frames
Threshold 2 pixels
Settle 20 s
Timeout 180 s
Max Iterations 10

Control Parameters (next to the drift plot) are on default:
Proportional gain 133.3/133.3
Integral gain 0.0/0.0
Maximum pulse 5000/5000
Minimum pulse 100/100


I would be happy about any ideas what to do/try.
One idea is to alternatively try PHD2 guiding once and see if the same behavior comes up - but I rather like to use the internal guider.

I have a second setup with a CEM25P and a (non remotely controlled) RasPi 4 and StellarMate OS. There I dont face any guiding problems at all. Guiding and dithering runs stable for hours. This new EQM-35 Pro slightly drives me nuts...

Thanks in advance!
Nico
↧

Spinning Wait Cursor (Mac) makes Plate Solving and Polar Alignment a pain - by: naugustin

March 1, 2020, 12:24 am
$
0
0
Hi there,

I´m using EKOS remotely on a RasPi 3 (StellarMate OS). So far so good, all devices are detected and I can take pictures.
The CCD, Fokus and Guide modules give reasonable fast previews (of course from the main camera the download takes a few seconds longer but thats fine).

Massive problems I have with the Align module:
Whenever I want to take a frame inn this module my Mac starts to think about something very carefully befor it does anything - meaning the "Spinning Beach Ball of Death" shows up for a while before the frame is taken. Well, for the normal alignment procedure I can live with this and just wait. But the meann thing is that this slows down the framerate for polar alignment dramatically.

When starting the 2 sec loop to adjust the mount orientation this stupid Beach ball shows off after each frame and it takes 30 sec or longer to get the next image. This makes an accurate polar alignment very lenghty, frustrating and taxing my patience. Did anyone else experienced this? Any thoughts?

Alternatively, tonight I will try a local "Alignment" profile in EKOS as a workaround and directly connected via cable for the polar alignment. But thats, of course not as it´s supposed to be ;-)

Cheers, Nico
↧
Search

Kstars crashes when changing profile... - by: Marc2b

March 1, 2020, 9:29 am
$
0
0
Simply going from my usual profile "EQ6-R@fedberry " to "Simulators" then try to connect.
Kstars crashes. I kill every INDI server on the PI then start kstars again and connect (Simulators) again. And it works...
Same thing if you try to change again your profile. Easy to reproduce.

Backtrace of the crash in att ...

- Marc
↧

Smart histogram like Sharcap to help to find the correct exposure - by: josemsubcn

March 1, 2020, 11:36 am
$
0
0
Im a newbie and I have a lot of problems to select the correct exposure to deep sky photography with a ccd. Sharcap seems to have a utility to Help to find the correct exposure. I think that could be very interesting to have any Help in función of light pollution(Bortle sky level), noise level of the ccd o cmos, the deeep sky object, etc. This is very complicarte?, as a newbie I think that yes, a lot variables to take into account, but if possible ohhhh my got!!!!!!

Jose

Enviado desde mi SM-T813 mediante Tapatalk
↧
↧

Pegasus Astro Ultimate PowerBox v2 issue on Debian 10 (probably solved) - by: vbo

March 1, 2020, 12:08 pm
$
0
0
Hello,

I'm currently adding a Ultimate PowerBox v2 from Pegasus Astro on my setup.
The setup is remotely controlled with a NUC installed on the telescope which runs Indiserver and devices drivers under Debian 10 OS ; the whole is controlled with KStars/Ekos on my desktop. The UPB v2 is connected to the NUC to manage power and ports.

I was not able to connect to the UPB v2 with Ekos. The system told me to add the current user to dialout group that I tried without success.
So, I've checked with lsusb if the UPB v2 was recognized. And it was (with a FTDI ship). Then, I've watched to /lib/udev/rules.d/99-indi_auxiliary.rules to know if idVendor/idProduct was included.
This file is normally configured for all FTDI ship but I saw that idProduct is not correct for my UPB v2. So, I have added a new line for the UPB where I have replaced idProduct 6001 to 6015 :


The new rules are then applied with :



And it works now !

So, is there any changes in the Ultimate PowerBox v2 or with FTDI ships (an addition of IdProduct) ? Is there an other solution without modifying the 99-indi_auxiliary.rules file ?

Thanks
Vincent
↧

Eqmod keyboard or gamepad control using astroberry - by: astro_chris

February 10, 2020, 2:33 am
$
0
0
Hi, I have astroberry installed on my raspberry pi4. It works great except one thing. I cant figure out how to control my mount using my wireless mini keyboard or a gamepad. Being able to do this is very useful when aligning. Surely theres a way to do this.
Thanks
↧

HEQ5 Mount STOPS Tracking and K-Stars Rendomly shuts down - by: NewfieStargazer

March 1, 2020, 4:44 pm
$
0
0
I am a fairly new used of K-Stars and Ekos and like it very much. I have, however have a recurrent issue that is causing pause for thought. I am running a RaspberryPi 4 with 4GB RAM and the latest build of Astroberry. I am controlling this remotely via K-Stars on my Laptop. Everything is working as expected, however during several nights now my HEQ5 mount randomly stops tracking. I believed that it may have been due to power supply issues, however this behaviour continued despite trying several different power supplies. I also thought that it could be R/T the power connector on the mount, however I again ruled this out by modifying the mount with a more sturdy PS connection. I really want to continue to use this set up, however it is useless if the tracking continues to randomly stop.

A second issue I have noted is that K-Stars will randomly shut down without any warning on the PC that I am using to control the RaspberryPi.

Can anyone help in this manor? I do not know if I have logs that can help, as I am new to this...perhaps hey are there and I just don't know where to look for them.

Jim
↧
Viewing all 15748 articles
Browse latest View live
Search