While I understand that the target group of the Plug-and-Make-Kit is not supposed to deal with I2C addresses, the documents still should give the correct data.
When checking the kit that I received in July, using Nick Gammon's Scanner (and an UNO R3 plus level shifters), the result was only ABX00101, 102 and 103 are listed correctly in the AKX00069-datasheet.pdf, page 14.
Buzzer (108) is 0x1E instead of 0x3C,
Knob (107) is 0x3A instead of 0x76,
Pixels (109) is 0x36 instead of 0x6C,
Buttons (110) is 0x3E instead of 07C.
Using the address 0x1E, I could produce some sound by sending Wire1.write(data, 8); to the buzzer.
I don't have the kit so just guessing there
You could be right and the doc is incorrect.
But the doc also states that
All Modulino® nodes are designed to have the possibility of having different I2C addresses via hardware or firmware changes....With the provided software, users can change the default I2C address of the dedicated I2C interface controller firmware
Was the kit brand new when you tested ?Would it be possible that those adresses were changed from the default?
Is the issue the same for the I2C modules that you did not mention?
Note that the addresses that you mention are multiplied by 2 (or shifted one place to the left). The address bits are the 7 most significant bits, the least significant bit is the R/W bit.
If referring to the address with the shifted value is correct or not is debatable; I do not know what wisdom is from that perspective.
to J-M-L: I got my kit from Amazon, and it was sealed, absolutely new.
It is true that the addresses of last four items were shifted to the left but does that make any sense? Anyway, it led me to find another mistake: not all addresses can be modified. The addresses of the distance sensor and the thermo sensor are fixed, they cannot be modified. The address of the move sensor can be changed by soldering.
No. What is worse is that is seems to be inconsistent but I might be mistaken.
What the four modules (that you mentioned) have in common seems to be that they have a microcontroller.
Copy/paste mistake, I guess.
The forum is not quite the place to report issues; you can report the issues here: https://www.arduino.cc/en/contact-us/
It looks like there is an off by 2x error, except for one of the addresses
0x1E x 2 = 0x3C
0x3A x 2 = 0x74 (not 0x76?)
0x36 x 2 = 0x6C
0x3E x 2 = 0x7C
It might be to do with the explanation here:
1 Like
No it is not an error, but your observation is correct.
The lower ones are the actual addresses, the higher values are shifted one bit as the I2C protocol adds a modus bit - read or write bit - to it.
That is the reason why one normally never see I2C addresses above 0x7F (decimal 127).
OK there exists a 10 bit addressing scheme too, but these are rare in Arduino land
Sorry, I didn't mean an error in the spec. I meant a misunderstanding of what values the code has to use versus the values written in the specification.
I've been caught out like this before. It's what made me notice the factor of x2 difference.
1 Like
Ah, you skipped reply #3 
Guilty as charged. Sorry about that I scrolled past the table without reading the text. I'll try and be more thorough
Don't worry, And you gave a link to an explanation so you're forgiven 
I have repeated Klausj's test, and used an I2C Scanner on the Modulinos of my Plug and Make Kit.
I had all 7 Modulinos connected at the same time, the results were as follows:
I2C Scanner
Scanning...
I2C device found at address 0x1E !
I2C device found at address 0x29 !
I2C device found at address 0x36 !
I2C device found at address 0x3A !
I2C device found at address 0x3E !
I2C device found at address 0x44 !
I2C device found at address 0x6A !
I2C device found at address 0x7E !
done
These results agree with what @Klausj found.
Although 7 devices were connected, 8 addresses were found.
I don't have that board, may be the Arduino UNO R4 WiFi has an on board I2C device ? (IMU may be ? or is it how it talks to the ESP32 ?)
I didn't use the Uno R4 WiFi that comes with the Plug and Make Kit. The I2C Scanner code would not compile for that board.
I used an Uno R3, together with a Sparkfun Qwiic Shield to do the test.
I'll do some more tests with the Modulinos connected one at a time.
ah OK - then indeed I've no clue what this is... 
(and I looked at the UNO R4 WiFi doc in the mean time and there is no IMU and it seems the ESP communication link is an UART... so it would not be that either))
1 Like
Hello everyone,
Thank you very much for bringing up the issue with the I2C addresses in the product datasheet. We have taken note of the discrepancies between the I2C addresses shown by the scanner and those listed in the datasheet.
I would like to inform you that we have created a request to review and update the content of the addresses table to ensure consistency between the I2C scanner results and the default addresses mentioned in the datasheet. We are actively working on this and hope to have the documentation updated as soon as possible.
We truly appreciate your patience and understanding, and we sincerely apologize for any inconvenience this may have caused.
Thank you again for the feedback, and have a great day!
1 Like