Recent content by sar104

Of course it won't be approved. And since nothing required you to invest in ADS-B out to begin with, I'm not sure why you think that's the FAA's fault. As for how the information gets to ATC - that's just the same principle as was used for LAANC - i.e. the FAA doesn't have and isn't funded to...

Those are the aircraft DAT files, which should be readable on the P4. They are quite large, and for most purposes the mobile device txt or DAT files are enough - unless you are using a third-party app that doesn't write standard files to the mobile device.

They are in the only place that you didn't look - your mobile device.

You guys are arguing different points. Yes - the magnetic distortion from the rebar or other ferrous metal does go away as the aircraft ascends, and the compass will then return to reading correctly. But that's not the problem, as @Meta4 is trying to point out. The problem, as I explained in...

I'm afraid that this one is going to remain a mystery. The aircraft switched to ATTI due to the GpsPositionNoMatch flag, not because of a lack of satellites.The txt log doesn't generally continue to report position when that happens, so I wonder if it is a slightly non-standard implementation of...

This thread is over two years old. On the Phantoms, the problem was generally a cracked antenna module or a poor connection to the main board.

Don't you just hate it when your drone is doing "Other"?

I don't understand the VPS zero height data, but looking at the sWave flag you are correct that it should be ignoring it.

Interesting. I'm not using PhantomHelp - I'm just reading directly from the file, and that shows zeros. I doesn't generally do that for out of range.

In this log the VPS data don't go blank - they go to zero. That doesn't seem correct - at least that's not how I'm used to seeing them behave. My hypothesis is that it's climbing because it's seeing zero height above the ground, and it doesn't switch to cruise because of that. I'd have to dust...

Yes - look at the VPS height. It's zero for most of the flight. The aircraft was above the RTH height when the RC RTH button was pressed, but notice that it climbed anyway until it hit the flight height limit of 120 m. The VPS height was confusing the FC, and it would not start the RTH until it...

Also the mobile device DAT - that begins as soon as the app connects following aircraft power up.

No - you don't accept anything like that at all.

I'd hazard a guess that everyone in the US got that message.

That's why I referred specifically to the FC uplink. The gimbal was responding, at least at some times: