Binding D16 to crossover RX62H rx

[timrowledge]

I bought a crossover/oversky/mxo-co RX62H rx for an indoor model and I can*not* persuade it to bind to my X9E. It's irritating the hell out of me.

It was sold to me (by Great Hobbies, a well known Canadian supplier) as a FrSky D16 capable rx. Supposedly the binding process is

1. power up rx
2. wait for it to flash fast, indicating binding mode
3. power up tx & bind 'as usual for your tx'.

Nope. I've tried more times than I remember. With & without telemetry, with more & fewer channels active. I've tried D8, just in case. I even tried all the other protocol crossover advertise - DSM (including 2, x & X2 etc), FlySky (how many protocols do the *they* need?) and Futaba, all on my iRange MCM. I'm confident *that* is working since I use it for two other indoor rx, both DSMX based.

So if anyone has experience in making these little buggers work with D16, do please tell me what incantations you used, which sacrifices you offered, etc etc.

 

[Wayne]

We sold the Cross over for a while and the units we got worked well, but as I recall I worked with them for a correct firmware.

@Jarron Do you recall if we had D16 V2 for these?

Eventually FrSky came out with their own Micros (after chasing them for a few years) and we stopped offering the Crossover.

 

[Chris]

The units that we had had V1 firmware on them... We had to update them all to V2. As I remember it it was a pain in the A$$.

 

[Wayne]

Bingo - If you reach out to crossover they should be able to supply you with the V2 firmware and the programmer. We sent our last programmer off a while back to a customer.

 

[timrowledge]

OK, I'll see if I can get any help with newer firmware. And I hadn't seen the FrSky micros before; a real pity they didn't do one with a brushless ESC!

 

[Wayne]

It was debated. Frsky only wanted to do brushed or brushless and at this scale brushed actually makes good sense. If you have a little larger model that can accept a brushless setup, then you are probably OK to added a tiny brushless ESC. That was the thinking at the time of development. (Tiny brushless motors are still rather spendy these days and they can be rather sensitive to letting out the magic smoke with a hint of over amping.

 

[timrowledge]

Tiny update; I realised that the FrSky protocol on my iRangeX iRX4 module might be V1 - and it seems that it is since the rx actually bound. Well, sort of. It claims to have bound but the servos don't exactly cooperate - one doesn't move at all and the other only does intermittently.

 

[mlitke]

Tiny update; I realised that the FrSky protocol on my iRangeX iRX4 module might be V1 - and it seems that it is since the rx actually bound. Well, sort of. It claims to have bound but the servos don't exactly cooperate - one doesn't move at all and the other only does intermittently.

Were you able to get it to work? I have not (yet) tried with a RX62H receiver, but I saw a similar response with an RX42-F2 (RX145). I have an FrSky X14 with an iRangerX iRX4 lite (4-in-1) module (this one). In order to finally get it to bind _and work_ these were the settings I used for the external module (note: the X14 is on EthOS, not OpenTX) Type: Multimodule, FrskyX; Protocol: CH_16; Channel RangeCH1-CH8. If I remember correctly, changing the channel range (to 1-8) is what finally got the servos to respond (instead of sort-of responding and twitching). I have another radio running EdgeTX (the successor to OpenTX), and the settings to get the receiver to work with it are: Mode: MULTI; Type: FRSkyX; Subtype D16; Ch.Range CH1-CH16. I saw similar issues when using the DSM/DSX protocols (with different DSM/X receivers), until the set a smaller channel range, I could not get the servos to work right.

I believe the iRX4 does both ACCST V1 and ACCST V2. From the list at DIY-Multiprotocol-TX-Module, ACCST V1 is FrskyX, and ACCST V2 is FrskyX2. I have not yet tried ACCST V2 (FrskyX2), but I have used ACCST V1 (FrskyX).

 

[mlitke]

Bingo - If you reach out to crossover they should be able to supply you with the V2 firmware and the programmer. We sent our last programmer off a while back to a customer.

I was just hoping you could confirm, that what you are saying is that an RX62H-F2 (ACCST V1 version) can be updated/converted to an RX62H-F3 (ACCST V2 version) by just flashing new firmware? I would think so, since the hardware should be the same. If it can be updated, by "programmer" do you mean the MxUSB-PG02 usb tool (see attached)? Thanks!