The web page accesses the Arduino through the INDI service, therefore you need to access the INDI service for changing the calibration. And don’t forget to save the parameters, otherwise they will be lost after a restart.
Read More...
That's a misunderstanding, it's not about KStars configuration.
What you need is an INDI client so that you can change the parameters of the INDI device - KStars has one, but if you have another one, fine. Parameter calibration is done through INDI configuration, there is no need to change the code.
HTH
Wolfgang
Read More...
Hi Gunter,
the documentation is here:
github.com/sterne-jaeger/indi-3rdparty/b...adme-WeatherRadio.md
Regarding the RG-11: If we order three items, it should work with customs and the shipping costs are reasonable. I'll send you a PN.
Wolfgang
Read More...
For tweaking the parameters I have an Excel so that I can import CSV data from a RRD export - see attachment. With some Excel knowledge it should be possible to understand how it works. For questions, send me a PN.
Read More...
It's even easier, you can calibrate the sensor parameters directly through the INDI interface:
github.com/sterne-jaeger/indi-3rdparty/b...g-weather-parameters
For explanation about K1..K5, see the section "Tuning Sky Temperature Parameters" in
lunatico.es/aagcw/enhelp/
HTH.
Read More...
Try to increase this value in the INDI dialog of your mount:El Corazon wrote: If this is mount dependent, then CEM25P users should be seeing this. Happened to me now 3 times at least. I am trying to figure out what the parameters are. Slew speed? What else?
Nothing magic, simply a bug. It should be fixed with commit 480e2db4.El Corazon wrote: Something else happened I cannot explain: In at least 2 instances, 2 luminous filter frame acquisitions were ADDED to my Capture sequence ahead of the rest of the sequence AND THE SEQUENCE FILE WAS SAVED (!).
Read More...
Hi Pit,
no, it's vice versa. Slewing for an alignment step starts with a delay and between the slew request and the slew execution there is a parallel mount status request which receives a "Tracking" as result. Since from an EKOS perspective the slew command comes before the mount status "Tracking", EKOS thinks that the slew is already finished (there is no dedicated "Slew finished" state).
Jasem and I discussed this a while ago and we came to the conclusion that it needs to be resolved on INDI side - which has not happened so far...
HTH
Wolfgang
Read More...
As far as I understand it, theoretically it could happen with all mounts. With my mount for example, I've never experienced it. But from time to time I experience it during alignment, but there it does not cause any problems other that solving needs to be restarted - which happens automatically.
Regarding "Remember Job Progress": sure, that helps, because I think at the end it's not that super important in which sequence exactly we capture the frames as long as we have the expected number of them. I personally have it always selected, because it enables shooting the same target over several nights until I have enough frames.
Cheers
Wolfgang
Read More...