Accurately quantify applied forces with FSR and STM32F031K6 for enhanced analysis
Unveiling force measurement like never before!
Published Oct 01, 2024
Click board™
Force Click
Dev. board
Nucleo 32 with STM32F031K6 MCU
Compiler
NECTO Studio
MCU
STM32F031K6
Harness the power of precise force measurement to enhance quality control across various applications
A
A
Hardware Overview
How does it work?
Force Click is based on the circuitry that allows the implementation of Force Sensing Resistors from Interlink Electronics. The Force Sensing Resistor is a thin sensor made of two membranes separated by a spacer around the edges. When pressed, the gap between the two membranes gets closed. This shorts the two membranes together with a resistance proportional to the applied force. This force sensitivity is optimized for human-machine interface devices, including automotive electronics, medical systems, industrial controls, and robotics. The FSR is a robust sensor with up to 10M of actuation and features a low device rise time of under 3 microseconds, as well as continuous analog force resolution. Force Click
sends analog values to the host MCU over the AN pin of the mikroBUS™ socket by using an OPA344, a low-power, single supply, rail-to-rail operational amplifier from Texas Instruments. This unity-gain stable OPAMP is ideal for driving sampling analog to digital converters. Rail-to-rail input and output swing significantly increase dynamic range, especially in low-power supply applications. The input to this OPA344NA is driven directly from the screw terminal and the force-sensing resistor. An ADM8829, a switched-capacitor voltage inverter with shutdown from Analog Devices, feeds the other side of the screw terminal and the force-sensing resistor. This charge-pump voltage inverter generates a negative power supply
from a positive input. The voltage conversion task is achieved using a switched capacitor technique using two external charge storage capacitors. An on-chip oscillator and switching network transfers charge between the charge storage capacitors. 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
Nucleo 32 with STM32F031K6 MCU board provides an affordable and flexible platform for experimenting with STM32 microcontrollers in 32-pin packages. Featuring Arduino™ Nano connectivity, it allows easy expansion with specialized shields, while being mbed-enabled for seamless integration with online resources. The
board includes an on-board ST-LINK/V2-1 debugger/programmer, supporting USB reenumeration with three interfaces: Virtual Com port, mass storage, and debug port. It offers a flexible power supply through either USB VBUS or an external source. Additionally, it includes three LEDs (LD1 for USB communication, LD2 for power,
and LD3 as a user LED) and a reset push button. The STM32 Nucleo-32 board is supported by various Integrated Development Environments (IDEs) such as IAR™, Keil®, and GCC-based IDEs like AC6 SW4STM32, making it a versatile tool for developers.
Microcontroller Overview
MCU Card / MCU
Architecture
ARM Cortex-M0
MCU Memory (KB)
32
Silicon Vendor
STMicroelectronics
Pin count
32
RAM (Bytes)
4096
You complete me!
Accessories
Click Shield for Nucleo-32 is the perfect way to expand your development board's functionalities with STM32 Nucleo-32 pinout. The Click Shield for Nucleo-32 provides two mikroBUS™ sockets to add any functionality from our ever-growing range of Click boards™. We are fully stocked with everything, from sensors and WiFi transceivers to motor control and audio amplifiers. The Click Shield for Nucleo-32 is compatible with the STM32 Nucleo-32 board, providing an affordable and flexible way for users to try out new ideas and quickly create prototypes with any STM32 microcontrollers, choosing from the various combinations of performance, power consumption, and features. The STM32 Nucleo-32 boards do not require any separate probe as they integrate the ST-LINK/V2-1 debugger/programmer and come with the STM32 comprehensive software HAL library and various packaged software examples. This development platform provides users with an effortless and common way to combine the STM32 Nucleo-32 footprint compatible board with their favorite Click boards™ in their upcoming projects.
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 Nucleo 32 with STM32F031K6 MCU as your development board.
Software Support
Library Description
This library contains API for Force Click driver.
Key functions:
force_generic_read- This function reads ADC dataforce_get_resistance- This function calculates resistance data based on the ADC inputforce_get_correction_factor- This function calculates the correction factor based on temperature and humidity data
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
* \brief Force Click example
*
* # Description
* This example showcases how to initialize and configure the logger and Click modules and
* read and display ADC voltage data read from the analog pin.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes and configures the logger and Click modules.
*
* ## Application Task
* This function reads and displays ADC voltage data from the analog pin every second.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "force.h"
// ------------------------------------------------------------------ VARIABLES
static force_t force;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( )
{
log_cfg_t log_cfg;
force_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 ----" );
log_printf( &logger, "--------------------\r\n" );
log_printf( &logger, " Force Click \r\n" );
log_printf( &logger, "--------------------\r\n\r\n" );
// Click initialization.
force_cfg_setup( &cfg );
FORCE_MAP_MIKROBUS( cfg, MIKROBUS_1 );
force_init( &force, &cfg );
}
void application_task ( )
{
force_data_t tmp;
// Task implementation.
tmp = force_generic_read ( &force );
log_printf( &logger, " * ADC value : %d \r\n", tmp );
log_printf( &logger, "--------------------- \r\n" );
Delay_ms ( 1000 );
}
int main ( void )
{
/* Do not remove this line or clock might not be set correctly. */
#ifdef PREINIT_SUPPORTED
preinit();
#endif
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
Additional Support
Resources
Category:Force
