TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (405 codes)
  3. Shawon Shahryiar (307 codes)
  4. jm_palomino (133 codes)
  5. Bugz Bensce (97 codes)
  6. S P (73 codes)
  7. dany (71 codes)
  8. MikroBUS.NET Team (35 codes)
  9. NART SCHINACKOW (34 codes)
  10. Armstrong Subero (27 codes)

Most Downloaded

  1. Timer Calculator (142119 times)
  2. FAT32 Library (75409 times)
  3. Network Ethernet Library (59567 times)
  4. USB Device Library (49555 times)
  5. Network WiFi Library (45360 times)
  6. FT800 Library (44995 times)
  7. GSM click (31486 times)
  8. mikroSDK (30567 times)
  9. microSD click (27900 times)
  10. PID Library (27635 times)
Libstock prefers package manager

Package Manager

We strongly encourage users to use Package manager for sharing their code on Libstock website, because it boosts your efficiency and leaves the end user with no room for error. [more info]

< Back
mikroSDK Library

ADC 2 Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.17

mikroSDK Library: 2.0.0.0

Category: ADC

Downloaded: 533 times

Not followed.

License: MIT license  

ADC 2 Click carries MCP3551/3, which is a 22-bit ADC with automatic internal offset and gain calibration.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "ADC 2 Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "ADC 2 Click" changes.

Do you want to report abuse regarding "ADC 2 Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


ADC 2 Click

ADC 2 Click carries MCP3551/3, which is a 22-bit ADC with automatic internal offset and gain calibration.

adc2_click.png

Click Product page


Click library

  • Author : MikroE Team
  • Date : Jan 2020.
  • Type : SPI type

Software Support

We provide a library for the Adc2 Click as well as a demo application (example), developed using MikroElektronika compilers. The demo can run on all the main MikroElektronika development boards.

Package can be downloaded/installed directly form compilers IDE(recommended way), or downloaded from our LibStock, or found on mikroE github account.

Library Description

This library contains API for Adc2 Click driver.

Standard key functions :

  • Config Object Initialization function.

    void adc2_cfg_setup ( adc2_cfg_t *cfg );

  • Initialization function.

    ADC2_RETVAL adc2_init ( adc2_t ctx, adc2_cfg_t cfg );

  • Click Default Configuration function.

    void adc2_default_cfg ( adc2_t *ctx );

Example key functions :

  • Function is used to check overflow high state.

    uint8_t adc2_check_over_high ( adc2_t *ctx );

  • Function is used to check overflow low state.

    uint8_t adc2_check_over_low ( adc2_t *ctx );

  • Function is used to read specific data from ADC convertor.

    uint32_t adc2_adc_value_read ( adc2_t *ctx );

Examples Description

This application enables usage of the 22bit ADC.

The demo application is composed of two sections :

Application Init

Initalizes SPI driver and makes an initial log.


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

    adc2_cfg_setup( &cfg );
    ADC2_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    adc2_init( &adc2, &cfg );

    Delay_ms ( 100 );

    log_printf( &logger, "------------------\r\n" );
    log_printf( &logger, "    ADC 2 Click   \r\n" );
    log_printf( &logger, "------------------\r\n" );
}

Application Task

This is an example that shows the capabilities of the ADC 2 Click


void application_task ( void )
{
    uint32_t adc_val;

    //  Task implementation.

    adc_val = adc2_adc_value_read( &adc2 );

    log_printf( &logger, "Value : %d", adc_val );
    log_printf( &logger, "------------------\r\n" );
    Delay_ms ( 1000 );
}

The full application code, and ready to use projects can be installed directly form compilers IDE(recommneded) or found on LibStock page or mikroE GitHub accaunt.

Other mikroE Libraries used in the example:

  • MikroSDK.Board
  • MikroSDK.Log
  • Click.Adc2

Additional notes and informations

Depending on the development board you are using, you may need USB UART Click, USB UART 2 Click or RS232 Click to connect to your PC, for development systems with no UART to USB interface available on the board. The terminal available in all Mikroelektronika compilers, or any other terminal application of your choice, can be used to read the message.


ALSO FROM THIS AUTHOR

Cap Touch 6 Click

0

Cap Touch 6 Click is a compact add-on board that easily integrates projected capacitive touch into users' applications. This board features the IQS227D, a single-channel capacitive controller with an internal voltage regular and reference capacitor from Azoteq. Besides the capacitive sensing area, this board also has output pins for proximity and touch events with their corresponding LED indicators. The IQS227D automatically tracks slow varying environmental changes via various filters.

[Learn More]

Pressure 2 Click

0

Pressure 2 Click carries MS5803, a high resolution MEMS pressure sensor that is both precise and robust. Its measurement range is from 0 to 14 bars (with a resolution of up to 0.2 mbars), but because of the stainless steel cap enclosure, the sensor can withstand up to 30 bars of pressure. Pressure 2 Click communicates with the target board MCU either through mikroBUS SPI or I2C lines, depending on the position in which the onboard jumpers are soldered.

[Learn More]

OLED C click

5

OLED C click arries the PSP27801 OLED display, the same one that we have used on Hexiwear. The click is designed to run on 3.3V power supply only. It communicates with the target microcontroller over an SPI interface.

[Learn More]