Then you have to assign the SDA and SCL pins to I2C_1 and I2C_2. In the first example, instead of wire, we use two self-created objects that we call I2C_1 and I2C_2: TwoWire I2C_1 = TwoWire(0) īefore you say: Super, then I can create more TwoWire objects ( TwoWire I2C_3 = TwoWire(2), etc.) according to this scheme, I have to disappoint you. You don’t usually care, because the object Wire is created with the inclusion of Wire.h. The wiring of two ADS1115 is not surprising: Two ADS1115 attached to freely selected I2C pinsįor programming you need to know that Wire is an object of the TwoWire class. My choice fell on pins 15, 16, 17 and 18. If you want to use both I2C interfaces of the ESP32, you first have to choose two SDA and two SCL pins.
How to use the two I2C interfaces of the ESP32 Variant 1: Define two interfaces As usual, the I2C communication is initialized with Wire.begin(). The ADS1115 object adc is created with ADS1115_WE adc = ADS1115_WE (ADS1115_I2C_ADDRESS). ADS1115 attached to the standard I2C interface of the ESP32 No pull-ups are required for the circuit, since the ADS1115 already provides them. Just note that this module requires some initial settings and then converts voltages that are attached to the A0 port. You don’t have to deal with it in depth to understand the post. In most cases, you will use a library for the controlled I2C part.Īs an example for an I2C device, I use the A/D converter ADS1115again. If you only use the default I2C interface, there is no big difference in handling to the Arduino or ESP8266 boards (e.g. The I2C interfaces of the ESP32 are located on pins 21 and 22 and / or on freely selectable pins. you have to set them before you can use them. The second interface is not predefined regarding the pins, i.e. The default interface is located at pins 21 (SDA) and 22 (SCL). However, the I2C interfaces of the ESP32 are organized in the same way for all versions (that I am aware of!). There are a number of different ESP32 boards available. So, I assume you’ve already integrated the ESP32 into your development environment.Īnother point that I am particularly concerned about in the article is the options of passing objects to functions or other objects. I will catch up on this in a separate post. This article is not an introduction to the ESP32. You may also be able to avoid address conflicts this way. In this article, I’ll stick to the topic and show you how to use the I2C interfaces of the ESP32. In my last post, I reported on how you use the TCA9548A or simple MOSFETs to control multiple devices with the same I2C address.
0 kommentar(er)
