SSD1306 OLED - sample code isn't working

[espruino-discuss2]

Posted at 2015-11-11 by bigplik

Hi, I've used code to run ssd1306 display from Espruino Web but it has some error
code I used

function start(){
 // write some text
 g.drawString("Hello World!",2,2);
 // write to the screen
 g.flip(); 
}

// I2C
I2C1.setup({scl:B6,sda:B7});
var g = require("SSD1306").connect(I2C1, start);

error I've got

>echo(0);
Uncaught InternalError: Timeout on I2C Write BUSY
 at line 1 col 19
{b.writeTo(d,[0,a])}
                  ^
in function called from line 1 col 147
...tion(a){b.writeTo(d,[0,a])});void 0!==c&&setTimeout(c,100);g...
                              ^
in function "connect" called from line 1 col 47
var g = require("SSD1306").connect(I2C1, start);
                                              ^
=undefined
>

anyone knows how to fix it?

[espruino-discuss2]

Posted at 2015-11-11 by bigplik

now I fixed timeouts, added 4,7k resistors from sda and scl to vdd, but can't see nothing on the screen, but Arduino code works and run display,

fixed ;)
usb socket cable wasn't keep pico strong enough to establish good connection

[gfwilliams]

Posted at 2015-11-11 by @gfwilliams

What size is your display? The default is for 128x64, but if you want to use 128x32 you have to use the code on the second half of the SSD1306 page.

[espruino-discuss2]

Posted at 2015-12-02 by bigplik

can't find command for screen rotation in ssd1306 graphic library, is there any?

[espruino-discuss2]

Posted at 2015-12-03 by DrAzzy

I think the graphics library has that?

See the reference pages

[gfwilliams]

Posted at 2015-12-03 by @gfwilliams

Yes, it's literally just g.setRotation(...)

[espruino-discuss2]

Posted at 2015-12-14 by bigplik

thank you for rotation tip,

since couple days I wonder how to write proper code to make something like display few screens on the ssd1306, let say 3 of them, and every screen will display different values, I made simple code where espruino count how many times I press the button, then depend of the number will change the screen display, but there is some issue, until I put on the display some value once (without setInterval ) then it works fluently, but when I put setInterval() function (for analog readings) I have some lag, and can't switch between screens smoothly
here is one of the codes I tried

I2C2.setup({scl:B10,sda:B3});
var g = require("SSD1306").connect(I2C2);

g.clear();
g.flip();


var S1,S2;
var BTN22 = B14;
var BTN11 = B15;
var screen = 0;

g.setFontVector(20);

pinMode(B14, 'input_pulldown');
pinMode(B15, 'input_pulldown');

function read(){
  g.clear();
  S1 = analogRead(A1);
  g.drawString("S1 " + S1.toFixed(3));
    g.flip();
}

function read2(){
    //clearInterval();
  g.clear();
  S2 = analogRead(A2);
  g.drawString("S2 " + S2.toFixed(3));
  g.flip();
}

function interval(){
  setInterval(read,500);
}

function interval2(){
  setInterval(read2,500);
}

function display(){
  if(screen === 1)interval();
  if(screen === 0)interval2();
  //console.log(screen);
}

setTimeout(function(){
  display();
},2000);

setWatch(function(e) {
  clearInterval();
  setTimeout(function(){
  display();
  console.log(screen);
  screen = screen + 1;
  if(screen > 1) screen = 0;
  },200);
},BTN11, {repeat: true, edge: 'rising', debounce:50});

where could be something wrong in my code?

[gfwilliams]

Posted at 2015-12-14 by @gfwilliams

What happens if you do:

function display(){
  g.clear();
  g.drawString("Working...");
  g.flip();
  if(screen === 1)interval();
  if(screen === 0)interval2();
  //console.log(screen);
}

When you run setInterval it will only call the function after 500ms, and then every 500ms after that.

Could that be explaining the delay you have?

[espruino-discuss2]

Posted at 2015-12-14 by bigplik

in my code button didn't react for every press I did, after 8-9 times it stock for a while, and working again and then stock next time, would like to make this screen change smooth, no lags

[gfwilliams]

Posted at 2015-12-14 by @gfwilliams

I'm afraid I don't really know why that would be then... What happens when you uncomment //console.log(screen); - does it print the number every time you press the button, or does it stop when you start having problems with the button?

[espruino-discuss2]

Posted at 2015-12-14 by bigplik

yes, numbers printed into console stop when I have the problem with the button

[gfwilliams]

Posted at 2015-12-14 by @gfwilliams

Are you sure it's not just an electrical problem with the way the button is wired up? What happens if you use the on-board button? Does it also have the problem?

[espruino-discuss2]

Posted at 2015-12-14 by bigplik

I checked that, even if I use internal BTN it still stop after several times, sometimes after tens of times, then works again, and stock, still same, maybe is something wrong in the construction of my code?

[espruino-discuss2]

Posted at 2016-01-13 by bigplik

any idea what can I do to get smooth change between screens?

[gfwilliams]

Posted at 2016-01-13 by @gfwilliams

You're still having the exact same problem with it?

[espruino-discuss2]

Posted at 2016-01-18 by bigplik

yes, it stops after several dozen press of the button, then works again and next stops

[gfwilliams]

Posted at 2016-01-18 by @gfwilliams

Try using the binary from http://www.espruino.com/binaries/git/commits/master/ in about half an hours' time and you should get a new firmware with it fixed

[espruino-discuss2]

Posted at 2016-01-18 by luwar

I think the usage of clearInterval() (with no arguments) is dangerous in general and should be avoided (except while playing in the Web IDE). Every module could use setInterval/setTimeout internally (and some do). I still like that clearInterval() does not remove the timer from setWatch anymore because it is a little unexpected.

Or is there any safe usecase for clearInterval(void) which I don't see?

[gfwilliams]

Posted at 2016-01-19 by @gfwilliams

Well, at the start of onInit() it's good - if you've saved with any intervals running but wanted to clear them - same with clearWatch().

In a small bit of code like above I don't think it's too bad as it won't interfere with anything else - but then again, if the code is that small, it's not too hard to keep track of intervals :)

[espruino-discuss2]

Posted at 2016-01-19 by bigplik

thank you Gordon, will check it today later on with new firmware

[espruino-discuss2]

Posted at 2016-03-03 by bigplik

Could anyone help to solve an issue with my code?
I have 3 screens, first screen "one" on the beginning, then second screen "OLED OFF?" and third "analogRead(A5)"
until I change screens by button (setWatch) and have no intervals set then it works really well, no lags, but when I want to update this analogRead(A5) informations every 500ms then I noticed that I can't switch to the other screen just by one push of the button, sometimes I need several or dozen push to do it, when I don't use intervals it works again,
what should I change to be able to have few screens where I can watch on different analog values updated every 500-1000ms?

function OLED(){
clearWatch();

I2C1.setup({scl:B6,sda:B7});
var g = require("SSD1306").connect(I2C1);
g.clear();
  g.flip();
  
pinMode(B14, 'input_pulldown');

var BTN22 = B15;
var screen = 0;
var battery = analogRead(A5)*2*3.3;

function screens(){
  g.clear();
  g.setFontVector(15);
  g.drawString("one",25,20);
  g.flip();
}

function screens2(){
 g.clear();
 g.setFontVector(15);
 g.drawString("OLED OFF?");g.flip();
}

function screens3(){
  battery = analogRead(A5);
 g.clear();
 g.setFontVector(20);
 g.drawString("" + battery.toFixed(2),20,20);
 g.flip();
}


setWatch(function(e) {
  clearInterval();
    screen++;
    console.log(screen);
    if(screen === 0) screens();
  if(screen === 1) screens2();
  if(screen === 2) screens3();setIterval(screens3,500);
  if(screen >= 2) screen = 0;
},BTN22, {repeat: true, edge: 'rising', debounce:150});

           
OLED();

[gfwilliams]

Posted at 2016-03-03 by @gfwilliams

Are you using an up to date firmware (1v85)? You had some problem like this before (caused by a global clearInterval and I changed the firmware to help fix it).

[espruino-discuss2]

Posted at 2016-03-03 by bigplik

I have version 1v85 and it isn't work, I have that error I described above

[gfwilliams]

Posted at 2016-03-03 by @gfwilliams

You know you've misspelt setInterval as setIterval, and haven't put brackets around functions that I think you expect to be executed in the same 'if' statement?

if(screen === 2) screens3();setIterval(screens3,500);

When you upload, do you not get any errors reported on the console? If you do, could you post them up? They might explain why it's not working.

[espruino-discuss2]

Posted at 2016-03-03 by bigplik

yes, I found it myself Gordon ;) just wanted to post I found solution ;)
my code looks now that, and is working now ;)

function OLED(){
clearWatch();

I2C1.setup({scl:B6,sda:B7});
var g = require("SSD1306").connect(I2C1);
g.clear();
  g.flip();

pinMode(B15, 'input_pulldown');

//Button tests
var BTN22 = B15;
var screen = 0;
var battery; // = analogRead(A5)*2*3.3;
var analogSample;

function screens(){
  g.clear();
  g.setFontVector(15);
  g.drawString("one",25,20);
  g.flip();
}

function screens2(){
  analogSample = analogRead(A2);
 g.clear();
 g.setFontVector(15);
 g.drawString("OLED OFF?");
 g.setFontVector(10);
 g.drawString(analogSample,60,50);
 g.flip();
}

function screens3(){
  battery = analogRead(A5);
 g.clear();
 g.setFontVector(20);
 g.drawString("" + battery.toFixed(2),20,20);
 g.flip();
}


setWatch(function(e) {
    screen++;
    console.log(screen);
    clearInterval();
    if(screen === 0) screens();
  if(screen === 1) setInterval(screens2,200);
  if(screen === 2) setInterval(screens3,500);
  if(screen >= 2) screen = 0;

  
},BTN22, {repeat: true, edge: 'rising', debounce:150});

}
           
OLED();

[espruino-discuss2]

Posted at 2016-03-03 by @MaBecker

@bigplik

took a copy of your code

got syntax error on first line: "Unmatched '{' ." where does function OLED end ?

ups, to slow, you alread found it by yourself ;-)

[espruino-discuss2]

Posted at 2016-03-03 by bigplik

found another issue,
if I want to just read analog values there clearInterval is ok, but if I want to measure something continuously, like time, stopwatch etc. then every time I swap between my screens I clear interval and will stop time or stopwatch which I don't want,
any solution?
or maybe there is some already written stopwatch code here?

[espruino-discuss2]

Posted at 2016-03-03 by DrAzzy

When you do setInterval or setTimeout they return a value. Pass that value to clearInterval and it will only clear that one.

[espruino-discuss2]

Posted at 2016-03-09 by bigplik

@drazzy ,what is the proper code form to stop interval that way you said?
I tried

clearInterval(){1}

and it works when I typed it into console,
but when I placed that form into my code into if statement
WebIDE shows errors,
I used then clearInterval(1); instead but it isn't work

[espruino-discuss2]

Posted at 2016-03-09 by MrTimcakes

DrAzzy means when you set your interval you assign it to a global variable. For example

var state, interval;
function toggleLed(){
  digitalWrite(LED1,state=!state);
}

setWatch(function() {interval=setInterval(toggleLed,500);},BTN, {repeat: true, edge: 'rising', debounce:5});

You would call clearInterval(interval) to stop only this interval.

[gfwilliams]

Posted at 2016-03-10 by @gfwilliams

@ducky thanks! I just edited your post above to change var interval=setInterval to interval=setInterval though - as using var would create a local variable rather than actually assigning to the global interval.