Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I don't receive some information in the Logs #29

Open
camargoz opened this issue May 13, 2024 · 9 comments
Open

I don't receive some information in the Logs #29

camargoz opened this issue May 13, 2024 · 9 comments

Comments

@camargoz
Copy link

When decrypting the Logs I receive various information about the Flight, however two crucial pieces of information are not found, such as the RC Joystick data and the notifications generated during the Flight.
I see that the options for obtaining this data are listed in the library, but when I decode they are not returned.

Does anyone know how I can fix this, or if there is any other problem I may be having with the SDK Key.

OBS:
I've already done the test with the Drones:
Mini 4 Pro, Mavic 3 Interprise/Classic, Matrice30, Air 2s, Mini 3, Avata, Mini 2 / SE, M300 RTK, Air 3 and Mavic Mini.

{
      "flightControllerState": {
        "attitude": {
          "pitch": -23,
          "roll": -14,
          "yaw": -968
        },
        "aircraftLocation": {},
        "flightMode": "GPSAtti",
        "satelliteCount": 11,
        "smartRTHState": "Unknown",
        "behavior": "GoHome",
        "areMotorsOn": true,
        "windWarning": "Unknown",
        "countOfFlights": 1,
        "velocity": {}
      },
      "cameraState": {
        "isInserted": true,
        "isVerified": true,
        "isFull": true,
        "isFormatted": true,
        "totalSpaceInMB": 2029,
        "remainingSpaceInMB": 1407,
        "availableCaptureCount": 53
      },
      "gimbalState": {
        "atitude": {
          "yaw": -82
        },
        "yawRelativeToAircraftHeading": -0.40000000596046448,
        "mode": "YawFollow"
      },
      "batteryState": {
        "voltage": 8330,
        "current": -952,
        "temperature": 27.200000000000003,
        "chargeRemainingInPercent": 99,
        "lowBatteryWarningThreshold": -1,
        "seriousLowBatteryWarningThreshold": -1,
        "index": -1,
        "lifetimeRemaining": 10,
        "designCapacity": 985600,
        "numberOfDischarges": 512,
        "fullChargeCapacity": 3710,
        "chargeRemaining": 3653
      },
      "airLinkState": {},
      "visionState": {
        "controlState": {}
      },
      "gimbalsState": {
        "0": {
          "atitude": {
            "yaw": -82
          },
          "yawRelativeToAircraftHeading": -0.40000000596046448,
          "mode": "YawFollow"
        }
      },
      "camerasState": {
        "0": {
          "isInserted": true,
          "isVerified": true,
          "isFull": true,
          "isFormatted": true,
          "totalSpaceInMB": 2029,
          "remainingSpaceInMB": 1407,
          "availableCaptureCount": 53
        }
      },
      "batteriesState": {
        "0": {
          "voltage": 8330,
          "current": -952,
          "temperature": 27.200000000000003,
          "chargeRemainingInPercent": 99,
          "lowBatteryWarningThreshold": -1,
          "seriousLowBatteryWarningThreshold": -1,
          "index": -1,
          "lifetimeRemaining": 10,
          "designCapacity": 985600,
          "numberOfDischarges": 512,
          "fullChargeCapacity": 3710,
          "chargeRemaining": 3653
        }
      }
    }
    ```
@dji-lyt
Copy link
Collaborator

dji-lyt commented May 15, 2024

Could you please clarify what you mean by the library providing this option? FlightRecordParseLib does not have the functionality to retrieve remote control joystick and notification information.

@camargoz
Copy link
Author

camargoz commented May 17, 2024

@dji-lyt

It has, because this functionality is referenced a few times in the code, where you can even find something about it in the file dji-flightrecord-kit/source/FlightRecordStandardizationCpp/model/MobileRC/FRMobileRCModelProto.pb.cc, in this file it references the Joystick.

Example of a function in this file that refers to the Joystick:
image

@dji-dev
Copy link

dji-dev commented May 20, 2024

Agent comment from yating.liao in Zendesk ticket #107244:

There is indeed a data model for stick state in the repository, but the current version does not have parsing functionality.

Could you please inform us of what you need the joystick data and notifications for?

°°°

@camargoz
Copy link
Author

I would like this data so that I can analyze my clients' flights, so that I can know the causes of an accident or crash.

@dji-dev
Copy link

dji-dev commented May 21, 2024

Agent comment from yating.liao in Zendesk ticket #107244:

Could you provide more details on why you would like to analyze the aircraft accidents? What types of accidents do you wish to analyze?

If there are any abnormalities during the flight of the aircraft, users can actually contact DJI for accident analysis.

°°°

@camargoz
Copy link
Author

My clients control the flights of their fleets, where they have some pilots, and they often like to know how their pilot did the flight, so they can better evaluate their pilots, so this data is very important for this. Do you know when you intend to add this functionality? or is there something I can do to get this data when I use the parse library?

@dji-dev
Copy link

dji-dev commented May 22, 2024

Agent comment from yating.liao in Zendesk ticket #107244:

I am currently unsure if FlightRecordParsingLib will add this feature, but I will gather the scenarios where you would use this feature and provide feedback to the relevant team for evaluation.

°°°

@camargoz
Copy link
Author

Thank you for your help

@dji-dev
Copy link

dji-dev commented May 23, 2024

Agent comment from yating.liao in Zendesk ticket #107244:

I am glad to be able to help you.

°°°

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants