Here are some, hopefully I give you what you want, otherwise, please give me specific parameters for which you want defaults:
I believe that if RA/DEC is not enabled, then the direction buttons below don't matter.
Phil: You asked several questions:
Re missing parameters: I assume you mean at least aggressiveness and min/max move for RA and DEC. In the version of KStars that you're using, those parameters can b found by looking on the main guider page, there are some tabs on the right side of the page and one is called control, click that. In version 3.5.5 that tab was moved to the same menu that you were looking at.
Re making a plot of mount movement without any guiding: the way to do that in Ekos is to "guide" but disable the guide pulses for both RA and DEC. That's on the main guiding page--the line on the left that says "Directions"--just uncheck both RA and DEC. Remember to re-check them when you're done.
To force a calibration: you can click on the garbage can to the right of the guide button which will clear the calibration. Then, after you press Guide it should calibrate before guiding. Depending on your settings, Ekos may try and reuse calibrations, or it may re-calibrate after each mount slew, so this garbage can press might not be needed.
There's a more than decent chance I don't know what I'm talking about here but, just in case not, here's what I mean:
Connect your mount to Ekos using the SkyWatcher -> EQMOD Mount connection, then just plug that cable from your computer's USB to the mount's hand controller port.
That's what I do with my Orion Atlas Pro, which I believe is pretty much the same mount as what you have.
@Collin: Just a guess, but perhaps it would work if you used the old-school approach for your mount, and plugged an FTDI cable into the the hand-controller port, e.g. using optcorp.com/products/stellarmate-usb-to-...q5-eq5-eq8-eq3-cable or the USB2EQ5 cable on www.store.shoestringastronomy.com/products_eq.htm
I think what I did, when I used VNC, is have my router reserve an ip address to the different machines, so I knew ahead of time which IP address was which, and then I told vnc to go the IP address. For NoMachine, it discovers the machines on the network, so that's a little easier.
Ron, I do this with KStars/Ekos. I just treat the two systems as separate. I have two different remote desktop sessions. They don't know about each other.
In my case I use NoMachine, and after I connect to the first machine, the File menu has a "New Main Window" option to start the 2nd session.
Yes, it should perform the meridian flip.
Not flipping during a meridian flip is a common issue.
It is usually fixed by setting the "Flip if HA > ..." parameter on the Mount Page.
I tend to use 0.25 hours, others use different values, it's mount dependent.
For a recent related thread, see:
One more thing for you to check.
Can you look at two of your images (just before and just after a dither with this display issue) and see if in fact it did dither by the amount graphed/expected?
Thanks for the report. I'm happy to look into it.
Am I correct: I understand your report as saying it's a graphics error--that is, the guiding is decent, but the graphs report offsets in DEC corresponding to dithering (but it doesn't do this for RA).
Are you using SEP MultiStar? Is the same thing reflected in the guiding page's graph?
Just in case it's some kind of temporary axis issue, can you reload the graph? That is, you could read-from-file from a different session, then go back to this one.
In general for guiding issues:
Please point to a full log uploaded somewhere (e.g. google drive) with verbose, File logging enabled for at least Indi, Guide, Mount and Drivers/Mount.
Also, though I may be able to find it in the log, not sure, please let me know all relevant parameters--e.g. screen shots of your guiding options pages
(Calibration, Guide, Dither & GPG) and the guide page itself.
FYI, this isn't an "affects everyone" bug--e.g. I dither too but don't see that in my imaging. Here's part of my graph from last night using the latest software. For no real scientific reason I tend to dither 2 pixels every 4th image.
The fix is now submitted into KStars' codebase.
If you built from the latest source, the fix should be there, or whenever a nightly build finishes
using this software (in a day or two) you can get nightly binaries that way.
I believe that's a PHD2 parameter. E.g. there are many hits to this google search: