Kevin Fairgrieve Posted January 13, 2015 Share Posted January 13, 2015 Version 2.0.14 / 2015-01-12 [Taranis] Fixed blank LCD screen at very low temperatures Shortened radio reboot time in case of watchdog reset Fixed timer problem in bootloader, which prevented radio from powering off after being connected to USB Fixed issue with heli swash plate mixing when using notrim Various fixes for double-keys Added switch auto detection in Timer source Totally removed splash screen display if duration is set to --- Back-light turned on sooner at startup (Taranis +) Fixed reverse polarity on external CPPM output Suppressed center beep fo r non-existing pots Fixed THt persistent timer running after model load (with Throttle at -100%) Fixed buffer overflow for automatic flight mode change audio announcements (if very long model and flight mode names were used) Limited stick throws to 100% when using trainer in add mode Fixed Lua lcd.drawLine(), first pixel was not drawn Fixed missing last column for some bitmap sizes Minor display corrections [9XR-PRO] MAVLINK adaptation [9XR] Added 115200 bps speed to MAVLINK [9X2561] PWM backlight fixed [All] Various texts and translations corrections Various small bug-fixes I will be updating mine later today. Kev Quote Link to comment Share on other sites More sharing options...
GONZO Posted January 13, 2015 Share Posted January 13, 2015 Before you update be aware that, as I understand it, the 2.0.14 version will alter your internal RF unit to the new standards(EN300 1.8.1) which may mean some of your old Rx may not work and will also require updated firmware. Also, there have been reports of problems with the update **LINK** Read from post 39120 onwards. HTH Quote Link to comment Share on other sites More sharing options...
Kevin Fairgrieve Posted January 13, 2015 Author Share Posted January 13, 2015 Well I went ahead and did the update!! All seems to be OK except that I have lost screen 8 on the setup menu. Stick and pot calibration. Will wait for the new download that is expected later today!! Kev Quote Link to comment Share on other sites More sharing options...
Kevin Fairgrieve Posted January 13, 2015 Author Share Posted January 13, 2015 Copied the update file to the SD card and installed from there. All screens now visible and working. Bootloader also updated. Can confirm that no RX needed to be re bound to the TX. Kev Quote Link to comment Share on other sites More sharing options...
PatMc Posted January 13, 2015 Share Posted January 13, 2015 Kevin, have you checked that X series Rxs work in D16 mode ? Quote Link to comment Share on other sites More sharing options...
John Privett Posted January 13, 2015 Share Posted January 13, 2015 Was just about to ask that Pat! Somebody (possibly here, possibly somewhere else) posted a link to a compatibility chart (I'd put the link here if I knew where it came from... I downloaded a pdf file from it!) That shows that X series rxs need to have the latest firmware loaded too to work in D16 mode, but will work in D8 mode. (All my rxs are X4R, X6R or X8R and bound in D16 mode.) If the rxs do need the firmware updating, what leads do I need - there seem to be two required unless I'm mistaken. I realise I don't need to update anything immediately, but I presume that any additional rxs I buy in the future will already have the Euro-compliant firmware, so I'll need to update the tx (and hence all existing rxs) to use them. Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 13, 2015 Share Posted January 13, 2015 Can anyone put a link to where it's said that the XJT rf module gets updated? I know one of the developers had an add-on for the firmware that allows the module to be updated via the SD card but I would be surprised (and disappointed) if any firmware version updates the module by default without any user interaction. The rf module firmware update has been entirely separate from the opsys firmware to date. Edited By Bob Cotsford on 13/01/2015 21:26:39 Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 13, 2015 Share Posted January 13, 2015 looking here it sounds like the earlier issues revolved around the bootloader - the Taranis' startup routines that load OpenTx and give the optons to update OpenTX from SDcard. Quote Link to comment Share on other sites More sharing options...
PatMc Posted January 13, 2015 Share Posted January 13, 2015 John, this is the compatibility chart **LINK** Bob, according to the chart if an X series Rx that doesn't have the new firmware works in D16 mode to a 2.0.14 version Taranis then the firmware hasn't been altered in the Tx. Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 13, 2015 Share Posted January 13, 2015 Posted by PatMc on 13/01/2015 21:16:25: Kevin, have you checked that X series Rxs work in D16 mode ? that's the $64k question! Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 13, 2015 Share Posted January 13, 2015 Ok, just for kicks and giggles I've just updated Companion to 2.0.14 and updated the tx to OpenTX 2.0.14 - result? D16 mode still works ok. Quote Link to comment Share on other sites More sharing options...
Kevin Fairgrieve Posted January 13, 2015 Author Share Posted January 13, 2015 For those who are interested. All my X6R RX still work fine. Still to check the couple of X8R though. Kev Quote Link to comment Share on other sites More sharing options...
Biggles' Elder Brother - Moderator Posted January 13, 2015 Share Posted January 13, 2015 Waiting with baited breath here Kevin. All my Rx's are X8R's and, like John, they are all bound D16. I haven't updated deliberately so I'd be interested in hearing about it. Like John I'm also interested in if anyone has tried updating the firmware in a Rx, how it went and how they did it. BEB Quote Link to comment Share on other sites More sharing options...
Chris Bott Posted January 14, 2015 Share Posted January 14, 2015 2.0.14 didn't last long did it? Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 14, 2015 Share Posted January 14, 2015 Are people getting confused between OpenTX (operating system) upgrades, bootloader firmware upgrades and RF module firmware upgrades? I am pretty sure that OpenTX updates so far are not touching the RF module, and it's the RF module updates to comply with the latest 2.4 GHz regulations that affect whether or not existing receivers work. As I see it: If you use components bought before 01/01/2015 then you can update both OpenTX and the Taranis bootloader to your hearts content or you can simply ignore the updates if you are happy with the way it works as supplied. These updates are done either through Companion, or with OpenTX v2.x you can put the update on the SD card and use the update mode on Taranis to load it. If you buy a new X series receiver in Europe from 01/01/2015 it should have the revised ACCST protocol and you will need to update the RF firmware in the Taranis and any older X series receivers or XJT transmitter modules. This is currently done by using the FRUSB or the older serial cable plugged into a PC port and running Frsky_Update_Sport.exe. Looks like the latest version is just to fix the issues in Companion mentioned at the start of this thread: Version 2.0.15 / 2015-01-13 Nothing new (only Companion fixes) Edited By Bob Cotsford on 14/01/2015 08:12:26 Quote Link to comment Share on other sites More sharing options...
Chris Bott Posted January 14, 2015 Share Posted January 14, 2015 I agree completely with what you say Bob, thanks for saving me some typing . I think there will be some "old" X series receivers on shop shelves for a while too. Quote Link to comment Share on other sites More sharing options...
Kevin Fairgrieve Posted January 14, 2015 Author Share Posted January 14, 2015 Just tried a small experiment. Flashed a X6R RX to the new firmware from the FrSky website. Here. I then tried to bind it to my TX. No joy. Looks like I wil need to flash the TX as well if I want to do all my RX. But is there a need? Apart from now I have one bricked RX, unless I can roll back the update. Kev Edited By Kevin Fairgrieve on 14/01/2015 09:38:38 Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 14, 2015 Share Posted January 14, 2015 oooh! - that's a bit of a pain that they don't have a rest-of-the-world firmware for the X6R! There are vanilla versions of the firmware for X8R and X4R - is it worth an email to FrSky asking for a vanilla X6R firmware to restore yours? Might even be worth flashing it with the vanilla X8R firmware as there is a line of thought that the 6 is just an 8 with less sockets fitted Quote Link to comment Share on other sites More sharing options...
flight1 Posted January 14, 2015 Share Posted January 14, 2015 I have flashed my tx and all x series rs to the new firmware (ETSI EN 300 328 V1.8.1) and all works fine. Had an old d4r 11 rx and that just needed to be rebound. Falshing the firmware for the recievers and the tx tranmission module are compleatly seperate to the boot loader and open tx updates. Here is a compatibility chart someone else has made http://www.rcmf.co.uk/4um/index.php/topic,102172.0.html (fourth post down), very use full. You need the FUC-3 and SPC cable. to flash firmware and the FrySky sport updater program and of course the relavent firmware. If you don't buy any new recievers then there is no need to update but all new RX bought will have the new euro firmware and your Tx modual will need updateing and all you current Rx's . Quote Link to comment Share on other sites More sharing options...
PatMc Posted January 14, 2015 Share Posted January 14, 2015 Kevin, Your X6R Rx should work in D8 mode until you update the Tx to ETSI EN 300 328 V1.8.1 then it should work in both modes. Flight1, that's the same chart that I linked to yesterday. Edited By PatMc on 14/01/2015 10:34:09 Quote Link to comment Share on other sites More sharing options...
Kevin Fairgrieve Posted January 14, 2015 Author Share Posted January 14, 2015 Posted by Bob Cotsford on 14/01/2015 09:53:36: oooh! - that's a bit of a pain that they don't have a rest-of-the-world firmware for the X6R! There are vanilla versions of the firmware for X8R and X4R - is it worth an email to FrSky asking for a vanilla X6R firmware to restore yours? Might even be worth flashing it with the vanilla X8R firmware as there is a line of thought that the 6 is just an 8 with less sockets fitted Have contacted frsky for that. Then I came across this on there forum. "Hi, if the firmware of your receiver is the EU fw, you can downgrade to the old firmware. The old firmware will be released to our website, and the X8R firmware also can be used to flash X6R, but X4R/X4RSB is not, now we don't have plan to release a new firmware for D series, and the firmware for EU FASST compatible receivers will be released in recent days, please be patient." So all is not lost. Kev Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 14, 2015 Share Posted January 14, 2015 I thought I'd seen it somewhere! Quote Link to comment Share on other sites More sharing options...
Kevin Fairgrieve Posted January 14, 2015 Author Share Posted January 14, 2015 Reflashed the X6R using the X8R firmware. Available from the frsky web site. **LINK** All working again with no need to rebind. Kev Quote Link to comment Share on other sites More sharing options...
GONZO Posted January 14, 2015 Share Posted January 14, 2015 Looks like I was wrong with my original assumption that the internal RF unit was changed to the new EU spec on update 2.0.14. Seems now that a separate action is called for, or have I got it all wrong again? From what FrSky have said concerning the D series firmware, lack of and no intention to change. Am I reading too much into this by assuming that the 'D series' is starting to be phased out.? Quote Link to comment Share on other sites More sharing options...
Bob Cotsford Posted January 14, 2015 Share Posted January 14, 2015 Mr G, in Kevin's quote from FrSky they state that a D series update is not in the pipeline. I guess this would be needed for future production as the telemetry return signal must be over the 10mW allowed without look-before-transmit, so you may be right. I think what caught you out originally is that there was a problem with the bootloader update method. I did notice that 2.0.14 looks to download 2 files to the transmitter, must be one for the bootloader and one for OpenTX. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.