Show Posts
Pages: 1 ... 42 43 [44] 45 46 ... 100
646  Using Arduino / Displays / Re: Need some help with my T6963-based display! on: June 19, 2013, 04:55:36 pm
Quote
So my question now is: how do I define analog outputs?
A0 = 14
A1 = 15
A2 = 16
...
see also: http://www.arduino.cc/en/Reference/AnalogPins

Oliver
647  Using Arduino / Displays / Re: Need some help with my T6963-based display! on: June 19, 2013, 04:06:22 pm
Quote
I now got the display itself working, but it's only showing a black square on the screen.
This is very good. You need to trim your variable resistor in that way, that the black pixels just disappear.

U8glib supports many displays. You need to uncomment the correct display constructor first:
Code:
// setup u8g object, please remove comment from one of the following constructor calls
// IMPORTANT NOTE: The complete list of supported devices is here: http://code.google.com/p/u8glib/wiki/device
...
//U8GLIB_T6963_128X64 u8g(8, 9, 10, 11, 4, 5, 6, 7, 14, 15, 17, 18, 16); // 8Bit Com: D0..D7: 8,9,10,11,4,5,6,7, cs=14, a0=15, wr=17, rd=18, reset=16

Additionally you need to inform U8glib how the display is connected to your Arduino board. For example if D0 is connected to Pin 8 of your board, the the first argument must be 8 for the constructor.

Quote
Could you give me a complete "hello world" example?
Could be done, but I need to know how the display is connected to your Board (see above).


Oliver
648  Using Arduino / Displays / Re: Does STRLIST in m2tklib support Touchscreen? on: June 19, 2013, 03:58:54 pm
Quote
Maybe there's a way to link an element to a variable to increment/decrement the _first variable by the height of STRLIST?
This should also work.

Oliver
649  Using Arduino / Displays / Re: Does STRLIST in m2tklib support Touchscreen? on: June 19, 2013, 03:16:05 pm
I try to make STRLIST aware of the "t1" option for the next release. Still you need the TSK elements to scroll to elements, which are not visible on the screen. I mean, once implemented "t1" will only apply to the visible elements of STRLIST. I do not have a good idea how to solve this without TSK elements...

Oliver

650  Using Arduino / Displays / Re: Does STRLIST in m2tklib support Touchscreen? on: June 19, 2013, 02:31:19 pm
Wow, good point. Thanks for reporting this.

Touch screen support has been added to m2tklib recently and it has not been tested so much. In fact, i never thought about STRLIST while implementing touch screen support. VSB on the other hand is a pure read only element. It does not receive any input.

As of now i suggest to use TSK elements to move the cursor up and down (as described in the touch screen tutorial).

I have created an issue for this...

Oliver

651  Using Arduino / Displays / Re: Need some help with my T6963-based display! on: June 19, 2013, 02:18:20 pm
Code:
U8GLIB_T6963_128X64(d0, d1, d2, d3, d4, d5, d6, d7, cs, a0, wr, rd [, reset])
from http://code.google.com/p/u8glib/ might work.

cs = /CE
a0 = C/D

The datasheet claims, that the -5V is generated and available at Vee: Place a variable resistor of 10K .. 20K between GND and Vee. Feed the output of the wiper of the variable resistor into V0.
Connect FS to GND. MD2 probably also needs to be connected to GND, but i am not sure. HLT must be connected to +5V.

Let me know if this works. The U8GLIB_T6963_128X64 constructor was not tested very much...

Oliver (u8glib)
652  Using Arduino / Displays / Re: Problem Interfacing Arduino Due and KS0108 128 X 64 LCD Screen.! on: June 17, 2013, 05:09:18 pm
Hi Bill

U8glib does  not read the busy flag. It just waits for the maximum time. U8glib could be optimized for this, but i was always thinking, that there is a much faster lib out there.

U8glib does not provide perfect support for the DUE. HW SPI is still not working. And SW SPI is not much faster than on the UNO.

Oliver
653  Using Arduino / Displays / Re: Problem Interfacing Arduino Due and KS0108 128 X 64 LCD Screen.! on: June 17, 2013, 03:52:06 pm
Quote
I do not know the state of the GLCDv3 lib with respect to KS0108
Also my mistake, I wanted to write:
I do not know the state of the GLCDv3 lib with respect to Arduino Due.

 smiley-red

Oliver
654  Using Arduino / Displays / Re: HITACHI - LMG7420PLFC-X on: June 17, 2013, 03:49:44 pm
Hi

Your Arduino Board has the pins labeld from 0 to 13 (above the UNO logo)
Addtionally A0 = 14, A1 = 15, A2 = 16 ... (other side of the board)

Now you need to connect your display to the Arduino Board:
D0..D7: 8,9,10,11,4,5,6,7, cs=14, a0=15, wr=17, rd=18, reset=16
The numbers represent the pins on your board.
For the display only symbolic names are given, like "cs" or "a0".
You have to find these symbolic names in your datasheet. Unfortunately these symbolic names differ from LCD to LCD. Some translation is given here: http://code.google.com/p/u8glib/wiki/device

Lets make an example. cs = 14
14 means A0 on your board. "cs" is the low active chip select, however this is named "ce" in your datasheet (p14) which is A14.
So you have to connect A14 from your display with A0 on the Uno.

a0 = 15
15 is A1 on the Uno. "a0" is called C/D and is located at A4. So connect A4 from your display with A1 on the Uno.

D1 = 9
Pin 9 on the Uno is labeld with "~9". D1 is DB1 on your display and is located at A8 of your display.

I hope you can finish the rest of the pins. I suggest to write down a mapping table for the 13 pins which are required as argument for the u8glib constructor.

Once this is done, you need to investigate settings for the other pins.
A18 should be unconnected
A19 must be connected to GND (i mentioned this earlier)

Setup the remaining (power) pins as shown in section 8.3 (page 11). You probably need a -15V source along wth the normal 5V. Of course the 5V could be used from the Uno. -15V is more complicated, batteries will do, i have used a compact DC/DC converter for may own display. For testing you could also use a variable voltage source, but ensure that 5V and -15 are isolated to each other.

You can see my T6963 Varitronix display on the u8glib gallery page: http://code.google.com/p/u8glib/wiki/gallery
 

Oliver
 

655  Using Arduino / Displays / Re: Problem Interfacing Arduino Due and KS0108 128 X 64 LCD Screen.! on: June 17, 2013, 02:05:02 pm
I do not know the state of the GLCDv3 lib with respect to KS0108, but u8glib (http://code.google.com/p/u8glib/) also supports the KS0108 display. Additionally you will need a level translation from 3.3V (Due) to 5V (KS0108). Unidirectional translation is fine for u8glib. However, this setup has never been tested before with u8glib. I would be interessted to see wether it works.

Oliver

656  Using Arduino / Displays / Re: HITACHI - LMG7420PLFC-X on: June 17, 2013, 01:59:54 pm
The trick is to find the name of the controller. In your case its a T6963 controller (mentioned on one of the last pages).
You could use u8glib (http://code.google.com/p/u8glib/) with the following constructor:
Code:
U8GLIB_T6963_240X128 u8g(8, 9, 10, 11, 4, 5, 6, 7, 14, 15, 17, 18, 16); // 8Bit Com: D0..D7: 8,9,10,11,4,5,6,7, cs=14, a0=15, wr=17, rd=18, reset=16
Of course you can choose the pin numbers as given in the code above, but also any other pins are ok.

Additionally: Apply "Low" (GND) to F/S pin of the display

Oliver
657  International / Deutsch / Re: Verschiedene LCD Displays on: June 16, 2013, 02:42:47 am
Hallo maverick1509

Ich denke mit diesem

oder diesem

müsste man schon zwischen 300 und 400 Zeichen auf ein 128x64 Display bekommen.
Bei einer Höhe von 64 Pixel bekommt man 10 (oder noch mehr) Zeilen unter.

Auf den bekannten Gebrauchtwarenbörsen werden manchmal 240x128 große Displays angeboten (T6963 Controller). Das würde dann mit u8glib auch prima funktionieren und die Anzahl der verfügbaren Zeichen vervielfachen.

Der größte Vorteil wäre aber m.E. dass man kleine Fonts (unwichtigere Information) mit großen Fonts (wichtige Information) mischen kann.

Das U8glib Projekt hat eine Übersicht zu allen sofort einsetzbaren Fonts: http://code.google.com/p/u8glib/wiki/fontsize

Grüße,
Oliver

658  Using Arduino / Project Guidance / Re: Simple menu system for u8g library on: June 16, 2013, 01:55:17 am
Of course m2tklib will require some flash rom, but it is also optimized for size. The definition of menues does not eat up a lot of rom. You can define a lot of menues / dialog boxes without much increase if flash rom size. Also the size of m2tklib depends on the elements you use. If you restrict yourself to M2_U32NUM (which can handle fix point numbers like xx.x) and M2_RADIO (and of course M2_BUTTON and M2_ROOT to jump between menues), then m2tklib will keep very small. Maybe you can reduce size by smaller u8glib fonts or by using the "reduced" fonts ("r" postfix).


Oliver
659  Using Arduino / Displays / Re: double (or other) sized Fonts on ST7565 128x64 GLED on: June 12, 2013, 02:02:22 pm
U8glib is the successor of dogm128 lib. I do not recommend to use dogm128.

Oliver
660  Using Arduino / Displays / Re: double (or other) sized Fonts on ST7565 128x64 GLED on: June 11, 2013, 01:25:56 pm
Hi
You could use u8glib instead of the adafruit lib. U8glib includes "several" small and larger fonts: http://code.google.com/p/u8glib/wiki/fontsize. It also has a "double sized" option: http://code.google.com/p/u8glib/wiki/userreference#setScale2x2

Oliver
Pages: 1 ... 42 43 [44] 45 46 ... 100