SPI/I2C OLED display

BrianA 2019-01-03 16:04:14 UTC #161

A question about usage of the OLED128x64 object:

Is there any way to use it without a scope object? I'm really only interested in ùsing the display for text (mode 0) and would like to avoid the overhead of a scope in my patch. Unfortunately, without a scope, I get a compile error when I try to run a patch. Alternately, what's the smallest leanest object I can include to meet the compile requirements of the OLED128x64 object?

SmashedTransistors 2019-01-03 18:14:03 UTC #162

No, there is no way ...

That's why i just added a tiar/HW/OLED128x64niceWOScope object

(note: don't forget to include a gpio/i2c/config object in all patches using tiar/HW/OLED138x64niceWOScope)

BrianA 2019-01-03 22:48:24 UTC #163

Service with a smile and a wink!! Thank you sir.

Suburb_Animal 2019-01-07 15:17:58 UTC #164

Has anyone tried to multiplex I2C Oled displays?

On Arduino itcan be done using an I2C Multiplexer : TCA9548A
One TCA9548A can multiplex up to 8 screens !
Addressing can be done using two additional digital output.

xoanxil 2019-01-08 17:11:26 UTC #165

Hi,

Is it possible to set zoom in/out? I am working with low frequencies.

Cheers!

SmashedTransistors 2019-01-08 18:11:16 UTC #166

Hi @xoanxil,

I think that zoom/scaling features should be implemented in a scope object, not in the OLED objects.

Maybe somebody already coded such a variant but I don't see such an object in the community repository.

SmashedTransistors 2019-01-08 18:13:32 UTC #167

I never experimented with such multiplexers on the Axoloti.

xoanxil 2019-01-08 20:22:00 UTC #168

Ok. Thank you for your answer!

SmashedTransistors 2019-01-08 22:40:19 UTC #169

Maybe that's another object on my todo list...

philoop 2019-01-08 23:33:33 UTC #170

yeah scope object... i need a chart object and i d wish it would be switchable

Captain_Burek 2019-01-09 09:30:15 UTC #171

This should be possible in general. I think the oled object just cares about the presence of an array called 't' in the object it is referred to. For example, I use this object to save SRAM, and it displays just fine.
scope fake.axo (929 Bytes)
If you write an object that combines this with a chart and uses the same variable, you should be able to get what you want (which you can't always )