Recent content by BudWalker

There is no direct relationship between control stick movement and RPM. If the throttle stick is increased by a certain amount that translates to a desired increase in ascent rate. Achieving that ascent rate depends on more than just motor speed such as lateral velocity and air density. Here...

Yes, the calibration may be better but not enough to matter. The result of the calibration can be seen in the eventLog stream as scale and bias values. Here's an example from my Mavic 2 68.882 : 5493 [L-COMPASS][scale cali(0)] succeed! bias:64.7 -348.9 -981.0 scal:3.545 3.517 3.741| I did a...

Sorry. Flight Controller.

3) Yes it's a good question...when the Spark's internal sensors are showing as unreliable...why wouldn't the Spark revert automatically to ATTI mode, instead of activating a full throttle fly away? Usually the "internal sensors" aren't showing as unreliable. All the FC knows is that Yaw...

The single most effective means to prevent a launch time fly away is to check the red triangle heading indicator in the map display. If it doesn't agree with the actual AC heading then erratic flight and possible fly away is likely. This method is more robust and accurate than any of the other...

I looked at the .txt which is consistent with Yaw being incorrectly initialized. There is a .DAT on the device running the Go App. It will have the data to determine if Yaw wasn't initialized correctly. Look here to see how to retrieve that .DAT. It will be the .....FLY098.DAT file.

Look like your everyday normal .DAT and .txt files. My suggestion to take a look at a .DAT file was in case you had additional questions. I guess I have to admit that I'm still not quite sure what your point or question is.

There are (at least) 2 sets of coords data that exist in the .DAT. There is the GPS coords that come directly from the GPS receiver. That's the raw GPS data that can be found in the GPS record - DatCon labels these fields GPS(0):Long and GPS(0):Lat. Then there are the latitude and longitude...

I believe those coordinates are referring to the APP.GPS. I.e., the location of the device running the DJI Go App. The raw GPS data in the .DAT should have the Spark's last position.

@rearback the .DAT file that you want will have a name that ends with "FLY044.DAT"

The .DAT file recorded on the DGI Go App device is different from the .txt file. The .DAT will almost certainly have GPS data. The reason is that the lat/long data recorded in the .txt is not actually GPS data. It's the result of the FC combining GPS, IMU, and magnetometer data. The .DAT will...

There will probably be geo coordinates in the .DAT file that exists on the device running DJI Go app. Look here to see how to retrieve that .DAT file. Then upload to a public sharing site like Dropbox and post a link to the uploaded .DAT

The red arrow shows what the AC thinks the heading is (Yaw). If it's inconsistent with the actual heading that's usually an indication that the Spark is sitting in a geomagnetic distortion. I.e., it's the location and not the Spark's compass that causes the discrepancy. But, if you're getting...

If the red arrow heading indicator is not consistent with the AC's actual orientation that means that the Yaw value is incorrect. Launching under this condition will likely result in erratic flight, possibly a fly away. The only way to fix this is to move the AC to another location. Calibrating...

A slightly different perspective is that it's not just a waste time and energy. It gets in the way of focusing on the real problem - that launch time fly aways are caused by a geomagnetically distortion at the launch site. IMHO if half the time and energy spent on the...