Same Tasmota .bin compiled, same board type, different behaviors...

[nicolatun995]

I've created, using Tasmocompiler, a custom Tasmota .bin file, using the v15.0.1 base system, since I need to implement the MPU-6050 gyroscope/oscilloscope features on my NodeMCU ESP8266 boards. I need to create seven boards with an oscilloscope for each one and other sensor which change from a board to another.
As Tasmota support page points out, this are the strings I've wrote in Custom Parameters Tasmocompiler page. I've verified that these strings are reported at the bottom part of the user_config_override.h file.

#define USE_I2C 
#ifndef USE_MPU6050
#define USE_MPU6050
  #define USE_MPU6050_DMP
#endif

I've been able to create the first board by flashing, with Tasmotizer, the .bin file I've created with Tasmocompiler. By setting on the Configuration>Module for I2C SCL and I2C SDA pins, I can see the MPU-6050 output measures.
Then I've tried to flash the second board in the same way of the previous board, by connecting another MPU-6050 in the same pins of the previous board. In this case I can't see the MPU-6050 output measures, neither in the home-page nor in the console page. I've also tried to change the ESP8266 board and the MPU-6050 but the result is the same.

What am I doing wrong?
Best regards and thanks all are gonna answer me!

[sfromis]

You could verify details with commands I2CScan look for the chip I2C address, probably 0x68 or 0x69, and I2CDriver look for number 25 in the list (without a ! marker for disabled). If a chip is detected by the matching Tasmota driver, messages like I2C: APDS9960 found at 0x39 appears shortly after boot.

[laurentppol]

Hi there,
From OP post: "I need to create seven boards with an oscilloscope for each one and other sensor which change from a board to another."
I am thinking about I2C address conflict. As MPU is the same, other things vary.
I2C address space is only 127 wide. Have You checked datashets for this? And also try working esp with non-working sensors?

Laurent