If we had single commands to do these, that would be nice!
left align
right align
center
justify
one space between each character
--------------------------------------
If we had single commands to do these, that would be nice!
left align
right align
center
justify
one space between each character
--------------------------------------
"If the Earth were a single state, Istanbul would be its capital." Napoleon Bonaparte
If those functions could be added without making the basic LCDOUT command use more code space it would be cool.
Just out of curiousity I had tried writing my own LCD control code (4bit, 8bit, & serial) - it was much easier than expected! And you can add in extra functions as needed.
Arch
Usually i use an external EEPROM to save the strings. As i use always the same routine to display strings, i format my strings to fit directly on the LCD, then, if i have to display results right, left or somewhere esle on the string i use specific structure to store LCD address in the EEPROM or in the program to point directly on the wanted LCD location.
Using a HEX editor make things easy to figure out how your data will be display on your LCD.
It's flexible even if it use a bit much EEPROM storage.
OR, Using another EEPROM structure, you can specify the origine point, the string lenght and do what you need with.
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
I see mister_e but it takes extra work, doesn’t it?
Who are the people that will really read "PBP Wish List" and then consider some of the posts for the next version?
In other words, is there really a consideration of the posts here?
If so, if they like an idea here at "PBP Wish List", will they really consider putting them into the next version and, may be, will name it with the member’s who posted it?
Code:sayzer $fe,$cx,”Hello Word” 'right align “Hello Word” on lcd mister_e 0, eeprom 'format the entire eeprom 'and assign 0 to each location.
Trademarks: name of “mister_e” belongs to mister_e
--------------
"If the Earth were a single state, Istanbul would be its capital." Napoleon Bonaparte
I don't want to start yet another "heated debate", but
I feel LCDOUT "as it is" gives you all you need to get started quickly on a standard character display.
With a bit of creativity you can achieve almost anything on a standard LCD.
(even simple graphics)
If you want more, go be creative and write your own routines that do exactly what you want (or need) and nothing else.
You will learn a lot and in addition you will (most likely) save some codespace.
Of Course LCDOUT could have more bells and whistles, but then it would require even more code space than it already does to simply display "Hello World"
(would it be a real benefit if it would require at least an 18F PIC to simply display two lines of text on any LCD?)
I started with HD44780 (or compatible) LCDs and was happy to have the (in my oppinion) powerful LCDOUT.
Today I use all kinds of displays with different controllers and I prefer Displays with SPI or I2C to save some port pins.
With those "non HD44780" Controllers LCDOUT is of no use at all,
one has just to be creative.
It is even more complex with GLCDs, which Controller should be supported?
There is actually no standard.
What I really like with PBP is: it is bullet proof.
Several other compilers have all kinds of "special features" but actually lack of basic functionality and reliability.
(One never knows where to start searching for the cause of an unexpected result)
I have never found a real bug in PBP
ok, sometimes code didn't work as expected,
but looking closer to it I had to realise:
it simply worked as designed!
PBP follows one simple rule:
GARBAGE IN - GARBAGE OUT
(I have seen other Products where you get GARBAGE OUT whatever you put in)
If one takes the time to study the excellent PBP Manual
and the datasheets of all hardware involved in the specific design
and follows some design rules
it will work reliably not only on the bench but also in the field.
regards
Ralph
_______________________________________________
There are only 10 types of people:
Those who understand binary, and those who don't ...
_______________________________________________
It would be awesome if PBP had a 2 wire LCD suppurt.
Maybe something like LCDOUT2 or something . . .
To clarify what i mean, i have attached a schematic and the ASM source code from Myke's page.
<< http://www.myke.com/lcd.htm >>> This is given at the end of the page.
Is it possible to incorporate this in PBP ???
He uses a shift register to send data and a resistor-diode AND logic to strobe the enable bit of the LCD . . .
How can i do this in PBP ? ? ?
Last edited by shahidali55; - 22nd April 2007 at 09:50.
I know this an old post, but could you elaborate a little more on how one would store strings in an external EEPROM and retrieve them. I can see where this might come in handy when building menus. "HSEROUT" is a little hungry for code space. I did a search on the forum, but nothing jumped out.
Thanks, David
Use a HEX editor, create your Menus (i used HEXWorkshop from bpsoft), then dump it in your EEPROM with a EEPROM programmer or else fancy method, like a custom PC application which will send the EEPROM dump to your PIC via Rs232 or USB.
An then, depending your EEPROM you really just need I2CREAD/SHIFTIN then a LCDOUT.
That's one method, you can also use the following method using the code space.
http://www.pbpgroup.com/modules/wfse...p?articleid=10
And there's a load of different version of it in this forum to.
HTH
Steve
It's not a bug, it's a random feature.
There's no problem, only learning opportunities.
Steve
Yes I use the embedded strings as part of my Logo Display. Works great BTW.
I also tried the custom approach and built a HyperTerm interface to an 24LC128 EEPROM, but the problem is viewing all the lines at once or editing a single entry. I will look at your Hex Workshop.
Thanks for the info
David
Bookmarks