Show Posts
Pages: 1 ... 42 43 [44] 45 46 ... 83
646  Using Arduino / Programming Questions / Re: Menu for Display on: January 27, 2013, 04:37:32 am
Hi
All number fields have a format option to limit the number of digits which are displayed.

See here: http://code.google.com/p/m2tklib/wiki/elref#U8NUM

The relevant part is this:
Format Options
    c: Number of digits, e.g. "c2" allows numbers between "00" and "99". Note, that this setting must fit to the min and max value.

This means you get the following results
Code:
M2_U8NUM(el,"c3",0,255,&number) --> "[000]"
M2_U8NUM(el,"c2",0,31,&number) --> "[00]"
M2_U8NUM(el,"c1",0,9,&number) --> "[0]"
The "c" format option is the key to format the output.
For your xy-grid you need to combine everything:
M2_U8NUM(el,"x0y1c2",0,31,&number) --> "[00]" at position (0,1)

Hope this helps,
Oliver

Edit: Added "code" section
647  International / Deutsch / Re: Display VLFM1383-05F Manual? on: January 27, 2013, 02:07:27 am
Im aktuellen u8glib Release ist noch ein kleiner Fehler mit der Reset Leitung enthalten, deshalb hier ein kleines bugfix release.

Oliver
648  International / Deutsch / Re: Display VLFM1383-05F Manual? on: January 26, 2013, 05:13:25 pm
@Dirk
Vielen Dank und Karma+

@Rene_Merten
1. Lade u8glib von http://code.google.com/p/u8glib/downloads/list herunter.
2. Installiere die lib wie im Wiki beschriben
3. Kommentiere in den Beispielen (sollten in der IDE an der üblichen stelle auftauchen) die Zeile
Code:
U8GLIB_SBN1661_122X32 u8g(8,9,10,11,4,5,6,7,14,15, 17, U8G_PIN_NONE, 16); ; // 8Bit Com: D0..D7: 8,9,10,11,4,5,6,7 cs1=14, cs2=15,di=17,rw=16,reset = 16
aus.
Verbinde
Arduino pin 8 mit d0
Arduino pin 9 mit d1
Arduino pin 10 mit d2
usw wie im Kommentar angegeben. Mit Cs1 ist E1 gemeint, das schrieb ich schon im letzten Beitrag von mir.
Natürlich kann man auch beliebige andere Arduino Pins nehmen, dann muss man das entsprechend im Construktor angeben (so wie bei der LiquidCrystal lib halt auch).

Wenn Fragen sind, gerne...

Grüße,
Oliver (u8glib)

Edit: Wenn es dieser Controller ist (was ja noch offen ist), dann gibt es, wie Uwe schon bemerkt hat, keinen 4 Bit Modus. Man kann aber das rw signal bei der u8glib auf GND legen und den reset über ein RC Glied schalten. Übrigens bekommt man so ab 10€ auch ein Display mit ähnlicher Auflösung, 4-Wire SPI Interface und vollständiger Doku.

649  International / Deutsch / Re: Display VLFM1383-05F Manual? on: January 26, 2013, 02:19:31 pm
Ich fasse mal zusammen:
122x32?
Ähnlich dem dip122, d.h. PT6520 controler (kompatibel zum SBN1661)
Ist plausibel, denn davon werden zwei Stück benötigt (entspricht dem Foto)
Allerdings ist der Chip an sich 5V kompatibel, d.h. die Widerstände eigentlich nicht nötig.

Pin 6 wäre dann E1 und Pin 15 wäre E2.

Ich glaube man könnte es damit mal wagen, u8glib auf das Display loszulassen.
Gemäß http://code.google.com/p/u8glib/wiki/device mit dem Constructor:
Code:
U8GLIB_SBN1661_122X32(d0, d1, d2, d3, d4, d5, d6, d7, cs1, cs2, di, rw [, reset])
di = A0
cs1 = E1
cs2 = E2

Viel Erfolg

Oliver

650  International / Deutsch / Re: Display VLFM1383-05F Manual? on: January 26, 2013, 09:43:08 am
keine Ahnung ob das hilft, aber
VL = http://www.varitronix.com

Grüße,
Oliver
651  Using Arduino / Programming Questions / Re: Menu for Display on: January 26, 2013, 09:34:51 am
Hi

I think there is some missunderstanding of the GRIDLIST. I would suggest to read documentation about it. Maybe you could instead of the GRIDLIST use the XYLIST, which might be simpler to use. With the XYLIST you must provide the left position of each child element, which lets you create more easily the menu  element.

Oliver
652  Using Arduino / Displays / Re: Arteffects! 128x64 LCD ST7920 on: January 26, 2013, 06:24:40 am
Hi

First you need to learn how to use the SD library (SD.h or SdFat.h)
Then you need a procedure which loads a file into RAM area. Then display the bitmap from RAM instead ROM (use u8g_DrawXBM instead of u8g_DrawXBMP for example)

Oliver
653  Using Arduino / Displays / Re: 12864ZW with u8glib - no DI pin?! on: January 26, 2013, 04:19:38 am
I forgot to mention, that there is a pending bug in u8glib where the reset pin is not handled correctly.
http://code.google.com/p/u8glib/issues/detail?id=133

You could:
- use a RC network for reset
- switch to SPI interface
- wait for the next official u8glib release (not scheduled yet)
- let me know if you need a prerelease

Oliver
654  Using Arduino / Displays / Re: 12864ZW with u8glib - no DI pin?! on: January 26, 2013, 12:01:17 am
The data/instruction pin (DI) might have a different name. In your case the corresponding pin is RS (register select).
Also remember to set PSB pin to "high" (connect to 5V)

Oliver
655  Using Arduino / Programming Questions / Re: Menu for Display on: January 25, 2013, 03:28:53 pm
Hi

Maybe i have not yet fully understood your problem. Do you want to program exactly one timer or more than one timer?

In either case, you need to know, what exactly needs to be entered for one timer.
You mention date and time, start and dev.
But it probably needs to be cut down to atomic data times like byte and words.
So this is probably the first step: To break down the required information to small pieces.
For example in this way:
time: hour (byte, 0..23), minute (byte, 0..59), seconds (0..59)
start: could be represented as a status byte: 0 for timer stopped, 1 for time is running. In that sense the variable should be better called "is_running". By the way it is a good practice to have a naming convention for variables. For example if all boolean variables start with "is_" then they are easily seen in the code. You could also do something like
if ( is_running ) ...
which will be executed if the time "runs"
An open question to me is the mentioned "dev" (select dev). What exactly needs to be selected? How much selectable items are there. Can it be mapped to some integer (byte) variable?

So, again, first step is to break down all this to variables. Then write some nice dialog entries for it.

Once done, the question is: Is there only one timer or are there more timers to handle. Of course the existing dialogs should be reused for each different set of timer configuration variables.

if you need to handle more than one timer, i think it will make sense to study tutorial 8: http://code.google.com/p/m2tklib/wiki/t08. Tutorial 8 has a configuration menu for the PWM output. Compare your timer data with the PWM output in this tutorial. This tutorial also introduces a top level menu. And: The PWM example is also available in the Arduino IDE (if m2tklib is installed correctly)

Oliver
656  Using Arduino / Displays / Re: 8bit grey scale LCD ? on: January 24, 2013, 03:02:23 pm
I have never seen any 8 Bit grayscale LCDs.
There are some 2 Bit graycale LCDs (DOGXL160) and OLEDs with 4 Bit grayscale (NHD-2.7-12864).

Oliver
657  Using Arduino / Displays / Re: Powertip PG12864 and Mega 2560 on: January 24, 2013, 02:59:41 pm
The Powertip PG12864 indeed uses the T6963 controller. There is a library mentioned on the Playground.
Pin connections are here: http://code.google.com/p/arduino-t6963c/wiki/T6963c

Oliver
658  Using Arduino / Programming Questions / Re: Menu for Display on: January 24, 2013, 02:53:42 pm
Hi

Excause me for not reading this thread more often.

I do not know much about the timer itself. What i can say: M2tklib will use
- digitalRead
- Serial interface for the Monitor Simulation
Can this do any harm to your system?

What you could do is to comment out
Code:
  m2.checkKey();
  m2.checkKey();
  if ( m2.handleKey() )
    m2.draw();
  m2.checkKey();
and check if things are working again.
Maybe you can also check the timer procedures with some small menu.
If this is working, that it is probably a memory issue.
Which Arduino do you use?

Oliver
659  Using Arduino / Programming Questions / Re: Menu for Display on: January 24, 2013, 01:59:14 am
After a quick review of your code i do not yet see a big mistake.

Is the Menu working without EEPROM?
Maybe there is a RAM overflow (too much of RAM consumption).

Oliver
660  Using Arduino / Programming Questions / Re: Menu for Display on: January 23, 2013, 05:34:43 pm
Hi

Timer()
The menu procedures will only provide a small delay. So your Timer() procedure should be called as usual in the loop().

EEPROM and m2tklib.
I do not see the full code, so it is difficult to say why the menu is not working.

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