User's Manual

User should notice that the server services on Module A match client services on
Module B and vice versa. So that data exchange between Module A and B could
follow client-server module where server maintains the data and client access to the
data.
From Module A, Battery Service is server service, so we could set battery level to be
100% by either of following commands as server services access:
 SUW,2A19,64 // Set Battery Level (UUID 0x2A19) to be 100
 SHW,001A,64 // Set Battery Level (handle 0x001A) to be 100
From Module B, Battery service is client role, we could read battery level from
server service on module A by following commands as client access:
 CURV,2A19
 CHR,001A
Both commands will return the value of Battery Level characteristic 0x2A19 to be
100 as follows:
R,64.
The output means the characteristic read returns data of 1 octet in length and value
of 0x64.
From Module B, notification could be started by issuing either of following
commands:
 CUWC,2A19,1
 CHW,001B,0100
Client service command “CUWC” writes configuration of UUID 0x2A19 to be
notification enabled. Client service command “CHW” writes value 0x0001 (little
endian format) to handle 0x001B, which corresponds to characteristic UUID of
0x2A19. According to Bluetooth Core Specification Volume 3, Part G, section 3.3.3.3
table 3.11, value 0x0001 means start notification.
Once notification is successfully started, Module A will notify host the event with
following format:
WC,180F,2A19,0002,0100.
It means the configuration for primary service 0x180F (Battery Service),
characteristic 0x2A19 (Battery Level) has been written by 2 octets with value
0x0001 (little endian format), or means notification has started. If Battery Level