rfDualModeRx
Project Setup using the System Configuration Tool (SysConfig)
The purpose of SysConfig is to provide an easy to use interface for configuring drivers, RF stacks, and more. The .syscfg file provided with each example project has been configured and tested for that project. Changes to the .syscfg file may alter the behavior of the example away from default. Some parameters configured in SysConfig may require the use of specific APIs or additional modifications in the application source code. More information can be found in SysConfig by hovering over a configurable and clicking the question mark (?) next to it's name.
Example Summary
In this example you will learn how to setup multi-mode radio driver to receive data from a transmitter. The Dual Mode RX example configures a BLE and proprietary radio mode to receive packets. The proprietary receiver waits for the first packet. After the first proprietary packet is successfully received, the BLE driver waits for the next BLE packet. The proprietary packet received is then compared to the BLE packet. This example is meant to be used with the Dual Mode TX example or Smart RF Studio. For every proprietary packet received CONFIG_PIN_RLED is turned on and CONFIG_PIN_GLED is turned off. When the same BLE packet is received, CONFIG_PIN_RLED is turned off and CONFIG_PIN_GLED is turned on. If the BLE packet received is not the same as the proprietary packet, CONFIG_PIN_GLED and CONFIG_PIN_RLED are both turned on. The frequency and other RF settings can be modified using SmartRF Studio.
Peripherals Exercised
CONFIG_PIN_RLED- Indicates a proprietary packet was successfully receivedCONFIG_PIN_GLED- Indicates a BLE packet was successfully received and the contents of the packet are the same as the proprietary packet receivedCONFIG_PIN_GLED&CONFIG_PIN_RLEDindicate a BLE packet was received but the contents of the BLE packet are not the same as the proprietary packet
Resources & Jumper Settings
If you're using an IDE (such as CCS or IAR), please refer to Board.html in your project directory for resources used and board-specific jumper settings. Otherwise, you can find Board.html in the directory <SDK_INSTALL_DIR>/source/ti/boards/<BOARD>.
Example Usage
The use of this example will require two launchpads, one running rfDualModeTx (Board_1)
and another running rfDualModeRx (Board_2). Run Board_2 first, followed by Board_1.
Board_1 is set to alternate between transmitting a proprietary packet and BLE packet
every 500 ms. CONFIG_PIN_RLED on Board_1 will turn on when a proprietary packet is
transmitted. CONFIG_PIN_RLED on Board_2 will turn on to indicate the packet was successfully
received. On Board_1, CONFIG_PIN_RLED will turn off and CONFIG_PIN_GLED will turn on to
indicate the BLE packet was successfully sent. The behavior on Board_2 will mimic the
LEDs on Board_1 with CONFIG_PIN_RLED turning off and CONFIG_PIN_GLED turning on. This indicates
the BLE packet was successfully received and matches the proprietary packet. The cycle
will then restart with the new packet.
If a packet is missed from the receiver, the current status of the lights will remain. The extended duration that the LED is on ( > 500 ms) indicates that the receiver is stuck in its previous state (see [figure 1]). The next proprietary will cause the receiver and transmitter to resync.
If the BLE packet is received, but the packet is not the same as the proprietary packet both CONFIG_PIN_GLED and CONFIG_PIN_RLED will turn on (see [figure 2]). This means both a proprietary packet and BLE packet were received but interference or a missed packet has caused the transmitter and receiver to become out of sync. If this happens the receiver and transmitter will automatically resync with the next proprietary packet.
