Question Avalon zero looses motor position ':X34#' results in 'Timeout error. (SOLVED!)

I think I've found the source of the issues and it was related to... USB cables and, probably, interference! The mount works like a charm now. I have a RPi 4B and, currently, I use all of the USB ports. To one of the ports I connect the ATIK CCD and if I use a USB 3.0|1 cable, I immediately get issues. I suspect that there are some interference going on between the ports. I didn't think that could be the case as I tried everything, shutting down all devices until only the mount was switched on, but, alas, the problem remained. Switching the CCD USB 3.0|1 cable to a v2 solved the problem immediately.

Lesson learned? I need to get a powered USB hub which will probably solve the issue as I assume they're probably better shielded.

Phew, I really love my Zero so happy camper now!

Cheers



********************************************


***** UPDATE 2022-08-17 *****

In order to verify ASCOM functionality I installed v6.6 of ASCOM together with v4.01 of Astro Photo Tools. Furthermore I bumped the StarGo FW to v7. After connection my Avalon Zero using USB and WiFi on different occasions, I connected the mount to APT, sync:ed the park position, selected an object and pressed 'goto'. The mount slewed but never confirmed it was finished. I could hear the motors stop but APT never confirmed that the slewing had stopped! Furthermore I'm unable to use the movement buttons in APT - nothing happens. I'm starting to believe I have a faulty StarGo unit and/or motors.

I really hope the Avalon team chimes in here in the near future. Currently my Avalon is bricked

Cheers

***** Original Posting *****
Hi!

I'm running a Raspberry PI4B with Astroberry v2.0.4 and Indilib v1.9.7. Connected I have:
- Avalon Zero Obs with StarGo connected over USB (Using the Indilib StarGo driver)
- Atik Horizon II
- QHY CCD5LII

Recently my mount started to behave erratic and says "Could not get the motor status from mount (err: -4)" or something like that. I've checked the logs and that is the only error reported. This usually shows after 3-4 and sometimes after up to 7 slews. After that the mount becomes very slow in its responses and it fails to report back the position to EKOS thus not updating the scope position in KStars. I can see that Ekos/Indilib sends :34# and then waits for 2 seconds which results in:

- Failed to receive full reponse: Timeout error. (Return code: -4)
- Failed to parse motor state response ''.
- Failed to parse motor state. Retrying...

And this goes on and on...

I've tried three different Avalon FW:s
- 6.20SP6
- 6.56B2
- 7.?

All of them behaves in the same way. Anybody else having the same behavior?

Cheers