Show Posts
Pages: 1 ... 30 31 [32] 33 34 ... 97
466  Using Arduino / Programming Questions / Re: GLCD ST7920 on: September 26, 2013, 02:56:03 pm
There is a section on the ST7920 on this page:

Here is a copy of that section:
    Serial mode (PSB = LOW)
        sck: Pin with label "E"
        mosi: Pin with label "RW"
        cs: Pin with label "RS".
        Example: U8GLIB_ST7920_128X64_1X(sck, mosi, cs [, reset]) is equivalent to U8GLIB_ST7920_128X64_1X(E, RW, RS, RST) for many display modules.
    Parallel mode (PSB = HIGH)
        en: Pin with label "E"
        di: Pin with label "RS"
        rw: Pin with label "RW"

Hope this helps,
467  International / Deutsch / Re: Probleme mit darstellung eines Bildes auf ein Oled Display on: September 25, 2013, 03:52:59 pm
Gibt es denn keine Anleitung, in der drawBitmap erklärt wird? Wenn nicht, hier noch zwei Ideen, woran es liegen könnte.
1) Die Breite des Bildes ist nicht durch 8 teilbar. Ich würde die Breite (in GIMP) auf 40 erhöhen. Das würde zumindest einige Fehlerquellen ausschließen.
2) Die Interpretation der Bits in einem Byte: Die kann natürlich genau falsch herum sein. Hier wäre es 'mal interessant zu sehen, was auf dem OLED dargestellt wird.

Ganz andere Alternative wäre auch u8glib... Eine Bitmap als XBM aus GIMP abgespeichert, sollte problemlos dargestellt werden:

468  International / Deutsch / Re: Probleme mit darstellung eines Bildes auf ein Oled Display on: September 25, 2013, 01:21:35 pm
Wenn es sich bei den Bilddaten tatsächlich um das Windows BMP Format handelt, kann das nicht von drawBitmap ausgegeben werden. drawBitmap erwartet ein einfaches Array mit Rohdaten. Ich würde da eher XBM benutzen (das beispielsweise mit gimp erzeugt werden kann).

469  Community / Products and Services / Re: Nokia5110 footprint compatible NEW 128x64 LCD on: September 24, 2013, 03:06:53 pm
Very nice. I have not seen new Arduino GLCD shields for a long time.

What will be the exact U8glib constructor?

470  Using Arduino / Displays / Re: teensy 3.0 with teensyduino and u8glib on: September 23, 2013, 03:53:55 pm
At least the missing "#include <Arduino.h>" should now be there.
I am sorry for not beeing more helpful here.

471  Using Arduino / Displays / Re: teensy 3.0 with teensyduino and u8glib on: September 23, 2013, 01:53:37 pm

The Arduino and AVR variants of U8glib make use of low level procedures. I have tested and implemented U8glib for the official Ardiono boards (Uno, Due, Leonardo) and the ChipKit board (PIC32). Unfortunately it does not support the Freescale K20 controllers.

472  Using Arduino / Displays / Re: char array in u8glib on: September 23, 2013, 01:37:30 pm
Maybe you should start from a working example. Try modifing the code until it does not work any more.

I have never seen such a behavior before. I have no idea what is wrong here. :-(


473  Using Arduino / Displays / Re: char array in u8glib on: September 22, 2013, 11:08:03 pm
By the way... Maybe the OLED is not compatible with the u8glib.
If I want to buy a new OLED, I searched this
Does it compatible with the u8glib? or others OLED what you proposed and where to buy?


Indeed i tested u8glib with the NHD OLED.
What looks strange to me is, that the screen goes black but goes to normal state after you connect the display to power again. In fact the software and the uC do work like nothing has happend. From that perspective, i have some doubts that this is an software issue.

Maybe you can do another test: Please add u8g.setContrast(<some low value>) to your program. The font should be come dark. Try repeating your example with different values of u8g.setContrast(). Idea is this: The display requires a lot of current. Maybe everything works with lesser current (lower values for u8g.setContrast()).


474  Using Arduino / Displays / Re: char array in u8glib on: September 22, 2013, 11:29:26 am
How is the white line connected in the video? Is it just the backlight LED?
What constructor is used in the examples? What is the exact type of the Display?

What is the error? From the video it seems that the display turns off after some time. Is this the unintended behaviour? 

475  Using Arduino / Displays / Re: Monochrome Graphic LCD 240 x 64 on: September 19, 2013, 09:48:52 am
Although not much related to Arduino, i just post my thoughs on this...

Will it work if I connect it in the same pin order of the Orignal LCD.
If this is a question, then the simple answer is "no".

You can not (simply) replace a display with the T6A39 with a display that is based on the T6963C.

You original display seems to be a "so called" controller-less display without internal memory and without a simple uC interface. It requres continues data stream to display something. The T6963 uses a frame buffer memory to drive the display and is able to show the something on the LCD without further uC interaction. Additional the T6963 has a usual 8 bit uC interface with some powerful commands.

Just compare the datasheets of the two controllers.

476  Using Arduino / Displays / Re: Use M2tklib with KS0108 GLCD -Menu functions on: September 18, 2013, 05:14:29 pm

I was not accurate enough on the font rendering topic. In fact i meant "accurate glyph positioning" instead of "font rendering". Font rendering will be perfect in both libraries.

Is far as i remember the problem was, that the font structures of GLCD did not provide all information on the ascend and decent height of the individual characters. Also it was difficult to derive width and x-offset of the glyphs. This is important for large none-monospaced fonts. But all in all it was not a big problem for GLCD: I was able to derive these numbers manually and also the fonts known to me in GLCDv3 are monospaced fonts (as far as i remember).

It shouldn't be that difficult to do with some C++ class inheritance and virtual functions.
M2tklib (and also u8glib) had been designed as pure C libraries. In both cases the C++ interface are simple wrappers around the C API. With GLCD and M2tklib, it is like this:
M2tk C++ API calls the M2tk C API
M2tk C API calls the M2tk GLCD graphics handler (calling convention in C)
M2tk GLCD graphics handler translates the calls back to C++ to call the GLCDv3 API
GLCDv3 does the graphics output on the target device.

On the other hand: GLCD + M2tklib examples are very simple. I make use of the existing GLCD object, so the user does not need to do anything except creating the M2tklib constructor.


477  Using Arduino / Displays / Re: Use M2tklib with KS0108 GLCD -Menu functions on: September 18, 2013, 05:36:23 am

Hi Pedro

Let me clarify things a little bit:
There are two different graphics libraries for the KS0108 based displays: "GLCDv3" and "U8glib"
Both do support KS0108 128x64 displays. Both have there pros and cons. And both are supported by m2tklib, however, you can not install m2tklib for both types of libraries.

That means, you have to decide: Use GLCDv3 or U8glib.
After this decision you can download and install the correct variant of m2tklib:     for GLCDv3 or      for u8glib.

From your previous post you where mentioning "GLCD" (which looks like Bill's GLCDv3 lib), but in your example you have used U8GLIB_KS0108_128 (which is obviously the U8glib library).
So it might have happend, that you wanted to use Bills GLCDv3 library, but accidently downloaded, which will unfortunately not work.

Additionally you do not need to download any additional files. Everything is included and placed in the correct folder if you download the correct variant of m2tklib.

From now on, i assume, that you want to use GLCDv3. I also assume, that GLCDv3 is already correctly installed.

To solve your problem please do the following
1) Locate the m2tklib folder and remove it completly (with all the subdirectories)
2) Download and unzip this file in the libraries folder of your Arduino tree
3) Start Arduino IDE and execute the hello world example, which should now work

Just some small words on the pros and cons of GLCD and u8glib (Bill, please correct me if i am wrong). GLCD is a lightning fast library. It has almost no additional memory consumtion and is excellent supported by Bill. My own library u8glib has some different rendering approach, is slower, uses more RAM, but also supports SPI based display controllers. Concerning m2tklib, u8glib has two more advantages: (A) Because of the different rendering approach, there will be no flickering of the screen and (B) the fonts are more precisly rendered with u8glib. In fact i designed u8glib after i wrote m2tklib, because i needed more accurate font rendering procedures to make the text appear more perfectly rendered within the text fields of m2tklib. Still GLCD is fully supported with m2tklib.

Hope this helps,

478  Using Arduino / Displays / Re: 2.7 SSD1325 OLED problem on: September 17, 2013, 03:50:28 pm
Indeed, i am also running out of ideas.


479  Using Arduino / Displays / Re: m2tklib menu and scroll bar on: September 16, 2013, 03:26:35 pm
This is not possible. VSB only works together with special elements, which are M2_STRLIST, M2_2LMENU, M2_X2LMENU and M2_INFO. You could use M2_STRLIST with 4 elements instead of the four buttons.

480  Using Arduino / Displays / Re: 2.7 SSD1325 OLED problem on: September 16, 2013, 01:11:42 pm
You could connect the reset input of the OLED with a digital pin of the Arduino. Add the pin number of that pin to the u8glib constructor. This will allow u8glib to control the reset of the OLED.

Pages: 1 ... 30 31 [32] 33 34 ... 97