RottenRow

Have you tried flashing the receivers with the UNI firmware? This eliminates the issue of different ACCST versions and LBT etc. Note that with the UNI firmware, you can bind the newly-flashed receiver (so you get a solid green LED) but you won't get any servo operation until you activate it using a code that you get from T9 or Aloft Hobbies. Also, sometimes a receiver won't bind if it is too close to the transmitter during the attempted binding process. Try them a few feet apart. Brian.

Sometimes on plans, tucked away somewhere, is a statement such as ‘all wood is balsa unless otherwise specified’; it’s worth looking all over again, in case you missed this. Robin’s models are always of very lightweight construction, and he often uses the split fuselage design that the DC3 has. I used to have a Percival Prentice built from his plans, it flew beautifully but had stress cracks around that fuselage joint, due to the odd heavier than ideal landing causing the joint to try to open up. I intended to add some extra support across the join, but unfortunately the model was involved in a mid-air collision before I got to do that. Looking at the photos in that build article, I would be tempted to add some kind of fixing at the top of the fuselage, across the joint, so that the joint doesn’t try to open up there. Brian.

You can get it in paper form for £10 a year, 3 issues I think. I’m not sure when the next one will be sent out though. Brian.

It’s BMFA News, not RCM&E, that carries Bill Kits’ box advert. Page 58 in the most recent printed version (February 2024). Brian.

Are you using the same USB lead that you used successfully on previous occasions? I’m just wondering if there is something non-standard about the on-board USB socket. Brian.

It is each flier’s responsibility to ensure that he or she flies safely. In the scenario presented, it would probably be the flier whose model was involved in the incident who would be liable, not the club itself, though it wouldn’t bode well for the continued existence of the club at that location. If your club is BMFA affiliated (and keeps that affiliation up to date annually) then the BMFA insurance indemnified the club’s committee members against any claim. Regarding the dual use of the airfield, whether both model flying and kart racing can operate simultaneously would depend on the proximity of each activity. The BMFA should be able to provide advice on all aspects of this. Brian.

Component shop will supply packs with a choice of connectors, see here: https://www.componentshop.co.uk/9-6v-eneloop-2000mah-aa-square-2x2x2-transmitter-battery-pack.html If one of those doesn’t suit, either transfer the existing connector to your new pack as Paul suggests, or replace the lead inside the transmitter with one made from a servo extension lead (remove the white wire) and get a battery pack with a standard Futaba connector. That is what I do on the old Futaba Field Force 7 txs, where the original batteries had tabs that pressed onto contacts in the tx case. Brian.

It’s worth flashing those X series receivers with the UNI firmware. Do them all, then send a list of the codes generated in the Activate LUA script to either T9 or Aloft Hobbies and they will send you back a list of activation code. From my experience, that has usually been within one working day. Brian.

Martin, the 120 was a squat engine (short stroke), the finned part of the cylinder was noticeably lower than its diameter. Here is a photo of my 120. Yours is definitely a 150, an early one as it has the Super Tigre carb. You will notice that the finned part of the cylinder is much higher on yours compared to the 120. Those shown on Paul’s paper sheet are the older ones with the glowplug at the front (the ones that Jon could no longer offer support for when the company was running). Yes it would have been better if they had been stamped with their size during manufacture, one wonders why they were left anonymous. Brian.

That’s the conclusion I came to as well. I think in Steve (OP’s) case, it’s his older version of Open TX that is limiting the number of different protocols that the transmitter can utilise, even though they are all ‘inside’ the MPM. Steve is (was) reluctant to update his version of Open TX, but that is probably the only way that he will get his transmitter to see all of the protocols available within his MPM. Or he could update the version of ACCST on his tx to V2, then the R6 Mini should bind directly with it (in ACCST mode). I was unsure whether that removed the option of D8 (for his other receivers), but Mike has said that D8 stays. Brian.

Great answer Mike, that explains a lot about what Steve is finding. Just one more please… do the Archer Plus receivers require specific firmware for either FCC or EU(LBT) when operating in ACCST mode, or don’t they care which mode the transmitter is using, as long as it’s V2? Brian.

Yes, it looks like you've come to a dead end for the moment. Perhaps somebody with a better knowledge of the MPM will come up with something. The correct protocol might be in your module but your tx won't let you select it, I don't know how you can tell that is the case though. Otherwise, it looks like you'll need to update the ACCST version in your tx to V2 LBT. I'm unsure if you dont lose the D8 option then though, though you could use your MPM for that as you mentioned previously. Brian.

Steve, my tx has Open TX version 2.3.11 as opposed to your version 2.2.3. I would guess that somewhere between these two versions, extra support was included for the MPM to cover the extra protocols that the module now has. Your version of Open TX doesn’t have the full ‘library’ of protocols. There is a way of manually loading a protocol if it isn’t listed on your tx. You use the custom entry (under Multi) and enter the protocol number (64 for FrSkyX2), then the sub-protocol (2 for EU LBT). This is described on the github page under ‘Serial Mode’, just above the ‘Protocol Table of Contents’ A bit complicated to try to describe… This is what it says… If still not listed, use the Custom entry along with the protocol and sub_protocol values indicated by the italic numbers under each protocol. You'll find a summary of the protocols and numbers to use in table below. Brian.

That’s the information given on the BUSA website. Their models, like DB’s, are sport scale so some liberties may have been taken. One possibility is to allow the use of standard 36” wood for the spars, leading and trailing edges etc. Just a guess… I just looked up the DB model on their website, and that is 77” wingspan too! Mick Reeves’ accurate quarter scale Pup has a wingspan of 79 1/2”. Brian.

Steve, my MPM has a lot more makes and protocols than yours is showing. Yet mine has an earlier version number (V1.3.2.86) than yours. Is yours the JP 4 in 1 module (label on mine in picture)? I know there are other versions of the module, perhaps there are differences. The list of available protocols is on this site (you need to scroll down for the list): https://github.com/pascallanger/DIY-Multiprotocol-TX-Module/blob/master/Protocols_Details.md I’m not sure how that helps you much I’m afraid. Brian.