Intermediate
30 min

Revolutionize signal synthesis with our V2F converter based on the VFC32KU and MK64FN1M0VDC12

Voltage waves to frequency: The future of signal generation

V To Hz 2 Click with Clicker 2 for Kinetis

Published Sep 29, 2023

Click board™

V To Hz 2 Click

Dev Board

Clicker 2 for Kinetis

Compiler

NECTO Studio

MCU

MK64FN1M0VDC12

Our voltage-to-frequency technology empowers you to seamlessly convert voltage levels into highly accurate frequency signals, setting a new benchmark for signal synthesis and control

A

A

Hardware Overview

How does it work?

V to Hz 2 Click is based on the VFC32KU, a voltage-to-frequency and frequency-to-voltage converter from Texas Instruments. It accepts voltage at its input and generates a pulse train, with a frequency linearly proportional to the input voltage. The pulse train is routed to a screw terminal labeled as FOUT, as well as the mikroBUS™ INT pin, labeled as FO. The signal can be then further processed by the host MCU. When V to Hz 2 click is operated for the first time, it needs to be calibrated. The click is equipped with two variable resistors for gain and offset fine-tuning. A calibration procedure should be executed before the first use of the Click board™ since even slight variations in the components tolerances could affect the value at the output. It is recommended to correct the offset after longer

time intervals, to compensate for the aging of the passive components on the Click board™. It is done by introducing a known voltage at the input, and adjusting the gain and the offset, until the signal with the expected frequency appears on the output. As already discussed, V to Hz 2 click is equipped with the input voltage terminal (VEXT), which is used to connect the control voltage up to 3.3V. Besides having control voltage input on this terminal, it is possible to select the voltage generated by the MCU as the control voltage input, too. INPUT SEL switch can be set so that the PWM pin from the mikroBUS™ is used as the control voltage input. The PWM signal generated by the MCU is filtered out by the onboard low pass filter so that the control voltage remains constant. The VFC32KU IC requires a dual power supply with

±15V. Therefore, this Click board™ utilizes another IC in order to provide the required voltages. It uses the TPS65131, a positive and negative output DC/DC Converter, from Texas Instruments. This DC/DC converter has already been used in Boost-INV 2 click, so it was tested "on the field" for this purpose. Providing well-stabilized output with the plenty of power headroom, it is a perfect solution for the V to Hz 2 click, also. To enable the conversion circuitry, the EN pin of the TPS65131 boost converter should be pulled to a HIGH logic level. This will activate the boost converter and provide the required power for the VFC32KU IC. This pin is routed to the mikroBUS™ CS pin and it is labeled as EN.

V To Hz 2 Click hardware overview image

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.

Clicker 2 for Kinetis dimensions image

Microcontroller Overview

MCU Card / MCU

default

Architecture

ARM Cortex-M4

MCU Memory (KB)

1024

Silicon Vendor

NXP

Pin count

121

RAM (Bytes)

262144

Used MCU Pins

mikroBUS™ mapper

NC
NC
AN
NC
NC
RST
Boost Regulator Enable
PC4
CS
NC
NC
SCK
NC
NC
MISO
NC
NC
MOSI
Power Supply
3.3V
3.3V
Ground
GND
GND
PWM Input
PA10
PWM
Frequency Output
PB13
INT
NC
NC
TX
NC
NC
RX
NC
NC
SCL
NC
NC
SDA
NC
NC
5V
Ground
GND
GND
1

Take a closer look

Schematic

V To Hz 2 Click Schematic schematic

Step by step

Project assembly

Clicker 2 for PIC32MZ front image hardware assembly

Start by selecting your development board and Click board™. Begin with the Clicker 2 for Kinetis as your development board.

Clicker 2 for PIC32MZ front image hardware assembly
Buck 22 Click front image hardware assembly
Prog-cut hardware assembly
Micro B Connector Clicker 2 - upright/background hardware assembly
Necto image step 2 hardware assembly
Necto image step 3 hardware assembly
Necto image step 4 hardware assembly
Necto image step 5 hardware assembly
Necto image step 6 hardware assembly
Flip&Click PIC32MZ MCU step hardware assembly
Necto No Display image step 8 hardware assembly
Necto image step 9 hardware assembly
Necto image step 10 hardware assembly
Debug Image Necto Step hardware assembly

Track your results in real time

Application Output via Debug Mode

1. Once the code example is loaded, pressing the "DEBUG" button initiates the build process, programs it on the created setup, and enters Debug mode.

2. After the programming is completed, a header with buttons for various actions within the IDE becomes visible. Clicking the green "PLAY" button starts reading the results achieved with the Click board™. The achieved results are displayed in the Application Output tab.

DEBUG_Application_Output

Software Support

Library Description

This library contains API for V To Hz 2 Click driver.

Key functions:

  • vtohz2_get_freq_out - Function gets the out frequency on mikrobus INT pin

  • vtohz2_enable - Function performs enabling and disabling of the device

  • vtohz2_pwm_start - This function starts PWM module.

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 VToHz2 Click example
 * 
 * # Description
 * This appliaction enables usage of a converter for analog voltage input signal into a pulse wave signal of a certain frequency.
 *
 * The demo application is composed of two sections :
 * 
 * ## Application Init 
 * Initializes driver and enables the click board.
 * 
 * ## Application Task  
 * Sets the output frequency by incrementing the pwm duty cycle from 0 to 100% in an infinite loop.
 * Results are being sent to USB UART terminal.
 * 
 * \author MikroE Team
 *
 */
// ------------------------------------------------------------------- INCLUDES

#include "board.h"
#include "log.h"
#include "vtohz2.h"

// ------------------------------------------------------------------ VARIABLES

static vtohz2_t vtohz2;
static log_t logger;

static float duty_cycle = 0.5;

// ------------------------------------------------------ APPLICATION FUNCTIONS

void application_init ( void )
{
    log_cfg_t log_cfg;
    vtohz2_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.

    vtohz2_cfg_setup( &cfg );
    VTOHZ2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    vtohz2_init( &vtohz2, &cfg );

    vtohz2_enable( &vtohz2, VTOHZ2_ENABLE );
    vtohz2_pwm_start( &vtohz2 );
}

void application_task ( void )
{
    for ( duty_cycle = 0; duty_cycle <= 1.0; duty_cycle += 0.01 )
    {
        vtohz2_set_duty_cycle ( &vtohz2, duty_cycle );
        log_printf( &logger," PWM Duty: %.2f%%\r\n", duty_cycle * 100 );
        Delay_ms( 100 );
    }
    log_printf( &logger, "------------------------------\r\n" );
}

void main ( void )
{
    application_init( );

    for ( ; ; )
    {
        application_task( );
    }
}


// ------------------------------------------------------------------------ END


Additional Support

Resources

Love this project?

'Buy This Kit' button takes you directly to the shopping cart where you can easily add or remove products.