Get Connected!

Come and join our community. Expand your network and get to know new people!

Alfred replied to the topic 'Guiding nightmare' in the forum. 1 hour 5 minutes ago

I am currently guiding with today's nightly build and I do not experience any problems. I started the night with yesterday's nightly and did not experience any guiding problems with this version either.

An ASI 294 for guiding and an ASI 294Pro for imaging are being used. Nightly Ekos running on Kubuntu 19.04.

Read More...

Rob Lancaster replied to the topic 'Guiding nightmare' in the forum. 1 hour 20 minutes ago

It looks like you are using be internal guider correct? Did you try the same thing using phd2 remotely from Ekos?

I am not sure I understand the PS in the original post. PHD2 can be used with Ekos remotely . I worked pretty hard about a year ago to use their api to update Ekos so that it would talk more thoroughly with PHD2 to integrate all the functions that I could into the Ekos interface so that running phd2 remotely would send all the info back and it would act mostly like you are using the internal guider. Is this what you are looking for? Because if so it already does it.

Or are you meaning that you want the internal guider to be updated to work more like phd2?

One thing that should be noted is that if you are imaging with a raspberry pi remotely over the network, the best plan is to run phd2 on the pi and to control it from Ekos on your laptop. It would not be a good plan to try to guide with the Ekos internal guider controlling a guide camera over WiFi on a pi. Phd2 running on the pi is much more responsive due to download times

Read More...

Rob Lancaster replied to the topic 'Guiding nightmare' in the forum. 1 hour 20 minutes ago

It looks like you are using be internal guider correct? Did you try the same thing using phd2 remotely from Ekos?

I am not sure I understand the PS in the original post. PHD2 can be used with Ekos remotely . I worked pretty hard about a year ago to use their api to update Ekos so that it would talk more thoroughly with PHD2 to integrate all the functions that I could into the Ekos interface so that running phd2 remotely would send all the info back and it would act mostly like you are using the internal guider. Is this what you are looking for? Because if so it already does it.

Or are you meaning that you want the internal guider to be updated to work more like phd2?

One thing that should be noted is that if you are imaging with a raspberry pi remotely over the network, the best plan is to run phd2 on the pi and to control it from Ekos on your laptop. It would not be a good plan to try to guide with the Ekos internal guider controlling a guide camera over WiFi on a pi. Phd2 running on the pi is much more responsive due to download times

Read More...

Ray Wells replied to the topic 'kstars crash on short exposure (with ASI camera)' in the forum. 1 hour 30 minutes ago

Just a quick hit and run thought here. Try removing your XML files and replacing with defaults. When you downgrade the XML's keep you old settings. Hope it helps. That sucks bad on a good night. Been there...cried on Jasem's shoulder more than once. :P

Read More...

Ray Wells replied to the topic 'Guiding nightmare' in the forum. 1 hour 35 minutes ago

I guided last night with an eq6-r and an asi120c-s on a converted finder scope. With the exception of a tight cable at one point, I was able to guide sub 1arcsec 600second exposures all night...and yes i'm stoked by that unusually good night. :)
With my new system I've found my tracking failures are almost always related to cable drag or polar misalignment. Also, I always clear any sync and tuning when I start each night as the mount tends to log erroneous settings from the previous setup if I don't. This could creep into tracking speeds on some mounts. I've found that I have better results by actually forcing the mount to be a bit west weighted(camera/focuser tilted west a bit) then shooting east, to help avoid bouncing on backlash. I tend to run my gains a bit high and I most recently switched my eq6r to 1.00x in settings and guiding.

Hope something here is of help to you.

Clear skies!
Ray

Read More...

Jose Corazon replied to the topic 'Guiding nightmare' in the forum. 1 hour 59 minutes ago

wvreeven wrote: In the guide cam image the green square is not centered on a star. Is Select Auto Star selected or do you select a star manually before starting the guiding calibration?


Wouter


Wouter, when you look closely you see that Auto-Star is selected.

I am not sure what is going on, but I also would like to know the Kstars version that was used in those instances.
Remember how we were trying to solve the guiding variations last year, only to revert back to the default values in the internal guiding module.
I have exclusively used the internal guider for the last 2 years and it has been rock-solid for me.
The "cannot reach guidestar after 21 iteration possible mount or backslash problem" issue was caused by a bug in the ZWO driver back when we were dealing with this some 18 months ago, or so. So if that is back, then the ZWO driver may be at fault again?
My guiding still works great, but I also did not upgrade to the latest Indi version yet.
Please post the version you are using.

Cheers

Jo

Read More...

AstroNerd replied to the topic 'Pegasus UPB v2 script question' in the forum. 3 hours 29 minutes ago

Ah, yes I guessed I was missing something....you can tell I am not a coder... :)

Read More...

the.cakemaker replied to the topic 'Guiding nightmare' in the forum. 3 hours 43 minutes ago

Thats how it looks here. Always running away to the top...

Read More...

Picard replied to the topic 'kstars/ekos build fails on ekos/manager.cpp' in the forum. 4 hours 46 minutes ago

i have the same issue :

[ 6%] Building CXX object kstars/CMakeFiles/KStarsLib.dir/ekos/opsekos.cpp.o
In file included from /home/christian/Projects/kstars/kstars/ekos/scheduler/scheduler.h:14:0,
from /home/christian/Projects/kstars/kstars/ekos/manager.h:30,
from /home/christian/Projects/kstars/kstars/ekos/manager.cpp:10:
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h: In member function ‘void Ui_Scheduler::setupUi(QWidget*)’:
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h:432:54: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Active, QPalette::PlaceholderText, brush1);
^~~~~~~~~~~~~~~
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h:438:56: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Inactive, QPalette::PlaceholderText, brush2);
^~~~~~~~~~~~~~~
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h:448:56: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Disabled, QPalette::PlaceholderText, brush5);
^~~~~~~~~~~~~~~
In file included from /home/christian/Projects/kstars/kstars/ekos/scheduler/scheduler.h:14:0,
from /home/christian/Projects/kstars/kstars/ekos/manager.h:30,
from /home/christian/Projects/kstars/kstars/ekos/opsekos.cpp:13:
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h: In member function ‘void Ui_Scheduler::setupUi(QWidget*)’:
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h:432:54: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Active, QPalette::PlaceholderText, brush1);
^~~~~~~~~~~~~~~
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h:438:56: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Inactive, QPalette::PlaceholderText, brush2);
^~~~~~~~~~~~~~~
/home/christian/Projects/kstars/build/kstars/ui_scheduler.h:448:56: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Disabled, QPalette::PlaceholderText, brush5);
^~~~~~~~~~~~~~~
kstars/CMakeFiles/KStarsLib.dir/build.make:1671: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/ekos/opsekos.cpp.o' failed
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/ekos/opsekos.cpp.o] Error 1
make[2]: *** Attente des tâches non terminées....
kstars/CMakeFiles/KStarsLib.dir/build.make:1575: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/ekos/manager.cpp.o' failed
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/ekos/manager.cpp.o] Error 1
CMakeFiles/Makefile2:432: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/all' failed
make[1]: *** [kstars/CMakeFiles/KStarsLib.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2

Read More...

Jacob Nowatzke replied to the topic 'Starlight Instruments Focuser Boss II & HSM20' in the forum. 5 hours 3 minutes ago

Here are the logs for a quick run-through of the Focus Lynx (another question I have, is can we please have an option to *not* display the FocusLynx F2 if we don't have a second focuser attached to the controller? It seems like a waste of space, especially when you're having a difficult time with malfunctions and the continuous crashing that KStars like to do- confusing the F1 and F2 is something I do too often; not very user-friendly in my opinion.

It seems the absolute focus position command works, but is not reflected in steps count box, just to the left of steps entry. Focusing In does not work and gives error. Focusing out works once, but after does not move the motor and does not display an error.

File Attachment:

File Name: log_12-06-47.txt
File Size: 309 KB


Best,
Jacob

Read More...

Jacob Nowatzke created a new topic ' INDI control panel kicks out of Losmandy Gemini tab when selecting Site#2' in the forum. 5 hours 20 minutes ago

When editing the Site#1 name (because it is blank each time I start INDI), I type my city "Arcata", press Set, and nothing is stored. Then, when I click on Site#2, it takes me to my FocusLynx tab, instead of filling in the fields for Site#2. This issue does not occur with Site#3 or Site#4.

Best,
Jacob

Read More...

John Hoogerdijk created a new topic ' kstars/ekos build fails on ekos/manager.cpp' in the forum. 5 hours 38 minutes ago

Can't build from nightly kstars/ekos bits due to following error:

[ 13%] Building CXX object kstars/CMakeFiles/KStarsLib.dir/ekos/manager.cpp.o
In file included from /home/jmh/Devel/kstars/kstars/ekos/scheduler/scheduler.h:14:0,
from /home/jmh/Devel/kstars/kstars/ekos/manager.h:30,
from /home/jmh/Devel/kstars/kstars/ekos/manager.cpp:10:
/home/jmh/Devel/build-kstars/kstars/kstars/ui_scheduler.h: In member function ‘void Ui_Scheduler::setupUi(QWidget*)’:
/home/jmh/Devel/build-kstars/kstars/kstars/ui_scheduler.h:432:54: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Active, QPalette::PlaceholderText, brush1);
^~~~~~~~~~~~~~~
/home/jmh/Devel/build-kstars/kstars/kstars/ui_scheduler.h:438:56: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Inactive, QPalette::PlaceholderText, brush2);
^~~~~~~~~~~~~~~
/home/jmh/Devel/build-kstars/kstars/kstars/ui_scheduler.h:448:56: error: ‘PlaceholderText’ is not a member of ‘QPalette’
palette.setBrush(QPalette::Disabled, QPalette::PlaceholderText, brush5);
^~~~~~~~~~~~~~~
kstars/CMakeFiles/KStarsLib.dir/build.make:1575: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/ekos/manager.cpp.o' failed
make[2]: *** [kstars/CMakeFiles/KStarsLib.dir/ekos/manager.cpp.o] Error 1
CMakeFiles/Makefile2:432: recipe for target 'kstars/CMakeFiles/KStarsLib.dir/all' failed
make[1]: *** [kstars/CMakeFiles/KStarsLib.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2

I also can't see a way to add the bug to github, so I'm doing it here.

Regards,

jmh

Read More...

Jacob Nowatzke replied to the topic 'Starlight Instruments Focuser Boss II & HSM20' in the forum. 5 hours 44 minutes ago

Ferrante,

Thank you kindly for your reply- I appreciate you and I apologize for being too vague in some statements. Yes, I have tried three Cat5e cables (Boss/HSM20 connection)- no difference. When I first start up, the error messages, starting with "[WARNING] Unable to read focuser status...." appear. I can Focus Out 100 steps, but after cannot Focus In at all. I cannot Focus In period. My versions are the same as yours, but my firmware has just been updated to 2.3.4 (no differences observed after updating firmware).

I was at a point where I began to follow the pseudo-tutorial that you linked to, but then Focus In commands either stopped working, or still acted as Focus Out.

I suppose what I'm asking for Ekos, is that "/SI Focus Boss" is added to the FocusLynx name, and "/HSM" is added to the FeatherTouch Motor Hi-Speed or Hi-Torque model names, which makes everything straightforward. I realize I'm dealing with an Optec FocusLynx controlled shipped as the FocusBoss, but can't we make things a little more straightforward, and just call it FocusLynx/ SI Focus Boss?

I'm also having a difficult time capturing the debug logs for this module, but it's likely my own doing.

Best, Jacob

Read More...

Wouter van Reeven replied to the topic 'Guiding nightmare' in the forum. 6 hours 23 minutes ago

In the guide cam image the green square is not centered on a star. Is Select Auto Star selected or do you select a star manually before starting the guiding calibration?


Wouter

Read More...

Alfred replied to the topic 'Guiding nightmare' in the forum. 6 hours 39 minutes ago

I cannot comment on your calibration problem. But one thing you should definitely do is set your proportional gain to 44.4. Thas assumes your guiding rate is indeed 1.5 as shown in the screenshot.
I suspect this is not correct though since normally the guiding rate should be around 0.5 or 0.3 or something similar.

What you should do is this:
1. find out what the guiding rate of your mount is.
2. enter the guiding rate in the corresponding field in Ekos
3. copy the resulting P: value to the "Porportional gain" filed in the control parameters.



Read More...

Alfred replied to the topic 'Interesting bug in Ekos' in the forum. 6 hours 51 minutes ago

There is no second instance of KStars here. Only the directory is opened, nothing else happens. Also, there is no additional KStars task being listed in System Monitor either.

Read More...

Rob Lancaster replied to the topic 'Missing text in KStars tool bar' in the forum. 7 hours 12 minutes ago

I think the real question was, why didn't they have ~/.config/kstarsrc in the first place? If KStars has been opened and it has been used, options have been saved, so that file should have been created. . . or am I wrong about that? If there was no kstarsrc file, how did that happen?

Read More...

Markku Siitonen replied to the topic 'Missing text in KStars tool bar' in the forum. 7 hours 41 minutes ago

That's great :)

A simple explanation would be that the first part "sudo updatedb" creates a database of all filenames and paths it can find in the system, the second part "locate kstarsrc" reads the database and get the filename and path to the file you specify.
The semicolon is there just to separate the two commands from each other.
Next time if no files are added or removed to the system you can just do a "locate filename" and find the specified file.
You can read more of the commands with : man updatedb and man locate

Fast and easy.

Cs,
/Markku

Read More...

Wouter van Reeven replied to the topic 'Missing text in KStars tool bar' in the forum. 8 hours 1 minute ago

So it was exactly where Rob said it would be in this post

indilib.org/forum/general/2001-missing-t...-tool-bar.html#43616


Wouter

Read More...