I tried a 3s pause before the first command and it isn't working :(
Moreover, I guess the screen is initalized as soon the bootscreen is displayed (quasi immediatly in fact)...

And after some test , it seems the lcd need differents pauses according to the commands. But it's the work of the ...

You need to pay particular attention to the acknowledge bit (specially the NAK). This indicates if the buffer is full and therefore you will need to hold off sending data."

That's what I mean , the nak is only there to prevent a buffer overflow.

But this isn't the case with the exemple . With ...

I cannot only send commands to the lcd, I have to keep attention to the NACK bit ?
So , the lcds'buffer is only a 'char' buffer , not a command buffer ?

I found the problem :
I have to introduce a pause between some commands

Look a my other topic 'Strange timing behaviour' today

I'm working on a PK202-25 PCB rev3.0 in I2C Mode at 350Kbps and I have (another) some problem.
Please take a look a this code :

LcdClearScreen();
pause(HUNDRED_MS);
LcdLocate(5,1); // set cursor to col 5 row 1
pause(HUNDRED_MS);
LcdPrintStr("Hello");

It works correctly .
If I remove the pauses ...

I tried exactly what you suggested ...
In fact some chars are printed at the good place but not the good ones:
it seems the startup screen chars are loaded (bank 0) .
I can display vertical and horizontal bars without trouble , so I have the feeling there's no numbers in the medium numbers bank

Hi,

I have exactly the same problem with a PK202-25 PCB V3.0
It seems the medium numbers are inexistant

Hello,

I want to use a PK202 with a 3.3V (but 5V tolerant)