I just upgraded to the latest updates (via the SM OS SM tools.
Now, my mount slews the opposite direction than what it should and in the INDI control panel , the Reverse indicator is on in the Motion Control tab fpr EQMOD... and even selecting the E/W & N/S doesn't change the behavior.
If referring to my comment.. guess what... I couldn't find out because VNC was non-responsive, as was trying to SSH into the RPi to try to run htop.
Because actually on my network, when working correctly the RPi4 is snappy enough to not have any issues. I have MORE issues trying to connect a remote KStars up to the RPi since the Mac version of it frequently dumps on itself in a most smelly manner.
I'm sorry... did you say a BETA version was being forced out on the stable platform?
If so, that is sheer stupidity at a base level.
A developer should NEVER push out ANY beta product in a stable channel. They should have an existing infrastructure of BETA testers that participate in the testing.
I know that I personally have lost many hours of capturing because an update was pushed out in the "stable" channel and was not apparently tested. And no, I'm not a programmer, but I've helped with BETA testing software as far back as the VERY early 90's, and even back then, you did NOT push out any BETA code into the stable product line (especially if dealing with a paid for product like StellarMate OS).
From what I understand, a known issue in the current version of KStars/INDI that should be fixed in the next version... still a few weeks out.
In the mean time, if you are using optical trains, simply set it at what the reducer/correct would b in the "Telescope" definition area.
Have tried that also, and also have gone and attached the hand controller and gone in and reset the mount via it also to the factory defaults (I'm making an assumption that it will clear all settings and set it back a it was shipped.
Still (for me) seems to be an EQMod issue.
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.
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.
TZ offset is -6 now, whereas before the time change it was -5... so the TZ is set correctly, even though I may have typed DST we are in CST - the offset is correct though).
Join the club... I upgraded to the most recent stuff tonight (11/12/2022 - using Stellarmate OS) and I have had NOTHING but issues with my EQ6-R Pro.
In fact, it's so bad I'm moving my captures onto my external storage and am going to go back to the original version that I had, as I KNOW that works with my setup... It's rather frustrating as it appears that regular licensed StellarMate OS users are actually the "BETA" testers for it, even when not using the "cutting edge" BETA stuff.
I am SO tempted to dump these RPi4's off on someone else and simply invest in two ZWO ASI Airs. At least THEY seem to work reliably and don't keep taking a crap all over themselves with every update. I lost over 5 hours of capture time tonight dorking around with this stuff. And for what I've spent on these RPi's I could have easily purchased the ASI Airs. The only reason I didn't was I liked the idea of being able to use other cameras down the line.
Hell, I've even thought about going to a Intel NUC, but I figure I'd have the same issues with it as I do with StellarMate since they both would use the same core software.
And yes, my time is set correctly... and it recognizes that we are in DST here in my EQMOD config screens for the mount.
Apparently there is a bug in the system. If you set your telescope FL correctly in telescope definition area, then in the optical train add the focal reducer, it dose not "do the math" and give the correct focal length. You have to set the focal length WITH the reducer factored in the telescope definition field. In my case, instead of setting 710mm and a reducer of 0.8 and getting around 586mm, I have to set the telescope at 568mm. Jasem is aware of the issue and there should be a fix pushed out in a few weeks to the new version.
I have to wonder if this may have something to do with what's happening to me (but not with the APP but VNC connection). Stellarmate OS on my RPi 4 8GB becomes VERY slow to respond, and when I try to connect with the app it is very slow to connect and respond when this is happening. Frequently it will disconnect from the VNC session and I can immediately reconnect, but it is still slow to respond and then suddenly it will go back to working correctly.
ST4 is the cable/format for what looks like a telephone cable.If you are using EQMod and are hooked directly to the mount via a computer using USB (in the case of my EQ6-R Pro you don't even need the ST4 cable hooked to the guide scope if it is already hooked also to the computer (in my case the RPi 4 running StellarMate OS). The guiding pulses will be transported via the USB cable to the mount.... and I recently discovered that and it allowed me to junk one more cable from the spaghetti mix on the setup.
Lucky you.... I'm having to reload RealVNC about every 30 seconds because either VNC becomes totally unresponsive or the RPi running the latest update (as of last night) simply disconnects.
Something is seriously wrong as prior to the latest update, I did not have that issue and the connection is very reliable. Using 5G and when I can get the RPi to respond, the signal strength is 71%, so it's not a weak signal issue.