Maybe someone will come along and correct them. I have no doubt there are flaws in my statistical ability.
#Orx dsmx issues code
and by looking at the code at the same rcg post it appears that dsmx hops between 23 channels.
#Orx dsmx issues 32 bit
Once they get up to 5 models then you back up to the entire 32 bit space anyway. Lets forget about that and say each Tx only has one model. not taking into consideration model match. In case of binding issues with other branded receivers press the "Change ID" button on module to change the Module ID to another unique value reserved for that module (5 ID's assigned to each module).There are over 4 billion unique ID's assigned to OrangeRx modules.ĮDIT - i got to thinking by multiplying the 2 tx I was coming up with all possible GUID combinations of which more than one would match. HK says wrote:Module uses a unique Global ID for binding. So this does have a practical aspect besides my typical disdain for a FUD. I do have an orangeRX module coming with my 9xr.
I would however like to carry a technical conversation as to the affect orangerx products have on other dsm based products over and above the normal interference all ISM devices are designed to overcome. Protocol and i cant carry a political conversation as to its merits. I know spektrum/dsm is not popular/robust/modern/etc. And if I show up there with spektrum gear I am shuned, orangerx gear and I am ran out of town I've never been to a large rc field but am getting the impression that dsm planes are just falling sky left and right and there is evidence pointing to orangerRX equipment being at fault. Additionally it appears the model match further uniquely identifies each packet sent out. Since then I took the time to gather some more information such as ' There are over 4 billion unique ID's assigned to OrangeRx modules.',albeit only 5 per module. Over and above that all versions of 'dss' inject a known table of noise into their transmission which is removed at the receiver to improve the s/n ratio that is inevitable in the ISM.Ĭomparing rc usage in the ISM to the crystal days is not an applicable comparison, IMHO.Įarlier i outlined a narrow scenario in which an issue could occur based on assumptions that have not been challenged. Inferring any protocols use on the ISM as 'chinese roulette' is just over the top IMHOīy the very nature of ISM band " communication devices using the ISM bands must tolerate any interference from ISM equipment, unlicensed operations are typically permitted to use these bands,"
So if you go to a busy field how many 9x's do you see that have an orange module sticking out the back ?ĭont forget about microwave ovens, wifi,bluetooth device, and anything else in the ISM band. I'm not saying it's something to ignore, and yes at a large field it may be an issue. So the issue seems to be if you have more than one orange module running in dsmx mode at the same time and they happen to be on the same PN code ( which the orange module utilizes ? 5-10 of them ), and the timing is such that the 2 signals are synchronized and stomping on one another, and the interference is so great that the receiver cant deal with it as all ISM band devices account for other devices using the same frequency, and the interference lasts for a long enough time for the rx to lose signal, then the plane falls out of the sky. This in no way affects 'genuine' dsmx Tx. The issue is that HK/orange did not decipher the entire code sequence,PN code, hence the button on the back.Ĥ. No one is saying that dsm2 is suspectable, are they ?ģ. Maybe HK/orange were too stubborn to use the publicly available data, probably not. dsm had been deciphered long before the orange TX. I'm sure I'm making some wrong assumptions and am trying to gain knowledge as to which assumptions are invalid - thanksġ. I know there are much more robust,desirable, feature laden solutions.īy my limited understanding - Seems like a fair amount of FUD going on here. I'd be the last to defend dsm,dsmx,HK,orange et al.