TOP Contributors

  1. MIKROE (2784 codes)
  2. Alcides Ramos (404 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 (141112 times)
  2. FAT32 Library (73905 times)
  3. Network Ethernet Library (58554 times)
  4. USB Device Library (48725 times)
  5. Network WiFi Library (44376 times)
  6. FT800 Library (43977 times)
  7. GSM click (30721 times)
  8. mikroSDK (29478 times)
  9. PID Library (27304 times)
  10. microSD click (27130 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

I2C 1-Wire Click

Rating:

0

Author: MIKROE

Last Updated: 2024-10-31

Package Version: 2.1.0.14

mikroSDK Library: 2.0.0.0

Category: 1-Wire

Downloaded: 412 times

Not followed.

License: MIT license  

I2C 1-Wire Click carries DS2482-800, a bridge device that performs bidirectional conversions between I2C masters and 1-Wire slave devices. These can be EEPROM chips, temperature sensors and similar devices that have momentary high source current modes.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "I2C 1-Wire Click" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "I2C 1-Wire Click" changes.

Do you want to report abuse regarding "I2C 1-Wire Click".

  • mikroSDK Library 1.0.0.0
  • Comments (0)

mikroSDK Library Blog


I2C 1 Wire Click

I2C 1-Wire Click carries DS2482-800, a bridge device that performs bidirectional conversions between I2C masters and 1-Wire slave devices. These can be EEPROM chips, temperature sensors and similar devices that have momentary high source current modes.

i2c1wire_click.png

Click Product page


Click library

  • Author : MikroE Team
  • Date : May 2020.
  • Type : I2C type

Software Support

We provide a library for the I2C1Wire 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 I2C1Wire Click driver.

Standard key functions :

  • i2c1wire_cfg_setup Config Object Initialization function.

    void i2c1wire_cfg_setup ( i2c1wire_cfg_t *cfg ); 
  • i2c1wire_init Initialization function.

    err_t i2c1wire_init ( i2c1wire_t *ctx, i2c1wire_cfg_t *cfg );

Example key functions :

  • i2c1wire_write_byte_one_wire This function writes one byte to the Click module.

    void i2c1wire_write_byte_one_wire ( i2c1wire_t *ctx, uint8_t input );
  • i2c1wire_read_byte_one_wire This function reads one byte from the Click module.

    uint8_t i2c1wire_read_byte_one_wire ( i2c1wire_t *ctx );
  • i2c1wire_one_wire_reset This function does a hardware reset of the Click module.

    void i2c1wire_one_wire_reset ( i2c1wire_t *ctx );

Examples Description

This example showcases how to initialize, confiure and use the I2C 1-Wire Click. The Click is a I2C (host) to 1-Wire interface (slave). In order for the example to work one or more 1-Wire (GPIO) Click modules are required. Gnd goes to gnd, power goes to power and the cha- nnels are there to read data from connected modules.

The demo application is composed of two sections :

Application Init

This function initializes and configures the logger and Click modules.


void application_init ( void )
{
    log_cfg_t log_cfg;
    i2c1wire_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.
    i2c1wire_cfg_setup( &cfg );
    I2C1WIRE_MAP_MIKROBUS( cfg, MIKROBUS_1 );
    i2c1wire_init( &i2c1wire, &cfg );
    Delay_1sec( );
}

Application Task

This function reads all of the channels on the Click module and displays any data it acqu- ires from them with a 100 millisecond delay.


void application_task ( void )
{
    uint8_t chan_state = 0;
    uint8_t cnt_chan = 0;
    uint8_t cnt_val = 0;
    uint8_t id_code[ 9 ] = { 0 };

    chan_state = 1;

    i2c1wire_soft_reset( &i2c1wire );
    Delay_10ms( );
    i2c1wire_set_config( &i2c1wire, I2C1WIRE_CONFIG_1WS_HIGH |
                                    I2C1WIRE_CONFIG_SPU_HIGH |
                                    I2C1WIRE_CONFIG_APU_LOW );
    Delay_10ms( );

    for ( cnt_chan = 0; cnt_chan < 8; cnt_chan++ )
    {
        i2c1wire_set_channel( &i2c1wire, cnt_chan );
        i2c1wire_one_wire_reset( &i2c1wire );
        Delay_10ms( );

        i2c1wire_write_byte_one_wire( &i2c1wire, I2C1WIRE_WIRE_COMMAND_READ_ROM );
        Delay_10ms();

        for ( cnt_val = 8; cnt_val > 0; cnt_val-- )
        {
            id_code[ cnt_val ] = i2c1wire_read_byte_one_wire( &i2c1wire );

            if ( id_code[ cnt_val ] == I2C1WIRE_WIRE_RESULT_OK )
            {
                log_printf( &logger, "\r\n Channel %d : No device on the channel\r\n", ( uint16_t ) cnt_chan );
                Delay_100ms( );
                break;
            }
            else if ( chan_state )
            {
                log_printf( &logger, " Channel %d : ID = 0x", ( uint16_t ) cnt_chan );
                chan_state = 0;
            }

            log_printf( &logger, "%d", ( uint16_t ) id_code[ cnt_val ] );
            Delay_10ms( );
        }

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

    log_printf( &logger, "***\r\n" );
} 

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.I2C1Wire

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

DIGI POT 6 click

5

DIGI POT 6 Click features the MCP41HVX1 family of devices which have dual power rails (analog and digital). The analog power rail allows high voltage on the resistor network terminal pins. The analog voltage range is determined by the V+ and V- voltages.

[Learn More]

LR 4 Click

0

LR 4 Click is a compact add-on board that contains a long-range transceiver. This board features the 32001353, RF technology-based SRD transceiver, which operates at a frequency of 868MHz from Mipot.

[Learn More]

BarGraph click - Cloud Demo

5

- The example contains all the necessary initializations and settings for a G2C click on a successful connection by Click Cloud. - BarGraph click (actuator) displays value of the counter that is settings on the Cloud. - This example demonstrate using the Actuator(counter) parser.

[Learn More]