m3td does not deliver osd

Completed
Follow
ht

hello,
We have dock2 and m3td updated to the latest version.

In "flighthub2", drone information (OSD) is communicated well.
However, when connecting to our third party server, 
Dock2 information (OSD) is transmitted well, but there is an error in m3td information (OSD) not being transmitted.

Is there any way to improve this error?

0

Comments

12 comments

Date Votes
  • DJI Developer Support
    Dear developers, Hello, thank you for contacting DJI Innovation. Can I provide error messages? What command did you operate when the error occurred? I hope our solution can help you, thank you for your email, wish you a happy life! Best Regards, DJI DJI innovation SDK technical support
    0
    Comment actions Permalink
  • ht
    • Edited

    1. Connect to our server as a third party

    2. Confirm that the OSD of dock2 is delivered.

    3. Activate debug mode

    4. Drone power on

     

    After doing this I expected the drone's OSD to come in. But it didn't come in.

    0
    Comment actions Permalink
  • DJI Developer Support
    Dear developers, Hello, thank you for contacting DJI Innovation. In the "FH2" platform, check whether the MQTT server can be accessed, and whether the osd message is not reported because of the mqtt server I hope our solution can help you, thank you for your email, wish you a happy life! Best Regards, DJI DJI innovation SDK technical support
    0
    Comment actions Permalink
  • Nikolay

    Good day, I encountered a similar problem. The first launch of the drone after rebooting the dock, the OSD comes, after turning off and then turning on the drone, the OSD no longer comes until the dock is rebooted. How to solve this problem?

    1
    Comment actions Permalink
  • ht

    The problem disappeared after updating the firmware!

    0
    Comment actions Permalink
  • Nick Fry

    I also have this issue, but I have updated both the drone and the dock2 to the latest firmware and I still have to restart the dock after the drone has powered down to get any MQTT messages from the M3D.

    0
    Comment actions Permalink
  • Jatin K

    Is there a way to solve this issue?

    I am also getting the same problem where the drone osd stops working randomly and no messages are received until the device reboot command is sent. If we perform a takeoff and fly to missions with no osd messages, the dock also doenst close when the drone returns to home. It keeps sending pinching error in hms despite the drone being completely inside. We need to keep rebooting the dock and it fixes after multiple tries. 

    0
    Comment actions Permalink
  • Nikolay

    Good day. Tell me, are you responding to the message update_topo in the topic status? If you do not respond to this message, then this problem occurs.

    1
    Comment actions Permalink
  • Jatin K

    Thanks for reply Nikolay, its very helpful. We dont reply to the update_topo message. Will do that to resolve this. 

    Have you seen the second issue where when this happens, the dock has issues closing as it cannot detect if the drone is getting pinched and keeps stopping from closing the dock?

    0
    Comment actions Permalink
  • Nikolay

    No, I have not encountered such a problem. I simply did not fly without OSD from the drone. My guess is that because it does not receive information from the drone, it cannot start the mode of closing the rotation of the blades to close the cover.

    0
    Comment actions Permalink
  • ht

    @Jatin K

    For dock1, There was a time when the cover did not close because the drone was not detected due to a hardware defect in the charging terminal area.

     

    If it is not detected, we recommend that you try cleaning it.

    0
    Comment actions Permalink
  • Nick Fry

    Thanks Nikolay! Replying to the update_topo message on the status topic fixed the issue for us

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post