Accelerometer | ADC | ADXL | Adxl20 | AVR | BasicStamp | BX-35 | BX28 | BX35 | COM3 | Compiler | Downloader | EEPROM | Electromagnet | GetADC | GP2D1 | GPS | I2C | IDE | Keypad | LCD | LCD+ | MIDI | Motors | Multitasking | Netmedia | Networking | PCB | PID | PlaySound | PWM | Relays | RTC | Servo | ShiftOut | SitePlayer | SPI | Stack | Timer | USB

In my experience, its almost certianly the long ribbon cable. I use a short ( 1 foot) screened circular cable and get very reliable results. I also refresh the keypad tags ( using ctrl-T) often, as I have found that in a noisy environment, the keypad tags can sometimes get corrupted, with puzzling results .. neil greatwitenorth wrote: > I have been having a little bit of trouble with the LCD+ using the > keypad. It is a similar problem to another post but the reply offered > > little help. The problem is that when I press a number other numbers > in its column will also show up. For ex. when I press 2 the screen > may show 20. I am using a rather long (2 feet) ribbon cable but have > made sure to ground the keypad to the lcd+ and BX-24. I don't think > its the cable though because I have connected the pins of the keypad > directly to the keypad pins of the LCD+ and still the same problem. > Here is my code that I used. > > dim com3_out(1 to 40) as byte > dim com3_in(1 to 40) as byte > > sub main() > Call openqueue(com3_out, 40) > call openqueue(com3_in, 30) > call definecom3(12, 16, bx1000_1000) > call opencom(3,9600, com3_in, com3_out) > call delay(0.5) > > call putqueuestr(com3_out, chr(15)) > call delay (0.01) > call putqueuestr(com3_out, chr(25)) > call delay (0.01) > call putqueuestr(com3_out, chr(12)) > call delay (0.01) > call putqueuestr(com3_out, chr(24) & chr(bx0001_0101)) > > end sub > Yahoo! Groups Sponsor ADVERTISEMENT > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. [Non-text portions of this message have been removed]

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

Hi greatwhitenorth ( name would help) What exactly are the symptoms you ar having? Try including this line in your code: call putqueuestr(ocom3,chr(20)&chr(49)&chr(50)&chr(51)&chr(48)&chr(52) _ &chr(53)&chr(54)&chr(48)&chr(55)&chr(56)&chr(57)&chr(48) _ &chr(73)&chr(48)&chr(72)&chr(48)) sleep(50) What this does is refresh the keycodes, in case they get corrupted, which I have had happen. neil greatwitenorth wrote: > I am now using a 2 inch cable and I have grounded the keypad. I > still > have the exact same problem. The cable isn't shielded but I wouldn't > think it would have to be if its only 2 inches long. What else could > be wrong? > > --- In basicx@y..., Neil Jepsen <jepsen@x> wrote: > > In my experience, its almost certianly the long ribbon cable. I use > a > > short ( 1 foot) screened circular cable and get very reliable > results. > > I also refresh the keypad tags ( using ctrl-T) often, as I have > found > > that in a noisy environment, the keypad tags can sometimes get > > corrupted, with puzzling results .. > > neil > > > Yahoo! Groups Sponsor ADVERTISEMENT > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. [Non-text portions of this message have been removed]

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

PS you may be using a different label from ocom3 greatwitenorth wrote: > I am now using a 2 inch cable and I have grounded the keypad. I > still > have the exact same problem. The cable isn't shielded but I wouldn't > think it would have to be if its only 2 inches long. What else could > be wrong? > > --- In basicx@y..., Neil Jepsen <jepsen@x> wrote: > > In my experience, its almost certianly the long ribbon cable. I use > a > > short ( 1 foot) screened circular cable and get very reliable > results. > > I also refresh the keypad tags ( using ctrl-T) often, as I have > found > > that in a noisy environment, the keypad tags can sometimes get > > corrupted, with puzzling results .. > > neil > > > Yahoo! Groups Sponsor ADVERTISEMENT > > Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. [Non-text portions of this message have been removed]

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I have been having a little bit of trouble with the LCD+ using the keypad. It is a similar problem to another post but the reply offered little help. The problem is that when I press a number other numbers in its column will also show up. For ex. when I press 2 the screen may show 20. I am using a rather long (2 feet) ribbon cable but have made sure to ground the keypad to the lcd+ and BX-24. I don't think its the cable though because I have connected the pins of the keypad directly to the keypad pins of the LCD+ and still the same problem. Here is my code that I used. dim com3_out(1 to 40) as byte dim com3_in(1 to 40) as byte sub main() Call openqueue(com3_out, 40) call openqueue(com3_in, 30) call definecom3(12, 16, bx1000_1000) call opencom(3,9600, com3_in, com3_out) call delay(0.5) call putqueuestr(com3_out, chr(15)) call delay (0.01) call putqueuestr(com3_out, chr(25)) call delay (0.01) call putqueuestr(com3_out, chr(12)) call delay (0.01) call putqueuestr(com3_out, chr(24) & chr(bx0001_0101)) end sub

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I am now using a 2 inch cable and I have grounded the keypad. I still have the exact same problem. The cable isn't shielded but I wouldn't think it would have to be if its only 2 inches long. What else could be wrong? --- In basicx@y..., Neil Jepsen <jepsen@x> wrote: > In my experience, its almost certianly the long ribbon cable. I use a > short ( 1 foot) screened circular cable and get very reliable results. > I also refresh the keypad tags ( using ctrl-T) often, as I have found > that in a noisy environment, the keypad tags can sometimes get > corrupted, with puzzling results .. > neil

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )

I also have the same problem occasionally... but always blamed it on contact bounce on the keypad. Although not really a feasible explanation, I have noticed that when pressing the keys gently and briefly, the problem seldom shows up. The keypad I use was supplied by RS (Electrovalue, outside Europe). Do we have the same keypad type in common, maybe? Edwin

(You need to be a member of basicx -- send a blank email to basicx-subscribe@yahoogroups.com )