Gene,Is
I notice in my log file that the errors occur before the location data is read. Is what we are seeing some sort of negotiation between the driver and the mount to ensure that each knows that the mount is a wedge? And the errors are an indicator that the orientation is not ALT-AZ?
Mike

Mike,

The AUX driver is agnostic to the mount type or motor cards install.

This issue seems to be a hand controller firmware version 'error'
My HC was version 5.31, I saw no errors like yours
I updated to v5.34 and now I see the error in the same place.

The AUX driver uses the handcontroller's 'passthrough' commands.
The message goes to the HC but the message contains info as to what device to talk to inside the mount.
The device to talk to is the third byte in the command sent
If the device does not exist the HC should just blindly timeout and not return anything to the driver.
Seems in v5.34 something changed in the HC firmware so now this message spits out.
Here is what I see now
CAUX 128.286470 sec : CMD < GET_VER> APP -> BAT
CSER 128.336883 sec : CMD <50 01 B6 FE 00 00 00 04>
INFO 129.343382 sec : Mount is unparked.
DEBUG 129.343611 sec : InitPark Axis1 0.00 Axis2 0.00
DEBUG 129.343719 sec : Setting Default Park Axis1 to 0.00
DEBUG 129.343783 sec : Setting Default Park Axis2 to 0.00
INFO 129.343854 sec : GUIDE not supported on MC version 5.14
CAUX 129.344254 sec : CMD <MC_GET_POSITION> APP -> AZM
CSER 129.394555 sec : CMD <50 01 10 01 00 00 00 03>
ERROR 130.061836 sec : Resp. char 4 is 03 ascii ^C
ERROR 130.061939 sec : RES <00 16 BF E8 F0 00 00 00>

I mentioned the AUX driver is mount agnostic, the following commands are executed looking for various component firmware versions:
getVersion(AZM);
getVersion(ALT);
getVersion(GPS);
getVersion(WiFi);
getVersion(BAT);

The GPS/WIFI/BAT should all just timeout if there is no hardware at that address inside the mount listening

I would consider this issue closed as there is nothing else in any logs that indicate this is causing problems.

Gene

Thanks, Gene! I really appreciate you looking at this and getting to the bottom of the problem, or in this case a non-problem. Now I can continue with confidence.
Mike

One more time, I tried Celestron AUX through the NexStar + HC in a real situation tonight and got the same result that I have been getting since the beginning. The capture and solve with slew to target is never able to converge on the target. The program just endlessly tries to move the mount to the target and fails. I will try the Skyportal wifi module to see if the HC is causing a conflict.
Mike

Mike,

When it tries to converge, does it just seem to get closer in the same direction but never get there or does it oscillate around the target, first over then undershoot?
Does the lack of convergence happen in only one axis or both?

What are your backlash settings for both AZM and ALT?

Gene

Gene,
It never gets close. My recollection is that it is declination that has the very large error (the first number in the table of results from alignment). RA is off too, but not as large an error, about two orders of magnitude worse in declination. I have no backlash compensation on, just letting PHD2 handle that.
Mike

Mike,

Have you built a mount model or just did a sync at a plate solve first location then try a GoTO?

Gene

I believe I have tried it both ways. Sync, then GOTO, Plate solve then GOTO. And no plate solve nor sync, then GOTO. The result seems to be the same. I tried with the Wifi dongle alone inside today, and at least this is stable, no wandering off. I'm about to take my mount outside.
Mike

That was a very informative evening. The Celestron Wifi wedge AUX driver performed quite well when the Nexstar+HC was removed and control was done just using the SkyPortal Wifi module. The system was stable and the RA and Dec errors while still on the large side were as low as 160 arcsec for a while. That is until my AZ clutch failed! I conclude I had two issues, the AUX driver is incompatible with the HC and I had a failing clutch and/or gearbox. Now I get to take it apart and see what the damage is. The mount is 16 years old.
Mike

Gene,
The set screw on the pinion gear for the AZ/RA drive no longer fits the hole and the epoxy holding the gear in fractured allowing the pinion to slip. One two many stalls of the motor I guess. Celestron does not appear to sell these gears separately. The pinion for the ALT/DEC drive seems to be identical and the motor assembly with the gear is available. Note sure I want to pay $159 for a gear that may not come off without damage. Any ideas on sourcing of the pinion? Or are the astronomy gods telling me to buy a new mount?
Mike

I able to attach the pinion by tapping a new set screw hole. So my mount is reassembled and seems no worse for wear. I took the opportunity to clean and relube both the RA and DEC drives. The gears all look in fine shape, no excessive wear. No new mount just yet!
Mike

Hi Mike,

I was not aware of a clutch on an SE mount for AZ? Sounds like you came through ok, get a chance to take it for a test drive, regardless of of which driver or visual?

Gene