1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html>
3<head>
4<META http-equiv="Content-Type" content="text/html; charset=windows-1252">
5<META name="GENERATOR" content="IBM WebSphere Studio Homepage Builder Version 8.0.0.0 for Windows">
6<META http-equiv="Content-Style-Type" content="text/css">
7<title>WMScanExParam</title>
8<LINK rel="stylesheet" href="../../css/nitro.css" type="text/css">
9</head>
10<body>
11<h1 align="left">WMScanExParam</h1>
12<h2>Definition</h2>
13<dl>
14  <dd>
15<CODE>#include &lt;nitro/wm.h&gt;</CODE><BR>
16  <PRE><CODE>
17typedef struct WMScanExParam
18{
19    WMBssDesc*  scanBuf;
20    u16         scanBufSize;
21    u16         channelList;
22    u16         maxChannelTime;
23    u8          bssid[ 6 ];
24    u16         scanType;
25    u16         ssidLength;
26    u8              ssid[32];
27    u16         ssidMatchLength;
28} WMScanExParam;
29</CODE></PRE>
30  </dd>
31</dl><h2>Elements</h2>
32<TABLE border="1" width="100%">
33  <TBODY>
34    <TR>
35<TD width="200"><CODE>scanBuf</CODE></TD>
36<TD width="800">Pointer to the buffer that stores the information about the parent devices discovered as a result of the search. Be sure to watch the cache because ARM7 directly writes this data to the buffer.</TD>
37    </TR>
38    <TR>
39<TD width="200"><CODE>scanBufSize</CODE></TD>
40<TD width="800">Size of the buffer that stores the parent device information. At the very least, there must be a size (of 64 bytes) that can store a single item of parent device information. The maximum size that can be designated is 1024 bytes. <BR> If only a size that can store multiple items of parent device information is designated, a continuous scan will be performed as much as is allowed by that buffer size. Also, because the size of the discovered parent device information can vary between 64 and 192 bytes, every time a parent device is found, its information is condensed and stored in the buffer. If the Nintendo DS is the parent device, the size of the parent device information will be 80 bytes + the size of the information inherent to that game. <BR> If the remaining size of the buffer is not fully 64 bytes when the parent device information is stored in the buffer, the scan operations will terminate at that point and the callback will be returned.</TD>
41    </TR>
42    <TR>
43<TD width="200"><CODE>channelList</CODE></TD>
44<TD width="800">Wireless channel to search as a bit field format. This is the same kind of format as that of the bit field obtained with the <A href="WM_GetAllowedChannel.html"><CODE>WM_GetAllowedChannel</CODE></A> function. <BR> A continuous scan will be performed a <code>maxChannelTime</code> number of times on each of the individual channels designated here.</TD>
45    </TR>
46    <TR>
47<TD width="200"><CODE>maxChannelTime</CODE></TD>
48<TD width="800">Maximum amount of time (in milliseconds) to continuously search on a single channel. Set to a value from 10 through 1,000. Normally, the value obtained in the <A href="WM_GetDispersionScanPeriod.html"><CODE>WM_GetDispersionScanPeriod</CODE></A> function should be designated here.</TD>
49    </TR>
50    <TR>
51<TD width="200"><CODE>bssid</CODE></TD>
52<TD width="800">MAC address of the parent device that is the target of the search. If everything is <CODE>0xFF</CODE>, there will be no extraction via the MAC address, and all parent devices will be the target of the search.</TD>
53    </TR>
54    <TR>
55<TD width="200"><CODE>scanType</CODE></TD>
56<TD width="800">Designates the scan type. Normally, this designates a passive scan (<CODE>WM_SCANTYPE_PASSIVE</CODE>). Active scan (<CODE>WM_SCANTYPE_ACTIVE</CODE>) is used only for special applications--for example, when a connection destination access point is designated in infrastructure mode. Specify <CODE>WM_SCANTYPE_PASSIVE_CUSTOM</CODE> and <CODE>WM_SCANTYPE_ACTIVE_CUSTOM</CODE> to perform partial matching on SSIDs as needed when the SSID for the special access point changes dynamically. Only these four values can be assigned.</TD>
57    </TR>
58    <TR>
59<TD width="200"><CODE>ssidLength</CODE></TD>
60<TD width="800">Length in bytes of the SSID used to extract the parent device that is the target of the scan. Set to a value from 0 through 32. If a 0 is designated, there will be no extraction via the SSID, and all parent devices will be the target of the search. If a value other than 0 has been specified, more than one parent may be found because SSID is filtered by checking for the length starting from the beginning to the end of the specified length.
61    </TD>
62    </TR>
63    <TR>
64<TD width="200"><CODE>ssid</CODE></TD>
65<TD width="800">SSID used to extract the parent device that is the target of the scan. This should be designated when searching only for the access point that is outputting a specially designated SSID in infrastructure mode. Since the Nintendo DS wireless parent device does not output an SSID beacon, there is no extraction via the SSID.
66      </TD>
67    </TR>
68    <TR>
69<TD width="200"><CODE>ssidMatchLength</CODE></TD>
70<TD width="800">When <CODE>WM_SCANTYPE_PASSIVE_CUSTOM</CODE> or <CODE>WM_SCANTYPE_ACTIVE_CUSTOM</CODE> is specified for <CODE>scanType</CODE>, this specifies the length of SSID in bytes for which partial matching is to be performed. The maximum length of the SSID is 32, so a value from 0 to 32 can be specified. When <CODE>WM_SCANTYPE_PASSIVE</CODE> or <CODE>WM_SCANTYPE_ACTIVE</CODE> is specified as the <CODE>scanType</CODE>, this configuration is ignored.
71      </TD>
72    </TR>
73  </TBODY>
74</TABLE>
75<H2>Description</H2>
76<P>
77Structure made up of the information that should be configured if performing a detailed control of the scan operation when starting a search for a parent device as a child device.
78</P>
79<H2>Revision History</H2>
80<P>
812005/09/07 Added a description of the <CODE>scanType ssidMatchLength</CODE> member.<BR> 2005/03/07 Added a description of each structure member.<BR> 2005/02/14 Initial version.
82</P>
83<hr><p>CONFIDENTIAL</p></body>
84</html>
85