That's interesting.
When you see the "N/A", has the drone been bound long enough, with a good enough view of the sky, to start seeing satellites?
Looking at the existing files, the drone itself is seeing the satellites, and using them to calculate position. It's even reporting what it sees to the controller in the form of telemetry that is recorded in the files. But your observation suggests the controller is not acknowledging satellite count, and it was previously noted the drone is not establishing "Home Point". I'm wondering if there is a difference in which frequency transmits the data, if there is some issue with the controller, maybe some issue with the FC section of the drone mainboard. A more advanced member will need to comment on those issues.
I guess there is a distant chance It could also mean the drone RF module is not transmitting as well as it should. That one should at least be added to the list of "unplug, clean, and reconnect".
When you see the "N/A", has the drone been bound long enough, with a good enough view of the sky, to start seeing satellites?
Looking at the existing files, the drone itself is seeing the satellites, and using them to calculate position. It's even reporting what it sees to the controller in the form of telemetry that is recorded in the files. But your observation suggests the controller is not acknowledging satellite count, and it was previously noted the drone is not establishing "Home Point". I'm wondering if there is a difference in which frequency transmits the data, if there is some issue with the controller, maybe some issue with the FC section of the drone mainboard. A more advanced member will need to comment on those issues.
I guess there is a distant chance It could also mean the drone RF module is not transmitting as well as it should. That one should at least be added to the list of "unplug, clean, and reconnect".