×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Can't change ISO of indi_v4l2_ccd device in EKOS

  • Posts: 7
  • Thank you received: 0
I actually tested it. What i have done was downloaded it from your fork. And installed it afterwards. On my virtual machine and on the raspberry pi. But I have not found any new options for the ISO Setting.

I have already opened an issue about the problem on github: github.com/indilib/indi/issues/173

If I should try something else just tell me or if you need remote access to an raspberry pi with atached camera - i think that would be manageable.
Last edit: 7 years 1 week ago by Dominik Laa.
7 years 1 week ago #15148

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

  • Posts: 226
  • Thank you received: 88
Are the Menu items listed in the driver capabilities as you show in your preceding post ?
They should be there as 'Integer Menu items'.
7 years 1 week ago #15158

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

  • Posts: 7
  • Thank you received: 0
Yes they are.
iso_sensitivity (intmenu): min=0 max=4 default=0 value=0
                                0: 0 (0x0)
                                1: 100000 (0x186a0)
                                2: 200000 (0x30d40)
                                3: 400000 (0x61a80)
                                4: 800000 (0xc3500)
           iso_sensitivity_auto (menu)   : min=0 max=1 default=1 value=1
                                0: Manual
                                1: Auto

I also attached there KStars Log-File.
7 years 1 week ago #15163
Attachments:

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

  • Posts: 226
  • Thank you received: 88
Ok I made a mistake in the integer menu item names, could you try again ?
And also have a look at the driver output as you did in your preceding post (when you circle in red its output).
Thanks.
7 years 1 week ago #15164

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

  • Posts: 7
  • Thank you received: 0
I have reinstalled it on the VM and on the Raspberry Pi but the same problem either - can't see any new options to controle the ISO. I have also attached the log file for the driver (on the raspberry pi).
7 years 1 week ago #15165
Attachments:

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

  • Posts: 226
  • Thank you received: 88
Well, au temps pour moi, V4L2 control types are defined in an enum, so I have to test the kernel version, not just use #ifdef.
I've made the corrections, so I hope that it would work now. At least show the items in the capability list.

Thanks again for testing.
Jean-Luc.
7 years 1 week ago #15168

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

  • Posts: 7
  • Thank you received: 0
With that the option is here - see also the Screenshot that I have attached.

So first I have to say thank you at least 1000 times :)

There is just one more issure: The maximum exposure time seems to be 10000 (may be 1 second) but the Rasperry Pi Camera supports up to 6 seconds. On the first page I can enter different values for "Expose" but they seem to make no real change. On The V4L2 Control Tab is also a value where you can enter times up to 10 000 (see also my second attached screenshot). That's acutally pretty bad because even ISO 800 and 1 Second may not be enough for some needs of Astronomy.

That value may come directly from V4L2 because that L readout gives me also:
exposure_time_absolute (int) : min=1 max=10000 step=1 default=1000 value=10000

There was also a thread about the problem (but only one entry) which also had the idea that the problem may be V4L2 related (what might be pretty bad I thing).

Thanks,
Dominik

Ps: Thanks for developing the solution !
Last edit: 7 years 1 week ago by Dominik Laa. Reason: added attachments
7 years 1 week ago #15174
Attachments:

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

  • Posts: 226
  • Thank you received: 88
Nice, at least it displays something ;-) More seriously did you check if those intmenu controls are effectively working ?
I would like to be sure before making a pull request.
Concerning the maximum exposure time, it is effectively set in the v4l2 port of the bcm2835 driver :
	V4L2_CID_EXPOSURE_ABSOLUTE, MMAL_CONTROL_TYPE_STD,
		/* Units of 100usecs */
              1, 1*1000*10, 100*10, 1, NULL,
Values should be min, max, default, step on the last line here, so you may change the max value to 6*1000*10 and recompile a kernel.
Now I wonder if this max value is not only available in a still picture mode.
The Expose control in the Main control tab should normally set the v4l2 Auto Exposure mode to manual, and the v4l2 Exposure time absolute to the one you entered. So that should work for values less than the v4l2 max (1 second).

Thanks again for testing,
Jean-Luc.
The following user(s) said Thank You: Jasem Mutlaq, Dominik Laa
7 years 1 week ago #15180

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

  • Posts: 7
  • Thank you received: 0
I will test the values tomorrow and give you feedback afterwards. You are right the Max Value of 6 Seconds seems to be only available in the still mode. The video mode seems to need at least 1 second. But I may try to change the value in the bcm driver - because i really need at least 3 seconds to be able to see any stars for autoguiding with my set up.

Edit: It will take little bit longer until I can test it because of personal reasons. As soon as possible I will test it. Sry !
Last edit: 7 years 1 week ago by Dominik Laa. Reason: Update
7 years 1 week ago #15182

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

Time to create page: 3.978 seconds