Discussion forum for the BasicX family of microcontroller chips.
|
That's right, when I apply power to my LCD+, the startup screen says: "00 Baud" I've tried communicating with it at all the standard speeds from 2400-115200 bps (with a VB program). At 115200, I see garbage chars on the screen, but the communication doesn't work. How can I reset this LCD+? I've been using several LCD+ units for a while and only ran into trouble when I tried to BOTH define custom characters AND define keypad key tags. These two operations appear to partially overwrite one another. To make sure it wasn't a problem with my code, I tried these operations using the NetMedia LCD+ demo program on Win98, with the LCD+ connected directly to the PC serial port. Same problem. After playing around with the order of defining key tags and custom chars, the unit got into this non-communicative state. NetMedia, please help me get this unit functional again! Thanks, - Phil Aspenwall |
|
|
|
Phil, You must have purchased your LCD+ awhile ago. The first production release had a bug that allowed users to store non-supported baud rate values to its EEPROM. With a non-supported baud rate value in its EEPROM the LCD+ would "boot-up" and default to 00 baud. When this happens the LCD+ baud rate could be anywhere from 300 to 115,200Kbps. The newer LCD+ firmware defaults to 9600 baud if a non-supported baud rate value is found. You should send it back for reprogramming. Regards, Chris ---------- From: Phil Aspenwall [SMTP:] Sent: Sunday, August 20, 2000 11:41 PM To: Subject: [BasicX] NetMedia Please Help: LCD+ says "00 Baud" That's right, when I apply power to my LCD+, the startup screen says: "00 Baud" I've tried communicating with it at all the standard speeds from 2400-115200 bps (with a VB program). At 115200, I see garbage chars on the screen, but the communication doesn't work. How can I reset this LCD+? I've been using several LCD+ units for a while and only ran into trouble when I tried to BOTH define custom characters AND define keypad key tags. These two operations appear to partially overwrite one another. To make sure it wasn't a problem with my code, I tried these operations using the NetMedia LCD+ demo program on Win98, with the LCD+ connected directly to the PC serial port. Same problem. After playing around with the order of defining key tags and custom chars, the unit got into this non-communicative state. NetMedia, please help me get this unit functional again! Thanks, - Phil Aspenwall |
|
I bought mine when they first came out , luckily I havent run into that problem. Is
there any way to tell if it has that problrm without locking up the display? >>> Chris Harriman <> 08/21/00 10:48AM >>> Phil, You must have purchased your LCD+ awhile ago. The first production release had a bug that allowed users to store non-supported baud rate values to its EEPROM. With a non-supported baud rate value in its EEPROM the LCD+ would "boot-up" and default to 00 baud. When this happens the LCD+ baud rate could be anywhere from 300 to 115,200Kbps. The newer LCD+ firmware defaults to 9600 baud if a non-supported baud rate value is found. You should send it back for reprogramming. Regards, Chris ---------- From: Phil Aspenwall [SMTP:] Sent: Sunday, August 20, 2000 11:41 PM To: Subject: [BasicX] NetMedia Please Help: LCD+ says "00 Baud" That's right, when I apply power to my LCD+, the startup screen says: "00 Baud" I've tried communicating with it at all the standard speeds from 2400-115200 bps (with a VB program). At 115200, I see garbage chars on the screen, but the communication doesn't work. How can I reset this LCD+? I've been using several LCD+ units for a while and only ran into trouble when I tried to BOTH define custom characters AND define keypad key tags. These two operations appear to partially overwrite one another. To make sure it wasn't a problem with my code, I tried these operations using the NetMedia LCD+ demo program on Win98, with the LCD+ connected directly to the PC serial port. Same problem. After playing around with the order of defining key tags and custom chars, the unit got into this non-communicative state. NetMedia, please help me get this unit functional again! Thanks, - Phil Aspenwall |