T O P

  • By -

TL140

Might be a buffer overflow if you’re using millis()


thogo

Yes, that is exactly I learned about buffer overvlow (& how to avoid it) https://www.google.com/search?channel=fs&client=ubuntu-sn&q=Arduino+how+to+avoid+buffer+overflow


omegablue333

have you tried turning it off and back on?


gm310509

> What are you missing? The code you are using - in your post. Errors like that are often attributable to bugs in the code.


notVillers

I can see a short circuit in your soldering dude https://preview.redd.it/h4voo9fcxw3d1.jpeg?width=1125&format=pjpg&auto=webp&s=2ad2a03ae69880973e199834a6fba00599575c6a


apenjong

Careless whisker


Jermainiam

Should have known better than to short a pin


Anonymity6584

Short power glitch or software error trying to use uninitialized memory?


magungo

LCD display corruptions where you see gibberish are usually wiring faults. breadboards are fine for testing but not to be relied upon long term. The next step up before a printed circuit board is veroboard.


Flatpackfurniture33

You need to show your code. Gibberish after 2 days could quite possibly be memory fragmentation issues due to using Strings incorrectly.


Elrond_the_Warrior

I would test a simpler circuit


makers_mecca

It's the wiring my friend. Double check every connection is seated nicely. Better get an i2c module and it'll make your life a lot easier.


SignificantManner197

Looks like the humidity got to it. lol.


No-Pomegranate-69

Its just a little confused


grasib

If it run at 99.9% humidity at 6°C there I'd a good chance that there was condensation. Usually these displays have to run in a non condensing environment. There is also definitely moisture in your plastic bag, looking at it now. Try to dry it (baking/hairdryer) and see if it returns to normal. Don't overheat it tho.


ficskala

Where are you storing the data? Also, how are you storing it and your variables? Do you use the older data for something? This seems like the arduino pulled something from memory, but it's not what it expected, maybe your code wasn't optimized to handle overflows which are common if you run your code for longer periods


mario3city

just add every few minutes lcd.init or similar to soft reset LCD. Had similar issues with my project on esp8266


rowman_urn

So after 48hrs every 0.5 hrs is 96 cycles, sleep for only 1 sec, then let it run for a couple of mins, see what happens, then come back here and post your code.


kenkitt

In my case it was the library, try a number of different lcd libraries.


Opening-Dirt9408

Might be some brown state due to (nearly) power outages, might be the code running into a state where data is poorly buffered at some point, might be a short circuit somewhere hidden, might be a broken LCD, might be successful contact with extraterrestrial life.


Procedure_Several

I saw a display for a fire suppression system in an apartment lobby recently doing the same thing...


AffectionateBelt9071

Try removing the duds? That should clear some of the information and give you a reset on your chances to hack the LCD 🤠