Create accurately timed pulses, and ensure synchronized operations in various systems and devices
A
A
Hardware Overview
How does it work?
One Shot Click is based on the LTC6993-2, a monostable multivibrator (also known as a "one-shot" pulse generator) with a programmable pulse width of 1μs to 33.6 seconds from Analog Devices. The LTC6993-2 is part of the TimerBlox® family of versatile silicon timing devices. A single resistor, RSET, programs an internal master oscillator frequency, setting the LTC6993's time base. The output pulse width is determined by this master oscillator and an internal clock divider, NDIV, programmable to eight settings from 1 to 221. The output pulse is initiated by a transition on the trigger input (TRIG). Each part can be configured to generate positive or negative output pulses. The LTC6993-2 has four versions to provide different trigger signal polarity and retrigger capability. Besides that, LTC6993-2 also offers the ability to dynamically adjust the width of the output pulse via a separate control voltage brought to the SET
pin of the IC. A simple trimmer or potentiometer could be used; however, due to reliability reasons, the AD5241 digital potentiometer is used for that purpose on One Shot Click. The word is also about a 256-position digital potentiometer with a low-temperature coefficient (30 ppm/°C) from Analog Devices. The AD5241 communicates with the microcontroller over the standard I2C interface so that the user can easily control and precisely calculate the output pulse width just by simply setting the wiper value in the AD5241 registers. One Shot Click also contains the multi-turn trimmer wired as a resistor divider between V+ and GND and brought to the DIV pin of the LTC6993-2. The DIV pin is the programmable divider and polarity input. The polarity input, which pin voltage is internally converted into a 4-bit result (DIVCODE). The MSB of DIVCODE (POL) determines the polarity of the OUT pins. When
POL = 0, the output produces a positive pulse. When POL = 1, the output produces a negative pulse. That way, the user can easily set the output pulse width range, and polarity by setting the desired voltage on the trimmer mentioned (VR1). This Click also contains test points to ease the user's access to the referent voltage. One can separate the trimmer from the rest of the circuit using the separation switch (SW1), then precisely set and measure the desired voltage and turn the switch back in the ON position. 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
Kinetis Clicker 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-M4 microcontroller, the MK22FN512VLH12 from NXP Semiconductor, a USB connector, LED indicators, buttons, a mikroProg connector, and a header for interfacing with external electronics. Thanks to its compact design with clear and easy-recognizable silkscreen markings, it provides a fluid and immersive working experience, allowing access
anywhere and under any circumstances. Each part of the Kinetis Clicker development kit contains the components necessary for the most efficient operation of the same board. In addition to the possibility of choosing the Kinetis Clicker programming method, using USB HID mikroBootloader, or through an external mikroProg connector for Kinetis programmer, the Clicker board also includes a clean and regulated power supply module for the development kit. The USB-MiniAB connection provides up to 500mA of current, which is more than enough to operate all
onboard and additional modules. All communication methods that mikroBUS™ itself supports are on this board, including the well-established mikroBUS™ socket, reset button, and several buttons and LED indicators. Kinetis Clicker 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/MK22FN512VLH12.jpg)
Architecture
ARM Cortex-M4
MCU Memory (KB)
512
Silicon Vendor
NXP
Pin count
64
RAM (Bytes)
131072
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
![One Shot Click Schematic schematic](https://dbp-cdn.mikroe.com/catalog/click-boards/resources/1ee790af-7aa4-691e-ba26-0242ac120009/schematic.webp)
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 One Shot Click driver.
Key functions:
oneshot_get_resistance
- This function reads the resistance data from the AD5241 chiponeshot_digital_read_rst
- This function reads the digital signal from the RST pinoneshot_digital_write_cs
- This function writes the specified digital signal to the CS pin
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 OneShot Click example
*
* # Description
* This example shows the user how to configure and use the One Shot click. The click has a
* monostable monovibrator which cam generate a pulse of width between 1μs and 33.6 seconds.
*
* The demo application is composed of two sections :
*
* ## Application Init
* This function initializes and configures the logger and click modules. Resistance data,
* acquired from the AD5241, is displayed at the end of the initialization process.
*
* ## Application Task
* This function triggers one shot every 8 seconds.
*
* \author MikroE Team
*
*/
// ------------------------------------------------------------------- INCLUDES
#include "board.h"
#include "log.h"
#include "oneshot.h"
// ------------------------------------------------------------------ VARIABLES
static oneshot_t oneshot;
static log_t logger;
// ------------------------------------------------------ APPLICATION FUNCTIONS
void application_init ( )
{
log_cfg_t log_cfg;
oneshot_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.
oneshot_cfg_setup( &cfg );
ONESHOT_MAP_MIKROBUS( cfg, MIKROBUS_1 );
oneshot_init( &oneshot, &cfg );
Delay_100ms( );
oneshot_default_cfg( &oneshot );
Delay_100ms( );
log_printf( &logger, " * Resistance: %.1f Ohm\r\n", oneshot_get_resistance( &oneshot ) );
}
void application_task ( )
{
oneshot_digital_write_cs( &oneshot, 1 );
Delay_ms( 1 );
oneshot_digital_write_cs( &oneshot, 0 );
log_printf( &logger, " * One shot triggered \r\n" );
log_printf( &logger, " --------------------------- \r\n" );
Delay_ms( 8000 );
}
void main ( )
{
application_init( );
for ( ; ; )
{
application_task( );
}
}
// ------------------------------------------------------------------------ END