Solved Problems getting StarGo to slew the mount correctly

I am having an issue with getting the mount to be slewed correctly using SkySafari Pro 6 or Cartes du Solei (SkyMap). I have the following versions of software running:
SkySafari Pro 6 (V 6.7.2); StarGo V 6.4.4; Firmware 6.4.0; Ascom Driver 6.8.6.5; and I have connected as MT Type M-uno, Axis mode Equatorial.
I have followed the instructions in the StarGO manual, V 4.1.2 that came with the mount. I am connected between my Android V67 Thinq phone (Android version 9) over the StarGo WiFi. The SkySafari connects OK with a strong signal, as I am close to the mount, and everything works according to the instructions up to page 65 when the mount is supposed to be synchronous with SkySafari. But when I select another object to improve my alignment the scope slews off in a different direction altogether, or moves very little. I had previously setup the StarGO observation location data and mount type, etc. via a direct USB connection between my laptop (running Windows 10, latest version) and the M-uno mount. I have checked everything a couple of times but I do not see anything wrong. However, every time I try to goto a different object in SkySafari, the mount slews somewhere else, usually away from the direction it should. I had done a Synch Home position in StarGo with the mount pointing to the NCP and CWD position just as stated in the manual. I also tried to use the manual controls to move the scope to a given object after the SkySafari slew failed, after the initial NCP 'align' step, and tried another 'align' hoping to improve the sky model, but further slews are still totally wrong. I have used both single star and multi-star modes. I have even tried the similar process in the manual using Cartes Du Ciel (SkyMap) latest version for Windows 10 using the USB connection and it has the exact same issue. Since I have only had the mount for two weeks I assume I am doing something wrong but cannot figure out what. Any help is appreciated. If anyone needs further info let me know, but I tried to provide as much as I thought was needed. Also, does anyone know how to 'clear' the mount alignment model one a multi-star starts adding points, so one can start over again?
Thanks,
Vince C.

Hi Vince,

Make sure that the motors aren't reversed in the StarGO settings (it's under one of the tabs, I forget which one). I have had weird initial slews before and it was the result of one of the motors being set to reverse. If those are both unchecked then maybe create a new profile - to do that you go back to the first tab in the software, type a name into the textbox, and click save.

As a note, my initial slew is always "off" but it will always be in the general direction of where I want to be. Usually I just have to adjust RA a bit to get on target, then I sync in CDC. I wouldn't bother doing a multi-star alignment. One-star alignment seems to work just fine.

Dan

Dan,
Thanks for the quick response. I have checked for reverse motor direction. Both boxes are unchecked. I did create a user profile and even looked at the .mcf file and it also shows that the reverse motors are unchecked. My observation location is correct and the time. When I close StarGo and bring it back up all the info looks correct for the location and mount type. I have it set for single star. But when I run SkySafari and do the initial align it has the mount tracker on Polaris, as expected. I just tried this and tried to slew to the moon, which is in the West, I did the go to after selecting to the moon and it moved from the CDW position to the East about 10 degrees and stopped. So far nothing different.

Just to close this thread, all problems have been resolved. There were fundamentally two problems. The first was the need to set the DEC motor to reverse in the RA DEC section of the StarGo user interface. It would have been useful to mention the possible need for this and what to look for in the manual. The second issue was erratic GoTo movements. This was caused by me not following the manual carefully enough. It had to do with me not connecting the hand controller when I used the third party planetarium applications. There is a setting in the Aux form that is Disable Keyboard that needs to be checked if operating without the keypad. Once I had these items addressed the system worked well. Thanks to Stefano for helping me through these settings.