Magnus replied to the topic 'No notification settings in KStars' in the forum. 2 months ago

Thanks Jasem.

Using the

kcmshell5 notify
command worked well :)

Read More...

Magnus replied to the topic 'No notification settings in KStars' in the forum. 2 months ago

I just tried the above with a following reboot, and it did not work. Still no notifications.

KStars about

Version 2.7.3
Using:
KDE Frameworks 5.18.0
Qt 5.5.1 (built against 5.5.1)
The xcb windowing system

uname -a
Linux workstation 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.1 LTS
Release:        16.04
Codename:       xenial


Read More...

Magnus replied to the topic 'Tiny gmailclient suitable for Ekos/KStars notifications on Git' in the forum. 2 months ago

After getting notification settings on my laptop, and testing notifications with script option the syntax is:

$(mmm -m "Capturing video")


Read More...

Magnus replied to the topic 'No notification settings in KStars' in the forum. 2 months ago

I tried the above command and got: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
My laptop where it's working is same Kubuntu release and same kernel.

Read More...

Magnus replied to the topic 'No notification settings in KStars' in the forum. 2 months ago

Notification settings is now present on my laptop vi kstars-bleeding. Still nothing on my up to date workstation.

I'll post back if there are any changes.

Read More...

Magnus created a new topic ' Tiny gmailclient suitable for Ekos/KStars notifications on Git' in the forum. 2 months ago

Hi.
After seeing that KStars has gotten new notifications settings I put together a small node gmail client (MailMeMessage) that can be used with the 'Script' option for notifications.

Syntax is real simple, so to set a alert for 'Video capture started' the syntax would be.

mmm -m "Capturing video"

Just have to figure out how to get the notification settings in KStars.
indilib.org/forum/ekos/1878-no-notificat...tings-in-kstars.html

MailMeMessage can be cloned here: github.com/magnue/MailMeMessage
Let me know if it works or not :)

Read More...

Magnus replied to the topic 'Forum appearance' in the forum. 2 months ago

Had some glitches there, but now It's back to original theme.

I think I started a new topic while forum service was rebooted.

Still cannot Insert a image in post.

Read More...

Magnus created a new topic ' No notification settings in KStars' in the forum. 2 months ago

Hi.

Earlier today I saw the new movie with video capture in Ekos and Notification setup in KStars.
I tried updating with apt update / upgrade, but did not get it, so I pulled the git repo and compiled, and still no notification settings.
The new Video capture is there in Ekos.

I have compiled and installed all mandetory and optional dependencies.
System is Kubuntu 16.04 LTS
Linux workstation 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Repository is @
commit fccc0226efc8d945dcd1b8782859e47e46afc05c
Author: Robert Lancaster <This email address is being protected from spambots. You need JavaScript enabled to view it.>
Date: Thu Jan 26 16:06:27 2017 +0300

Read More...

Magnus replied to the topic 'Orion Starshoot Autoguider' in the forum. 2 months ago

Click on Options and disable 'two axis'




Read More...

Magnus replied to the topic 'Orion Starshoot Autoguider' in the forum. 2 months ago

So this is something that must be investigated!

I have a perfectly clear night, witch is not usual. It's a lot of moon, but I'm imaging my first nb session :woohoo:

So today I did not manage to calibrate the qhy at all. No matter what I did it would not reach start point after 30 iterations.
So what I noticed, was that it never complained about ra, only dec.
So I turned off calibration of dec. At this point the guider did not know that I have to swap de, so I enabled that manually.

What happened the? First the dec axis was dropping all the way to -20 or something, in the passing of a minute or so, but then it gradually got back on track!
It's like guiding is a self calibrating effort :)
Just look at the guide graph after it settled, and notice it's qhy5 via qhy5.
Not sure, but I'm thinking the calibration algorithm is not agreeing with the qhy5.

First picture is guiding started with uncalibrated dec, second is after it had settled. Looks like it's working just fine to me.





Read More...

Magnus replied to the topic 'Using the asi1600 (Gain=Gain|Unity=Gamma|Offset=Brightness)?' in the forum. 2 months ago

After some digging around, this is the result.

Hi. I asked the question about unity here stargazerslounge.com/topic/268797-asi160...ment&comment=3123271

Apparently it's the gain setting of 139, so a therm and not a setting.


Unity gain refers to a Gain setting of 139. It's the value that produces 1 ADU per electron. Doesn't mean very much in practice except that no extra dynamic range is obtained by going below a gain of 139, as I understand it.


This results in Unity = A Gain of 139 | Gain = Gain | Brightenss = Offset | Gamma (apperently a camera setting that is not present in ascom). From what I understand Gamma = 50 is the default (neutral) setting.

Could be nice with that last conclution in the CCD faq, as it took some digging to resolve :)

Read More...

Magnus replied to the topic 'Using the asi1600 (Gain=Gain|Unity=Gamma|Offset=Brightness)?' in the forum. 2 months ago

Ok. I added a post on (the) ZWO formu, hopefully someone can clarify.

zwoug.org/viewtopic.php?f=17&t=6756

Read More...

Magnus created a new topic ' Using the asi1600 (Gain=Gain|Unity=Gamma|Offset=​Brightness)?' in the forum. 3 months ago

Hi.
In preperation for installing the asi1600mm-c I'm taking cooled flats and biases.
One thing I'm having issues to understand is that the image settings in the INDI driver is different than the official asi drivers.

The asi uses gain, unity gain and offset, but thee INDI driver has Gain, Gamma and Brightness.
I guessed on the translation above based on the range of values I can set in the driver, but not sure if its correct.
I hope they are 1 to 1 translations and that the indi driver does not calculate the actual settings from gamma and brightness? Is it just for consistency with other cameras?

Also when tis is answered, perhaps it's a good addition to the CCD Faq? Will save people from guessing.

Thanks in advance, Magnus

Read More...

Magnus replied to the topic 'Orion Starshoot Autoguider' in the forum. 3 months ago

The 3sec exposures was a little out of the ordenary. I usually try 0.5 first and then work my way up. When seeing is bad I start to get white streaks all over the image, and the stars are gone. It usally happens when I do not realize I'm imaging clouds :) I need a sky meter in my observatory!

Read More...

Magnus created a new topic ' 20 minute meridian flip Celestron AVX' in the forum. 3 months ago

Hi everyone :)

So this is something quite strange as I have a lot of not (optimal) settings to combat some (issues).

The Celestron AVX has a feature to keep imaging across the meridian up to 20 deg. This is really a nice feature, as you can balance your mount to have East Heavy Balancing and get more use of it before you have to flip. On some targets you might not want to image much further than 20 deg past meridian depending on the alt of the target at that time, so all in all a good feature, but I can not use it!

With the design of my observatory I need the mount to be parked 'flat', pointing on ~182, 1 (az alt). If I let the mount pass the meridian with 20deg then the parking position would randomly be on the east or left side of the observatory. (as 182 can be reached from either side if the scope is allowed to pass the meridian). I will soon install a light source for flats that makes it so the scope has to park on the east side. To force this to be true I have set the settings in the AVX to allow for imaging 0 deg past the meridian.

Not sure that any of this is to blame, but when I'm imaging and the scope reaches the meridian the scope stops tracking. Guiding stops, and if I'm imaging there is a lot of trails due to no tracking. So then I should be able to wait until the object I'm imaging to pass the meridian (wait a minute or so), then slew to the same object and the scope will flip. This does not work. The scope stays on the east side of the meridian even if I issue slew commands. It looks like it tries to slew to the target without flipping but fails as its not allowed to pass the meridian. The reason I mentioned the settings above about the possibility to slew 20 deg past the meridian is because it takes 20 minutes before I can slew to the object I'm imaging and the result is a meridian flip.

One way I know of fixing this, is if it was possible to set the 'Meridian' option in the driver. The AVX has a meridian option that you can set to 'Prefer Current | Prefer East | Prefer West' By setting this it is possible to tell the mount to do the flip even if it thinks it can continue to image across the meridian. I would have to change it back before parking, but then I would not miss 20 min imaging every time a object passes the meridian.

Anyone know of another way to fix this, or if the Meridian option in the AVX is even documented? If someone has any tips on how to make this work, then please let me know.

Magnus :)

Read More...

Magnus replied to the topic 'Orion Starshoot Autoguider' in the forum. 3 months ago

myxlflik wrote:

The SSAG does seem able to more reliably connect for me via INDI now as well. Perhaps I will give the built in guiding a shot again once I have some decent weather to try.

Hi myxlflik(?)

Just want to share that I'm using the Orion SSAG successfully with boult in ekos guider.

That's a truth with some modifications. It does work with Celestron AVX with 'Guiding Via' set to celestron gps, and use pulse cmd set in the celestron driver.
I have also one or two times managed to calibrate with 'Guiding via' QHY5, but it seams more likely to fail.

I would like to add that i have never had any issues connecting the SSAG and getting images from it. It's always the calibration that is the tricky part.

Just an half hour ago or something I had ha patch of clear skies, opened up my roof calibrated and started guiding. (Then as always a lot of clouds! [damit!])

Some notes about maximizing the chance of success. Polar aligning is a lot more important than PHD2 on Windows. When I was using windows I could point my scope to north with a Android compass and set the mount to 59deg and PHD2 would calibrate. This does not work with the built in ekos guider (atleast not with SSAG).

By using the Polar alignment tool in Alignment module I now have ~35 sec error in Az error and ~15 sec error in Alt. The one thing that makes the PA tool difficult to use is that it uses 'Capture and Slew'. This does not work with a poor PA. As the images are downloaded and the solver solves, then the scope has drifted away from the solution in time for it to solve. I always ended up getting closer and closer until the solver error was more or less the same every time.

My fix to this was to set to 'Capture and Sync' Every time the solver syncs then slew to the middle of the solution, and the PA tool continues. Not sure but I suspect the tool might be less accurate this way?, however you will get close enough to eventually re run the tool with 'Capture and Slew' and so complete a good PA. Not sure that my PA with 5 sec and ~15sec is the best, but it's all that i had (time) for in the cold weather.

I'm not sure what the celestron driver's 'Pulse CMD' does and why th SSAG is more likely to complete calibration when it's done. The 'Guide Via' option does make Ekos send guide signals directly to the mount, so the guiding part of the SSAG is not used, and the ST-4 port is bypassed. (at this point I think the SSAG is reduced to a camera, and non of the guiding capabilities of the device is used).

Figured this could be useful info for some people with the SSAG.

Picture of todays guiding. (not very good seeing, so the guide graph is a little wobbly) :)




Read More...

Login

3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!