Alternatively, maybe that "let the hand control decide" means you should just leave it up to the skywatcher?

But then Ekos won't know it's time to recenter your target on the west side, you won't be able to decide whether you want to recalibrate your guiding, refocus, etc.

Probably best to get skywatcher to sit tight and let Ekos handle the flip if you can.

Read More...

Hmmm. I've never used a skywatcher mount. Look for something like "meridian limit."

You can do all the testing during the day when you can see what's happening.

Try to slew to different sides of the meridian and see what happens. If you are looking east and you try to slew to a location just west of the meridian, what happens? If you slew to a point *just barely* west of the meridian when you're looking east, does the mount just nudge a few degrees, or does it flip around to come to that point from the west side?

Maybe you don't need to define any kind of meridian limit for your mount? Try just setting Ekos to flip at HA = +1 degree (see screenshot below).

Then (again during daytime is fine for testing) slew to a point just east of the meridian and track. Watch the hour angle in Ekos get closer and closer to zero and then creep into the positive. What happens when you reach the HA = +1 degree?  Ekos should send a slew at that point and the mount should flip.
Hmmm. I've never used a skywatcher mount. Look for something like "meridian limit."

You can do all the testing during the day when you can see what's happening.

Try to slew to different sides of the meridian and see what happens. If you are looking east and you try to slew to a location just west of the meridian, what happens? If you slew to a point *just barely* west of the meridian when you're looking east, does the mount just nudge a few degrees, or does it flip around to come to that point from the west side?

Maybe you don't need to define any kind of meridian limit for your mount? Try just setting Ekos to flip at HA = +1 degree (see screenshot below).

Then (again during daytime is fine for testing) slew to a point just east of the meridian and track. Watch the hour angle in Ekos get closer and closer to zero and then creep into the positive. What happens when you reach the HA = +1 degree?  Ekos should send a slew at that point and the mount should flip.

  


 

Read More...

3.5.3 stable connects to all my devices now, but I have an endlessly repeating series of error messages from the lx200_10micron mount driver:

Log snippet:
[2021-05-02T08:15:03.949 MDT DEBG ][ org.kde.kstars.indi] - LX200 10micron : "[SCOPE] CMD <#:GS#> "
[2021-05-02T08:15:04.023 MDT DEBG ][ org.kde.kstars.indi] - LX200 10micron : "[SCOPE] RES <21:57:22.00> "
[2021-05-02T08:15:05.046 MDT DEBG ][ org.kde.kstars.indi] - LX200 10micron : "[SCOPE] CMD <#:GS#> "
[2021-05-02T08:15:05.119 MDT DEBG ][ org.kde.kstars.indi] - LX200 10micron : "[SCOPE] RES <21:57:23.10> "
[2021-05-02T08:15:06.206 MDT DEBG ][ org.kde.kstars.indi] - LX200 10micron : "[SCOPE] CMD <#:GS#> "
[2021-05-02T08:15:06.303 MDT DEBG ][ org.kde.kstars.indi] - LX200 10micron : "[SCOPE] RES <21:57:24.28> "

I'm going to start a new thread because this seems specific to the lx200_10micron and not just the bad PPA.

Read More...

It's confusing because some of this logic is in the mount firmware, and some is in Ekos. This means the specifics are different for different mounts.

At least for my mounts (iOptron, 10Micron), it's not "side of pier" but rather "hour angle" that triggers the flip. There are two interacting pieces of info:

1) The mount firmware (not Ekos) normally slews to locations from the west side or the east side (of course!) depending on where in the sky its target coordinates currently are (azimuth). There is a "gray zone" very close to the meridian which ca be set in the hand controller to allow a slew-from-the-west to a point just before the meridian. I usually set this gray zone to be very small -- for me, 1 degree. If Ekos triggers a slew to any point west of that gray zone, the mount will approach it from the west.

2) In Ekos there's a setting to perform a meridian flip at some hour angle past the meridian. This must be set AFTER the "gray zone" set in the hand control. In y case I set this for 1.5 degrees past the meridian.

The usual series of events is
a) Mount tracks past the hand control gray zone (hour angle = +1 degree) while exposing an image
b) Mount tracks past Ekos "Meridian Flip" limit (hour angle = +1.5 degrees) while STILL exposing image, sends message "Meridian Flip Waiting"
c) Ekos completes current image and downloads from camera
d) Ekos sends command to slew mount to current target RA/DEC
e) Mount flips in order to approach target from the west because it's west of the "gray zone"
f) Ekos does an "alignment" step using plate solving to re-center target
g) Ekos begins exposing next image in sequence

The critical thing for me is to set the gray zone in the and paddle to be smaller than the meridian flip angle in Ekos.

Read More...

When the drivers are updated, will the fix appear in the "stable" PPA, or only in the nightlies?

Read More...

Here's a link that explains how to go back and forth from the nightlies (beta) and the stable version:
indilib.org/download.html

Start by uninstalling the nightly version
sudo apt-get install ppa-purge
sudo ppa-purge ppa:mutlaqja/indinightly

Then you may or may not need to reinstall the stable version:
sudo apt-add-repository ppa:mutlaqja/indinightly
sudo apt-get update
sudo apt-get install indi-full kstars-bleeding gsc

Good luck!
Scott

Read More...

Not sure anybody needs to hear this, but I updated both my intel NUC and a Pi4 to INDI 1.9.0 and KStars 3.5.3 Stable this morning and all my equipment connects and operates just fine. 

Read More...

Hi Ron,

Please post a screenshot of your Profile Editor screen in Ekos (on the client machine). In Kstars, you start Ekos, then click the tiny little "Edit Profile" button near the top (it looks like pencil).

Here's an example of what it should look like. Do you have all your devices set up properly in there?

Do you have the remote server set?  Please post a screenshot of it and let me know.

Scott
Hi Ron,

Please post a screenshot of your Profile Editor screen in Ekos (on the client machine). In Kstars, you start Ekos, then click the tiny little "Edit Profile" button near the top (it looks like pencil).

Here's an example of what it should look like. Do you have all your devices set up properly in there?

Do you have the remote server set?  Please post a screenshot of it and let me know.

Scott
  



Read More...

My itty-bitty-indi-pi is currently on 192.168.1.222
Its web server runs on http://192.168.1.222:8624
And it controls devices via port 7624

Here's a screenshot from my MacBook running Safari
My itty-bitty-indi-pi is currently on 192.168.1.222
Its web server runs on http://192.168.1.222:8624
And it controls devices via port 7624

Here's a screenshot from my MacBook running Safari
  



Read More...

On my indi-pi server, I have a file
/etc/systemd/system/indiwebmanager.service

And in that file I have
[Unit]
Description=INDI Web Manager
After=multi-user.target

[Service]
Type=idle
# MUST SET YOUR USERNAME HERE.
User=denning
ExecStart=/usr/local/bin/indi-web -v
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

I can't remember if I had to create that file or if it was created by the web server when I checked "Auto Start"

Read More...

Try this:

On your Rpi4-1, type "ip a" to find out its IP address.
For now I will assume it's 10.42.0.2
Then type "/usr/local/bin/indi-web -v"

This will start the indi web server

Then on your Rpi4-8 (or a laptop, or whatever), open a web browser
In the URL bar, type 10.42.0.2:8364

The indi server web interface will come up in your browser
Configure your devices
Before you close the browser window, check the boxes at top left for "Auto Start" and "Auto Connect"

Then try rebooting Rpi4-1 without a monitor attached.

Again, try using the web server on Rpi4-1 in a browser on your laptop. Should pop right up.

Finally, go into Ekos on Rpi4-8 and configure your device profile to use the remote server

Read More...