|
|
|
|
|
by mschuster91
1348 days ago
|
|
> While this is interesting (broadcast to whom exactly?) It's hard to find any information about how Remote-ID is supposed to work, but in theory the ID packets are sent by WiFi NAN and Bluetooth so that they can be received by anyone in the radio range (which is quite important for authorities to track down violators, e.g. people flying around hospital helipads). Unfortunately, current phones seem to lack support hardware-wise (see [1], page 6). [1] https://www.cencenelec.eu/media/CEN-CENELEC/Events/Webinars/... |
|
The FAA hasn't specified an implementation. It's on the manufacturer to come up with a means of compliance, and then get the FAA to sign off on it. There is a standard put out by the ASTM, which is heavily based on an open source project, OpenDroneID.
The standard moved away from NAN in the draft phase, in favor of vendor elements in 802.11 beacon frames. You can choose 802.11 or Bluetooth Low Energy. If you choose 802.11, 2.4ghz is required and 5ghz is recommended. If you choose BLE, v4 is required, and doing v5 as well is recommended.