×

INDI Library v1.9.1 Released (26 Jun 2021)

Bi-monthly INDI Library v1.9.1 is released bringing a few new drivers and improvements to existing drivers.

Re:An alignment issue in KStars via INDI

  • Posts: 576
  • Thank you received: 55
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
Max S.

RPI 4 B (4Gb) with SMate
Nikon D5500 H-a modified. Nikon D5500 stock
AT72EDII, TPO RC6
ASI2600MC Pro
ZWO ASI120MM Mini on ZWO 30F4
ZWO ASI224MC-S on Orion 50 mm f/3.2
ZWO EAF x 2
SW AZ-GTi
SW HEQ5
RST-135
The following user(s) said Thank You: Vladimir
2 years 7 months ago #32369

Please Log in or Create an account to join the conversation.

  • Posts: 13
  • Thank you received: 1
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.

Спасибо, обязательно ;)
HEQ5 Pro
ZWO ASI 1600MC-cool
Remote telescope on Ubuntu 16 by indiserver
Kstars
The following user(s) said Thank You: maxthebuilder
Last edit: 2 years 7 months ago by Vladimir.
2 years 7 months ago #32371
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 576
  • Thank you received: 55
Looks like your park position is not right..
Max S.

RPI 4 B (4Gb) with SMate
Nikon D5500 H-a modified. Nikon D5500 stock
AT72EDII, TPO RC6
ASI2600MC Pro
ZWO ASI120MM Mini on ZWO 30F4
ZWO ASI224MC-S on Orion 50 mm f/3.2
ZWO EAF x 2
SW AZ-GTi
SW HEQ5
RST-135
The following user(s) said Thank You: Vladimir
2 years 7 months ago #32372

Please Log in or Create an account to join the conversation.

  • Posts: 498
  • Thank you received: 101
Double check your time and location
12" pier with HDX110 using EQMod
ASI 1600 mono/color mains with ASI290MM in off-axis
ASI filter wheel
Moonlite focusers for the sharpening
AT115EDT w/.8x for the light
Fedora Linux, 100% INDI
The following user(s) said Thank You: Vladimir
2 years 7 months ago #32377

Please Log in or Create an account to join the conversation.

  • Posts: 1039
  • Thank you received: 130
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... :)
Stellarmate OS on Raspberry pi4b
Skywatcher EQ8 pro, on steel pier
Takahashi FSQ85, FS60cb & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar x2 Guide Camera
Pegasus Ultimate Hub V2 for all USB & Power
Pegasus focus motors on all scopes
The following user(s) said Thank You: Vladimir
2 years 7 months ago #32383

Please Log in or Create an account to join the conversation.

  • Posts: 1008
  • Thank you received: 297
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.
HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access
The following user(s) said Thank You: Vladimir
Last edit: 2 years 7 months ago by Eric.
2 years 7 months ago #32389

Please Log in or Create an account to join the conversation.

  • Posts: 407
  • Thank you received: 74
"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 :-(
RPI3 Ubuntu 16.04 / AMD desktop Kstars under Ubuntu 16.04 Mounts :azeq6 ,SWAZGoTo

RPI3 Fedora testing out on AMD desktop Fedpra 28 - running kstars 2.9.4 , Indilib 1.7.4 ?????
The following user(s) said Thank You: Vladimir
2 years 7 months ago #32392

Please Log in or Create an account to join the conversation.

  • Posts: 1008
  • Thank you received: 297
Power! Good point! I solved two such issues myself in the past: one was that the dew heaters were on the same 12V as the mount, and the other was that a CPL plug was connected on the local mains loop. Both were causing damaging noise onto the serial port communications...

-Eric
HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access
The following user(s) said Thank You: Vladimir
2 years 7 months ago #32394

Please Log in or Create an account to join the conversation.

  • Posts: 13
  • Thank you received: 1
Ok, I see, so I need to:
1. Set more precise time and a scope location
2. Correct the park position of the mount manually to match the default park position in Kstars

I thought that Kstars doesn't have default park point. I mean looks like there is some kind of a stepper position, which translated in Kstars as "position towards NCP".
But I expected that the first sync on NPC would overwrite this point. So I make the park position a stepper position when RA and DE Steps are both set to 10000000, so I can easily reset park position at this point, knowing, that this position is pointing to NCP. Looks like I was wrong.
But I still can't understand, can't I really manually set this default park position? It's just a wrong model of my mount in Kstars/INDI. Is it possible to set that "this" stepper position positioned towards NCP? Is there a model of my mount that by default identify (when no alignment has been made at all) that some stepper position of the mount is pointing to the specific place in the sky?
HEQ5 Pro
ZWO ASI 1600MC-cool
Remote telescope on Ubuntu 16 by indiserver
Kstars
Last edit: 2 years 7 months ago by Vladimir.
2 years 7 months ago #32402

Please Log in or Create an account to join the conversation.

  • Posts: 13
  • Thank you received: 1
Not sure that power can create a problem, but I will double check this as well.
HEQ5 Pro
ZWO ASI 1600MC-cool
Remote telescope on Ubuntu 16 by indiserver
Kstars
2 years 7 months ago #32404

Please Log in or Create an account to join the conversation.

  • Posts: 1008
  • Thank you received: 297
I see you have the same mount as I have. If you're interested in the driver-level details of parking/home values in eqmod, I can offer this: github.com/indilib/indi/issues/717. But there have been quite a few interesting posts recently on the subject in the forum.
On the HEQ5, check whether the red power led is blinking while slewing and tracking. If it is, power is probably on the issue list.

-Eric
HEQ5-Pro - Atik 314E - Orion ED80T - DMK21 on Orion 50mm
DIY 3D-printed Moonlite and FWheel RGB/LPR
KStars and indiserver on two Atom 1.6GHz 1GB RAM Linux, VPN remote access
2 years 7 months ago #32406

Please Log in or Create an account to join the conversation.

  • Posts: 6
  • Thank you received: 2
I have a HEQ5 Pro as well and I have had strange alignment/slewing problems lately when I start the session. These are usually fixed by returning the mount to park position and then disconnecting all equipment, stop & start INDI/EKOS again. Usually that does the trick by starting it again from "fresh" park position. I usually start the session with Polemaster polar aligment and I use the mount control to rotate mount and then return it to park position. I'm not sure if that is the reason for the strange slewing problem.

When I did a full restore to my Stellarmate I forgot to change the time zone correctly which caused this method to fail and I was not able to slew the mount to anywhere correctly, so that is one thing to check.
The following user(s) said Thank You: Vladimir
2 years 7 months ago #32428

Please Log in or Create an account to join the conversation.

Time to create page: 0.641 seconds