Mike Blandford

No! The RX6R uses a different processor and RF chip (all-in-one device). UNI firmware for the RX4R and RX6R is currently in beta test. T9 already offer the option to send in your receivers to have UNI firmware flashed, so they should be in a position to supply the activation code at some point. Whether they have this set up yet I don't know. Mike Edit: I use Firefox and on this site every post I make takes about a minute to take place!

The self install UNI firmware is now available (no cost): It is posted here: https://forum.alofthobbies.com/index.php?threads/universal-accst-firmware-is-coming.2252/post-39272 together with instructions. Receivers currently supported are: X8R, X6R, X4R, X4R-SB, RX8R and RX8R-PRO. Features: Auto-detect of protocol V1/V2, FCC/LBT. Mitigation of the "V1 bug". Auto-tuning to match the Tx frequency. The SBUS output may be swapped to be an extra servo output. VFR (Valid Frame Rate) telemetry value. Random telemetry errors eliminated. Map any channel to any output. Individually select servo outputs to be 18mS or 9mS rate. Supports dual bind. X4R may be configures to output CPPM. X8R uses the RSSI signal as an analog input (A2) with a voltage range of 0-3.3V. Mike

The unique ID is fixed for each Rx, it is obtained from the processor. I expect the script to be available for all of ETHOS, EdgeTx, openTx and erskyTx. The LUA script has been tested on openTx and erskyTx, a BASIC script is also OK on erskyTx. EdgeTx should be tested shortly. I'm not aware if there will be any cost for this firmware is flashing yourself, I've only just completed and tested the changes. Mike

We are beta testing this firmware on the RX4R and RX6R receivers. For these we have been testing a "user activation" feature. This involves users flashing the receiver themselves, then binding. At this point no receiver outputs work (no servo outputs, no SPort, no SBUS). You then run a script on the Tx that obtains a 12-character unique ID from the receiver. You send this to one of the main FrSky dealers (or possibly me!) and get a 6-character activation code back. Using the same script as before you enter this into the Rx and it is then fully activated and all outputs work. I've just completed adding this to the existing receivers that support UNI firmware (X8R, X6R, X4R, X4R-SB, RX8R and RX8R-PRO), so this method of getting UNI on those receivers should be available quit soon. Mike

If they are different makes, then you may find they default to different timing, which will likely result in different power levels out. Mike

Some of the ACCST receivers available from FrSky dealers (T9HobbySport in the UK) ship with the optional UNI firmware. This firmware auto-detects between V1 and V2 so you don't have that to worry about that with these receivers. Mike

It looks like ours is powered from our solar powered charge batteries. I flew with it operating this afternoon, no problems with the radio link. Mike

This is what the beacon looks like. I understand it is powered from a 12V battery. It transmits it's physical location and NOTAM data, so is able to warn full size aircraft of model flying activity. It is only switched on while model flying is taking place. - A full size aircraft, equipped with the appropriate display and software, will see a white triangle with height information. In the small image you may see 1.7 and +4.7^. The 1.7 is the height limit (1700 ft) and the 4.7 (4700 ft) is the minimum height the aircraft should attain, in this case as it has been set to 3000 ft clearance. Mike

I believe RM receivers are using FrSky protocol. As such they are using the CC2500 RF chip in the Tx module. The accuracy of the crystal in the Tx module is not as good as FrSky modules. It is possible that RM receivers also have lower accuracy crystals. Consequently, you do need to carry out the "Frequency Tuning" for each receiver. Have you done this? I have several multiprotocol modules. On the same, FrSky receiver, I need values between -40 and +40 for the different modules. Mike

How is your Tx antenna oriented? If it points almost straight at the 'plane, then it is having the minimum possible signal being sent. From some testing that was done on the universal ACCST firmware for FrSky receivers, a VFR of 60% is considered a low level, anything above that indicates a good performance. Control was, however, maintained even at a VFR of 10% ! Mike

Don't plug the Rx in until the updater screen is showing "finding receiver". The Rx only looks for an update for a very short time after it is powered on. Another way is to only connect ground and signal from the Rx to the STK, then power the Rx from a battery, get to the "finding receiver" stage, then connect the battery to the Rx. Mike

I'd use the sub-trim setting to set the middle position, then the min and max to set the endpoints. Mike

A "Universal" ACCST firmware is available for some FrSky receivers, see here: Universal ACCST Firmware Mike

It says it is a BLheli ESC with Dshot. If it is BLheli, then it is fully programmable with many settable parameters (the same as FrSky Neuron ESCs), but you need the BLheli app to run on your computer to set it up, and a special connection to "talk" to it. As it has Dshot, it may not support normal PWM input, Dshot is, I understand, a high speed method of sending the throttle information to the ESC. Mike

I've only just received my BMFA news and haven't read the article fully. Many transmitters are now storing radio and model data on a SD card. Since many 'phones allow a SD card to be used in them, I would be very surprised if using a 'phone near a Tx would corrupt the SD card contents. I would think the 'phone would corrupt its own SD card if that was likely to happen! Mike

I haven't got the internal module available yet, only external modules. Currently supported are XJT-lite, MPM-lite and crossfire/ELRS (yes to the IRX one). The way the dualboot works is to power up into the last used OS unless you hold the RTN button pressed at power on when it swaps to the "other" OS. Instructions are here: https://openrcforums.com/forum/viewtopic.php?f=7&t=13679 Mike

Potentially, the MPM (Multi-Protocol Module) will be supported by ETHOS at some in the future. However, NOW, you may include erskyTx on the X20 and get MPM support. I have arranged this so you have a dual-boot system, choosing between ETHOS and erskyTx. I don't have a X18 at present so this is only on the X20. With these radios you should not need to look at the screen while flying, just set up voice output. Mike

The Taranis (and plus) has a "soft power switch" that keeps power on after you switch off to make sure the EEPROM is completely written. What is happening is power is getting to the processor so it starts up, then detects the power switch is off, so just turns the soft power off. If you turn the power switch on, does the Tx operate normally? My guess is the resistor that holds the soft power switch off is not connecting to ground. This would allow leakage current to turn the power switch on. The processor would then start up and turn the power switch off, but would only hold it off while the processor was receiving some power. According to the schematic (rev 0.2 main board) I have, the resistor is R53 (100K), and pulls he gate of Q2 to 0V. As a first step, perhaps inspect the soldering of that resistor. Warning: The X9D+ has two, flat ribbon cables that connect to the main board. One of these includes full battery voltage. If, for any reason you need to disconnect these, unplug the battery. It is possible, while plugging these cables back in to connect full battery voltage to the processor, which will destroy the processor. This happened to me on a prototype X9D+. I replaced the processor and it then worked again. Mike

This is for testing the dual receiver setup only. When the Tx is using the receiver number of the main Rx, that Rx provides the servo control. When the Tx uses the receiver number of the "backup" Rx, the main Rx loses signal and so should use the SBUS data from the "backup" Rx and still provide servo control. This tests that both receivers are working and the main receiver is getting the SBUS signal from the "backup" receiver. For flying, you would bind both receivers using the same receiver number, with the "backup" receiver bound with no telemetry. Mike

There is a point of view that if the shaft needs to be cut off then you are mounting the motor the wrong way round! If you mount the motor with the fixed part on the firewall so the whole of the motor, prop and spinner are in front, then any imbalance in the prop and spinner will cause large forces where the motor is mounted to the firewall. I had trouble with a long motor (a 2832) mounted this way in my WOT4. No matter how well I tried to get the prop/spinner balanced I had significant vibration at high throttle. The solution was to build a ply box so the motor mounted with the fixed part forwards, so the motor body was behind the firewall and the prop/spinner were in front. This then means all the rotating parts are much closer to the mounting, and in my case completely cured the vibration problem. Mike

I have a model based on Wolfgang Matt's Superstar that I built and flew before 1982 with a HP61 for power. It is now electric powered and I still fly it. I have a "Unique Models" spitfire that I built in 1974. I never managed to fly it then I was trying to do it electric but an Astro Flight 25 (Ferrite) with 16 NiCd cells was too heavy. I have now flown it with a brushless/lipo setup. As I didn't like the foam wings with a straight leading edge (it just didn't look right), it now has a correct shape, built up wing, but the fuselage and tail is original. My WOT4 pre-dates 1997, first flown with an OS40 4-stroke (when I returned to model flying after a break), it is now electric and is still flown. I also have a scratch built model of 52" span, based on the Superstar design, that is regularly flown, I have pictures dated 2002 of that, and a scratch built electric glider, also with pictures dated 2002, that is airworthy, although I haven't flown it for a couple of years. Also an even smaller Superstar based scratch built model dated 2005. I had to build that one to replace a similar model that suffered a mid-air with a Laser powered Corsair. The collision was almost head on and the Laser just chopped my model up until the prop hit the NiCd power pack. Curiously the current model also suffered a mid-air, although this time it only lost half a wing panel and I managed to repair it. Mike

If you have two transmitters, bind each Rx to a different Tx, then if you turn the Tx bound to the RX8R off, the other Tx should then provide the control. If only one Tx available, bind the two receivers using different receiver numbers. If you then swap the receiver number on the Tx between the two, you should see one Rx lose signal and the other gain signal, but keep control of the servos. I believe the RX8R will use the data from the SBUS in if it misses a small number of packets (sent every 9mS), it may do so if only a single packet is lost. Given only 8 channels are sent in a single packet, and SBUS passes all 16 channels, it probably waits for a couple of packets to be missed. Mike

Even with a steerable tailwheel my BH mosquito was difficult to steer while taxiing (with larger wheels than in the kit as well). Because there is little airflow over the rudder, it isn't in the prop wash of either motor, I use separate channels for the two motors and have asymmetric thrust configured, enabled by a switch, so that while taxiing moving the rudder channel causes the motor on the inside of the required turn to slow down. Now it is very easy to turn on the ground. Mike

From things I've read, CH12 has to change much quicker than over 2 seconds, and CH3 (throttle) must be at -100%. Mike

What do you need help with for updating your D8 receivers? If I can improve the instructions I will do so. Mike