How do you manage transmitter profiles?

Hardware Radios
1

Just curious how different people are doing this?

Do you have a single profile for similar vehicles? Say 1 single Ardu trad heli on the transmitter then use that for all of them and make your configs are consistent for inputs?

Use a template and copy it for each Heli so that your profiles can better support small differences?

I have a profile for each currently but am considering going to a single profile for all my ardu helis. I make it sound like a lot but thats just 3 working and 3 more projects that may never be finished. The issue im finding is when I make small changes and tweaks to the transmitter setup I have to remember to go update the others or they wont all work the same anymore. The downside is that each aircraft is slightly different in in what equipment they have because playing around with different things is sorta the point for me. So it makes it also not as practical to have a single profile and work around that for all aircraft of a type.

I am contemplating the same change for my tiny whoops with the same advantages and compromises.

So just wanted to see how others are managing this and what peoples thoughts are on why one way or the other.

2

For R&D I would keep at least one profile per aircraft (I tend to accumulate a few per vehicle if there are major configuration changes like switching telemetry configuration)

3

I use the same basic profile for everything, but I copy it and enable additional features/functions as needed for each different vehicle. I use model match (with ExperessLRS) to ensure I only bind very intentionally.

4

Arducopter (and other modern flight control firmwares) makes it easy to use a single profile, for they generally require no settings on the transmitter – no trims, no curves, etc. So a single profile can easily be used as the basis for each new model with changes only needed if you wish to add or delete a function switch.

1 Like
5

My system has evolved to the level I more or less have one basic template that copy for each type of drone. One for Arducopter, one for betaflight, one for arduplane, etc. I do often end up making individual models because I’ve been playing with different radio protocols and settings, but at least my important switches (arm, modes) and layout stays consistent for the type.

2 Likes