Use your forum account to login.


TOP Contributors

  1. MikroElektronika Team (684 codes)
  2. Shawon Shahryiar (258 codes)
  3. Alcides Ramos Zambrano (168 codes)
  4. Dany (66 codes)
  5. S P (65 codes)
  6. MikroBUS.NET Team (35 codes)
  7. NART SCHINACKOW (34 codes)
  8. Roman Toropov (26 codes)
  9. FOURNET Olivier (25 codes)
  10. Alberto Trasimeni (25 codes)

Most Downloaded

  1. Timer Calculator (92121 times)
  2. FAT32 Library (48058 times)
  3. Network Ethernet Library (43900 times)
  4. USB Device Library (34135 times)
  5. Network WiFi Library (31551 times)
  6. FT800 Library (27038 times)
  7. GSM click (21335 times)
  8. PID Library (21187 times)
  9. microSD click - Example (17475 times)
  10. GSM 2 click (14345 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

I2c non blocking



Author: Dany

Last Updated: 2015-07-08

Category: Internal MCU modules

Downloaded: 2083 times

Followed by: 5 users

Replacement routines for I2c1_Rd and I2c1_Wr but here with timeout, so no blocking any more when a device one tries to access is not present.
The mE I2c library is still needed for the remaining I2c routines.

No Abuse Reported

Do you want to subscribe in order to receive notifications regarding "I2c non blocking" changes.

Do you want to unsubscribe in order to stop receiving notifications regarding "I2c non blocking" changes.

Do you want to report abuse regarding "I2c non blocking".

  • Information
  • Comments (0)

Library Blog

Library I2c_TimeOut

This library contains replacements for I2c1_Rd and I2c1_Wr with timeout functionality (so non blocking).
For the moment only available for P16 and P18 PIC's with only one HW I2c module.

All other routines of mE's I2c library are not replaced, and have to be used as before.

The interface of the non blocking (with TimeOut) I2c routines library is:
// interface

function I2C1_Rd_TimeOut(Ack: byte; TimeOut: word): byte;
// TimeOut should be >0 !  Its value is in units of 10us, so '50' means a timeout of '500 us'
// A timeout less than 100us (value of TimeOut = 10) is useless with 100 Khz clock speed.
// This function returns the I2c value read (except when I2c timeout, see below).
// See also the variables "I2c_TimeOut" and "I2C_LastError" below.

procedure I2C1_Wr_TimeOut(data_: byte; TimeOut: word);
// TimeOut should be >0 !  Its value is in units of 10us, so '50' means a timeout of '500 us'
// A timeout less than 100us (value of TimeOut = 10) is useless with 100 Khz clock speed.
// See also the variables "I2c_TimeOut" and "I2C_LastError" below.

var I2c_TimeOut: word; // After using one of the above routines the remaining timeout can be found in this variable.
                       // Check this value for an indication how close an I2C device comes to a timeout state.
    I2C_LastError: byte; // Gives the success or failiure state after using one of the above routines:
    // The following values can occur:
    //   _I2C_OK: NO error, all OK
    //   _I2C_TIMEOUT: TimeOut error
    //   _I2C_NO_ACK: No acknowledge from slave (writing only)
const // values for I2C_LastError
   _I2C_OK      = 0;
   _I2C_TIMEOUT = 1;
   _I2C_NO_ACK  = 2;


The outcome (success or some failiure) can be found in variable "I2C_LastError", see above for the possible values.
The routine usage is e.g.:
  I2c1_Wr_TimeOut(Data_, 250); // Write “Data_” with a timeout of 2500 microseconds (2.5 millisecs)
  // Check if there was a problem during above I2c write try:
  If (I2C_LastError = _I2C_OK)
  then ...                    // all OK
  else If (I2C_LastError = _I2C_TIMEOUT)                       
  then ...                    // timeout error, no response in time from the I2c device
  else If (I2C_LastError = _I2C_NO_ACK)
  then ...                    // no ack from the I2c device

If no errors occured then the time left over from the total timeOut value (in above example the "250") can be found in variable "I2c_TimeOut"

Normally an I2c transmission takes at least 90 microseconds at 100Khz, so a timeout value of less than 10 is useless.

Have fun!


2015-01-26: Replaced the mB files: all mB files are compilable now (which e.g. means that all "with" statements are dealt with). I could however not link and test the libraries (no mB licence).

Version 2.0, dd 2015-07-08: changed the interface of the library. Thanks Rainer Hantsch for the testing and  valuble suggestions!




* 2 (alternative) libs to drive LCD's (4 bits connections): - One lib specific for 2x16, - one more generic (upto 4 rows, 16-20 chars per row). * A library to drive LCD via I2c (PCF2116 based, 1 to 4 rows, 12 or 24 chars per row * A library to drive standard LCD's via I2c * A library to drive standard LCD's via SPI.

[Learn More]

PID Library


PID library with fixed calculation time interval. A PID Usage example is added. Octal delivered the mB and an mC version.

[Learn More]

Tool: Show PIC Data


This tool shows the PIC data (PIC capabilities) derived from the CSV files in the MikroProg Suite directory (and used by it).
For mP, mC and mB, PIC, dsPIC and PIC32.

[Learn More]