Articles in this section

FlightHub Sync

xiaorong.zheng
  • Updated
Follow

FlightHub Sync Documentation

Architectural Design

  1. Configure AWS Cloud OSS details and callback address in FlightHub 2.

  2. After completing the wayline mission, the dock uploads media files to the corresponding AWS Cloud OSS.

  3. Upon receiving successful file upload notification, FlightHub 2 sends callback data to the user's specified cloud platform through the configured callback address.

Integration Process

Operator: Third-party Partners

Process Details

Preparation

Media transmission parameter configuration.

Storage Address

Use STS temporary credentials to access OSS, refer to AWS Cloud's official documentation for configuration information.

{

"access_key_id":"xxxxxxx", // required

"access_key_secret":"xxxxxxxx", // required

"bucket":"xx-bucket", // required

"region":"us-east-1", // required

"arn":"xxxxxx", // required

"policy": "xxxxxxx", // optional

"role_session_name":"xxxxx", // required

"provider":"aws"// required, aws or ali

}

API Address (Notification Receiving Interface)

Must be an HTTPS interface, such as https://x.com/xxx

Request Parameters:

{
    "notify_type":"drc_file_upload_complete",
    "org_id":"Organization ID",
    "org_name":"Organization Name",
    "prj_id":"Project ID",
    "prj_name":"Project Name",
    "sn":"Device SN",
    "task_info":{
        "task_type":"Task Type",
        "tags":["Tag 1","Tag 2"]
    },
    "files":[
        {
            "name":"Name",
            "key":"AWS Cloud key"
        }
    ],
    "folder_info":{
        "expected_file_count":0,
        "uploaded_file_count":0,
        "folder_id":0
    }
}

Return:


{
    "code":0,
    "message":"Error Message when code is not 0"
}

Configuration

  1. Access organization settings with admin rights.

  1. Configure storage bucket details.

  1. Refer to the preparation section, formatted as JSON.

  1. Enable the Media File Direct Transfer function

  1. Schedule tasks for Media File Direct Transfer and set tags.

Testing

  1. After flight, check if the media file library transmission is completed, and there should be a popup notification says "media uploaded to third party platform + task tag".

    2. Confirm third-party platforms receive notifications on time with right format and complete information (organization + project + device + task + file + tag).


{
    "notify_type":"drc_file_upload_complete",
    "org_id":"Organization ID",
    "org_name":"Organization Name",
    "prj_id":"Project ID",
    "prj_name":"Project Name",
    "sn":"Device SN",
    "task_info":{
        "task_type":"Task Type",
        "tags":["Tag 1","Tag 2"]
    },
    "files":[
        {
            "name":"Name",
            "key":"AWS Cloud key"
        }
    ],
    "folder_info":{
        "expected_file_count":0,
        "uploaded_file_count":0,
        "folder_id":0
    }
}

FAQ

  1. What happens if the STS credentials are incorrect in FlightHub 2?FlightHub 2 will display an error when saving STS. Successful setup means correct STS.

  2. If the client platform doesn't process FlightHub 2 callbacks, will there be retries?Yes, in the first 2 hours, there's a callback every 30 minutes. Afterwards, it's every 2 hours.

  3. Supported oss

    AWS, Ali

     

Related articles

Comments

5 comments

Date Votes
  • Matias Herreros

    Hi. I've been trying to configure my AWS Cloud OSS in Flighthub2. I noticed two things:

    1. The screenshots used in this document are not up to date.
    2. After completing the "Storage Location" field with all the necessary data, I get the following error:  
      >>>> err:  Error: Request failed with status code 400
      url:  /manage/api/v1/organizations/HIDDEN_ID/c2c/solution/media_data_direct_trans 【post】 
      code      : 200610
      codeMessage: "Request failed. Try again later"
      data: Array(5)
            0:{}
            1:{}
            2:{}
            3:{}
            4:{}

    The inputed data follows exactly the JSON format described in this document:

    {
    "access_key_id":"AWS ACCESS KEY ID",
    "access_key_secret":"AWS SECRET KEY",
    "bucket":"BUCKET NAME",
    "region":"us-east-1",
    "arn":"ROLE ARN",
    "role_session_name":"SESSION NAME",
    "provider":"aws"
    }

    Could you provide more information regarding the "Storage Location" JSON? Is the format correct? The ARN needed is the one of the Role or the one of the Bucket?

    Could you provide documentation regarding the error code and message? I couldn't find documentation associated with this online.

    Thanks,

     

    0
    Comment actions Permalink
  • JacekKosciesza
    • Edited

    Hi Matias. I've written an article about it: DJI FlightHub Sync: Media File Direct Transfer to AWS. Maybe you will find it useful.

    2
    Comment actions Permalink
  • Matias Herreros

    Hi Jacek, thank you for sharing your article. It is updated and very well detailed!

    1
    Comment actions Permalink
  • Alex Hall

    JacekKosciesza thaks for putting this, as we have been working on this also.

    How has your testing gone? Can you confirm this is only currently working for DJI dock and no drones like Mavic 3? this is really annoying as we use both for or worklows, yet as usual DJI provide half-baked solution..

    Have you experimented with the RTMP streaming? we are finding a latency of over 12 seconds, its really bad...

    1
    Comment actions Permalink
  • JacekKosciesza
    • Edited

    Hi Alex Hall,

    Can you confirm this is only currently working for DJI dock and no drones like Mavic 3?

    Yes, it works with Dock, but I couldn't make it work with my Mavic 3E. I sent question about it to the DJI with a list of several issues/questions/suggestions) e.g.

    1. FlightHub Sync not triggered with Mavic 3E or when pilot switched to a manual mode during flight
    2. Missing notification (it happened once or twice)
    3. Uploaded file count (some inconsistency in notifications for "expected_file_count" vs "uploaded_file_count)
    4. File uploaded notification (I get some notification about uploaded KMZ files, but structure of this notification seems to be incorrect e.g. I don't get "notify_type" or "notify_time" like for other notifications)
    5. Incomplete notification (sometimes files are uploaded to S3 bucket, but list of the files is not present in notification, I just get one entry in the files array which is "Remote-Control")
    6. Suggestions about API improvements: e.g. missing date_time filed when file was created (instead of only having it in the file name, but without milliseconds), not clear file_type and sub_file_type (usually it's 10, 1 or 0)

    DJI never responded to those questions.

    Have you experimented with the RTMP streaming?

    Yes, I'm currently working on livestreaming feature, so yeah I experimented with stream forwarding and telemetry.

    BTW: in both cases I would have suggestion to the DJI to make it work using secure protocols (using TLS) + more advanced auth e.g. using certificates + fully customizable stream forwarding URL, because I couldn't make it work directly with AWS services like IVS and IoT Core and I had to use some proxy services.

    we are finding a latency of over 12 seconds, its really bad...

    From my experience (with my Mavic 3E, architecture like: DJI -> NGINX proxy -> Amazon IVS) latency was around 6 seconds I think. But yeah, it would be great if they would support lower latency protocols like WebRTC or SRT.

    Jacek

     

     

     

    0
    Comment actions Permalink

Please sign in to leave a comment.

close