So.. since it was my plan to image same objects this week. I did.
My scope is a modest AT72EDII F6. Nothing close to RASA's F2.
The Leo Triplet came out not too bad.
But the Markarian's chain... at 120 sec x 60 it was nothing to look at (very light polluted area).
Tonight I retried at 240 sec x 40. Not much better.
Next week I'll drive 8 hours away from home to a dark place and see what difference will that make (hopefully everything will cooperate).
I already learned to live with this (double check for those things) but would like to report anyway.
There is a couple of settings in INDI Control Panel which sometimes change voluntarily.
Maybe there are more but these two are sort of important.
1st. 8 bit/16 bit format for ASI294. Sometimes this setting sticks at 16 bit (which I prefer) but sometimes reverts to 8 bit .
2nd. I have two cameras (guide and primary). Sometimes INDI makes both cameras "Primary" - this caused crashes on many occasions before I noticed.
Just reporting potential bugs.
I reported this a while back. Then it didn't work (for me and some other people) on both Windows and RPI KStars clients.
It has been working very well for quite some time now on RPI client (which I mainly use).
Tried it on Windows client (v. 3.2) three nights ago - all worked except for this polar alignment issue.
Last night updated to v. 3.2.1 - same issue remained.
Symptom - start PA procedure, 3 rotations, select star, next, press "refresh" every 1 sec (tried different refresh intervals, different exposure times - didn't help),
-- it doesn't refresh at all. Takes a frame and then the log shows "cannot capture while CCD exposure is in progress. retry in 10 sec".
At the same time, framing in the Focus module works, looping in the Guide module also works.
Is this just me and some of my settings or this really is a bug?
My guide/alignment camera is ASI120. Main camera is ASI294.
But again, it works great on RPI client. Would be nice to have it working on Windows too...
After the updates I had a successful session. No crashes. No hiccups. Everything worked.
Except for the usual (for me) auto-guiding problem. It works but is not very accurate. RA guiding is good but the DEC is not so (sometimes it's better sometimes its worse and it takes many tries to get calibrated - it keeps failing at the last step - DEC reverse drift. The first three steps usually go without a fail).
I probably have some play/backlash in the DEC axis. My mount is cheap (but very light and great for a mobile setup), so this is to be expected, I guess.
Happy with the outcome. : )
That's what I was planning to do tonight... One of them.
Thanks for sharing!
Yes... Today a bunch of INDI drivers got updated.
All is fine now.
This was a build I downloaded just 3 hours ago.
No errors, just my mount/camera wouldn't show up as if they were not connected.
Both RPI and Windows clients.
Once I reverted to an older build, all started to work normally again (with the same cabling).
Dunno. Maybe it was a faulty install.
reverted back to an older build (10 days ago or so) - all is well
Last night I tried 100% mobile setup - everything was running on RPI (Stellarmate with a recent nightly). 10" HDMI monitor, keyboard and mouse also connected to RPI.
All went exceptionally well - polar alignment worked as it should (no "refresh" problem as with the Windows client), autoguiding worked great (struggled to calibrate it, but once calibrated it was perfect) . Plate solving was fast. No crashes.
Happy. Thank you!
Attaching the result - Pinwheel. 120 x 60 sec, gain 150 + 60 x 120 sec, gain 200 - 4 hours total exposure. Very light polluted location.
Tomorrow, I will go to a remote and darker place - hopefully it will work there too (never tried my setup away from home yet).
Great info - thanks!
pch wrote: All depend what you do with your telescope.
But if it's to make nice pictures some kilometers do not make a difference.
The limit may be the hour angle computation, this can make the mount meridian flip wrong, or trying to slew to an object below the horizon.
111 km make a difference of one degree, take this as the limit.
Some days it goes without a problem but often KStars just crashes after a few frames.
This kind of crash comes out of the blue when everything was set, aligned and fine.
A sequence was defined and shooting was started.
Tonight it crashed after 33x60 sec frames. While I was away from my Windows desktop.
Good thing is that when I restarted - it remembered everything. I just needed to recalibrate/restart autoguiding and after that it was ready to continue shooting.
Now it's on the 82nd frame out of 90. I guess, it won't be crashing anymore tonight even though I am actively using this PC (typing this post, doing my taxes in TurboTax, etc).
Just sharing my experiences,
: ) I do realize that it's best to be accurate...
Still, it would be interesting to know what the consequences are if I am, say, 1-50 km off...
I am not taking about 1000 km which would, I guess, make a huge difference.
OK. I'll experiment myself.
I do realize that it's important....
But my question was (I should've emphasized it more clearly) - what is the tolerance there?
Is it OK to move 1km away without updating? 2km? 10?
2 digits after decimal point is enough? 3?