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.4 Conﬁguring the module and modifying the device settings

It is strongly recommended to have identical settings on all devices, which have

to open a connection with each other or are to be used in Beacon mode.

The module’s parameters are stored in ﬂash, but have a local copy in RAM. The ﬂash param-

eters can be modiﬁed by the

CMD_SET_REQ

, read by the

CMD_GET_REQ

and retain their content

even when resetting the module.

7.4.1 CMD_SET_REQ

This command enables direct manipulation of the parameters in the module’s settings in

ﬂash. The respective parameters are accessed by means of the corresponding settings in-

dex, which can be found in Table

Parameters of 2 or more Bytes have to be transferred with the LSB ﬁrst unless noted differ-

ently in the corresponding description.

The modiﬁed parameters only take effect after a restart of the module. This

may be done by a

CMD_RESET_REQ

if the module does not restart automatically.

The ﬂash memory used to store these settings has a limited count of write

cycles. Try to avoid performing periodic

CMD_SET_REQ

as each command will

use one write cycle.

The validity of the speciﬁed parameters is not veriﬁed. Incorrect values can

result in device malfunction!

To save the parameters in the ﬂash memory of the module, the particular mem-

ory segment must ﬁrst be ﬂushed entirely and then restored from RAM. If a

reset occurs during this procedure, the entire memory area may be corrupted

(e.g. due to supply voltage ﬂuctuations).

Recommendation: First, verify the conﬁguration of the module with

CMD_GET_

REQ

and only then apply a

CMD_SET_REQ

if required to avoid unnecessary ﬂash

cycles.

Format: