MSDK 5.3 and Mini 3 Pro Obstacle Data Limitation

Completed
Follow
InfoSystems
  • Edited

Any news about this incomplete MSDK 5.3 implementation?

DJI Mini have a perfect size for small places indoor missions.

Thank you

0

Comments

15 comments

Date Votes
  • DJI Developer Support
    The latest version of the SDK should have fixed this problem. You can try upgrading to the latest version.
    0
    Comment actions Permalink
  • InfoSystems
    • Edited

    I suppose I used your last demo and sdk

    0
    Comment actions Permalink
  • InfoSystems

    Maybe the demo it's outdated?

    0
    Comment actions Permalink
  • InfoSystems
    • Edited

    In the demo app says 5.6.0 1182 MSDK VERSION. In fact I'm using your last SDK

    0
    Comment actions Permalink
  • InfoSystems
    • Edited

    Really need this perception module working. All our project it's based on the obstruction sensors.

    Thank you in advance

    0
    Comment actions Permalink
  • InfoSystems
    • Edited

    Testing the 5.6.0 Sample, I´m getting this warnings in this place in PerceptionFragment.kt (maybe could be something on the sample not SDK):

    Lambda argument should be moved out of parentheses.

    Tried apply the correction with no luck too. 

    private fun observerPerceptionInfo() {
        perceptionVM.perceptionInfo.observe(viewLifecycleOwner, {
            perceptionInfo = it
            updatePerceptionInfo()
            changeObstacleAvoidanceEnableSwitch()
            changeOtherEnableSwitch(it)
        })
        perceptionVM.obstacleData.observe(viewLifecycleOwner, {
            obstacleData = it
            updatePerceptionInfo()
        })
        perceptionVM.obstacleDataForRadar.observe(viewLifecycleOwner, {
            radarObstacleData = it
            updatePerceptionInfo()
        })

        perceptionVM.radarInformation.observe(viewLifecycleOwner, {
            radarInformation = it
            changeObstacleAvoidanceEnableSwitch()
            updatePerceptionInfo()
        })
        perceptionVM.radarConnect.observe(viewLifecycleOwner, {
            isRadarConnected = it
            if (it) {
                rl_radar_obstacle_avoidance_switch.show()
            } else {
                rl_radar_obstacle_avoidance_switch.hide()
            }
        })
    0
    Comment actions Permalink
  • InfoSystems

    Seems that the perception sample it´s not getting any information correctly about the avoidance status too

    0
    Comment actions Permalink
  • DJI Developer Support
    I apologize for any confusion caused by my previous response. Regrettably, the issue regarding the mini 3's inability to acquire obstacle avoidance information remains unresolved. At present, there is no specific timeline for when this matter will be addressed. It may be necessary to consider it as a potential feature requirement. We kindly request that you provide us with your feedback in the following format: - [Demand Scenario]: Could you please provide us with an analysis of the original demand scenario? It would be helpful to understand who the end user is and what the scenario requirements are. - [Scenario value]: We would appreciate it if you could describe the actual value, social value, and economic value for users. - [Priority]: It would be great if you could explain the importance of the requirement (high, medium, low). If it is high, please let us know why it is important. Additionally, if the degree of urgency (high, medium, low) is high, please explain why it is urgent.
    0
    Comment actions Permalink
  • InfoSystems

    We need Virtual Sticks, Obstacle Data and compass orientation. The 3 are highest urgency as the development stopped because Obstacle Data.

    0
    Comment actions Permalink
  • InfoSystems

    We need fly indoors, Obstacle data should be one of the first resources added. It's not good have differences in sdk per aircraft or this have to be explicit in API reference, that mislead us to use DJI MINI 3 PRO as option to use in our project.

    0
    Comment actions Permalink
  • InfoSystems
    • Edited

    There is no logic have Virtual Sticks without Obstacle Data. As you move you have to know when to stop. This should be reason enough to get this implemented. Any virtual stick application potentially will lead to a crash if have any obstacle.  At least 3 same requests from developers months ago.

    This should not be addressed as a new feature, but a bug, because will lead to a crash.

    0
    Comment actions Permalink
  • DJI Developer Support
    We apologize for the negative experience you have encountered. We acknowledge that the mentioned function is not suitable due to our lack of attention. If your project requires immediate attention, an industry-grade aircraft like the Mavic 3 enterprise would be a better choice.
    0
    Comment actions Permalink
  • InfoSystems
    • Edited

    If this will get the MSDK developers attention I can wait. Mini 3 size ,weight and noise it's perfect for indoor tight spaces, even better than Mavic.

    Thank you in advance

    0
    Comment actions Permalink
  • InfoSystems
    • Edited

    Mini 4 PRO will be compatible with MSDK?

    0
    Comment actions Permalink
  • DJI Developer Support
    I would like to inform you that I have already reported this issue to our Research and Development team as a bug. However, we are currently unable to determine the fixed time for this issue. Furthermore, I regret to inform you that the mini 4 device does not currently support the SDK. Nevertheless, I would like to assure you that we have plans to adapt the mini4 device to support the SDK in the future.
    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post