@Baris_Dogan wrote:
Every babe has a name given by his parents.
DIYdrones (rover, plane, multirotor) are also babies of their developers.
Although I searched through APM full parameter list and Mission Planner user interface; I have found nothing about giving a personal name to our vehicles.My opinions about the importance of naming DIY vehicles are below:
- Psychological effect: it will improve the relation between the vehicle and its developer.
- Data Log Handling: We have many APM based drones and it is hard to manage data logs. We have 6 quadrotors, 2 hexarotors, 3 planes and use different computers as a ground station. For example; when we download telemetry and data flash logs of a quadrotor via Mission Planner, all quadrotor logs are stored in the same folder. Then it becomes really hard to handle too many log files, hard to separate the files. For there is no vehicle distinguishing parameter (except quadrotor, sitl, small, etc.) in the parameter list; Mission Planner save logs into the same folder. For example all quadrotor logs are stored in "...Documents\Mission Planner\logs\QUADROTOR\1\" folder.Just adding a new parameter (ex: MAV_NAME) in to APM stack will be the solution. Then Mission Planner or other software can use this parameter to handle vehicle specific data. In the configuration wizard, the first question may be "What is the name of your vehicle?" for example.
Short of long: data logging is a very important issue, which should be done carefully for better flight results. Logs are generally analyzed very after making flights. I could find no parameter to distinguish my vehicles. So; Mission Planner cannot separate the log files of different vehicles. First; a “name” parameter should be add to APM stack; second, Mission Planner should adopt this by giving folder names or log file names as the “name” parameter.
Best Regards…
Posts: 2
Participants: 2