Convert analog voltage into PWM signals with LTC6992CS6-1 and PIC18F47K42TQFP
Generate PWM signals at frequencies up to 1 MHz, providing flexibility for high-speed applications
Published Mar 15, 2024
Click board™
AN to PWM 2 Click
Dev.Board
Curiosity Nano with PIC18F47K42
Compiler
NECTO Studio
MCU
PIC18F47K42TQFP
Achieve precise analog-to-PWM signal conversion, enabling smooth control over devices like LEDs, heaters, and servo motors with minimal effort
A
A
Hardware Overview
How does it work?
AN to PWM 2 Click is based on the LTC6992CS6, a voltage-controlled PWM generator from Analog Devices. This device is chosen because it keeps its output clocking at all times and offers glitch-free, a first cycle-accurate startup within 500μs of Power-On. The output of this Click board™ can source or sink up to 16 mA, and it has a linear response, so applying a voltage in a range of -2.5 to 2.5V on its input will result in generating the PWM pulse train with a duty cycle linearly proportional to the input voltage. The output PWM signal is brought to the INT pin of the mikroBUS™ socket to enable fast and precise duty cycle measurement using the interrupt routines. The LTC6992CS6 has a MOD pin, which represents pulse-width modulation input where it is necessary to bring an analog signal. To bring the corresponding signal to that pin, this Click
board™ uses an analog circuitry made of OpAmp AD8616ARZ from Analog Devices. In the first part of the circuit, amplifier OPA1 adjusts the input signal through a reference voltage of 2.5V by the MCP1525 from Microchip and applies input voltage in a range of -2.5 to 2.5V. The next part of the circuit is the voltage divider and amplifier OPA2, which has the function of a buffer, after which the signal required by the MOD pin of the LTC6992CS6 is obtained. The output frequency can range up from 3.81Hz to 1MHz and is controlled via the AD5171, a 64-position (OTP) digital potentiometer from Analog Devices, which programs the LTC6992CS6’s internal master oscillator frequency. The output frequency is determined by this master oscillator and an internal frequency divider programmable to eight settings from 1 to 16384. It
communicates with MCU using the standard I2C serial interface that operates at clock rates up to 400 kHz and represents the most accurate way to set the frequency. It also left the possibility of adjusting the frequency via resistors RH and RL by placing appropriate resistors. This Click board™ is designed to be operated only with a 5V logic level. A proper logic voltage level conversion should be performed before the AN to PWM 2 Click is used with MCUs with different logic levels. More information about the LTC6992CS6’s functionality, electrical specifications, and typical performance can be found in the attached datasheet. However, the Click board™ comes equipped with a library that contains easy-to-use functions and a usage example that can be used as a reference for the development.
Features overview
Development board
PIC18F47K42 Curiosity Nano evaluation kit is a cutting-edge hardware platform designed to evaluate the PIC18F47K42 microcontroller (MCU). Central to its design is the inclusion of the powerful PIC18F47K42 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 2.3V to 5.1V (limited by USB input voltage), 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
40
RAM (Bytes)
8192
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.
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Schematic
Step by step
Project assembly
Start by selecting your development board and Click board™. Begin with the Curiosity Nano with PIC18F47K42 as your development board.
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.
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™.
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.
Software Support
Library Description
This library contains API for AN to PWM 2 Click driver.
Key functions:
antopwm2_set_frequency- This function sets a frequency output in a range from 500kHz to 1MHz by setting the digipot resistanceantopwm2_set_frequency_otp- This function sets a frequency output in a range from 500kHz to 1MHz by setting the digipot resistance in OTP mode
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 AN to PWM 2 Click example
*
* # Description
* This example demonstrates the use of AN to PWM 2 click board by changing the PWM output
* frequency from 500kHz to 1MHz in steps of 50kHz.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes the driver and logger.
*
* ## Application Task
* Changes the PWM output frequency every 5 seconds in steps of 50kHz going through the full range
* from 500kHz to 1MHz. The currently set frequency will be displayed on the USB UART.
*
* @note
* Applying a voltage of -2.5 to 2.5V on the input will generate the PWM pulse train
* with a duty cycle linearly proportional to the input voltage.
*
* @author Stefan Filipovic
*
*/
#include "board.h"
#include "log.h"
#include "antopwm2.h"
static antopwm2_t antopwm2;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
antopwm2_cfg_t antopwm2_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.
antopwm2_cfg_setup( &antopwm2_cfg );
ANTOPWM2_MAP_MIKROBUS( antopwm2_cfg, MIKROBUS_1 );
if ( I2C_MASTER_ERROR == antopwm2_init( &antopwm2, &antopwm2_cfg ) )
{
log_error( &logger, " Communication init." );
for ( ; ; );
}
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
static uint32_t freq = ANTOPWM2_FREQ_MIN;
if ( ANTOPWM2_OK == antopwm2_set_frequency ( &antopwm2, freq ) )
{
log_printf ( &logger, " Frequency: %lu Hz\r\n\n", freq );
}
freq += 50000;
if ( freq > ANTOPWM2_FREQ_MAX )
{
freq = ANTOPWM2_FREQ_MIN;
}
Delay_ms ( 5000 );
}
int main ( void )
{
application_init( );
for ( ; ; )
{
application_task( );
}
return 0;
}
// ------------------------------------------------------------------------ END
