Development Examples

[中文版]

Data Throughput Mode Application

What is Throughput Mode?

FSC-BT618x Bluetooth BLE data module has two work modes: Throughput Mode and Command Mode .

The generic data throughput firmware for the FSC-BT618x series modules default to throughput mode. To switch modes, refer to FSC-BT618x General Data AT Command Set and use AT+TPMODE command.

The differences between the two work modes are as follows:

  • Throughput Mode :

    Bluetooth Not Connected : Data received via UART is parsed as AT commands.

    Bluetooth Connected : All data received via UART is sent as-is to the remote Bluetooth device. It does not contain any data headers or framing and does not require AT commands to send data.

  • Command Mode :

    Bluetooth Not Connected : Data received via UART is parsed as AT commands.

    Bluetooth Connected : Data received via UART is still parsed as AT commands. It will contain specific response indication headers and framing. Data must be sent to the remote device using AT commands, such as AT+LESEND.

Module to Phone Application

1.Module Side: After power-on, the module will continuously send broadcast packet data;

2.Mobile Phone Side: Open the [FeasyBlue App] , scan for broadcast packets of nearby Bluetooth BLE devices, find the target Bluetooth module, and establish a connection;

3.After successful connection, the status pin of the module will pull up the level, indicating that the connection has been established;

4.After successful connection, in the transparent transmission mode, the module will automatically transmit the serial port data it receives to the remote end (mobile phone side) via air.

../_images/bt618x-data-bt-app.png

Module to Module Application

Demonstration of BLE communication data transparent transmission between FSC-BT618(Module1) and FSC-BT618(Module2) Bluetooth modules, as follows:

1.Scan for nearby BLE devices

FSC-BT618(Module1) scans for nearby Bluetooth BLE devices.

1Send：<<AT+SCAN=1                // Scan nearby Bluetooth BLE devices
2Response：>>OK
3     >>+SCAN={                   //Scan Started
4     >>+SCAN=0,0,DC0D30001888,-45,10,FSC-BT630
5     >>+SCAN=2,0,DC0D30000015,-42,23,FSC-BT1038C-LE-AKM-0015
6     >>+SCAN=3,0,DC0D300017A8,-62,11,FSC-BT3721V
7     >>+SCAN=4,0,DC0D30000446,-31,9,FSC-BT618               //Module2
8     >>+SCAN=5,0,A4405B28A838,-65,10,AirGo AS01
9     >>+SCAN=}                  //Scan Completed

2.Establish BLE connection request

FSC-BT618(Module1) establishe BLE protocol connection with FSC-BT618(Module2) via the AT+LECCONN command.

1Send:     <<AT+LECCONN=DC0D300004460      // Establish BLE connection request
2Response: >>OK

Warning

AT+LECCONN=Target Bluetooth MAC address + 1-bit address type.

How to obtain the address type:

Use AT+SCAN=1 for scanning. The second parameter in the return result is the address type, as in the following example:

1 //The address type is the second parameter, which is "0".
2
3 Response: >>+SCAN=+SCAN=4,0,DC0D30000446,-31,9,FSC-BT618

3.BLE Connection Established Successfully

In throughput mode, after the Bluetooth connection is successfully established, the serial port cannot receive event response indicators. The current connection status can be determined by the level state of Pin18 (status indicator pin) of FSC-BT618, as detailed below:

High Level (H)： Indicates Bluetooth is successfully connected.

Low Level (L) ： Indicates Bluetooth is not connected or the connection has been disconnected.

4.Send Data

The throughput mode of the general data transmission firmware is enabled by default. After BLE connection is successfully established, data can be sent directly without the need to send data via AT commands:

../_images/bt618x-data-bt-bt.png

Read/Write Module Default Parameters

When Bluetooth is not connected, the module parses UART data as AT commands. The host can query and modify the module’s default parameters. The following example demonstrates:

  1. Write Device Name : ABC

  2. Read Device Name

  3. Read Bluetooth Address

@startuml hide footbox skinparam sequenceMessageAlign center box "local" #LightBlue participant Host as host participant Module as bt end box rnote over host, bt: Write Device Name to ABC host -> bt: AT+NAME=ABC\\r\\n bt -> host: \\r\\nOK\\r\\n" rnote over host, bt: Read Device Name host -> bt: AT+NAME\\r\\n bt -> host: \\r\\n+NAME=ABC\\r\\n\\r\\nOK\\r\\n" rnote over host, bt: Read Bluetooth Address host -> bt: AT+ADDR\\r\\n bt -> host: \\r\\n+ADDR=DC0D30010203\\r\\n\\r\\nOK\\r\\n @enduml

Data Transmission Flow

1.When the module is powered on, it continuously sends broadcast data outward. A remote Bluetooth device (e.g., a mobile phone) can obtain the broadcast packet by searching and initiate a connection request to the module.

2.After the connection is successfully established, the module will pull high the connection status pin to notify the host that the Bluetooth connection has been successfully established.

3.The host can send data to the remote Bluetooth device via the Bluetooth module, and the remote Bluetooth device can also send data to the host.

@startuml hide footbox skinparam sequenceMessageAlign center box "local" #LightBlue participant Host as host participant Module as bt end box box "remote" #LightBlue participant ”Remote BT“ as remote end box rnote over host, remote: Establish Connection bt --> remote: Broadcast Packet bt <-- remote: Scan bt --> remote: Broadcast Packet bt <-- remote: Request Connection Establishment rnote over host, remote: Connection Successful host <- bt: Pull High the Connection Status Pin rnote over host, remote: Send Data host -> bt: Serial Port Transmission ABC bt --> remote: Send Data ABC bt <-- remote: Bluetooth Sending DEF host <- bt: Serial Port Output DEF bt <-- remote: Bluetooth Disconnection host <- bt: Connection Disconnected host <- bt: Pull Low the Connection Status Pin bt --> remote: Broadcast Packet @enduml

Module Acts as Master to Connect to Remote Device

The module can act as master device to connect to remote slave devices.

The host can send AT commands to control the module to perform scanning, connection, and disconnection operations. The following shows the process of connecting to other devices:

@startuml hide footbox skinparam sequenceMessageAlign center box "local" #LightBlue participant Host as host participant Module as bt end box box "remote" #LightBlue participant ”Remote BT“ as remote end box host -> bt: AT+SCAN=1\\r\\n host <- bt: \\r\\nOK\\r\\n bt --> remote: SCAN bt <-- remote: Broadcast Packet host <- bt: \\r\\n+SCAN=0,0,DC0D30001888,-65,10,FSC-BT630\\r\\n host -> bt: AT+LECCONN=DC0D300018880\\r\\n host <- bt: \\r\\nOK\\r\\n bt --> remote: Request to establish an LE connection rnote over host, remote: Connection Successful host <- bt: Pull High the Connection Status Pin rnote over host, remote: Send Data host -> bt: Serial Port Transmission ABC bt --> remote: Send ABC via Bluetooth bt <-- remote: Send DEF via Bluetooth host <- bt: UART Output DEF host -> bt: AT+LEDISC\\r\\n host <- bt: \\r\\nOK\\r\\n bt --> remote: Request to disconnect LE connection rnote over host, remote: Connection Disconnected host <- bt: Pull Low the Connection Status Pin bt <-- remote: Broadcast Packet @enduml