Interesting. I'm running the bleeding edge on an AstroPi3 installed Kstars on an Odroid-N2 and I have the menu item "Configure Notifications". My AstroPi3 install was relatively recent (probably less than 2 weeks)>
Thanks I figured that must be the case. I'll tweak my coordinates.
Is there a directionality to the polygon? I've created what it indicates is a correct polygon, but I assume that the coloured polygon in the centre of the screen represents the viewable area, but I would have expected it not to be shaded (less readable)
Is this the correct behaviour?
I haven't yet had a chance. The recent new moon was spent backcountry camping (Kejimkujik National Park) and doing time-lapse
I will try it soon.
This is a dumb question, as I of course could just try it and experiment, but I'm about to try Dithering for the 1st time...
Both Ekos and Phd2 seem to allow the enabling of dithering. If I configure Ekos to use Phd2 guiding do I also enable Dithering in Ekos or does Phd2 handle all of that?
Also trying a new ZWO ASI224MC as the guide camera rather than my QHY5IllM. Phd2 will directly connect to the ZWO, while (for me) it would only connect to the QHY via indi. This will get closer to matching rlancaste's suggested setup.
I haven't tried overclocking the RPi4, but I just tried writing to a SD card on the Odroid-N2 -> about 19 sec.
A non-scientific test:
Odroid-N2 using AstroPi3 setup
Raspberry Pi4 using Stellarmate
RemoteDesktop into these using NoMachine: No debugging enabled, Storage to the internal (Rpi4 or Odroid-N2) storage,
1) Capture dummy 1 sec exposure Nikon Z7 (90 MB fits), 1 sec exposure QHY5Ill-M (1.2MB fits) as 2 jobs in the Capture queue,
2) Let the fits previewer display each image as it is captured.
So with the RPi4 KStars Build: 2019-09-08T20:04_46Z (oops, not the latest) about 21 sec.
and the Odroid-N2 Kstars Build: 2019-09-24T09:50:13Z about 14 sec.
The difference could be attributed to:
Kstars version (I wouldn't think so)
the number of CPU cores/speed
the speed of the storage device (Rpi4 -> SD, Odroid-N2 -> eMMC)
Memory did not appear to be an issue.
If anyone else has both devices, it would be nice to see if this is reproducable.
The only issue I have now is that Phd2 (for those so inclined) sees the camera via indi, but not with a direct connection (on an Odroid-N2 Ubuntu 18.04.3 LTS kernel 4.9.180-62 aarch64). Not sure I want to break things by tinkering this time.
So with the recent 85-qhyccd.rules update, I can run my qhy5LLM under indilb successfully,
When I tried to connect to it directly in Phd2 to use your suggestion, it can't find the camera. I suppose I should do some reading to see how this camera needs to be installed to make Phd2 happy as well as Kstars.