Staticpasskey Mode - We PROTEUS-III User Manual

WIRELESS CONNECTIVITY & SENSORS
User manual Proteus-III
Indication CMD_DATA_IND : Received string
"EFGH" from FS_BTMAC
0x18 0x00 with RSSI of 0xC1 (-63dBm)
Response CMD_TXCOMPLETE_RSP : Data
transmitted successfully
7. Now module A closes the connection, so both modules will get a disconnect indication.
Info
Request CMD_DISCONNECT_REQ : Disconnect
Response CMD_DISCONNECT_CNF : Request
received, disconnect now
Indication CMD_DISCONNECT_IND : Connection
closed
Indication CMD_DISCONNECT_IND : Connection
closed
8. You may want to perform a CMD_FACTORYRESET_REQ to restore default settings.

5.6.1.2. StaticPasskey mode

In case of the "StaticPasskey" mode, a pass key has to be entered at the central side that has
to match the pass key of the peripheral. Here the Proteus-III uses a static pass key in the
peripheral role that is stored in the parameter RF_StaticPasskey . When using this method,
the central device requests its host to enter the correct pass key (see CMD_PASSKEY_IND ). In
this case the pass key of the peripheral has to be entered on central side using the CMD_
PASSKEY_REQ command. If the entered pass key is correct, the channel will be opened for data
transmission. Otherwise, the connection will be rejected.
Example: Secured connection with security method "StaticPasskey"
1. Power-up the modules and make their UARTs accessible by the host(s) (115200 Baud,
8n1). After the power-up or after reset the following sequence is sent from the module to
the host.
Info
Response CMD_GETSTATE_CNF : Module A
started in ACTION_IDLE mode.
Response CMD_GETSTATE_CNF : Module B
started in ACTION_IDLE mode.
2. Request the FS_BTMAC of both modules.
Order code 2611011024000
Version 1.8 , July 2022
0x55 0x00 0x00 0xDA
02 C4 01 00 00 C7
Module A
02 07 00 00 05
02 47 01 00 00 44
02 87 01 00 16 92
Module A
02 41 02 00 01 01 41
www.we-online.com/wcs
02 84 0B 00 55 00
00 DA 18 00 C1 45
46 47 48 D7
Module B
02 87 01 00 13 97
Module B
02 41 02 00 01 01 41
41