adam/LoRa_APRS_iGate
1
0 Fork 0
mirror of https://github.com/richonguzman/LoRa_APRS_iGate.git synced 2026-10-30 18:41:58 +01:00
Code Issues 55 Packages Projects Releases Wiki Activity

Difference in I2C usage between boards #240

New Issue
Open
opened 2026-10-05 05:52:57 +02:00 by adam · 1 comment
adam commented 2026-10-05 05:52:57 +02:00
Owner
Copy link
Copy source

Is there any difference in I2C communication between the TTGO LoRa V 2.1. and Heltec Wireless Stick Lite V3 (without display) boards? Except for the pins used, of course. With the first one, I used a BME680 sensor without any problems, but with the second one, it writes to the serial output: "BME/BMP/Si7021/SHTC3 sensor Active in config but not found! Check Wiring" and error -2. What does this message actually mean? The sensor hardware is the same. Is there some kind of address error? When I don't connect the sensor at all (and it is turned on in the configuration), the board starts normally, but only transmits empty WX data.
I saw the same message on the serial port when I used INA219 in parallel on the TTGO board.

Edit:
I tested it more (in wx_utils, I uncommented the line //Serial.println(addr)):
The TTGO board can read BME280, BME680, INA219, and the second display. But not a combination of BME680 with anything else. It sends its address to the serial port, but then displays the "Check Wiring" error.
The Heltec board reads the display and BME280. It cannot read INA219 or BME680 at all.
I tried connecting directly to the board pins to keep the wires as short as possible. Otherwise, TTGO can read BME280 even on a 10m UTP cable. Does anyone have experience with this?

Would it be possible to reduce the I2C speed?

Is there any difference in I2C communication between the TTGO LoRa V 2.1. and Heltec Wireless Stick Lite V3 (without display) boards? Except for the pins used, of course. With the first one, I used a BME680 sensor without any problems, but with the second one, it writes to the serial output: "BME/BMP/Si7021/SHTC3 sensor Active in config but not found! Check Wiring" and error -2. What does this message actually mean? The sensor hardware is the same. Is there some kind of address error? When I don't connect the sensor at all (and it is turned on in the configuration), the board starts normally, but only transmits empty WX data. I saw the same message on the serial port when I used INA219 in parallel on the TTGO board. Edit: I tested it more (in wx_utils, I uncommented the line //Serial.println(addr)): The TTGO board can read BME280, BME680, INA219, and the second display. But not a combination of BME680 with anything else. It sends its address to the serial port, but then displays the "Check Wiring" error. The Heltec board reads the display and BME280. It cannot read INA219 or BME680 at all. I tried connecting directly to the board pins to keep the wires as short as possible. Otherwise, TTGO can read BME280 even on a 10m UTP cable. Does anyone have experience with this? Would it be possible to reduce the I2C speed? <!-- github-sync-id:3734425741 -->
adam commented 2026-10-05 05:52:58 +02:00
Author
Owner
Copy link
Copy source

Is there anyone who has successfully used the INA219 and BME280 together? Especially on Heltec boards...

Is there anyone who has successfully used the INA219 and BME280 together? Especially on Heltec boards... <!-- github-comment-id:3694158011 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/LoRa_APRS_iGate#240