I didn't use Capture sequence scripts. All the KStars interaction for this is via DBus calls & signals. All the Siril interaction is via the siril_commmand.in & siril_command.out pipes.
What I do is test to make sure the Capture job queue is empty and then call the Capture start function. This creates a one frame preview job using the current settings (the same as clicking the Capture start button with no jobs in the table. Once the frame is received I pass it to Siril and watch for the stacked result. When that's ready I pass it back to Ekos for display and start Capture again. Repeat until stopped by the user.
If you want to go a similar route, learning about DBus is a good start. As well as reading around the subject I'd recommend the D-Feet and Bustle applications for manually interacting with and monitoring the DBus interfaces.
Read More...
Hi,
I had a similar thought and have made good progress on implementing it. In my implementation the live stacked image is returned to Ekos and shown in the image preview window on the Manager tab. This is almost ready for release but for one thing - I found a bug in Siril that makes it's piped command handling flakey. I've found the bug and submitted a fix to the Siril team but it's still awaiting review and then the next maintenence release of Siril (1.2.2).
Read More...
- Any software author can make rules for their requirements. So you end up with multiple applications/drivers trying to claim the same device.
- The rules are processed in numeric order.
- Higher numbers "win" by overwriting matching rules in lower numbers. There's also priority from where the rules are stored. See www.freedesktop.org/software/systemd/man/latest/udev.html
- Mode=0666 is setting permissions. 6 means r/w, there are three of them for owner, group & all users. Ignore the leading 0 for most purposes.
- Don't know
- Don't know
Read More...
The . in front of indi makes it a hidden directory in Linux. To see it in your file browser you'll need to find and select the option for "Show hidden files and directories" (or some similar name). You can also try Ctrl-H as a shortcut for this.
Read More...
Building from source is quite easy thanks to nou's scripts, see indilib.org/forum/development/14271-astr...indi-and-kstars.html
It does take a few hours on a Pi4 though.
Read More...
A very capable DIY solution is the Observatory Control System (OCS) from the author of OnStep. See onstep.groups.io/g/onstep-ocs/wiki.
There is an INDI driver available (that I wrote) but it's still in a beta state. I believe it's complete but there hasn't been a lot of real works testing yet.
Read More...
Sorry, I don't know enough to directly advise you on this. I also don't have relevant equipment for motivation or testing.
I've found it easiest to find an INDI driver of similar functionality and read through the source to try to understand how it's been done before. You can also refer to the
INDI developer manual
Read More...
"I'm a little confused because I don't found the Indi control panel."
INDI doesn't have a GUI in itself. The client draws it based on the drivers declared properties.
Read More...
Probably gpsd grabbing the port, it comes with very wide reaching udev rules that capture just about any serial - USB convertor.
Read More...
Oh right, that looks like an on camera dark frame subtraction to cancel read noise. I'm surprised they bothered on a IMX533 camera as the read noise is very low anyway. Personally I wouldn't bother with the LRN mode for planetary or DSO (where I'd be using darks during the stacking/calibration process anyway).
Read More...
Yes, the ZWO cameras do support the FirecCapture 'High Speed' option that turns the ADC's down to 8-bit and this is what I measured as it's generally recommended for planetary imaging where we're typically not stretching the signal aggressively as we often do with DSO imaging. However the 0.6sec full res download in KStars/Ekos is at the full 16-bit so there's still a large difference there.
Read More...