Don't know about anyone else... but had a chance to get out tonight as it was clear, and when trying to GoTo (via KStars to Caph to check the alignment out, the tracking in KStars simply stopped about 1/2 there and the mount quit responding. I disconnected the EQ6R-Pro and then connected it back, and ti continued slewing to the target and was able to do an alignment with it.Then, I decided to target NGC_133. Gets in the general area, and then when it is trying to complete the alignment, it can't as it does not appear to be slewing the mount to change the alignment.Power the entire system down, start it all back up, and it starts and runs OK... UNTIL I have to go out to do some weight movement for the RA. Try to do an alignment again after this and rinse and repeat the above cycle.Then to top it off, the guiding (which I have configured to use EQMod) for the DEC went from a fairly steady 0.23 to over 23.5 in a matter of seconds and then was bouncing all around... and when checking the scope, it seemed rock solid. And these are using same placement marks for the scope that I have been having excellent luck with.
I then attach my ST4 cable and change the image train for the guide scope to track using the ZWO ASI290mm and then it goes back to this (which is not the greatest it's been but MUCH better than what it was earlier tonight).
Now, tell me, how exactly do I have "insufficient stars" in the image to do alignment?
I've even got both 8.8GB data sets loaded to use for alignment.
I'm beginning to have some serious doubts about StellarMate OS on the RPi. Seems like ever since the optical trains were instituted into the mix of software, stuff has gone off the rails (and I have a strong suspicion the similar developers are involved in both). And I'd REALLY like to be able to enable the logging, but StellarMate OS then became totally unresponsive to ANY input via VNC.Then, when I go outside to check the mount and scope, the weights are pointing directly west, and the scope is pointed directly up... which is nowhere NEAR where the target it was supposed to skewing to was.
And here is an example of going back to the EQMod tracking a few hours later after using ST4 and the camera.
As you can see, it went fully back to crapping all over itself using the EQMod driver after over 5 hours of tracking successfully using ST4 interface.
And here we are back to using the ST4 interface 2 minutes later with NO changes made other than changing the optical train to the camera (ST4) and then doing a new alignment (which detected within range) and starting the guidng up again.
So, in my limited knowledge of programming and astrophotography but many decades of dealing with programs and BETA testing, I strongly suspect there are still issues with the EQMod driver that have not been resolved. To put it in a nutshell, it still seems to be farkled beyond regular use