DX8 and AR8000 and AR6200 Binding problem

[johnsandywhite]

My son has 2 Raptor 50 Titans that he set up with his brand new DX8 and AR8000 Rx along with telemetry on both Helis. He has been flying them for the last 3 months without ANY problems. However, due to people mentioning that after any major programming alterations he should re-bind, last night he did so on his best Raptor. It would NOT bind in with the AR8000 and now will NOT bind in with a spare AR6200. Both receievers will not bind with my Transmitter either. Prior to his trying to re-bind, the Tx always showed it as connecting to a DSM2. Now it shows DSMX no matter what changes we make it the service menu.
Both his and mine have no problems binding to normal DSM2 Receivers.
Some time ago he updated the DX8 with 2.03 but had problems and has now gone to the 2.01 version.
We are tearing our hair out (i've not got much left) trying to fathom this out. As a consequence, he won't even attempt to switch to his second Raptor in case the same happens.
I have searched around the WWW and seen some problems with the AR8000 binding but every thing we have tried has failed.
Any help will be MORE than appreciated.

[Mark_T]

I can explain at least part of what you are seeing.

On the older firmware you are using, during the bind process it shows you what the receiver is capable of, not what you are binding as.

So if you set the tx to bind in DSM2 mode then bind to a DSMX receiver like the AR8000 then during the bind it will show DSMX, but once bound and you reconnect, the TX will show you are in DSM2 mode.

Also if you have telemetry set up use the button on the TM1000 to get both the TM and RX units in bind mode.

[johnsandywhite]

Just another point. We have taken the AR8000 out of the Heli and plugged in seperate servos to try and bind. The AR6200 was spare and has not been used. Both show the same DSMX on both our Transmitters.

Also, the AR8000 appears to bind because the light goes solid, but the servos do nothing.

[Mark_T]

Do you have a satellite attached to the AR8000? It will not work without one.

[johnsandywhite]

Do you have a satellite attached to the AR8000? It will not work without one.

That is a point. We had the satellite plugged in at first, same with the AR6200. We then tried them without and the AR8000 as I said appeared to bind. But nothing worked. I will try once again with the AR8000 and a satellite attached.

[Mark_T]

That is a point. We had the satellite plugged in at first, same with the AR6200. We then tried them without and the AR8000 as I said appeared to bind. But nothing worked. I will try once again with the AR8000 and a satellite attached.

Make sure it is a DSMX satellite as well, the part number on the back will end in an 'X'.

[johnsandywhite]

Sorted. The problem was the Satellite that was fitted to the AR8000 in the Raptor. I fitted the Satellite from the AR6200 and it is now binding and the servos work. Thanks for your input Mark. It got me to thinking about all the different things with cables, wires, switches etc that can and DO go wrong. My son is still baffled as to why it worked up until he tried re-binding.

[Mark_T]

Glad it is working OK now

The weakest link on the Spektrum receivers is usually the little cable to the satellite and sometimes just moving it around a little is enough to cause one that was working to fail.

Do try to keep the DSM2 satellites with DSM2 receivers and the DSMX ones with the DSMX receivers (AR8000) though. They may work in DSM2 mode when you mix them up but it is not recommended.

[johnsandywhite]

That's quite true Mark. Although we are fairly new to Spektrum and 2.4 we have done quite a lot of research about the DX8 problems and about the DSMX and DSM2. The Transmitter is now showing DSM2. Once again thank you.

[Splashy]

I started to have problems binding my DX8 with an AR8000 and then with a 6210. There were several problems - one where it would not give the DSM2 or DSMX message at all and one where it gave the message but the lights on the receiver and satellite were still flashing.

I have since resolved this issue but am not 100% sure why it was resolved. The best I can do is to let you know how I resolved it. I do not have the time to go back and forth trying out all the options.

1. Move to an area of low WiFi. If I try to do anything on my desk (which is right next to a DECT phone and a Wireless LAN access point) then I cannot bind at all.

2. Reset the model you are having the problem connecting to. After the reset switch off the TX. Do not go to main menu. I'm not sure how important this is.

3. Bind

Works for me. I think the important step is to move away from high levels of 2.4Ghz. Kind of makes sense if the signal from the TX is being drowned out.

Hope this helps someone.