×

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

Bi-monthly release with minor bug fixes and improvements

indi_toupcam_ccd arm32 wrong resolution

  • Posts: 33
  • Thank you received: 0
Hello. I having a RisingCam IMX224 that uses the indi_toupcam_ccd driver on a raspberry pi.

I've notice on indi versions 1.9.2 and 1.9.4 the maximum resolution is 640x480 even though it should be 1280x960. I also can't manually set it to the higher version it errors with it being invalid.

If I use 1.8.9 I get the full resolution (sorry I have not tried other versions besides these three).

I do not see this issue on amd64.

This happens if I build it myself, or if I use astroberry binaries for raspberry pi. Has anyone else noticed this or found a solution?
 
Last edit: 2 years 1 month ago by Russell Valentine.
2 years 1 month ago #80218

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

  • Posts: 33
  • Thank you received: 0
I also did try different libtoup debs. I was using libtoupcam_1.48.0-1_armhf.deb with 1.8.9 and libtoupcam_1.50.1_armhf.deb with 1.9.4

However extracting the .so file from 1.48.0 deb and copy it over onto 1.50.1 made no change.
2 years 1 month ago #80219

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

If the issue in the SDK itself, can you please communicate directly with Toupcam or the manufacturer of your camera for support?
2 years 1 month ago #80221

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

  • Posts: 33
  • Thank you received: 0
I currently suspect it isn't with the SDK itself. Sorry if my messages were confusing. My second message was trying to say that I swapped out the SDK and the issued remained. While this doesn't rule out a problem in the SDK it does seem to indicate that it was something that changed in indi that is causing this.

I am up for trying to debug this some more but would need some guidance on where to start.

This may or may not be helpful but the output of the lower resolution image still has color in raw format, so whatever is causing it to be scaled keeps the bayer pattern.
2 years 1 month ago #80237

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

Aren't the resolution selections available in the Control tab?
2 years 1 month ago #80250

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

  • Posts: 33
  • Thank you received: 0
In Image Settings -> Frame?

If I try to change it to 1280x960 it says invalid width requested.
2 years 1 month ago #80285

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

  • Posts: 33
  • Thank you received: 0
Okay in controls-> Resolution.

And I see the default for arm vs non-arm had changed since 1.8.9:

<pre>
+ // In case there is NO previous resolution set
+ // then select the LOWER resolution on arm architecture
+ // since this has less chance of failure. If the user explicitly selects any resolution
+ // it would be saved in the config and this will not apply.
+#if defined(__arm__) || defined (__aarch64__)
+ if (m_ConfigResolutionIndex == -1)
+ finalResolutionIndex = ResolutionSP.nsp - 1;
</pre>

Just confused myself real hard since I had a both script thas was getting the lower resolution and ekos was getting lower resolution, but not when on amd64. Really helped me see my error when I did git diff against 1.8.9 and saw default just for arm had changed.

Sorry to waste your time. Thank you for the help.
Last edit: 2 years 1 month ago by Russell Valentine. Reason: formatting
2 years 1 month ago #80287

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

Time to create page: 0.567 seconds