FuriousFPV regularly releases new firmware for the True-D diversity module, which is deigned for the Fatshark Dominator. In this post we will explain about how to flash new firmware and update the logo. This guide covers:. Updating Firmware on V3 Modules (via Micro USB Interface).
With a passionate pursuit of performance and speed that define the bare essentials of micro FPV racing, our team of electronic and mechanical engineers from.
Updating Firmware on V1/V2 Modules (Via FTDI cable). Calibration (very important that you do this before first use, and after each firmware update) Updating Firmware on V3 Modules The new come with integrated USB port that allows you to update firmware much easier.
There is no more FTDI cable required. Connect micro USB port to a computer, a new COM port should appear (I use Windows 10). Download the following files from FuriousFPV’s website:. “XLoader Update firmware True-D Version 3”. One of the Version 3 firmware files with your favourite logo (I chose IntoFPV, because it’s my favourite forum:) ). Unzip both files and run XLoader.exe as administrator. In Xloader GUI, Select your firmware file (.hex file).
Set Baud Rate to 57600, and set the correct COM port, leave Device as “Uno(ATMega328)”. Hit “upload” That’s it! It should only take 10, 20 seconds until your module restarts and displays your new custom logo at start-up. Here is a list of custom logo’s available for the V3 module Updated on the 22nd Feb 2017. Create your own logo?
First you need to create a logo, then send it to FuriousFPV and they will create a custom firmware including the logo for you. Logo requirement:. file format: PNG. image dimension 128.64 pixels. logo max size – 128 pixels by 54 pixels (leaving at least 10 pixels at the bottom).
colour must be black and white. Email – sales AT furiousfpv.com Is there V3 firmware for V1/V2 modules? The firmware used in the V3 module is also available for the V1/V2, the firmware number is V2.1. The following instructions should work, only difference is you should now download the V2.1 firmware to upload.
Update True-D Firmware on V1/V2 Modules First of all, can V1 and V2 True-D module update to new firmware? The answer is yes by using a FTDI cable. New module you buy in the future should come with USB port, so there is no need for a FTDI cable. However if you already own the V1 or V2 module and wish to update the firmware, this guide might help you. (Warning: I take no responsibility for damaged module during firmware flashing, flash at your own risk. Please Consult FuriousFPV if in doubt) There are more than 1 way of flashing, one way is using XLoader.exe, which we use in this guide. Another possibility is, explained by FuriousFPV. You will need this (only $3!).
Download Furious Fpv Drone
And in this guide we are using Windows 10. Download Firmware 2. Open Xloader.exe Xloader.exe is located in: UpdateFIRMWARETRUEDREV2.0 XLoader XLoader.exe 3. Load Hex File, and Xloader Settings Find the.hex file “TrueDREV2.0” inside the folder FIRMWARETRUEDREV2.0 UpdateFIRMWARETRUEDREV2.0 FIRMWARETRUEDREV2.0 TrueDREV2.0.ino.hex Set Device to ATmega328, and Baud Rate to 57600. Make sure you choose the COM port of your FTDI adapter.
Connect FTDI Module with your True-D module Remove the white plastic piece from the module, and you should see the 6 pins next to the antenna connectors. Pinout is DTR,TX,RX,VCC,CTS,GND (from left to right). TX and RX should match on the FTDI and True-D, i.e., TX to TX, and RX to RX. On the FTDI module you can select 3.3V or 5V. I use 5V because when I chose 3.3V, it doesn’t power up the module.
Screenshot from FuriousFPV’s tutorial video When FTDI and True-D are connected correctly, you should see a solid green LED on the true-D and it should power up like normal. Flashing On Xloader, select the COM Port of the FTDI, and press Upload. FTDI lights will start blinking rapidly indicating that it’s talking to the True-D.
Flashing will take a minute, when it’s finished, it will say “done” at the bottom of Xloader. Note: Do not remove connection, or power down devices during firmware upload, it might damage your True-D. If it get stuck at uploading it could mean your TX and RX connection are reversed, or these pins are loose.
Double check and try again. True-D Module Calibration Why Calibrate True-D? It’s important to calibrate your True-D diversity module when you first receive it. Also it’s necessary to calibrate it again every time you update firmware. You should also try calibrate it first If you find symptoms such as. smart search function not working. screen rolling issue.
worse signal overall True-D Calibration Procedure. Remove both antennas from True-D. Power on your quadcopter (with VTX and FPV camera). Move your quad about 5m (15ft) away from the True-D unit.
On the True-D unit, press the middle button and navigate to SETTING and select CALIBRATE. After calibration, make sure the lower value is within 155 to 205 and upper value is within 380 to 440. If values are correct, press SAVE and EXIT, if not need to re-calibrate again. Edits History Update (16/Nov/2016): I’m having trouble flashing one of my units, when using XLoader, it simply gets stuck at uploading, and FTDI adapter LED doesn’t flash (no data activity). When using OSDconfig, it returns an error saying “Failed to talk to bootalder”. I am looking for a solution and when I manage to fix it I will come back and update on this page. Update (20/Nov/2016): Some people having issues of “failed to talk to bootloader”, or stuck uploading error, was able to flash their modules by performing “timing trick).
Basically, if you are using XLoader, you should hit upload as soon as you power up the module, and if you use OSDConfig, you should load the firmware file as soon as you power up the module. However so far only modules of Rev01 and Rev02 confirmed they were successfully flashed their module with timing trick, Rev00 are still having this issue. You can find the Rev version under the screen, it’s printed on the PCB. See for detail.
Update (22/Feb/2017): Added instructions for True-D V3 modules. Update (13/Apr/2017): Added Calibration instructions. 23 thoughts on “ FuriousFPV True-D Diversity Receiver Module Firmware Upgrade”. SteveA I was having all kinds of trouble updating a Rev01 board. The boot timing issue fixed the problem, but I was going wrong on applying the power.
I was thinking that plugging the USB in was a good way to turn the power on and off to the board. Beefjack guild wars 2 announced for machine. The solution was to connect all the wires to the VRX except the power and then plug the USB into the computer. Once everything is recognized in the Xloader, then I connect the power pin and do the update.
↓. Mike S Did some searching around, looks like the older hardware (V2) is listed as not compatible with the newer V3 firmware I did successfully flash v3.2 firmware onto the V2 module, but it was not fully working. The module would boot up just fine, and switch across (a limited number of) channels, but was limited to just that function – scrolling through channels, no main menu or other options on wheel click. Any idea if they have (or are close to having) a solution for the older hardware? It’s been a while, they are on 3.2 already Would be great to have the white flash elimination on older hardware. Thanks for the great site!!
I had a weird video problem that looks very similar. Now I'm starting to think the problem IS the TrueD. I was kind of suspecting it was the problem.
Im guessing the trueD rebooted or something. Because if you watch your vide feed plugging in, you can see very similar video behavior. Maybe the power supply in the goggles is not up to the task? Check my post.
Go to the very end of the video. EDIT: What are you showing at the end of the video? Was the module doing something weird? No just showing that it was the True-D in my goggles. That video was made for the tec at true-d. For what reason they wanted to see it i don't know.
Cuz they are still not stepping up. The tec sent a mail lastnight, asked if i contacted the reseller. Ummmm I sent you a forward of all 18 emails of both the reseller and the true-d tec, YOU!
So i don't know if he don't know how to read, or is a bot! Lol sad sad sad Just watched your vid, yeah mine did that alot before it crapped out. Nice flyin spot. At this point i don't know if id use it even if they sent me a new one. But i can still bitch at them. No just showing that it was the True-D in my goggles.
That video was made for the tec at true-d. For what reason they wanted to see it i don't know. Cuz they are still not stepping up. The tec sent a mail lastnight, asked if i contacted the reseller. Ummmm I sent you a forward of all 18 emails of both the reseller and the true-d tec, YOU!
So i don't know if he don't know how to read, or is a bot! Lol sad sad sad Just watched your vid, yeah mine did that alot before it crapped out. Nice flyin spot. At this point i don't know if id use it even if they sent me a new one. But i can still bitch at them Thanks. Its a super fun spot. I have been flying there for over a year now and still have fun.
Sorry to hear about you getting the runaround. From what I understand the buisness is located out of Vietnam, so English not being their first language can probably explain weird responses from them. I have a buddy that emailed them recently asking for a manual for one the old models and they responded with 'What problem are you having' lol So relieved to hear that yours did the same thing before it crapped out. Relieved because I REALLY didnt want the problem to be my craft or goggles. Mainly the craft since I have had soooooooo many problems with it and I just put a whole new setup on it.
Lol Bummed a little bit signs are pointing toward the TrueD though since I really liked having diversity in one module. Thanks for your response.
I have tried the 2.2 version but when flashed i still see 2.1 version? The file i used is.
Firmware FW2.2 for True-D V1/2 (FURIOUS FPV logo) 5/04/2017 when it was posted on there site?is this the correct file? I just answered this in the pm you sent me; Yes that sounds like the right file and is the same as I used. On the Furious download page it is listed as 2.2 and date is 5/04/2017 If your firmware update is successful you will see 2.2 on the startup screen.
If you do not update it correctly (lots of youtube vids or see oscar's website, google furious v2 firmware update) you will see whatever previous one you had. Hope this helps mate. I just answered this in the pm you sent me; Yes that sounds like the right file and is the same as I used. On the Furious download page it is listed as 2.2 and date is 5/04/2017 If your firmware update is successful you will see 2.2 on the startup screen.
If you do not update it correctly (lots of youtube vids or see oscar's website, google furious v2 firmware update) you will see whatever previous one you had. Hope this helps mate.
Tom I got 2.2 installed on receiver.was strange though after flashing it never said on xloader that was complete,it just acted like it was still loading file,never said so many bytes received?then on screen it was flashing a locked screen,but I was able to unlock In menu it shows same menu as before?is this normal? Also top reads like 208 and bottom 103 after calibration? Yes 2.2 at startup screen though. Shen, Those calibration #'s don't look right. They should be; - Min: 190 ± 30 - Max: 400 ± 40 Maybe you have not followed the calibration instructions properly or maybe your firmware update did not work properly. It should not just hang and say nothing like your's did.
Maybe check out the tutorials and try again. Sorry mate but I really cannot help you further with this. Good luck sorting this out and cheers. Tom I went back and deleted all files and d/loaded them again and the flash went perfect.no errors All seems good now. Nothing new for updates or versions in a while. Wonder if they're still working on improvements I've noticed this too, but I wouldn't be surprised if FFPV is working on something entirely new and different.
With the RC Split, SmartAudio, micro CCD cams, BF OSD, and other new video technologies I get a funny feeling something new is on the horizon that might exploit all of these features via the VRx. Furious would be the ones to pull the trigger too. They haven't been intimidated by potential flops, and I like that about them. Crossing my fingers and toes. Got my Furious True-D V3.5 yesterday and installed it in my Dominator V3's, which has been working flawlessly with nexwave module. What happens now is no picture on antenna/module A. Just grey screen as if not powered.
When True-D switching to antenna/filter B picture is just fine. Running fw 3.5. Anyone having any idea what the problem might be? Is the A module dead? Shouldn't I get some errors or something from unit display. Signal strength showing 100% and diversity/switching antennas are working correct but no picture on A module.