Phantom 4 Pro problem with MAVLINK commands #218
Comments
|
Apparently MAVLink is working fine, nevertheless there are some Every time when I have the QGC and start RD, the app crash with the following exception. The issue should be with the FTP transaction, according to MAVLink documention, requestMsgId 395 is
Apparently that FTP transaction done is being done with a null pointer, additionally the method appears as deprecated since 2022-04. Any ideas how to solve it? |
|
Definetively a bug in the implementation. |
|
Why is it using FTP? Maybe it's old custom code that shouldn't be there. The bug you described could be triggered by some leftovers of his customizations in MAVLINK commands that were not tested afterwards. |
|
Good, I did understand how to move the code to the plugin file, because the lines are in the Other aspect is the ACK necessity after a command, I saw that is already implemented but is not always sent. I added in the I still need to test during flying, If all goes fine I will create a PR. |
|
I also found and fixed many of those missing ACKs. I don't remember if QGC and MAVSDK were 100% compatible regarding ACKs (I remember the implementations had some deviations, but I got them working fine for my use cases). |
|
I already did some tests, and when I create a mission on QGC appears the uploading message in logcat but when slide the bar to start the mission, nothing happens after that. |
What DJI model? |
|
I'm not sure if phantom 4 supports on-board missions. |
|
I don't exactly know if P4P supports on-board missions, but I was looking into the |
|
There is anyway to test the support of on-board missions? I accidentally already added the model to the list and enabled it. After populating the |
|
For onBoard, just don't use the MissionManager class.
I couldn't test it though because I have a cheap mini.
…On September 5, 2024 9:05:35 PM GMT-04:00, Angel Ayala ***@***.***> wrote:
There is anyway to test the support of on-board missions? I accidentally already added the model to the list and enabled it.
When I upload the mission enters into `MAVLinkReceiver` class's `finalizeNewMission` method with all working fine, but after sliding the drone lifts and then nothing happens and, there is no movement nor error log.
After populating the `missionItems` through `mModel.missionManager.setMission` which method (must be) is called? I was thinking in check the method's flow calls first, I'm using the mission planner from QGC with just one coordinate.
Any thoughts on what could it be?
--
Reply to this email directly or view it on GitHub:
#218 (comment)
You are receiving this because you commented.
Message ID: ***@***.***>
|
Describe the bug
After source code compilation and installing RD, the APK crashed when after tap the Drone button.
I changed two lines of code, and I was able to use it, however, I still facing some problems.
I already set the RD and QGC settings, and I can arm the drone from my smartphone and through QGC, nevertheless, no success with other MAVLINK commands.
With QGC I can read some sensor data, but I can't send the home location or other MAVLINK related commands with success.
On the logcat from android studio, after open RD I get some some error log, then when I tap the Drone button I get other error messages.
When I start the DroneKit's python script to read the vehicle state, I can see the captured state until the armed info, after that, the script keeps waiting set the home location command, which never happens.
There are some LDM related error, but on the DJI's site appears that is not mandatory, maybe because is a chinese smartphone?
I don't know, can you help me?
Steps To Reproduce
case PHANTOM_4_PRO:in theMainActivity.javafile at line 949, and update the line 296 ofDroneModel.javawithuseMissionManager = m_model == Model.PHANTOM_4_PRO.Screenshots
No response
Drone Model
Smartphone Model
Additional context
DroneKit
python vehicle_state.py --connect udpin:0.0.0.0:14550command output:RD start log output:
log after tap Drone button
The text was updated successfully, but these errors were encountered: