SeehawerB
Second Officer
Flight distance : 5414203 ft
Germany
Offline
|
I am contemplaning this Remote ID thing for many days now. And have some conclusions I'd like to verify:
1. The Drone has built in GPS, the Googles don't - this is the main problem I suppose.
2. The Drone gets a GPS fix after few seconds and sets the home point accordingly.
3. In the US, you have to connect your phone to the Googles only one time, before take off.
4. After take off you may disconnect the phone and get a subsequent "Remote ID warning".
5. Supposedly the Drone has to send out the actual coordinates of itself AND the pilot, is that right?
If these are the facts, some questions arise:
A. One could achieve SAME behaviour using the first home point coordinates as the goggles = pilots coordinates because usually theses coordinates are nearly identical.
So why is there ANY connection to a phone as a GPS source necessary?
B I suppose, the "Remote ID Warning" after take off and disconnecting the phone is simply there because it is mandatory the phone keeps connected for the whole flight, but you do not cut the engines after take off for safety reasons. So disconnecting the phone at any time is against the rules for Remote ID.
This brings us back to A., because if Remote ID demands to always transmit not only the actual coordinates of the drone, the pilots coordinates also have to be transmitted.
C. There would only be one good solution for anybody, in the US or elsewhere: Goggles need an internal GPS receiver. WHAT A SHAME they obviously lack this. Only few bucks difference in design. The whole Remote ID topic is not new at all. So why DJI, WHY?
So out of all this, I think it could be a good idea to develop a small addon for the Googles: a tiny external GPS receiver that gets its power from the USB C connection to the Googles and is tiny enough to be mounted on the head strap. This device could be light, small and cheap to create. And could sort this hole thing out in a good manner. So, DJI, what's the point? |
|