Yes you can save to the SD card. In EKOS set the Upload option to Local. Then set the Remote directory to /home/pi/whatever
However, the downloading of the images whether I'm capturing subs or images for alignment is very slow. It takes 40-60 seconds to download one image. I'm thinking there must something I'm doing wrong either in my process or my setup. I'm hoping someone might have some suggestions for me.
Also, is there a way to just save images to the SD card and not have them download? Once I'm happy with the image, it would be nice to speed things up by just running a sequence of captures where it only saves on the camera SD card.
I have format set to native and upload set to client. I am using the offline solver in alignment (with Astrometry loaded on the Raspberry Pi).
I'm having issues with KStars/EKOS crashing on Windows 10. Is there a way to debug the programs on W10?
Polar Drift Alignment is close to being one-shot. It operates near the pole and relies on the fact that PA drift is perpendicular to the PA error so it detects the error on both axes. It also does not need any calibration for camera rotation nor any slewing. All it needs is a guide star within about 5 degrees of the pole. On the down side its accuracy is limited by PE and seeing as it uses very small drift amounts that get smaller as PA error reduces. It can also give wrong results when tracking is disabled as the resulting RA drift is indistinguishable from PA drift. But used correctly, it should however be able to get within 10 arcminutes quite readily and in good conditions even less.
The theory is described at canburytech.net/DriftAlign/DriftAlign_4.html
I developed the module in PHD2 so it would not be a stretch to implement in Ekos.
Use PHD2 Polar Drift Alignment tool. You just select a star near the pole, make sure tracking is on , then start the tool. It shows you where you need to move the star to for a pretty good polar alignment. Not as precise as other methods but very simple and quick. No need to rotate the mount or anything like that. Can be done without PHD2 being calibrated also.
If there's enough interest, maybe the tool could be incorporated into EKOS?
Make sure PHD2 is in server mode. Tools menu, tick Enable server
I'm not at all familiar with the Ekos code but I had a good look through it and I think I can see the cause of this problem.
In line 1732/33 of capture.cpp, sendNewImage is only called for imges saved locally. But it is sendNewImage that does the emit newImage at line 792 which causes the counter to be updated.
Also, in sendNewImage there is also code that test for local saving of the image.
So either the emit NewImage needs to be moved to before line 1732 or the if statement at line 1732 should be removed. Or something along those lines
I'm running indi-asi driver version 1.6
Should I install the nightly?
I am having the same issues. One possible clue is that the config file for the ASI1600MM has entries tagged as device='ZWO CCD ASI120MM-S'
But otherwise, the saving of the VideoFormat seems to be somewhat random. Sometimes saving correctly, sometimes as 8 bit and sometimes with no values at all. This last case causes errors on config load sometimes on the ASI120 and sometimes on the ASI1600
Config files attached
I just did some testing with different combinations of settings. Basically, the counter stops working when the images are saved to Remote only. Saving Locally or to Both the counter works as expected.
I save to remote only as it takes a fraction of a second to save the image and move on versus many seconds to download to the local Ekos machine. Over the course of an evening that is a big time saving
Interesting. I normally use FITS viewer for checking things before imaging but when imaging I save the images to the remote device to avoid the download time. So in that situation the FITS viewer does not come into play.