SSD1306.p module poweron() method

[ruffrecords]

I am working on a battery powered Pico project where I want to minimise power use when the pico is in lightsleep(). The project has an OLED display attached for which I also want to minimise power draw during lightsleep().

The SSD1306.py library includes poweron() and poweroff() methods. The poweroff() method works as expected and the OLED power consumption drops to a around 15 microamps. However, the poweron() method does nothing. Looking at the source this is because the method consists of a single pass statement.

I found an article about the SSD1306 which listed the poweroff() command as 0xAE and the corresponding poweron() command as 0xAF. Looking again at the source of SSD1306.py I see that poweroff() calls self.write_cmd) passing it 0xAE. So, I tried modifying the poweron() method to call self.write_cmd() passing it 0xAF and I am very pleased to say it works exactly as expected. The data is retained in the display when poweroff() is called and restored when poweron() is called.

So, I have two questions.

1. I am an OOP newbie so can someone confirm that my fix is valid
2. Why is this not included in the SSD1306.py module

Cheers

Ian

[peterhinch]

I am not clear which SSD1306 driver you are using. The official driver does have a poweron() method here.

[ruffrecords]

Hi Stewart, many thanks for your reply. I had no idea that mim even existed. What a great resource.

Cheers

Ian

[peterhinch]

Also see https://awesome-micropython.com/ which is more comprehensive than mim and also recommends the official driver.

[sosi-deadeye]

mim is the best way to find these packages.

I've seen this for the first time. Is there any hint in the docs to find this?

[Josverl]

No, as it's not directly part of the project, I know @mattytrentini mentioned lt , so he will know more about its provenance

[scruss]

Also see https://awesome-micropython.com/ which is more comprehensive than mim

Awesome MicroPython may sometimes list packages that are hardware-specific or obsolete without letting the user know. This isn't the fault of the maintainers in any way.