Reference Manual

ManualsBrandsWuerth Elektronik eiSos ManualsElectronicsRadio module HVIN 1101102

Table Of Contents

Introduction
- Operational description
  - Key features
  - Connectivity
- Block diagram
- Ordering information
Electrical specifications
- Recommended operating conditions
- Absolute maximum ratings
- Power consumption
  - Static
  - Dynamic
- Radio characteristics
- Pin characteristics
Pinout
Quick start
- Minimal pin connections
- Antenna connection
  - On-board PCB antenna
  - External antenna
- Power up
- Quickstart example
Functional description
- State indication using the LED pins
- Sleep mode
- Identification of a Proteus-III device on the radio
- Connection based data transmission, with or without security
  - Further information for a secure connection setup
- Unidirectional connectionless data transmission using Beacons
- Energy-efficient distance estimation solutions
- Configure the module for low power consumption
- Start the direct test mode (DTM)
- Using the 2 MBit and LE Coded phy
- Connection setup using LE Coded phy
Host connection
- Serial interface: UART
  - Reset behaviour
The command interface
- Scan for other modules in range
- Setup connections
- Transmit and receive data
- Configuring the module and modifying the device settings
  - CMD_SET_REQ
    - Example 1
    - Example 2
  - CMD_GET_REQ
    - Example 1
- Manage the device state
- Run the Bluetooth test modes
  - CMD_DTMSTART_REQ
  - CMD_DTM_REQ
- Switching GPIOs by remote control
- Other messages
  - CMD_ERROR_IND
- Message overview
UserSettings - Module configuration values
- FS_DeviceInfo: Read the chip type and OS version
  - Example 1
- FS_FWVersion: Read the firmware version
  - Example 1
- FS_MAC: Read the MAC address
  - Example 1
- FS_BTMAC: Read the BLE conform MAC address
  - Example 1
- FS_SerialNumber: Read the serial number of the module
  - Example 1
- RF_DeviceName: Modify the device name
  - Example 1
  - Example 2
- RF_StaticPasskey: Modify the static passkey
  - Example 1
  - Example 2
- RF_SecFlags: Modify the security settings
  - Example 1
  - Example 2
- RF_SecFlagsPerOnly: Modify the security settings (Peripheral only mode)
  - Example 1
  - Example 2
- RF_ScanFlags: Modify the scan behavior
  - Example 1
  - Example 2
- RF_BeaconFlags: Interprete the advertising data
  - Example 1
  - Example 2
- RF_AdvertisingTimeout: Modify the advertising timeout
  - Example 1
  - Example 2
- RF_AdvertisingFlags: Configure the advertising packet
  - Example 1
  - Example 2
- RF_ScanFactor: Modify the scan factor
  - Example 1
  - Example 2
- RF_ScanTiming: Modify the scan timing
  - Example 1
  - Example 2
- RF_ConnectionTiming: Modify the connection timing
  - Example 1
  - Example 2
- RF_TXPower: Modify the output power
  - Example 1
  - Example 2
- RF_SPPBaseUUID: Configure the SPP base UUID
  - Example 1
  - Example 2
- RF_Appearance: Configure the appearance of the device
  - Example 1
  - Example 2
- UART_ConfigIndex: Modify the UART speed
  - Example 1
  - Example 2
- CFG_Flags: Configure the module
  - Example 1
  - Example 2
- DIS_ManufacturerName: Configure the manufacturer name
  - Example 1
  - Example 2
- DIS_ModelNumber: Configure the model number
  - Example 1
  - Example 2
- DIS_SerialNumber: Configure the serial number
  - Example 1
  - Example 2
- DIS_HWVersion: Configure the HW version
  - Example 1
  - Example 2
- DIS_SWVersion: Configure the SW version
  - Example 1
  - Example 2
- DIS_Flags: Configure the device information service
  - Example 1
  - Example 2
Timing parameters
- Reset and sleep
- BLE timing parameters
- Connection establishment
- Connection based data transmission
Peripheral only mode
- Reasons to use the peripheral only mode
- Restrictions
- How to use the peripheral only mode
- More information
  - Radio
  - UART
Remote GPIO control
- Supported GPIO_IDs for remote and local control
Customizing the Proteus-III
- DIS - Device information service
- UUID
- Appearance
Custom firmware
- Custom configuration of standard firmware
- Customer specific firmware
- Customer firmware
- Contact for firmware requests
Firmware update
- Firmware update using the SWD interface
- Firmware update using the Proteus-III OTA bootloader
  - Firmware update steps using the Nordic nRF Toolbox app
Firmware history
Design in guide
- Advice for schematic and layout
- Dimensioning of the micro strip antenna line
- Antenna solutions
Reference design
- EV-Board
- Trace design
Manufacturing information
- Moisture sensitivity level
- Soldering
- ESD handling
- Safety recommendations
Physical dimensions
- Dimensions
- Weight
- Module drawing
- Footprint
- Antenna free area
Marking
- Lot number
- General labeling information
Bluetooth SIG listing/qualification
- Qualification steps when referencing the Proteus-III
Regulatory compliance information
- Important notice EU
- Important notice FCC
- Conformity assessment of the final product
- Exemption clause
- FCC Compliance Statement
- IC Compliance Statement
- FCC and IC requirements to OEM integrators
  - Pre-certified antennas
- ARIB Declaration of conformity
  - Label
  - Certified antennas
Important notes
- General customer responsibility
- Customer responsibility related to specific, in particular safety-relevant applications
- Best care and attention
- Customer support for product specifications
- Product improvements
- Product life cycle
- Property rights
- General terms and conditions
Legal notice
- Exclusion of liability
- Suitability in customer applications
- Trademarks
- Usage restriction
License terms
- Limited license
- Usage and obligations
- Ownership
- Firmware update(s)
- Disclaimer of warranty
- Limitation of liability
- Applicable law and jurisdiction
- Severability clause
- Miscellaneous

Info Module A Module B

⇒ Request

CMD_CONNECT_REQ

with

FS_BTMAC

module B

02 06 06 00 11 00 00

DA 18 00 D1

⇐ Response

CMD_CONNECT_CNF

: Request

understood, try to connect now

02 46 01 00 00 45

⇐ Indication

CMD_CONNECT_IND

: Physical

connection established successfully to module

with

FS_BTMAC

0x11 0x00 0x00 0xDA 0x18 0x00

02 86 07 00 00 11 00

00 DA 18 00 50

⇐ Indication

CMD_CONNECT_IND

: Physical

connection established successfully to module

with

FS_BTMAC

0x55 0x00 0x00 0xDA 0x18 0x00

02 86 07 00 00 55 00

00 DA 18 00 14

⇐ Indication

CMD_PASSKEY_IND

to ask for the

pass key

02 8D 07 00 00 11

00 00 DA 18 00 5B

⇒ Answer with the

CMD_PASSKEY_REQ

and the

pass key "123123"

02 0D 06 00 31 32

33 31 32 33 09

⇐ Response

CMD_PASSKEY_CNF

: Pass key ok 02 4D 01 00 00 4E

⇐ Indication

CMD_SECURITY_IND

, status 0x02

(encrypted link, pairing, no bonding), with

FS_BTMAC

0x11 0x00 0x00 0xDA 0x18 0x00

02 88 07 00 02 11 00

00 DA 18 00 5C

⇐ Indication

CMD_SECURITY_IND

, status 0x02

(encrypted link, pairing, no bonding), with

FS_BTMAC

0x55 0x00 0x00 0xDA 0x18 0x00

02 88 07 00 02 55 00

00 DA 18 00 18

⇐ Indication

CMD_CHANNELOPEN_RSP

: Channel

opened successfully to module with

FS_BTMAC

0x11 0x00 0x00 0xDA 0x18 0x00 and maximum

payload size of 0xF3 (243 Bytes) per packet

02 C6 08 00 00 11 00

00 DA 18 00 F3 EC

⇐ Indication

CMD_CHANNELOPEN_RSP

: Channel

opened successfully to module with

FS_BTMAC

0x55 0x00 0x00 0xDA 0x18 0x00 and maximum

payload size of 0xF3 (243 Bytes) per packet

02 C6 08 00 00 55 00

00 DA 18 00 F3 A8

5. Once the connection is active, data can be sent in each direction. Let us send a string

"ABCD" from module B to module A.

The RSSI values will be different in your tests.