Ensure exceptional performance in office automation and industrial settings with TB67S102 and PIC18F57Q43
Engineered for success: Your path to seamless automation
Published Feb 13, 2024
Click board™
Multi Stepper Click - TB67S102
Dev Board
Curiosity Nano with PIC18F57Q43
Compiler
NECTO Studio
MCU
PIC18F57Q43
Our driver's primary purpose is to bring accuracy and dependability to your automation needs, driving productivity and ensuring consistent performance.
A
A
Hardware Overview
How does it work?
Multi Stepper Click is based on the TB62269FTG, a two-phase bipolar stepping motor driver using a PWM chopper (customized by external resistance R2 and capacitor C1) from Toshiba Semiconductor. The TB62269FTG comes with a built-in clock-in decoder (CLOCK-in controlled), which means that each up-edge of the CLK signal, routed to the PWM pin of the mikroBUS™ socket, will shift the motor's electrical angle per step. It also incorporates a low on-resistance MOSFET output stage, which can deliver a 1.2A current with a motor output voltage rating of 38V, in addition to integrated protection mechanisms such as over-current and over-temperature detection. In addition, it allows from full-step up to 1/32 steps resolution, with the help of which motor noise can be significantly reduced with smoother operation and more precise control. As mentioned, the TB62269FTG supports various step resolution configurations through its control signals. 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 step-resolution control signals on the onboard header J1 on pins labeled as P1 and P2 for the device's DMODE1 and DMODE2 control. The PCA9555A also allows choosing the least significant bit (LSB) of its I2C
address by positioning SMD jumpers labeled ADDR SEL to an appropriate position marked as 0 and 1. The output channel's current 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. Also, this Click board™ has a Standby function, activated when all three step-resolution control signals are in their low logic state, used to switch to Standby mode by setting all motor control pins to a low logic state. When the Standby mode is active, the TB62269FTG stops supplying the power to the internal oscillating circuit and motor output part (the motor drive cannot be performed). In addition to the I2C communication, several GPIO pins connected to the mikroBUS™ socket are also used. The Enable pin, labeled as EN and routed to the CS pin of the mikroBUS™ socket, optimizes power consumption used for power ON/OFF purposes. Also, a simple rotation direction function routed to the AN pin on the mikroBUS™ socket allows MCU to manage the direction of the stepper motor (clockwise or counterclockwise), while the RST pin of the mikroBUS™ socket initializes an electrical angle in the internal
counter to set an initial position. When it comes to angle monitoring, this driver has a dual way of monitoring selected by positioning the SMD jumper labeled as JP5 to an appropriate position marked as P6 or INT, which chooses to monitor 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, it has an additional LED for anomaly indication. Suppose a state such as an overtemperature or overcurrent is detected. In that case, such anomaly is indicated by a red LED marked as DIAG and via P7 pin over the I2C INT to the mikroBUS™ INT pin, proceeding JP5 is set to P6. Multi Stepper Click supports an external power supply for the TB62269FTG, which can be connected to the input terminal labeled as VM and should be within the range of 10V to 38V, 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.
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.
Microcontroller Overview
MCU Card / MCU
Architecture
PIC
MCU Memory (KB)
128
Silicon Vendor
Microchip
Pin count
48
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.
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 gf.cm, while the pull-in torque is 300 gf.cm. This motor makes a reliable and efficient choice for your stepper motor needs.
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 Curiosity Nano with PIC18F57Q43 as your development board.
Track your results in real time
Application Output
This Click board can be interfaced and monitored in two ways:
Application Output- Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
UART Terminal- Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.
Software Support
Library Description
This library contains API for Multi Stepper TB67S102 Click driver.
Key functions:
multisteppertb67s102_set_step_mode- This function sets the step mode resolution settings.multisteppertb67s102_drive_motor- This function drives the motor for the specific number of steps at the selected speed.multisteppertb67s102_set_direction- This function sets the motor direction by setting the AN pin logic state.
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 MultiStepperTB67S102 Click example
*
* # Description
* This example demonstrates the use of the Multi Stepper TB67S102 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 "multisteppertb67s102.h"
static multisteppertb67s102_t multisteppertb67s102;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
multisteppertb67s102_cfg_t multisteppertb67s102_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.
multisteppertb67s102_cfg_setup( &multisteppertb67s102_cfg );
MULTISTEPPERTB67S102_MAP_MIKROBUS( multisteppertb67s102_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == multisteppertb67s102_init( &multisteppertb67s102, &multisteppertb67s102_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
if ( MULTISTEPPERTB67S102_ERROR == multisteppertb67s102_default_cfg ( &multisteppertb67s102 ) )
{
log_error( &logger, " Default configuration." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf ( &logger, " Move 200 steps clockwise \r\n\n" );
multisteppertb67s102_set_direction ( &multisteppertb67s102, MULTISTEPPERTB67S102_DIR_CW );
multisteppertb67s102_drive_motor ( &multisteppertb67s102, 200, MULTISTEPPERTB67S102_SPEED_FAST );
Delay_ms ( 2000 );
log_printf ( &logger, " Move 100 steps counter-clockwise \r\n\n" );
multisteppertb67s102_set_direction ( &multisteppertb67s102, MULTISTEPPERTB67S102_DIR_CCW );
multisteppertb67s102_drive_motor ( &multisteppertb67s102, 100, MULTISTEPPERTB67S102_SPEED_FAST );
Delay_ms ( 2000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END
