10 min

Unleash the power of bipolar stepper motors in your projects with TB67S101 and PIC18F4550

Boost productivity, minimize downtime: Your automation ally

Multi Stepper Click - TB67S101 with Curiosity HPC

Published Nov 01, 2023

Click board™

Multi Stepper Click - TB67S101

Development board

Curiosity HPC


NECTO Studio



Our bipolar stepper motor driver is meticulously designed to provide precise and reliable motion control, making it an essential component for office automation, commercial, and industrial equipment, ensuring smooth and accurate movements in your applications.



Hardware Overview

How does it work?

Multi Stepper Click is based on the TB67S101AFG, a two-phase bipolar stepping motor driver using a PWM chopper (customized by external resistance R2 and capacitor C1) from Toshiba Semiconductor. The TB67S101AFG incorporates a low on-resistance MOSFET output stage, which can deliver a 2.8A current with a motor output voltage rating of 47V, in addition to integrated protection mechanisms such as over-current and over-temperature detection. In addition, it supports full-, half-, and quarter-step resolution, with the help of which motor noise can be significantly reduced with smoother operation and more precise control. As mentioned in the product description, this stepping motor driver is PHASE-in-controlled. These control signals are provided through the PCA9555A port expander, which establishes communication with the MCU via the I2C serial interface. This Click board™ also allows a connection of external control signals on the onboard header J1 on pins labeled as P1 and P2 for the device's PHASE-in control. The PCA9555A also allows choosing the least significant bit (LSB) of its

I2C slave address by positioning SMD jumpers labeled ADDR SEL to an appropriate position marked as 0 and 1. In addition to PHASE signals, four A/B channel logic signals, INA1, INB1, INB2, and INA2, are used to control the motor, adjusting the desired step resolution. AN, CLK, and EN pins of the mikroBUS™ socket control the first three signals. The INA2 signal allows dual control selected by positioning the SMD jumper labeled JP5 to an appropriate position marked as P6 or INT, which chooses control via the expander or INT pin of the mikroBUS™ socket. In the case of the selected INT position of the JP5 jumper, the JP10 jumper needs to be unpopulated. Also, this Click board™ has a Standby function routed to the RST pin of the mikroBUS™ socket used to switch to Standby mode by setting all motor control pins to a low logic state. When the Standby mode is active, the TB67S101AFG stops supplying the power to the internal oscillating circuit and motor output part (the motor drive cannot be performed). This Click board™ also has an additional LED for anomaly indication, but since

this version of the stepper driver does not support this feature, this indicator cannot be used. The motor A/B channel current output value can be set manually using an onboard trimmer labeled VR1, which sets the reference voltage from 0V to 3.3V. The default configuration of the JP4 jumper is the VREF position that sets both channels' output current via the VR1 trimmer. In this case, avoid position P4 on a jumper JP4 since the VREFA pin requires an analog signal for setting. Multi Stepper Click supports an external power supply for the TB67S101AFG, which can be connected to the input terminal labeled as VM and should be within the range of 10V to 47V, while the stepper motor coils can be connected to the terminals labeled as B+, B-, A-, and A+. 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.

Multi Stepper Click - TB67S101 hardware overview image

Features overview

Development board

Curiosity HPC, standing for Curiosity High Pin Count (HPC) development board, supports 28- and 40-pin 8-bit PIC MCUs specially designed by Microchip for the needs of rapid development of embedded applications. This board has two unique PDIP sockets, surrounded by dual-row expansion headers, allowing connectivity to all pins on the populated PIC MCUs. It also contains a powerful onboard PICkit™ (PKOB), eliminating the need for an external programming/debugging tool, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, a set of indicator LEDs, push button switches and a variable potentiometer. All

these features allow you to combine the strength of Microchip and Mikroe and create custom electronic solutions more efficiently than ever. Each part of the Curiosity HPC development board contains the components necessary for the most efficient operation of the same board. An integrated onboard PICkit™ (PKOB) allows low-voltage programming and in-circuit debugging for all supported devices. When used with the MPLAB® X Integrated Development Environment (IDE, version 3.0 or higher) or MPLAB® Xpress IDE, in-circuit debugging allows users to run, modify, and troubleshoot their custom software and hardware

quickly without the need for additional debugging tools. Besides, it includes a clean and regulated power supply block for the development board via the USB Micro-B connector, alongside all communication methods that mikroBUS™ itself supports. Curiosity HPC development board allows you to create a new application in just a few steps. Natively supported by Microchip software tools, it covers many aspects of prototyping thanks to many number of different Click boards™ (over a thousand boards), the number of which is growing daily.

Curiosity HPC double image

Microcontroller Overview

MCU Card / MCU




MCU Memory (KB)


Silicon Vendor


Pin count


RAM (Bytes)


You complete me!


The 28BYJ-48 is an adaptable 5VDC stepper motor with a compact design, ideal for various applications. It features four phases, a speed variation ratio of 1/64, and a stride angle of 5.625°/64 steps, allowing precise control. The motor operates at a frequency of 100Hz and has a DC resistance of 50Ω ±7% at 25°C. It boasts an idle in-traction frequency greater than 600Hz and an idle out-traction frequency exceeding 1000Hz, ensuring reliability in different scenarios. With a self-positioning torque and in-traction torque both exceeding 34.3mN.m at 120Hz, the 28BYJ-48 offers robust performance. Its friction torque ranges from 600 to 1200, while the pull-in torque is 300 This motor makes a reliable and efficient choice for your stepper motor needs.

Multi Stepper Click - TB67S101 accessories image

Used MCU Pins

mikroBUS™ mapper

A-Channel Control 1
Standby Control
B-Channel Control 2
Power Supply
B-Channel Control 1
Interrupt / A-Channel Control 2
I2C Clock
I2C Data
Power Supply

Take a closer look


Multi Stepper Click - TB67S101 Schematic schematic

Step by step

Project assembly

Curiosity HPC front no-mcu image hardware assembly

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

Curiosity HPC front no-mcu image hardware assembly
GNSS2 Click front image hardware assembly
MCU DIP 40 hardware assembly
Prog-cut hardware assembly
GNSS2 Click complete accessories setup image hardware assembly
Curiosity HPC Access MB 1 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Necto DIP image step 7 hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output

After loading the code example, pressing the "DEBUG" button builds and programs it on the selected setup.

Application Output Step 1

After programming is completed, a header with buttons for various actions available in the IDE appears. By clicking the green "PLAY "button, we start reading the results achieved with Click board™.

Application Output Step 3

Upon completion of programming, the Application Output tab is automatically opened, where the achieved result can be read. In case of an inability to perform the Debug function, check if a proper connection between the MCU used by the setup and the CODEGRIP programmer has been established. A detailed explanation of the CODEGRIP-board connection can be found in the CODEGRIP User Manual. Please find it in the RESOURCES section.

Application Output Step 4

Software Support

Library Description

This library contains API for Multi Stepper TB67S101 Click driver.

Key functions:

  • multisteppertb67s101_set_step_mode - This function sets the step mode resolution settings in ctx->step_mode.

  • multisteppertb67s101_drive_motor - This function drives the motor for the specific number of steps at the selected speed.

  • multisteppertb67s101_set_direction - This function sets the motor direction to clockwise or counter-clockwise in ctx->direction.

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 main.c
 * @brief MultiStepperTB67S101 Click example
 * # Description
 * This example demonstrates the use of the Multi Stepper TB67S101 click board by driving the 
 * motor in both directions for a desired number of steps.
 * The demo application is composed of two sections :
 * ## Application Init
 * Initializes the driver and performs the click default configuration.
 * ## Application Task
 * Drives the motor clockwise for 200 steps and then counter-clockiwse for 100 steps with
 * 2 seconds delay before changing the direction.
 * Each step will be logged on the USB UART where you can track the program flow.
 * @author Stefan Filipovic

#include "board.h"
#include "log.h"
#include "multisteppertb67s101.h"

static multisteppertb67s101_t multisteppertb67s101;
static log_t logger;

void application_init ( void ) 
    log_cfg_t log_cfg;  /**< Logger config object. */
    multisteppertb67s101_cfg_t multisteppertb67s101_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.
    multisteppertb67s101_cfg_setup( &multisteppertb67s101_cfg );
    MULTISTEPPERTB67S101_MAP_MIKROBUS( multisteppertb67s101_cfg, MIKROBUS_1 );
    if ( I2C_MASTER_ERROR == multisteppertb67s101_init( &multisteppertb67s101, &multisteppertb67s101_cfg ) ) 
        log_error( &logger, " Communication init." );
        for ( ; ; );
    if ( MULTISTEPPERTB67S101_ERROR == multisteppertb67s101_default_cfg ( &multisteppertb67s101 ) )
        log_error( &logger, " Default configuration." );
        for ( ; ; );
    log_info( &logger, " Application Task " );

void application_task ( void ) 
    multisteppertb67s101_set_direction ( &multisteppertb67s101, MULTISTEPPERTB67S101_DIR_CW );
    if ( MULTISTEPPERTB67S101_OK == multisteppertb67s101_drive_motor ( &multisteppertb67s101, 200, 
                                                                     MULTISTEPPERTB67S101_SPEED_FAST ) )
        log_printf ( &logger, " Move 200 steps clockwise \r\n\n" );
        Delay_ms ( 2000 );
    multisteppertb67s101_set_direction ( &multisteppertb67s101, MULTISTEPPERTB67S101_DIR_CCW );
    if ( MULTISTEPPERTB67S101_OK == multisteppertb67s101_drive_motor ( &multisteppertb67s101, 100,
                                                                     MULTISTEPPERTB67S101_SPEED_FAST ) )
        log_printf ( &logger, " Move 100 steps counter-clockwise \r\n\n" );
        Delay_ms ( 2000 );

void main ( void ) 
    application_init( );

    for ( ; ; ) 
        application_task( );

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

Additional Support