Binding Niight Vapor to Frsky Horus/multiprotocol module

[Geoff S]

I decided to treat myself to a new Night Vapor and it arrived this morning very promptly from Leeds Model Shop.  I had an old Vapor that was given to me needing repair but I haven't flown it for years (pre-Covid).  It's bit too far gone now, hence the new one.  As I flew the old one with my Horus/Multiprotocol module I just bought a Bind and Fly version.  Unfortunately, it will not bind on either DSM or DSMX.  I also use the Horus to fly my 400mm ws T28 on the V761 protocol and that still works OK.  I've tried distancing the transmitter from the model by about 2 metres to no avail.  Any ideas gratefully received.

 

I've had the Multiprotocol module for some years.  It has no controls/switches on it, just a mini USB port and a red and a green LED.  The green LED is on but the red one is flashing - not sure what that means.  I can't remember if I had to download the s/w for it.

[Kim Taylor]

Has the mpm firmware been updated at all?

I've heard of issues binding to newer Spektrum rx's on older mpm firmware. 

For binding to my Lemon rx, I find that I have to select the correct sub protocol (DX2 iirc), using 'Auto' doesn't seem to work

I'm using (iirc) version 1.3.3.20 - newer versions allow forward programming, so I'll have to update at some point, I suppose. 

Kim 

Eta newest version is 1.3.4.0

Edited December 28, 2024 by Kim Taylor

[Peter Christy]

Geoff: If you need to update the mpmodule, the easiest way to do it is from the transmitter itself. The difficult bit is locating the right version of the firmware!

 

Make sure you get the version where the channel order is the same as you use on your transmitter! As an ex JR man, I always used to make mine follow the old JR order of TAER, and I can't recall what FrSky's default is. This is important, as the module will re-map the channels for protocols that need it - Spektrum, like JR, is TAER, so if your FrSky is set to the FrSky default, you will need the remapping to make the throttle failsafe work on the right channel on some Spektrum gear!

 

Once you have identified and downloaded the right firmware, put it on the transmitter's SD card in the "Firmware" folder. Then if you select that from the system menu on the transmitter, it will ask you if you want to flash the external module and do it for you.

 

Saves a lot of messing around trying to do it from a computer!

 

--

Pete

 

[Geoff S]

I've tried updating the firmware - several times!  As Pete writes the hard bit is to decide which version to use.  I started with Futaba so my preferred channel order is aetr, but there's a whole host of different files with no real indication of which to choose apart from the channel order.  I doubt if that really affects initial bind anyway and that's my problem.

 

I found when I was selecting the right protocol on Multi that it got stuck on 'Assam' and wouldn't move. That meant I lost my V761 setting for my 400mm ws T28.  When I updated the firmware that problem  cleared but now it'll no longer bind to the T28, which it had earlier. I seem to be adding to my problems 🙂

 

Updating the firmware is quite easy as I eventually discovered.  I download the .bin file from Github and then into the Firmware folder.  I restarted the Horus after disconnecting from my PC and then it was just a matter of going to the Firmware folder and clicking on the file for it to be downloaded automatically to the module. 

 

However, I'm still in the same pickle.  I've had the plug-in module for probably 6 years and never bothered up dating it - in fact I'm not sure I needed to download the firmware in the first place.  I'll have a quick look inside to see if it's something silly like a broken  antenna feed and then, if necessary buy a new one.  It's cheaper than buying a Spektrum transmitter 🙂

 

Thanks for the help.  I've only been on this for 2 days!

[Peter Christy]

Geoff: You don't say which MPmodule you have, but if you go here: https://downloads.multi-module.org/ there is a handy little selector box to help you. If your module is not shown there (iRange?) you probably want the STM32 4in1 version. You probably also want the EU version, and it also allows you to select your preferred channel order.

 

Hope this helps!

 

P.S. The module type box is scrollable, though it doesn't look like it!

P.P.S. You also need the serial version to talk to Frsky or similar transmitters. The PPM version is for old JR Txs.

 

--

Pete

 

Edited December 29, 2024 by Peter Christy
P.S.

[Geoff S]

Thanks, Pete.  That link led me to exactly the same firmware I tried yesterday and which, sadly, didn't work.  I opened the box and the antenna connection looks to be fine and the rest is really, like a lot of things, unrepairable. I've ordered a new module.  The one I have has worked without problems for 6/7 years so I hope the new one will solve my problem.  It's only money (not a huge amount) after all 🙂

[Peter Christy]

If you want to send me the old one, I can try and flash it here and send it back to you. You might end up with two! 😁

 

--

Pete

 

[RottenRow]

Check the soldering of the connector that mates with the Tx Geoff. On my MPM this fell out due to almost no solder having been applied during manufacture. Resoldered and all was well.

 

Probably unlikely in your case as it appears to allow firmware flashing, but worth a look.

 

Brian.

[Geoff S]

4 hours ago, Peter Christy said:

If you want to send me the old one, I can try and flash it here and send it back to you. You might end up with two! 😁

 

--

Pete

 

 

Thanks for that, Pete.  I'll wait until my new one arrives in about a week (assuming the delivery is as prompt as they claim).  It might be worth trying.

4 hours ago, RottenRow said:

Check the soldering of the connector that mates with the Tx Geoff. On my MPM this fell out due to almost no solder having been applied during manufacture. Resoldered and all was well.

 

Probably unlikely in your case as it appears to allow firmware flashing, but worth a look.

 

Brian.

 

I never remove it (until now, that is) so any connection problems are unlikely.  My Horus tells me the module flashing worked but I might try it without the module fitted and see if it gets upset.

 

Geoff

[Peter Christy]

Geoff: PM sent!

[Geoff S]

I received my new 4 way multiprotocol  module this morning, 2 days before the original estimated date.  Considering I ordered it over the Christmas/New Year period that's excellent service from AliExpress.

 

It's a TRangeX.  It has a rotary switch, a mini USB socket, a 'Bind' push button and a red and green LED on the back.  It binds perfectly on MULTI V761 4ch mode for my mini 400mm ws T28.  It still won't bind to either of my Vapors!   I have an old, early Vapor with a very damaged airframe  that I was given a few years ago and I used to fly using the old module in my Horus.  The receiver board works (I think. Anyway, the LED flashes as expected) but it won't bind.  Neither will my new Night Vapor.

 

The external module settings I've tried are: DSM2 DSMX CH1 - CH8 (both with and without telemetry).  Also tried DSM2 DSM2 and DSM2 LP45.  I must be doing something wrong but I can't think what.  I'll take everything to the next indoor session and see if the new Vapor binds with a 'real' Spektrum transmitter but, other than that, I'm at a loss.

[Geoff S]

The new module arrived, fitted and tried with same lack of joy!  I took the Vapor to the indoor flying and it bound perfectly to a club-mates DX6i (unfortunately it's Mode 1  so I didn't get to fly it).  It also bound easily to a Jumper 16 transmitter.  Anyway, I've bought a clean looking DX6i on eBay as an easy solution.  It'll be handy for other models and my RF9.5 simulator.  I had one for a short time some years ago and sold it for about the same price as this one so it's not a big deal - about the same price as a new pair of trousers and less than a tank of diesel at £69 +p&p  🙂

🙂

[Ron Gray]

Instead of DSMX / DSM2 protocols, try PPM.

[Kevin Fairgrieve]

There was also a new "multi" LUA released in the last few hours. You could try replacing that.

Github link

 

Also attached here.

 

main.lua

[John Wagg]

1 hour ago, Kevin Fairgrieve said:

There was also a new "multi" LUA released in the last few hours. You could try replacing that.

Github link

 

Also attached here.

 

main.lua 8.66 kB · 0 downloads

Sorry to divert the subject but what does the  "LUA" file do?

Or do you have a link to explain it better.

I have a RM TX16S so is this relevant to me?

Thanks.

 

[John Wagg]

Back on subject and not sure if this is relevant.

Updating the MPM on my TX16S there is a choice of 3 firmware types = Air, Surface, EU(LBT).

I found if I selected the "EU(LBT)" that I lost some of the protocols. So I presume it lost some FCC protocols (non EU) ?

Selecting the "Air" version replaced the protocols that were missing.

Sorry I can't remember what was missing but the EU(LBT) protocols are still included.

 

[Kevin Fairgrieve]

The LUA is basically the code that tells the module which protocol to use. Specific to the Tandem so not needed on the TX16S

 

See the image for a sample of the code.

Edited January 18 by Kevin Fairgrieve
Wrong file format

[Geoff S]

12 hours ago, Ron Gray said:

Instead of DSMX / DSM2 protocols, try PPM.

 

Tried that to no avail. 

 

It's certainly odd and I'm sure I'm doing something silly.  Anyway, I've got the Spektrum dx6i I bought on eBay, it look like new and came very well packed. It's a bit limited on mixing and I'm yet to discover what channel the 'gear' switch or 'flaps' switch is on but that only affects models on Realflight. It works fine on the Vapor, though I haven't worked out how to program a switch to make sure I'm not on 'Safe'.  Though tilting the switched on model doesn't affect either the rudder or elevator.  The village hall we fly in isn't huge so we need to be able turn tightly.

[Mike Blandford]

What firmware and revision do you have on the Horus?

What should happen is you set the external RF mode to MULTI, the type to DSM, and the sub-type to AUTO.

Next start the Rx in bind mode, then select BND on the Tx.

The Rx should bind, and send back the specific DSM mode and number of channels to the Tx that then sets the correct parameters. You may need to try the Tx at different distances from the Rx for this response to be received, it is only sent once, so if missed, the bind doesn't complete properly.

 

There have been some receivers that won't bind unless the throttle channel is low enough (even needing a specific value).

With the MPM, depending on the firmware flashed, it may be doing channel mapping. DSM expects to see TAER. The MPM may be accepting AETR and automatically changing this to TAER when DSM is selected.

If the channel mapping is off, then you would need to configure your mixes to send TAER.

 

As a suggestion, you could try creating a new model, and set all of the first 4 channels to output throttle, making sure they all are then at -100%. Now try binding using AUTO.

 

Having looked at a pdf manual I note it says "make sure your channels don't exceed 100% when binding". Now 100% on DSM is 80% on the Horus, so a second test, with all channels set to throttle, is to set the limits of all 4 channels to 80%, then try binding again.

 

Mike

[Geoff S]

Thanks, Mike.  I'll look into that once I get fired up again.  I haven't updated the Horus firmware since I bought it which must be over 5 years ago - pre-Covid, anyway and I've just had to replace the RTC battery for the second time 😞.  Under 'Version' in the Sys it says VERS 2.3 12-otx (1eddde1f).  Which, I assume refers to the RF firmware rather than the Open TX.

 

When setting up the Vapor I changed the channel allocation from my normal AETR (my first transmitter was a Futaba and I stuck with that since) to the Spektrum TAER and the channel monitor confirms that.

[RottenRow]

A couple of things come to mind Geoff…

 

Firstly, have you set the internal RF to ‘off’ in the settings for the Vapor? I have noticed that you get a different set of protocols for the external MPM if the internal RF isn’t turned off. I’ve no idea why that is.

 

Also, as Spektrum uses model matching in DSM2 and DSMX perhaps that is somehow affecting the binding process.

 

Brian.

[Geoff S]

Internal RF is definitely 'OFF'.  The Horus binds to the Spektrum 'dongle' on my PC to allow connection to Realflight OK. The MPM  setting for that is Multi-DSM-X2F. 

[Geoff S]

Success, though I've no idea why!  I tried binding the Vapor with the MPM settings as above (Multi-DSM-X2F) and it worked.  However, I'd set up the Vapor with the Spektrum TAER channel settings but they were awry.  Throttle was on the elevator (CH3) which meant it was half throttle when I bound which was 'interesting' at the time.  In fact the channel settings were as my usual AETR (ie Futaba).  Once I'd reset my Channels then things got to be (almost) normal except that the rudder on the model was controlled by the Aileron control and not by the Rudder until I mixed them together. Now it works as it should.

 

The interesting thing is that in the Model Setup section there's a message immediately below External RF Mode, line which reads V1.3.3.20 AETR.  It seems the MPM translates the Futaba channel settings to the Spektrum TAER automatically, though what X2F means, I have no idea.