I have a strange behaviour. I built 3 converters. One for a FF7 with a DX5e module pulled from a DX4e. Working perfect. Then I built another two, same circuit. One with the small 1mW module, working also fine with a FF9 radio. And then I have my nemesis.

Built the same like the others, a DX5e module from a new V2 mcpx DX4e. I tried everything. checked the code. Checked the serial signal to the RF module. Built a serial interface with a Prolific chip, which is capable of 128kbit (reading the same data like when the module is connected to the DX4e back). When I try to bind, the RX changes flashing, and stops flashing. But afterwards the light does not get solid. If I plug the module to the DX4e back, everything works fine (I soldered a connector for testing on it).

The only difference I found so far is the time between 2 frames. With the DX4e it is about 21ms, with the arduino and T10CP I get 23ms. Can this be the problem ? The impulses of the serial communication are the same length, so the bitrate should be fine.

Are you binding to the MCPx?
It is fussy about the timing being too long, but will work with anything below 22msec, right down to 11msec.

Best time to use is 22msec. Works with everything I tried(AR61xx,AR7000,AR8000,MCPx, DSMx mode where applicable)
(This is the total time for the frame including the data packet, not the time from the end of the data packet to the beginning of the next one)

Need some help here.Want to get mode 4 on a DX6i which does not allow channel reassignment as far as the sticks go. Is there any way around this other than pulling the plugs on the main board and switching them. Another way would be to get a Turnigy 9 and stick a DSM2 module in it. Any other way?

I read on another thread (I think) that there is a bit of a binding procedure when you're talking to the radio? I can find or figure it out myself, but if anyone knows what that is or has a link handy, I'd appreciate it.

There are two kinds of modules. Some of them go into bind mode every time the module is powered up. Those are simple to use
The other requires a slightly different header to enter bind mode. Generally those ones require you to push in a stick or something like that on power up to enter bind mode.
Bind mode can only be entered on power up, not later.

You should be able to modify your Android app to display the value of the first two header bytes. to see what is going on.

Can you describe the hardware+software you are using to go from serial into the USB port?

@pmackenzie - Yeah I'll have to change my app to grab the first header bytes. Right now it just keeps displaying the next packet it finds. I have the kind of transmitter that requires you to press down on the stick to enter bind mode, so I'll have to sort that out.

I do give some description of my setup in the video description (which you have to go to YouTube for, instead of watching the embedded one).

But basically, I have a 3.3v USB to serial board (FTDI type) I got from Sparkfun.com, and I have the RX and ground on that hooked up to the data and GND lines of the controller.

Then I wrote an app that uses an open source FTDI library for android to talk to the FTDI chip. Its all pretty simple actually.

I'm using the standard Android development environment (Eclipse) that they suggest you use (and is free).