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

Start signal Command | 0x40 Length Status CS

0x02 0x5C 0x01 0x00 1 Byte 1 Byte

Status:

0x00: Request received, will perform factory reset now

0x01: Operation failed

0xFF: Operation not permitted

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 (e.g. due to supply voltage ﬂuctuations),

the entire memory area may be destroyed.

During start-up of the device, the user settings memory is checked for consis-

tency. In case of inconsistency (e.g. the memory was erased) the device will

perform a factory reset.

This command also removes all bonding data.

7.5.6 CMD_UARTDISABLE_REQ

This command disables the UART of the module. It will be re-enabled when the module

has to send data to the host (e.g. data was received via RF or a state is indicated) or if

the WAKE_UP pin is used (apply a falling edge, hold low for at least 10ms before applying

a rising edge and hold high for at least 10ms). In this case, either the received data or a

CMD_UARTENABLE_IND

is transmitted by the module. Afterwards the UART will stay active until

another

CMD_UARTDISABLE_REQ

CMD_SLEEP_REQ

or a timer triggered sleep event occurs.

Format:

Start signal Command Length CS

0x02 0x1B 0x00 0x00 0x19

Response (

CMD_UARTDISABLE_CNF

Start signal Command | 0x40 Length Status CS

0x02 0x5B 0x01 0x00 1 Byte 1 Byte

Status: