FYI - The latest MPX update to version 3.3 on EVO Pros apparently manages to lock out modules such as XPS. In prior versions (up to 2.62) it was possible to get the EVOs to work by shorting pin 2&5. With the new update this seems to no longer work. Is this true? Are there any options to upgrade this in the future or have MPX managed to lock XPS out of their market?

It causes quite some anger with EVO users. Apparently Multiplex is trying to shut out the module suppliers with software to push their new M-link. It took Multiplex several years to implement minor upgrades in software on their old EVO but apparently when it comes to protecting their market they can come up with updates in a rush and did not even announce what they were up to...

This is also stopping some flight simulators from working the pro upgrade. If so it may also effect the training mode in the pro so the two transmitters won't talk to each other.
If Evo did this on purpose, its a bad move on their part but who knows, they may have screwed up by releasing a bad upgrade. Well see what drew says once he gets a handle on what's happening. I'm looking for a new radio that will work with XPS as I like their receivers and the new ones they're coming out with. I'm still hoping there is a new XPS radio sometime in the future Rather than another Graupner.

Just got back the EVO from Hitec yesterday. I am going to see if we can make a single wire solution. If not, then people will have to add a second connector to our board (the spot already exists for it).

I can see that people manage to make an interface to communicate with MPX 3.3 software and also send telemetry data back to MPX. I also read that JETI is working on it. Do we expect XPS to evolve their TX module to speak MPX anytime soon?

We already have it working ourselves. I am finishing the telemetry code for the transmitter modules. Most people don't realize that we have had the ability to get telemetry data back to ALL of our transmitter modules. When we announced this capability several years ago, everyone wanted PC support. Nobody cared about transmitter telemetry until other companies started doing it, and then everyone wanted it... go figure.

So, I have created a fake MLINK module in software. The new firmware upgrade will require that you attach two wires from our telemetry port on the transmitter module to the EVO's module port.

When we announced this capability several years ago, everyone wanted PC support. Nobody cared about transmitter telemetry until other companies started doing it, and then everyone wanted it... go figure.

So everybody wanted to bring their laptop to the field and have a buddy keeping an eye on the screen and report any important data to them while flying, and nobody wanted the cute little device that could be attached to the Tx with LCD panel, bright warning LED's, SD card for data recording and headphone socket?