Closed CTTCGeoLab closed 3 years ago
Hi, there are two options for you to ask for help:
Post your issues on StackOverflow: https://stackoverflow.com/questions/tagged/dji-sdk, the community can help you.
Report your issues to dev@dji.com, as it's our official channel for developers to request DJI Developer Support now.
For DJI Developer Support, we have the following three tiers:
Standard
This free support is available to anyone reaching out to dev@dji.com. There is no guarantee for response time.
Preferred
This support comes with Pro membership for 99 USD per year. You can purchase it on DJI Developer Website. These requests have priority over Standard ones. Starting today, Preferred questions will be replied to within 2 to 5 business days (Monday – Friday).
Premium
This one-time ticket is considered high-priority and costs 499 USD per issue. You can purchase it on DJI Developer Website after you become the Pro membership developer. Starting today, Premium questions will be replied to within 1 business day (Monday – Friday). This may include communication with DJI SDK engineers, but will not involve face-to-face interaction. Time limitations apply, and please keep in mind that one question is permitted per ticket. We will do our best to resolve your issue, but there some situations demand deeper engineering efforts.
Follow either opencv or ros version of the camera calibration process. Then get the intrinsic then generate the Q matrix. Then use the opencv reproject to 3D function.
stereo calib https://sourishghosh.com/2016/stereo-calibration-cpp-opencv/
http://wiki.ros.org/camera_calibration
Getting Q matrix https://docs.opencv.org/2.4/modules/calib3d/doc/camera_calibration_and_3d_reconstruction.html#stereorectify
Hi, I am subscribing via ROS to the following topic /dji_sdk/stereo_240p_front_depth_images corresponding to the stereo disparity map from the front-facing camera of M210 in 240x320 resolution.
The images acquired are in MONO8 format and it can be seen how the intensity values changes in function of the distance. The problem is that there is no information associated about how to interpret the pixel values in order to estimate distances to objects. There is no evident correlation between the values and the distances.
In addition the SDK does not provide a camera_info topic associated so it is not possible to generate pointclouds coming from this information.