When ever i go to adjust any of the properties in the indi control panel i get the following errors, but this only started to happen the last couple of days, before that it was working perfectly.
2019-01-15T19:59:03: Driver indi_v4l2_ccd: indi_v4l2_ccd dispatch error: Property Image Adjustments is not defined in V4L2 CCD.
2019-01-15T20:00:18: Driver indi_v4l2_ccd: indi_v4l2_ccd dispatch error: Property CCD_FRAME is not defined in V4L2 CCD.
2019-01-15T20:00:23: Driver indi_v4l2_ccd: indi_v4l2_ccd dispatch error: Property CCD_BINNING is not defined in V4L2 CCD.
2019-01-15T20:00:28: Driver indi_v4l2_ccd: indi_v4l2_ccd dispatch error: Property CCD_COMPRESSION is not defined in V4L2 CCD.
2019-01-15T20:00:32: Driver indi_v4l2_ccd: indi_v4l2_ccd dispatch error: Property CCD_FRAME_TYPE is not defined in V4L2 CCD.
2019-01-15T20:00:33: Driver indi_v4l2_ccd: indi_v4l2_ccd dispatch error: Property CCD_FRAME_RESET is not defined in V4L2 CCD.
2019-01-15T20:00:35: Driver indi_v4l2_ccd: indi_v4l2_ccd dispatch error: Property CCD_COLOR_SPACE is not defined in V4L2 CCD.
I just tested the current head GIT V4L2 driver with the web-camera of my laptop and it seemed to work fine so hopefully it's just a dodgy build in the PPA, the log looks a bit like the driver crashed, there might be more info in the indiserver output.
Thanks, yes it crashes and is restarted. If you can run it under gdb (instructions are somewhere on this forum, can't browse with this phone unfortunately) that would give where the crash happens. It does get pretty far in initialization though.
I've had some instability with V4L2 sometimes. (Before and after this patch) I haven't tracked it down.
Nothing the patch does should have caused that unless there's an assumption about pixel size. (Which wouldn't be the problem in the logs above, since it went with the default. So as far as the code, the only difference is the message. )
I appreciate your work, and just pushed a few more, that I don't know if they work, and added a tested option, so that things can be added, and if they work, they can be marked as tested.
INDI as far as I know doesn't have an easy way to get that information, or any surveys. I know I am ambivalent on them, but maybe add an option in Kstars to generate a report of data that could be posted somewhere could be something looked at? Because sometimes it's hard to tell if people are using something or if it was working years ago, but got broken. (Any way it's done, it's imperfect.)
It seems the reported name in the post above is the same for several generic camera boards using the Sony IMX290 color version. I have a version purchased on Aliexpress with a product name of "2mp Camera module"
Reported Name In Indi using V4l2 driver: USB 2.0 Camera: USB Camera Common Name: Generic USB Camera Module IMX290
Pixel size 2.9um x 2.9um
Using the INDI webcam driver, there is no access to adjust this cameras settings (brightness, contrast, gamma, gain, etc.) but will give a looping feed in Ekos for guiding. If selecting V4L2 CCD the settings are available but there is no image when trying to use it under Ekos.
I am relatively new here, but my driver spat out this message and I am here to say that it works!
2020-12-27T21:48:42: [INFO] Please report that the camera worked: Name: NexImage 10/NexImage 10 Detected and working, to bit.ly/2S1Vxjq
2020-12-27T21:48:42: [INFO] Setting pixel size correctly for NexImage 10
I am not sure what information you will need, but its the first time I am seeing this mesage, and yet not the first time it has been plugged in.