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

Pulsar2 issue with PyIndi client - parking/unparking - by: alenide

July 19, 2018, 3:05 am
$
0
0
Hi everybody,

I'm of indi protocol and I'm trying to write a code to control my telescope by means the PyIndi-client.
The telescope is on fork mount and the Pulsar2 (PULSAR HAND 3.1 V5.7a firmware update 02/2018) manage the slewing.
I'm writing an almost automatic code to unpark, slew and park the telescope but testing one by one the single functions I had a problem with the park/unpark.
Running the code it seems that it is not able to send the command of park and unparking, so if the mount is parked and I run the code to unpark, it runs and ends successfully(that means without stop during the execution with some error) but the mount remain parked.
If someone has any suggestion about the possible problem of error please let me know.
Attached the code that I run, probably I was not very clear so if you need more details.

Thank you in advance
Daniele
↧
Search

first dither loses guide star and aborts capture - by: alacant

July 19, 2018, 6:02 am
$
0
0
Hi everyone
The first dither is so large that PHD2 cannot recover the guide star, even though the dither i set at only 3px. I tested this on a 250 f5 and a 150 f5 with the same results.
After that,it seems that no dither pulses are sent as PHD2 does not respond to the dither command.
Any ideas?
TIA,
Steve
logs: drive.google.com/open?id=1hRe12w3rZA7KBjR_VeutuUfmedlMCpsl
↧
↧

Could not open file /tmp/kstars/phd2.fits - by: alacant

July 19, 2018, 8:30 am
$
0
0
Hi
Loads of these errors:

[2018-07-18T23:23:00.126 CEST INFO ][ org.kde.kstars.fits] - Loading FITS file "/tmp/kstars/phd2.fits"
[2018-07-18T23:23:02.638 CEST INFO ][ org.kde.kstars.fits] - Loading FITS file "/tmp/kstars/phd2.fits"
[2018-07-18T23:23:02.640 CEST CRIT ][ org.kde.kstars.fits] - "Could not open file /tmp/kstars/phd2.fits. Error could not open the named file"
[2018-07-18T23:23:05.265 CEST INFO ][ org.kde.kstars.fits] - Loading FITS file "/tmp/kstars/phd2.fits"
[2018-07-18T23:23:08.172 CEST INFO ][ org.kde.kstars.fits] - Loading FITS file "/tmp/kstars/phd2.fits"
[2018-07-18T23:23:08.173 CEST CRIT ][ org.kde.kstars.fits] - "Could not open file /tmp/kstars/phd2.fits. Error could not open the named file"
Th frequency is related to the -in this case- 2 second guide exposure.

Eventually capture is aborted -the log ends abruptly- and kstars disappears from the screen.
The PHD2 window is refreshing fine and guiding is good. AFAICT, PHD2 doesn't write anything to /tmp. Any idea of the cause of these error messages?
TIA
Logs:
drive.google.com/open?id=1EAKu5qeg-KkyI05wsyL94wjh_9Dir2G_
↧

What's next for EKOS? - by: Lead_weight

July 19, 2018, 10:48 am
$
0
0
The platform has become very mature over the last year. Attention seems to be diverting towards EKOS Live. I'm wondering what are the next big features that EKOS still needs to support to continue advancing the platform?

From the forums I can tell there's still some development being put towards the scheduler, and refining it. Efforts are still going into better driver support. Are there really any big sets functionality left out at this point? What is the future direction of EKOS?
↧

BUG: ZWO ASI 183 MC PRO does not work in full resolution! - by: RogueSquadron

July 19, 2018, 11:26 am
$
0
0
Hi,

here's another bug: ZWO ASI 183 MC PRO does not work in full resolution in Rasperry Pi! It keeps on crashing when starting live video or when taking a preview image the Rasperry freezes completely when trying to display the downloaded image.

It is purely related to the resolution (5496 x 3672). I have another ZWO ASI 290 MC which works well. I turned down the resolution of the 183 to the one of the 290 (1936 x 1096) and it works as well. It seems KStars / Ekos can not handle the big data sizes.

To be honest, I am a bit disappointed right now as NONE of my equipment seems to be working without problems with Ekos:

Skywatcher EQ6-R: driver keeps on freezing (at least on Mac via the handcontroller, did not yet try on the Raspberry with direct cable)
Canon 7D: Canon driver crashes, as well as the GPhoto, have to get out and power off and on the Canon
Skywatcher AZi GTI: does not work at all with Ekos
ASI-290 MC: Does not record temperature data
ASI-183 MC Pro: See above

I am wondering if I should really get the focuser, I was luring at ;-)

So, please keep up the good work so far with KStars / Ekos, but please please fix some of the issues at least!

Thanks

Rogue
↧
↧

Timeout Setting for Guiding when it should re-align - by: RogueSquadron

July 20, 2018, 1:15 am
$
0
0
Yesterday I had the following scenario with the Scheduler:

- tracking to traget (M27).
- Aligning successful
- started to calibrate guiding but then the mount was moving to fast and moving way off the target. Guiding calibration was never successful, because it could get hold of the guiding star

I had to stop the process and start over and then it worked.

Here is my recommendation / wish:

When guiding is not successful for some time and KStars even notices that the mount has moved way off the target, then please go back to alignment and do it again. Even if the guiding would have been successful after a few minutes the FOV would not have the object in view anymore.
↧

When is the temperature threshold being applied? - by: RogueSquadron

July 20, 2018, 3:05 am
$
0
0
I was just taking 300secs darks and realized the set temperature threshold was not taken into account during the session, but only at the beginning? Is that the intended behavior?
↧

slew before dcap - by: Bundy

July 20, 2018, 4:46 am
$
0
0
I have a very small observatory, is its possible to slew to the object before decapping the telescope? ( i assuming scripting can achieve this, but wondered if there was just a simple setting.

thanks

d
↧
Search

EOS 6D wrong exposure times - by: seescho

July 20, 2018, 5:45 am
$
0
0
The error with the mirrorlockup has gone thanks to the last commit. But now, i have another problem with the 6D:

Exposure-times longer than 1s result in pictures with exposure-times set in the camera. Exposure-settings in EKOS are ignored.
Exposure-times 1s and lower work as expected

Camera is set to M-Mode.
↧
↧

Shared libraries problem with ATIK drivers on Raspbian - by: crw4096

July 20, 2018, 8:44 pm
$
0
0
Hi,

I just created a new Raspbian Stretch install and installed all the INDI lib packages. When I tried to start the server with my devices, the ATIK filter wheel and CCD drivers complained of missing shared libraries:

and

Both messages are repeated multiple times.

Having hacked shared libs before, I created symlinks from the existing libs to the versions the drivers wanted:


This seems to satisfy the loader, but I haven't tried this out with the actual equipment yet, so, no idea if it works.

Any advice? Certainly I'll try out the equipment with this hack in place, but is there any way we can get these drivers updated to the recommended lib versions?

For completeness, I should say I ran "sudo apt-get updates; sudo apt-get upgrade" after the initial setup of Stretch, so I don't know if there were originally earlier versions of these libs present...

Thanks,

Charles
↧

make is failing with a target error - by: phomer60

July 20, 2018, 11:54 pm
$
0
0
I am getting the following error from a build today.. This is the first update in about a week and is on a Raspberry Pi running Raspbian.

kstars/CMakeFiles/KStarsLib.dir/build.make:2549: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/ekos/ekoslive/message.cpp.o' failed
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/ekos/ekoslive/message.cpp.o] Error 1
CMakeFiles/Makefile2:328: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/all' failed
make[1]: *** [kstars/CMakeFiles/KStarsLib.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
↧

How do I have EKOS upload images via ethernet to my Mac? - by: PK

July 21, 2018, 7:17 am
$
0
0
I am connected to Stellarmate via Ethernet through VNC.

Everything woks well, but I want to have EKOS upload my images via the ethernet instead of saving them on the Stellarmate Pi.
Can someone explain what I use in the Local "Remote" Dirctory fields so the files come back across ethernet to my Mac?

Thanks!
↧

Focus with assorted filters - by: PK

July 21, 2018, 10:28 am
$
0
0
What are the steps required to set up my filter settings to include an offset per filter - or should I just perform an autofocus between every filter change?

PK
↧
↧

indi-eqmod DEC reverse disabled upon restart - by: alacant

July 21, 2018, 3:07 pm
$
0
0
Hi everyone. I think this may be related to guiding flips I'm having with PHD2 guiding.
If I enable Reverse DEC in eqmod and save the configuration, the next time I restart INDI, it is disabled again. I have to enable it each time I start a new session,
Would it be possible to make it sticky?
Cheers,
Steve
logs: drive.google.com/open?id=1DoAn-zMBlGQB_DUsrRzgS2mCOTZOHTIQ
↧

Scheduler - Exposure past start-up time on ASAP setting - by: El Corazon

July 21, 2018, 3:21 pm
$
0
0
Hi Eric and Jasem,

I came across a new idiosyncracy in the scheduler: When I program a specific target and I set it to start ASAP it will work fine ONLY if I start the scheduler BEFORE astronomical twilight allows it to run (it goes to sleep until then). The same settings will no longer work once the earliest startup time defined by astronomical twilight has past. In that case the scheduler will tell me that the job is invalid, because startup time has passed (by anything between 0 and 3 seconds, depending on how fast the scheduler reacts to the push of the start button).

I would think that all that is required is to program a 10 second delay, i.e. add 10 s to the actual time at the moment the scheduler is started when set for ASAP. The only workaround I have found so far is to manually program a startup time with a delay added, but for that I need to sit at the computer and it is laborious to do if I need to restart the scheduler for any number of reasons, like the focuser failing or the guide module not finding a guide start right away.

Attached the log from 2 nights ago, not sure how informative they are. I had to add manual startup times between 2215h and ~2240h local time, because of the above described past startup time issue.

Please let me know your thoughts,

Jo

PS: Attachment was too large, here link for download: www.dropbox.com/sh/x6qa5fp1pv54i3x/AABWK...Zu-oxlNawATBt7a?dl=0
↧
Search

Captures stalled permanently after dithering - by: gbeaton

July 21, 2018, 3:27 pm
$
0
0
Last night guiding and dithering was working pretty well. But a few times the captures stopped with a status indicating it was waiting for dithering to complete. The problem was that dithering had already completed. It appeared to occur when by chance the guide star was lost during dithering. So in the end guiding resumed but captures halted. I was able to getting going again by manually stopping capture and starting again. It seemed to continue where it left off.

Attached are logs.
↧

Scheduler - Exposure past start-up time on ASAP setting - by: El Corazon

July 21, 2018, 3:21 pm
$
0
0
Hi Eric and Jasem,

I came across a new idiosyncracy in the scheduler: When I program a specific target and I set it to start ASAP it will work fine ONLY if I start the scheduler BEFORE astronomical twilight allows it to run (it goes to sleep until then). The same settings will no longer work once the earliest startup time defined by astronomical twilight has past. In that case the scheduler will tell me that the job is invalid, because startup time has passed (by anything between 0 and 3 seconds, depending on how fast the scheduler reacts to the push of the start button).

I would think that all that is required is to program a 10 second delay, i.e. add 10 s to the actual time at the moment the scheduler is started when set for ASAP. The only workaround I have found so far is to manually program a startup time with a delay added, but for that I need to sit at the computer and it is laborious to do if I need to restart the scheduler for any number of reasons, like the focuser failing or the guide module not finding a guide start right away.

Attached the log from 2 nights ago, not sure how informative they are. I had to add manual startup times between 2215h and ~2240h local time, because of the above described past startup time issue.

Please let me know your thoughts,

Jo

PS: Attachment was too large, here link for download: www.dropbox.com/sh/x6qa5fp1pv54i3x/AABWK...Zu-oxlNawATBt7a?dl=0
↧
↧

Connecting to same DSLR camera model not possible - by: AstroWill

July 22, 2018, 3:51 am
$
0
0
Hi,

Currently I've been dual imaging using two KStars instances. I have attempted triple imaging with three instances and it works but my QHY5 is very unstable and unpredictable (besides not being suited for 300s+ subs). A friend has lent me a 550d to try out and I already have a 550d of my own.

A setup I'm testing tonight is as follow: 450D (modified) + 550D (modified) + 550D (stock). I can connect to the other 550D because of identification issues.

If there a way to change the ID of the 2nd Canon 550D so that Device Manager sees it as a different device?

Many thanks in advance,
Will.
↧

ASI 183 with USB 2 creates extreme readout noise at one side - by: RogueSquadron

July 22, 2018, 5:17 am
$
0
0
Hi, I did some tests with the ASI 183 MC Pro and found out that when connected at USB 2 it creates extreme readout noise at one side of the sensor.

As I would like to use the cam with StellarMate, I wonder if there are any settings I can change to eliminate this problem. I know the cam has 256 MB built in DDR memory actually to prevent readout noise due to slower connections.

I attach 2 photos, one with no noise at USB 3 and one with at USB 2. Both are 300 secs darks in the same environment taken at the same temperature
↧

indi-webcam - by: doume

July 22, 2018, 6:13 am
↧
Viewing all 14088 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>