We PROTEUS-III, User Manual

Page: 71 / 244

WIRELESS CONNECTIVITY & SENSORS
User manual Proteus-III
7.2. Setup connections
7.2.1. CMD_CONNECT_REQ
This command tries to setup a connection to the Proteus-III, which is identified by the
FS_BTMAC
used in the command. After the module prints a
CMD_CONNECT_CNF
to confirm that the request
was received, the indication message
CMD_CONNECT_IND
follows which determines whether the
connection request was accepted by the other device.
In case of enabled security features (see the setting
RF_SecFlags
) a
CMD_SECURITY_IND
is
output in addition.
As soon as the connection setup has been completed and all services have been discovered
successfully a
CMD_CHANNELOPEN_RSP
is sent to the host. Now data may be sent using the
CMD_DATA_REQ
.
Format:
Start signal Command Length BTMAC CS
0x02 0x06 0x06 0x00 6 Bytes 1 Byte
Response (
CMD_CONNECT_CNF
):
Start signal Command | 0x40 Length Status CS
0x02 0x46 0x01 0x00 1 Byte 1 Byte
Status:
0x00: Request received, try to connect to the device with the
FS_BTMAC
0x01:
Operation failed
0xFF: Operation not permitted
7.2.2. CMD_CONNECT_IND
This telegram indicates the connection status and, in case of success, the
FS_BTMAC
of the
connected device. This indication message is the result of a connection request (
CMD_CONNECT_
REQ
).
Format (connected successfully):
Start signal Command Length Status BTMAC CS
0x02 0x86 0x07 0x00 0x00 6 Bytes 1 Byte
Format (failed to connect):
Start signal Command Length Status CS
0x02 0x86 0x01 0x00 0x01 1 Byte
Status:
0x00: Physical connection established successfully
0x01: Connection failed, e.g. due to a timeout (as defined by
RF_ScanTiming
)
Order code 2611011024000
69
Version 1.8 , July 2022 www.we-online.com/wcs