PCB Design Review: DPI-LVDS Sony Vaio LCD Devboard

Ordering a PCB with mistakes sucks. We should help each other avoid such mistakes – especially newcomers. One of the best ways to avoid these mistakes, especially if it’s your first one, is to get a few other people to look at it. You deserve to get a PCB that is as functional and as helpful as humanly possible, so that you can be happy with your project, and feel ever so slightly more confident in yourself in whatever you shall set out to do next.

At the end of last year, I put out a call for design review submissions, and we’ve received enough projects to make me feel overwhelmed for a bit. A design review has always felt like a personal thing, and here we are doing them in public. But in that sense, we hope that everyone can learn from them, and we hope to push forward a healthy review culture.

What’s more, these articles won’t just be design review. Every project I’m highlighting is worthy of a Hackaday feature just on its own, so tune in and learn more about them!

Today’s Contestant

For this example, I will be walking through a review I’ve already given someone with a pretty cool board, for a pretty cool project I’ve already shown you. Remember the Sony Vaio remake project? A fair bit of people have reached out to me afterwards, and one of them, [Exentio] also had the same Sony Vaio rebuild idea in mind. We started chatting, and he decided to tackle one of the project’s milestones, and perhaps the most crucial one – adapting the LCD.

Continue reading “PCB Design Review: DPI-LVDS Sony Vaio LCD Devboard”

Check Your Board: Call For Submissions

As both beginning hackers and Silicon Valley investors alike keep discovering, there are a lot of differences between hardware and software. One important difference is cost of iterating over a design. In software, you can comfortably rerun your build process and push updates out near instantly to tons of users. In hardware, all of that costs money, and I do mean, it costs way more money than you’d want to spend.

When I see people order boards that could never work because of some fundamental design assertions, with mistakes entirely preventable, it hurts. Not in an “embarrassment” way – it’s knowing that, if they asked someone to take a look at the design, they could’ve received crucial feedback, pulled the traces on the board differently or added some components, and avoided spending a significant chunk of money and time expecting and assembling a board that has a fundamental mishap.

Every thing like this might set a beginner back on their hacker journeys, or just have them spend some of their valuable time, and we can do a ton to prevent that by simply having someone experienced take a look.

Continue reading “Check Your Board: Call For Submissions”