Hi Jasem,Thank you for the tips and advice, they were very helpfull.I found out the following.The V4L2 driver always crashed when logged in as “pi”. Adding another common user solved the problem, although you need to arrange the permissions and also need to run “sudo chmod 777 /dev/video0” to be able to access the camera.I have a lot of stability troubles on this Ras pi (tried multiple installs on multiple sd cards), i found out that running via an Ethernet cable instead of wifi and powering on the eq3 mount (even when not using it) seems to have solved some. (I think a power usage problem from the mount via usb on the pi adapter).With V4L2 I can change the pixel size and get it as full HD in Ekos.The whole setup works now fine (in theory) and is able to guide on e.g. Vega and holds my 600 mm super steady (unfortunately there is nothing to photograph there ). I have tried to add the canon 6D (main imaging camera) on Indi before but it did not work straight away and I figured to keep that on manual, as I want to save on camera SD anyways, so the only gain would be focus adjustment via Indi (using a Tamron 150-600 G2).However the main issue remains the lack of stars in the guide scope. I found that the V4L2 seems to only mount it as an 8 bit sensor (and actually I doubt the Bresser can handle more? I can’t seem to find it online.) Also the longest exposure time seems to be around 74 ms (due to the webcam nature, or is this a driver issue?). I think longer exposure times just stacks zeros resulting in a 0 for all pixels but the brightest ones, that with auto stretching, end up as 255. (p.s. autostretching does not help with determining optimal focus)All in all I am doubting I should buy another guide scope sensor that can handle longer native exposures, does anybody know if this would solve the problem? Which budget sensor would you advice? I need to have enough guide stars around the nice areas (m31, the popular nebulas and Pleiades) on a 240mm/60mm guide scope.Thanks in advance. EPT

Read More...