Show Posts
Pages: 1 ... 35 36 [37] 38 39 ... 101
541  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()).


542  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? 

543  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.

544  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.


545  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,

546  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.


547  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.

548  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.

549  Using Arduino / Displays / Re: Outdoor display 3-5" OLED or something else? on: September 15, 2013, 02:08:45 pm
I hope that the display can be directly connected to the Arduino. The display has a controller included, but i have not analysed it. I assume the controller has its own frame buffer memory, so it should not be an issue to use it with an 8 Bit controller.

It seems that buy-display does not sell any frames.

Grüße aus BW
550  Using Arduino / Displays / Re: Outdoor display 3-5" OLED or something else? on: September 15, 2013, 06:34:47 am
I had already asked for a price on the DOG display. They're over 150€ a piece :-(

Which one?
The DOGS102 white reflective should be less than 10€. Ok, could be too small.

Another option could be this (or different color)
Some of them are claimed to be sunlight readable (see datasheet).

I ordered one of these displays and hope to add support for u8glib soon.
Shipping will cost extra $7. Also production will take 1 week and shipping probably another 2 weeks. At least they did not reached me until now (two weeks since my order was placed).


551  Using Arduino / Displays / Re: Outdoor display 3-5" OLED or something else? on: September 15, 2013, 12:32:51 am
Already mentioned above: Pure reflective displays are very well suited for outdoor use. There should be at least one variant for each type of the EA DOG series of displays, which is availalble as reflective version.

But small note: As far as i know there is no Arduino lib available for the UC1611 controller.

552  Using Arduino / Displays / Re: 2.7 SSD1325 OLED problem on: September 14, 2013, 02:21:39 am

OLEDs require some power. OLEDs of that size can easily draw 100mA and more (up to 400mA). The question is, how do you power your OLED. If the OLED is powered by the 3.3V output of the Arduino, then the power could break down after some (short) time. As far as i remember, the Arduino 3.3V can only provide 50mA. Maybe enough as long as the OLED is black, but insufficient as soon as something is displayed. I suggest to power the OLED by some external source (I often use 2x AA in my projects).

Another option might be, that the init sequence for the OLED is incorrect. The init sequence in u8glib has been written for the NHD OLED, so it might be different for your OLED. But from your description, i assume, that your power source can not provide enough current.

553  Using Arduino / Displays / Re: 2.7 SSD1325 OLED problem on: September 13, 2013, 12:12:26 pm
OLEDs do not have a backlight.

554  International / Deutsch / Re: Daten in Flash via PROGMEM on: September 12, 2013, 02:49:23 pm

1. Es sollten (müssen?) globale Arrays sein.
2. Man kann nicht schreibend auf die Arrays im Flash zugreifen (jedenfalls nicht so einfach)
3. Die Verwendung von PROGMEM und prog_uint16_t ist vermutlich redundant.
4. Bei meinen eigenen Versuchen mussten die PROGMEM attribute immer kurz vor dem "=" stehen.
5. Um portabel zu sein (falls die Arduino IDE doch mal irgendwann den aktuellen g++ verwenden sollte), sollte man noch ein "const" voranstellen.
6. Die von der Arduino IDE verwendete g++ Version ist recht buggy  was progmem betrifft. Da hilft es manchmal PROGMEM durch __attribute__ ((section (.progmem.meinpersonlichereindeutigerstring))) zu erstzen.

Zusammengenommen sieht das dann so aus:

const uint16_t array[5] __attribute__ ((section (.progmem.blabla))) = { 1, 2, 3, 4, 5 } ;

Ich sollte vielleicht noch erwähnen, dass auch der Zugriff nicht so trivial sein wird, wie Du es in deinem Beispiel machst.

Ich empfehle auch das Studium der folgenden Seite:

Viel Erfolg,

Edit: Die Position des attributes war von mir falsch angegeben.
555  Using Arduino / Displays / Re: 2.7 SSD1325 OLED problem on: September 12, 2013, 01:22:26 pm
In the initial thread it was written that the display is from aliexpress, but the datasheed given is from dfrobot. So i do not think that the datasheet is helpfull in this case.

Do I need to remove R20 to R21 and R18 to R19?
Exactly. Setting BS1 and BS2 to zero (that means resoldering both resistors to the 0 position) will put the display into SPI mode. The datasheet of the controller and also the datasheet from dfrobot will tell you where to find the SPI pins.
D0 = CLK
D1 = Data In
D/C = A0

Pages: 1 ... 35 36 [37] 38 39 ... 101