Detect the transition points in sinusoidal waveforms with PIC32MZ1024EFH064
Sense the ebb and flow of sinusoidal signals
Published Nov 12, 2023
Click board™
Zero-Cross Click
Dev Board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
Designed for engineers and innovators, our sinusoidal change detection solution ensures that you capture every shift in your signal, empowering you to respond effectively to dynamic changes in your applications.
A
A
Hardware Overview
How does it work?
Zero-Cross Click is based on the circuitry that provides Zero Crossing Detection (ZCD). The alternate current can be connected over two block terminals. As it is intended for this Click board™ to work with high voltages, the critical components are placed on the bottom side, but still, take all precautions when working with this Click board™. On the top side is an AC ON LED to present the AC presence visually. All the magic is happening in
the circuitry at the bottom side of this Click board™. The current passes through the Graetz bridge circuitry, consisting of four DLGL5980. The alternate current converts to a direct current, which is necessary for driving an LED in an EL357N-G, a phototransistor photocoupler from Everlight. When activated, the optocoupler sends a LOW logic state to a ZC pin, the pin with which the Zero-Cross Click communicates with the
host MCU. 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. 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
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
Click board™ 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
This Click board can be interfaced and monitored in two ways:
Application Output- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for Zero-Cross Click driver.
Key functions:
zerocross_pin_read- Zero-Cross pin reading function.zerocross_get_freq- Zero-Cross frequency reading 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 Zero-Cross Click Example.
*
* # Description
* This example demonstrates the use of the Zero-Cross Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initialization of the log UART and basic Click initialisation.
*
* ## Application Task
* Reading frequency value approximately once every second.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "zerocross.h"
static zerocross_t zerocross; /**< Zero-Cross Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
zerocross_cfg_t zerocross_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.
zerocross_cfg_setup( &zerocross_cfg );
ZEROCROSS_MAP_MIKROBUS( zerocross_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == zerocross_init( &zerocross, &zerocross_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float freq_val = 0;
zerocross_get_freq( &zerocross, &freq_val );
log_printf( &logger, " Freq %.2f Hz \n\r", freq_val );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
