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

7.6 Run the Bluetooth test modes

The test modes "DTM" as speciﬁed by the Bluetooth

SIG are deﬁned in the Bluetooth

Core speciﬁcation.

7.6.1 CMD_DTMSTART_REQ

This command restarts the module in direct test mode (DTM). When starting in DTM mode,

CMD_GETSTATE_CNF

message follows which indicates that the test mode has been enabled

successfully. Now the

CMD_DTM_REQ

can be used to start and stop various test modes.

As soon as the module is reset, the DTM will be left again and normal operations can be

performed.

Performing a reset will leave the DTM and restart the module in the

ACTION_IDLE

state.

Format:

Start signal Command Length CS

0x02 0x1D 0x00 0x00 0x1F

Response (

CMD_DTMSTART_CNF

Start signal Command | 0x40 Length Status CS

0x02 0x5D 0x01 0x00 1 Byte 1 Byte

Status:

0x00: Request received, will enable the direct test mode now

0x01: Operation failed

0xFF: Operation not permitted

7.6.2 CMD_DTM_REQ

This command starts and stops various test modes. To be able to run these test modes, the

DTM has to be enabled ﬁrst using the

CMD_DTMSTART_REQ

. After a test has been started, it

has to be stopped ﬁrst before a next test can be run.

The default TX power value is 8 dBm, the allowed range is from -40 up to +8 dBm (see

chapter

8.17

for valid TX power values). The valid range for channel is 0. . . 39.

Format:

Start

signal

Command

Length

Command

code

Channel /

Vendor option

Length /

Vendor

command

Payload CS

0x02

0x1E

0x04

0x00

1 Byte 1 Byte 1 Byte

1 Byte 1 Byte

Command code:

0x00: DTM setup