Developer

3689482320?profile=original

Introducing the Issue and the solution:

We've talked about FRSky's CPPM signal on this other post that compares it with a standard PPM signal. The issue is that originally FRSky's CPPM runs at 18 milliseconds. That short period has no space enough for 8 channels plus a proper sync pulse.

After carrying that issue to FRSKY, Jani came up with two FRSky's beta firmwares running CPPM at a 27 milliseconds period. We did test it at the DIYDrones Dev Team and it seems to work pretty fine.

Some guys at that old post were expressing their worries about the 37Hz update speed from the new custom firmware. However, keep in mind that probably you will not see any difference. Mainly if you aren't a crazily fast acrobatic pilot. Furthermore, our focus here is on drones. A good example is the Mission Planner that uses only 20Hz for joystick control.

Well, now those beta firmwares became official: There are custom firmwares for the receivers D8R-XP and D4R-II on their BetaTestSection. The links are now on FRSKY's download area. (Thanks Vladmir for the heads up).

D8R-XP_CPPM_27ms

D4R-II_CPPM_27mS

About the Updating process:

Inside of each update zip file there is a PDF explaining how to update your receiver. I'll not describe it here because it's pointless.

Reading their manual you'll see that an FRSky USB cable is necessary. That adapter is a TTL level "USB to RS232" one.

But what's the difference from that adapter and a common "USB to Serial TTL" one? There is just a single difference: the signal is inverted. FRSky's adapter uses the RS232 logic but not an usual RS232 high voltage level that would vary from -25V to +25V. Though the receiver's serial input has internally not just an inverter but also has a RS232-to-TTL voltage level shifter as shown on the diagram bellow (from FRSky's Two Way System Manual):

3689482264?profile=original

How to use an FTDI cable:

When I received the first beta firmware some improvisation was needed because I had no the required FRSky's adapter.

I've used my FTDI 3.3V cable with a little trick and it did work perfectly! All I did was configuring the cable to work with inverted input and output signals. ;)

Here goes how you can make that too (at your own risk):

First you need this powerful tool who did the magic: The "FT_PROG" from FTDI Utilities. It runs from a folder and doesn't need to be installed.

The first thing you'll gonna do is attach your FTDI cable and select "Scan and Parse" from "Devices" menu.

3689482381?profile=original

After finding the adapter the screen will be like this:

3689482282?profile=original

Now you'll navigate at the "Device Tree" selecting the "Hardware Specific" node for checking the proper options that will invert TXD and RXD (output and input of FTDI cable).

3689482333?profile=original

Now click on the "flash icon" as shown below:

3689482406?profile=original

On the programming screen click on the button "Program" and watch the status bar until it finish.

3689482287?profile=original

That's it! After the steps above you have a TTL inverted FTDI cable.

It's reversible, of course. You just need to follow the same steps but this time deselecting the inverting check-boxes.

You'll just need to use some jumper cables. The receiver can be powered  by the 5V output from the FTDI cable.

Remember of crossing the connection between your FTDI cable and the receiver input:

FTDI_TXD (orange) goes on the Receiver_RXD.

FTDI_RXD (yellow) goes on the Receiver_TXD.

If you'll flash your receiver... good look! =)

Please, add comments telling us about your experience on it.

E-mail me when people leave their comments –

You need to be a member of diydrones to add comments!

Join diydrones

Comments

  • I have the D8R-XP shouldn't be much different.  from top to bottom (GND/+/Signal) respectively.

    You can power the receiver as you normally do and just make sure not to use the power from the FTDI, that will work as well.

  • I see now, so on my ftdi.. just invert the tx/rx and connect to the receiver.

    take the +5v from USB-->FTDI--> to (+)Rail of the receiver... they are all connected, anyone gives power to the receiver.

    take the GND and put that on the GND of the receiver as well.  anywhere, they are all connected.  Just the signals are separate.  

    Hope that makes sense?

  • Let me clarify,  The data port on the receiver has Gnd, AD2, Rx, and Tx.  Of these 4 pins on the D4R-II Data Port,  what is connected to the FTDI Adapter?     In other words, On your set-up do you just have the inverted Tx/Rx, Ground and +5V jumped to a (+) terminal of any channel?  Just 4 Connections?  Also are any two channels required to be jumped together so the receiver knows it is in programming mode?

    Thanks,

  • Hello Cameron, I am not sure what you are referring to on the AD2?  are you talking about the A2 of the receiver?

    Nonetheless, I pulled +5V from the USB on the FTDI Adapter and alligator clipped it to the (+) rail of the receiver.

    Worked great.

  • Besides the inverted TX & RX, is the AD2 connected to the FTDI?  Or is the AD2 the +5V supply?

    Thanks!

  • Thanks Sandro, just curious. I find that the APM/Configuration screen is not so responsive to the joystick movements... is there some setting on the radio that has to be configured for the adjustment?

  • Works perfectly, Thanks for the post!

  • I am having the same issue as you, Scott.  I am using a Prolific (pl2303) USB-to-TTL.  I cannot invert the signal in software so I used a spare hex inverter to handle this.  I'm getting the same results: the UID shows up but the firmware load does not go past 2%.  One time out of maybe 30 or so it went to 5%.

    I will post here again if I manage to get it to work.

  • Just tried with a D8R-XP and got the same result. Got the UID but trying to download the firmware goes to 2% and no further.

  • @Sandro: Thank you very much!! Following your instruction and this info http://code.google.com/p/uavp-mods/wiki/FrSkyProgramming worked on the first attempt - and my FTDI is still working :) !!!

    Thanks!!

    Kraut Rob

This reply was deleted.