Why a p10 standard sm with 2X option enabled should be in
SCANNING 1X/1X instead of SCANNING 2X/1X ?
Perhaps the AP has 2X turned off?
Nope, and anyway is SCANNING not REGISTERED yet
Oh. Maybe you answered your own question then. Technically it would make sense for the SM to try the lower modulation rate first, the lower rate signal is more likely to work.
As far as I understand the SM with 2X enabled should be showing
SCANNING VC0 2X/1X where the first 2X means 2X is enabled and the second means that the current rate is set to 1X
when associated the SM should show
REGISTERED VC YY RATE 2X/1X if signal level is only capable of 1X
REGISTERED VC YY RATE 2X/2X if signal level allows 2X rate
Am I missing something?
I double checked my old training documentation - it states that data must be sent through the SM before it will attempt 2x operations. If your radio is currently scanning for a link, it’s going to do so in 1x until it registers with an AP.
LUID: 003 : MAC: 0a-00-XX State: IN SESSION (Encrypt Active)
Session Timeout: 0, AirDelay 155 (approximately 1.44 miles (7595 feet))
Session Count: 10, Reg Count 10, Re-Reg Count 0
RSSI (Avg/Last): 1170/1156 Jitter (Avg/Last): 1/1 Power Level (Avg/Last): -52/-53
Sustained Uplink Data Rate (AP): 20000 (kbit)
Uplink Burst Allocation (AP): 500000 (kbit)
Sustained Downlink Data Rate (AP): 20000 (kbit)
Downlink Burst Allocation (AP): 500000 (kbit)
Low Priority Uplink CIR (D): 0 (kbps) Low Priority Downlink CIR (D): 0 (kbps)
Rate : VC 19 Rate 1X/1X
LUID: 021 : MAC: 0a-00-XX State: IN SESSION (Encrypt Active)
Site Name : Wcust-250
Session Timeout: 0, AirDelay AirDelay 180 (approximately 1.67 miles (8820 feet))
Session Count: 4, Reg Count 2, Re-Reg Count 3
RSSI (Avg/Last): 1221/1214 Jitter (Avg/Last): 7/7 Power Level (Avg/Last): -56/-56
Sustained Uplink Data Rate (AP): 20000 (kbit)
Uplink Burst Allocation (AP): 500000 (kbit)
Sustained Downlink Data Rate (AP): 20000 (kbit)
Downlink Burst Allocation (AP): 500000 (kbit)
Low Priority Uplink CIR (D): 0 (kbps) Low Priority Downlink CIR (D): 0 (kbps)
Rate : VC 18 Rate 2X/2X
wifiguy explain me this please... it is driving me insane. two ap same board, same config, same fpga, same software, against the same std sm. Why one gives me the session status with the site name (and goes 2X) and the other one not. What am I missing...
How many SM’s are in 2X on the first AP? There is a limitation to the number of SM’s that will run in 2X on an AP.
on the first no sm is in 2x and the status is somehow mutilated…
THe strange thing that the same ap in the past used to do 2X and correct status that’s why I am wondering if there is a strange option or something (bside the 2X enable of course 
I only quickly glanced at the thread, but I’ll offer my thoughts:
1) Previous poster is correct - until you are Registered ‘and’ sending data, then the SM doesn’t KNOW if it can send 2x or not, so it shows 1x
2) Registration must be successful before this occurs
Running for a plane, so forgive me if I didn’t read the “rest of the story”
how many SMs can run in 2X?
To run in 2x mode reliably, you need to have a good enough signal that your signal is at least 10dB above the noise floor. Alternately, if you are in 2X mode and the jitter regularly exceeds 10 then you need to turn it off.
I think jerry was talking about the number of SMs that having a good signal can operate at 2X at the same time. The manual does mention something, but is not very clear
Correct me if I’m wrong as I can’t seem to find it in my training docs, but…
The long and the short of it is that the AP has so many slots available (it correlates to the VC numbers). In 1x mode you get your 200 (give or take) SMs as they all use one VC - I think it stands for Virtual Channel. In 2x mode they use two VCs, so if all your SMs are communicating in 2x mode, the AP will only support 100 give or take SMs. Mix and match 1x and 2x and you get different numbers.
I remember about the VC from the manual but I think that was related to high priority channel. When the high priority channel is enabled, the max number of SMs is reduced to 100. I have several SMs in 2X and they only show in VC in use
Site Name : 1694
Software Version : CANOPY 8.2
Software Boot Version : CANOPYBOOT 3.0
FPGA Version : 060407 (DES, Sched, US/ETSIv1.3.1) P9
Session Timeout: 0, AirDelay 500 (approximately 4.64 miles (24500 feet))
Session Count: 2, Reg Count 2, Re-Reg Count 1
RSSI (Avg/Last): 532/526 Jitter (Avg/Last): 6/3 Power Level (Avg/Last): -76/-76
Sustained Uplink Data Rate (SM): 300 (kbit)
Uplink Burst Allocation (SM): 0 (kbit)
Sustained Downlink Data Rate (SM): 600 (kbit)
Downlink Burst Allocation (SM): 0 (kbit)
Low Priority Uplink CIR (SM): 0 (kbps) Low Priority Downlink CIR (SM): 0 (kbps)
Rate : VC 20 Rate 2X/2X
Sorry so quick again…
1) VCs are related to High-Priority Channels (Virtual Circuit is correct <grin) - so you get 100+ SMs if HP is activated on all SMs…
2) Without HP, all 200+ SMs could transmit in 2x if they met the RF criteria
3) However, not all 200+ could get 14 Mb/s throughput (of course)
HTH…running for another meeting…
CTCA-info wrote: Sorry so quick again...
1) VCs are related to High-Priority Channels (Virtual Circuit is correct <grin) - so you get 100+ SMs if HP is activated on all SMs...
2) Without HP, all 200+ SMs could transmit in 2x if they met the RF criteria
3) However, not all 200+ could get 14 Mb/s throughput (of course)
HTH....running for another meeting.... :)
Thanks for the refresher :D