 Notice. New forum software under development. It's going to miss a few functions and look a bit ugly for a while, but I'm working on it full time now as the old forum was too unstable. Couple days, all good. If you notice any issues, please contact me. |
Forum Index : Microcontroller and PC projects : LCD Screen Corruption
  Page 2 of 2 |
|||||
| Author | Message | ||||
| Phil23 Guru  Joined: 27/03/2016 Location: AustraliaPosts: 1667 |
One worries, Doing it in a rush, work stuff to do, but will read some data sheets properly later or maybe try adding a routine LCD Close followed by LCD Init again as some Duct Tape.... |
||||
| ajkw Senior Member  Joined: 29/06/2011 Location: AustraliaPosts: 290 |
Phil, I recall... when I was having similar garbage issues I did have a option to re initialise the display using LCD CLose, LCD init* before each update to the data on the screen. I think it caused a little flicker on the screen but that was better than garbage. I later had a menu option to turn the 'noise filter' on or off as required. Solving the noise issue with a cap as previously mentioned was the proper fix. Anthony. * 'initlcd' I have for whatever MM version I was up to. |
||||
| Phil23 Guru Joined: 27/03/2016 Location: AustraliaPosts: 1667 |
I did catch a bit of corruption yesterday, so though I'd stop the code for some quick checks. Typed LCD CLOSE at the prompt & it returned Error: Not open. So initialised it at the prompt, did a hello world & ran it again. So can add that to the mix, that for some reason once it's become corrupted MMbasic thinks it's closed. Repeated the same thing when corruption is not present & Close just returns me to the prompt as expected. |
||||
Azure Guru Joined: 09/11/2017 Location: AustraliaPosts: 446 |
Sorry to say but I suspect there is more going on than the corruption on the display, that is just the most obvious thing. You need to check the voltages and signals on the board while it it running and doing different things: Transmitting, updating display, idle, etc Hopefully that will confirm if there is a power or signal noise/corruption (or not) due to hardware and you can go from there. It may be a very simple fix once the cause is found. Until then if you change the code, you are going to end up putting band-aids on band-aids without really knowing the problem and things will just get more complicated and obscured. If you don't have time at the moment, then I would leave it for now and put up with the corrupted display until you do have time to look at it properly. |
||||
Quazee137 Guru Joined: 07/08/2016 Location: United StatesPosts: 600 |
looks like it might be a dip in the current. even with caps not having enough will pull all voltages down maybe enough to even affect the mite and lcd. Also look out for the LDO regs if you have a high input voltage you are limited to how much current you can draw before it thermally shuts down and back on. I ran in to that problem using 12v wall warts. Every thing worked fine till I pulled 600mA them it toggled off/on. After going to a 6V every thing works great. |
||||
| Quazee137 Guru Joined: 07/08/2016 Location: United StatesPosts: 600 |
After looking at your board I though this might be something to check. Esp power Are you putting it into sleep mode and having something wake it up? At wake up it could be pulling the supply down enough to glitch things. And for the LCD bits 1-2-4 LCD's HD44780 instruction set |
||||
| Phil23 Guru Joined: 27/03/2016 Location: AustraliaPosts: 1667 |
The ESP is connected to the console, so not sure if it is still transmitting VT-100 screen updates regardless of whether client PC's are connected or not. interesting thought though, & it gives me a vague feeling that when the entire system is less active, there's less awareness of the dud screens. But on the other hand, I'm also less likely to have a PC connected to the console monitoring it's output. Phil. |
||||
| Page 2 of 2 |
|||||
 Print this page |
 |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |
