Problems with AZ-GTI mount and PHD2

  • Posts: 10
  • Thank you received: 0

Problems with AZ-GTI mount and PHD2 was created by Carlos Martínez

Hi everybody.

I'm having a lot of problems using EKOS and external autoguiding in PHD2. If I enable DEC guiding mode as "Auto" I always get a graph like the attached one. At first, it goes well but when a north correction pulse is done, the DEC red line goes down wildly.

Instead of that, if I only change USBs to my Windows laptop and start ASCOM + Cartes du ciel + APT + PHD2, the graph is perfect, as seen on attachment.

This is my equipement:
  • Mount: Skywatcher AZ-GTI + Star Adventurer wedge + serial cable
  • Main tube: Skywatcher Evostar 72ED 420mm + Canon 550D
  • Guiding tube: Svbony SV165 30mm/120mm + ZWO ASI178MC
  • System: Raspberry PI 4 & Astroberry (INDI Library v1.8.6 & KStars v3.4.3 using EQMod driver)

I have a friend with the same problem.

What could be the problem? Bad settings? Driver bug?

Here are PHD2 logs. I think I'm going to test it again tonight and I'll get INDI logs.


Thank you in advance.
4 years 3 days ago #60506
Attachments:

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


×

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

Bi-monthly release with minor bug fixes and improvements

Read More...
  • Posts: 10
  • Thank you received: 0

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


Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

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

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

Same results with internal guiding?
4 years 3 days ago #60529

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.

Thanks for your reply.

With internal guiding I got the same results as in this post , so I abandoned this option because PHD2 was running well on Windows with good results. I thought using the same guider first to compare results and then resolve internal guider problems. At the moment, I can't guide on linux correctly, only using DEC mode South, but it is not as acurate as Auto mode.

I haven't mentioned that in Linux and Windows, PHD2 has the same settings and that in Linux (astroberry) I've only run INDI server (using the web manager) and PHD2, because of I think the problem is INDI driver. PHD2 versions are the same on Windows and Linux too.

I can attach windows PHD2 logs if you want them.


Thanks again.
4 years 3 days ago #60536

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

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

once last thing to try: ST4 cable. If used instead of sending pulses to EQMod, does this make any difference?
4 years 3 days ago #60545

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.

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.
4 years 3 days 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.
4 years 3 days 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
4 years 3 days 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.
4 years 3 days 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


Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

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.
4 years 1 day 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.
4 years 1 day ago #60631
Attachments:

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

Time to create page: 0.847 seconds