- 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...
Mmmm, interesting. So there's only a minor uplift from RPi4/8G to RPi5/8G.
I would say that there is something less than ideal going on with your ASI2600MC though. I run the same camera on a RPi4/8G and I see 120fps @ 400x400 in FireCapture and a typical download time for 6428x4176 in KStars/Ekos of around 0.6sec.
I have the camera connected through a USB3 hub which plugs into one of the RPi's USB3 ports and the flash stick storage directly in the other USB3 port of the RPi. If you have the camera and storage sharing a single USB3 port of the RPi (eg. both connected to a hub) that might go some way to explaining it. Of course, if there is some USB bandwidth problem going on, your throughput on the other cameras may be similarly hobbled but I have no comparison for those.
Read More...
You only need to disconnect your imaging camera. Mount, focuser & filter wheel can be simultaneously connected in FireCapture. Obviously if you ask both Ekos and FireCapture to perform conflicting actions it will get in a mess - ie don't use Ekos guiding and FireCapture guiding at the same time.
Personally I don't have a filter wheel or auto focuser but for guiding I can select my INDI connected mount in FireCapture, I assume the other devices work in a similar manner.
I'd be interested to know what fps you get from which camera with what resolution when using the RPi 5.
Read More...