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

  • Hello, I'am having a strange problem when trying to configure the ftdi with the invert options in ftprog. It does the programming without giving any errors . however if I scan the device again after doing this, these settings are not retained. Watch my video here:
    Pls help
  • Having a project of refurbished parts ( http://www.spectra.com/hitachi/used-system/218/index.htm ) I'de say it's quite challenging to do so. Learning the firmware at first and knowing certain specifications on what hardware needed is initial.

    Used Hitachi HUS 110, 130, 150 Storage: Buy,Sell, Support
    Spectra buys and sells USED Hitachi HUS 110,130,150. 24/7 3rd party Maintenance, Post Warranty Support, and Repair Services.
  • IMPORTANT INFO:

    I was not able to flash my FrSky D4R-II using FTDI USB cable on Windows 7 or Windows 8 (it doesn't recognize my receiver and doesn't show receiver UID #).

    I was able to flash it only on Windows XP.

    You should use FTDI driver's version 2.8.14 or less (http://www.wut.de/e-3wwww-51-inus-000.php), otherwise newer drivers can make your FTDI device non-working by changing device PID to 0x0000 instead of 0x6001.

  • Can be such method used also with Frsky D8R v2    or   Frsky D8r-II  (not plus)   ?

    Flash file is the same ?

  • Ok here is my video

    https://www.youtube.com/watch?v=wLmObtlzqvY

  • Ok :) I tried to connect ... as  I wrote earlier while connecting the D4R-II with a BEC. Of course via FTprog, I inverted TX & RX logical state.

    I used this software http://rc-miskolc.emiter.hu/index.php?option=com_content&view=a...

    and Abracadabra ... TX RSSI, RX RSSI and AD1 (BEC) are displayed :).

    I also used RS232 data logger prog and it's capture frame too :)

     

     

    FrSky Config Program
    Magi István Modellező Weblapja.
  • @Jani. As being a rookie ... as you said, I just discovered recently that this port was in practice a mixture of two others ones. With which software can I capture such packets ? maybe with FTprog too or do I need to write my own one with a special API ?

  • Didn't know they also send raw RC packages there, just thought telemetry would go there. Thx for the info!

  • Developer
    Sebastien sure you can do that. Firsy you need to understand FrSky protocol and how they made it. There are two main protocols running ob that port. One main transfer proto and then Hub proto is encapsulated inside of transport.
    Jusy google frsky telemetry protocol and you will find protocol descriptions. If you cannot find, let me know and in can send those to you
    br,jani
This reply was deleted.