I can't set the i2c timeout to values lower than 1000 millis. wire.setTimeOut(n) with n<1000 also becomes 1000. Why ?

Is your board a ESP32 ? Which timeout are you using where and how and why do you want to use a timeout ? The Arduino Uno has a timeout for the low-level I2C code: setWireTimeout() - Arduino Reference The Stream class has a timeout for Serial communication (useless for the I2C bus): Stream.setTime…

ESP32 is. In a sketch that does several tasks. It also communicates with an i2C sensor module. I2C blocks the ESP32 in I2Cread() for 1 sec if the sensor is disconnected. I made the rest of the I2C operations non-blocking. But I can't change the timeout to I2Cread() in case the sensor is disconne…

put the code to read the sensor in its own task. Have the result set of the read returned in a queue. Now the code can process other things while waiting for the i2c read to return a result set. One can use the ESP32's I2C API, Inter-Integrated Circuit (I2C) - ESP32 - — ESP-IDF Programming Guide la…

Consider the following task void fParseDewPointWindChill( void *pvParameters ) { while ( !MQTTclient.connected() ) { vTaskDelay( 250 ); } struct stu_message px_message; String sDewPoint = ""; String sWindChill = ""; sDewPoint.reserve( payloadSize ); sWindChill.reserve( payloadSi…

Ok and thanks @Idahowalker , I can put i2c_read in another task, but I don't understand why the timeout was limited to a minimum of 1000 millis. I only need to read 4 bytes to see that I have communication. Create_task for a simple i2c ?

What are the functions "I2Cread()" and "i2c_read" ? Can you show the sketch ? I can mention dozens of problems, but it would be easier if you show the sketch instead of me trying to guess what your sketch is doing. My guess is that you see the I2C bus as a bus for serial data and use the Arduino …

There is nothing special in my sketch. TwoWire::requestFrom(..., timeOutMillis, ...) from Wire.cpp who calls: i2cRead(uint8_t i2c_num, uint16_t address, uint8_t* buff, size_t size, uint32_t timeOutMillis, size_t *readCount) from i2c-hal-i2c.c next: i2c_master_read_from_device((i2c_port_t)i2c_nu…

You are using something very very very very very (5 times very) special :bangbang: I have not heard of "TwoWire::requestFrom(..., timeOutMillis, ...)" before and even Google can not find the file "i2c-hal-i2c.c". Mayby you are using the second parameter for the number of bytes as timeout …

perhaps looking at the I2C code may provide reason why. So I used the words "arduino wire library github" to get to the library. Which gets me to ArduinoCore-avr/Wire.cpp at master · arduino/ArduinoCore-avr · GitHub where you can look at how the wire library does its thing. Where with some reading …

I think I am not understood. My mistake. My english. The question was simple: Why does the i2c arduino ide implementation for ESP32 not allow a read timeout lower than 1000 milliesc? Did someone else succeed under 1 sec ?

Arduino IDE, ESP32, I2C Timeout problem

Projects Networking, Protocols, and Devices

18f December 30, 2022, 3:16pm 15

Hi,
I put I2C in other Core

Topic		Replies	Views
Esp32c3 Time out when connecting via i2C General Guidance	11	2255	October 15, 2025
I2C code for sensors Sensors	21	363	May 28, 2026
Errno 110 Timeout when using I2C between Pi and Pico 2 using Arduino HAL Programming	12	169	August 21, 2026
Wire setWireTimeout not available on UNO R4 UNO R4 WiFi	1	171	December 26, 2024
IDE 2.3.7 now gives Error: 4 DEADLINE_EXCEEDED: Nesso N1	31	18991	March 30, 2026

Arduino IDE, ESP32, I2C Timeout problem

Related topics