EC15N
Overview
The SDC-EC15N ExpressCard radio card from Laird combines a high-performance, dual band 802.11n radio with software, both designed for business-critical mobile devices that operate in harsh environments. No other Wi-Fi radio card can match the range, robust security, seamless mobility, and manageability of the EC15N card.
Note: This product has reached end of production and is available on a limited basis only.
Specifications
Part Number | Antenna Options | Antenna Type | Chipset (Wireless) | Compliance | Connector | Data Rate | Dimension (Height - mm) | Dimension (Length - mm) | Dimension (Width - mm) | Encryption | Frequency Range (Max) | Frequency Range (Min) | Frequency Range 2 (Max) | Frequency Range 2 (Min) | Input Power | Logical Interfaces | Network Architecture | OS/Software | Operating Channels (2.4 GHz) | Operating Channels (5 GHz) | Operating Humidity | Operating Systems Supported | Power Consumption | Product Type | Protocols | Security | System Architecture | Technology | Weight | Wireless Specification |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
SDC-EC15N End of Life (EOL) | MMCX Connector (x2) | External | Broadcom BCM4322 | FCC | ExpressCard | Up to 300 Mbps | 4.75 mm | 99.35 mm | 33.57 mm | Encryption Key Provisioning: Static (40 and 128 bit lengths). Pre-Shared (PSK)Dynamic: 802.1X Extensible Authentication Protocol. Types: EAP-FAST | 2495 MHz | 2400 MHz | 5825 MHz | 5150 MHz | 3.3 V DC +/- 10% | PCI Express | Infrastructure and ad hoc | Windows XP, Windows Embedded, Windows Mobile, Windows CE | ETSI:13 (3 non-overlapping). FCC:11 (3 non-overlapping). MIC:14 (4 non-overlapping) | 20 MHz Channels -- ETSI: 19 non-overlapping. FCC: 23 non-overlapping. MIC: 8 non-overlapping. KC: 12 non-overlapping. 40-MHz Channels -- ETSI: 9 non-overlapping. FCC: 11 non-overlapping. MIC: 4 non-overlapping. | 10 to 90% (non-condensing) | Windows XP Professional | Transmit: 600 mA (1980mW). Receive: 450 mA (1485mW). Standby: TBD mA (TBD mW) | Embedded Module | Media Access: Carrier sense multiple access with collision avoidance (CSMA/CA) | Standards: Wireless Equivalent Privacy (WEP) | Hosted | 802.11abgn | .529 oz (15 g) | 802.11 a/b/g/n Wi-Fi |
Documentation
Do we recommend conformal coating your modules?
We highly do not recommend conformal coating the radio module. If you plan on encapsulating the radio module in a potting compound or conformal coating, you must assure that the compound in liquid or solid form does not enter under the shield where there are sensitive RF components. Some of the capacitive and inductance values are as low (pF and nH) and could be sensitive to contacting materials such as potting compounds. There are potting compounds and conformal coatings which have very good dielectric constants and are suitable for 2.4 GHz potting applications, however, when you apply any of these, they were not accounted for in the circuit design and might reduce performance of the device (or all together cause it not to function). You should run tests on their particular potting compound and evaluate radio's performance and range. Also, it's worth mentioning that applying any compound, conformal coating or potting directly to the module WILL void the warranty. If your application requires 100% sealing of the radio module, there is a way to do this very successfully without impacting the module performance. Simply place the module on your PCB. Place a plastic cover over the module (like a hat), make the cover large enough to cover the whole module. Apply glue around the bottom perimeter of the cover where it sits on the PCB. This allows the module to function in free air-space while there is a complete seal around it. This information is only for reference and we recommend you should conduct your own testing with your prototype of your end application to find the best suitable fit for your design.
How many reflows do you recommend for your modules?
We only recommend reflowing our modules once as it can damage the module and void the warranty.
What's the recommended process to clean modules?
The recommended cleanser is "hydrocarbon cleaning oil", which can be used to clean the RF shield and PCB. We do not recommend the use of alcohol as it doesn't work as well and could leave residue on the boards.
Before LCM detects a Wi-Fi radio, how do I hard code the radio module it would use?
The radio chipset value is written by the driver when it loads, and indicates which radio is actually installed. LCM uses this value to determine some parameters that vary between radio types. If you want to hard code the Wi-Fi radio before the driver loads, you can do so with this registry: [HKEY_LOCAL_MACHINE/Comm/SDCCF10G1/Parms/Configs/GlobalConfig] "RadioChipSet"=dword:00000006 The values for that registry key are in the sdc_sdk.h as follows: typedef enum _RADIOCHIPSET { RADIOCHIPSET_NONE = 0, RADIOCHIPSET_SDC10 = 1, //BCM4318 RADIOCHIPSET_SDC15 = 2, //BCM4322, RADIOCHIPSET_SDC30 = 3, //AR6002, RADIOCHIPSET_SDC40L = 4, //BCM4319, RADIOCHIPSET_SDC40NBT = 5, //BCM4329, RADIOCHIPSET_SDC45 = 6, //AR6003, RADIOCHIPSET_SDC50 = 7, //AR6004, } RADIOCHIPSET;
mandatory/optional input for EAP type
mandatory/optional input for EAP type EAP credentials Mandatory input Optional input LEAP User name, user password EAP FAST User name, user password PAC file, FAC password PEAP MSCHAP User name, user password CA cert PEAP GTC User name, user password CA cert EAP TLS User name, user cert CA cert EAP TTLS User name, user password CA cert PEAP TLS User name, user cert CA cert Note 1: this settings should be read in user perspective but not for actual implementation. For example, when a user does not input PAC file, it will use auto PAC provisioning. If a user inputs it, it will do a manual PAC provisioning. Note 2: user password is not used for TLS but only user cert is used instead.
In EAP-TLS, there is a setting of username. What is the purpose of it? Will it be used during the authentication? Does it need to be the same as in CA?
EAP-TLS is a tunnel authentication. outer identity: this is the User-Name in the RADIUS packet and visible to all intermediate parties inner identity: this is the actual user identification. It is only visible to the user himself and the Identity Provider The user cert is issued to a user identified by the username, so the username has to be configured so we know which user cert we should be using for the authentication. By default, the username is also used during authentication as the outer identity which gets sent in the identity response packet.
What are the reasons for the null packets in an RF trace?
There are two reasons to send out null packets with p bit enabled. 1. Its RSSI has crossed over the Roam Trigger and the client radio is supposed to start scanning for a new AP. 2. The client radio is running one of our power-save modes (Fast or Max) and is going to sleep for a brief (e.g. 20 ms) period and is telling the AP so it will buffer traffic for it while it sleeps. After a radio has slept for some period of time (defined as the interval between DTIM periods) it is supposed to wake up and indicate to the AP that it is awake by sending a null packet with the P-bit turned off. The radio should only wake if it has traffic to send or it sees from the DTIM in the AP?s beacons that the AP has traffic to send to it.
Does Laird recommend ways to suspend/resume for Wi-Fi radios?
Method 1: Radio driver is asked by power manager to go to low power state Suspend/resume without cutting power to radio Method 2: Radio driver is asked by power manager to go to low power state Cut power to radio Suspend/ Resume Reapply power to radio Eject/insert radio Note 1: Method 1 is the simplest way to deal with suspend/resume, but the OEM needs to consider the current consumption of the radio at a low power state. For example, current consumption for the 40NBT is 7.7mA and for the 45N it is 200uA. Note 2 : In general, method 1 is more recommended because method 2 may cause a delay to make the radio reconnect after resume.
What is the difference between sdcgina.exe and sdc_gina.exe?
sdcgina.exe vs sdc_gina.exe : sdcgina.exe spawns all of the components we need (e.g. supplicant, scutray). sdc_gina.exe is a UI application that, for example, pops up when the credentials must be input.
DFS channels in KCC
The following channels require DFS in Korea KCC/KC domain. Channel Frequency MHz 52 5260 56 5280 60 5300 64 5320 100 5500 104 5520 108 5540 112 5560 116 5580 120 5600 124 5620
What is the difference between eap-mschapv2 and mschapv2 in EAP_TTLS?
With EAP-MS-CHAPv2, the data sent in tunnel will be encapsulated as EAP-MESSAGE AVP (attribute-value pair). In the case of MS-CHAPv2, there is no such extra encapsulation it is just the MS-CHAPv2 message.
KCC domain
The attached document is the list current channels for the KCC domain as of 2015. In document, red means DFS required.
As the PMKcaching, two options in the setting, standard or opmk. What is the definition of these two options?
Standard: indicates PMK Caching: This means that the 802.1x authentication can be skipped on an access point that a client has already authenticated to once before. Only the 4-way handshake needs to happen. This is useful for a client that needs to reconnect to an access point that it roamed away from previously, due to signal loss etc. However, if a client has not roamed to a particular access point during its current working session, it must then authenticate to that specific access point using 802.1x. PMK Caching is the method defined in the 802.11x (WPA/WPA2) specification. Opportunistic Key Caching: With this method, a client device can skip the 802.1x authentication with an access point after a full authentication,and only needs to perform the 4 way handshake when roaming to access points that are centrally managed by the same WLC in an LWAPP or other controller-based infrastructure. This means that the client doesn't need to authenticate with access points that it wants to roam to, as long as the client has authenticated successfully to at least one of the access points in the same zone as the access point that handled the previous successful authentication. In this case, the PMK identifier has been cached at a central location, like the WLC (or wireless switch.) With OKC, the client must support this method for it to be used, even if the infrastructure has been configured with OKC enabled.
Which EAP types Laird supports in CCKM?
CCKM is supported with all EAP types Laird supports?LEAP, EAP-FAST, PEAP-MSCHAPv2, PEAP-GTC, PEAP-TLS, EAP-TLS and EAP-TTLS. ACS supports all of the EAP types except EAP-TTLS. However, supporting CCKM is not dependent on using ACS as the RADIUS server. Laird can do CCKM with any RADIUS server since CCKM support is in the wireless infrastructure.
How to find the PE15N registry setting in Windows?
The Vendor ID and Device ID of PE15N are 14E4 and 432B. The PCI registry paths are under [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Enum\PCI] and [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI] Under these two paths, you can find all registered PCIe modules in this system. Fine the one that with VEN_14E4&DEV_432B-----, and this is the one PE15N register in the system.
Become an Ezurio Customer to Gain Exclusive Access to Our Design Experts
- Antenna Scans
- Antenna selection and placement
- Custom antenna design
- Worldwide EMC testing / certifications
- Embedded RF hardware / firmware design
- Cloud architecture and integration
- Mobile application development
- Product & Industrial Design
Distributors
Distributor | Phone Number | Region | Website |
---|---|---|---|
Arrow Electronics | 1-855-326-4757 +44 2039 365486 |
APAC, North America, South America, EMEA | Website |
Avnet | 1-480-643-2000 +44 1628 512900 |
APAC, North America, South America, EMEA | Website |
Braemac Australia, New Zealand, South East Asia | +61 2 9550 6600 +64 9 477 2148 |
APAC | Website |
Cal-Chip Connect | 1-215-942-8900 |
North America | Website |
DigiKey | 1-800-344-4539 |
North America, South America, APAC, EMEA | Website |
EBV Elektronik | EMEA | Website | |
Farlink Technology China, Hong Kong | +86 13266922199 |
APAC | Website |
Farnell | 1-800-936-198 +44 3447 11 11 22 |
EMEA | Website |
Future Electronics | 1-800-675-1619 1-514-428-8470 |
North America, South America, APAC, EMEA | Website |
Glyn | +49-6126-590-0 |
EMEA | Website |
Hy-Line Germany Only | +49 89 614 503 0 |
EMEA | Website |
Jetronic China, Hong Kong and Taiwan | 852-27636806 |
APAC | Website |
Laird Connectivity | 1-847-839-6925 +44 1628 858941 |
North America, South America, APAC, EMEA | Website |
M2M Germany | +49-6081-587386-0 |
EMEA | Website |
Martinsson | +46 8 7440300 |
EMEA | Website |
McCoy South East Asia | +65 6515 2988 |
APAC | Website |
Mouser | 1-800-346-6873 +44 1494 427500 |
North America, South America, APAC, EMEA | Website |
RS Components | +852-2421-9898 +44 3457-201201 |
North America, South America, APAC, EMEA | Website |
Ryoyo Japan | +81-3-3543-7711 |
APAC | Website |
Solsta UK Only | +44 (0) 1527 830800 |
EMEA | Website |
Supreme Components International India, South East Asia | +65 6848-1178 |
APAC | Website |
Symmetry Electronics | 1-866-506-8829 |
North America | Website |
Tekdis Australia and New Zealand | +61 3 8669 1210 |
APAC | Website |
Telsys | +972 3 7657666 |
EMEA | Website |
WPG | +44 1628 958460 |
EMEA | Website |