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

QHY Driver: Testing required - by: Schwarze

$
0
0
Hello,
some time ago, I noticed that the temperature regulation for cooled QHY cameras is broken. It starts cooling, until the temperature is reached, and then stops measuring and regulating the temperature for the rest of the night.
Now I have build a patch, which does fix the issue, which works fine with my QHY8L camera. Before I submit a pull request, some more testing is needed. I think, following should be tested:
1. Does the change have any effect on non cooled why cameras?
2. Does the change have any effect on cooled, non regulated why cameras?
3. Does this issues exist on other cooled regulated QHY cameras, and if so, does the patch fix this too?

If you own a QHY camera and are willing to test, your help would be appreciated.


I can provide the compiled binary for 32 Bit ARM compiled on Astroberry 2.0 (Debian Buster...). It should run on raspberry 3 and 4 32 Bit, but I am not sure if it works on Ubuntu based distributions. But I could build one on a Raspberry Pi 3 running StellarMate if required.
For other architectures, I do not yet have a build environment, but at least amd64 and maybe i386 could be arranged.


For those who compile their INDI Library themselves here is the patch:

diff --git a/indi-qhy/qhy_ccd.cpp b/indi-qhy/qhy_ccd.cpp

index eeaef0dd..84fa1149 100644
--- a/indi-qhy/qhy_ccd.cpp
+++ b/indi-qhy/qhy_ccd.cpp
@@ -27,7 +27,7 @@
#include <algorithm>
#include <math.h>

-#define TEMP_THRESHOLD 0.2 /* Differential temperature threshold (C)*/
+#define TEMP_THRESHOLD 0.05 /* Differential temperature threshold (C)*/
#define MAX_DEVICES 4 /* Max device cameraCount */

//NB Disable for real driver
@@ -1778,6 +1778,12 @@ void QHYCCD::updateTemperature()
{
SetQHYCCDParam(m_CameraHandle, CONTROL_MANULPWM, m_PWMRequest);
}
+ // Temperature Readout does not work, if we do not set "something"
+ else if (TemperatureNP.s == IPS_OK)
+ {
+ SetQHYCCDParam(m_CameraHandle, CONTROL_MANULPWM, CoolerN[0].value * 255.0 /100 );
+ }
+

ccdtemp = GetQHYCCDParam(m_CameraHandle, CONTROL_CURTEMP);
coolpower = GetQHYCCDParam(m_CameraHandle, CONTROL_CURPWM);
@@ -1803,9 +1809,21 @@ void QHYCCD::updateTemperature()

if (TemperatureNP.s == IPS_BUSY && fabs(TemperatureN[0].value - m_TemperatureRequest) <= TEMP_THRESHOLD)
{
- TemperatureN[0].value = m_TemperatureRequest;
+ TemperatureN[0].value = ccdtemp;
TemperatureNP.s = IPS_OK;
}
+ // Restart regulation if needed.
+ if (TemperatureNP.s == IPS_OK && fabs(TemperatureN[0].value - m_TemperatureRequest) > TEMP_THRESHOLD)
+ {
+ TemperatureN[0].value = ccdtemp;
+ TemperatureNP.s = IPS_BUSY;
+ }
+
+
+
+
+
+

IDSetNumber(&TemperatureNP, nullptr);
IDSetNumber(&CoolerNP, nullptr);


Regards

Dirk

Guiding failed after meridian flip - by: RugbyRene

$
0
0
Hi all,

Last night I was imaging M83 and my mount did a meridian flip just before midnight. The flip went off without a hitch except for the guiding. Basically when it captured and sub-framed it didn’t pick up a star. I had to stop the calibration and manually pick a star for it to guide on.

Are there any settings I should look at so that it works next time?

Regards

Rene

Celestron Skyris 274c and 618m - by: aj55

$
0
0
Dear all,
I have a Celestron Skyris 618m and a 274c. Both are made by the Imagingsource (DMK)
Are there drivers for these camera's ?
Under windows the'll run in IC Capture and Astroart for instance, but no go under Stellarmate (which sees them as DMK camera's but refuse to connect)
Cheers, Arnold

Scheduler ignores meridian flip - by: pmneo

$
0
0
Hello I have in issue with the scheduler. I have created an Job for M51 with a sequence of lrgb wich should be run in a loop until twilight. The meridian flip is set to ha > 0.

The flip was executed well, but with the next loop the slew to target reverts the flip and my teleskope collided with the mount :(

My only idea is to expand the seqeuence to several hours ...

Thanks

No dithering applied between two Capture Sequences: Bug or Feature? - by: pmneo

$
0
0
I have configured a LRGB seqeuence:

3xL, 3xR, 3xG, 3xB

Dithering is only applied the following way:

L1, Dither, L2, Dither, L3, NO Dither, R1, Dither, R2, Dither, R3, NO Dither, G1, Dither, G2, Dither, G3, NO Dither, B1, Dither, B2, Dither B3 ...

So is this is a bug or a feature?

Thanks for clarification.

Astrometry to fetch Comets - by: aselonia

$
0
0
Hi

My equipment's are the followings:
AZEQ6 - Meade SC 10" - KStars/Ekos/Indi on a tinker board/Ubuntu 18.04 _ Capture images with Sony Alpha 7S

Since two weeks I do have some issues with my AZEQ6, one motor prevents to perform the correct 3 stars triangulation but tracking is ok.
So I'v decided to find a procedure to use the polar alignment tool and astrometry tool of ekos to route the telescope to a comet position (C/2019 Y4) or any position in the sky.

I did the polar alignment, it works perfectly. I test the accuracy by pointing a bright star anywhere in the sky and activating the sideral tracking - OK zoomed star remains perfectly centered on the APN's view.

Now I need your help to accomplish the following:

1- I manually point the area of the comets by unblocking the RA and DEC locks - OK
2- I took a picture of the area the telescope is currrently pointing and 've submitted the pict to nova.asstrometry.net that returns me the names of objects. (the comet is not in the field otherwise it would be a chance !)

From there I would like to resync kstars and shows the position where the telescope is pointing by using the picture I took. My understanding is that I can't use directly the astrometry module of KStars because it don't know where I'm pointing in KStars so astrometry is not resolving.

I plan to use the load and slew function but from there I'm a bit lost. Do I have to park the telescope at the current position ?

Thanks to help by providing a procedure to find any object in the sky by using the astrometry module either local or external.

Thanks
JP

Celestron Skyris 274c and 618m - by: aj55

$
0
0
Dear all,
I have a Celestron Skyris 618m and a 274c. Both are made by the Imagingsource (DMK)
Are there drivers for these camera's ?
Under windows the'll run in IC Capture and Astroart for instance, but no go under Stellarmate (which sees them as DMK camera's but refuse to connect)
Cheers, Arnold

BUG: EKOS - PHD Guiding not configurable - by: starhopper

$
0
0
Hello Forum,

I want give EKOS another try but it fails configuring PHD. May I made something wrong?
I am running KStars Bleeding and made a new profile with the profile editor. First issue, if I select
PHD2 it does not fill the TCP/IP port with the tcp port. I had to fill it manally. Pressing save.
A recall of the profile shows that I will not be saved. EKOS does not show the Guiding tab.

Thomas

INDI focuser driver for Waveshare Stepper Motor HAT for Raspberry Pi - by: kross

$
0
0
Hello all!

I have written a new INDI driver, for the Waveshare Stepper Motor HAT. I've been using Radek Kaczorek's driver for the Adafruit Motor HAT for a while now, and while it works, I came across this Waveshare HAT which looks to be a bit better.

Advantages of the Waveshare Stepper Motor HAT versus the Adafruit Motor HAT:
  • Real stepper driver, a Texas Instruments DRV8825
  • Up to 1/32 microstepping, for super quiet and smooth focusing
  • Adjustable current limiting
  • Doesn't use i2c
  • Can power the Pi and the stepper motor with a single 12V connection. No more 12V and 5V dual power to the Pi!

Even with 1/32 microstepping, I can get very reasonable speeds, since we're not using i2c, but are just triggering a single GPIO pin every time we want to step the motor. At 1/32 microstepping, I can get a full revolution of a 1.8 degree stepper motor in about half a second. 1/16 or 1/8 microstepping will, of course, be 2x and 4x faster, respectively.

From a programming standpoint, controlling the stepper is quite simple, and they include sample C code (unlike Adafruit which only includes Python code, which must be ported to C). My driver code was heavily inspired by (read: stolen from) Radek Kaczorek's original astroberry-amh driver.

Anyway, the code is here. If you do try it out, drop a note and let me know how it works out for you!

github.com/k-ross/indi-wmh-focuser

FITS viewer - by: Acapulco Rolf

$
0
0
Hi
Is there some setting that needs to be invoked in order for the ekos FITS viewer to show the HFR value for a given capture during an imaging session?

All images appear to show -1 for the HFR value

(SOLVED) IP Webcam - by: sting

$
0
0
Hi to all,

I was trying to start a connection between my smartphone camera, via IP Webcam app (android), choosing "connection" as "IP Camera", but there is no way to start, even if all seems ok in configuration.
I tried also using PHD2, with no result.
May be a problem in INDI Server or something similar?
Everything works fine, connecting to the camera via web browser inside the lan.
Has anyone experience?
Thanks!

Luca

Create an action(srcipt) at the end of a sequence - by: constant1462

$
0
0
Hello
so I'm about to finish my remote control observatory and I'd like to do an action all at the end of a sequence.
Here's the actual order of things, which is ok, it's already working:

One command to open the roof: Okay.
2 open the telescope cap: ok
3 open roof: ok
4 takes the telescope out of the park position :ok
5 shooting :ok
6 put the telescope on park:ok
7 closes the telescope cap : ok
8 command to close the roof:ok
9 roof close : ok
10 do the Flat: NOT OK

so how can I make sure that at the end of it all I can run the Flat sequence.
I specify that the lighting of the light for the Flats will be controlled by a relay on an arduino board.
I have 2 choices: either I automate it with the roof control, or I give it an arduino box with the "arduino swicher" command.

But how do I give the order in the sequence to make the flats when the roof is closed or when the dome is parked?

Thanks for your help!

Ubuntu MATE now works on Raspberry Pi4 - by: El Corazon

$
0
0
Looks like one can get Ekos to run now on the RPi4 using Ubuntu MATE at 64 bit.

Huge improvement over the Pi3.



Ekos 3.3.6 : No summary screen preview on MacOSX - by: nmac

$
0
0
I still have this problem on my Mojave Mac:
indilib.org/forum/general/5462-new-mac-k....html?start=36#41572

Fits images are still not displaying on summary screen preview during the capture session.
I have confirmed and I have this option selected, so it should work. It only works on independent fits viewer window.

Since I have reported this for the first time it never worked again, either building from sources or downloading from KStars website.

Nobody has this problem???

kstars versions for osx Sierra - by: Fivel

$
0
0
Hello.
I was told that Rob could help with this, not so new topic.
When I looked at the OS requirements, to install newer versions of kstars, versions 3.4.0 and newer only required OSX 10.12+
Unfortunately, when I tried to install and run version 3.4.0, I got the error that said my OS was to old to run it.
I am running version 3.3.9 with no issues. I suppose that the downloads page should be edited to reflect the minimum OS version needed as 10.13 (or higher?).

Fivel

ALS - Astro Live Stacker - by: Gilles

$
0
0
Hi
Dragonlost and i are very proud to introduce our little toy "ALS" / Astro Live Stacker.
It's a small Python(3) application dedicated to live stack.


It's watching a specified folder for new FITS frames to arrive.
Each new frame is stacked with previous result.
Two methods are available : sum and mean.
It can also register on the fly.
If Bayer pattern is present in fits header, demosaic is also done on the fly.
You can use it with eKos sequence, telling ALS where FITS files are stored.
But you can use any other software providing FITS frames.

We will try to add a dark substraction,
and will add this interesting request from one of us :
Opening a webserver to publish stacked image.
Why ?
During a public session, people could connect to our local hotspot and see and download "their" image :cheer:

I've done a video to show it working, it's in french but you'll see it running with a CCD simulator and real archived frames


It's really an early beta -but working- toy
Any ideas and improvments are wellcomed, feel free to involve :
github.com/gehelem/als

This is the place for me to thank Dragonlost for his tremedous help

Gilles.

Problems with two scopes running in parallel - by: sterne-jaeger

$
0
0
Hi all,
I am experiencing a strange behavior that I cannot explain currently. This happens only when I have two mounts with their own INDI server running in parallel.



The only thing that they have in common is that they share a Starlight Instruments focuser controller, that is running physically on the one scope, but it can support two focusers.

What happens is that sporadically EKOS gets totally confused, it receives informations from both mounts. This is not 1:1 reproducible, but it sometimes happens that both mounts receive slew commands. And it also happens sometimes that one of the KStars crashes.

Am I the only one seeing this effect?

Some facts about my setup: Avalon Linear & Avalon m-zero, INDI servers running on Raspberry PIs, Starlight Instruments FocusLynx with Starlight Instruments PDMS focusers.

- Wolfgang

PEC recording with EKOS - by: lemmu

$
0
0
Mount is Ioptron CEM 40. Is there is a way to record PEC with EKOS?

Advice re Astrophysics Experimental driver - by: Spartacus

$
0
0
Hi ,
The weather in Queensland, Australia has been terrible this weekend so I have been having another go at an abandoned KStars project.
I am currently using KStars/EKOS with an NEQ6 running EQMod for astrophotography with everything working fine. My son has an AP1100 and has recently left home and lucky for me has left me in charge of the AP1100 mount.
We tried to use KStars with the AP1100 about 12 months ago but gave up after a few months of frustration. This time I have a lot more knowledge and have managed to get it working pretty much perfectly apart from it insists on using DEC co-ordinate as 00:00:00 for Park 3 instead of -90:00:00. This puts the scope at 90 degrees to the mount axis. Generally Astrophysics Park 3 should point directly at the South Celestial Pole e.g. in line with the mount axis. Az co-ord is 180:00:00 for both of these positions so the co-ordinates showing in the park position in INDI is the same as this does not show DEC.
This is not necessarily an issue just a curiosity. Anyone know what I may be doing wrong? Otherwise in use the mount knows where it is and slews correctly and everything else works as expected which is great. I have tried doing a custom park but it always reverts to the DEC 00:00:00 setting.
Cheers
Mike

Re:Problems with two scopes running in parallel - by: sterne-jaeger

$
0
0
Hi all,
I am experiencing a strange behavior that I cannot explain currently. This happens only when I have two mounts with their own INDI server running in parallel.



The only thing that they have in common is that they share a Starlight Instruments focuser controller, that is running physically on the one scope, but it can support two focusers.

What happens is that sporadically EKOS gets totally confused, it receives informations from both mounts. This is not 1:1 reproducible, but it sometimes happens that both mounts receive slew commands. And it also happens sometimes that one of the KStars crashes.

Am I the only one seeing this effect?

Some facts about my setup: Avalon Linear & Avalon m-zero, INDI servers running on Raspberry PIs, Starlight Instruments FocusLynx with Starlight Instruments PDMS focusers.

- Wolfgang
Viewing all 15748 articles
Browse latest View live


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