Bluetooth¶

Bluetooth allows devices to transmit data wirelessly. It uses the 2.4 GHz radio frequency band. The xPico 250 and xPico 270 support dual-mode Bluetooth Classic and BLE wireless connectivity.

In the diagram, the items in gray are supported by xPico 250 and xPico 270. Customers have to implement BLE profiles on top of GATT for BLE. For BT Classic, profiles like SPP are included already. Additional profiles are planned for future releases, and the SDK can be utilized to develop them as well.

For sample applications, see the SDK User Guide.

BLE¶

BLE (Bluetooth low-energy) is optimized for short bursts of data transmission and is designed for low power consumption. BLE devices have pre-connection and post-connection roles.

Before connection, a BLE device is a peripheral or a central device. Peripheral devices advertise and wait for a wireless connection from a central device. Central devices scan for peripherals. Once the connection is made, a peripheral device is a slave and a central device is a master.

After connection, a device can be either a client or a server. This is separate from the peripheral/central or slave/master roles. A client accesses resources hosted on the server. In most cases, the peripheral device becomes the server and the central device becomes a client.

BLE Central Role¶

In the BLE Central Role, the xPico 250 and xPico 270 can use QuickConnect to connect to devices using GATT.

BLE Central Status¶

You can view the status of the BLE Central state as well as a list of connected devices. A connected device's name, device address, options, and status is displayed.

The options column represents the following advertisement types:

Value	Description
0	Device is not configured with advertisement flags.
1	Limited Discoverable Mode
2	General Discoverable Mode
4	BR/EDR Not Supported
5	Limited Discoverable Mode, BR/EDR Not Supported
6	General Discoverable Mode, BR/EDR Not Supported
8	Simultaneous LE and BR/EDR to Same Device Capable (Controller)
9	Limited Discoverable Mode, Simultaneous LE and BR/EDR to Same Device Capable (Controller)
10	General Discoverable Mode, Simultaneous LE and BR/EDR to Same Device Capable (Controller)
16	Simultaneous LE and BR/EDR to Same Device Capable (Host)
17	Limited Discoverable Mode, Simultaneous LE and BR/EDR to Same Device Capable (Host)
18	General Discoverable Mode, Simultaneous LE and BR/EDR to Same Device Capable (Controller)
24	Simultaneous LE and BR/EDR to Same Device Capable (Controller, Host)
25	Limited Discoverable Mode, Simultaneous LE and BR/EDR to Same Device Capable (Controller, Host)
26	General Discoverable Mode, Simultaneous LE and BR/EDR to Same Device Capable (Controller, Host)

In Web Manager, go to Bluetooth > BLE > Central > Status.

For CLI, see Status Bluetooth BLE Central level.

For XML, see configgroup Bluetooth BLE Central.

Bluetooth BLE Central QuickConnect¶

Use QuickConnect to discover and connect to devices.

Standard operating firmware now supports automatic connection management. When devices come within proximity of the gateway, they can start communicating when connected without needing to go through the complete connection management process.

To access Bluetooth BLE Central QuickConnect in Web Manager, go to Bluetooth > BLE > Central > QuickConnect.

You can see a list of all Bluetooth BLE devices using the GATT profile within range. This is the discovery phase of the Bluetooth connection process. To perform a directed scan for a particular device, enter the device address, formatted as xx:xx:xx:xx:xx:xx in the Device Address field and click Scan. To refresh the scan results every 60 seconds, check the box.

Scan results include device name, address of the device, Received Signal Strength Indicator (RSSI), and Options. See BLE Central Status for a description of the Options column.

Click the device address to attempt to connect to that device.

For CLI, navigate to the status Bluetooth BLE Central level. Use Broadcast scan to scan for Bluetooth devices within range. Alternatively, use Directed scan <Device Address> to scan for a particular device address. Locate the Bluetooth device to which you want to connect and note its device address. To connect to that device, use Connect <Device Address>. For more information, see Status Bluetooth BLE Central level.

Bluetooth BLE Central Configuration Settings¶

In Web Manager, go to Bluetooth > BLE > Central > Configuration.

For CLI, see Config Bluetooth BLE Central level.

For XML, see configgroup Bluetooth BLE Central.

Settings	Description
Mode	Enable or disable Bluetooth BLE Central.
Autoconnect Interval	Specify the period of time to wait before trying to reconnect to devices. This can be in seconds, minutes, and/or hours.
Autoconnect Timeout	Specify the period of time the device will continue to attempt to reconnect to devices. After the timeout period, the device will stop trying to reconnect until the Autoconnect Interval has passed. This can be in seconds, minutes, and/or hours.

BLE Peripheral Role¶

In the BLE peripheral role, xPico 250 and xPico 270 supports the Gateway Provisioning Profile by default. Use the SDK to build your BLE profiles on top of the GATT layer and integrate it within your own embedded application.

Gateway Provisioning Profile enables communication with the Lantronix Gateway Provisioning mobile application for iOS or Android. Using the application, you can use your mobile device to connect to the gateway, complete initial gateway provisioning, and configure the gateway.

See the Gateway Provisioning mobile application documentation for iOS or Android for more information. The Gateway Provisioning mobile application can be found on the App Store for iOS and Google Play for Android.

BLE Peripheral Status¶

You can view the BLE Peripheral state, the Bluetooth device address for the local Bluetooth device, and the Bluetooth device address for the connected device.

In Web Manager, go to Bluetooth > BLE > Peripheral > Status.

For CLI, see Status Bluetooth BLE Peripheral level.

For XML, see configgroup Bluetooth BLE Peripheral.

BLE Peripheral Configuration Settings¶

To enable/disable BLE Peripheral:

In Web Manager, go to Bluetooth > BLE > Peripheral > Configuration.

For CLI, see Config Bluetooth BLE Peripheral level.

For XML, see configgroup Bluetooth BLE Peripheral.

Bluetooth Classic¶

Bluetooth Classic uses the master/slave architecture. The master device scans for slave devices, which respond to the inquiry. The master then initiates a connection.

One master device can connect to a maximum of seven slave devices. A slave device can only be connected to a single master device. A master device can communicate with any slave device to which it's connected. A slave device can communicate only with the master device to which it's connected. The xPico 250 and xPico 270 supports the master role with the SPP profile. The xPico 250 and xPico 270 has three SPP Lines, allowing access to three SPP slave devices at a time.

Bluetooth Classic Master Mode¶

The xPico 250 and xPico 270 uses Bluetooth Classic in the Master role.

Bluetooth Classic Master Status¶

You can view the status of the Bluetooth Classic Master state as well as a list of bonded devices. A bonded device's name, device address, Profile, and state is displayed.

In Web Manager, go to Bluetooth > Classic > Master > Status.

For CLI, see Status Bluetooth Classic Master level.

For XML, see configgroup Bluetooth Classic Master.

Bluetooth Classic Master QuickConnect¶

Use QuickConnect to discover and pair to devices.

Standard operating firmware now supports automatic connection management. When devices come within proximity of the gateway, they can start communicating when connected without needing to go through the complete connection management process.

To access Bluetooth Classic Master QuickConnect in Web Manager, go to Bluetooth > Classic > Master > QuickConnect.

You can see a list of all Bluetooth devices within range. This is the discovery phase of the Bluetooth connection process. To perform a directed scan for a particular device, enter the device address , formatted as xx:xx:xx:xx:xx:xx in the Device Address field and click Scan. To refresh the scan results every 60 seconds, check the box.

Scan results include device name, address of the device, Received Signal Strength Indicator (RSSI), and Profile.

Click the device address to page and attempt to pair and bond to that device.

The Bluetooth Connect page will open. Select the profile, enter the passphrase, and click Connect to connect to the device. If the device is unable to connect, please check the tlog. See Logging for more information.

For CLI, navigate to the status Bluetooth Classic Master level. Use Broadcast scan to scan for all Bluetooth devices with supported profiles within range. Alternatively, use Directed scan <Device Address> to scan for a particular device address. Locate the Bluetooth device to which you want to connect and note its device address. To connect to that device, use Connect <Device Address> <profile> [passphrase]. For more information, see Status Bluetooth Classic Master level.

Bluetooth Classic Configuration Settings¶

In Web Manager, go to Bluetooth > Classic > Master > Configuration.

For CLI, see Config Bluetooth Classic Master level.

For XML, see configgroup Bluetooth Classic Master.

Settings	Description
Mode	Enable or disable Bluetooth Classic Master.
Autoconnect Interval	Specify the period of time to wait before trying to reconnect to devices. This can be in seconds, minutes, and/or hours.
Autoconnect Timeout	Specify the period of time the device will attempt to reconnect to devices. This can be in seconds, minutes, and/or hours.

Bluetooth Connection Process¶

Connecting a Bluetooth device consists of multiple phases.

• Discovery: A BLE central device or Bluetooth Classic master scans for Bluetooth devices that are advertising.
• Paging: A master device pages a slave device to request a connection. The slave device sends a response. This phase is only applicable to Bluetooth Classic.
• Pairing: Two devices exchange security information in order to create a connection.
• Bonding: Two devices store security keys that were exchanged when pairing so they can use them again to connect in the future.
• Connecting: After pairing is successful, the devices are connected.
• Communicating: Once the devices are connected, they can exchange data.