Bring a new level of control to your projects with DH101ALSMT001 and PIC18F57Q43

Thumbs up to precision: Perfecting user experience

Thumbwheel Click with Curiosity Nano with PIC18F57Q43

Published Feb 13, 2024

Click board™

Thumbwheel Click

Dev. board

Curiosity Nano with PIC18F57Q43

Compiler

NECTO Studio

MCU

PIC18F57Q43

From concept to execution, find out how 10-position thumbwheel switch can lead you to design excellence

Hardware Overview

How does it work?

Thumbwheel Click is based on the DH101ALSMT001, 10-position thumb wheel switch from Apem. The combination of copper alloy, hard gold, stainless steel, and plastic housing makes it very robust. The thumb wheel switch has four basic pins as outputs on this Click board™, pulled down. By selecting one of the positions, the wheel switch internally connects up to four of those pins to a common VCC. The combination of the pulled-up pins can be read, thus letting the host MCU know what position of the Thumbwheel click is

selected. To make things easier, this Click board™ features the DS2408, a 1-Wire 8-channel addressable switch from Analog Devices. It is a programmable I/O device with open drain outputs that can individually capture the state changes at the PIO inputs for interrogation by the bus master. The four output pins from the DH1 are connected to the corresponding IO pins of the DS2408. The DS2408 uses a 1-Wire interface with a single digital signal at 15.3Kbls, or 100Kbps, to communicate to the host MCU. For communication, you can

choose between OW0 or OW1pins of the mikroBUS™ socket over the GP SEL (OW1 selected by default). The DS2408 has a unique factory-lasered 64-bit registration number, so more Thumbwheel Clicks can be used on a single bus. This Click board™ can operate with either 3.3V or 5V logic voltage levels selected via the VCC SEL jumper. 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

PIC18F57Q43 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate microcontrollers within the PIC18-Q43 family. Central to its design is the inclusion of the powerful PIC18F57Q43 microcontroller (MCU), offering advanced functionalities and robust performance. Key features of this evaluation kit include a yellow user LED and a responsive

mechanical user switch, providing seamless interaction and testing. The provision for a 32.768kHz crystal footprint ensures precision timing capabilities. With an onboard debugger boasting a green power and status LED, programming and debugging become intuitive and efficient. Further enhancing its utility is the Virtual serial port (CDC) and a debug GPIO channel (DGI

GPIO), offering extensive connectivity options. Powered via USB, this kit boasts an adjustable target voltage feature facilitated by the MIC5353 LDO regulator, ensuring stable operation with an output voltage ranging from 1.8V to 5.1V, with a maximum output current of 500mA, subject to ambient temperature and voltage constraints.

PIC18F57Q43 Curiosity Nano double side image

Microcontroller Overview

MCU Card / MCU

Architecture

PIC

MCU Memory (KB)

128

Silicon Vendor

Microchip

Pin count

RAM (Bytes)

8196

You complete me!

Accessories

Curiosity Nano Base for Click boards is a versatile hardware extension platform created to streamline the integration between Curiosity Nano kits and extension boards, tailored explicitly for the mikroBUS™-standardized Click boards and Xplained Pro extension boards. This innovative base board (shield) offers seamless connectivity and expansion possibilities, simplifying experimentation and development. Key features include USB power compatibility from the Curiosity Nano kit, alongside an alternative external power input option for enhanced flexibility. The onboard Li-Ion/LiPo charger and management circuit ensure smooth operation for battery-powered applications, simplifying usage and management. Moreover, the base incorporates a fixed 3.3V PSU dedicated to target and mikroBUS™ power rails, alongside a fixed 5.0V boost converter catering to 5V power rails of mikroBUS™ sockets, providing stable power delivery for various connected devices.

Used MCU Pins

mikroBUS™ mapper

1-Wire Data IN/OUT

PA0

RST

SCK

MISO

MOSI

Power Supply

3.3V

Ground

GND

1-Wire Data IN/OUT

PB0

PWM

INT

SCL

SDA

Power Supply

Ground

GND

Take a closer look

Click board™ Schematic

Step by step

Project assembly

Curiosity Nano Base for Click boards front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Curiosity Nano with PIC18F57Q43 as your development board.

Barometer 13 Click front image hardware assembly

PIC18F57Q43 Curiosity Nano front image hardware assembly

Curiosity Nano with PICXXX MB 1 - upright/background hardware assembly

PIC18F57Q43 Curiosity MCU Step hardware assembly

Necto No Display image step 8 hardware assembly

Debug Image Necto Step hardware assembly

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 Thumbwheel Click driver.

Key functions:

thumbwheel_get_position - This function gets the position of the rotary sprocket.

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 Thumbwheel Click Example.
 *
 * # Description
 * This example demonstrates the use of Thumbwheel click board 
 * by displaying the exact position of the rotary sprocket. 
 *
 * The demo application is composed of two sections :
 *
 * ## Application Init
 * Initializes the driver and checks the communication.
 *
 * ## Application Task
 * Demonstrates the usage of thumbwheel_get_position function
 * which gives the exact position of the rotary sprocket. 
 * The position will be displayed on the UART Terminal. 
 *
 * @author Aleksandra Cvjeticanin
 *
 */

#include "board.h"
#include "log.h"
#include "thumbwheel.h"

static thumbwheel_t thumbwheel;
static log_t logger;

void application_init ( void ) 
{
    log_cfg_t log_cfg;  /**< Logger config object. */
    thumbwheel_cfg_t thumbwheel_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.
    thumbwheel_cfg_setup( &thumbwheel_cfg );
    THUMBWHEEL_MAP_MIKROBUS( thumbwheel_cfg, MIKROBUS_1 );
    if ( ONE_WIRE_ERROR == thumbwheel_init( &thumbwheel, &thumbwheel_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
    
    if ( THUMBWHEEL_ERROR == thumbwheel_check_communication ( &thumbwheel ) )
    {
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    }
    
    log_info( &logger, " Application Task " );
}

void application_task ( void ) 
{
    static uint8_t old_position = 0xFF;
    uint8_t position; 
    
    if ( ( THUMBWHEEL_OK == thumbwheel_get_position ( &thumbwheel, &position ) ) && 
         ( old_position != position ) )
    {
        log_printf( &logger, " Position: %u \r\n\n", ( uint16_t ) position );
        old_position = position; 
    }
    Delay_ms( 100 );
}

void main ( void ) 
{
    application_init( );

    for ( ; ; ) 
    {
        application_task( );
    }
}

// ------------------------------------------------------------------------ END