Identification Of A Proteus-Iii Device On The Radio; Connection Based Data Transmission, With Or Without Security - We PROTEUS-III User Manual

WIRELESS CONNECTIVITY & SENSORS
User manual Proteus-III
5.5. Identification of a Proteus-III device on the radio
The Proteus-III can be identified on the radio interface by its FS_BTMAC . This FS_BTMAC is a
®
Bluetooth -conform MAC address, which is part of the data package sent during advertising in
ACTION_IDLE mode. A FS_BTMAC has the size of 6 Bytes.
In ACTION_SCANNING state a module listens to the data packets of all advertising devices in
range and stores their FS_BTMAC to an internal data base. With help of this FS_BTMAC a con-
nection to the corresponding device can then be established using the CMD_CONNECT_REQ com-
mand.
To simplify the identification of Proteus-III devices on the RF-interface a short user-defined
name (see RF_DeviceName ) can be given to the module, which is also part of the advertising
packet.
The FS_BTMAC consists of the company ID 0x0018DA followed by the module's
serial number FS_SerialNumber .

5.6. Connection based data transmission, with or without security

®
In the Bluetooth LE standard the data transmission typically is connection based. A connec-
tion between two devices can be secured or unsecured (default configuration). In any case,
each data packet transmitted is acknowledged on the link layer, such that it is resent as long
as it has not been received from the receiver. The following lines describe how to run the con-
nection setup and data transmission using the Proteus-III.
If module A is supposed to setup a connection with module B, the host of module A must
send the command CMD_CONNECT_REQ including the FS_BTMAC of module B to module A. If the
FS_BTMAC of module B is unknown, a radio scan shall be run before by module A to discover all
®
available Bluetooth LE enabled devices in range.
After sending the command CMD_CONNECT_REQ , the module answers with a CMD_CONNECT_CNF to
signal that the request has been understood and the module tries to establish the connection.
If module B cannot be found on the air within a timeout, module A outputs a CMD_CONNECT_IND
with "failed" as status. Otherwise, as soon as the physical connection has been set up suc-
cessfully, module A and B output a CMD_CONNECT_IND message with the status of the successful
connection and LED_1 turns on.
Next some security and authentication messages will follow, like CMD_SECURITY_IND , if security
is enabled.
After the physical connection has been setup successfully the modules exchange their services
(WE SPP-like). As soon as this has finished successfully, a CMD_CHANNELOPEN_RSP message
is sent to the host indicating that the connection is ready for data transmission. In addition,
LED_2 turns on.
Now, data can be transmitted in both directions using the command CMD_DATA_REQ . It is con-
firmed by the messages CMD_DATA_CNF (data will be processed) and CMD_TXCOMPLETE_RSP (data
transmitted successfully).
Each time data has been received a CMD_DATA_IND message will be output containing the re-
ceived data.
Order code 2611011024000
Version 1.8 , July 2022 www.we-online.com/wcs
37