INDI LibCamera Driver

  • Posts: 74
  • Thank you received: 11

Replied by Anjo on topic INDI LibCamera Driver

Actually... the LibCameraRaw is a LibCameraEncoder, so one could not use the LibCameraStill in favor of that and get the Video options too? Then there would only be one instance of the app running.
1 year 9 months ago #88703

Please Log in or Create an account to join the conversation.

INDI LibCamera Driver - Page 7 - INDI Forum - Results from #72
  • Posts: 119
  • Thank you received: 36

Replied by Simon on topic INDI LibCamera Driver


Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Please Log in or Create an account to join the conversation.


×

INDI Library v2.0.7 is Released (01 Apr 2024)

Bi-monthly release with minor bug fixes and improvements

Read More...
  • Posts: 119
  • Thank you received: 36

Replied by Simon on topic INDI LibCamera Driver


Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 11

Replied by Anjo on topic INDI LibCamera Driver

You don't attach to kstars, you attach to the driver code. You can debug the whole thing without kstars by using indi_setprop with the right properties.

If you follow you instructions, you can set a breakpoint in, say, Connect() and then hit the connect button in kstars (or set it to On via indi_set_prop). You debugger will stop at that breakpoint.
1 year 9 months ago #88707

Please Log in or Create an account to join the conversation.

  • Posts: 119
  • Thank you received: 36

Replied by Simon on topic INDI LibCamera Driver

Thank you ANJO.
Can you give me example of how to start exposure with indi_setprop? Probably there is domentation somewhere that I should have read? :)
1 year 9 months ago #88708

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 11

Replied by Anjo on topic INDI LibCamera Driver

Start the driver, connect and then:

pi@astrocam:~/astro/cam/libcamera-apps/build $ indi_getprop |grep EXP
LibCamera.CCD_EXPOSURE.CCD_EXPOSURE_VALUE=1
LibCamera.CCD_ABORT_EXPOSURE.ABORT=Off
LibCamera.STREAMING_EXPOSURE.STREAMING_EXPOSURE_VALUE=0.10000000000000000555
LibCamera.STREAMING_EXPOSURE.STREAMING_DIVISOR_VALUE=1
LibCamera.STREAMING_EXPOSURE.STREAMING_EXPOSURE_VALUE=0.10000000000000000555
LibCamera.STREAMING_EXPOSURE.STREAMING_DIVISOR_VALUE=1
pi@astrocam:~/astro/cam/libcamera-apps/build $ indi_setprop LibCamera.CCD_EXPOSURE.CCD_EXPOSURE_VALUE=1
Last edit: 1 year 9 months ago by Anjo.
1 year 9 months ago #88709

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 11

Replied by Anjo on topic INDI LibCamera Driver

Other neat tricks:

# connect a driver
pi@astrocam:~/astro/cam/libcamera-apps/build $ indi_setprop LibCamera.CONNECTION.CONNECT=On
# disconnect a connected driver
pi@astrocam:~/astro/cam/libcamera-apps/build $ indi_setprop LibCamera.CONNECTION.DISCONNECT=On
1 year 9 months ago #88710

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 11

Replied by Anjo on topic INDI LibCamera Driver

Basically, at this point I wouldn't worry about EKOS. The primary target is to get several exposures and aborts working which can be done via the shell. When you're debugging, you can already see you're getting the correct exposure values.

All other things, like gain or whatever should be done by putting in a command line string in INDI via some generic LIBCAMERA_OPTIONS and parse that. Then you can quily test if things work.

After that, there should be UI for the individual options, but frankly, that's pretty tiresome work. Bla create prop, Bla create propP, bla parse INewFoo. Boooring.

The only interesting part is getting the whole thing to run - and hopefully more reliable than v4l2 and raspi...
1 year 9 months ago #88711

Please Log in or Create an account to join the conversation.

  • Posts: 124
  • Thank you received: 13

Replied by Outta on topic INDI LibCamera Driver


Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Please Log in or Create an account to join the conversation.

  • Posts: 119
  • Thank you received: 36

Replied by Simon on topic INDI LibCamera Driver

Yeeeeee, OUTTA I'm glad that you solved issues with your device. I think we are making good progress here. I'm can't wait to put my HQ cam finnaly to test under clear skies and do some long exposure test! :D
1 year 9 months ago #88720

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 11

Replied by Anjo on topic INDI LibCamera Driver

There's already code in libcamera-app to create dng, though, which are to my knowledge some "standard" raw format.

Check out dng_save in libcamera-apps/image/dng.cpp.

I played around some more and in theory I guess using one app should work.

There seem to be mixups between what libcamera threads and indi threads are doing. Also, startPreview seems to get called even when you give it nopreview in the options.
1 year 9 months ago #88721

Please Log in or Create an account to join the conversation.

  • Posts: 74
  • Thank you received: 11

Replied by Anjo on topic INDI LibCamera Driver

I added your code to my fork, but it gives me the "full frame", ie 1937xsomething and not 1920x1080 as it should?

github.com/indilib/indi-3rdparty/compare...i-3rdparty:libcamera

Also, I think we should just copy over the libcamera-app code verbatim like it was done before with the includes. I just don't know how to get the top level to also build the sublevel? Then we shouldn't need to make install or anything of the libcamera-apps, potentially overwriting system stuff.

When things work, we can pull out the bits we need into the driver and remove the apps code, but I'm not sure it's worth the effort.

For now, getting repeatable exposures to work should be the first prio.
Last edit: 1 year 9 months ago by Anjo.
1 year 9 months ago #88722

Please Log in or Create an account to join the conversation.

Time to create page: 1.236 seconds