Suppose DSM2 header is inaccurate

[GoogleCodeExporter]

After using a protocol analyzer to sniff the interface between the SPEkTRUM MCU 
& the tx module, I suppose DSM2 header of Open9x is inaccurate.

Both X1TXN & X1TXO had been tested.

The first byte of header seems to be:

    01 IS_HELI (!BIT0 = Airplane)
    08 DSMX/DSM2 dual mode
    00 France
    10 EU 100mW
    20 Range Test
    40 US 200mW (Must |EU = 50 )
    80 bind

bitwise ORed

e.g.

DSMX/DSM2 dual mode & Power Setting is US , then first byte should be 58.

The menu option LPXDSM2 assign 0x00 due to the LP4/5 has no UI to set the 
correct radiation regulation, so use the most conservative France regulation. 

I suggest to modify the related menu & code to correctly reflex the user wanted 
power / protocol setting, and to meet the national regulation.

note:

Dans la cas d'une utilisation en extérieur, la puissance de sortie est 
limitée pour certaines parties de la bande. Voir la table ci-dessous ou 
visitez http://www.arcep.fr/ pour de plus amples détails

Location Frequency Range (MHz) Power (EIRP)

Indoor (No restrictions)

2400-2483.5 100 mW (20 dBm)

Outdoor 

2400-2454      100 mW (20 dBm)
2454-2483.5    10 mW (10 dBm)

Original issue reported on code.google.com by myfo...@gmail.com on 15 Dec 2012 at 5:57

[GoogleCodeExporter]

To make UI modification as small as possible,
suggest to change UI setting to

DSM2(FR)
DSM2(EU)
DSM2(US)
DSMX(FR)
DSMX(EU)
DSMX(US)

These options include (3 power setting, FR/EU/US) x  (2 modes, 
DSM2only/DSM2+DSMX)

Original comment by myfo...@gmail.com on 20 Dec 2012 at 5:33

[GoogleCodeExporter]

Note that the French restriction of 10mW in the upper part of the band is 
obsolete, it was revoked this summer. So France mode is now irrelevant. 

Original comment by bernet.a...@gmail.com on 26 Dec 2012 at 9:41

[GoogleCodeExporter]

Then, should we change the options to be ?

DSM2(EU)
DSM2(US)
DSMX(EU)
DSMX(US)

Or any suggestion?

Original comment by myfo...@gmail.com on 26 Dec 2012 at 5:28

[GoogleCodeExporter]

I think I'd prefer 2 separate settings - one DSM2/DSMX and one US/EU. 

I wonder if all modules accept US/EU setting. I have a DX4e module that doesn't 
offer the setting and a spectrum analyzer, so I could have a look once 
implemented :)

Original comment by bernet.a...@gmail.com on 26 Dec 2012 at 9:14

[GoogleCodeExporter]

I prefer 2 separate settings too.

But this involves companion 9x & users' old setting compatibility.
On the other hand, if the user has no DSM2/X modules, the extra menu will be 
useless. :-P

Original comment by myfo...@gmail.com on 27 Dec 2012 at 3:28

[GoogleCodeExporter]

I have spectrum analyzer & network analyzer, but even without a spectrum 
analyzer, you may check the current from the battery side at home easily.

For 200mW RF output, the power consumption must be higher than 100mW. ;)

Original comment by myfo...@gmail.com on 27 Dec 2012 at 5:58

[GoogleCodeExporter]

@myfox
Would you take care of this issue? I even don't own any DSM2 module / receiver!

Original comment by bson...@gmail.com on 27 Dec 2012 at 7:50

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

"On the other hand, if the user has no DSM2/X modules, the extra menu will be 
useless. :-P"
It should of course be under the protocol choice, and only appear when 
proto==DSM, just like the current range check and RxNum. 

Original comment by bernet.a...@gmail.com on 27 Dec 2012 at 8:49

[GoogleCodeExporter]

I have no dsm2/x module in my T9x neither. :-(

I'm planning to buy 1 and fix issue 155 when I am freed from daily jobs.

Original comment by myfo...@gmail.com on 27 Dec 2012 at 4:40

[GoogleCodeExporter]

i have both a home made dsm2/x module and will soon have an orangeRX dsm2 
module so if you'll code i'll test it if you want?

Original comment by Mechcond...@gmail.com on 30 Dec 2012 at 11:57