New findings I have to report on firmware 1.2.3 with ASCOM server 6.5.15.
1) When I click Park on the Ascom server, the scope goes to azimuth 270 deg, which is the current expected behavior. When I press Park in NINA, the scope goes to HOME. I'm not sure why the behavior in NINA is different, since it connects to the mount through ASCOM. Please give us the ability to specify the park coordinates.
2) I experienced a random failure to track. After slewing to several targets, tracking stopped. The mount was responsive to new slew (GoTo) commands, but once it settled it wouldn't start tracking the new target. I could not turn on tracking from ASCOM Server, NINA or the hand controller. I had to power off the mount to reset it, then back to normal. This happened once over 4 consecutive days of use. The green light in ASCOM Server may be on, but still not tracking, as stars have streaks and ASTAP platesolve fails.
3) If I change the guiding rate in advanced tab, from 0.5 sidereal to anything else, PHD2 guiding sets the calibration step to a huge value of 10000ms, the star is lost, and PHD2 is just looping. I've tried 0.7x, 0.8x,0.9x guide rates and the same behavior was observed. PHD2 notices when you change the guide rate, and wants you to perform a calibration. Even if I manually put 350ms guiding pulse, which is the expected value for 0.5x sidereal, as soon as I click Shift+Guide to perform calibration, the guiding pulse is reset to a huge number that pushes the star so far that it ends up lost. The workaround is to go back to 0.5x guiding rate and then everything works as expected.
Please investigate these issues and provide any feedback/tips.