Add RemoteID to Peripherals section

[rmackay9]

On this page we should add a status update on AP support and which hardware is available (or expected to be available and compatible). We should probably mention which countries the id is valid for.

• https://dronescout.co/dronebeacon-mavlink-remote-id-transponder/ (US?)
• EAMS Robotics remote id for Japan
• DroneTag: https://dronetag.cz/en/products/mini/ (mavlink capable)
• Aerobits: https://www.aerobits.pl/product/idme/ (mavlink capable) see idME idME+
• Wurzbach Electronics may be working on a product https://wurzbachelectronics.com/
• Sagetech may be working on a product https://sagetech.com/
• Pierce Aerospace may be working on a product https://www.pierceaerospace.net/products-services

We should also add a link back to this issues list as a way to gather info from the community on other devices that become available.

[BluemarkInnovations]

DroneBeacon supports EU, US and also Japan Remote ID standard. (As I understand the Japanese Remote ID standard is equal to the one in USA.)

Also there is a PR for Remote ID support in ArduPilot ArduPilot/ardupilot#21075 (So currently Remote ID transponders are not supported by ArduPilot.)

[rmackay9]

@BluemarkInnovations,

Great, thanks for that additional info. I've updated the PR so it lists the regions for the DroneBeacon. The Japan standard is the same as the US I think although I also wonder if a Japanese "giteki" is required to make it legal in Japan. Most transmitters require a "giteki".

For now I'm going to assume that PR will get in soon enough that I don't need to add a comment to the wiki..

[BluemarkInnovations]

Some other things which could be useful for this page:

• free Remote ID Android app: https://play.google.com/store/apps/details?id=org.opendroneid.android_osm
  (source code: https://github.com/opendroneid/receiver-android) So users can install this app, to check the information that the Remote ID transponder is broadcasting.
• I think "giteki" is similar to CE in Europe and FCC in the USA. Although the modules needs to be compliant for each country, ArduPilot also needs to make sure that the module is configured correctly for each region. More info here: https://github.com/opendroneid/opendroneid-core-c#comparison For instance an Operator ID is mandatory in the EU, but optional elsewhere.
• MAVLink capable is similar to saying it has USB. What I don't know is if a MAVLink capable device support the MAVLink messages defined here: https://mavlink.io/en/services/opendroneid.html It could be that devices with GPS (and other sensors) on-board only use proprietary MAVLink messages.

[rmackay9]

@BluemarkInnovations, thanks for that. I've added a link to the android app. I think that AP will provide the mavlink messages on that wiki page although I haven't reviewed it completely.

[Hwurzburg]

autoclose, reopened for device tracking...

[lukasbrchl]

Hi, our device Dronetag Mini and Dronetag Beacon supports reading MAVlink messages. We don't use the structures defined in OpenDroneID. We have described details in our documentation

[friissoren]

Just FYI: We are trying to maintain a list of devices capable of transmitting remote ID here: https://github.com/opendroneid/receiver-android/blob/master/transmitter-devices.md

The two lists are probably not completely overlapping, since you will be focusing on add-ons that can feed in MAVLink messages, while the one on the opendroneid page will be more general. I will add a cross link to your list.

[rmackay9]

@lukasbrchl,

Great, thanks very much for the feedback. I'll created a PR to move the Dronetag Mini up into the, "MAVLink enabled devices" section.

[rmackay9]

@friissoren,

OK thanks! I've added a link to the OpenDroneId list of devices to the same PR mentioned above.

[optical-o]

Hello,
i have created a PR #5126 with some enhancements for the RemoteID page.