Best Practices & Model Matching

This guide covers essential practices for using UAV Management effectively: ensuring telemetry mapping works, organizing a fleet, and making the most of all features.

Model Name Matching: The Key to Automatic Telemetry Mapping

UAV Desk automatically associates imported flight logs and telemetry files with aircraft by matching the Drone Name you registered in UAV Desk with the model name recorded by your transmitter (in flylog.csv or TeleLog filenames).

How it works

• Your transmitter's flylog.lua script records a "ModelName" every time it logs a flight.
• When you import logs via the Imports page, UAV Desk looks for a matching Drone Name in your registered aircraft.
• If it finds an exact match, the flight is automatically assigned to that aircraft.
• If no match is found, the import fails or requires manual intervention.

The match is exact and case-sensitive

Examples

If automatic mapping fails

• Manual assignment: You can manually assign individual flights to aircraft via the Flight Logs page after import.
• Rename the aircraft: Update the Drone Name in UAV Desk to match your transmitter's model name exactly (including case and punctuation).
• Rename on transmitter: Update your transmitter's model name to match the existing UAV Desk entry.

Pro tip: It's easier to rename once during initial setup than to fix mismatches later. Take a few seconds to ensure exact consistency.

Fleet organization best practices

Use consistent naming conventions

• Avoid special characters: Stick to letters, numbers, hyphens, and underscores. Avoid spaces, accents, or symbols that might cause issues in filenames or logs.
• Be descriptive: Use names like "FPV Quad 5in" rather than "Quad #1". This makes it clear what the aircraft is at a glance.
• Prefix by type (optional): Use prefixes like "RAC_", "MAP_", "SIM_" to organize aircraft by purpose (Racing, Mapping, Simulator).
• Example naming scheme:
  • FPV_5inch_1
  • FPV_7inch_1
  • Mapping_Quad
  • Wing_1
  • Sim_Phoenix

Register all aircraft upfront

Before you start importing logs, register all your aircraft in UAV Management. This ensures that when you import, flights are automatically assigned to the correct aircraft rather than requiring manual correction later.

Include identifiers

Fill in the Registration Number and Serial Number fields if available. This:

• Provides a paper trail if you sell or transfer an aircraft
• Helps distinguish between multiple aircraft of the same model
• Supports warranty and insurance claims

Documentation and specifications best practices

Record what you know

Fill in as much detail as you're comfortable with:

• Manufacturer, firmware, ESC, receiver, and flight controller details help you remember configurations and assist with troubleshooting.
• You don't need to be exhaustive, but the more you record, the more useful the record becomes over time.

Update when things change

If you upgrade a component (e.g., replace the ESC or update firmware), click the pencil icon to edit the aircraft and update the record. This ensures your UAV Management entry reflects the current configuration.

Configuration file management best practices

• Store before major changes: Before adjusting PIDs or filters, save the current config as a reference. This lets you compare and understand what you changed.
• Use descriptive names: Instead of "config.txt", use "PID_Stable_2025-02-15" or "Conservative_Filter". This makes it clear what each file represents.
• Date your files: Include dates in config names (e.g., "Racing_2025-02-10"). Over time, this builds a timeline of your tuning iterations.
• Keep known-good backups: Always have a snapshot of a configuration that flies well, so you can quickly restore it if new changes don't work out.
• Use the diff viewer: Once you have two configs, compare them to understand which parameters differ. This is invaluable for learning what each setting does.

See Configuration Files and Config Diff Viewer for more details.

Maintenance tracking best practices

Log every service

• Record crashes repairs, motor rebuilds, propeller replacements, solder joint rework, anything that touches the aircraft.
• Include the date, a clear description, and attach photos or receipts if you have them.

Set realistic maintenance intervals

• Use manufacturer recommendations as a starting point (e.g., propellers every 3 months, motors every 6–12 months).
• Adjust based on your own experience. If a component wears faster than expected, set a more frequent interval.

Keep maintenance and reminders in sync

• When you perform maintenance (log an entry), immediately update the Maintenance Reminder ("Last" date) so the next scheduled date auto-fills.
• This keeps both records synchronized and prevents accidental double-maintenance.

See Maintenance Logs and Maintenance Reminders for details.

Archive and lifecycle best practices

• Archive more than delete: When an aircraft is retired or damaged, mark it inactive rather than deleting. This preserves its complete flight history.
• Use inactive for temporary storage: Aircraft undergoing repair? Mark inactive to prevent accidental imports. Reactivate when it's back in service.
• Keep simulator entries: Use the Simulator checkbox to flag flight simulator UAVs. You can then filter them separately from real aircraft via the Type filter.

Multi-aircraft fleet tips

• Organize by purpose: Use the Type filter (All / Physical / Simulators) and Status toggle (Active / Inactive) to quickly view subsets of your fleet.
• Use color or naming consistency: While UAV Desk doesn't have built-in color coding, you can use prefixes in names (e.g., "RAC_", "MAP_", "FUN_") to organize by purpose.
• Assign serial numbers: For identical models, include a serial or number suffix (e.g., "5inch Quad #1", "5inch Quad #2") to distinguish them.