
PAN1322
Application Note
28
Revision 1.2, 2013-12-18
Design Guide
Table 3. Configurable combination of Input and Output Capabilities for eUniStone.
Input
Output
Description
Example
0
0
No input and No output
Sensor
0
1
Display only
Display
1
0
Input, no output
Remote control
1
1
Input and Display YesNo
Display with settings
2
0
Keyboard Only
Keypad
2
1
Keyboard, Display YesNo
Mobile phone/Handheld device
For example if the host solution have an input button, the Input capability shall be set to ‘1’. If the host
solution has a keyboard, the input capability shall be set to ‘2’. The Output refers to the accessories
capability like e.g. screen.
When bonding with a Smartphone the accessories configured Input and Output Capabilities used, will
result in different bonding procedures since the manufactures of the mobile phones have made
interpretation and implementation how it should work. See chapter
Secure Simple Pairing (SSP) is supported but also the legacy paring is supported when connecting to
older Bluetooth devices for backwards compatibility, see SPP-AT specification [
5.1.3.3
Registering service - UUID and CoD.
To be able to use eUniStone in an accessory in combination with a Smart Phone App, specific
Universally Unique Identifier (UUID) and Class of Device (CoD) are needed. UUID, CoD and also service
name and port number is registered in eUniStone with the command AT+JRLS. The
UUID’s
that can be
used shall either be one containing the Serial Port Profile or a random UUID which is specific for
Android phones.
A Serial Port Profile accessory, according to Bluetooth standard, uses either a short or a long UUID as
below;
the short UUID 0x1101 or;
the long UUID 0x0000110100001000800000805F9B34FB
Class of Device
should be set according to what kind of device the accessory is. CoD does not tell the
exact services and functionality available in an accessory, but it is recommended to have a class of
device in eUniStone as close as possible to what’s implemented. The CoD consist of a 24 bit field.
When Smart Phones search for accessories the CoD may result in finding or not finding the accessory
since the manufactures of the phones handle CoD differently. Below are a couple of examples;
Table 4. Class of Device bits for a handheld terminal with bar-code scanner.
Major Service Classes
Major Device Classes
Minor Device Class
Bi
2
2
2
2
1
1
1
1
1
1
1
1
1
1
9
8
7
6
5
4
3
2
1
0