ModalAI Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Starling 2: TOF sensor not recognized by VOXL Portal

    Starling & Starling 2
    3
    22
    478
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Alex KushleyevA
      Alex Kushleyev ModalAI Team @Hector Gutierrez
      last edited by

      @Hector-Gutierrez ,
      OK, so it looks like that the 4 detected cameras are actually streaming data.

      I am not sure why voxl-portal is not showing any cameras. When you access the voxl-portal via browser, do you see the actual portal (with green menu bar at the top), but no cameras are listed in the Cameras section?

      How are you connected to the drone? (wifi, adb, etc).

      Regarding the TOF sensor, since voxl-camera-server -l did not show that the TOF sensor is detected, the stream is not available.

      Please double check that com.qti.sensormodule.irs2975c* file is in /usr/lib/camera/ directory - please provide the exact name or let me know if it's missing.

      Also, can you please take a picture of your cameras plugged into the M0173 camera front end? I just want to make sure the TOF sensor is plugged in correctly.

      Alex

      Hector GutierrezH 1 Reply Last reply Reply Quote 0
      • Hector GutierrezH
        Hector Gutierrez @Alex Kushleyev
        last edited by

        @Alex-Kushleyev
        Hi Alex, I disassembled and reassembled the camera board and now I get 4 cameras in VOXL Portal ! I did reconnect the ToF sensor as well to the camera board, it seems properly connected.
        The cameras working well are hires_large_color, and all three tracking cameras. I still dont see the ToF sensor , and the view of the hires camera is blurry (out of focus). The hires camera was recently replaced, so how to get it into focus is another question.
        I listed the files on /usr/lib/camera and found this file: com.qti.sensormodule.irs2975c_3.bin
        So now we are down to the ToF sensor (and to put the hires camera in focus). Let me know what to try next !
        thanks, Hector

        Alex KushleyevA Hector GutierrezH 2 Replies Last reply Reply Quote 0
        • Alex KushleyevA
          Alex Kushleyev ModalAI Team @Hector Gutierrez
          last edited by

          @Hector-Gutierrez , in order to focus the hires camera (I am assuming IMX412), you can twist the lens in the M12 lens holder. Normally we do focus the hires cameras to a norminal focus distance, but maybe you had one from earlier batch which was not focused. Also, focus of the camera depends on the application, so it is recommended for users to double check and correct the focus for their needs. If there is some sealant on the threads, it is not permanent and can be removed using tweezers - loosening it up a bit should allow you to twist the lens inside the holder.

          Regarding the PMD TOF, not sure yet. Has it worked before?

          Alex

          1 Reply Last reply Reply Quote 0
          • Hector GutierrezH
            Hector Gutierrez @Hector Gutierrez
            last edited by

            @Hector-Gutierrez
            Hi Alex - As you suggested, the focus issue was resolved by twisting the lens until good focus at 3 m. was achieved.
            The TOF sensor remains a problem. I've tried detaching and reconnecting its cable (on both ends) but no luck so far.
            Both VOXL Portal and voxl-camera-server -l only see 4 cameras.
            We didnt use the TOF sensor before so I didnt notice if it was working previously or not.
            Please let me know what to try next - thanks, Hector

            Alex KushleyevA 1 Reply Last reply Reply Quote 0
            • Alex KushleyevA
              Alex Kushleyev ModalAI Team @Hector Gutierrez
              last edited by

              @Hector-Gutierrez , can you please send a picture of the TOF sensor connected to M0173? Just to make sure the connections are correct.

              Hector GutierrezH 1 Reply Last reply Reply Quote 0
              • Hector GutierrezH
                Hector Gutierrez @Alex Kushleyev
                last edited by

                @Alex-Kushleyev
                Hi Alex - attached are some pictures of the connection. Something odd is happening. The connector engages its socket in two different locations relative to the hole for the screw. In the centered location (where it should be!) the TOF sensor causes a power short and the drone wont boot (see picture with red LED). In the off-center location there is no short and the drone boots, but I only get 4 cameras and the TOF is not visible.
                ![centered.jpg](Request Entity Too Large) ![off-center1.jpg](Request Entity Too Large) ![off-center2.jpg](Request Entity Too Large) ![power-short.jpg](Request Entity Too Large)

                Hector GutierrezH 1 Reply Last reply Reply Quote 0
                • Hector GutierrezH
                  Hector Gutierrez @Hector Gutierrez
                  last edited by

                  @Hector-Gutierrez
                  Download link for the pictures in case they did not attach to previous message:
                  https://quickconnect.to/asapstorage/d/s/13iMi9oRZUxhkQYoW2DCHtZ7nI9HgYJx/bj3PLF8EXd5pKdKgwphVqcbD7VaaMBQX-V7WAgk58WAw

                  Hector GutierrezH 1 Reply Last reply Reply Quote 0
                  • Hector GutierrezH
                    Hector Gutierrez @Hector Gutierrez
                    last edited by

                    @Hector-Gutierrez
                    Update from my previous post. I install the TOF connector in the centered location and fully attach the screws (including the one that secures the TOF ribbon cable). There is no short, the drone start normally, and I get 4 cameras on VOXL portal, but no TOF. Also voxl-camera-server -l only see 4 cameras. So TOF connection is definitely Ok, but sensor not present.

                    Alex KushleyevA 1 Reply Last reply Reply Quote 0
                    • Alex KushleyevA
                      Alex Kushleyev ModalAI Team @Hector Gutierrez
                      last edited by

                      @Hector-Gutierrez , I am sorry, i was not able to access the image you shared. Can you please just resize / crop the image so that it fits into the forum? Just please make sure the details are still easy to see.

                      Thank you!

                      Alex

                      Hector GutierrezH 2 Replies Last reply Reply Quote 0
                      • Hector GutierrezH
                        Hector Gutierrez @Alex Kushleyev
                        last edited by

                        @Alex-Kushleyev
                        Hi Alex - attached are the pictures. centered.jpg off-center1.jpg

                        After installing the TOF connector in the centered location and fully attach all the screws (including the one that secures the TOF ribbon cable), there is no short and the drone starts normally. I get 4 cameras on VOXL portal, but no TOF. Also voxl-camera-server -l only see 4 cameras. So TOF connection seems definitely Ok, but sensor not present. Seems to me like a bad TOF sensor - let me know your thoughts.

                        Hector GutierrezH 1 Reply Last reply Reply Quote 0
                        • Hector GutierrezH
                          Hector Gutierrez @Hector Gutierrez
                          last edited by

                          @Hector-Gutierrez Clarification on the pictures. The top picture is the centered position of the TOF ribbon cable. The bottom picture can be disregarded. The connection is done on the centered position (top picture). Thanks.

                          1 Reply Last reply Reply Quote 0
                          • Hector GutierrezH
                            Hector Gutierrez @Alex Kushleyev
                            last edited by

                            @Alex-Kushleyev - Any updates on this thread ? Let me know if there is anything else I could try or if you consider this a hardware problem with the PMD sensor itself. Thanks, Hector

                            Alex KushleyevA 1 Reply Last reply Reply Quote 0
                            • Alex KushleyevA
                              Alex Kushleyev ModalAI Team @Hector Gutierrez
                              last edited by

                              @Hector-Gutierrez , sorry about the delay.. Before submitting RMA (i will provide instructions), can you please share the output of dmesg after you run voxl-camera-server -l ? this will let me confirm that there is an attempt to ping the TOF sensor and it fails. You could save the output of dmesg into a text file and share it or paste it here.

                              A successful dmesg output should look something like this (this is from a Starling 2 Max), which has an extra IMX412 camera:

                              [ 1712.362675] CAM_ERR: CAM-MEM: cam_mem_mgr_create_debug_fs: 126 failed to create dentry
                              [ 1712.383711] CAM_INFO: CAM-HFI: cam_hfi_init: 878 Init IO1 : [0x10c00000 0xcf300000] IO2 [0xe0200000 0x1ed00000]
                              [ 1712.393864] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079,OEM_IMAGE_VERSION_STRING=CRM,BUILD_TIME: Oct 17 2019 05:49:19,CACHE_ENABLED at icphostinterface.c:636 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM
                              [ 1712.393868] CAM_INFO: CAM-ICP: cam_icp_mgr_process_dbg_buf: 2572 FW_DBG:CICP_FW_E : HFI  :ELF variant: CACHE-ENABLED:T480:API_V2:USE_CDM_1_1: , API version: 0x2000049 at icphostinterface.c:637 QC_IMAGE_VERSION_STRING=CICP.FW.1.0-00079 OEM_IMAGE_VERSION_STRING=CRM
                              [ 1712.393916] CAM_INFO: CAM-ICP: cam_icp_mgr_hw_open: 3879 FW download done successfully
                              [ 1712.470777] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.58
                              [ 1712.472096] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.56
                              [ 1712.474369] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.60
                              [ 1712.474408] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Linked as a consumer to regulator.79
                              [ 1712.498846] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:0,slave_addr:0x30,sensor_id:0x356
                              [ 1712.498997] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.79
                              [ 1712.502731] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.60
                              [ 1712.502868] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.56
                              [ 1712.502981] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor0: Dropping the link to regulator.58
                              [ 1712.526976] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.58
                              [ 1712.527116] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.60
                              [ 1712.527175] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.56
                              [ 1712.527326] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Linked as a consumer to regulator.79
                              [ 1712.541852] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:1,slave_addr:0x34,sensor_id:0x577
                              [ 1712.541967] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.79
                              [ 1712.543257] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.56
                              [ 1712.543316] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.60
                              [ 1712.543392] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor1: Dropping the link to regulator.58
                              [ 1712.561608] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.60
                              [ 1712.563718] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.59
                              [ 1712.565875] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.55
                              [ 1712.567770] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Linked as a consumer to regulator.79
                              [ 1712.575483] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x7a,sensor_id:0x2975
                              [ 1712.577616] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.79
                              [ 1712.579717] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.55
                              [ 1712.579758] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.60
                              [ 1712.579812] qcom,camera ac50000.qcom,cci:qcom,cam-sensor3: Dropping the link to regulator.59
                              [ 1712.604128] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.58
                              [ 1712.606318] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.56
                              [ 1712.608394] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.60
                              [ 1712.608473] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Linked as a consumer to regulator.79
                              [ 1712.631999] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:6,slave_addr:0x30,sensor_id:0x356
                              [ 1712.632517] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.79
                              [ 1712.636492] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.60
                              [ 1712.636595] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.56
                              [ 1712.636686] qcom,camera ac4f000.qcom,cci:qcom,cam-sensor6: Dropping the link to regulator.58
                              [ 1712.662182] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.59
                              [ 1712.662338] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.60
                              [ 1712.662399] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.56
                              [ 1712.662543] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Linked as a consumer to regulator.79
                              [ 1712.677605] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:2,slave_addr:0x34,sensor_id:0x577
                              [ 1712.677728] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.79
                              [ 1712.679699] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.56
                              [ 1712.679736] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.60
                              [ 1712.679789] qcom,camera ac50000.qcom,cci:qcom,cam-sensor2: Dropping the link to regulator.59
                              [ 1712.739998] CAM_WARN: CAM-CRM: cam_req_mgr_close: 160 release invoked associated userspace process has died
                              

                              Specifically, the following line says that the TOF sensor has been probed successfully:

                              [ 1712.575483] CAM_INFO: CAM-SENSOR: cam_sensor_driver_cmd: 918 Probe success,slot:3,slave_addr:0x7a,sensor_id:0x2975
                              

                              If the probe fails, you would see some CCI errors. If you do not see anything related to slave address 0x7a , the the sensor is not being probed and the issue is on the SW configuration side, which we can investigate further.

                              Alex

                              1 Reply Last reply Reply Quote 0
                              • First post
                                Last post
                              Powered by NodeBB | Contributors