Alright, I’ve hinted and even mentioned what all the components are in the scoreboard, but not really in much detail. To supplement my building blocks series of posts, I thought I would put together a simple diagram of how all the different building blocks are connected and with some basic stats for each.
As you can see, there is quite a bit of power distribution throughout the design. This was one of my main focus points because I wanted to make sure the power was distributed in a safe and maintainable manner. The last thing I want is an epic failure during the middle of a game (i.e. flames…).
Let’s see…I’ve done building blocks post on the digits and the SMPS. I think next I’ll discuss some of the code I used on the atMega328p and then perhaps a blog on the battery, battery safety, and power distribution.
Building Blocks: Explosions are BAD!
Who says you can’t live on the edge as a geek? This next building block is really in there for safety more than anything else. What am I talking about? LiPo batteries.
LiPo batteries have an excellent stored power to weight ratio, however, they are contentious beasts. You can’t overcharge them, or they’ll explode. You can’t drain them past a certain point or they’ll become damaged and will burst into flames the next time you charge them. Check this out:
One of the most common things I’ve seen in my research about LiPo batteries is that people tend to forget to disconnect the batteries after use and the battery silently reaches the critical discharged state over time while no one is looking. It’s safer to just toss the pack than try to revive it, although there are many accounts of folks doing just that.
Well, I plan on having an on/off switch on the scoreboard, so I don’t expect to run into any issues of discharge over time when I’m not using the battery, however, I do want to have some sort of protection from excessive discharge while I am using the scoreboard. I’d rather not have my scoreboard burst into flames when it runs out of battery. What I’d much rather do is warn me of a low battery, and then have it simply turn itself off if the voltage gets critically low.
Luckily, there are a number of IC companies that make chips that do just what I want. I decided to go with an ICL7665 from Maxim because their datasheet was very detailed and included quite a bit of information relevant to my particular application.
The design concept is simple. The chip, which runs off the full 12V, has a couple comparators internally. These comparators monitor the voltage on their inputs and toggle an output when the voltage is less than the reference. The first comparator will be used for the Low Battery Indication LED. The second, with a bit of hysteresis built in, will drive a MOSFET on the 12V input. When turned on, the MOSFET will allow 12V to enter the scoreboard from the battery. When the voltage reaches a critical level, the ICL7665 will turn off the MOSFET and the scoreboard will go dark.
I’ve put the design into a schematic and laid out a SMD version of the board. I’ve not tested this, but I’m expecting to have this built in the next few days. I will report on my success or failure. Here are some pictures of the design:
[Note: I’ve removed the schematics and board layout because there was an error in how I had the MOSFET connected. I don’t want to post things that don’t work, so hopefully I’ll build this thing, test it, and then be able to repost the design. Sorry folks.]
An interesting concept that I thought of and that I will be testing on a prototype board is whether I can have the ICL7665 be powered AFTER the MOSFET. Why would this be a good idea? Well, the IC still takes power, even when it’s cut the power. If you put the IC after the MOSFET, then it will be powered down when the power is cut. The problem there is how do you power things up initially? Well, I was thinking a momentary switch across the Source/Drain of the MOSFET will allow me to temporarily bypass the MOSFET to allow 12V into the circuits to turn them on. Not sure if I explained this clearly, but if this works, it’ll be really cool and I’ll have to write about it in more detail.
Cheers!!
Building Blocks: Introduction
It’s pretty funny how my neighbors view my different projects. They’re always asking, “so…why don’t you just buy one of those on the internet?”, to which I reply, “none of those on the internet do exactly what I want them to do.”
This project is no different. I wanted an open scoreboard hardware platform that I can control from common wireless devices (mobile phones, netbooks, etc.) I also wanted a scoreboard that didn’t cost me $1000 and that I could actually repair myself. Well, I haven’t exceeded the $1000 mark, but it hasn’t been a cheap project either. Subsequent versions (i.e. those made by fans of the blog) should be significantly cheaper without all the trial and error (and error, and error, etc.)
When I began to plan this project, in earnest, I quickly decided that the best way to pull this off would be to cut the project down into building blocks. Mass produced products benefit from a single monolithic PCB that does everything. For me, that simply isn’t the case. This thing needs to be modular so that I can build the smaller building blocks, test them, and then move on to others. I’m going to detail each building block in a series of posts along with the files I used to create them.
The building blocks I am working on now are score digits, inning digits, balls/strikes/outs, microcontroller, and finally the wireless interface.
I don’t need no stinking drill press! That’s right. I drill my holes by hand. Yes, I even own a rather large drill press, but I find it easier to achieve the precision I’m looking for with a simple hand drill.
This is one of the 7 segment display boards for the scoreboard. I did the layout in Eagle and then used the toner transfer method to put it on some 4”x6” copper clad I bought on Ebay. I use a solution of diluted HCl and H2O2 as etchant. It works great and is a bit greener than the Ferric Chloride method. Do a search at Instructables. There’s a couple instructables on this method of etching.
Here’s a preview of where I am at right now with the scoreboard. Unfortunately I did not think of blogging my progress until now, so I’ve made some significant progress already. I will try to go back and document most things I have done so far. Stay tuned for that.
Let’s Get Started, Shall We?
A few years ago, I realized that there were many things I’ve always wanted to do and learn, but never took the time. Some of these things come from as far back as when I was a kid, but I never had the time or the opportunity to pursue them.
So…I took up Snowboarding. Now, a 38 year old on a snowboard for the first time is a comical thing to see. After a few years and a couple mishaps where I smashed my knee real good and almost knocked myself out even though I was wearing a helmet (thankfully), I decided that I scratched that itch enough and should move on.
So…I decided to build a robot. Oh yeah, it was going to do everything and I knew exactly what I wanted to do. I realized that I knew bupkis about anything to do with electronics and mechanical engineering. I did know that I have some significant skills as a programmer, so I hoped that would help compensate for my other deficiencies.
In programming, things are on and off, true or false; values are known and don’t deviate. I came to find out that it is not the same in the real world of electronics and mechanics. No amount of programming prowess was going to compensate for my electronics and mechanical newb-ness. I was going to have to learn how to reign in an analog world into a digital format that I can work with.
So…I decided to learn electronics. Digital electronics, at first, because it fits best into my digital view of the world. I went through the whole breadboard , then toner transfer, etching, and building my own circuits. I’ve learned a lot in this journey.
So…I decided to scrap the robot project. Why? Well, to be blunt, most robots I saw during my journey in electronics fell short of the expectations I would have for myself. Some stood out, but it was clear that there was a significant amount of electronics, mechanics, and programming skill behind them that I felt I simply didn’t have at this point. What to do then?
Well, I figured I should hone my electronics skills by building a project of significant complexity in electronics. Next I should hone my mechanics skills by building a project of significant complexity in mechanics. For my first project, I decided that I should build an electronic scoreboard for my daughter’s softball team. The beauty of this project is that it involves almost no mechanics whatsoever. That way my lack of experience with mechanics won’t stall the project.
This is where I am today. Building the scoreboard. And this blog is my attempt at documenting my successes and my failures. Along the way, I expect to be able to post valuable information for others to use, and hopefully I can also see some feedback from the community for improvements to my project.
I have many other interests and projects going on, so you may see much more than just the scoreboard on here. Feel free to enjoy my other ramblings as well.
