How to write/read strings EEPROM/LCD


Closed Thread
Results 1 to 23 of 23

Hybrid View

  1. #1
    Join Date
    Dec 2005
    Posts
    46


    Did you find this post helpful? Yes | No

    Default

    Joe,
    I got "rid" of all of the LCD out commands with a sub and sure thought that would do the trick, but my program only went from 3934 to 3931. Here's what I did:


    IF Refresh > 8 Then Refresh = 1
    ref:
    Select Case Refresh
    GoSub lcdone ' Position cursor at home
    T[0]="R":T[1]="e":T[2]="f":T[3]="r":T[4]="e":T[5]="s":T[6]="h":T[7]=" "
    GoSub LCDout1
    GoSub lcdsec
    Case 1
    T[0]="N":T[1]="o":T[2]="n":T[3]="e":T[4]=" ":T[5]=" ":T[6]=" ":T[7]=" "
    GoSub LCDout1
    RefTime = 0
    Case 2
    T[0]="3":T[1]="0":T[2]=" ":T[3]="S":T[4]="e":T[5]="c":T[6]=" ":T[7]=" "
    GoSub LCDout1
    RefTime = 30

    etc........

    LCDout1:
    LCDOut STR T
    Return


    What did you mean by "Also see select case instructions in the manual."...am I missing something there?

    Arch,
    I fixed the "IF Refresh > 8 " problem. Thanks for that. I've looked at the LOOKUP command, but really don't don't understand it. I guess if I set up the alphabet as constants, that won't use any space, but once I use lookup to read them into an array, woukldn't that take up the same space as above?

    mister_e,
    This board design has been done for a while, so I can't use external on this one, but if I do it on another design, when I retrieve the strings to go into the LCDOUT command, won't that put me in the same boat? As you can see, I'm quite a rookie at this. :-) I don't think I can do the embedded strings either since this chip won't let me use program space. "Flash Program Write" is disabled when I select that chip in the EPIC Programmer.
    Gary

  2. #2
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default

    Ah crap! So the RTFM of the day goes to me

    Using an external EEPROM solve the problem, the only thing you have to keep in your PIC is the EEPROM start address of your string. From there, you just call and display routine.

    Anyways, i'm pretty sure there's something to do around this without changing your actual stuff... let me sleep on this. If you want, you can post your whole code here or, if you can't for some privacy and/or commercial reason, send it on my e-mail.
    Last edited by mister_e; - 29th January 2007 at 05:40.
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

  3. #3
    Join Date
    Aug 2006
    Location
    Look, behind you.
    Posts
    2,818


    Did you find this post helpful? Yes | No

    Red face To quote Homer S

    Quote Originally Posted by g-hoot View Post
    Joe,



    What did you mean by "Also see select case instructions in the manual."...am I missing something there?
    Dohe!
    Well it's like this, these coke bottle thick glasses . . . I didn't see you had used select case already, Just ignorant of me, sorry.
    JS
    EDIT: You might check with Darrel, I think he has something that measures the code size for each bit of code, but understand this, my memory isn't worth much.
    Last edited by Archangel; - 29th January 2007 at 06:33. Reason: add
    If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
    .
    Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
    .
    There simply is no "Happy Spam" If you do it you will disappear from this forum.

  4. #4
    Join Date
    Dec 2005
    Posts
    46


    Did you find this post helpful? Yes | No

    Default

    "the only thing you have to keep in your PIC is the EEPROM start address of your string"

    Ahh, I think it's starting to sink in to my thick melon. What I was trying to do was set up the alphabet in upper and lower case, and numbers and a few other characters in eeprom, and then call each one individually. I noticed in many places that people were looping through like this:
    for i = 0 to 7
    read i, LCDtext(i)
    next i

    but that wouldn't work with the alphabet deal since I had to jump around to different, non-sequential eeprom locations.
    So, what you are saying is that I would save each actual string in eeprom and then just give the loop the starting location of the string. I'm only using about 16 locations of eeprom right now, and this chip has 256, so that leaves me enough room for about thirty 8 character strings, so that should help a bunch. I'll give that a shot tonight.
    Thanks all,
    Gary

  5. #5
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default

    can you post your text string here?

    maybe there's some word you can use from one and merge into another... but will this worth?
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

  6. #6
    Join Date
    Dec 2005
    Posts
    46


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by mister_e View Post
    can you post your text string here?

    maybe there's some word you can use from one and merge into another... but will this worth?

    Hey Steve,
    I think you have got me thinking enough that I can get enough space free to add what I need. The code is pretty long so I just emailed you the code also, just to take a quick look at it if you want. Please don't spend too much time on it. Thank you very much for taking the valuable time to look at it.
    Gary

  7. #7
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default

    Quote Originally Posted by Joe S. View Post
    You might check with Darrel, I think he has something that measures the code size for each bit of code, but understand this, my memory isn't worth much.
    I think you talk about...

    How much code would a code hog hog
    http://www.picbasic.co.uk/forum/showthread.php?t=2418
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

  8. #8
    Join Date
    Aug 2006
    Location
    Look, behind you.
    Posts
    2,818


    Did you find this post helpful? Yes | No

    Default Right-O

    Quote Originally Posted by mister_e View Post
    I think you talk about...

    How much code would a code hog hog
    http://www.picbasic.co.uk/forum/showthread.php?t=2418
    Yes Sir, Mister_e !
    That was what I saw!
    If you do not believe in MAGIC, Consider how currency has value simply by printing it, and is then traded for real assets.
    .
    Gold is the money of kings, silver is the money of gentlemen, barter is the money of peasants - but debt is the money of slaves
    .
    There simply is no "Happy Spam" If you do it you will disappear from this forum.

  9. #9
    Join Date
    Dec 2005
    Posts
    46


    Did you find this post helpful? Yes | No

    Default

    Man, this thing is a pain in the booty. Using eeprom works great until i get more that about 30 characters saven in it. Then my LCD just displays black rectangles/blanks. If I delete all of the charcters from eeprom and just leave about 50, it works fine? I dunno, maybe the pic nees a pause somewhere at startup to read the eeprom? Here's the sub:

    EEtext:
    LCDtextNm = 0
    For EEnum = EEnum TO EEnum+7
    Read EEnum, LCDtext[LCDtextNm]
    LCDtextNm=LCDtextNm+1
    Next EEnum
    LCDOut STR LCDtext
    Return

  10. #10
    Join Date
    Sep 2004
    Location
    montreal, canada
    Posts
    6,898


    Did you find this post helpful? Yes | No

    Default

    this one is dangerous and you trick the compiler
    Code:
    For EEnum = EEnum TO EEnum+7
    doing that you'll jump in an endless loop. i don't know what's around your sub but i think this one make much sense

    Code:
    EEtext:
        For CharAddress = EEnum TO EEnum+7
             Read CharAddress, Char
             LCDOUT Char
             Next 
        
        Return
    Steve

    It's not a bug, it's a random feature.
    There's no problem, only learning opportunities.

  11. #11
    Join Date
    Dec 2005
    Posts
    46


    Did you find this post helpful? Yes | No

    Default

    This is getting plain silly. If I have this:
    EEPROM 30,["R","e","a","d","y"," "," "," "]
    EEPROM 38,["D","e","l","a","y"," "," "," "]
    EEPROM 46,["1","5"," ","S","e","c"," "," "]
    EEPROM 54,["2","0"," ","S","e","c"," "," "]

    The run through the sub:

    EEtext:
    LCDtextNm = 0
    EnumC = EEnum
    For EEnum = EnumC TO EnumC+7
    Read EEnum, LCDtext[LCDtextNm]
    LCDtextNm=LCDtextNm+1
    Next
    LCDOut STR LCDtext
    Return

    Ready will display, but the other 3 strings produce a blank screen. If I replace the "e" in ready with a space " " then it works fine, except for the fact that it now says "R ady". ;-) I have had lots of strange happenings with the LCD, like for instance, I can't display a number ending in "0". Also can't display the name "MCKELLOP". Who knows?....
    Gary

Similar Threads

  1. Parsing Strings...
    By TerdRatchett in forum mel PIC BASIC Pro
    Replies: 23
    Last Post: - 15th February 2009, 05:13
  2. Please help with storing strings in codespace
    By g-hoot in forum mel PIC BASIC Pro
    Replies: 3
    Last Post: - 16th May 2008, 02:02
  3. Processing lengthy strings
    By sougata in forum mel PIC BASIC Pro
    Replies: 1
    Last Post: - 21st March 2006, 06:27
  4. I2CWRITE writing Strings to EEPROM
    By NavMicroSystems in forum mel PIC BASIC Pro
    Replies: 9
    Last Post: - 27th March 2005, 20:45
  5. reading 2c strings
    By beto in forum mel PIC BASIC Pro
    Replies: 12
    Last Post: - 22nd December 2004, 16:26

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts