Perfect for automotive and building access control systems where reliable and sensitive signal reception is crucial.
A
A
Hardware Overview
How does it work?
MICRF TX Click is based on the MICRF112, an RF transmitter IC from Microchip. This high-performance IC is designed for simplicity in operation, functioning on a "Data-In, RF-Out" basis. It supports both Amplitude Shift Keying (ASK) and Frequency Shift Keying (FSK) modulation types and incorporates a Phase-Locked Loop (PLL) for reliable frequency stabilization. Specifically made for the 315MHz band, the MICRF112 requires only a basic crystal oscillator - such as the onboard 9.84375MHz crystal - to accurately establish its operating frequency alongside minimal external components to match the power amplifier's output with the antenna. It is ideally used in various applications like Remote Keyless Entry (RKE) systems, various remote controls (for set-top boxes, HVAC systems, and appliances), Garage
Door Openers (GDO), Tire Pressure Monitoring Systems (TPMS), outdoor weather stations, and systems for security, alarm, lighting and fan control, doorbells, irrigation, and more. Concerning the board's connectivity with an MCU, this board uses several pins on the mikroBUS™ socket. The EN pin functions as a chip enable function for toggling the device ON or OFF state. The DAT pin directly accepts modulation data input (ASK or FSK, determined by the MODE SEL jumper's setting). In the case of FSK modulation, an additional capacitor like C12 is required between the XTLOUT and XTAL_MOD pins of the MICRF112 (C12 not populated by default). If the user desires a different frequency than the onboard oscillator, they should desolder the R7 resistor on the board, thereby disconnecting the onboard oscillator. Then, a 1nF
capacitor should be soldered in place of the C13 capacitor, and the CLK pin is then used as the reference oscillator input. Operating with a 3.3V input from the mikroBUS™ power supply, the MICRF112 can generate a continuous wave (CW) output power of +10dBm into a 50Ω antenna load. It also boasts an energy-efficient shutdown mode, drawing a mere 50nA, making it highly suitable for battery-dependent devices. This Click board™ can be operated only with a 3.3V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. Also, it comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32F446RE MCU offers a cost-effective and adaptable platform for developers to explore new ideas and prototype their designs. This board harnesses the versatility of the STM32 microcontroller, enabling users to select the optimal balance of performance and power consumption for their projects. It accommodates the STM32 microcontroller in the LQFP64 package and includes essential components such as a user LED, which doubles as an ARDUINO® signal, alongside user and reset push-buttons, and a 32.768kHz crystal oscillator for precise timing operations. Designed with expansion and flexibility in mind, the Nucleo-64 board features an ARDUINO® Uno V3 expansion connector and ST morpho extension pin
headers, granting complete access to the STM32's I/Os for comprehensive project integration. Power supply options are adaptable, supporting ST-LINK USB VBUS or external power sources, ensuring adaptability in various development environments. The board also has an on-board ST-LINK debugger/programmer with USB re-enumeration capability, simplifying the programming and debugging process. Moreover, the board is designed to simplify advanced development with its external SMPS for efficient Vcore logic supply, support for USB Device full speed or USB SNK/UFP full speed, and built-in cryptographic features, enhancing both the power efficiency and security of projects. Additional connectivity is
provided through dedicated connectors for external SMPS experimentation, a USB connector for the ST-LINK, and a MIPI® debug connector, expanding the possibilities for hardware interfacing and experimentation. Developers will find extensive support through comprehensive free software libraries and examples, courtesy of the STM32Cube MCU Package. This, combined with compatibility with a wide array of Integrated Development Environments (IDEs), including IAR Embedded Workbench®, MDK-ARM, and STM32CubeIDE, ensures a smooth and efficient development experience, allowing users to fully leverage the capabilities of the Nucleo-64 board in their projects.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M4
MCU Memory (KB)
512
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
131072
You complete me!
Accessories
Click Shield for Nucleo-64 comes equipped with two proprietary mikroBUS™ sockets, allowing all the Click board™ devices to be interfaced with the STM32 Nucleo-64 board with no effort. This way, Mikroe allows its users to add any functionality from our ever-growing range of Click boards™, such as WiFi, GSM, GPS, Bluetooth, ZigBee, environmental sensors, LEDs, speech recognition, motor control, movement sensors, and many more. More than 1537 Click boards™, which can be stacked and integrated, are at your disposal. The STM32 Nucleo-64 boards are based on the microcontrollers in 64-pin packages, a 32-bit MCU with an ARM Cortex M4 processor operating at 84MHz, 512Kb Flash, and 96KB SRAM, divided into two regions where the top section represents the ST-Link/V2 debugger and programmer while the bottom section of the board is an actual development board. These boards are controlled and powered conveniently through a USB connection to program and efficiently debug the Nucleo-64 board out of the box, with an additional USB cable connected to the USB mini port on the board. Most of the STM32 microcontroller pins are brought to the IO pins on the left and right edge of the board, which are then connected to two existing mikroBUS™ sockets. This Click Shield also has several switches that perform functions such as selecting the logic levels of analog signals on mikroBUS™ sockets and selecting logic voltage levels of the mikroBUS™ sockets themselves. Besides, the user is offered the possibility of using any Click board™ with the help of existing bidirectional level-shifting voltage translators, regardless of whether the Click board™ operates at a 3.3V or 5V logic voltage level. Once you connect the STM32 Nucleo-64 board with our Click Shield for Nucleo-64, you can access hundreds of Click boards™, working with 3.3V or 5V logic voltage levels.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via Debug Mode
1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.
2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.
Software Support
Library Description
This library contains API for MICRF TX Click driver.
Key functions:
micrftx_send_data
- This function builds and sends a packet of data. The packet format is as follows (MSB first, manchester IEEE 802.3): MICRFTX_TRAINING_BYTES, PREABMLE, LEN, DATA_IN, CRC16 (calculated from whole packet excluding training bytes).
Open Source
Code example
This example can be found in NECTO Studio. Feel free to download the code, or you can copy the code below.
/*!
* @file main.c
* @brief MICRF TX Click Example.
*
* # Description
* This example demonstrates the use of MICRF TX click board by sending
* a predefined message to the receiver.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Sends a predefined message every 3 seconds and displays it on the USB UART.
*
* @note
* The MICRF RX click board is a compatible receiver for the MICRF TX click.
* Here are a few steps for troubleshooting if you are experiencing issues running
* this example:
* - Make sure the MICRF TX click is set to ASK mode with on-board jumpers.
* - Check the MCU clock configuration, use an external oscillator instead of the MCU's
* internal one for better accuracy on manchester data rate delay.
* - Measure the actual data rate on the data line and adjust the MICRFTX_MAN_BIT_LEN_US
* value accordingly.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "micrftx.h"
#define MICRFTX_PREAMBLE 0x5AA5 /**< Packet preamble word. */
#define MICRFTX_MESSAGE "MIKROE" /**< Text message to send. */
static micrftx_t micrftx; /**< MICRF TX Click driver object. */
static log_t logger; /**< Logger object. */
/**
* @brief MICRF TX send data function.
* @details This function builds and sends a packet of data.
* The packet format is as follows (MSB first, manchester IEEE 802.3):
* MICRFTX_TRAINING_BYTES, PREABMLE, LEN, DATA_IN, CRC16 (calculated from whole packet excluding training bytes).
* @param[in] ctx : Click context object.
* See #micrftx_t object definition for detailed explanation.
* @param[in] preamble : Preamble word.
* @param[in] data_in : Data buffer.
* @param[in] len : Number of bytes in data buffer.
* @return None.
* @note Default manchester bit length is set to 2000us.
*/
static void micrftx_send_data ( micrftx_t *ctx, uint16_t preamble, uint8_t *data_in, uint8_t len );
/**
* @brief Manchester encode bits.
* @details This function encodes a data byte to manchester word (IEEE 802.3).
* @return Manchester word.
* @note None.
*/
static uint16_t micrftx_man_encode ( uint8_t data_in );
/**
* @brief Reflect bits.
* @details This function reflects a desired number of bits in data.
* @return Reflected data.
* @note None.
*/
static uint16_t micrftx_reflect_bits( uint16_t data_in, uint8_t len );
/**
* @brief CRC-16/MAXIM calculation for CRC16 function.
* @details This function calculates CRC16 with parameteres:
* @li @c Width 16 bit
* @li @c Polynomial 0x8005 ( x16 + x15 + x2 + x0 )
* @li @c Initialization 0x0000
* @li @c Reflect input True
* @li @c Reflect output True
* @li @c Final Xor 0xFFFF
* @li @c Example { 69, 00 } - 0xAFD1
* @param[in] data_buf : Array of bytes to calculate crc from.
* @param[in] len : Number of bytes to calculate crc from.
* @return Calculated CRC.
* @note None.
*/
static uint16_t micrftx_calculate_crc16 ( uint8_t *data_buf, uint16_t len );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
micrftx_cfg_t micrftx_cfg; /**< Click config object. */
/**
* Logger initialization.
* Default baud rate: 115200
* Default log level: LOG_LEVEL_DEBUG
* @note If USB_UART_RX and USB_UART_TX
* are defined as HAL_PIN_NC, you will
* need to define them manually for log to work.
* See @b LOG_MAP_USB_UART macro definition for detailed explanation.
*/
LOG_MAP_USB_UART( log_cfg );
log_init( &logger, &log_cfg );
log_info( &logger, " Application Init " );
// Click initialization.
micrftx_cfg_setup( &micrftx_cfg );
MICRFTX_MAP_MIKROBUS( micrftx_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == micrftx_init( &micrftx, &micrftx_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf ( &logger, " Sending data: %s\r\n\n", ( char * ) MICRFTX_MESSAGE );
micrftx_send_data ( &micrftx, MICRFTX_PREAMBLE, MICRFTX_MESSAGE, strlen ( MICRFTX_MESSAGE ) );
Delay_ms ( 3000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
static void micrftx_send_data ( micrftx_t *ctx, uint16_t preamble, uint8_t *data_in, uint8_t len )
{
uint8_t training[ ] = MICRFTX_TRAINING_BYTES;
uint8_t packet_buf[ MICRFTX_MAX_DATA_LEN + 5 ] = { 0 };
uint16_t crc = 0;
uint16_t man_data = 0;
uint8_t byte_cnt = 0;
uint8_t bit_cnt = 0;
packet_buf[ 0 ] = ( uint8_t ) ( ( preamble >> 8 ) & 0xFF );
packet_buf[ 1 ] = ( uint8_t ) ( preamble & 0xFF );
packet_buf[ 2 ] = len;
memcpy ( &packet_buf[ 3 ], data_in, len );
crc = micrftx_calculate_crc16 ( packet_buf, len + 3 );
packet_buf[ len + 3 ] = ( uint8_t ) ( ( crc >> 8 ) & 0xFF );
packet_buf[ len + 4 ] = ( uint8_t ) ( crc & 0xFF );
micrftx_enable_device ( ctx );
Delay_10ms( );
// Send training bytes first
for ( byte_cnt = 0; byte_cnt < sizeof ( training ); byte_cnt++ )
{
man_data = micrftx_man_encode ( training[ byte_cnt ] );
for ( bit_cnt = 0; bit_cnt < 16; bit_cnt++ )
{
if ( man_data & MICRFTX_MAN_MSB )
{
micrftx_set_data_pin ( ctx );
}
else
{
micrftx_clear_data_pin ( ctx );
}
man_data <<= 1;
Delay_us ( MICRFTX_MAN_BIT_LEN_US / 2 );
}
}
// Send the packet bytes
for ( byte_cnt = 0; byte_cnt < ( len + 5 ); byte_cnt++ )
{
man_data = micrftx_man_encode ( packet_buf[ byte_cnt ] );
for ( bit_cnt = 0; bit_cnt < 16; bit_cnt++ )
{
if ( man_data & MICRFTX_MAN_MSB )
{
micrftx_set_data_pin ( ctx );
}
else
{
micrftx_clear_data_pin ( ctx );
}
man_data <<= 1;
Delay_us ( MICRFTX_MAN_BIT_LEN_US / 2 );
}
}
Delay_10ms( );
micrftx_disable_device ( ctx );
}
static uint16_t micrftx_man_encode ( uint8_t data_in )
{
uint16_t man_data = 0;
for ( uint8_t bit_cnt = 0; bit_cnt < 8; bit_cnt++ )
{
man_data <<= 2;
if ( data_in & ( 0x80 >> bit_cnt ) )
{
man_data |= 1; // 1: low going to a high
}
else
{
man_data |= 2; // 0: high going to a low
}
}
return man_data;
}
static uint16_t micrftx_reflect_bits( uint16_t data_in, uint8_t len )
{
uint16_t data_out = 0;
for ( uint16_t cnt = 0; cnt < len; cnt++ )
{
data_out |= ( ( data_in >> cnt ) & 1 ) << ( len - cnt - 1 );
}
return data_out;
}
static uint16_t micrftx_calculate_crc16( uint8_t *data_buf, uint16_t len )
{
uint16_t crc16 = 0x0000;
for ( uint16_t cnt = 0; cnt < len; cnt++ )
{
crc16 ^= ( micrftx_reflect_bits( data_buf[ cnt ], 8 ) << 8 );
for ( uint8_t bit_cnt = 0; bit_cnt < 8; bit_cnt++ )
{
if ( crc16 & 0x8000 )
{
crc16 = ( crc16 << 1 ) ^ 0x8005;
}
else
{
crc16 <<= 1;
}
}
}
return micrftx_reflect_bits( crc16, 16 ) ^ 0xFFFF;
}
// ------------------------------------------------------------------------ END