I have the same devices (WATEC + stk1160) and I can successfully open the stream in ekos using directly V4L2 CCD.
However, I cannot take single captures (my goal is to perform astrometry), even when selecting stack: Additive option.
It says: "Absolute exposure duration control is undefined and tacking is not supported".
Did you manage to make it work on your side?
Thank you and clear skies
I tried again tonight, and it seems in my case, it was just due to bad polar alignment.
Tonight I am getting the same weird behavior as you described.
The east calibration is using the wrong direction, using both st4 or direct pulses, using phd guiding or ekos internal guider.
Sending manual orders works fine.
I changed the gemini2 battery today because it was depleted.
Still have no clue on your side?
I connected Ekos to the AZ GTi mount successfully, but the goto actions seem irrelevant.
For example, when moving only in altitude, it also moves in azimuth (is it using equatorial mode?).
When connecting with the Android app, it does say Alt mode.
Thank you and clear skies!
On my side, I am using the notifications to launch a small java program playing a mp3 file.
This warns me when the sequence stopped, and I can snooze it by closing the app (which you cannot do if you run the sound directly).
However, I did not find the appropriate event to use.
For example, when I stop the sequence manually, the alarm is triggered.
dmsummers wrote: @Alex, If you use a Pegasus PowerBox, or V2, or any other sensor that reports temperature via "WEATHER_TEMPERATURE", (i.e. if you see temperature reported in the dome tab), then you will likely be able to use the autofocus delta-T feature that florian mentions.
If your focus issue is indeed due to the temperature, I think it could be solved by the feature I recently developed : trigger autofocus on temperature change. It uses the focuser probe, if available, to compare the last focus temperature to the current temperature, and triggers the autofocus in case it reaches the specified limit.
The feature should be delivered in the next release, but you can test it with the nightly.
How could it be possible to have drift if you are guiding?
I followed the instructions from here:
Here is the merge request:
How do I submit it to gitlab?
In focus.cpp, method Focus::setAutoFocusResult, I always get a null pointer when trying to access the Temperature property (although the logs show the temperature, and it is displayed in the INDI control panel):
INDI::Property * np = currentFocuser->getProperty("TemperatureNP");
I managed to run the debugger, and of course we get a null pointer for the property "TemperatureNP".
I also tried to understand the indi driver code, what the difference between TemperatureN and TemperatureNP is. But I think I would need help here.