FWIW, I also see the same issue--4 rows missing from some images on my ZWO ASI 1600mm pro using Ekos.
It is usually, but not always, the first image from a set of images I start taking from the camera tab.
I don't use the scheduler (yet) so it's not that. Since I typically take 120s exposures, I just throw these away, not a big deal for me.
I only discover the issue in post when running Blink on PixInsight.
I'm sure I could recover several of these images (and companion images that were not "cropped") if that would be useful to someone who might be looking into this.
Thanks. Just wondering, since in my current version of Indi doesn't have the purge-data button (just current, default, and writedata)--it's Stellarmate OS, downloaded this past November, I believe) could I hand-edit that file if I needed to? Or remove it? I notice that currently it has one value for parkposition/axis1position and another different large int for parkposition/axis2position.
If this happens again, should I remove that file? Should I edit it a certain way?
It would sure be great to have a workaround just-in-case.
TL;DR SOLVED, but who know why--perhaps a scope factory reset?
First off: I had the right hemisphere, right time in both Ekos and Kstars, right latitude/longitude.
Went out again tonight, and, starting off parked and pointing at Polaris. Despite that, Indi told me the Declination was -42 or something like that (and altitude below the horizon). I went through the telescope's handset setup and alignment (no problem at all with alignment), but Indi was still off. I tried to set the RA/Dec manually to something like 0,90, but couldn't set it in Indi because "it wasn't tracking", and "it won't track below the horizon". grrrrr. I re-plugged in the handset, found and selected the factory reset button, again re-initialized (time, location, etc) and re-1-star-aligned, and then parked it. (Did parking matter this time?) Re-plugged in the scope to my Raspberry Pi, re-started Indi/Ekos, and magically this time Indi declared Dec=90! It's now happily taking pictures of Horsehead.
So, once again, really don't know what the issue was. My suspicion: that is the indi_eqmod driver gets a bad setting (like, for instance, reverse declination after a meridian flip) stuck in its memory and uses it inappropriately. When that happens, the software is hosed until I accidentally do something to dislodge it. Next time: factory reset, park, and keep my fingers crossed! (But, of course, why would a factory reset affect the indi_eqmod driver? However, the scope was giving me good coordinates when the driver wasn't, so it's likely in the driver...).
I noticed when I just used it, that it said on startup that it was reversing the declination. Should it be doing that? Could that be my issue?
Pretty regularly, I manage to get in a situation where ekos/indi can't seem to sensibly control my Orion Atlas Pro mount. I assume I have some configuration issue, but I can't see to figure out what that might be.
I run Stellarmate OS (a release I downloaded in early December) but I get similar issues with the current sudo apt-get install version of indi & kstars on a different linux pc.
For instance, the mount will be pointed up (e.g. at orion tonight, about altitude 40-degrees) but mount control says it's pointed below the horizon and therefore won't track, and therefore won't sync. I adjust it so that it is in a position that it things is up (so it will track, so I can sync it) where that position is also up in the sky (for real) and then plate solve and sync. Kstars will then show it pointing correctly on its sky map. Then, however, if I ask it to slew to something very close by, it slews halfway across the sky.
I've tried using the Atlas Pro's handset alignment, and that works fine. But then, when hooking the mount back up to Indi/Ekos, the same problems re-occur (so I don't think the mount itself is the issue).
The time seems right in the Indi control panel's eqmod mount, site management tab (e.g. it's 11:45pm in california on 1/23, and it says UTC 2019-01-24T06:45:05 and UTC offset -8. (Actually, perhaps it should be -7, but that shouldn't cause the magnitude of error I'm seeing). Kstars shows my location and local time properly on its screen, top left and bottom left.
The Lat/Lon in the same tab says Lat 37:26:24 Lon 237:50:13 which I believe is "close" (I actually set it to Lon=-122, but it converts that to 237). Hemisphere says "North".
What usually happens is I struggle with this for an hour, finally somehow get it working via manual sync'ing, plate solving, etc, then am able to take pictures. I've taken astrophotos successfully at least 15 evenings in the past couple months, however, these problems always seem to recur sooner or later.
When I'm in such a mess, What is the procedure to "reset" and start from scratch? Is there a setting I'm missing that I should have set? Are there things I should avoid touching when in such a panic?
What is Align Method = "EQMOD Align" vs "Alignment Subsystem" in the Options tab? Is that relevant?
Should I hit "Clear sync data" in the Sync tab when the scope isn't making sense?
Happy to send logs or whatever might help solve this.
Sorry if I vented a bit
Thanks for the great instructions. I was able to fully compile and run indi/kstars/ekos using your Building INDI from Source link above. I compiled it on a Raspberry Pi running Ubuntu 16.04, and ran it on that platform as well. There were a few minor things to figure out, mostly related to compiling 3rdParty, but it worked!
My question is this: I assume what I've compiled and am running is HEAD at the time I did the git clone. I'd rather compile/run/experiment-with a more stable version. I assume there's a way e.g. to get git to clone a tag related to, say, the recent version 3.0 of this software, but I could not find the tags for that. (e.g. tried 'git tag -l' and given the tags, looked at the dates with 'git show TAG' but there we no tags dated around the end of 2018, in fact nothing past the summer). I'm obviously not that facile with git. What commands would I run to get and compile the source for a stable release?
The last couple of nights I was shooting the horsehead nebula from silicon valley, and it crossed the meridian around 11:15pm (though it's altitude was no where near 90). I had mount limits checked using 5-degrees and 90-degrees, but horsehead was nowhere near 90-degrees altitude (perhaps 50-degrees). The camera tab was taking a series of pictures, and the Phd2 tracker was tracking. Around that time, I started getting guiding errors with PhD2, though the sky was clear, and it should have had no issues. I switched over to the internal guider, and got the same issues--where I believe it said it couldn't correct RA. I Also, I believe it had crossed the meridian and didn't do the automated meridian flip I expected.
All these error went away when I disabled the mount limit and manually forced a meridan flip by asking it to track to something on the other side of the meridien (is there a way to simply request a flip, or an early flip?).
I'm a bit confused on the mount limit altitude meaning. Clearly what's important is preventing the camera end of the scope from hitting the tripod legs--so the scope's altitude when it's pointing at something crossing the meridien I suppose is 90, even if it's tracking something whose altitude is << 90.
Clearly, I suspect that the limit was somehow disabling the RA corrections and the meridian flip (though the mount was still tracking). I have no logs or other useful info for you. I'm sure the limit was set at 90-degrees. Sorry about that. If there's some kind of pilot error here, sorry, please let me know what I got wrong. Or, if you want some logs etc, I can try and re-create this and turn on some kind of logging as you request (please give instructions). I am running the latest stellarmate OS release on a raspberry pi.
I've started using indi/ekos/kstars on an RPi and things have been going reasonably well. Thanks!
I would like to better understand the focus tab.
I've been using it to manually focus--e.g. I usually click auto-select star, sub-frame, full-field and then framing.
I look at the plot and hfr number, and turn the focus knob to try and minimze the hfr (ie get the plot points to a minimum).
This seems to work ok, though a little noisy (I assume that's just variation in seeing).
My questions. What do the values on the plot mean? Is this an ensemble hfr or a single star's value?
Even if I try and select the star myself, and view the hfr on the mouse-hint, the values in the hfr text-box and the values on the plot don't seem to correspond to the star I selected.
Or, if I click auto-select-star, also the hfr for that star doesn't seem to correspond to the plot.
Also, is this the recommended way of doing manual focus? Should this work better than trying to center a Bahtinov pattern, or should I just stick to that?
Finally, I'm not sure I understand how to use the relative profile display. What are the two (red and green) plots in there, and how should I interpret the results?