Switch signals between their pull-up or pull-down states with DTH-08 and PIC32MX470F512H
Simple yet effective way to manage signal states for electronic projects, enhancing their reliability and performance
Published Mar 13, 2024
Click board™
EasyPull Click
Dev. board
6LoWPAN clicker
Compiler
NECTO Studio
MCU
PIC32MX470F512H
Configure used mikroBUS™ signals within applications to be either in a pull-up or pull-down state
A
A
Hardware Overview
How does it work?
EasyPull Click is a compact add-on board designed to empower users to easily configure used mikroBUS™ signals within their applications to be either in a pull-up or pull-down state. This board is equipped with two 8-position switches that enable the pull-up or pull-down configuration for mikroBUS™ signals such as AN, RST, PWM, and INT, as well as for communication protocols like SPI, UART, and I2C. All resistors on the EasyPull Click are set to 4.7kΩ, ensuring consistent performance across various signal lines. Whether for prototyping or final product development, EasyPull Click provides developers with a practical tool for enhancing their projects with reliable signal management capabilities. Configuring the signal lines to the desired state is straightforward, thanks to the clear directional arrows on each switch's left
side. These arrows indicate the direction to toggle the switch to achieve either a pull-up (upward direction) or pull-down (downward direction) state. This feature allows for quick and easy adjustments, enhancing the board's usability and flexibility in different project setups. Additionally, the EasyPull Click board™ offers an unpopulated header marked as EXT, which extends four signals from the switches - two from each - labeled as EXTx. This header can be used as a conventional GPIO (General Purpose Input/Output) signal according to the user's requirements. The board also includes two sets of unmarked resistors at the top, connected to the EXT signals, maintaining the 4.7kΩ resistance value consistent with the rest of the board. A unique feature of the EasyPull Click is its low-power mode capability, achieved by cutting
the ID CUT traces on the back of the board. The connection to the lower section of the board, which includes the power (PWR) LED and ID chip, is interrupted by cutting these lines. This action results in significant energy savings, making the EasyPull Click an excellent choice for energy-sensitive applications that require efficient power management. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC 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
6LoWPAN 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 PIC microcontroller, the PIC32MX470F512H from Microchip, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Along with this microcontroller, the board also contains a 2.4GHz ISM band transceiver, allowing you to add wireless communication to your target application. Its compact design provides a fluid and immersive working experience, allowing access anywhere
and under any circumstances. Each part of the 6LoWPAN Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the 6LoWPAN 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 for the Clicker board, which is more than enough to operate all onboard and additional modules, or it can power
over two standard AA batteries. 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. 6LoWPAN 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)
512
Silicon Vendor
Microchip
Pin count
64
RAM (Bytes)
131072
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 6LoWPAN 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 EasyPull Click driver.
Key functions:
easypull_get_an_pin- This function reads the state of the AN pin of EasyPull click boardeasypull_get_rst_pin- This function reads the state of the RST pin of EasyPull click boardeasypull_get_cs_pin- This function reads the state of the CS pin of EasyPull click board
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 EasyPull Click Example.
*
* # Description
* This example demonstrates the use of PIR 2 Click boards.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and USB UART logger.
*
* ## Application Task
* It checks the state of the pins and displays their state on the USB UART.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "easypull.h"
static easypull_t easypull; /**< EasyPull Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
easypull_cfg_t easypull_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.
easypull_cfg_setup( &easypull_cfg );
EASYPULL_MAP_MIKROBUS( easypull_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == easypull_init( &easypull, &easypull_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_an_pin( &easypull ) )
{
log_printf( &logger, " AN pin state: HIGH \n" );
}
else
{
log_printf( &logger, " AN pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_rst_pin( &easypull ) )
{
log_printf( &logger, " RST pin state: HIGH \n" );
}
else
{
log_printf( &logger, " RST pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_cs_pin( &easypull ) )
{
log_printf( &logger, " CS pin state: HIGH \n" );
}
else
{
log_printf( &logger, " CS pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_pwm_pin( &easypull ) )
{
log_printf( &logger, " PWM pin state: HIGH \n" );
}
else
{
log_printf( &logger, " PWM pin state: LOW \n" );
}
if ( EASYPULL_PIN_STATE_HIGH == easypull_get_int_pin( &easypull ) )
{
log_printf( &logger, " INT pin state: HIGH \n" );
}
else
{
log_printf( &logger, " INT pin state: LOW \n" );
}
log_printf( &logger, "- - - - - - - - - - - - - \r\n" );
Delay_ms( 1000 );
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
