You can test using the simulator.
"2020-09-16T22:29:09.259 Mitteleuropäische Sommerzeit INFO ][ org.kde.kstars.ekos.capture] - "Ekos will refocus in 3.600 seconds.""
Also, you are set to refocus after 1 hour anyway. Most likely, temperature drop will not exeed the [delta] T before the next refocus will be triggered anyway.
So if you want to test refocus on delta[T], disable the refocus after 60 min check box.
I can 100% confirm Chris' analysis. He helped me figure out the same problem earlier this year when I had the same erratic behavior with an iOptron SmartEQ mount, which - importantly - uses the same hand controller as the CEM25P.
The culprit is the DST setting.
Set that that to 'N', i.e. no, and your problems will go away.
By the way, I am now using the CEM25P as well and there is no problem with meridian flip, works like a charm, provided the time zone is set correctly.
Autofocus on [delta]T works like a charm using the MoonLite focuser driver. I have it set to automatically refocus if [delta]T > 1.5 and it does so faithfully.
Jacquigreenland wrote: I ran across this thread and wanted to offer some info that may or may not be useful.
We have an ipolar on my wifes setup and I wanted to move everything onto an RPi so we didn't have to trail long usb cables from the gear to the laptop (she likes to sit in the warm) and as a result I've been playing with ekos and the ipolar.
The ipolar seems to work happily with the V4L driver and doing some USB sniffing on the protocol the official software uses it does seem like a pretty bog standard device in that respect. What I did have to do is change some settings in the indi control panel as it seems to default to a 640x1280 image and not the 1280x960 it is under capture options which led to some interesting visual effects. I also needed to tweak the gain up quite a bit to get decent images (around 288-320 gave me good results) and with that set and a 250ms exposure I have been able to capture images which I can solve at nova.astrometry.net so it does seem to have the capability.
However, actually trying to run the polar alignment routine (using the local engine with all the indexes downloaded) leads to the astrometry process just sitting at 100% CPU and never finishing, or at least not finishing within any timescale I've so far left it running (in the order of 5-10 minutes) and I was under the impression it should be a lot faster than that.
Hopefully that information helps in that the ipolar seems to work well enough to capture images to solve with the V4L driver, I'm just now stumped on what my problem with solving them locally is so am going to need to learn a bunch more about the commands to try and run it against the images I captured from last night as my cloudy SW UK skies are not likely to give me another clear period to test in for a while.
Did you specify the correct directory under Solver Tab > Options?
The installed index files should be marked with green check marks there, if the correct directory has been specified. If they are not marked, make sure the correct link to the folder containing the index files is loaded and uncommented in the configuration file.
With the exception of the Orion Nebula, I never had a need for that, but I agree, it would be great to have that option.
It would still be good to see your logs and know what equipment you are using. RMS 0.3 is indeed extremely low. That support's Steve's hot pixel hypothesis.
I would be surprised if flexure were the problem, unless you are using a superlong focal length telescope. For instance, I see no flexure with an RC8 at 1600 mm and a 280 mm guide scope.
Deesk06 wrote: Hi everyone,
I have been having an issue lately with the internal guider. I believe there is something I am doing that is wrong, but I am not sure where to start.
First of all, my issue is that I am getting star trails when guiding. For instance, I took a 120 second guided and unguided image...and to my surprise the unguided image had round starts but my guided started to get elongation(RA Axis).
I was shocked when I saw that because it really doesn't make any sense. It has to be a setting that I had input correctly for the internal guider. The only thing is that I have been using auto star, so the calibration should have taken care of everything.
Another issue I am thinking of is differential flexure between my guide scope and main imaging scope.
Not sure where to start with this, if anyone has any ideas I am all ears
Mine work, too. No problem with connecting after installing from the latest git. The crashes are gone and all the peripherals are recognized again for me.