Originally Posted by dziedrius

if I understand correctly, they use GUID as id (http://www.spektrumrc.com/DSM/Technology/DSM2.aspx), if that is true, then according to wikipedia "the total number of unique such GUIDs is 2^122 or 5.3×10^36. This number is so large that the probability of the same number being generated randomly twice is negligible".
Unless all orange tx modules have initial id equal or their id not truly GUID, possibility to have two people with same id's in single field is much smaller than possibility to win jack pot seven times in a row

But they at least considered that it could happen so atleast they protected our planes from "possibly" being shot down.

Originally Posted by molond

But they at least considered that it could happen so atleast they protected our planes from "possibly" being shot down.

Not really, they just give you a way to change the ID of your module so that you can continue using it AFTER your plane has been shot down by a totally unexpected ID problem... LOL

Originally Posted by Kilrah

Not really, they just give you a way to change the ID of your module so that you can continue using it AFTER your plane has been shot down by a totally unexpected ID problem... LOL

Wait, will we have to start asking people what brand and GUID they are flying with? Like the good old days? (which I thankfully never had to endure)

Not even, as you have no way to know a TX's ID... so it's more like russian roulette style

But as dziedrius said, it's virtually impossible for it to happen. I do wonder why the Orange module has it, unless they know they did some kind of weak implementation it makes no sense... And even then it could only affect operation of several Orange modules together, Spektrum users wouldn't suffer from it.

Originally Posted by Kilrah

Not even, as you have no way to know a TX's ID... so it's more like russian roulette style

But as dziedrius said, it's virtually impossible for it to happen. I do wonder why the Orange module has it, unless they know they did some kind of weak implementation it makes no sense...

Its a just in case feature so no one can sue them. If they didn't have it, and someone (or many people) claimed their $500 dollar plane crashed because of someone else's GUID was the same, there would be no way for HobbyKing/OrangeRX to prove it was not their fault.

That's how the world works these days.

They could use the Manufacturer ID as a basis of the GUID, that maybe Spektrum uses for theirs:
http://www.rcgroups.com/forums/showt...3#post23333011
http://www.rcgroups.com/forums/showt...3#post23332944

But given there is a Change ID button, I worry that they don't...

Si.

Originally Posted by SimonChambers

They could use the Manufacturer ID as a basis of the GUID, that maybe Spektrum uses for theirs:
http://www.rcgroups.com/forums/showt...3#post23333011
http://www.rcgroups.com/forums/showt...3#post23332944

But given there is a Change ID button, I worry that they don't...

Si.

I was thinking the very same thing, if collision possibility is so small, why all the hassle with special button to reset id, they couldn't get production line to inject unique ids and thought it will be simpler to add the button?

Originally Posted by dziedrius

I was thinking the very same thing, if collision possibility is so small, why all the hassle with special button to reset id, they couldn't get production line to inject unique ids and thought it will be simpler to add the button?

It is really a formality the legal department said they needed as there is no way to guarantee that the OrangeRX module will not have the same GUID.

It is so a lazy American (or most westerners) can't sue Hobbyking because their plane was shot down by a clashing GUID (which may or may not be true). Doing this Hobbyking can say they did as much as they could (since Spektrum hasn't told them which codes have been used, blame shifted) to prevent this failure.

The real problem is you can sue for anything now days.

Originally Posted by Kilrah

...Spektrum users wouldn't suffer from it.

The introduction of an independent line of TX (modules)means there is a small but real possibility of a GUID clash. This represents a risk to all users of DSM2/X radios equally. It means that Spectrum users can no longer be certain that shootdown isn't possible, which is a great shame. However the risk is small if the guid generation is genuinely random.

In the ethernet world they create unique using a unique MFG number (48 bits I think) combined with a unique device number (another 48 bits) and that is good for billions of unique numbers. I would expect the GUID on these systems to be generated in a similar way.

In the Ethernet world there is a global authority that manages manufacturer codes. AFAIK there is no such authority ensuring unique codes in this domain.

The link above explains that while there may indeed be a unique manufacturer's ID on each Cypress chip, there is no compulsion for the user of the Cypress chip to use the chip's ID in the GUID. Then there is the possibility of non-genuine/clone chips etc.

The risk is probably low, we will learn more once units start shipping in volume, but it is a shame that one of the marvelous benefits of moving from legacy FM to 2.4G is being undermined. Even though I have been a happy user of DSM and DSM2 since they first emerged, this would tend to push me towards a different RF solution such as FrSky in the future.

Not sure how real is this link but maybe it could be the 9xr http://www.hacksmods.com/2012/11/hob...tter/#lightbox[996]/3/

Originally Posted by AlexNZ

Not sure how real is this link but maybe it could be the 9xr http://www.hacksmods.com/2012/11/hob...tter/#lightbox[996]/3/

Yeah, that is reliable. Those images came off of www.turnigy9xr.com, before it said, "Coming Very Soon."

Originally Posted by jmacfann

Hey Kilrah what plane is that you are holding. Off topic I know

To follow up on the OT, it's this one. Some photos here.

I was hoping the 9XR would be released today for Black Friday...