Get Connected!

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

Bryan Bourn created a new topic ' Fresh Ubuntu Install?' in the forum. 46 minutes ago

I did some searching, but can't seem to find an answer.  I'm trying to install KStars/Ekos on a clean Ubuntu OS (onboard Mini PC).  According to the "Installing KStars" KDE site (, the apt install script doesn't result in a working KStars.  I suspect there's a bunch of prerequisites (INDI?) that are required.  I've tried the snap package as well, but that gives me a really old version.  Does anyone have a working set of commands to get KStars/Ekos installed and running on a clean Ubuntu system?

sudo apt-add-repository ppa:mutlaqja/ppa
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding


i ve test with the simulator . 

it is the option 'reverse DEC with pier" in the Guide option which  is my problem
if i check it , DEC is not swap when i move from West to East 
if i uncheck it , Dec is swap . 

the description of this option was not clear for me . And i cant find it on help file ? 



OK for that that come after;

1) There is a buggy behavior with certain ASUS routers where WiFi clients connected at 2.4 GHz and 5 GHz can't reliably communicate with each other (although internet connectivity for both is fine). The solution is to turn off "Airtime Fairness" (I did it on both bands):

2) On the iOS devices, it is important to use http vs. https, in order for noVNC to work. Either will get you the start page, but at least for me, only http will work to connect VNC.

3) If you are having trouble getting your Pi to connect via 5GHz (and you are close enough to the router for 5GHz) make sure you have your network localisation set properly. Your Pi needs to know what country you're in so as to know what the correct frequency bands are to 5GHz WiFi.




Yes, it will be very useful to be able to abort a job as soon as an altitude limit is reached. If this limit is useful to star a job, the same utility lies on finishing it. Good point



It probably is related to what Jasem wrote. I used a 5 slot EFW before ad probably didn't erase the XML file.


Weird. My 8-filter EFW reports 8 filters and has worked fine from the start, also running on kubuntu 20.04.2 LTS.


I find fewer drivers to be better, so chose a ZWO guider to go with ZWO mains. If the pair does not work, there is usually a good chance that the main will not work by itself either, so reverting 1 driver allows things to work again.
Right now is a good example, where the new ASI camera SDK appears to be causing some problems for myself and others. Reverting to the previous version, and both cameras work again.

I currently guide with a 290MM Mini, and quite like it.



Jasem Mutlaq replied to the topic 'iOptron GEM45' in the forum. 4 hours 12 minutes ago

GEM45 is supported, so is iPolar, but I don't think you can capture more than 1 second in iPolar now since it uses a generic webcam driver.


I ve check these tow option 

If you're using eqmod with your eqm, it knows when and what to change during a flip.
Don't check anything other than what is already there by default. Simply perform the calibration with the default settings.
Clear the calibration data and go again.
Cheers and clear skies,


Glad to hear that it works.

There's a locking safety switch in Telescope and Dome Tabs:
In Telescope Tab-> Options->Dome locks:  This prevents the mount from unparking when dome is parked. 
And in Dome Tab->Options->Mount locks:  This prevents the dome from parking when mount is unparked. 

In my remote hosting facility they provided a device for additional security: two magnet switches fixed on the RA of the mount and connected directly to the roof hardware controller.
In park position the switches close a circuit so that there's a physical check on the mount position and not just rely on software controls.  More or less the same as the laser trigger you're thinking of.

Rain / bad weather. You need to connect your rain gauge or meteo station to Ekos through an INDI driver and set safety conditions.
Then Ekos itself manages shutdown (park mount, park dome etc) if weather is not safe.

To connect your device to Ekos you can think of using a standard INDI driver or write your own.
If your rain gauge can output a text file via LAN or Serial port to your Ekos PC, as a first approach I suggest Weather Watcher driver that just need such a text file with proper information.



After a bit more work I got past that part and it now seems to work.
A few other questions: I am using this to close my roll off shed using a garage door opener. Mechanically it all looks good.
I will probably not use the scheduler to open the roof. Too much can go wrong with dire consequences, for example trying to open with the roof latches locked.
The OBS is in my back garden so my main use, particularly in the summer, will be to set the scheduler going and get indi to image and shutdown while I sleep.
THe main disaster I can foresee is the roof shutting without the scope being parked. Park scope is a tick box on the scheduler which I could forget. Is there a way in the my roof park script to check the scope is indeed parked?
I will probably try and also implement a physical check using a laser trigger and a last resort "collision" switch on the roof. But it would be good to be able to check the indi status.
The other possible disaster is rain. I have a rain gauge, what do you think is the best approach to connect this to trigger shutdown?


If you have been cheated, Learn how to contact cash app support

Please contact our cash app support team to report fraudulent activity on your...
Show more

Cash app customer service number: Instant solution tips

In this way, clients need to comprehend the strategies that may empower them to interface...
Show more

Thanks, this looks really promising. I have read the threads you suggested.  I have copied the full set of scripts to /usr/share/indi/scripts/   ran sudo chmod +x *.*To test I left all the scripts at their default "Empty" values except park, where I added the lines: 
print "Shutting   Roof ..."
Just to see if it runs.
I then created a simple Indi Ekos profile with the dome scripting gateway. When I ran it, the control panel shows the full set of scripts but the gateway would not connect with the error "2021-04-15T09:28:37: [WARNING] Failed to connect "
I looked at your script for which contains a USB connect routine, but I assume I can leave it empty, or does it need something to connect to?
I switched on the log files, but the directory is empty.

Getting there, grateful for the help.



Thanks man!
Yesterday I followed Celestron instructions to the letter:

  1. Pointed the wedge towards the North with a compass
  2. Performed an EQ North alignment (I used the two stars method)
  3. Done a polar alignment adjusting the wedge instead of using the directional control
  4. Re-done the EQ North alignment
At that point, I noticed that my StellarMate was acting out after an update - couldn't connect either with VNC or SSH. So I missed my chance to check how good my polar alignment was based on your instructions... 
I had spent 2 hours doing all alignments so I decided to take some pics anyway with the DSLR camera (this time with the light pollution filter). I pointed the scope at M81 - without any indication on the accuracy beside what Sky Guide on my phone was showing. :P

30 seconds at ISO400:

30 seconds at ISO1600:

I was very much out of focus, but I didn't notice on the spot. Looking at the glass half full, at least I have learnt how to do a polar alignment (hopefully it will become faster as I go), and I have taken a mental note to check that all the equipment is working after any update.
Now I also know that the laptop's battery won't last long enough if StellarMate doesn't work.




in the option of calibration , there is an option to reuse a guidiing calibration and an option to DEC swap when the subject is on the other side of the pier than the calibration set.

I ve check these tow option and uncheck the option to get a full calibration on each mount slew 
but i ve got problem with that. 
last night i make a guiding calibration on a subject on the west side , the set was very good as the object was near meridian/equator. Guiding was good
my next object was on east side and at the start the guiding was awfull.  The DEC was not automaticly swapped . I check the DEC SWAP checkbox , and the guiding is now good.

i check the pier side report by the mount (EQM35pro, eqmod) and it was good.

Did i miss something in order to be able to reuse calibration ? 
i can redo a calibration each slew but as my mount got hugh DEC backlash, sometime i got calib failure if i m not near equator/meridian.

also , if i do only a RA calibration , how dec guiding will be ? with standard dec guiding speed ? 

thanks for your help :)



Another issue I had with GHY294M was with USB. The QHY camera seems to need more power via USB3 than the equivalent ZWO, so when I simply swapped my ASI294MC pro for QHY294M it didn't work at all, so I am now running all my USB stuff through a good (12V,3A powered) USB hub (Anker 10 Port 60W Data Hub with 7 USB 3.0 Ports and 3 PowerIQ). Cheap hubs "powered" by usb power may not work. This arrangement works 100%. Hope that helps.