Show Posts
Pages: 1 ... 31 32 [33] 34 35 ... 97
481  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
Oliver
482  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)
http://www.buy-display.com/default/cog-display.html
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).

Oliver



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

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

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.

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

Oliver
486  International / Deutsch / Re: Daten in Flash via PROGMEM on: September 12, 2013, 02:49:23 pm
oh...

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:

Code:
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:
http://www.nongnu.org/avr-libc/user-manual/pgmspace.html

Viel Erfolg,
Oliver

Edit: Die Position des attributes war von mir falsch angegeben.
487  Using Arduino / Displays / Re: 2.7 SSD1325 OLED problem on: September 12, 2013, 01:22:26 pm
@TheCoolest
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.

@liming
Quote
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

Oliver
488  Using Arduino / Displays / Re: 2.7 SSD1325 OLED problem on: September 11, 2013, 11:39:45 pm
One reason could be, that the SPI mode is not enabled. In fact i wonder how this is done. Often there are jumpers or solder pads to enable SPI mode. Maybe you can attach a picture of the back side of the display to verify this.

The SPI pins are shared with the lines for 8-Bit parallel mode. You can find this information in the datasheet of the controller.

Oliver

489  Using Arduino / Displays / Re: 240x64 dots LCD display identification help on: September 10, 2013, 03:06:07 pm
Or measure the resistance between the module pin and the controller pin.

Oliver
490  Using Arduino / Displays / Re: 240x64 dots LCD display identification help on: September 10, 2013, 02:19:01 pm
ok, agree... it was not that clear on the other pics.
You could look for the controller datasheet and try to trace the pins to the controller pins. With this approach you could at least figure out the digital input.

Oliver
491  Using Arduino / Displays / Re: 240x64 dots LCD display identification help on: September 10, 2013, 12:35:44 pm
Quote
all seem to be connected to other things
Why do you think so? From your picture it seems that 21 ands 22 are not connected to something.

Oliver
492  Using Arduino / Displays / Re: GLCD (KS0108) - Pinguino/chipKIT - Code Port on: September 10, 2013, 02:49:21 am
Ok, then it might be better to ask Bill (author of GLCDv3) directly. As far as i know he planned to work on some updates.

Oliver
493  Using Arduino / Displays / Re: GLCD (KS0108) - Pinguino/chipKIT - Code Port on: September 10, 2013, 02:03:31 am
The Arduino variant of u8glib (http://code.google.com/p/u8glib/) also runs on the ChipKit board (well, at least it should run and it did run in the past, but i was to lazy to test the latest release of u8glib with the chipkit board).

U8glib supports KS0108 based displays, however note, that you can not connect the KS0108 to the ChipKit board directly, because the output levels are at 3.3V which are too less for the KS0108 controller. In fact i never got my KS0108 display work with my ChipKit Uno. However, Displays based on the ST7920 or ST7565 controller are known to work.

Hope this helps,
Oliver
494  Using Arduino / Displays / Re: 240x64 dots LCD display identification help on: September 09, 2013, 11:48:47 pm
http://www.telcona.com/fileadmin/user_upload/products/Casil/Telcona-CGM24064.pdf

Oliver
495  Using Arduino / Displays / Re: looking for a big oled screen on: September 08, 2013, 04:13:56 pm
ah, ok...
Well, from software perspective, it is a question of minutes to get it working. The NHD OLED just needs some power. But the connection to the Arduino Uno (or any other 5V board) requires a level shifter for the signals. This is indeed more complicated. For the Arduino Due it is much simpler, just connect the NHD Board directly.

Oliver
Pages: 1 ... 31 32 [33] 34 35 ... 97