Enhance your design, unlock the full potential of your DC motors, and attain versatile control across multiple operational modes
A
A
Hardware Overview
How does it work?
DC MOTOR 10 Click is based on the TLE 6208-6 G, a fully protected Hex-Half-Bridge-Driver explicitly designed for automotive and industrial motion control applications from Infineon Technologies. It integrates an efficient H-Bridge with a low ON resistance of approximately 0.8Ω through each branch. Furthermore, the built-in features like Over- and Undervoltage-Lockout, Over-Temperature-Protection, and the low quiescent current in standby mode open a wide range of automotive- and industrial applications. DC MOTOR 10 Click is ideally suited for the rapid development of various DC motor driving applications, including home appliances, printers, industrial equipment, mechatronic applications, and more. The part is based on Infineon Smart Power Technology SPT®, which
allows bipolar and CMOS control circuitry in accordance with DMOS power devices existing on the same monolithic circuitry. The six low and high-side drivers are freely configurable and can be controlled separately. Therefore all kinds of loads can be combined. In motion control, up to 5 actuators (DCMotors) can be connected to the six half-bridge outputs (cascade configuration). Operation modes forward (CW), reverse (CCW), brake, and high impedance are controlled from a standard SPI-Interface. Controlling the outputs via software from a central logic allows for limiting power dissipation. The internal logic of TLE 6208-6 G is supplied by the VCC voltage, typical with 5V. The VCC voltage uses an internally generated Power-On Reset (POR) to initialize
the module at Power-on. The advantage of this system is that information stored in the logic remains intact in the event of short-term failures in the supply voltage VS. The system can therefore continue to operate following VS undervoltage without having to be reprogrammed. The undervoltage information is stored and can be read out via the interface. This Click board™ can only be operated with a 5V logic voltage level. The board must perform appropriate logic voltage level conversion before using MCUs with different logic levels. However, the Click board™ comes equipped with a library containing functions and an example code that can be used as a reference for further development.
Features overview
Development board
Fusion for PIC v8 is a development board specially designed for the needs of rapid development of embedded applications. It supports a wide range of microcontrollers, such as different PIC, dsPIC, PIC24, and PIC32 MCUs regardless of their number of pins, and a broad set of unique functions, such as the first-ever embedded debugger/programmer over WiFi. The development board is well organized and designed so that the end-user has all the necessary elements, such as switches, buttons, indicators, connectors, and others, in one place. Thanks to innovative manufacturing technology, Fusion for PIC v8 provides a fluid and immersive working experience, allowing access anywhere and under any
circumstances at any time. Each part of the Fusion for PIC v8 development board contains the components necessary for the most efficient operation of the same board. In addition to the advanced integrated CODEGRIP programmer/debugger module, which offers many valuable programming/debugging options and seamless integration with the Mikroe software environment, the board also includes a clean and regulated power supply module for the development board. It can use a wide range of external power sources, including a battery, an external 12V power supply, and a power source via the USB Type-C (USB-C) connector. Communication options such as USB-UART, USB
HOST/DEVICE, CAN (on the MCU card, if supported), and Ethernet are also included, including the well-established mikroBUS™ standard, a standardized socket for the MCU card (SiBRAIN standard), and two display options (graphical and character-based LCD). Fusion for PIC v8 is an integral part of the Mikroe ecosystem for rapid development. Natively supported by Mikroe software tools, it covers many aspects of prototyping and development 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
Type
8th Generation
Architecture
PIC
MCU Memory (KB)
64
Silicon Vendor
Microchip
Pin count
80
RAM (Bytes)
3828
You complete me!
Accessories
DC Gear Motor - 430RPM (3-6V) represents an all-in-one combination of a motor and gearbox, where the addition of gear leads to a reduction of motor speed while increasing the torque output. This gear motor has a spur gearbox, making it a highly reliable solution for applications with lower torque and speed requirements. The most critical parameters for gear motors are speed, torque, and efficiency, which are, in this case, 520RPM with no load and 430RPM at maximum efficiency, alongside a current of 60mA and a torque of 50g.cm. Rated for a 3-6V operational voltage range and clockwise/counterclockwise rotation direction, this motor represents an excellent solution for many functions initially performed by brushed DC motors in robotics, medical equipment, electric door locks, and much more.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Track your results in real time
Application Output via UART Mode
1. Once the code example is loaded, pressing the "FLASH" button initiates the build process, and programs it on the created setup.
2. After the programming is completed, click on the Tools icon in the upper-right panel, and select the UART Terminal.
3. After opening the UART Terminal tab, first check the baud rate setting in the Options menu (default is 115200). If this parameter is correct, activate the terminal by clicking the "CONNECT" button.
4. Now terminal status changes from Disconnected to Connected in green, and the data is displayed in the Received data field.
Software Support
Library Description
This library contains API for DC Motor 10 Click driver.
Key functions:
void dcmotor10_resetStatusReg();
- Function is used to reset status register.void dcmotor10_enableChann1();
- Function is used to enable channel 1.void dcmotor10_sendCommand( uint16_t wrData );
- Function is used to send command.
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
* \brief DcMotor10 Click example
*
* # Description
* This example is running dc motors on channels 1 through 3.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initalizes SPI, click drivers and uninhibites the device.
*
* ## Application Task
* This example demonstrates the use of DC MOTOR 10 click by running dc motors
* on channels 1 through 3, first all 3 together and then separately.
*
* \author Jovan Stajkovic
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "dcmotor10.h"
// ------------------------------------------------------------------ VARIABLES
static dcmotor10_t dcmotor10;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( void )
{
log_cfg_t log_cfg;
dcmotor10_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 ----" );
// Click initialization.
dcmotor10_cfg_setup( &cfg );
DCMOTOR10_MAP_MIKROBUS( cfg, MIKROBUS_1 );
dcmotor10_init( &dcmotor10, &cfg );
Delay_ms( 100 );
dcmotor10_inhibit(&dcmotor10, DCMOTOR10_UNINHIBIT );
dcmotor10_send_cmd( &dcmotor10, DCMOTOR10_RESET_STATUS_REG );
Delay_ms( 100 );
}
void application_task ( void )
{
dcmotor10_send_cmd( &dcmotor10, DCMOTOR10_ENABLE_1 | DCMOTOR10_ENABLE_2
| DCMOTOR10_ENABLE_3 );
Delay_ms( 5000 );
dcmotor10_send_cmd( &dcmotor10, DCMOTOR10_ENABLE_1 );
Delay_ms( 5000 );
dcmotor10_send_cmd( &dcmotor10, DCMOTOR10_ENABLE_2 );
Delay_ms( 5000 );
dcmotor10_send_cmd( &dcmotor10, DCMOTOR10_ENABLE_3 );
Delay_ms( 5000 );
dcmotor10_send_cmd( &dcmotor10, DCMOTOR10_RESET_STATUS_REG );
Delay_ms( 1000 );
}
void main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END