Measure both linear and rotational movements of a magnet with AS5510 and PIC32MZ1024EFH064
Revolutionize magnetic sensing
Published Sep 28, 2023
Click board™
Magneto 11 Click
Dev. board
PIC32MZ clicker
Compiler
NECTO Studio
MCU
PIC32MZ1024EFH064
Unlock a world of possibilities with our magnetic sensing solution, capable of seamlessly tracking magnetic fields, magnet positioning, and angle of rotation for enhanced control and automation
A
A
Hardware Overview
How does it work?
Magneto 11 Click is based on the AS5510, a 10-bit linear position sensor with digital position (interface) output from ams AG. The AS5510 can measure the absolute position of lateral movement in combination with a diametrical two-pole magnet. The sensor needs a simple 2-pole magnet to measure a lateral movement, and the measured distance depends on the magnet geometry. Depending on the magnet size, a lateral stroke of 0.5mm ~ 2mm can be measured with air gaps around 1.0mm. With stronger magnets, even higher lateral strokes and air gaps are possible. The AS5510 comes in a version of a ±50mT full-scale sensing range to deliver the highest
reliability and durability in contactless position measurements. By selecting different measurement ranges, it is possible to choose different sensitivity values; the default sensitivity value of the AS5510 is 97.66µT/LSB. It also features a Power-Down mode that helps save energy and maximize run-time in battery-powered applications. Magneto 11 Click communicates with MCU using the standard I2C 2-Wire interface for switching between four different sensitivity ranges and for simple data transmission to an MCU, supporting Fast Mode Plus operation with a clock frequency up to 1MHz. The absolute position is measured with a resolution of 10 bit = 1024
positions, and it is provided as a digital value on the serial interface. Besides, the AS5510 allows choosing the least significant bit (LSB) of its I2C slave address using the SMD jumper labeled ADDR SEL. The selection can be made by positioning the SMD jumper to an appropriate position marked as 1 or 0. 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
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
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 Magneto 11 Click driver.
Key functions:
magneto11_get_magnetic_field- This function reads the magnetic field strength in mTmagneto11_set_sensitivity- This function writes specified data to the sensitivity registermagneto11_set_config- This function writes specified data to the config register
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 Magneto11 Click example
*
* # Description
* This example demonstrates the use of Magneto 11 click board by reading and displaying
* the magnetic field strength value.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and performs the click default configuration.
*
* ## Application Task
* Reads the magnetic field strength value in milliTesla and displays the results on the USB UART
* every 200ms approximately.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "magneto11.h"
static magneto11_t magneto11;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
magneto11_cfg_t magneto11_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.
magneto11_cfg_setup( &magneto11_cfg );
MAGNETO11_MAP_MIKROBUS( magneto11_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == magneto11_init( &magneto11, &magneto11_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( MAGNETO11_ERROR == magneto11_default_cfg ( &magneto11 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
float magnetic_field;
if ( MAGNETO11_OK == magneto11_get_magnetic_field ( &magneto11, &magnetic_field ) )
{
log_printf ( &logger, " Magnetic Field: %.3f mT \r\n\n", magnetic_field );
Delay_ms ( 200 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
