Announcement

Collapse
No announcement yet.

iCatch V35MA in Caddx Baby Turtle FPV camera - questions

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • iCatch V35MA in Caddx Baby Turtle FPV camera - questions

    Hi,
    I've ordered one of these:

    https://caddxfpv.com/products/baby-turtle-whoop-version
    (Great close up shots: https://www.youtube.com/watch?v=npMqB-Wy0sQ)

    And I just joined this forum and my first post @ https://www.goprawn.com/forum/action...r-to-superview is a little tool i wanted to share. I use it as much as I use the "start recording" feature on my other camera.

    What i would like to hopefully achieve with the new Caddx Baby Turtle is the addition of a 4:3 resolution in firmware. Something like [email protected] should be a very similar workload for the V35MA as the already featured [email protected]

    Any thoughts about this?
    It doesn't have USB. Can i retrieve the firmware and modify it?
    it's got RX and TX, UART i presume.

    (P.S. I don't know what sensor is in this camera, i am only assuming it's 4:3 like many others. If it's native 16:9 then there would be no point, i realize)

    Thank you for any comments, ideas, thoughts, info

    Cheers
    Greg

  • #2
    Originally posted by sickgreg View Post
    Can i retrieve the firmware and modify it?
    There is an SPI flash memory chip (SOIC8) located near the memory card slot. It can be dumped with a CH341A USB dongle and a clip.
    Donate here if you want to support my efforts and this site.

    Email me if you have any offers, requests or ideas.

    Comment


    • #3
      Awesome
      That gives me somewhere to start when the camera arrives (if i don't crash the drone too hard and kill it first!)
      I will post here when i make progress
      Thanks
      Greg

      Comment


      • #4
        According to the product page you linked there should be a 4:3 mode already available in the firmware "Changeable by OSD". It does not specify what resolution 4:3 mode would shoot in.


        The V35MA it is possibly paired with OV4689 (16:9) which would make it a 16:9 native sensor. But it's really hard to say without the product in hand. Could be one of the IMX sensors as well and those tend to be 4:3.

        Comment


        • #5
          Originally posted by DrekiTech View Post
          should be a 4:3 mode already available in the firmware "Changeable by OSD"
          That's right there is however it only changes the aspect ratio of the live analog output used for transmitting @ 5.8Ghz to the pilot on the ground. The modes for HD recording are 720p,1080p and 30fps,60fps.

          What is the best way to find out what sensor is being used once the product is in hand? Would it be dumping the firmware or a visual inspection or some other way?

          Comment


          • DrekiTech
            DrekiTech commented
            Editing a comment
            Easiest way is to reach out to the company and ask them directly to be honest. We can make a "best guess" based on what sample videos and photos look like. However it's just a crapshoot honestly and even if you pull the lens of most sensors aren't marked.

        • #6
          I have received the camera and installed it in my drone. Here is a sample video. The only effect added is SuperView style non-linear horizontal stretch and artifacts added by YouTube compression. It's got a pretty good field of view. No idea still if it is a 4:3 or 16:9 sensor. I will try to contact the company....

          Comment


          • petesimon
            petesimon commented
            Editing a comment
            the 1440p 60fps (same as 2.5k) is a good feature!

          • DrekiTech
            DrekiTech commented
            Editing a comment
            Looks pretty sweet. I always liked the video the V35 / 6350 processor could produce at 1080p60, good detail and reasonable colour processing.

        • #7
          the 1440p 60fps (same as 2.5k) is a good feature!
          It's good yeah but not a feature.
          The camera does 1920x1080 and the video has been non-linearly stretched to 2560x1080 (pseudo-1440p with black bars top and bottom) looking like cinematic GoPr0 SuperView using this tool: https://github.com/Niek/superview.
          The effect can also be achieved in real-time with my HLSL shader; https://github.com/sickgreg/Realtime...retch/releases in a player such as Media Player Classic https://mpc-hc.org/downloads/

          If the cam has a 4:3 sensor and is cropping to get 16:9 then I am hoping to create a custom resolution of 1600 x 1200 (or if not that then 1440 x 1080) that utilizes the whole sensor and captures more image at the top and bottom. The resulting 4:3 video can then be non-linearly stretched to 2133 x 1200 (or 1920 x 1080) to a full 16:9 video the same as the super wide video i already posted but with more image instead of black bars at the top and bottom, or in other words achieve GoPr0 SuperView on this $64 drone friendly cam. If I can't do that for whatever reason, you are right it already nice as is.

          Comment


          • #8
            There is an SPI flash memory chip (SOIC8) located near the memory card slot. It can be dumped with a CH341A USB dongle and a clip
            Finally got my CH341A programmer.

            I prepared the flash memory device by smashing it into the ground several times from the air at high speed,
            and then clipped on the programmer.

            You were right, it can be dumped. I tried in Windows and Linux and got an identical 8MB file with both methods. The chip is a KH25L6436F but was detected as MX25L6436E by flashrom (Linux) and MX25l6405D in Windows. This is the first firmware i have ever dumped. Not sure if the slight mismatch is an issue or not.

            https://1drv.ms/u/s!AstlGSqozNFRgVvp...KFYq5?e=SoOyGK

            Within the file i find reference to at least 2 image sensors; VD6869 and OV4689 which are both 4MP, 16:9, 2688x1520 sensors. Perhaps the actual sensor is one of those or neither of those. No idea. Haven't heard back from the manufacturer unsurprisingly.

            Any thoughts?
            Cheers
            Greg

            Comment


            • nutsey
              nutsey commented
              Editing a comment
              Seems like the OV4689 could be "based on" the STM VD6869. Most likely Omnivision's PureCell technology has something to do with the VD6869...
          Working...
          X