Set, track, and achieve your wellness milestones easily with STP201M and PIC18LF45K80
Step by step to success: Pedometer magic in your hand
Published Nov 01, 2023
Click board™
Pedometer Click
Dev Board
EasyPIC v7
Compiler
NECTO Studio
MCU
PIC18LF45K80
Our pedometer is your reliable companion for tracking daily steps, empowering you to achieve your fitness goals with precision
A
A
Hardware Overview
How does it work?
Pedometer Click is based on the STP201M, a 3D pedometer module with an IC chipset from NiceRF. The module itself is designed for wrist pedometer products, like the pedometer bracelet or watch for example. The end user doesn’t have to worry about doing any calculations on their own, or worry about what the algorithm for step detection is doing, since the INT pins output is already a measurement of the steps that were taken. Specifically, a MEMS sensor. Micro-electro-mechanical system sensors, abbreviated to MEMS, are made out of very small components, with their size usually ranging from 1 to 100 micrometers. These account for the sensor being very small and therefore it having low energy consumption and
also not requiring a lot of space. This particular sensor is a 3D one. The three axes it utilizes, allow for precise measurements of any movement and the direction its taking. The three axes system, along with the MCUs meticulous algorithm, make it significantly less likely to make any false-positive counts (ex. tying up shoes). The MCU has two distinguished modes. The first one of them is the operational mode. The MCU is designed to go into the operational mode whenever it senses some activity. However, if there is no discernible movement over the course of 20 seconds, it goes into the sleep mode. This mode is characterized by the very low energy consumption of only 5 μA max. The STP201M modules communication is
somewhat different from the standard I2C protocol. Since our libraries do not support it, the user has the capability of changing the code of the main MCU in order to fit the protocol of the module and thus change any preprogramed settings. Since the modules maximum operatin voltage is 3.6V, the Pedometer click uses the 3.3V rail for power supply. The other pins it utilizes are the, before mentioned, Interrupt pin, and the I2C Clock and Data pins. This click also has a Power LED indicator. This Click Board™ is designed to be operated only with 3.3V logic level. A proper logic voltage level conversion should be performed before the Click board™ is used with MCUs with logic levels of 5V.
Features overview
Development board
EasyPIC v7 is the seventh generation of PIC development boards specially designed to develop embedded applications rapidly. It supports a wide range of 8-bit PIC microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB-B. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyPIC v7 allows you to connect accessory boards, sensors, and custom electronics more efficiently than ever. Each part of
the EasyPIC v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use various external power sources, including an external 12V power supply, 7-23V AC or 9-32V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B) connector. Communication options such as
USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets. These sockets cover a wide range of 8-bit PIC MCUs, from PIC10F, PIC12F, PIC16F, PIC16Enh, PIC18F, PIC18FJ, and PIC18FK families. EasyPIC v7 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development 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
PIC
MCU Memory (KB)
32
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
3648
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 EasyPIC v7 as your development board.
Track your results in real time
Application Output
After pressing the "FLASH" button on the left-side panel, it is necessary to open the UART terminal to display the achieved results. By clicking on the Tools icon in the right-hand panel, multiple different functions are displayed, among which is the UART Terminal. Click on the offered "UART Terminal" icon.
Once the UART terminal is opened, the window takes on a new form. At the top of the tab are two buttons, one for adjusting the parameters of the UART terminal and the other for connecting the UART terminal. The tab's lower part is reserved for displaying the achieved results. Before connecting, the terminal has a Disconnected status, indicating that the terminal is not yet active. Before connecting, it is necessary to check the set parameters of the UART terminal. Click on the "OPTIONS" button.
In the newly opened UART Terminal Options field, we check if the terminal settings are correct, such as the set port and the Baud rate of UART communication. If the data is not displayed properly, it is possible that the Baud rate value is not set correctly and needs to be adjusted to 115200. If all the parameters are set correctly, click on "CONFIGURE".
The next step is to click on the "CONNECT" button, after which the terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
Software Support
Library Description
This library contains API for Pedometer Click driver.
Key functions:
pedometer_get_interrupt_state- Functions for get Interrupt state on the INT pinpedometer_get_step_counter- Functions for get step counterpedometer_generic_read- Generic read 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
* \brief Pedometer Click example
*
* # Description
* This application detected steps.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes driver init and sets step counter on 0.
*
* ## Application Task
* It checks if a new step is detected, if detected new step -
* reads the current number of steps made and logs data to the USBUART.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "pedometer.h"
// ------------------------------------------------------------------ VARIABLES
static pedometer_t pedometer;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
pedometer_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.
pedometer_cfg_setup( &cfg );
PEDOMETER_MAP_MIKROBUS( cfg, MIKROBUS_1 );
pedometer_init( &pedometer, &cfg );
}
void application_task ( void )
{
// Task implementation.
uint8_t new_step;
uint32_t s_counter;
char demoText[ 50 ];
new_step = pedometer_process( &pedometer );
if ( new_step == PEDOMETER_NEW_STEP_DETECTED )
{
s_counter = pedometer_get_step_counter( &pedometer );
log_printf( &logger, " Step Counter : %d \r\n ", s_counter );
Delay_ms( 50 );
}
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
