Did you try to start the indiserver and driver from the command line e.g. "indiserver -vv indi-sv305"?
There is an other topic on INDI Driver for SVBONY cameras, may be it could help
indilib.org/forum/wish-list/6373-indi-dr...html?start=180#62323
Read More...
My ASI120 don't work properly with PRI4 due to USB interface issues and may be it is the same with ASI22.
I get major time delays or even timeout errors if I try to read out the ASI120 with RPI4. No problems with RPI3.
Read More...
In my setup ASI120 and RPI4 B don't work properly together (USB issues) and that would explain the difference.
With PRI3 I didn't have this problems. Please check is you get large delays or even timeout errors from the guiding camera. If yes, USB interface is probably the root cause. In my setup ASI120-S works properly with RPI4 B.
Read More...
Good afternoon,
I wonder if the unit of HFR in the Ekos "Focus Modul" or "Fits Viewer" is pixel or arcsec.
Many thanks
Aloys
Read More...
Hy,
Many thanks for this information and the link.
I guess I have to spend some time to get a deeper understanding of SEP and the meaning of the different models and parameters.
Arnold
Read More...
I'm trying to understand the meaning of the sky parameter in the EKOS analysis module. I guess it could be mag/arcsec^2 but sometimes I got some doubts. Are there any information available how this parameter is calculated without digging into the sources?
Many thanks.
Read More...
When I use my ASI EAF focuser with INDI the focuser value "absolute position" is decreasing with each movement of the focuser regardless of the movement direction. As soon as the value "zero" is reached no movement is possible without new initialisation of the absolute position. I guess that is not intended.
Read More...
When I use my ASI EAF focuser with INDI the absolute position in the driver is decreasing with each movement of the focuser regardless of the moving direction. As soon as the value zero is reached no movement is possible without new initialisation. I guess that is not intended.
Read More...
To my knowledge this feature is under test and shall be incorporated in version 3.5.2 of kstars.
See "indilib.org/forum/general/8602-new-polar...me-and-features.html" to follow discussion.
Read More...
If I check the "Local Sidereal Time" in the EQMOD TAP "Site Management" it seems to be different from other sources with same input data. "Julian Date", "UTC" and "Longitude" seems to be correct but "Local Sidereal Time" shows a deviation of "2x impact of Longitude". To me it looks like a signature issue of the "Longitude" impact. Could please someone verify my observation?
Read More...
Integral gain of zero is a good starting point as high integral gain may cause stability problems. Min and max pulse should not be that critical. Good starting points are min=100 ms and max=5000ms.
Read More...
The impact of symbols is very strong but there are more parameters with impact on binary size (see e.g. interrupt.memfault.com/blog/best-firmware-size-tools).
Read More...
The different binary code size is most probably caused by the symbols in your code. If you "strip" your binary, it will be close to the "original Stellarmate" size.
Read More...