Achieve accurate and reliable data for RPM and speed measurements using LS7366R and PIC32MZ2048EFM100
Counting with confidence: Your quadrature counter solution
Published Oct 19, 2023
Click board™
Counter Click
Dev Board
Curiosity PIC32 MZ EF
Compiler
NECTO Studio
MCU
PIC32MZ2048EFM100
Experience the precision of an advanced quadrature counter, designed to elevate your design with accurate motion measurements
A
A
Hardware Overview
How does it work?
Counter Click is based on the LS7366R, a 32-bit quadrature counter with a serial interface from LSI Computer Systems. It is a CMOS counter with a direct interface for quadrature clocks from incremental encoders. It also interfaces with the index signals from incremental encoders to perform various marker functions. This counter can be configured to operate as a 1, 2, 3, or 4-byte counter. It can also be programmed to work in several counting modes such as Modulo-N, Non-recycle, Range-limit, or Free-running mode. This Click board™ features a 2x5 header (2.54mm pitch) with pins to interface the LS7366R inputs, VCC, and a few GNDs, basically the power supply
pins of the Click board™ itself. The VCC and GND pins can power the quadrature incremental encoder. This header also includes ENCA and ENCB, the input A and B pins of the LS7366R, to directly apply the quadrature clock outputs from incremental encoders on them, and Index (ENCI) pin, a programmable input driven directly by an incremental encoder's index output. The LS7366R uses a standard 4-wire SPI serial interface to communicate with the host MCU over the mikroBUS™ socket. The counter is enabled when EN input is in a high logic state; otherwise, it is disabled with a LOW logic level. In addition, this Click board™ features interrupt over INT pin that
can be configured to use LFLAG or DFLAG over the LF and DF solder jumpers with DFLAG set by default. This way, users can choose LFLAG, an open drain latched output, or DFLAG, an instantaneous push-pull output, thus using these outputs to flag Carry, Borrow, Compare, and Index occurrences. 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
Curiosity PIC32 MZ EF development board is a fully integrated 32-bit development platform featuring the high-performance PIC32MZ EF Series (PIC32MZ2048EFM) that has a 2MB Flash, 512KB RAM, integrated FPU, Crypto accelerator, and excellent connectivity options. It includes an integrated programmer and debugger, requiring no additional hardware. Users can expand
functionality through MIKROE mikroBUS™ Click™ adapter boards, add Ethernet connectivity with the Microchip PHY daughter board, add WiFi connectivity capability using the Microchip expansions boards, and add audio input and output capability with Microchip audio daughter boards. These boards are fully integrated into PIC32’s powerful software framework, MPLAB Harmony,
which provides a flexible and modular interface to application development a rich set of inter-operable software stacks (TCP-IP, USB), and easy-to-use features. The Curiosity PIC32 MZ EF development board offers expansion capabilities making it an excellent choice for a rapid prototyping board in Connectivity, IOT, and general-purpose applications.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC32
MCU Memory (KB)
2048
Silicon Vendor
Microchip
Pin count
100
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 Curiosity PIC32 MZ EF 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 Counter Click driver.
Key functions:
counter_read_cntr- This function reads CNTR, using click object.counter_read_str- This function reads STR, using click object.counter_read_otr- This function reads OTR, using click object.
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 Counter Click example
*
* # Description
* This application measures the speed and the position of the DC motor shafts.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver and configures the click board.
*
* ## Application Task
* Reads data from the CNTR register and calculates the speed of the motor in Rad/s.
* All data is being displayed on the USB UART terminal where you can track their changes.
* The CNTR is a software configurable 8, 16, 24 or 32-bit up/down counter which
* counts the up/down pulses resulting from the quadrature clocks applied at the
* A and B inputs, or alternatively, in non-quadrature mode, pulses applied at the A input.
*
* ## NOTE
* An appropriate motor with optical encoder needs to be connected to the click board.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "counter.h"
// ------------------------------------------------------------------ VARIABLES
static counter_t counter;
static log_t logger;
static int32_t count;
static int32_t count_old;
static float speed;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
counter_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.
counter_cfg_setup( &cfg );
COUNTER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
counter_init( &counter, &cfg );
counter_default_cfg( &counter );
Delay_ms( 300 );
}
void application_task ( void )
{
count = counter_read_cntr( &counter );
log_printf( &logger, "Counter: %ld\r\n", count );
speed = ( float ) ( count - count_old ) / 3600.0;
speed *= 6.283185;
log_printf( &logger, "Speed: %.4f Rad/s\r\n", speed );
count_old = count;
log_printf( &logger, "-------------------------\r\n" );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
