Unleash the power of lightning-fast AC/DC current measurements with LTS 6-NP and PIC32MZ1024EFH064
Empower your electrical insights
Published Sep 30, 2023
Click board™
LEM Click
Dev Board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
Navigate the world of electrical currents with unrivaled speed and confidence using our solution, offering exceptional measurement performance for your projects
A
A
Hardware Overview
How does it work?
LEM Click is based on the LTS 6-NP, a current transducer from Lem. It acts as a transformer with 2000 turns as a secondary coil and a load resistance of 2kΩ and above. The primary coil is a wire of the load itself, threaded through the middle of the current transducer while fully isolated and galvanic separated from the secondary coil. The LTS 6-NP uses the Hall effect to output the values regarding the current that passes through. The sensor output passes to the MCP607, a micropower CMOS operational amplifier from Microchip. It is a unity-gain stable, low offset voltage OpAmp that includes rail-to-rail
output, swing capability, and low input bias current. The output values from the operational amplifier pass to the MCP3201, a 12-bit analog-to-digital converter with an SPI serial interface from Microchip. The MCP3201 provides a single pseudo-differential input features on-chip, sample and hold, a maximum sampling rate of up to 100ksps, and more. The MCP3201 gets the 2.048V reference voltage from the MAX6106, a low-cost, micropower, low-dropout, high-output-current voltage reference from Analog Devices. The LEM Click uses the 3-Wire SPI serial interface of the MCP3201 to communicate with the host MCU supporting SPI 0
and SPI 3 modes with a frequency of up to 1.6MHz. The voltage amplified through the MCP607 can be directly monitored through the AN pin of the mikroBUS™ socket, which is useful if the host MCU has a higher ADC resolution. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the PWR 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
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 LEM Click driver.
Key functions:
lem_get_current- Function is used to read current in amperes or milliamperes
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
* \brief Lem Click example
*
* # Description
* Demo app measures and displays current by using LEM click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes SPI, LOG and click drivers.
*
* ## Application Task
* This is an example that shows the capabilities of the LEM click by measuring
* current passing through the conductor placed through the hole on the sensor.
*
* \author Jovan Stajkovic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "lem.h"
// ------------------------------------------------------------------ VARIABLES
static lem_t lem;
static log_t logger;
static float current;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
lem_cfg_t cfg;
/**
* 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.
lem_cfg_setup( &cfg );
LEM_MAP_MIKROBUS( cfg, MIKROBUS_1 );
lem_init( &lem, &cfg );
log_printf( &logger, "---------------------\r\n" );
log_printf( &logger, " LEM Click \r\n" );
log_printf( &logger, "---------------------\r\n" );
}
void application_task ( void )
{
current = lem_get_current( &lem, LEM_MILIAMP_COEF );
log_printf( &logger, " Current : %.2f mA \r\n", current );
log_printf( &logger, "---------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
