12-13-2024, 03:53 PM
My M16 is deployed, so I have limited ability to make code changes of significant magnitude, i.e., solely testing the SHT31. However, I do have a couple of questions/thoughts:
- The loop() method does contain a U8G2 update. Would moving that out to a periodic task, e.g., every 30s, remove/reduce the I2C conflict and allow the SHT31 time to respond?
- The sample code I got from this board defined the SSD1306 as U8G2_SSD1306_128X64_NONAME_F_SW_I2C ("Full buffer mode") , but uses the do-while loop... looking at the docs (from my novice understanding) this approach looks to work best with a sendBuffer() approach . Would defining the SSD1306 as U8G2_SSD1306_128X64_NONAME_1_SW_I2C ( "Page buffer mode") + do-while work better? Or is this irrelevant?
- The loop() method does contain a U8G2 update. Would moving that out to a periodic task, e.g., every 30s, remove/reduce the I2C conflict and allow the SHT31 time to respond?
- The sample code I got from this board defined the SSD1306 as U8G2_SSD1306_128X64_NONAME_F_SW_I2C ("Full buffer mode") , but uses the do-while loop... looking at the docs (from my novice understanding) this approach looks to work best with a sendBuffer() approach . Would defining the SSD1306 as U8G2_SSD1306_128X64_NONAME_1_SW_I2C ( "Page buffer mode") + do-while work better? Or is this irrelevant?