Nice!View OLED Panel just showing noise

So I worked through a Firmware flashing issue. Essentially, I think my PC blocked the flashing and I was able to flash from another device. However, now I’m getting just noise with both OLEDs. I checked the solder, desoldered and resoldered. Did so at 270C. The board did take a beating doing so. Is it possible that the OLED board is the culprit and I just need replacements? I ordered a couple more OLED panels just in case, but wanted to reach out to see if there is anything else I’m missing.
No description
8 Replies
TyperAI
TyperAI2mo ago
It's possible the nice!view is the culprit, but let's try a few things first. Ensure the nice!views are fully inserted into their sockets. If you have no-solder headers, make sure they're pushed all the way in. Also, double-check that the nice!nano is fully seated in its sockets. Sometimes a slightly loose connection can cause issues. If you're still getting noise after that, it's possible the OLEDs are damaged. You can try the new ones when they arrive. If you still have issues, reply to this message or tag me for further help!
TheDanMonster
TheDanMonsterOP4w ago
Another note: the keyboard pairs and works just fine otherwise I got the new screens and installed them and it's the same exact issue 😦 @TyperAI
TyperAI
TyperAI4w ago
Since the keyboard is pairing and functioning otherwise, but you're still experiencing noise with the OLEDs, it suggests that the issue may be related to the connection or configuration rather than the OLEDs themselves. Here are a few steps to troubleshoot further: 1. Check Connections: Ensure that the nice!view sockets are properly soldered and that there are no cold solder joints. Sometimes, even if they look good, they may not be making proper contact. 2. Firmware Configuration: Make sure that the firmware you flashed supports the nice!view. If you flashed a firmware that doesn't include support for the OLEDs, they won't function correctly. You can refer to the firmware section in the documentation to ensure you're using the correct files. 3. Inspect for Shorts: Check for any solder bridges or shorts around the nice!view and nice!nano connections. A multimeter in continuity mode can help identify any unintended connections. 4. Reset the Firmware: If you haven't already, try re-flashing the firmware to ensure that everything is set up correctly. If you've gone through these steps and the issue persists, please let me know, and we can explore further options!
TheDanMonster
TheDanMonsterOP4w ago
just did 1 and 3 right now, no indication of a short. I guess I need to buy new pcb boards. rats Not sure what else to do @TyperAI
TyperAI
TyperAI4w ago
It's frustrating when troubleshooting leads to a dead end. Before considering new PCBs, let's try a couple more things. 1. Try a different firmware: Flash the keyboard with a different firmware, even if it's just a default one. This can help rule out any software issues. You can find the default firmware files in the firmware section of the build guide. 2. Check the nice!nano: It's rare, but sometimes the nice!nano itself can have issues. If you have a spare, try swapping it out to see if that resolves the problem. If these steps don't work, it's possible there's an issue with the PCB. If you'd like to explore that further, please reply to this message or tag me for further help!
TheDanMonster
TheDanMonsterOP4w ago
I'll grab new PCBs and headers.
TyperAI
TyperAI4w ago
That sounds like a good plan! Replacing the PCBs and headers should help resolve the issue if everything else checks out. If you have any questions during the installation or need further assistance, feel free to reach out. Good luck with the new parts!
PurpleTaro
PurpleTaro4w ago
@TheDanMonster heeeey.. crazy thought - do you have any jump cables? Keyword is crazy.. buuuut you could possibly pull the nice nano out, then cable the nano to the niceview directly with nothing else in between. If you want me to try here, i can give it a shot since my stuff is half disassembled and show you what that would look like, i recently added a PR into the docs so i even know which pins are the right pins 😄

Did you find this page helpful?