The ProFLEX01-R2 RF modules are high performance 2.4GHz IEEE 802.15.4 radios (CC2520 & CC2591) and microcontrollers (MSP430F5437A) in a cost effective, pre-certified footprint.
The module comes preloaded with the TI 802.15.4 MAC-Stack that can be used with the LSR host serial interface.
Full debug and programming capabilities are included to develop custom applications. Easily load the TI ZigBee® stack or MAC onto the module and create your own network.
Texas Instruments MSP-FET430UIF USB Debug Interface.
Elprotronic FET-Pro430 Lite Software
Ensure the Development Board is powered as indicated by the lit green LED (shown below powered by USB). Plug the MSP-FET430UIF into J11 of the Development Board. Ensure the MSP-FET430UIF is plugged into a USB port as indicated by the green LED on the device.
FET-Pro430 Lite Software Setup
Run the FET-Pro430 Lite Software. See the FET-Pro430 Software User Guide for complete information on setting up and using the software.
In the Setup menu select the “Connection/Device Reset” option to adjust connection settings to support USB.
On the main screen adjust the Microcontroller Type to match the microcontroller, either the MSP430F5437 (ProFLEX01) or MSP430F5437A (ProFLEX01-R2).
Programming the ProFLEX01 Module
On the main screen click the “Open Code File” button to load the *.a43 firmware file.
On the main screen click the “AUTO PROG.” button to begin programming.
The programming process will start. When complete look for the green Pass indicator in the “Status” section.
IAR Embedded Workbench for MSP430
IAR Embedded Workbench for MSP430 is an integrated development environment for building and debugging embedded applications. IAR Website
See TI website for available software solutions for the CC2520.
Firmware development can be done on the ProFLEX01 module using development tools available through TI. It can be plugged into the LSR Development Board and be easily adapted to other hardware.
The MSP-FET430UIF plugs into J11 of the Development Board as pictured below. J11 is a 2x7 pin shrouded connector.
ProFLEX01-R2 is certified with these Antennas
Quality & Environmental
The MAC ID on the module contains the LSR organizational unique identifier (OUI) of 0x00,0x25,0xCA followed by a unique number. The MAC ID is stored in the microcontrollers flash memory. If the module is reprogrammed the MAC ID will be lost as the flash memory is erased. If the MAC needs to be retained it could be read back from the barcode (described below) or be queried out of the module with a serial host command 0x05 before the module is reprogrammed and then later programmed back in (by host command 0x04 or by a custom application in the module).Barcode
The barcode contains the following information: MAC ID, module revision, module name, module part number. An example readout would be: 25CA0200000515,1.0,ProFLEX01,450-0076
The serial communications interface to the module is via a simple UART. Transmit (TX) and receive (RX) are the only two signals required to communicate with the module, and the default communication settings are 19,200 baud, 8 data bits, no parity, and one stop bit (19,200 – 8N1).
The ProFLEX01 Host Protocol lists all the serial commands that are issued between the module and the host processor.Host Commands to Configure UART Communication
Host Msg Type 0x50 "Set Host Interface Configuration"
Used to enable CTS functionality (off by default) and minimum time between packets being transmitted from the module to the host (0 by default).
Host Msg Type 0x18 "Set Host Data Rate"
Used to set the baud rate (19200 by default).Sleep Wakeup & Alert, Reset Alert
The wakeup and reset alert settings can be set and queried by the module using host message types 0x1C and 0x1D respectively.Putting the Device to Sleep
Host message type 0x17 "Set Low Power Mode" is used to put the device into sleep. The device enters low power mode 3 as defined in the MSP430 datasheet. Wakeup is only possible through the wakeup pin described below.Waking up From Sleep Wakeup Alert
The Wakeup Alert Status message can be used to alert the host microcontroller when it wakes up from sleep. This useful for two main reasons:
The Reset Alert Status message can also be used to alert the host microcontroller when the module has been reset. This useful so the host microcontroller knows that the ProFLEX01 module is ready to operate and can then accept commands over the host interface.
Selected ModFLEX series modules ship with LSR’s FLEXConnect firmware. The idea behind FLEXConnect is to support applications that require range extension, but don’t need the complexities of a full blown mesh network.See the ModFLEX FLEXConnect page for more information.
The ProFLEX01 module can be programmed to transmit periodic beacons. See host message types 0x52 to 0x55 for more information.
It is assumed that any device transmitting a periodic beacon is not sleeping as the periodic timer is only running when the device is not sleeping.
The compliance limits (FCC, ETSI) can be set and queried by the module using host message types 0x4A and 0x4B respectively.
The ProFLEX01 module ships with the compliance limit set to FCC which allows for about +20dBm output power on channels 11 to 25. Channels 11-23 and 25 need to have their output power backed off slightly to be compliant with the FCC certification. Channel 26 is not available in FCC mode.
There are two ETSI modes of operation depending on which antenna is being used, either the F-Antenna or the Dipole. In ETSI operation channels 11 to 26 are available to use.
The LSR application that ships with the module ensures that invalid, non-compliant modes cannot be set on the module. See the RF Characterisics in the ProFLEX01 Datasheet for information on the exact limits for each mode. Some examples follow:
Some of the module's configuration is stored to NVM automatically (such as host baud rate), however most need to be saved manually with the host message 0x12. See the ProFLEX01 Host Protocol for information on what parameters need to be manually saved.
The reset (nRESET) pin (14) is an active low input. On the ProFLEX01 module it is pulled high internally with a 47k? resistor. To reset the module, pull the pin low to ground for at least 2?S. This is necessary to ensure a proper reset of the module.
The reset line can be controlled by the host micro or a reset IC. A local reset switch can also be connected if desired. Be sure that if multiple reset sources are tied together that there is no contention between them. In the sample application circuit a 1k ohm series resistor is used to provide some isolation between the MSP-FET430UIF plugged into the JTAG and the host reset as it is possible both could be active at the same time.
The JTAG connection is used to download new firmware or as the debug port for firmware development. The connector shown on the schematic mates with the TI MSP430 USB-Debug-Interface MSP-FET430UIF. It is highly recommended that any host board being developed use this connector, or if space does not permit at least allow access to to the JTAG pins though test points.
LSR periodically releases new firmware to introduce new features on the module and possibly bug fixes. If the JTAG connections are not accessible the firmware on the module will not be able to be upgraded.
The VCC pin on the ProFLEX01 module may require additional power supply filtering represented on the application circuit with the xx value capacitor. The type of filtering required will depend on the power supply being used to power the module. Care needs to be taken that clean regulated power is supplied to the ProFLEX01 Module or performance issues can result.
In order to wake the module from sleep mode, an additional input pin (WAKEUP) with interrupt capability on the ProFLEX01 module needs to be used. For simplicity it is recommended that this be connected to the Host UART RX signal as pictured in the sample application circuit. To wake the ProFLEX01 module out of sleep simply send a dummy byte to the module.
The host micro in this example is controlling the reset input of the ProFLEX01 module.
FAQsClick to view frequently asked questions.
The module supports a protocol very similar to AT commands. It is a binary packet protocol, which is described in the "Host Protocol Guide."
The only supported interface is UART. If SPI or IIC is required this could be developed through a design services contract.
Yes, customers can write their own code in the module.
Yes, the LSR application can be customized. Contact LSR sales for more details.
Source code for the module can be purchased through a design license. Contact LSR sales for more details.
The answer to this question depends on if you plan on using the modular certification of the module. If you want to use the modular certification you need to use one of the antennas that the module was certified with. Consult the datasheet, or product webpage to determine which antennas the module was certified with. If none of the certified antennas meet your requirements, another antenna may be used, however the modular certification will NOT be valid. The new antenna will need to be tested for EMC compliance. Contact LSR’s EMC Test Services to learn more about this process and how we can help.
Yes, this is possible if: 1) The peak gain of the alternate antenna is less than or equal to the original antenna, and 2) The antennas are the same type. There are some cases that are not black and white. It is the customer's responsibility to collect and retain the appropriate and accurate test data traceable to NIST standards for the alternate antenna. Please contact LSR to discuss any questions.
ForumPost or view product support questions
EMail Technical SupportEmails will be assigned a Technical Support Request (TSR) number and assigned a LSR resource. We work diligently to respond to all email and forum posts as soon as possible.
EMail Technical SalesUse the form below, for questions relating to RF Design Services, RF Module Sales and EMC Testing Services, email our Technical Sales Department.