¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

I2C adress of OLED #ATU-10 #atu-100


 

Am I correct that the adress of the OLED display is 78 and not 42? Is the adress the same for every OLED display? The display of my (2nd) kit doesn¡®t display anything.?

vy 73 de
Rolf, DL8BAG?


 

The 0.96 inch OLED display with SSD1306 controller?is usually accessed at i2c address 3C.? Some are at address 78.
Some modules have address select pads on the back.?Refer to the SSD1306 datasheet: ? ?
?
If you have a spare ESP32, ESP8266, or other Arduino supported board lying around, compile an i2c scan tool (it only takes a few minutes)?
??
The Arduino software build uses the Wire library, available for all Arduino supported boards.?
??
?
On a Raspberry Pi?
?sudo apt-get install python-smbus i2c-tools?
?sudo i2cdetect -y 1?
?
The i2cscan utility tests communicating to all i2c addresses and reports results on the serial debug terminal.?
To actually display something, you need more code using additional libraries:?
???
???
??
??
?


 

¿ªÔÆÌåÓý

Thank you really very much for the detailled information. Now I have an idea where to dig further. Especially the hints regarding how to test the display is helpful although I will check whether the connecting cable is providing a good contact etc.?
Vy 73 de?
Rolf, DL8BAG?

Am 21.02.2022 um 16:14 schrieb N0YWB <n0ywb1@...>:

?
The 0.96 inch OLED display with SSD1306 controller?is usually accessed at i2c address 3C.? Some are at address 78.
Some modules have address select pads on the back.?Refer to the SSD1306 datasheet: ? ?
?
If you have a spare ESP32, ESP8266, or other Arduino supported board lying around, compile an i2c scan tool (it only takes a few minutes)?
??
The Arduino software build uses the Wire library, available for all Arduino supported boards.?
??
?
On a Raspberry Pi?
?sudo apt-get install python-smbus i2c-tools?
?sudo i2cdetect -y 1?
?
The i2cscan utility tests communicating to all i2c addresses and reports results on the serial debug terminal.?
To actually display something, you need more code using additional libraries:?
???
???
??
??
?


 

Hi,

two things were wrong: display type and adress - obviously the display cannot show anything if you looking at the wrong adress and afterwards try to talk to it in a foreign language :-)
Thanks again for your hints. This reveals of course one thing: without a pickit3 you would consider the kit to be defect although it wasn't and you sometimes need to dig into the details.
Vy 73 de
Rolf, DL8BAG


 

A buyer should not have to reprogram a so called pre-programmed part! It should be ready to go. Isn't that why we buy kits with the processor pre-programmed? With all the different processors being used now days, It would be expensive to have programmers for all of them.

Max KG4PID

On Wednesday, February 23, 2022, 08:55:24 AM CST, Rolf Schroeder <rolf@...> wrote:


Hi,

two things were wrong: display type and adress - obviously the display cannot show anything if you looking at the wrong adress and afterwards try to talk to it in a foreign language :-)
Thanks again for your hints. This reveals of course one thing: without a pickit3 you would consider the kit to be defect although it wasn't and you sometimes need to dig into the details.
Vy 73 de
Rolf, DL8BAG


 

¿ªÔÆÌåÓý

I agree,

the quality is by far not the same as Elecraft or QRP-Labs or Heathkit (used tobe). And I had to buy pcb from one supplyer and housing as well as diplay from another.

Vy 73 de

Rolf, DL8BAG

?

Von: [email protected] <[email protected]> Im Auftrag von Max via groups.io
Gesendet: Mittwoch, 23. Februar 2022 18:45
An: [email protected]
Betreff: Re: [ATU100] I2C adress of OLED #ATU-10 #atu-100

?

A buyer should not have to reprogram a so called pre-programmed part! It should be ready to go. Isn't that why we buy kits with the processor pre-programmed? With all the different processors being used now days, It would be expensive to have programmers for all of them.

?

Max KG4PID

?

On Wednesday, February 23, 2022, 08:55:24 AM CST, Rolf Schroeder <rolf@...> wrote:

?

?

Hi,

two things were wrong: display type and adress - obviously the display cannot show anything if you looking at the wrong adress and afterwards try to talk to it in a foreign language :-)
Thanks again for your hints. This reveals of course one thing: without a pickit3 you would consider the kit to be defect although it wasn't and you sometimes need to dig into the details.
Vy 73 de
Rolf, DL8BAG


 

The issues are caused because the nature of the design.? N7DDC did a great job on this design and made it open source including the code.? There are dozens of small companies selling "their" version of the design with no forward support.? The problem comes when the owner decides to upgrade to the latest firmware and downloads it from Github.? Along with updating the firmware, the download changes the display parameters back to the original ones which don't work on supplied display.? Get the manual at the link below and change the modifiers to match your configuration and you will be fine.


On Wed, Feb 23, 2022 at 12:45 PM, Max wrote:
?
A buyer should not have to reprogram a so called pre-programmed part! It should be ready to go. Isn't that why we buy kits with the processor pre-programmed? With all the different processors being used now days, It would be expensive to have programmers for all of them.
?
Max KG4PID
?
On Wednesday, February 23, 2022, 08:55:24 AM CST, Rolf Schroeder <rolf@...> wrote:
?
?

Hi,

two things were wrong: display type and adress - obviously the display cannot show anything if you looking at the wrong adress and afterwards try to talk to it in a foreign language :-)
Thanks again for your hints. This reveals of course one thing: without a pickit3 you would consider the kit to be defect although it wasn't and you sometimes need to dig into the details.
Vy 73 de
Rolf, DL8BAG


 

The address "issue" is actually quite simple.? I2C addresses are comprised of 7 bits and in use are followed by a read/write bit which is 0 for write and 1 for read.? As the firmware only writes and never reads, the designer chose to add the write bit into the address.? So if your display address is hex 27 for example, this is 0010 0111 in binary, add a zero for the write bit and the address becomes 0100 1110 which is hex 4E, bingo.? Another example hex 3c (0011 1100) becomes hex 78 (0111 1000).?

Hope this helps.


 

It helped me. I had already figured the bits were shifted and bit 1 was now a zero but didn't know why. Now I do!

Thanks!!
Vince - K8ZW.

On 03/06/2022 10:03 AM, David M0TGC wrote:
The address "issue" is actually quite simple. I2C addresses are
comprised of 7 bits and in use are followed by a read/write bit which is
0 for write and 1 for read. As the firmware only writes and never
reads, the designer chose to add the write bit into the address. So if
your display address is hex 27 for example, this is 0010 0111 in binary,
add a zero for the write bit and the address becomes 0100 1110 which is
hex 4E, bingo. Another example hex 3c (0011 1100) becomes hex 78 (0111
1000).

Hope this helps.
--
Michigan VHF Corporation -- nobucks dot net
K8ZW -