MPM Model Program Manager enables you to manage the setup programs you have in your computer radio control transmitter.

As a very minimum, MPM gives you a backup and restore facility, but offers much more.

All the programs are stored in a MPD file. Each MPD file is tied to a transmitter type. This is because MPM can deal with a number of transmitters. You can have multiple MPD files for the same transmitter if you really want to but we do not advise it. Each transmitter type is supported by a MTH handler plug-in. You need at least one. The MPD file contains a list of models shown in a MPD window of MPM Figure 1. Models are shown in a similar way to folders and have a name of your model. Each model name must be unique in the database

Each model contains a tree of versions. At a minimum, you would have one version. However, you can have many versions allowing you to store a number of versions of the same model. This allows you to experiment with the setup for the model or to store different setups for different configurations for the same model.

The tree of versions is used to show where a version has come from version history. In this way you can easily move between versions as changes are made. We advise that you use this to store changes as you make them so that you can revert if something does not work. The organization of the tree is completely up to you. One way may be to have major versions at the root and derive minor versions from there. Alternatively, you may want one long chain, but this can be difficult to maintain. You can always drag a version from within the tree and drop it elsewhere in the tree. It is also possible to use drag and drop to copy a version tree from one model to another. In this way you can creaate a new model and start from a known starting point.

Each version within a model must be uniquely named. When you create a new version, MPM will put you into the editor to enter a new name and will check that it is unique for that model before accepting it.

Each version of a model has a data entry for the actual data of the setup and a number of annotation icons.

With each version of the setup for a model, it is important to record what changes you made from the version it was derived from. Annotations allow this. You may have many annotations within a version and you would use this to keep a journal or log, perhaps a flight log or just somewhere to make notes about your model.

Each MPD file also contains a number of LoadLists.

A loadlist provides a mapping of your database of models and versions to your transmitters. The LoadList is used as a list of what to load into your transmitter. You can load different versions of the same model if you choose. This enables you to use different configurations of the same model allowing you to experiment. Alternatively, you can use versions of different models, particularly if you have many models, taking a sub-set out at a time. This is of great value with a transmitter of limited memory capacity.

MPM remembers which load list you last used to set up your transmitter. You must tell MPM if you are using one transmitter or more. With one transmitter, MPM knows the last LoadList that was uploaded was to the transmitter. With more than one transmitter, MPM must be able to distinguish transmitters. With some transmitters, MPM can do this automatically, but with others it will need to prompt you. When you next connect your transmitter to MPM, MPM will be able to detect changes you made on the transmitter and give the chance to create a new version and save the new data.

Future Features

In a future version, MPM will be able to tell exactly what changes you made and show the differences. MPM will also be able to show differences between any two versions (even across models).

Also, MPM will be able to offer a full editing facility graphically, allowing you to edit assignments, mixing, modes etc and channel signal routing (depending on your transmitter’s features). MPM will also offer a transmitter mimic. The mimic will show the transmitter and allow you to move the sticks and switches. It will also show the channel servo outputs (either as bar graphs, percentages or as a servo arm) so you can visually check the stick to output function.

MPM will be able to support, in a limited way, migrating setup data from one transmitter to another allowing you to take some of the pain out of upgrading your transmitter.

For more details, contacts us at Denveralde Products.