PDA

View Full Version : Spektrum range testing procedure


samr007
07-06-2007, 04:48 AM
What is considered the correct procedure for range-testing a Spektrum radio setup?

I read the 1/3 page blurb on range testing in the DX7 manual, and it seems to suggest that one should walk 30 paces away from the model, hold down the bind/range test button, wiggle one of the sticks, and watch if the servo(s) move.

Should I be testing the link through the entire process of walking the 30 paces?

What is considered a successful range test?

At the 30 paces distance, should I have full control without any interruptions? Should I have full control with any transmitter antenna orientation?

I've tried to get repeatable results with a dinky little AR6100 receiver in a T-rex 450S. I've made several attempts at several times and locations with the rx fully removed from the model, on the ground. Sometimes it cuts out intermittently at 12 paces, usually longer with the antenna not pointed directly at the receiver. Sometimes it goes all the way to 20 paces. On rare occasions, I can get full control all the way out to 30 paces.

These guys apparently get similar results with a module: http://www.helifreak.com/viewtopic.php?t=41683. Should it be similar with the DX7?

Is there some way of predicting a lower bound on the actual range based on how many paces one can back up in range test mode and still have full control?

It has never cut out on me in flight, but it's unnerving that the range test never seems to live up to the standard in the manual.

th3tick
07-06-2007, 10:42 PM
I'm with you 100%. Mine will sometimes work at 30 paces, but then 5-10 seconds later, it stops. If I drop to 25 paces, it works most of the time.

Now, I've been sloppy about doing this testing, and have flown over 160 packs on my TRex 450SE v2 with this setup. All my crashes have been caused by me or by mechanical issues. The radio has been rock solid.

I called Horizon Hobby, and they said I should send my radio in. So here I sit with a radio that has had 0 problems, excepting in this screwy test. For my part, I'm gonna ignore it and go fly. I just can't justify being down 2-3 weeks for a problem that hasn't caused an actual problem.