Difference between revisions of "NWMUDS:ScanOnConnection"

From 3dbrew
Jump to navigation Jump to search
(Created page with "=Request= {| class="wikitable" border="1" |- ! Index Word ! Description |- | 0 | Header code [0x00220402] |- | 1-... | ? |} =Response= {| class="wikitable" border="1" |- !...")
 
 
(One intermediate revision by one other user not shown)
Line 8: Line 8:
 
| Header code [0x00220402]
 
| Header code [0x00220402]
 
|-
 
|-
| 1-...
+
| 1
| ?
+
| Output buffer max size
 +
|-
 +
| 2-14
 +
| Input [[NWM_Services|ScanInputStruct]].
 +
|-
 +
| 15
 +
| [[NWM_Services|wlancommID]]
 +
|-
 +
| 16
 +
| This is the ID also located at offset 0xE in the CTR-generation [[NWM_Services|structure]].
 +
|-
 +
| 17
 +
| (Size<<4) <nowiki>|</nowiki> 12
 +
|-
 +
| 28
 +
| Output [[NWM_Services|BeaconDataReply]] buffer ptr
 
|}
 
|}
  
Line 26: Line 41:
  
 
=Description=
 
=Description=
Presumably used to send probe requests for finding UDS networks, instead of parsing [[NWMUDS:RecvBeaconBroadcastData|beacons]]. While official applications do have code for this command, there's no known official applications which actually use it.
+
This is about the same as [[NWMUDS:StartScan]] except this only returns already received beacon data, and it can ''only'' be used when connected to a network.

Latest revision as of 07:41, 23 July 2023

Request[edit]

Index Word Description
0 Header code [0x00220402]
1 Output buffer max size
2-14 Input ScanInputStruct.
15 wlancommID
16 This is the ID also located at offset 0xE in the CTR-generation structure.
17 (Size<<4) | 12
28 Output BeaconDataReply buffer ptr

Response[edit]

Index Word Description
0 Header code
1 Result code

Description[edit]

This is about the same as NWMUDS:StartScan except this only returns already received beacon data, and it can only be used when connected to a network.