Hello,

I own a OAK-D Pro PoE with Wide FOV.

I'm noticing a bad depth accuracy. Indeed, the camera measures 3 meters while the real distance is 3.5 meters. The camera is placed on the ceiling and frames a plain floor. 3.5 meters is the central vertical distance.

I used both AlphaScaling 1 and 0 without any difference.

Thanks in advance

  • jakaskerl replied to this.
  • Hi Jaka,

     

    Thaanks! It turns out all I had to do was press the spacebar to continue (!). Wouldn't it be helpful to have a message saying so? With the video, I thought the person was just closing the window in the interface, and the tutorial doesn't mention it. The script itself says to press the spacebar to continue in the first step, but (maybe it's just me!) I didn’t think to do that after the step of taking the images. It’s not just after the first pop-up; you need to press the spacebar multiple times until the calibration is fully done. Also, I assume it's set up this way so you can review and validate each pop-up before continuing, so wouldn’t it be nice if the tutorial explained that process too—like what to look for during each step?

     

    Thanks again.

    LcicC The camera is placed on the ceiling and frames a plain floor.

    How does the depth map look? Is it uniform or very noisy? If the floor is too texture-less the stereo algorithm might have some problems.

    Perhaps the calibration is bad. Could you give me the MXID of the device, I can check factory calibration. If that is the case, i'd recommend you recalibrate the device. https://docs.luxonis.com/hardware/platform/depth/calibration/

    Thanks,
    Jaka

    5 days later

    Hello,

    This is the MxId: 1844301041EFE9F400

    Thank you in advance

      When following such tutorial, I get the error "Failed to detect markers on the image" in the calibration step. Indeed the camera does not recognize the grid of squares as expected: see attached image.

      The same happens when I use a 28" screen to display the Charuco board, with no particular brightness condition (neither saturated or with direct light).

      Any idea what's going on?

      14 days later

      LcicC
      Sorry, I must have missed the post...

      The aruco markers are not detected.
      Which repo version are you using, which depthai version?
      What command do you use to call the calibrate.py?

      Thanks,
      Jaka

        11 days later

        Hi jakaskerl

         

        Repo version: the lastest from GitHub - luxonis/depthai: DepthAI Python API utilities, examples, and tutorials., I guess its v3.6.1

        Depthai version: also the lastest,  2.28.0.0

        Command to call calibrate: python3 calibrate.py -s 3.3 –board OAK-D-PRO-W-POE -nx 7 -ny 4

        Charuco board: the 28” screen one as per link in the tutorial Calibration (luxonis.com)

         

        I also tried with an older version of depthai (2.24), different cameras, and printing the charuco board instead of displaying it on the screen.

          LcicC
          Your board is 13 by 7 not 7 by 4.. Also, it looks like the board is very "wavy" and is terrible if you want to calibrate for camera distortions. Make sure it is as flat as you can possibly make it.

          Thanks,
          Jaka

          Using 28” screen, and command python3 calibrate.py -s 3.3 –board OAK-D-POE-W-97 -nx 15 -ny 8, it looks alright but then the calibrate.py gets stuck right after the three “INTRINSIC CALIBRATIONS”.

            LcicC
            Is the charuco board actually 15x8? I think a window should pop up to check the epipolar error.

            Thanks,
            Jaka

            Yes, the board is 15x8 (not the same of the first image). My bad, there is the pop window and then it gets stuck.

              Hi Jaka,

              I have waited both with the window opened, and after having closed the window. It gets stuck.

              I’m using command python3 calibrate.py -s 3.6 –board OAK-D-POE-W-97 -nx 15 -ny 8, with charuco board for 28” screen and depthai version 2.28.0.0.

              getEepromData() gives product name OAK-D-W-POE-97 and board name NG9097.

                LcicC
                Ok I will take a look. I'll let you know if I can reproduce the issue.

                Thanks,
                Jaka

                Hi @LcicC
                I tested the script and got no issues.

                • which window is the one that the script gets stuck on?
                • try closing it with spacebar; apparently some force close of windows bricks python...
                • Can you provide any images of right before the script dies and right after?

                Thanks,
                Jaka

                Hi Jaka,

                 

                Thaanks! It turns out all I had to do was press the spacebar to continue (!). Wouldn't it be helpful to have a message saying so? With the video, I thought the person was just closing the window in the interface, and the tutorial doesn't mention it. The script itself says to press the spacebar to continue in the first step, but (maybe it's just me!) I didn’t think to do that after the step of taking the images. It’s not just after the first pop-up; you need to press the spacebar multiple times until the calibration is fully done. Also, I assume it's set up this way so you can review and validate each pop-up before continuing, so wouldn’t it be nice if the tutorial explained that process too—like what to look for during each step?

                 

                Thanks again.