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?
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.
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 2 months ago by Russell Valentine. Reason: formatting