Hello everyone,

I work in KStars via INDIserver (both latest version). Currently, I'm having the following problem:

After switching on, in order to calibrate the mount I use the Align tab in Ekos. My actions are:
1. I launch Ekos, connect to the INDI-server
2. In the INDI Control Panel window in the EQMOD section on the Aligment, Sync and Align tabs, I delete all points and coordinates. Click on
Aligment => "Delete all the entries in the set" -> "Ok",
Sync => "Clear Sync Delta"
Align => "Clear List"
3. After that, I do Plate Solving (position recognition) of the current position once (near the pole)
4. I send EQMod to some bright star (Track command).
5. In Ekos, on the Align tab, select "Slew to target" and click "Capture & Solve". The error is quite high but falls with each iteration, and after several iterations, the star is in the center. During this time, several synchronization points are stored in EQMod.
6. I do steps 4 and 5 again for another star.
7. In theory, there's enough for calibration, but when you hover over the 3rd star, the error remains very high.
8. No matter how many times I do over steps 4, 5, 6. When aiming at another star, the mount keeps missing (even the frame does not fit).

Also, there's some strangeness in how Kstars shows where the mount is pointed to. I hardly move the mount, but it jumps over the half of the sky. More clearly you can see it on this video (in addition recorded all settings):
monosnap.com/file/YA5sktm9gEzYXkjehJvhnuyz7PBiww

I'd be glad to have any help in solving this problem.

P.S.: HEQ5 Pro, Skywatcher 100id, NexDome.

Bypass step 3. This step will result in nothing but problems. Sync to a star at least 15 degrees from the celestial pole. So just bypass step 3.

-Eric

Yes, I would second not plate solving too near the pole, it can cause issues. Also I would recommend not doing "Slew to Target," but just sync in your various plate solves building your model. This will avoid getting numerous erroneous points too close to one another. I would recommend choosing several target areas in the sky that are separated far apart (particularly in RA), plate solving in each location, and then after you do a few, you should have a good model. Don't worry so much about getting it to center the targets at first, each plate solve will tell the mount exactly where it is, no matter where it is pointing. As your model gets better with each additional point, soon enough your slews will center on the targets you select.

Thanks,

Rob

Also, you maybe not properly polar-aligned.
Polar alignment cannot be done remotely - you actually need to manually move the mount's mechanical controls.

Thank you all for your advice. I will for sure try everything, but when the sky is clear. Unfortunately, at this time of the year, it's really rare.

But what can you tell about videos, and how my point "jumps" in Kstars, after I move a mount a little bit? Is it normal?
Also, about polar alignment. Look at the video. If I clear all sync data, I don't know for what reason, but Kstars show the mount pointing far away from the celestial pole. And my first sync - I just return it to the actual place. And it's more than 10 degrees error.

Just think about it. If your mount (not the telescope) is not positioned right - you'll have a big problem. The mount needs to be polar aligned. Its head needs to be pointing exactly at the North Celestial Pole (NCP). If it's off by several degrees you'll have a big problem. If you point your telescope at NCP and plate solve - it's not polar alignment.
There's a procedure in Ekos to perform the polar alignment. There you use not the electronic mount controls but mechanical/manual screws to move the mount left/right and up/down.
Так победимъ.
Max

Yes, I know it. My mount is properly aligned and in park position pointing exactly at the NCP. So the problem is only in Kstars or INDI. Why, if I drop all alignment points, and my mount is in the park position (pointing NCP), Kstars shows that my mount is pointing far away from NCP. Look at the attached picture:


If I make plate solve, it updates to NCP.

Спасибо, обязательно

Looks like your park position is not right..

Double check your time and location

You need to set your park position correctly,
With your mount in the home position, scope up weights down, and everything turned on, right on Polaris on the skymap and go to EQMOD mount and then sync, oncle the crosshairs shows on Polaris then click set as park..job done...
If the mount does move, just undo clutches and manually move back to home position..
Next time you start up it will show crosshairs on Polaris, this is also why your goto’s are all off too...

Agreed, getting the park position right is important. More important than polar alignment actually. A bad polar alignment can be overcome with alignment, and can be introduced voluntarily to solve declination backlash issues when guiding.

-Eric

EDIT: time and location are equally important, especially as I read your scope is remote.

"Also, there's some strangeness in how Kstars shows where the mount is pointed to. I hardly move the mount, but it jumps over the half of the sky. More clearly you can see it on this video (in addition recorded all settings):"

Maybe , i suggest, that you have a problem with your local cables - are they catching or even damaged so that the signal is being interfered with.

Or you have a power problem.

Doesn't matter about the NCP,Alignment etc - it should still move relatively smoothly even to the wrong position - IMO

Is everything running locally (Kstars/Ekos/Indi drivers) if not the jumping could be Internet response times - even doing VNC remote to locally run Ksars/Indi set up over bad communications will appear to jump or be erratic but still get to the end point (even if its wrong).

Dont know enough about the Indi Eqmod version but why delete alignment data between sessions, if you are not moving your scope after closedown - I hardly ever did this on my Windows version of Eqmod???

Perhaps you could "park" at a different position , I assume Indi Eqmod allows this as per Windows version, and see if it gives you the same problem - and don't delete the alignment data.

Hope you find a solution.

I know its remote but something's need checking locally