Extend your network beyond boundaries with ADM2763E and STM32F410RB
The power of full isolation: Redefining RS485 communication
Published Oct 08, 2024
Click board™
RS485 Isolator 3 Click
Dev. board
Nucleo 64 with STM32F410RB MCU
Compiler
NECTO Studio
MCU
STM32F410RB
Unleash the potential of your RS485 network with complete isolation, transforming the way you communicate and ensuring data integrity like never before
A
A
Hardware Overview
How does it work?
RS485 Isolator 3 Click is based on the ADM2763E, a 5.7kV RMS signal isolated RS-485 transceiver from Analog Devices. The ADM2763E is optimized for low speed over long cable runs and has a maximum data rate of 500kbps. It is protected against ≥±12 kV contact and ≥±15 kV air IEC 61000-4-2 electrostatic discharge (ESD) events on the RS485 receiver and driver terminal pins, easily accessible via the screw terminal blocks. The ADM2763E has four bus signals: signal A for the noninverting input signal, signal B for the inverting input signal, signal Y for the noninverting output signal, and signal Z for the inverting output signal, alongside a common ground connection. Using coplanar transformer coils with an ON or OFF keying modulation scheme allows a high data throughput across the isolation barrier of the ADM2763E while minimizing radiation emissions. Architecture like this provides a digital isolator immunity to common-mode transients >250 kV/μs
across the device's full temperature and supply range. The ADM2763E also features a proprietary transmitter architecture with a low driver output impedance that increases the differential output voltage. The high differential output voltage extends the reach of the ADM2763E to longer cable lengths and makes this board suitable for PROFIBUS® nodes when powered with 5V on the isolated side of a supply (isolated-side provides the possibility of a supply voltage in the range from 3V to 5.5V). Besides commonly used UART TX and RX pins on the mikroBUS™ socket, this board also has receiver and driver enable pins routed to the RE and DE pins of the mikroBUS™ socket. It also features a receiver cable invert pin, routed to the INV pin of the mikroBUS™ socket, to quickly correct the reversed cable connection on the A and B receiver bus pins while maintaining complete receiver fail-safe performance. In addition, the ADM2763E has a built-in receiver
fail-safe for the bus Idle condition, accessible through some of the unpopulated onboard jumpers (the R4 and R5 pull-up resistors to the VDD2 isolated-side supply on the ADM2763E pins A and Y, as well as the R14 and R15 pull-down resistors to the GND2 common ground connection on pins B and Z). These resistors can be fitted if the user connects this board to other devices that require external biasing resistors on the bus. The ADM2763E also has a jumper that allows adding a 120Ω load to the RS485 receiver by placing the jumper cap on it. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VDD1 SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. Also, this Click board™ comes equipped with a library containing easy-to-use functions and an example code that can be used as a reference for further development.
Features overview
Development board
Nucleo-64 with STM32F410RB 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)
128
Silicon Vendor
STMicroelectronics
Pin count
64
RAM (Bytes)
32768
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
Click board™ Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Nucleo 64 with STM32F410RB MCU as your development board.
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.
2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.
3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.
Software Support
Library Description
This library contains API for RS485 Isolator 3 Click driver.
Key functions:
rs485isolator3_enable_receiver_input- RS485 Isolator 3 enable receiver input functionrs485isolator3_disable_receiver_input- RS485 Isolator 3 disable receiver input functionrs485isolator3_disable_output- RS485 Isolator 3 disable output function
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief RS485 Isolator 3 Click Example.
*
* # Description
* This example reads and processes data from RS485 Isolator 3 clicks.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables the selected mode.
*
* ## Application Task
* Depending on the selected mode, it reads all the received data or sends the desired message
* every 2 seconds.
*
* ## Additional Function
* - static err_t rs485isolator3_process ( void )
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "rs485isolator3.h"
#define PROCESS_BUFFER_SIZE 200
#define DEMO_APP_RECEIVER
// #define DEMO_APP_TRANSMITTER
static rs485isolator3_t rs485isolator3;
static log_t logger;
uint8_t data_buf[ 8 ] = { 'M', 'i', 'k', 'r', 'o', 'E', '\r', '\n' };
/**
* @brief RS485 Isolator 3 data reading function.
* @details This function reads data from device and concatenates data to application buffer.
* @return @li @c 0 - Read some data.
* @li @c -1 - Nothing is read.
* See #err_t definition for detailed explanation.
* @note None.
*/
static err_t rs485isolator3_process ( void );
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
rs485isolator3_cfg_t rs485isolator3_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.
rs485isolator3_cfg_setup( &rs485isolator3_cfg );
RS485ISOLATOR3_MAP_MIKROBUS( rs485isolator3_cfg, MIKROBUS_1 );
if ( UART_ERROR == rs485isolator3_init( &rs485isolator3, &rs485isolator3_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
rs485isolator3_default_cfg ( &rs485isolator3 );
#ifdef DEMO_APP_RECEIVER
rs485isolator3_enable_receiver_input( &rs485isolator3 );
rs485isolator3_disable_output( &rs485isolator3 );
log_info( &logger, "---- Receiver mode ----" );
#endif
#ifdef DEMO_APP_TRANSMITTER
rs485isolator3_disable_receiver_input( &rs485isolator3 );
rs485isolator3_enable_output( &rs485isolator3 );
log_info( &logger, "---- Transmitter mode ----" );
#endif
log_info( &logger, " Application Task " );
Delay_ms( 100 );
}
void application_task ( void )
{
#ifdef DEMO_APP_RECEIVER
rs485isolator3_process( );
#endif
#ifdef DEMO_APP_TRANSMITTER
rs485isolator3_generic_write( &rs485isolator3, data_buf, strlen( data_buf ) );
log_info( &logger, "---- Data sent ----" );
Delay_ms( 2000 );
#endif
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
static err_t rs485isolator3_process ( void )
{
int32_t rx_size;
char rx_buf[ PROCESS_BUFFER_SIZE ] = { 0 };
rx_size = rs485isolator3_generic_read( &rs485isolator3, rx_buf, PROCESS_BUFFER_SIZE );
if ( rx_size > 0 )
{
log_printf( &logger, "%s", rx_buf );
return RS485ISOLATOR3_OK;
}
return RS485ISOLATOR3_ERROR;
}
// ------------------------------------------------------------------------ END
