HEQ5 Pro connection issues with 1.8.2

Mapleleaf

Prior to Christmas, I setup my scope and HEQ5 Pro in the warm 😀 basement to hookup a new travel router to my AA Pro via Ethernet. All good with the network and my AAP connected to the mount using the EQMOD cable and I could slew it around. Shut it all down and enjoyed the holidays.

Fast forward to 2 nights ago when I fired it up again and the v1.8.2 firmware was pushed into the AAP. Now, I cannot get the AAP to connect to the mount and it displays an error message to check the cable and baud rate.

Baud rate set to 9600 and EQMOD cable is good … have previously used it on my PC direct to the mount with ASCOM software and subsequently with the AAP.

Tried cycling power in all the possible orders, tried different baud rates, different USB ports on the AAP and the Pegasus PBA which is hubbed into the AAP. Nada, nothing, zilch.

Have submitted logs and ticket to ZWO so hope to hear back but wondering if other folks are experiencing mount connection issues with 1.8.2 and or have suggestion on diagnostic steps.

sergimartin

I have exactly the same problem with my HEQ5 Pro. I hope they release a patch for this...

sergimartin

After restarting is working again. I don't know... 😉

Mapleleaf

Was troubleshooting this further last night and it seems to be related to the USB ports. Right now, I only have the EQMOD mount cable and an upstream cable from the Pegasus PP Advanced plugged into the AAP. I’m using a USB port to power the travel router but otherwise, there is nothing else plugged into the Pegasus box. See attached image for cabling

Cabled this way, the mount connection fails. If I unplug the cable between the Pegasus and the AAP (either end), the mount connection succeeds and all appears to be good. Even more interesting, is the mount connection remains intact if I reconnect the Pegasus box to the AAP.

The connection failure persists if I connect the the EQMOD cable through the Pegasus’ hub so it doesn’t seem to be an strictly electrical USB issue but has a software contributing cause. It presents as if the AAP is unable to detect/communicate with the EQMOD cable if there is any other USB cable connected. If, once the initial handshake is complete, the AAP seems to be able to maintain communication with the mount, irrespective of any other USB connections made (don’t have my cameras connected at this point).

BTW: the cabling scheme is unchanged from my pre-Christmas work but now fails which does suggest that there was a problem introduced with the 1.8.2 (9.10) release.

@Sergei Martin, what is your USB cabling setup? Are you able to get a successful connection if you only have the mount connected?

sergimartin

Sorry, I didn't understand your setup, I don't use the Pegasus hub. I connect from heq5 to asiair pro directly through the pegasus eqmod cable, nothing else between.

Mapleleaf

Hi Sergei,

If my theory is correct, the key question is do you have any other USB connections (from any device) to the AAP, in addition to the EQMOD cable? If so, remove all USB cables except the EQMOD from the AAP and then try mount connection and see if it works then.

In my case, that worked. However, if your EQMOD cable is the only connection to the AAP, then there is either a second root cause or my theory is not correct.

Another possibility is if the Pegasus is providing back voltage to the AAP which is a "no no" per the USB spec but apparently pretty common. I saw some postings recently from Chen (@w7way) noting back voltage can cause AAP issues. I don't have any immediate way to test for that but that would be a Pegasus specific issue, unrelated to any other connections present.

Will test some more tonight by connecting my cameras, adding two more connections alongside the Pegasus and will post results.

George

Mapleleaf

Took a little longer than expected and by the time I tested, the 1.8.3 version was released. The good news: the problem seems to be solved. Mount connections on power up were successful with cameras and the Pegasus plugged in to the USB points. As the stated intention of the 1.8.3 was to fix the STA problem, no idea why the mount connection problem disappeared but can’t complain.

Now just wait for warmer weather and clearer skies.