AZ-GTI in AZ-mode tracking problems

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

AZ-GTI in AZ-mode tracking problems

Mat
Topic Author
Offline
Premium Member

Posts: 80
Thank you received: 11

[solved/workaround] AZ-GTI in AZ-mode tracking problems was created by Mat

Hey Folks,
I love my az-gti(x) in AZ mode and the concept of kstars/ekos in combination with an RPI4 is so cool, but at the moment I'm dealing with some problems.
I installed Katars/Ekos from the astroberry repository and everything connected perfect. Mount via wifi and asi120mini of course via USB. If the tracking works i can even guide with 1.3 to 1.8 RMS what I think is amazing in AZ.
But sometimes i have serious problems with the tracking that I just can't explain. I tried now for a week every button in the options, but no success. Its so frustrating.
If it happens for example, with no tracking the stars drift in the southwest to the right side (normal) - if I start the tracking (via the padlock or with a goto) the stars drift more to the left side. It seems that the speed is just too high and wrong. If I slew to another target, I may have the problem up/down or diagonal direction.

But I can’t understand why:
- if I use the synscan App on IOS tracking works really good, even with one star alignment
- date and time are ok
- 12 volt is ok (tested 2 different sources)
- location is fine (my city is in the database)
- platesolving runs perfect (solves every picture and syncs)
- gotos with inbuildt math are good

things that might need mentioning:
- AZ Mode!
- now newest az-gti firmware 3.40
- track factor in the options doesn’t seem to work (0.5 to 5 no difference in wrong drifting)
- polling makes no difference
- guide calibration fails (i think it simply cant overcome the wrong drift)
- track factor less than 0.4 causes a super crazy mount movement (described from a user on issuehunt )
- sometimesI can’t stop tracking via padlock symbol it just runs in the background (I can see the drift, but padlock is unchecked) so I have to press the abort-motion-button (that works every time).

And there are days/ moments it just works - with exact same setup. So it can be that I m tracking a target fine, changing the target (goto works!) an the new target i get the wrong drift.

my first question to go one step further:

If I have a perfect platesolve from a target and I start tracking, does the alignment have an influence on the chosen trackingrate?

And is there any other way to control tracking speed than track factor option?

Are there updates in the indi_skywatcherAltAzMount (Version 1.7)?

Are there any updates on that issuehunt topic (lots of my problems are described here too)

I would be grateful for any hint, because I'm really frustrated... if it runs, it is so cool!

Regards,
Mat

<strong>EDIT: A solution/workaround was found for the problem of strong drift. can be found in post:</strong>
end of thread

The following user(s) said Thank You: Jasem Mutlaq

Last edit: 6 months 3 weeks ago by Mat.

1 year 2 months ago #90947

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

Jasem Mutlaq
Online
Administrator

Replied by Jasem Mutlaq on topic AZ-GTI in AZ-mode tracking problems

There is a long discussion on INDI Github issues about this very topic. I'm out of any fresh ideas on this subject. We need someone who is experienced with this or even perhaps SkyWatcher (doubt it) to step in and improve the situation.

We were working on Celestron AUX driver and Thomas used a sniffer to check the packets sent from the HC to to the mount. I think a similar approach might be useful. Perhaps use Wireshark to check packets exchanged between AZ-GTi and Synscan App? Maybe this will provide some insight on what needs to be done at the driver level.

1 year 2 months ago #90956

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

Mat
Topic Author
Offline
Premium Member

Posts: 80
Thank you received: 11

Replied by Mat on topic AZ-GTI in AZ-mode tracking problems

Thank you for your reply and for supporting this software.

sad to hear - the weird thing is - one day it works for a target and than most of the time it simply tracks to fast / wrong... it's annoying, because AZ-GTI in AZ mode with KSTARS/EKOS is so fast to set up and fun to use.

Perhaps somebody else finds a solution. I will try a few more different routines - perhaps I am lucky and find a way to get it working. My next step is that i ordered a cable (FTDI USB to RJ12/6P6C Serial Cable for Sky Watcher AZ-GTI Mount ) to see if it makes a differnce not to use wifi. otherwise I would give up soon... it took me many clear nights :silly:

Regards
mat

1 year 2 months ago #90959

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

Alan Archer
Offline
Premium Member

Posts: 118
Thank you received: 19

Replied by Alan Archer on topic AZ-GTI in AZ-mode tracking problems

Mat,
I also recently acquired the AZ-GTI mount as a lightweight travel setup and have the same problem. I use a Raspberry Pi 4B with Ubuntu Mate 22.04 64 bit and Kstars / Ekos 3.6.2 installed from the PPA.
I use an ASKAR 135 / ASI 585 as the imaging scope train and a RVO Horizon 32mm / ASI 120 mini as the guide train.
In AZ Mode the tracking is slightly too fast and it seems to struggle to get a decent image with an exposure of more than 15 / 20 seconds.
I've also tried to use it in EQ Mode and the result is similar, the tracking rate in RA is always West of where it should be.
Polar alignment in EQ Mode is done via the Ekos Alignment module and it works fine without issue.
Also in EQ Mode the guide calibration seems to work every time with the internal guider.
I was sure it was my particular mount that was at fault and the RA motor was running too fast or the encoder isn't quite correct.
Sky Watcher do say that it's not suitable for astrophotography, so I just assumed that the tracking rate is only as good as the tolerances on the components used to build it and some units will track better than others.

I do use the FTDI USB cable to control it, I've not tried WiFi yet.

I also noticed the track rate adjustment made little or no discernible difference

Next time I have a clear sky I'll try setting it tracking in Lunar or Solar rate to see if this may help.

Thanks

Alan

1 year 2 months ago #90977

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

Mat
Topic Author
Offline
Premium Member

Posts: 80
Thank you received: 11

Replied by Mat on topic AZ-GTI in AZ-mode tracking problems

Hey Alan,

yesterday I tried to visualize the whole thing. Befor the screenshot i took about 15 platesolves in different areas and the goto was fine.

Here are two screenshots.

After about 10 attempts I got a valid calibration (really crazy looking one). Then I deactivated RA and DEC and started guiding. Now you can see the tracking drift very well in the guide plot (no guide pulses used). The normal direction (without tracking) would be down left in the plot - red arrow shoes what is happening with the tracking. The track factor <1 or >1 even with 5 has absolutly no impact on the tracking. The plot ist excat the same every time.

The second image was taken about 20 seconds after I stopped tracking via the padlock (it is unchecked). You can clearly see that the tracking is still active in the background as the star in the green box is still moving to the down left (what woult be right up in the plot :silly:

).

>>>I do use the FTDI USB cable to control it, I've not tried WiFi yet.

i hoped that coult fix it for me...

but i will try anyway

For me the solution could be a button like "do what you do, just 20% slower" - it's a pity the track factor has absolutly no impact. It coult be the solution. i would love to short trail and error the right speed before imaging!

There must be a solution! I think we just haven't found it yet... :unsure:

Regards,
Mat

1 year 1 month ago #90989

Attachments:

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

Alan Archer
Offline
Premium Member

Posts: 118
Thank you received: 19

Replied by Alan Archer on topic AZ-GTI in AZ-mode tracking problems

Mat,

I've just checked my firmware version and it's the same as yours 3.40. It's currently in the Right Arm setup so I can use it either way AZ or EQ.

The weather is promising to be clear here on Friday night so I may get some testing done with the different track rates. I'll let you know the results if the weather behaves itself.

Thanks

Alan

Last edit: 1 year 1 month ago by Alan Archer. Reason: corrected firmare version

1 year 1 month ago #90999

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

Mat
Topic Author
Offline
Premium Member

Posts: 80
Thank you received: 11

Replied by Mat on topic AZ-GTI in AZ-mode tracking problems

hey
I tried again yesterday. The USB cable connection didn't change anything, but I will continue to use it to avoid connection problems. At the beginning of the evening the tracking went briefly, then it got bad again. Then at 12 p.m. suddenly a short period with good tracking (pulse guiding was active):

I now have a new suspicion: The power supply of both battery packs (12 V 2 A) and the power adapter (12V 1 A) should actually be sufficient (0.75 is required). Nevertheless, it could be that the batteries deliver less voltage when it is cold or perhaps for a exact tracking you need more power, so I will buy and test this evening with a 13.5V 3A power adapter.

I think the screenshot shows that the tracking can work... I will report the results!

Regards

1 year 1 month ago #91018

Attachments:

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

Mat
Topic Author
Offline
Premium Member

Posts: 80
Thank you received: 11

Replied by Mat on topic AZ-GTI in AZ-mode tracking problems

No Luck...

12,2 with 3A
13.7 with 2,4A

No difference in tracking with INDI. Sometimes it works for a short time, than the hard drift starts agin.

1 year 1 month ago #91037

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

Michael
Offline
Junior Member

Posts: 39
Thank you received: 15

Replied by Michael on topic AZ-GTI in AZ-mode tracking problems

Hello, Mat. Your symptoms sound 100% identical to mine. I'm in the same boat as you and have been struggling as well. As someone mentioned earlier, we've had a pretty extensive discussion about it here: github.com/indilib/indi/issues/1646. If you have verbose logging turned on, could you attempt a session and send me your log? I'd be interested in the calculated offsets during each tracking attempt. For privacy reasons, remove your location data from the log header.

Thank you for confirming that it isn't a power supply issue. I performed the same test as well, and we can rule that out.

The following user(s) said Thank You: Jasem Mutlaq

1 year 1 month ago #91069

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

Mat
Topic Author
Offline
Premium Member

Posts: 80
Thank you received: 11

Replied by Mat on topic AZ-GTI in AZ-mode tracking problems

Hey Michael,

glad (and sad) to hear somebody else is struggling.

My Setup is a AZ-GTI(x Version) with newest firmware 3.40 (normal, not right arm). The x-Version is in the inside the same as a normal AZ-GTI, but you can load a bit more and on both sides. My primary scope is a Sharpstar 76 APO with 3 kg.
But can definitely rule out weight problems, because yesterday I built an adapter (finder shoe to normal rail) and operated the mount the whole evening only with the guidescope (Svbony 30/120). The load was a maximum of 400 grams (with cables) yesterday... and I can definitely say that I don't have such an extreme drift with the synscan app (up to date iOS), even with the sharpstar mounted. So I m quite sure it has be a software issue. I also have no problems with the plate solving that others have mentioned, solves every time.

the only thing that which is still a mystery to me, Jasem mentioned on Github not to use inbuilt math. For me it's the only plugin that creates a working goto (and that works great gotos a mostly on point). So i still do not unterstand if alignment has actually an influence on the guide rate? Can i do one platesolve an start guiding? would it be the same as putting 10 platesolve points? (With the app even with a one-star-alignment the drift is relatively good.)

Logfile: Is my location only in the header or do i have to remove other lines?

Last edit: 1 year 1 month ago by Mat.

1 year 1 month ago #91075

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

Mat
Topic Author
Offline
Premium Member

Posts: 80
Thank you received: 11

Replied by Mat on topic AZ-GTI in AZ-mode tracking problems

hey folks,

the sky is cloudy so perhaps we can take a short look at this, perhaps its related to our problem. If there are any private information in the logs please tell me, that i can edit the post.

As i mentioned i have movement in mount even after stopping tracking. Perhaps its that movement, what disrupting our tracking. i tried to log this:

1. i started the mount and EKOS.
2. Change to inbuilt Math.
2. moved the mount to a random point.
4. Give the mount a manual alignment sync (right click) in kstars on the point it thinks it is.

After Syncing I didnt start the tracking - mount doesnt change position:

[2023-03-04T18:51:49.194 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:51:49.216 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:51:49.217 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:51:49.232 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:51:49.233 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:51:49.249 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <45327E> "
[2023-03-04T18:51:49.249 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:51:49.477 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <C8D181> "
[2023-03-04T18:51:49.477 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270405 (Zero 8388608) -> AZ 339.478646° "
[2023-03-04T18:51:49.477 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507848 (Zero 8388608) -> AL 20.701389° "
[2023-03-04T18:51:49.478 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876074 y 0.327923 z 0.353498 "
[2023-03-04T18:51:49.478 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:51:49.478 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876074 0.327923 0.353498"
[2023-03-04T18:51:49.478 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:51:49.479 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874264 0.332748 0.353470"
[2023-03-04T18:51:49.480 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:04 DE 56:33:11 "
[2023-03-04T18:51:50.266 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:51:50.288 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:51:50.288 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:51:50.304 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:51:50.305 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:51:50.321 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <45327E> "
[2023-03-04T18:51:50.321 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:51:50.338 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <C8D181> "
[2023-03-04T18:51:50.338 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270405 (Zero 8388608) -> AZ 339.478646° "
[2023-03-04T18:51:50.338 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507848 (Zero 8388608) -> AL 20.701389° "
[2023-03-04T18:51:50.338 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876074 y 0.327923 z 0.353498 "
[2023-03-04T18:51:50.339 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:51:50.339 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876074 0.327923 0.353498"
[2023-03-04T18:51:50.339 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:51:50.339 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874264 0.332748 0.353470"
[2023-03-04T18:51:50.339 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:05 DE 56:33:11 "
[2023-03-04T18:51:51.338 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:51:51.360 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:51:51.360 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:51:51.376 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:51:51.377 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:51:51.392 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <45327E> "
[2023-03-04T18:51:51.394 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:51:51.409 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <C8D181> "
[2023-03-04T18:51:51.410 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270405 (Zero 8388608) -> AZ 339.478646° "
[2023-03-04T18:51:51.410 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507848 (Zero 8388608) -> AL 20.701389° "
[2023-03-04T18:51:51.411 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876074 y 0.327923 z 0.353498 "
[2023-03-04T18:51:51.411 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:51:51.411 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876074 0.327923 0.353498"
[2023-03-04T18:51:51.412 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:51:51.412 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874264 0.332748 0.353470"
[2023-03-04T18:51:51.413 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:06 DE 56:33:11 "

Than after 30 seconds no movement i started the tracking and you can see, that the mount moves:

[2023-03-04T18:52:02.129 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] IsInMotion "
[2023-03-04T18:52:02.129 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] IsInMotion "
[2023-03-04T18:52:02.129 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876105 y 0.327869 z 0.353471 "
[2023-03-04T18:52:02.130 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking AXIS1 CurrentEncoder 8270405 OldTrackingTarget 0 AXIS2 CurrentEncoder 8507848 OldTrackingTarget 0 "
[2023-03-04T18:52:02.130 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZ 339.482391° (1955418 microsteps) AL 20.699783° (119230 microsteps)  "
[2023-03-04T18:52:02.131 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZOffset -10 microsteps ALOffset 2073621 microsteps. "
[2023-03-04T18:52:02.132 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I130A00B> "
[2023-03-04T18:52:02.147 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 restart. "
[2023-03-04T18:52:02.149 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <G110> "
[2023-03-04T18:52:02.158 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <J1> "
[2023-03-04T18:52:02.176 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 offset 21 microsteps rate 761904 direction 0 "
[2023-03-04T18:52:02.176 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I2006A18> "
[2023-03-04T18:52:02.193 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS2 restart. "
[2023-03-04T18:52:02.193 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <G211> "
[2023-03-04T18:52:02.206 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <J2> "
[2023-03-04T18:52:02.222 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS2 offset -10 microsteps rate 1600000 direction 1 "
[2023-03-04T18:52:02.223 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 error -8270405 AXIS2 error -8507848. "
[2023-03-04T18:52:02.980 CET DEBG ][     org.kde.kstars.ekos.mount] - Mount status changed from  "Idle"  to  "Tracking"
[2023-03-04T18:52:03.127 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:52:03.150 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <111> "
[2023-03-04T18:52:03.150 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:52:03.166 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <311> "
[2023-03-04T18:52:03.166 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:52:03.183 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <5C327E> "
[2023-03-04T18:52:03.183 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:52:03.199 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <BDD181> "
[2023-03-04T18:52:03.200 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270428 (Zero 8388608) -> AZ 339.482639° "
[2023-03-04T18:52:03.201 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507837 (Zero 8388608) -> AL 20.699479° "
[2023-03-04T18:52:03.202 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876108 y 0.327866 z 0.353466 "
[2023-03-04T18:52:03.203 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:52:03.203 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876108 0.327866 0.353466"
[2023-03-04T18:52:03.204 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:52:03.204 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874298 0.332691 0.353439"
[2023-03-04T18:52:03.205 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:16 DE 56:33:10 "
[2023-03-04T18:52:03.205 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876125 y 0.327835 z 0.353455 "
[2023-03-04T18:52:03.206 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking AXIS1 CurrentEncoder 8270428 OldTrackingTarget 8270426 AXIS2 CurrentEncoder 8507837 OldTrackingTarget 8507838 "
[2023-03-04T18:52:03.206 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZ 339.484790° (1955432 microsteps) AL 20.698755° (119224 microsteps)  "
[2023-03-04T18:52:03.207 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZOffset -5 microsteps ALOffset 2073612 microsteps. "
[2023-03-04T18:52:03.207 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I1555814> "
[2023-03-04T18:52:03.219 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 offset 12 microsteps rate 1333333 direction 0 "
[2023-03-04T18:52:03.219 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I200D430> "
[2023-03-04T18:52:03.231 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS2 offset -5 microsteps rate 3200000 direction 1 "
[2023-03-04T18:52:03.232 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 error -2 AXIS2 error 1. "
[2023-03-04T18:52:04.020 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-03-04T18:52:04.200 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:52:04.223 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <111> "
[2023-03-04T18:52:04.224 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:52:04.239 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <311> "
[2023-03-04T18:52:04.240 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:52:04.256 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <6A327E> "
[2023-03-04T18:52:04.257 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:52:04.275 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <B6D181> "
[2023-03-04T18:52:04.280 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270442 (Zero 8388608) -> AZ 339.485069° "
[2023-03-04T18:52:04.281 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507830 (Zero 8388608) -> AL 20.698264° "
[2023-03-04T18:52:04.281 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876129 y 0.327831 z 0.353446 "
[2023-03-04T18:52:04.282 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:52:04.283 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876129 0.327831 0.353446"
[2023-03-04T18:52:04.283 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:52:04.284 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874319 0.332657 0.353419"
[2023-03-04T18:52:04.284 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:16 DE 56:33:10 "
[2023-03-04T18:52:04.286 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876144 y 0.327800 z 0.353438 "
[2023-03-04T18:52:04.287 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking AXIS1 CurrentEncoder 8270442 OldTrackingTarget 8270440 AXIS2 CurrentEncoder 8507830 OldTrackingTarget 8507832 "
[2023-03-04T18:52:04.288 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZ 339.487191° (1955446 microsteps) AL 20.697726° (119218 microsteps)  "
[2023-03-04T18:52:04.289 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZOffset -4 microsteps ALOffset 2073612 microsteps. "
[2023-03-04T18:52:04.289 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I1555814> "
[2023-03-04T18:52:04.290 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 offset 12 microsteps rate 1333333 direction 0 "
[2023-03-04T18:52:04.290 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I200093D> "
[2023-03-04T18:52:04.312 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS2 offset -4 microsteps rate 4000000 direction 1 "
[2023-03-04T18:52:04.313 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 error -2 AXIS2 error 2. "
[2023-03-04T18:52:04.992 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-03-04T18:52:05.272 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:52:05.294 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <111> "
[2023-03-04T18:52:05.294 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:52:05.310 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <311> "
[2023-03-04T18:52:05.311 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:52:05.326 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <78327E> "
[2023-03-04T18:52:05.326 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:52:05.342 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <B1D181> "
[2023-03-04T18:52:05.343 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270456 (Zero 8388608) -> AZ 339.487500° "
[2023-03-04T18:52:05.343 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507825 (Zero 8388608) -> AL 20.697396° "
[2023-03-04T18:52:05.344 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876148 y 0.327796 z 0.353432 "
[2023-03-04T18:52:05.344 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:52:05.345 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876148 0.327796 0.353432"
[2023-03-04T18:52:05.346 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:52:05.346 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874339 0.332622 0.353405"
[2023-03-04T18:52:05.347 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:16 DE 56:33:10 "
[2023-03-04T18:52:05.348 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876164 y 0.327766 z 0.353421 "
[2023-03-04T18:52:05.349 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking AXIS1 CurrentEncoder 8270456 OldTrackingTarget 8270454 AXIS2 CurrentEncoder 8507825 OldTrackingTarget 8507826 "
[2023-03-04T18:52:05.349 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZ 339.489587° (1955460 microsteps) AL 20.696699° (119212 microsteps)  "
[2023-03-04T18:52:05.350 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] New Tracking Target AZOffset -5 microsteps ALOffset 2073612 microsteps. "
[2023-03-04T18:52:05.350 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I1555814> "
[2023-03-04T18:52:05.363 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 offset 12 microsteps rate 1333333 direction 0 "
[2023-03-04T18:52:05.364 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <I200D430> "
[2023-03-04T18:52:05.374 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS2 offset -5 microsteps rate 3200000 direction 1 "
[2023-03-04T18:52:05.374 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] Tracking -> AXIS1 error -2 AXIS2 error 1. "
[2023-03-04T18:52:05.994 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.

Here i stopped the tracking, but as you can see, it still moves on (padlock is unchecked):

[2023-03-04T18:52:30.996 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:52:31.017 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <111> "
[2023-03-04T18:52:31.018 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:52:31.033 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <311> "
[2023-03-04T18:52:31.034 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:52:31.049 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <C0337E> "
[2023-03-04T18:52:31.050 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:52:31.066 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <22D181> "
[2023-03-04T18:52:31.067 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270784 (Zero 8388608) -> AZ 339.544444° "
[2023-03-04T18:52:31.068 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507682 (Zero 8388608) -> AL 20.672569° "
[2023-03-04T18:52:31.069 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876617 y 0.326979 z 0.353027 "
[2023-03-04T18:52:31.069 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:52:31.070 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876617 0.326979 0.353027"
[2023-03-04T18:52:31.070 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:52:31.071 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874812 0.331807 0.352999"
[2023-03-04T18:52:31.072 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:16 DE 56:33:09 "
[2023-03-04T18:52:31.981 CET DEBG ][     org.kde.kstars.ekos.mount] - Mount status changed from  "Tracking"  to  "Idle"
[2023-03-04T18:52:32.024 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-03-04T18:52:32.066 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:52:32.091 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <111> "
[2023-03-04T18:52:32.093 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:52:32.106 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <311> "
[2023-03-04T18:52:32.107 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:52:32.121 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <CE337E> "
[2023-03-04T18:52:32.122 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:52:32.138 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <1BD181> "
[2023-03-04T18:52:32.140 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270798 (Zero 8388608) -> AZ 339.546875° "
[2023-03-04T18:52:32.141 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507675 (Zero 8388608) -> AL 20.671354° "
[2023-03-04T18:52:32.142 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876638 y 0.326944 z 0.353007 "
[2023-03-04T18:52:32.142 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:52:32.143 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876638 0.326944 0.353007"
[2023-03-04T18:52:32.144 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:52:32.144 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874833 0.331772 0.352979"
[2023-03-04T18:52:32.145 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:16 DE 56:33:08 "
[2023-03-04T18:52:33.001 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-03-04T18:52:33.979 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:52:33.979 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <111> "
[2023-03-04T18:52:33.979 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:52:33.980 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <311> "
[2023-03-04T18:52:33.980 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:52:33.980 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <D8337E> "
[2023-03-04T18:52:33.980 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:52:33.981 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <15D181> "
[2023-03-04T18:52:33.982 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8270808 (Zero 8388608) -> AZ 339.548611° "
[2023-03-04T18:52:33.982 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507669 (Zero 8388608) -> AL 20.670313° "
[2023-03-04T18:52:33.982 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.876654 y 0.326920 z 0.352990 "
[2023-03-04T18:52:33.983 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:52:33.983 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.876654 0.326920 0.352990"
[2023-03-04T18:52:33.983 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:52:33.984 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.874849 0.331748 0.352962"
[2023-03-04T18:52:33.984 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:16 DE 56:33:07 "

if i press ABORT MOTION 30 sec later, it really stops moving:

[2023-03-04T18:53:02.858 CET DEBG ][           org.kde.kstars.indi] - ISD:Telescope: Aborted. 
 
[2023-03-04T18:53:02.859 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <K1> "
[2023-03-04T18:53:02.868 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <K2> "
[2023-03-04T18:53:02.992 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-03-04T18:53:03.148 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:53:03.171 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:53:03.172 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:53:03.188 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:53:03.188 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:53:03.204 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <1F357E> "
[2023-03-04T18:53:03.204 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:53:03.220 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <63D081> "
[2023-03-04T18:53:03.222 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8271135 (Zero 8388608) -> AZ 339.605382° "
[2023-03-04T18:53:03.222 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507491 (Zero 8388608) -> AL 20.639410° "
[2023-03-04T18:53:03.223 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.877155 y 0.326117 z 0.352485 "
[2023-03-04T18:53:03.224 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:53:03.225 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.877155 0.326117 0.352485"
[2023-03-04T18:53:03.225 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:53:03.226 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.875355 0.330948 0.352458"
[2023-03-04T18:53:03.226 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:20 DE 56:32:45 "
[2023-03-04T18:53:04.007 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.
[2023-03-04T18:53:04.221 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f1> "
[2023-03-04T18:53:04.244 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:53:04.244 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <f2> "
[2023-03-04T18:53:04.260 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <101> "
[2023-03-04T18:53:04.260 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j1> "
[2023-03-04T18:53:04.276 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <1F357E> "
[2023-03-04T18:53:04.277 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] CMD <j2> "
[2023-03-04T18:53:04.294 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[SCOPE] RES <63D081> "
[2023-03-04T18:53:04.295 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis1 encoder 8271135 (Zero 8388608) -> AZ 339.605382° "
[2023-03-04T18:53:04.296 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Axis2 encoder 8507491 (Zero 8388608) -> AL 20.639410° "
[2023-03-04T18:53:04.297 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] TDV x 0.877155 y 0.326117 z 0.352485 "
[2023-03-04T18:53:04.298 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ApparentVector"
[2023-03-04T18:53:04.299 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.877155 0.326117 0.352485"
[2023-03-04T18:53:04.302 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] Vector dump - ActualVector"
[2023-03-04T18:53:04.303 CET DEBG ][           org.kde.kstars.indi] - AlignmentSubSystem: "[ALIGNMENT] 0.875355 0.330948 0.352458"
[2023-03-04T18:53:04.304 CET DEBG ][           org.kde.kstars.indi] - AZ-GTi Alt-Az WiFi : "[ALIGNMENT] Sky RA 19:49:21 DE 56:32:45 "
[2023-03-04T18:53:04.990 CET WARN ][                       default] - qrc:/qml/mount/mountbox.qml:502:17: QML MouseArea: Detected anchors on an item that is managed by a layout. This is undefined behavior; use Layout.alignment instead.

So here my question for @jasem:

Can this, lets call it "ghost movement" :silly:

, be the cause for all the wrong tracking? Is it perhaps active "in the background" and is making things worse?

And @michael and @alan:
Can you confirm this behavior?

Regards,
Mat

1 year 1 month ago #91080

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

Jasem Mutlaq
Online
Administrator

Replied by Jasem Mutlaq on topic AZ-GTI in AZ-mode tracking problems

Thank you for the logs Mat. So this was indeed an issue when toggling off the tracking, but it shouldn't affect tracking itself. During tracking, the azimuth and altitude offsets are calculated and the speed rates are set accordingly.

1 year 1 month ago #91082

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

Time to create page: 1.262 seconds