Our PGA solution enables seamless signal amplification with customizable gain settings, making it the ideal choice for your applications where precision and flexibility are paramount
A
A
Hardware Overview
How does it work?
GainAMP Click is based on the LTC6912, a dual channel, low noise, digitally programmable gain amplifier (PGA) from Analog Devices. The click is designed to work on either a 3.3V or 5V power supply. It communicates with the target MCU over the SPI interface, with additional functionality provided by the following pins on the mikroBUS™ line: AN, RST. GainAMP Click also features three
screw terminals and a power indication LED. The gains for both channels are independently programmable, using a 3-wire SPI interface to select voltage gains of 0, 1, 2, 5, 10, 20, 50, and 100V/V (LTC6912-1). All gains are inverting. The LTC6912 consists of 2 matched amplifiers with rail-to-rail outputs. When operated with unity gain, they will also process rail-to-rail input signals.
A half-supply reference generated internally at the AGND pin supports single power supply applications. It operates from single or split supplies from 2.7V to 10.5V in total. A programmable-gain amplifier (PGA) is an electronic amplifier whose gain can be controlled externally (by analog or digital signals).
Features overview
Development board
EasyAVR v7 is the seventh generation of AVR development boards specially designed for the needs of rapid development of embedded applications. It supports a wide range of 16-bit AVR microcontrollers from Microchip and has a broad set of unique functions, such as a powerful onboard mikroProg programmer and In-Circuit debugger over USB. The development board is well organized and designed so that the end-user has all the necessary elements in one place, such as switches, buttons, indicators, connectors, and others. With four different connectors for each port, EasyAVR v7 allows you to connect accessory boards, sensors, and custom electronics more
efficiently than ever. Each part of the EasyAVR v7 development board contains the components necessary for the most efficient operation of the same board. An integrated mikroProg, a fast USB 2.0 programmer with mikroICD hardware In-Circuit Debugger, offers many valuable programming/debugging options and seamless integration with the Mikroe software environment. Besides it also includes a clean and regulated power supply block for the development board. It can use a wide range of external power sources, including an external 12V power supply, 7-12V AC or 9-15V DC via DC connector/screw terminals, and a power source via the USB Type-B (USB-B)
connector. Communication options such as USB-UART and RS-232 are also included, alongside the well-established mikroBUS™ standard, three display options (7-segment, graphical, and character-based LCD), and several different DIP sockets which cover a wide range of 16-bit AVR MCUs. EasyAVR v7 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

Architecture
AVR
MCU Memory (KB)
64
Silicon Vendor
Microchip
Pin count
40
RAM (Bytes)
4096
Used MCU Pins
mikroBUS™ mapper
Take a closer look
Click board™ Schematic

Step by step
Project assembly
Track your results in real time
Application Output
1. Application Output - In Debug mode, the 'Application Output' window enables real-time data monitoring, offering direct insight into execution results. Ensure proper data display by configuring the environment correctly using the provided tutorial.

2. UART Terminal - Use the UART Terminal to monitor data transmission via a USB to UART converter, allowing direct communication between the Click board™ and your development system. Configure the baud rate and other serial settings according to your project's requirements to ensure proper functionality. For step-by-step setup instructions, refer to the provided tutorial.

3. Plot Output - The Plot feature offers a powerful way to visualize real-time sensor data, enabling trend analysis, debugging, and comparison of multiple data points. To set it up correctly, follow the provided tutorial, which includes a step-by-step example of using the Plot feature to display Click board™ readings. To use the Plot feature in your code, use the function: plot(*insert_graph_name*, variable_name);. This is a general format, and it is up to the user to replace 'insert_graph_name' with the actual graph name and 'variable_name' with the parameter to be displayed.

Software Support
Library Description
This library contains API for GainAMP Click driver.
Key functions:
gainamp_read_an_pin_value
- GainAMP read AN pin value functiongainamp_read_an_pin_voltage
- GainAMP read AN pin voltage level functiongainamp_set_gain
- Function for sets gain of the GainAMP Click
Open Source
Code example
The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.
/*!
* @file main.c
* @brief GainAMP Click example
*
* # Description
* This is an example that demonstrates the use of the GainAMP Click board.
*
* The demo application is composed of two sections :
*
* ## Application Init
* Initializes SPI module and set CS pin and RST pin as OUTPUT,
* initialization driver init and resets chip.
*
* ## Application Task
* Sets the gain for both channels, channel A and channel B.
*
* @author Stefan Ilic
*
*/
#include "board.h"
#include "log.h"
#include "gainamp.h"
static gainamp_t gainamp;
static log_t logger;
void application_init ( void )
{
log_cfg_t log_cfg; /**< Logger config object. */
gainamp_cfg_t gainamp_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.
gainamp_cfg_setup( &gainamp_cfg );
GAINAMP_MAP_MIKROBUS( gainamp_cfg, MIKROBUS_1 );
err_t init_flag = gainamp_init( &gainamp, &gainamp_cfg );
if ( ( SPI_MASTER_ERROR == init_flag ) || ( ADC_ERROR == init_flag ) ) {
log_error( &logger, " Application Init Error. " );
log_info( &logger, " Please, run program again... " );
for ( ; ; );
}
gainamp_reset( &gainamp );
Delay_ms( 100 );
log_info( &logger, " Application Task " );
}
void application_task ( void )
{
gainamp_set_gain( &gainamp, GAINAMP_CHANNEL_A_x1 | GAINAMP_CHANNEL_B_x5 );
Delay_ms( 10000 );
gainamp_set_gain( &gainamp, GAINAMP_CHANNEL_A_x10 | GAINAMP_CHANNEL_B_x100 );
Delay_ms( 10000 );
}
void main ( void )
{
application_init( );
for ( ; ; ) {
application_task( );
}
}
// ------------------------------------------------------------------------ END