| | ||||||
| | ||||||
| Welcome to The FlyingGiants Community! We're all about fun, and inside you'll find the greatest, friendliest, and most helpful group of people around! If this is your first time visiting, please check out site, and click here to sign up! We hope to see you soon!! |
| |||||||
| 2.4 Ghz Spread Spectrum Technology Discuss Spektrum, Futaba FASST, and all of the exciting 2.4 transmitter/receiver technology here! |
![]() |
| | Thread Tools | Display Modes |
| | #193 (permalink) |
| Bad-ass Super Contributer! ![]() Join Date: Jan 2006 Location: Lexington, SC Age: 25
Posts: 3,879
|
Then it's on the lower power setting if it's on the factory settings. You use the button on the module to program it... From the manual: SET POWER LEVEL Range: 1 to 5 With the STATUS LED solid red, press and hold the PROG button until the STATUS LED turns off. The STATUS LED will now slowly flash green the number of times equal to the current power setting. For example, the default power level is 5, so the STATUS LED will flash green five times. After the flashing stops you have five seconds to change the power level. To change the power level, press and release the PROG button one time for each level of power you would like. For example, if you wanted the power level to be the lowest possible value, you would press and release the PROG button just once. If you wanted the power level to be 3, you would press and release the button three times. If you do not press the PROG button within five seconds, or if the value you enter exceeds what is allowed, the STATUS LED will alternately flash red and green (error condition occurred) and no change will be made. At this point, you are back at the programming mode start (where you can select a programming option). If you do make a change, the STATUS LED will blink green/red/orange in rapid succession to let you know that the change was successful. |
|
| | #195 (permalink) | ||||||||||||||||||
| Gettin' Lower! ![]() Join Date: Mar 2008 Location: Germany
Posts: 43
|
Frank | ||||||||||||||||||
| |||||||||||||||||||
| | #196 (permalink) | ||||||||||||||||||
| Caymanian Pirate Code Monkey ![]() Join Date: Jul 2006 Location: Mustang OK, USA Age: 29
Posts: 1,389
|
__________________ Sawdust is weight leaving the airframe. | ||||||||||||||||||
| |||||||||||||||||||
| | #197 (permalink) | ||||||||||||||||||
| Gettin' Lower! ![]() Join Date: Feb 2008
Posts: 35
|
and Bergs. I continue to not understand why people like Bergs so much, because I've had nothing but problems with them. Slower response time, they move the servos slower, and they literally lock up or glitch and fall out of the sky anywhere inside about a 10 square mile area or so around where we fly. There are faster DSP Rxs like the Sombra gear. My XPS gear feels pretty responsive, but so do some of my 72Mhz Rxs, so I won't make any claims either way. BTW, someone can correct me if I'm wrong here, but it seems that with a packet based system fed from PPM input it should be possible that the response could *feel* different, like this. Normally the PPM 20ms frame (roughly 13ms of signal, and 7ms sync pause) is fed serially to the Rf Tx and then to Rf Rx on the other end of the link in the receiver, and as each pulse for each servo comes along, the Rx filters it out and sends it to the appropriate channel. If the input contains movement on 8 servos, then channel 1, gets updated first, then 2, then 3, then 4.. and so on for 13ms. Then there's a 7ms sync pause and the next PPM frame comes along. Now let's say the Tx rolls up all the stick inputs in the Tx PPM frame after the first 13ms, sends a packet that takes 2ms (yes that's 2m latency beyond the original PPM signal pulses, had it been transmitted serially). Rx receives the packet and instead of feeding all the servos serially one after another, it sends every servo their pulse starting at the same moment. This might *feel* different. It's not faster, it's not significantly slower either, but it might be perceived differently. BTW, I don't know if XPS does it this way or not, but it could. Any 2.4Ghz packet based system could. Maybe I'll get out the silly scope. ian Last edited by Daemon; 03-19-2008 at 06:48 PM. | ||||||||||||||||||
| |||||||||||||||||||
| | #198 (permalink) | ||||||||||||||||||
| That Was a Close Shave! ![]() Join Date: Oct 2006 Location: USA
Posts: 641
|
FWIW, I've never had so much as a glitch with Bergs. They do slow down if heavy interference is encountered, possibly why they are so "slug"gish to you. | ||||||||||||||||||
| |||||||||||||||||||
| | #199 (permalink) | |||||||||||||||||||||||||||||||||
| Bad-ass Super Contributer! ![]() Join Date: Feb 2006 Location: New Zealand Age: 55
Posts: 791
|
The Bergs strong DSP requires a delay of at least one whole frame (20mS) in order to validate the integrity of the data it's received and you're right -- it *is* noticeable. I remember going back to a "dumb" PPM system after flying the old Berg 5/II receivers and I was astonished at how much more immediate the model's responses were (mind you this was a 3D profile with HS5925 (0.08Secs) servos). The newer "mild DSP" receivers such as the Coronas seem to introduce far less delay -- I suspect they're checking each pulse as it's received and passing it on without waiting for a full frame to be constructed/buffered.
| |||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||
| | #200 (permalink) | ||||||||||||||||||
| That Was a Close Shave! ![]() Join Date: Oct 2006 Location: USA
Posts: 641
|
Funny that some of the indoor precision/freestyle guys run those sluggish Bergs. You'd never guess by watching them that their receivers sucked. | ||||||||||||||||||
| |||||||||||||||||||
| | #201 (permalink) | ||||||||||||||||||
| Bad-ass Super Contributer! ![]() Join Date: Feb 2006 Location: New Zealand Age: 55
Posts: 791
|
You *do* notice the difference however if you're switching back and forth. You haven't noticed those people who've switched from PCM to 2.4GHz suddenly flying better just because they've lost a little latency do you? | ||||||||||||||||||
| |||||||||||||||||||
| | #202 (permalink) |
| Gettin' Lower! ![]() Join Date: Feb 2008
Posts: 35
|
Around here, they suck. All of them. Pre-CC ,post-CC, every model, Berg 4, 5, 6, 7. They lag, they glitch, they fly out of range at 100 yards and fall from the sky. I *literally* don't trust them any further than I can throw them, and several times, visiting pilots have come to our slopes or fields and had planes glitch, lock-out badly in the air, or crash outright, and we've discovered that they're using a Berg, again, both old and new models. I've even discovered it by recognizing the symptoms and asking "Do you have a Berg in there?" and getting an affirmative response, having not known before. I owned 3 of them at one point, and gave them all away to out of staters. By contrast, old "dumb" Rxs like the Hitec 555, Electron 6, Superslim 8, and all manner of FMAs work flawlessly, and we regularly fly them out over half a mile (as we also do with various 2.4Ghz systems including XPS, Spektrum, Airtronics FHSS). I wish I knew why, but knowing that they work so badly here, makes me not trust them anywhere else, because we don't know what causes the problem so don't know where else we're going to encounter it. And it's not just one field or one slope. It's roughly 10-15 square miles of area near the mountains west of Denver. I'm not trying to drag this thread off topic but it's sort of an interesting case study, because it demonstrates how huge the difference in experience with a particular product can be. We're busy talking about how badly XPS sucks, while some people have had no problems at all with them, and it mirrors my experience with Bergs which some people swear by, but I've lost expensive planes to. ian |
|
| | #203 (permalink) |
| Just happy to be here... ![]() Join Date: Mar 2008 Location: Phoenix, AZ USA
Posts: 14
|
I could tell the difference from my electron6 rx's compared to the DX-6 2.4ghz. The difference was not so much in speed but in stability. I was flying an Ark400 heli when I first tried the DX-6 and was actually amazed at how stable the heli became just by installing the AR-6000. All the little twitches (I would guess baby glitches) went away and the heli felt sooo much more connected. I immediately dumped all of my 72mhz stuff and started buying more AR-6000's. The XPS/evo12 feels about the same as my DX-7 so I would only assume that if I started with XPS it would have been the same difference from 72mhz.
|
|
| | #204 (permalink) | ||||||||||||||||||
| Seasoned Veteran ![]() Join Date: Jul 2007 Location: Enumclaw, Washington
Posts: 252
|
| ||||||||||||||||||
| |||||||||||||||||||
![]() |
| Tags |
| xps |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| JR-9303 2.4 Field Results | 1bwana1 | 2.4 Ghz Spread Spectrum Technology | 182 | 06-02-2009 01:23 PM |
| Xtreme Link Experiences | Fly3DWithStyle | 2.4 Ghz Spread Spectrum Technology | 1221 | 03-27-2009 12:37 PM |
| Independent tests prove lack of frequency hopping with XPS | XJet | 2.4 Ghz Spread Spectrum Technology | 1501 | 11-21-2008 10:24 AM |
| Final accurate 5955 torque testing results! | Extra260 | Transmitters, receivers, servos & Navigation | 124 | 02-06-2008 09:45 AM |
| ZDZ 210 is two noisy? | martin18152 | Gas Engines and Power | 28 | 04-23-2006 07:53 PM |