Add electronic reporting according to new europeen law

[activa73]

Current Behavior

No current behavior

Desired Behavior

The goal is to implement a protocole to dirve an external wifi module like ESP32 for exemple to send data according to the futur european law for drone > 800 g.In french this law start 29 June. This trame must have gps to send speed, longitude, latitude, height,... to the wifi module.
Input variable must be the ID of the plane.

Suggested Solution

This web site explain how to make an electronic reporting module with open source ressources.
https://www.helicomicro.com/2020/05/26/une-solution-open-source-pour-le-signalement-electronique-a-distance-a-moins-de-40-e/
Code to communicate with wifi module is implemented in GPL licence.
Here the library : https://github.com/khancyr/droneID_FR
Here an example of implementation in TTGO T-BEAM board : https://github.com/khancyr/TTGO_T_BEAM

Who does this impact? Who is this for?

For all European user

Additional context

[digitalentity]

INAV is already able to output telemetry, whichc contains all information required to implement this kind of beacon. Interpreting the telemetry and further transmitting it via WiFi or BLE is up entirely up to the beacon firmware and out of scope for INAV.

[activa73]

Yes I know t is not possible to controle the firmware of beacon chip directly by inav. I just want to resend data come from inav gps to esp32 chip. The goal is to connect fc board to esp32 using serial port (RX TX) to resend gps data to esp32. After we can develop firmware on esp32 to read gps data and format trame according to law.
What do you think?

[digitalentity]

Reuse one of the existing telemetries - MAVLink, LTM or other.

[activa73]

Ok thank you, I will search in this direction. With your experience, What is the best telemetry for my situation?

[wx4cb]

mavlink would probably be your best bet as it's what ardupiot and others use

[activa73]

Ok thank you.

[stale]

This issue / pull request has been automatically marked as stale because it has not had any activity in 60 days. The resources of the INAV team are limited, and so we are asking for your help.
This issue / pull request will be closed if no further activity occurs within two weeks.

[stale]

Automatically closing as inactive.