Enhance automation in industrial environments and applications that need managing resistive and inductive loads up to 50mH, featuring a current capability of 0.5A for each channel
A
A
Hardware Overview
How does it work?
IPD Click - 2017 is based on the TPD2017FN, an 8-channel low-side switch featuring MOSFET outputs from Toshiba Semiconductor, designed to be directly driven by CMOS and TTL logic circuitry. It's ideally suited for driving inductive and resistive loads, such as industrial programmable logic controllers for industrial use, motors, relays, lamps in factory automation equipment, and more. A key advantage of the TPD2017FN is its built-in overcurrent and overtemperature protection, enhancing system stability by safeguarding against excessive heat and current. Equipped with the capability to handle back electromotive force from inductive loads without surpassing the component's voltage tolerance, the TPD2017FN is optimized for loads up to 50mH with a current capacity of 0.5A per channel, supported by an external power supply ranging from 8-24V. The channels can be
operated in parallel to increase the current capability of the outputs. As mentioned, this Click board™ incorporates comprehensive protection mechanisms, including overtemperature protection that deactivates all outputs (OUT1-OUT8) if the temperature exceeds 175°C and overcurrent protection that limits voltage and current during load shorts, ensuring the device and its connected peripheral safety. Designed for straightforward integration with CMOS and TTL systems, the IPD Click features input control terminals for each output channel, allowing independent channel control. Inputs IN1 to IN4 interface directly via the mikroBUS™ socket, with additional inputs IN5 to IN8 accessible through an unpopulated header. Each input control pin of the TPD2017FN is equipped with a built-in 300kΩ pull-down resistor to maintain a LOW logic state in an open state. This
Click board™ comes with optional inductive load decoupling diodes unpopulated by default, the CRS20140A from Toshiba Semiconductor, allowing users to add them in the case of higher inductive loads. Also, it is equipped with jumpers for the diode configuration of the used load switch and its power management. These jumpers are pre-configured, enabling immediate use without the need for any adjustments. 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
Clicker 2 for Kinetis 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 ARM Cortex-M4F microcontroller, the MK64FN1M0VDC12 from NXP Semiconductors, two mikroBUS™ sockets for Click board™ connectivity, a USB connector, LED indicators, buttons, a JTAG programmer connector, and two 26-pin headers for interfacing with external electronics. Its compact design with clear and easily recognizable silkscreen markings allows you to build gadgets with unique functionalities and
features quickly. Each part of the Clicker 2 for Kinetis development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Clicker 2 for Kinetis programming method, using a USB HID mikroBootloader or an external mikroProg connector for Kinetis programmer, the Clicker 2 board also includes a clean and regulated power supply module for the development kit. It provides two ways of board-powering; through the USB Micro-B cable, where onboard voltage regulators provide the appropriate voltage levels to each component on the board, or
using a Li-Polymer battery via an onboard battery connector. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several user-configurable buttons and LED indicators. Clicker 2 for Kinetis 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
![default](https://dbp-cdn.mikroe.com/catalog/mcus/resources/MK64FN1M0VDC12.jpg)
Architecture
ARM Cortex-M4
MCU Memory (KB)
1024
Silicon Vendor
NXP
Pin count
121
RAM (Bytes)
262144
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![IPD Click -2017 Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1eed6f2e-4954-6158-b74d-0242ac120003/ipd-2015-click-v100-Schematic-1.png)
Step by step
Project 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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed554e-d80f-6694-8cb9-02420a000272/AP-Step1.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-3c0f-6800-a19f-02420a000272/AP-Step3.jpg)
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](https://dbp-cdn.mikroe.com/cms/shared-resources/1eed5550-d4d0-6b20-a348-02420a000272/AP-Step4.jpg)
Software Support
Library Description
This library contains API for IPD Click -2017 driver.
Key functions:
ipd2017_all_pins_set
- IPD 2017 pin setting functionipd2017_set_out_level
- IPD 2017 set output level functionipd2017_get_out_state
- IPD 2017 get output level function
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 IPD 2017 Click Example.
*
* # Description
* This example demonstrates the use of IPD 2017 click board by toggling the output state.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Switches on all output pins state for 2 seconds, then switches them off, and turns them on one by one.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "ipd2017.h"
static ipd2017_t ipd2017; /**< IPD 2017 Click driver object. */
static log_t logger; /**< Logger object. */
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
ipd2017_cfg_t ipd2017_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.
ipd2017_cfg_setup( &ipd2017_cfg );
IPD2017_MAP_MIKROBUS( ipd2017_cfg, MIKROBUS_1 );
if ( DIGITAL_OUT_UNSUPPORTED_PIN == ipd2017_init( &ipd2017, &ipd2017_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
log_printf( &logger, " Turning OUT 1 to OUT 4 HIGH \r\n" );
ipd2017_all_pins_set( &ipd2017 );
Delay_ms( 2000 );
log_printf( &logger, " Turning OUT 1 to OUT 4 LOW \r\n" );
ipd2017_all_pins_clear( &ipd2017 );
Delay_ms( 2000 );
log_printf( &logger, " Turning OUT 1 to OUT 4 one by one \r\n" );
uint8_t out_sel = IPD2017_OUT1_PIN_MASK;
do
{
ipd2017_set_out_level( &ipd2017, out_sel, IPD2017_PIN_STATE_HIGH );
Delay_ms( 2000 );
ipd2017_set_out_level( &ipd2017, out_sel, IPD2017_PIN_STATE_LOW );
out_sel <<= 1;
}
while ( out_sel <= IPD2017_OUT4_PIN_MASK );
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END