I think you may have cottoned on to what's happening. I haven't tried to get Ekos to control my Minitower2 since then, but I do remember that after the first astrometry, it would keep slewing way off towards the west (always by the same amount in any session). And for park also it went west. So maybe something in the clock is what's causing it. It would be great if SM/Ekos could also control an MT2! Cheers.
Doh, I'm clearly an idiot, thanks @Alacant! I'd noticed that and hovered over the icon and where it says "Centre Sky Map Centre" just thought that was something else. This is v handy, thank you!
Can that be done for the Align function too? (I've noticed that if I load-and-slew to a particular FITS file location, and then meridian flip happens, the Align module seems to get lost about where it's meant to be looking for?).
Thanks Hy, that's v helpful. I'll try that on the reverse DEC setting out of curiosity (I don't think I need to b/c when I've played w that in the past - out of sheer ignorance! - it's not been good; my mount is an HEQ5Pro).
Yes, I did look at the log the next day & wish it had kept trying (I'm still puzzled about what could have happened - the main scope with narrow FOV found & aligned fine, so I'd have thought that the guide scope with a much larger FOV would be less susceptible to a freak cloud since it would need to be a much bigger cloud which would also interfere with the primary scope; M81 was pretty much near the zenith at that time, so no way any trees or roof lines could have been a factor. A mystery).
On the keeping-trying aspect side of Scheduler, I didn't realise that was a one-time rule that it only tries at that time. The reason I set a time was b/c I was in the middle of an imaging run which was centred on empty space to get a particular framing. And so I just thought I'd set a time to switch to M81, b/c I couldn't figure out how to se the earlier target as a Scheduler run (the Scheduler seems to require a specified target, vs the ability to either put in specific co-ordinates, or put a load-and-solve file as the target - unless I'm missing something. If Scheduler could be set up to not need a named target that would be great b/c then I could do these all as Scheduler runs and w the Terrain tool also up & running, hopefully it would figure out by itself when to switch targets)?
Anyway, thanks for the pointers on the guide calibration - much appreciated.
So last night I left the rig on an imaging run (Leo Triplet) that was meant to finish at around 0120 w a job (m81) scheduled to start from 0130. I thought that the Leo run may not finish all its images (time added for dithering & settling etc), and was curious to see what would happen.
Looked this morning, and happily the scheduler took priority at 0130, the Leo run was terminated and the mount slewed and aligned successfully on M81.
But then the guiding seems to have been the problem - it couldn't calibrate. But it was a clear night (the plateseolving & alignment worked so it can't be have been clouds at that time, and it was guiding fine for the Leo run).
Slightly disappointing b/c it was 4 hrs of missed moonless skies. Hey ho, M81 will still be there in the future, but it would be good to understand how/why this happened b/c if Scheduler is going to be unreliable I am going to have to change my imaging sequencing.
Log file here: www.dropbox.com/s/20ydmtxbytvtpr2/log_20-37-09.txt?dl=0
Guidelog file here: www.dropbox.com/s/cs0gjg36k2syh03/guide_...06T20-45-50.txt?dl=0
Thanks Wolfgang, the log file should be at the end of this link:
You'll see that the log file starts for a 31 Jan session and then suddenly becomes a 4 Feb session. Not sure why it didn't start a new log file for the Feb session. The first successful flip & continuation happens around 2140-2150ish. The flip that happened but then imaging didn't continue is around 0226.
There was a scheduler job that should have begun anyway at 0230 if I remember correctly & that didn't start.
Thanks in advance for any insights!
I was testing if I could use EKOS to control an old iOptron MiniTower2 the other day. Connected the laptop to the handset and the handset to the mount. The mount connected fine and when I told it to do a star align, it went in roughly the right direction, saw that it was not there and then for the correction went waaaaayyyy off. Strange thing was that when I told it to Park, it would not go to the same position that it started in (it went to a completely strange position). Even after I purged the parking configuration & mount model on EKOS.
Is the problem the handset, as in, do I need to clear alignment on the handset and then drive it with EKOS? Or do I need to align with the handset first and then connect EKOS (the problem with that is visual alignment probably won't be as accurate as EKOS alignment would be, and its a faff to replace a diagonal and EP w a camera and refocus for an EAA session)?
I've encountered a strange problem. If I Load & Slew to a particular object (typically a certain framing from previous image runs), if EKOS identifies that as a known target, it does the flip and continues fine. But a couple of times, where the alignment is centred on empty space (eg a pt between the Leo Triplet), it comes to flip time, does the flip but then nothing. And eventually crashes.
This happened last night when btw there was also a known-target job scheduled after the Leo run was meant to have finished. But the job never started. So it seemed to do the flip, didn't know where it was, and kept on doing I'm not quite sure exactly what until it came time to close? (The log runs on for 3 hrs after this flip happened so it was alive and not crashed but nothing seemed to be happening - yet when I opened up the laptop this morning there was an error box and Kstars had crashed).
I can share the log file but its 198Mb big for some reason so it exceeds the size limit for attaching? (Another weird thing, the log file was appended to a log file from 31st Jan rather than starting its own log file)
Not quite sure what's happening?
Thanks Giles much appreciated. I haven't noticed any performance lags with the ZWO CCD driver so far so maybe I've been lucky (or am using small files w quick downloads, since not a full-frame camera).
Hmm, I'm guessing these multiple individual camera drivers couldn't also be used for multiple instances of EKOS (ie if one Pi was connected to two camera+mount combinations)? Or could it be? (For example, an EqMod mount with 2 ZWO cameras & an iOptron mount w a ZWO camera)?
I updated my Stellarmate OS (from 1.5.1. to 1.6.2) and happily the Esatto driver seems to be there in 1.6.2 on the SM Web Manager (1.5.1 didn't have it on the Web Manager).
I'm having to re-setup my equipment profiles, and noticed that whereas before there used to be just one "ZWO CCD" in the camera drivers, there is now "ZWO CCD", "ZWO Camera 1", "ZWO Camera 2" and "ZWO Camera 3".
Pls could someone tell me the difference between those?
Sorry it's been a long time since I upgraded so apologies if I missed something big in the interim! (I was working on the "if it's not broken, don't fix it" rule until I needed the Esatto driver)