Hi Mike,
Hmmmm
How are you cabled into your Celestron Focuser, direct USB serial or through the AUX port on the mount?
The response packet causing the error, I am clueless.
If you have time and are so inclined, try a startup with your Ekos profile only having the AUX driver and say CCD Simulator, then connect.
Would be interesting if you see the error this way.
It does look like on startup your system is quite busy.
The last command executed was a get AZM encoder position
[2022-11-22T20:28:28.010 UTC : "[CAUX] CMD <MC_GET_POSITION> APP -> AZM "
[2022-11-22T20:28:28.048 UTC : "[CSER] CMD <50 01 10 01 00 00 00 03> "
Then it spits out
[2022-11-22T20:28:28.716 UTC : "[ERROR] Resp. char 4 is 00 ascii "
[2022-11-22T20:28:28.718 UTC : "[ERROR] RES <2C F7 AB 88 55 00 00 00>
This response cannot be parsed so it is bit bucketed, no harm done
Then it asks for ALT
[2022-11-22T20:28:28.720 UTC : "[CAUX] CMD <MC_GET_POSITION> APP -> ALT "
[2022-11-22T20:28:28.764 UTC : "[CSER] CMD <50 01 11 01 00 00 00 03> "
Which gets no response and times out
Then starts the normal 1 second polling interval for ALT and AZ
[2022-11-22T20:28:30.767 UTC : "[CAUX] CMD <MC_GET_POSITION> APP -> AZM "
[2022-11-22T20:28:30.817 UTC : "[CSER] CMD <50 01 10 01 00 00 00 03> "
[2022-11-22T20:28:30.817 UTC : "[CSER] RES (8
: <3B 04 10 20 01 00 00 00> "
[2022-11-22T20:28:30.818 UTC : "[CSER] Got 4 bytes: ; payload length field: 4 ; MSG: "
[2022-11-22T20:28:30.818 UTC : "[CSER] [00 04 10 20 01 00] "
[2022-11-22T20:28:30.818 UTC : "[CAUX] RES <MC_GET_POSITION> AZM -> APP [00 00 00] "
[2022-11-22T20:28:30.818 UTC : "[CAUX] CMD <MC_GET_POSITION> APP -> ALT "
[2022-11-22T20:28:30.874 UTC : "[CSER] CMD <50 01 11 01 00 00 00 03> "
[2022-11-22T20:28:30.874 UTC : "[CSER] RES (8
: <3B 04 11 20 01 00 00 04> "
[2022-11-22T20:28:30.875 UTC : "[CSER] Got 4 bytes: ; payload length field: 4 ; MSG: "
[2022-11-22T20:28:30.875 UTC : "[CSER] [00 04 11 20 01 00] "