Mike Blandford

I wrote the firmware for doing the SPort device updating, originally for ersky9x firmware. It was added to openTx eventually, but forced you to upgrade to 2.1 to get the feature. For those using 2.0.15 to 2.0.19, I built versions of openTx using my original method, you can find them here: **LINK**. To access the feature, power on holding the two horizontal trims APART. You need to put the upgrade .frk file in a "Firmware" (no s) directory. You should be able to update the main firmware using the bootloader (which I also wrote), accessed by powering on holding the two horizontal trims towards each other. Mike.   Edited By Mike Blandford on 10/03/2017 22:30:19

I can wait, I'm still (slowly) building a BT Tempest. Will the 110 retracts be used for the Hurricane as well then? I also have a Black Horse Mosquito on which I'd like to upgrade the retracts. Would the 110 retracts likely be suitable for that purpose? Mike.

I've now ported ersky9x to the QX7. If you want to try it, go here: **LINK**. Mike.

I don't think this was ever picked up by openTx, but I have implemented the addition of a rotary encoder on the Taranis. On the standard Taranis, it replaces one of the pots while on the Plus, there is a spare analog input available. See this thread for details: **LINK** The three logic signals from the encoder are combined to provide a single analog value. The firmware then decodes the analog value to extract the original three logic signals. I have full support for this in ersky9x. Since the X9E includes an encoder, openTx already includes code to handle the menus, so it should port into openTx. Mike.

Yes, add me to the list to make 8 so far. Mike.

The EU limitation relates to use of the 2.4GHz band, in particular transmission. The Tx transmits a lot, so has to comply by doing LBT. The Rx doesn't transmit all the time, I think it is only every third receipt. As such, the Rx may well comply with the requirements as it only uses the 2.4GHz band a small amount. Mike.

For information, the EU-LBT (LBT=Listen BeforeTalk) firmware for the XJT that is the latest named: XJT_LBT_build151223.frk does support D8 mode to 'D' receivers and V-II receivers. As long as the firmware on your Tx offers D8 mode, then you may use this. I have this on an early Taranis and just checked it worked with a D8R-II. For those who don't know, I use ersky9x firmware (not openTx). FrSky have very recently released a new version of the XJT firmware (XJT_LBT_build161214.frk), but this is specifically described as for the Taranis plus since Nov 15th 2016. Quote from FrSky: "FrSky has improved the performance of the BK-RF board of Taranis X9D Plus since Nov. 15th, 2016. For those with production dates between Nov. 15th, 2016 to Dec. 23rd, 2016, if you’d like to use with LR12 mode (L9R receiver), pls flash the firmware to Ver161214." I'm not certain either when openTx added the support for flashing the internal XJT and/or external SPort devices. I wrote the code that does the flashing, but it was some time later that it was added into openTx, I think it may have been added to 2.1. Because many users didn't want to update to 2.1, I built versions of 2.0.15 through to 2.0.19 that included a "maintenance mode" (the method I use on ersky9x) that allows the required flashing. To access maintenance mode you power on holding both horizontal trims APART. If you want to flash one of these specific versions, go to: **LINK**, to get the download. On that post there is also a pdf document "SportFlash.pdf" with instructions on using the feature. Graham: Only the XJT module and 'X' receivers need firmware upgrading. Mike.   Edited By Mike Blandford on 07/01/2017 22:45:41

Is that the 4-in-1 Multi-protocol module. If so, have you updated the firmware on it? The default firmware it ships with may well not support the E010. Mike.

Simon, actually a car side light bulb is not a simple resistance either! When cold, the resistance is much less than when alight and hot. Mike.

Thanks for that testing. I've relayed this to FrSky and they are looking into the problem. Mike.

That's correct. If you have a servo on the throttle channel it is easiest to see if it moves once in a while, then change the throttle stick position and wait again. Mike.

Posted by Chris Bott - Moderator on 11/12/2016 12:48:57: Rx 1,2,5 & 6 work with my Taranis but 0,3 & 4 don't. V3 board in Tx. Could you test the non-working Rx numbers a bit more please? I've found that they bind OK, but then, after powering the Rx off and on, the red LED is flashing slowly indicating no signal. However, just occasionally (e.g. 5-10 seconds apart), the green LED flashes on and the servos jump to where the sticks are. Do you see this? I'm asking as I'm in direct contact with FrSky development and trying to help solve this (and other) problems. Geoff: Any chance you could also try some different Rx numbers please? Mike.

Curious. The XJT module works on 0, 3, 4, 7, 9, and 10 and doesn't work on 1, 2, 5, 6, 7 and 8, the exact opposite of the Taranis. Mike.

Geoff: I've something for you to try with your original Taranis. I was testing something (unrelated) today and so triede binding the S6R to my external XJT module in a 9XR-PRO. The bind was OK, but I was then surprised when the S6R didn't respond. I took the XJT apart and see it is the (old) V2 PCB. This XJT had been working with the S6R. On checking, I noticed I was using a "receiver number" of 1. I changed this to 0 (the value I had used previously) and the S6R bound and worked OK. I then pulled out my prototype Taranis with the internal V2 board and tried lots of RxNums. 0, 3, 4, 7, 9, and 10 didn't work but 1, 2, 5, 6, 7 and 8 did work. With the external XJT in the 'PRO, 0 and 3 work but 1 and 2 don't. I've still to check more values, another early Taranis, and I want to check a plus on lots of RxNums. Please try your early Taranis with different RxNums. Mike.

The website reports "Compatibility - FrSky Taranis X9D Plus/X9E/Horus X12S/XJT in D16 mode" for the S6R, so the non-plus Taranis is not included. I prompted them to remove DFT/DJT/DHT comnpatibility! Mike.

FrSky seem to have made a mistake on the S6R firmware download page. These are the files that were posted by FrSky when they just released their 161109 firmware for the S6R: S6R_20161109.frk - the non-EU version S6R_EU_20161109.frk - the EU (presumably LBT, as it's the only one for EU now) version And these are the files available at FrSky download page now: S6R_FCC_20161109.frk - the non-EU version S6R_LBT_20161109.frk - the EU / LBT version" These later files do not work properly! Mike.

Just fixed a bug so new versions posted. Mike.

I've posted further updates for SportSet here: **LINK**. I've posted both windows and linux(32-bit) versions. These also have the accelerometer calibration option in them, so, in general, I think they are complete as far as functionality is concerned. I may try to improve the "useability" in due course. Mike.

For anyone running linux, I've managed to build a copy of SportSet for Linux. I've posted it along with the windows version. Mike.

Note that if the magnets become weaker, they do not, automatically, cause the motor to lose power. What this does cause is the kV of the motor to increase. Mike.

I've posted another update to SportSet: Graphics for the mounting options added, I also reduced the size of the graphics data so the .exe gets smaller. Offset angle and enable values added. Single COM port selector with 'scan' button to re-discover available COM ports. This is useful if you start the program before you plug the STK in. Mike.   Edited By Mike Blandford on 24/11/2016 17:21:32

I don't think the antenna gain matters. The Regs refer to EIRP (isotropic), so assume the equivalent spherical radiation which, I believe, means assume the antenna is non-directional, so doesn't have any gain (which makes it directional. I can see a dip in the power rail that lasts for about 6.5mS when a DJT is operating. How much of this time the module is actually transmitting I don't know. Mike.

I'll need to check the exact time for which the 'D' mode transmits. Note that it is not the duty cycle that must be <10% but the MU (medium utilisation) that must be <10%. I believe the FrSky module, in 'D' mode transmit at 60mW, so thay are already only using 60%. Then they only transmit some of the time. Then they only transmit 3 times out of 4, the 4th time is used to receive telemetry data. Mike.

Of course an airspeed sensor would be useful for that, I was trying to keep it simple. You could always add some slow or delay (or both) to the second mix on channel 9. Then the change of the stabiliser gain won't happen immediately, giving the aircraft time to change speed. Mike.

An idea that might be useful. I'll try it myself sometime when I get my S6R into a model and fly with it! The stabilising gain, if set OK for low speed operation may be too high for high speed. Since the master gain is controlled by CH9, try reducing the gain as the throttle is advanced: CH9: +50% P2 Offset(50%) *-20% Thr Offset(80%) [a MULTIPLY multiplex mix] With the throttle fully down, the gain is as set by the pot (P2 in my case on ersky9x). With the throttle fully up, the set gain is reduced to 60% of the value set by the pot. You could use a curve rather than a fixed, linear reduction. Mike.