Generally, an issue is either "solved" (meaning you don't need any help and the only reason to read any further is if you want to know how it was solved) or it is not, in which case you need help. The two quotes above appear to be contradictory. Is the issue "solved" (you don't need any help) or not ? This is the first post on this topic and there are no replies yet so if you need help you might want to rephrase the first quote using the "Modify" button so people will know you still need help.
Robert
This is correct.
So what is your point ? If you are posting to help others you need to state this because posting the solution before the problem just confuses the issue.
If your post looked like this:
[quote]The LCD works fine on other code.
Why does this happen, and how can I fix it?[/quote]
[quote]SOLVED
The arrays were too big.[/quote]
INSTEAD OF THE OTHER WAY AROUND, it would still be incomplete because the array size has not been reduced in the code
you provided. If you are posting to help others then you need to post the problem first and then the solution, such as my
example above. In addition you need to post the corrected code (as I have done with the attached file) , and explain that if
you change the array size to 192 instead of 256 the glitch disappears. Also, you might propose a reason for the glitch, such
as, the string array code is using too much of the ram required to run lcd code. Whether or not this is the correct conclusion,
I couldn't tell you. I simply reduced the array size based on the "array too big" comment and found that I could display a
message on a 16x2 lcd on both lines without any glitches.
You can test the attached program by substituting the correct lcd descriptor as I have done.
[code]// LiquidCrystal lcd(12, 11, 5, 4, 3, 2); // Original Descriptor
LiquidCrystal lcd( 8, 9, 4, 5, 6, 7 ); //Pins for the freetronics 16x2 LCD shield. LCD: ( RS, E, LCD-D4, LCD-D5, LCD-D6, LCD-D7 )
// Descriptor I substituted to run the code on my keypad shield (a Linksprite "Button Shield")
// to run on your keypad shield plug in the correct pin numbers LCD: ( RS, E, LCD-D4, LCD-D5, LCD-D6, LCD-D7 )
You also have a possible space-leak via the String class - going round a loop
allocating a String that you don't use isn't particularly useful either!
This is a bit beyond my programming expertise. Can you explain what a "space-leak" is "
Is that like a rip in the space-time continuum ?
Just kidding. ..
Seriously, could you please elaborate a little on that ?