open drone ID implementation added few lines about remote ID transponder architecture

Author: BluemarkInnovations

libraries/AP_OpenDroneID/AP_OpenDroneID.cpp

@@ -20,6 +20,9 @@
  * The code has been tested with the BlueMark DroneBeacon MAVLink transponder running this command in the ArduPlane folder:
  * sim_vehicle.py --wipe-eeprom --console --map -A --serial1=uart:/dev/ttyUSB1:9600
  * (and a DroneBeacon MAVLink transponder connected to ttyUSB1)
+ * 
+ * The Remote ID implementation expects a transponder that caches the received MAVLink messages from ArduPilot 
+ * and transmits them at the required intervals. So static messages are only send once to the transponder.
  */
 
 #include <stdio.h>

libraries/AP_OpenDroneID/AP_OpenDroneID.h

@@ -20,6 +20,9 @@
  * The code has been tested with the BlueMark DroneBeacon MAVLink transponder running this command in the ArduPlane folder:
  * sim_vehicle.py --wipe-eeprom --console --map -A --serial1=uart:/dev/ttyUSB1:9600
  * (and a DroneBeacon MAVLink transponder connected to ttyUSB1)
+ * 
+ * The Remote ID implementation expects a transponder that caches the received MAVLink messages from ArduPilot 
+ * and transmits them at the required intervals. So static messages are only send once to the transponder.
  */
 
 #pragma once
@@ -121,7 +124,7 @@ class AP_OpenDroneID {
     void update();
     void send_dynamic_out();    
     void send_static_out(); 
-    
+
     // get methods
     MAV_ODID_ID_TYPE get_id_type();
     MAV_ODID_UA_TYPE get_ua_type();