Vext in CubeCell HTCC-AB01_V2

Hello. Are there some changes how VEXT works in dev-board V2? I tried using same as it works with V1 but I2C scanner can’t find sensors. When I switch power cable to VDD pin next to Vext pin then it can find sensors. I think the Vext pin is not giving power. Tried with 3 different V2 board.

void setup()
{
  Serial.begin(115200);
  Wire.begin();
  pinMode(Vext, OUTPUT);
  digitalWrite(Vext, LOW);
}

It is recommended to use a multimeter to measure.

I did measure with multimeter and both Vext and 3v3 seems to output 3.3v. Could there be some problem or changes with I2C then? I was also unable to detect HDC1080 sensor with Cubecell v2 using 3v3 pin for power but it works like that on CubeCell v1. Or could this be software related? Here is the PlatformIO code I use:

#include <Arduino.h>
#include "Wire.h"

void setup()
{
  Serial.begin(115200);
  Wire.begin();
  pinMode(Vext, OUTPUT);
  digitalWrite(Vext, LOW);
}

void loop()
{
  byte error, address;
  int nDevices;

  Serial.println("Scanning...");

  nDevices = 0;
  for (address = 1; address < 127; address++)
  {
    Wire.beginTransmission(address);
    error = Wire.endTransmission();

    if (error == 0)
    {
      Serial.print("I2C device found at address 0x");
      if (address < 16)
        Serial.print("0");
      Serial.print(address, HEX);
      Serial.println("  !");

      nDevices++;
    }
    else if (error == 4)
    {
      Serial.print("Unknown error at address 0x");
      if (address < 16)
        Serial.print("0");
      Serial.println(address, HEX);
    }
  }
  if (nDevices == 0)
    Serial.println("No I2C devices found\n");
  else
    Serial.println("done\n");

  delay(5000);
}

After testing more I found out it sometimes works and finds the sensor powered by Vext pin using I2C scan but most of the resets no devices are found. This never happens if using 3v3 pin. Also tried adding delay here and there but it only made things worse. Never had anything like this with CubeCell v1…

Hi @jaws, it looks to me that to enable Vext we now need to digitalWrite(Vext, HIGH) instead of digitalWrite(Vext, LOW). At least, that is what I see with my board. Can you try?