Nice rig! Two questions:
1) Is that a Samyang/Rokinon 135 lens?
2) Did you 3D print those tube rings?
Trying to use PHD2 to guide Paramount MyT under Ubuntu 18.04, KStars 3.0.0.
Of course I have TheSkyX running first, with IP server port 3040.
INDI and Ekos can then see and control the mount, slew, image, etc.
But I can't get PHD2 to connect to the mount at all, either through INDI or through AUX Mount (ports 7624 and 3040).
All I get is a "connection timeout" message, and then "Failed to connect to mount."
Also, I'm trying to guide using "Direct Guide" not relays on the mount.
Perhaps I'm confused as to whether PHD2 is controlling the mount via Ekos/INDI (port 7624), or via port 3040 to TheSkyX, or both?
Can anybody help with this?
FYI I used the Polar Alignment Tool three nights ago in Ekos 2.9.8 and it worked like a charm.
I regularly guide using PHD in Ekos with everything connected via INDI, but have never tried the PHD polar alignment tool.
@stash helped me with a very similar problem a few weeks ago, this advice is exactly right.
Use "verbose" option, adjust "downscaling" to keep "extracted stars" to around 100-200, and manage index files to just the appropriate scale for your rig.
WISH LIST: make these adjustments automatically!
I can be TAUGHT to manage image scale/index files and downscaling/extracted stars, because the algorithms are pretty simple. Therefore they should be in code instead of being passed down in the forum.
The image scale only needs to be determined once per session, then the algorithm should never use inappropriate index files again.
Downscaling is more dynamic. Images in rich Milky Way fields need more downscaling than those near the galactic poles. But solve-field provides plenty of feedback, which should be used to tweak the downscaling parameter on the next attempt.
In the meantime, we can turn on verbose output and watch intently as the "extracted stars" text scrolls by, then hit "Stop, then go into the Options tab to change the Downscaling parameter, then click "Solve and Sync" again and again until we get a good result.
Thankfully KStars internal guider calibrates very quickly, so it's not a big deal to repeat this procedure.
But a better approach is to use the declination and side-of-pier to calculate guiding adjustments, so that the calibration remains valid all over the sky. Just as with PHD, PHD2, TheSkyX, or MaxIM DL, it's unnecessary to calibrate for a specific target.
Rather, calibration provides the orientation of the guide camera and guider image pixel scale relative to the sky. The rest of the guide pulse calculation is precisely deterministic from the declination and pier side.
There's no reason to calibrate again unless you either (1) change out equipment -- mount, guide scope, camera; or (2) forget the declination and side-of-pier where calibration was performed. Unfortunately it appears that the KStars guider does the latter every time!
Thank you very much -- this was exactly what I needed!
I've just installed KStars on a new Mac and tried to import all my profiles and settings (especially my local horizon) from linux using the following command
scp -r LINUX-MACHINE:/home/airscott/.local/share/kstars ~/Library/Application\ Support/.
Worked great, and when I launch KStars on the Mac I see my local horizon. Yay!
But every time I launch KStars on the Mac I get the following error:
Unable to find INDI Drivers directory: /usr/local/share/indi
Please make sure to set the correct path in KStars configuration
Would somebody please let me know where to point KStars config for the Mac Indi directory?
Once the HIPS overlay becomes corrupted, it stays messed up, even after restarting KStars, no matter how much I scroll and zoom. The only cure seems to be going into the cache options and restoring the default Disk=1000 memory=300, then retsarting KStars.
Oddly, I just tried it on my MacBook pro (16 GB RAM) and I get lovely high-res renders with higher cache settings. No sign of the corruption I see in ubuntu.
I'm fine with just leaving the cache alone, but it does look like a real bug.
I realize this is an INDI forum, and I'm posting about KStars. Please refer me someplace else if appropriate.
The HIPS all-sky imagery overlay is a wonderful feature for framing targets. I've been experimenting with allocation of disk and memory for this feature, and find a repeatable bug.
Under View->HIPS All Sky Overlay -> HIPS Settings -> Cache, when I select other values than the default (Disk=300, Memory=300) the HIPS display is corrupted. I can still see the image overlay but it's "smeared out" into horizontal banding that looks a lot like old-fashioned electronic static.
When I reset using the "Restore Defaults" button and restart KStars, everything goes back to normal.
This is on an Intel i3 box with 8 GB RAM running ubuntu 18.04.
Screenshots attached below to illustrate the problem.