Let me know if I can help test the driver fixes. The combination of real mount and ccd simulator works really well for that purpose.
On a separate note: Have you considered making this into a generic telescope driver / mount model that just talks to the motor controller on arbitrary telescopes? Or pull the functionality into a separate mount mode / telescope pointing plugin that can be used by telescope drivers? I started reading about the different approaches to aligning and calculating pointing models and I think it would be great if these research papers could be put into practice easily.
let me start by saying thank you for developing the plugin. It brings me one more step towards my goal of simply putting up the telescope outside and do all my aligning and observation from inside the house.
I have been testing the Celestron AUX driver in the last couple of days using my real mount and the CCD simulator to be weather independent while it is cloudy outside. I can reproduce the tracking problems using the Nearest Plugin simply by doing continuous exposures using the simulator. You can clearly see the start wandering out of the frame. Once I switched to the Internal plugin those problems went away.
The warning message is useful, because the Raspberry Pi throttles down when it does not get enough power which will affect the speed and responsiveness.
I had a similar problem using a battery instead of a power supply. The battery I bought only outputs 2A over the USB port, so I was ready to exchange it for a stronger one. I did some more experimentation and it turned out to be the USB cable connecting the battery to the Raspberry Pi. Maybe try to exchange the USB cable to another one you have or get a new high quality USB cable. Anker cables are usually good.
You can check if your Pi gets throttled or got throttled since power-up with the script on this page: harlemsquirrel.github.io/shell/2019/01/0...-thermal-issues.html