×

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

Bi-monthly release with minor bug fixes and improvements

Read More...

Problems with AZ-GTI mount and PHD2

  • Posts: 10
  • Thank you received: 0

Replied by Carlos Martínez on topic Problems with AZ-GTI mount and PHD2

Hi.

Sorry but the AZ-GTI doesn't have ST4 port. I only can use EQMod driver or specific AZ-GTI, but this driver doesn't support serial connection.

I think de mount is OK, because in Windows using ASCOM there is no problem.

Can I test something more?

Thank you.
3 years 7 months ago #60546

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

  • Posts: 10
  • Thank you received: 0

Replied by Carlos Martínez on topic Problems with AZ-GTI mount and PHD2

Sorry, I haven't said that I have tested it using WIFI, connecting directly astroberry to the mount Hotspot and connecting the mount to atroberry Hotspot too.

Thanks.
3 years 7 months ago #60547

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

  • Posts: 2257
  • Thank you received: 223

Replied by Gonzothegreat on topic Problems with AZ-GTI mount and PHD2

I do not know which firmware version you are running, but take a look at this thread www.cloudynights.com/topic/586532-new-sk...fi-mount/?p=10441991
3 years 7 months ago #60548

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

  • Posts: 10
  • Thank you received: 0

Replied by Carlos Martínez on topic Problems with AZ-GTI mount and PHD2

OK, I'll read this thread.

The firmware is a recent one, because I bought the mount on august.

But I think that the problem is not that, because using the same configuration, only changing to windows, the guiding is perfect. The problem only occurs using Linux (INDI + PHD2), using Windows (ASCOM + PHD2), everything is OK.

Thanks again.
3 years 7 months ago #60550

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

  • Posts: 226
  • Thank you received: 88

Replied by Jean-Luc on topic Problems with AZ-GTI mount and PHD2

HI,
I checked the guiding pulse in the INDI logs: the DEC axis has 2073600 steps, which is roughly 24 steps per second for sidereal rate, and the 1.250 North guiding pulse at 0.5x shows a difference of 13 steps which seems correct. From the driver point of view, it can't do more.
I noticed in your first PHD2 logs some problems while calibrating. In the RA case, East/West moves seems ok (8 west moves, 4 east moves:
01:04:15.864 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:21.199 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:26.560 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:31.903 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:37.187 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:42.493 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:47.788 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:53.049 00.000 3013644336 MoveAxis(W, 1250, -)
01:04:58.320 00.001 3015503888 WEST calibration completes with steps=8 angle=-178.7 rate=2.618 parity=1
01:04:58.344 00.000 3013644336 MoveAxis(E, 2500, -)
01:05:04.945 00.000 3013644336 MoveAxis(E, 2500, -)
01:05:11.547 00.000 3013644336 MoveAxis(E, 2500, -)
01:05:18.100 00.000 3013644336 MoveAxis(E, 2500, -)
For the DEC axis, North/South moves are problematic (22 North, 6 south):
01:05:24.634 00.000 3013644336 MoveAxis(N, 1250, -)
01:05:29.857 00.000 3015503888 Backlash: Rejected small move of 0.7 px
01:05:29.858 00.000 3013644336 MoveAxis(N, 1250, -)
01:05:29.886 00.028 3015503888 Backlash: Limpiando paso de backlash   2, Last Delta = 0.72 px, CumDistance = 0.72 px
01:05:35.109 00.001 3015503888 Backlash: Rejected small move of 0.8 px
01:05:35.109 00.000 3013644336 MoveAxis(N, 1250, -)
01:05:35.136 00.027 3015503888 Backlash: Limpiando paso de backlash   3, Last Delta = 0.83 px, CumDistance = 1.53 px
01:05:40.438 00.001 3015503888 Backlash: Rejected small move of 0.8 px
01:05:40.442 00.000 3013644336 MoveAxis(N, 1250, -)
01:05:40.470 00.028 3015503888 Backlash: Limpiando paso de backlash   4, Last Delta = 0.77 px, CumDistance = 2.08 px
01:05:45.789 00.000 3015503888 Backlash: Rejected small move of 0.6 px
01:05:45.790 00.000 3013644336 MoveAxis(N, 1250, -)
01:05:45.820 00.030 3015503888 Backlash: Limpiando paso de backlash   5, Last Delta = 0.58 px, CumDistance = 2.66 px
01:05:51.144 00.001 3015503888 Backlash: Rejected small move of 0.7 px
01:05:51.144 00.000 3013644336 MoveAxis(N, 1250, -)
01:05:51.169 00.025 3015503888 Backlash: Limpiando paso de backlash   6, Last Delta = 0.74 px, CumDistance = 3.32 px
01:05:56.380 00.001 3015503888 Backlash: Rejected small move of 0.8 px
01:05:56.380 00.000 3013644336 MoveAxis(N, 1250, -)
01:05:56.407 00.027 3015503888 Backlash: Limpiando paso de backlash   7, Last Delta = 0.84 px, CumDistance = 4.08 px
01:06:01.720 00.000 3015503888 Backlash: Rejected small move of 1.4 px
01:06:01.721 00.001 3013644336 MoveAxis(N, 1250, -)
01:06:01.750 00.029 3015503888 Backlash: Limpiando paso de backlash   8, Last Delta = 1.39 px, CumDistance = 5.46 px
01:06:07.013 00.000 3015503888 Backlash: Accepted clearing move of 4.5
01:06:07.014 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:07.040 00.026 3015503888 Backlash: Limpiando paso de backlash   9, Last Delta = 4.49 px, CumDistance = 9.62 px
01:06:12.339 00.001 3015503888 Backlash: Rejected small move of 1.4 px
01:06:12.340 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:12.365 00.025 3015503888 Backlash: Limpiando paso de backlash  10, Last Delta = 1.43 px, CumDistance = 11.05 px
01:06:17.627 00.000 3015503888 Backlash: Accepted clearing move of 2.3
01:06:17.628 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:17.653 00.025 3015503888 Backlash: Limpiando paso de backlash  11, Last Delta = 2.28 px, CumDistance = 13.26 px
01:06:22.931 00.001 3015503888 Backlash: Rejected small move of 1.8 px
01:06:22.931 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:22.959 00.028 3015503888 Backlash: Limpiando paso de backlash  12, Last Delta = 1.81 px, CumDistance = 15.07 px
01:06:28.229 00.000 3015503888 Backlash: Accepted clearing move of 3.0
01:06:28.229 00.000 3015503888 Backlash: Got 3 acceptable moves, using last move as step 1 of N calibration
01:06:28.229 00.000 3015503888 Backlash: North calibration moves starting at {1986.6,1533.0}, Offset = 18.7 px
01:06:28.229 00.000 3015503888 Backlash: Total distance moved = 21.2
01:06:28.229 00.000 3015503888 Backlash: Falling Through to state GO_NORTH
01:06:28.254 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:33.642 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:38.988 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:44.318 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:49.648 00.000 3013644336 MoveAxis(N, 1250, -)
01:06:54.989 00.000 3013644336 MoveAxis(N, 1250, -)
01:07:00.329 00.000 3013644336 MoveAxis(N, 1250, -)
01:07:05.650 00.000 3013644336 MoveAxis(N, 1250, -)
01:07:10.961 00.000 3013644336 MoveAxis(N, 1250, -)
01:07:16.247 00.000 3013644336 MoveAxis(N, 1250, -)
01:07:21.530 00.001 3015503888 NORTH calibration completes with angle=87.4 rate=1.822 parity=-1
01:07:21.563 00.000 3013644336 MoveAxis(S, 2500, -)
01:07:28.130 00.000 3013644336 MoveAxis(S, 2500, -)
01:07:34.708 00.000 3013644336 MoveAxis(S, 2500, -)
01:07:41.267 00.000 3013644336 MoveAxis(S, 2500, -)
01:07:47.803 00.000 3013644336 MoveAxis(S, 2500, -)
01:07:54.360 00.000 3013644336 MoveAxis(S, 1250, -)
01:07:59.615 00.001 3015503888 Omitted calibration alert: Advisory: Calibration successful but little south movement was measured, 
so guiding may be impaired.
Afterwards, there are many North guide pulses before the DEC axis starts to diverge, that does not occur at the first North guide pulse (even if they don't seem to be very effective). I will try to look what happens when the DEC starts diverging.
At first sight, I would think of a weight balance issue, or a loosen axis clutch. Or there may be a bug in the motor controller firmware as suggested by @Gonzothegreat, which the ASCOM driver is aware of ?
Maybe a log from an Ascom/PHD2 session would be helpful here. I'm also thinking to the SideofPier property, which seems to be used by some guiding software to use the correct axis direction.
3 years 7 months ago #60620

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

  • Posts: 10
  • Thank you received: 0

Replied by Carlos Martínez on topic Problems with AZ-GTI mount and PHD2

Hi again.

Thank you very much.

I attach here PHD2 logs of the photo from the first post.

Here is a capture of the Synscan app showing the firmware version. It is 3.22.A5.


I think I can downgrade it to v3.20 to test it, but... I don't have the problem in windows. Is so frustrating :S. It seems like the bug only affects in linux. Ascom driver is from Skywatcher. Perhaps they solved or ignore the bug in their driver, don't you think so?

Thank you again.
3 years 7 months ago #60630
Attachments:

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

  • Posts: 10
  • Thank you received: 0

Replied by Carlos Martínez on topic Problems with AZ-GTI mount and PHD2

It seems that there is a newer firmware version from Skywatcher. v3.26.



It's a shame that no changelog is included :-(.

I'll try it as soon as possible. Perhaps there is the solution.

Bye.
3 years 7 months ago #60631
Attachments:

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

  • Posts: 2257
  • Thank you received: 223

Replied by Gonzothegreat on topic Problems with AZ-GTI mount and PHD2

The 3.26 still has the DEC issue from reading the last update off the CN thread. Downgrade to 3.20 instead and do your testing.
3 years 7 months ago #60636

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

  • Posts: 226
  • Thank you received: 88

Replied by Jean-Luc on topic Problems with AZ-GTI mount and PHD2

Had a more precise look to the logs, and immediately notice an unexplained variation of the DEC axis position as reported by the motor controller firmware. For instance during the calibration:
[2020-09-23T23:25:15.234 CEST DEBG ];EQMod Mount : "[SCOPE] Current encoders RA=8153754 DE=9502321 "
[2020-09-23T23:25:15.885 CEST DEBG ];EQMod Mount : "[DEBUG] Timed guide North 1250 ms at rate 7.52053  "
[2020-09-23T23:25:15.887 CEST DEBG ];EQMod Mount : "[DEBUG] SetDERate() : rate = 0.5 "
[2020-09-23T23:25:15.887 CEST DEBG ];EQMod Mount : "[MOUNT] SetMotion() : Axis = 2 -- dir=forward mode=slew speedmode=lowspeed "
[2020-09-23T23:25:15.900 CEST DEBG ];EQMod Mount : "[MOUNT] SetSpeed() : Axis = 2 -- period=1329692 "
[2020-09-23T23:25:17.181 CEST DEBG ];EQMod Mount : "[DEBUG] End Timed guide North/South "
[2020-09-23T23:25:17.290 CEST DEBG ];EQMod Mount : "[SCOPE] Current encoders RA=8153804 DE=9502334 "
[2020-09-23T23:25:18.478 CEST DEBG ];EQMod Mount : "[SCOPE] Current encoders RA=8153832 DE=9502332 "
[2020-09-23T23:25:19.455 CEST DEBG ];EQMod Mount : "[SCOPE] Current encoders RA=8153856 DE=9502342 "
[2020-09-23T23:25:19.601 CEST DEBG ];EQMod Mount : "[DEBUG] Timed guide North 1250 ms at rate 7.52053  "
[2020-09-23T23:25:19.604 CEST DEBG ];EQMod Mount : "[DEBUG] SetDERate() : rate = 0.5 "
[2020-09-23T23:25:19.605 CEST DEBG ];EQMod Mount : "[MOUNT] SetMotion() : Axis = 2 -- dir=forward mode=slew speedmode=lowspeed "
[2020-09-23T23:25:19.611 CEST DEBG ];EQMod Mount : "[MOUNT] SetSpeed() : Axis = 2 -- period=1329692 "
[2020-09-23T23:25:20.890 CEST DEBG ];EQMod Mount : "[DEBUG] End Timed guide North/South "
[2020-09-23T23:25:21.533 CEST DEBG ];EQMod Mount : "[SCOPE] Current encoders RA=8153907 DE=9502344 "
[2020-09-23T23:25:22.602 CEST DEBG ];EQMod Mount : "[SCOPE] Current encoders RA=8153934 DE=9502343 "
At the end at the first Timed guide pulse, the DEC axis changes by itself: 9502334, 9502332 then 9502342. Starting from 9502321, the first guide pulse is correct leading to 9502334 (~12-14 steps), then it moves by itself, and the second guide pulse is only 2 steps from 9502342 to 9502344. But 9502344 is almost correct starting from the beginning. Unless another application is moving the mount, I have no explanation. I did not go further, if I understood South guiding works correctly as you reported, I don't know why the firmware makes special corrections on the North axis. I don't own a STM32 dev board to debug the firmware and I suppose their ASCOM driver is closed source. Did you try with the ASCOM eqmod driver ?
It seems they did not solve the issue (or consider this is not a normal usage of the mount) (thanks @Gonzothegreat) What do they mean with 'telescope pointing forwards' ?
An explanation of the existence of these 2 motor firmwares (altaz and eq) may be that the handcontroller is altaz only and always send commands to the motor board as if it was in altaz mode. If the mount is on an eq wedge you then have to change the Dec axis speeds in the motor firmware and that may explain this issue. But not sure.
3 years 7 months ago #60640

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

  • Posts: 970
  • Thank you received: 94

Replied by alacant on topic Problems with AZ-GTI mount and PHD2

Hi everyone
Guys, are we sure the azgti is reporting side of pier correctly?

@OP: (pointing south for now, there maybe different issues crossing the pole to the north) slew east of meridian:
indi_getprop *.TELESCOPE_PIER_SIDE.*

now slew west of meridian:
indi_getprop *.TELESCOPE_PIER_SIDE.*

What's the output of each command?
Cheers and clear skies,
Steve
3 years 7 months ago #60647

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

  • Posts: 10
  • Thank you received: 0

Replied by Carlos Martínez on topic Problems with AZ-GTI mount and PHD2

Hello everyone.

Last night I tested firmware v3.20 and this solved the problem. But the guiding was not as good as in Windows (I tested too).

It could be an encoders problem? I think I have read in a forum that it should be done, but I'm not sure.

I attach PHD logs from INDI and ASCOM. I can't attach KStars log because it's 48Mb long :-S.

I think that this problem is solved.

Thanks again.
3 years 7 months ago #60716
Attachments:

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

  • Posts: 2257
  • Thank you received: 223

Replied by Gonzothegreat on topic Problems with AZ-GTI mount and PHD2

Good to hear you got the main problem sorted out :)
3 years 7 months ago #60717

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

Time to create page: 1.296 seconds