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.

Read More...

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)

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

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.

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.

Read More...

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.

Read More...

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.

Read More...

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.

Read More...

Hi again.

I've got some KStars logs and the PHD2 related. I attach them.

At first DEC mode south was selected, because it doesn't fail, then changed to DEC mode auto that failed a few time after.

23:32:12 - DEC south mode guiding
23:34:00 - Changed to DEC mode auto
23:35:20 - Guiding failed

Here are some guiding logs that I've found. Sorry but I don't understand INDI logs between them (as you can see, logs are in spanish, sorry about that):

[2020-09-23T23:28:07.406 CEST INFO ][     org.kde.kstars.ekos.guide] - "PHD2: Guiding started."
[2020-09-23T23:28:07.427 CEST INFO ][     org.kde.kstars.ekos.guide] - "Guiado automático iniciado."
[2020-09-23T23:28:07.516 CEST INFO ][     org.kde.kstars.ekos.guide] - "PHD2: Tiempo de exposición fijado a: 1.50"
[2020-09-23T23:28:07.555 CEST INFO ][     org.kde.kstars.ekos.guide] - "PHD2: Modo de guiado DEC fijado a: South"
[2020-09-23T23:34:07.647 CEST DEBG ][     org.kde.kstars.ekos.guide] - PHD2: event: "{\"Event\":\"GuideParamChange\",\"Timestamp\":1600896847.633,\"Host\":\"astroberry\",\"Inst\":1,\"Name\":\"Dec Guide Mode\",\"Value\":\"Auto\"}\r\n"
[2020-09-23T23:34:07.648 CEST DEBG ][     org.kde.kstars.ekos.guide] - PHD2: event: "{\"Event\":\"ConfigurationChange\",\"Timestamp\":1600896847.633,\"Host\":\"astroberry\",\"Inst\":1}\r\n"
[2020-09-23T23:34:07.649 CEST INFO ][     org.kde.kstars.ekos.guide] - "Evento de PHD2 desconocido: ConfigurationChange"
...
[2020-09-23T23:36:12.552 CEST INFO ][     org.kde.kstars.ekos.guide] - "PHD2: Guiado automático detenido."
[2020-09-23T23:36:12.570 CEST DEBG ][   org.kde.kstars.ekos.capture] - Guiding state changed from "Guiding" to "Aborted"
[2020-09-23T23:36:12.571 CEST INFO ][     org.kde.kstars.ekos.guide] - "Guiado automático interrumpido."

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)