Just to throw it out there, we have done automated testing of our DSM2 bug detection (tens of thousands of power cycles with a test rig), and it seems spektrum's 2048-resolution DSM2 problem occurs randomly in around 1 in 300 power cycles. So if you want to save a bit of money, you could wait for the next SK720 update instead of buying DSMX gear.
linksmechanic>"If it happens 1 in every 300 power cycles Why haven't I crashed my my Hangar 9 beast or my P.A. extra mx or my trex 250? I have powered on the units at least 500 times in 2 years."
It occurs *randomly* between 1 in 200 and 1 in 400 boot ups, depending on the severity. Try flipping a coin a few times; notice it doesn't alternate head/tail/head/tail. Basic stats says some people will get to 1000 boots without a problem, and some to just 50.
Also, it does vary in severity. I'm giving away some hard work here, but to clarify: For 11ms and >7 channel radios, the full channel set is spread across two frames, call them A and B. Normally, they go ABABABABAB. Most of the time the bug shows as something like AAAABBBBAAAABBBB, and less often it shows as AAAAAAAAAAAAB. If you're a tame flyer you might not even notice more than a bit of stuttering with the first version of the problem. A hot flyer might mis-time maneuvers and crash.
>So why does this error only happen with the sk720 and not jr/spektrum/horizon receivers?
(1) It doesn't, and (2) it does. The problem was originally found by [a] Vbar [flyer]. In fact I first isolated it myself by looking at the raw data from a sat rx with a logic analyzer - no SK720 required, just several hours of looking for weirdness. Once initially bound, the SK720 just receives the data, and nothing is sent to the sat rx. You can be sure it also happens with native spektrum rx's, because you can bind it with one and then find the issue (eventually) with a single sat rx and a 3.3v supply.
How many people make it to 300 flights without something else failing, or dumb thumbs? This issue probably got lost in the background hail of falling RC aircraft. It may also be that *direct* servo motion "looks weird" with a bad bind, and people often notice, and just shrug and reset their radio.
>I spoke with an engineer(an independant contractor for horizon) that designs the circuit boards for horizon(family member) and he is a little stunned by what He is hearing here.
It isn't a problem with their hardware. It's pretty obviously a firmware bug. All software has bugs in it, no matter who writes it, no matter how big the company behind it, no matter how much they test it. It's actually impossible even in principle to be sure a non-trivial piece of software is completely bug-free (the Halting Problem).