Easily select and process analog signals from multiple sources with MAX4634 and PIC32MZ1024EFH064
Switch to perfection
Published May 31, 2023
Click board™
Analog MUX 5 Click
Dev Board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
Experience the power of precise and low-voltage analog data switching for uncompromised audio, video, data-acquisition applications, and many more
A
A
Hardware Overview
How does it work?
Analog MUX 5 Click is based on the MAX4634, a low-on-resistance, low-voltage analog multiplexer from Analog Devices. CMOS switch construction of the MAX4634 allows the processing of analog signals within its supply voltage range. It features 4Ω maximum ON-resistance (RON) and offers RON matching between switches to 0.3Ω maximum and RON flatness of 1Ω maximum over the specified signal range. Also, all digital inputs have +0.8V and +2.4V logic thresholds, ensuring TTL/CMOS-logic compatibility with +5V operation. This Click board™ communicates with MCU using several GPIO pins.
It can be enabled or disabled through the EN pin routed to the CS pin of the mikroBUS™ socket, hence, offering a switch operation to turn ON/OFF power delivery to the MAX4634. It also provides two address signals, labeled as A0 and A1 and routed to the PWM and INT pins of the mikroBUS™ socket, that determine the activation of the desired analog input channel based on their setup while monitoring of that input analog signal is done using AN pin of the mikroBUS™ socket. Each analog input has a jumper for its hardware activation or deactivation from R3 to R6 and capacitors for additional filtering of the input
channels from C3 to C6. Proper power-supply sequencing is recommended for all CMOS devices. Before applying analog signals or logic inputs, always apply the power supply first, especially if the analog or logic signals are not current-limited. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. This way, both 3.3V and 5V capable MCUs can use the communication lines properly. However, the 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
PIC32MZ Clicker is a compact starter development board that brings the flexibility of add-on Click boards™ to your favorite microcontroller, making it a perfect starter kit for implementing your ideas. It comes with an onboard 32-bit PIC32MZ microcontroller with FPU from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access anywhere and under
any circumstances. Each part of the PIC32MZ Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the PIC32MZ Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for PIC, dsPIC, or PIC32 programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB Micro-B connection can provide up to 500mA of current, which is more than enough to operate all onboard
and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. PIC32MZ Clicker is an integral part of the Mikroe ecosystem, allowing you to create a new application in minutes. Natively supported by Mikroe software tools, it covers many aspects of prototyping thanks to a considerable number of different Click boards™ (over a thousand boards), the number of which is growing every day.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC32
MCU Memory (KB)
1024
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
524288
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the PIC32MZ clicker as your development board.
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 Analog MUX 5 Click driver.
Key functions:
analogmux5_cfg_setup- Config Object Initialization function.analogmux5_init- Initialization function.analogmux5_default_cfg- Click Default Configuration function.
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 Analog MUX 5 Click Example.
*
* # Description
* This example showcases how to initialize, configure and use the Analog MUX 5 click module.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables the analog inputs.
*
* ## Application Task
* This is an example that shows the use of a Analog MUX 5 click board.
* In this example, we switch from channel AN1 to channel AN4,
* read and display the voltage on the active channel.
* Results are being sent to the Usart Terminal where you can track their changes.
*
*
* @author Nikola Peric
*
*/
#include "board.h"
#include "log.h"
#include "analogmux5.h"
static analogmux5_t analogmux5; /**< Analog MUX 5 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
analogmux5_cfg_t analogmux5_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.
analogmux5_cfg_setup( &analogmux5_cfg );
ANALOGMUX5_MAP_MIKROBUS( analogmux5_cfg, MIKROBUS_1 );
if ( ADC_ERROR == analogmux5_init( &analogmux5, &analogmux5_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( ANALOGMUX5_ERROR == analogmux5_default_cfg ( &analogmux5 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float analogmux5_an_voltage = 0;
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_1 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 1 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_2 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 2 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_3 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 3 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_4 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 4 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
/*!
* @file main.c
* @brief Analog MUX 5 Click Example.
*
* # Description
* This example showcases how to initialize, configure and use the Analog MUX 5 click module.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and enables the analog inputs.
*
* ## Application Task
* This is an example that shows the use of a Analog MUX 5 click board.
* In this example, we switch from channel AN1 to channel AN4,
* read and display the voltage on the active channel.
* Results are being sent to the Usart Terminal where you can track their changes.
*
*
* @author Nikola Peric
*
*/
#include "board.h"
#include "log.h"
#include "analogmux5.h"
static analogmux5_t analogmux5; /**< Analog MUX 5 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
analogmux5_cfg_t analogmux5_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.
analogmux5_cfg_setup( &analogmux5_cfg );
ANALOGMUX5_MAP_MIKROBUS( analogmux5_cfg, MIKROBUS_1 );
if ( ADC_ERROR == analogmux5_init( &analogmux5, &analogmux5_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( ANALOGMUX5_ERROR == analogmux5_default_cfg ( &analogmux5 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float analogmux5_an_voltage = 0;
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_1 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 1 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_2 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 2 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_3 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 3 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
analogmux5_select_ch( &analogmux5, ANALOGMUX5_SEL_CH_4 );
Delay_ms ( 100 );
if ( ADC_ERROR != analogmux5_read_an_pin_voltage ( &analogmux5, &analogmux5_an_voltage ) )
{
log_printf( &logger, " Channel [ 4 ] ---> AN Voltage : %.3f[V]\r\n\n", analogmux5_an_voltage );
}
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
