Want To Play Pong On Your Oscilloscope?

I always have! I don’t know why, but I like the idea of using an oscilloscope screen as a general use video display. Why not? In my case it sits on my desk full time, has a large screen area, can do multiple modes of display, and is very easy control.
Making an oscilloscope screen do your bidding is an old trick. There are numerous examples out there. Its not a finished project yet, so be nice. It is actually rather crude, using a couple parts I had on hand just on a whim. The code is a nice mixture of ArduincoreGCCish (I am sorry, still learning), and includes the following demos:

  1. Simple low resolution dot drawing
  2. A font example
  3. A very quickly and badly written demo of pong

The software runs on an Attiny84 micro controller clocked at 16Mhz, paired up with a Microchip MCP42100 dual 100k 8 bit digital potentiometer though the Attiny’s USI (Universal Serial Interface) pins. This is a fast, stable and accurate arrangement, but it requires sending 16 bits every time you want to change the value of one of the potentiometers so its also very piggy. I was just out to have some fun and did not have a proper 8 bit DAC. This was the closest thing outside of building one.
Join us after the break for pictures a (very) brief video and more.

Continue reading “Want To Play Pong On Your Oscilloscope?”

Comment System Updates

We’ve been working hard on this one and finally made a tiny bit of progress.

You will find that comments are now nested.  We can see there are some slight visual issues, but we’re working on it. Please be patient with us.
Another edition you will find is the “report” button. If you find comments offensive, click that button to let us know.

Again, we’re still working through this and have a decent list of quirks that need worked out but it seems to be mostly functional.

Live NBA Scoreboard With Huge 7-segment Displays

[Kianoosh] was in Las Vegas over spring break and was fascinated by the real-time sports scores displayed at the casinos. He figured that this would be an easy enough project to duplicate, so he built a gigantic NBA scoreboard that updates live from the NBA website.

The build uses the OS X Automator to pull scores down from the NBA’s mobile site. Sending this through a parser written in Java, the scores are then sent to an ATMega32 over an XBee. [Kianoosh] posted all the code and schematics, as well as a PDF writeup. Because the scoreboard is sport-agnostic, [Kianoosh] plans on writing new code for the NFL, MLB, and NHL. We’re really impressed with this build, and with the giant 7-segment LEDs, this would be a great addition to a sports bar (or really any bar).

Continue reading “Live NBA Scoreboard With Huge 7-segment Displays”

Making And Selling Star Wars Costumes Ruled To Be Legal

 

[Andrew Ainsworth] has been making and selling costumes based on Star Wars character (some original, and some of his own creation) for several years. Lucasfilm sued him for $20 million back in 2004 claiming infringement of intellectual property rights. He stopped selling them in the US (as it was a US copyright) but now the UK Supreme Court has ruled in his favor, siding with his claim that the costumes are functional items and not works of art.

Good for him, but copyright issues aren’t what interests us here. The BBC clip showing him using a vacuum former to make the Stormtrooper helmet really caught our attention. A bit of further searching led us to find the thirteen minute video after the break showing the entire process, from sculpting the mold by hand, to forming the components, and the final assembly seen above. It’s a fascinating process that makes use want to build our own vacuum former (preferably on a larger scale than this one). It would come in handy whether it’s Star Wars, Daft Punk, or any number of other projects you’ve got in mind.

Continue reading “Making And Selling Star Wars Costumes Ruled To Be Legal”

Hackaday Comment Policy; We’re Cleaning Up.

Sit down for a moment commenters, we need to talk.
Yes, you all knew this post was coming one day. We’ve talked about this topic at length internally, and we have decided that we’re going to clean up our act. For some time, Hack a Day has been growing a reputation as the prime source of extremely negative, vulgar, rude, sexist, and inflammatory comments in the hacking community. We’ve had complaints from readers (yes there are readers that aren’t commenters, thousands of them) and fellow members of the hacking community about this problem for a long time. [Eliot] even mentioned it back in 2009 when a job applicant expressed concern. We’ve nicely tried to steer things to the positive in a variety of ways, from suggesting commenters to be more supportive, jokingly making a troll detector, and simply stating that the comments need to stay “on topic and nice”.

When we see things like these  tweets by [Jeri Ellsworth], we hang our heads in shame.

She’s not the only one. We actually get this quite regularly. As our readership grows, we see it more and more often. We get emails explaining that people have done a hack but don’t really want to post it because the commenters will just tear it apart in an unnecessarily aggressive and negative way. We have actually had people ask us to remove their projects and comments due to uncivil behavior. Constructive criticism is good, but insulting and angry deconstruction isn’t helpful to anyone.

We’re better than that aren’t we? We are fast, agile and fairly unrestricted in our content. We should be at the center of this community, not on the outer edges, reviled by many for the behavior of a few. Hackaday should be the teacher at the front of the classroom, not the kid in the back throwing wadded up paper at the kids in the front.

What we’re doing:
First off, as far as we can foresee, we will never close the comments section of our web site down. Hackaday should be a home for the entire hacking community and as such, you will always be able to settle in and have a reasonable discussion. We do not want to implement any sort of G+ integration or similar, nor do we want to require registration to leave a comment. We will if we absolutely have to, but lets try to avoid that.

Comment sections and forums have often been a place where negative comments can get out of hand. There are many theories for why this happens, but the result is usually the same: rules and moderation. Many sites have already laid down the law and are adhering to their goals of keeping things civil. We realize that we are to blame if our image is this poor, so we are doing something about it.

From this point moving forward, Hackaday comments will be civil. If you are posting an empty in-joke (“where’s the Arduino?”), a declaration of “not a hack”, a racist, sexist, completely off topic, platform-hating, or personally insulting comment, your post will be deleted. This will be at the discretion of whichever Hackaday staff member happens to see your comment first.

Can you criticize Hackaday?
You can’t walk into a business and start screaming about how much they suck without being escorted out immediately.  Same thing applies here.

We are always hard at work trying to find interesting hacks, makes, repairs, tweaks, videos, etc. that appeal to a wide spectrum of readers. We put this web site together for you, as well as 200,000 other individuals.  Not everything will appeal to everybody. That would be impossible. However, if you don’t like a post or project, just skip it – we’ll have another one ready in short order. We will feature projects that appeal to the seasoned EE as well as the complete beginner. We were all beginners at one time, and it would have been great to have something like Hack a Day around back then to show us hacks ranging from simple to advanced.

From time to time however, Hack a Day can be a less than desirable place to hang out, especially for those who are coming here for the first time. We don’t want to chase off young, creative minds. As a community, we should be helping those that are just starting to venture into hacking electronics.

If you have a problem, email us. You’ll probably actually get a response that way too.  My email is Caleb@ and you’re always welcome to email me personally. Again, please be civil (yep, I’ve had my share of death threats).

Grammar/spelling corrections and dead links:
No need to comment, just email us. A message to team@ will suffice, but you will probably get a quicker response by emailing the author directly. We know we have issues – we’re often so excited about a hack that some little goof slips by. Email us and we’ll fix it. Don’t write a 3 paragraph comment about how important the oxford comma is, or how we’re obviously incapable of functioning because we accidentally flubbed a word. We promise we will never intentionally screw up some grammar, spelling, or punctuation.

What you can will do to help:
Be constructive.

Every project here probably has an area that could be improved, or a part that was done inefficiently. Support your fellow hackers by offering your expertise. Explain why something isn’t working, or how you would improve it. Don’t slam them for their shortcomings. Also keep in mind that different people go about things different ways. Poster X didn’t build something the way you did?  Offer an alternative without being insulting. If someone chooses to use their brand new Core i7 monster system to drive a few LEDs, that’s their prerogative. Inside, we all know that it is not the most efficient use of money or technology, there’s no reason to beat that dead horse in public.

You know what else encourages hackers to do more projects? A pat on the back. I talk to people all the time who say that they just don’t have any constructive criticism for the projects, so they don’t comment. Well, that and they know they’ll bring the ire of the worst commenters if they happen to ask a silly question. Drop in and say what you like about a project. Those positive posts might just be enough to encourage that hacker to take it a step further. How many projects have you seen dropped simply because people thought there wasn’t any interest? Tons. If you like a project, let them know.

To encourage this, the writers are going to be keeping an eye on the comments. Randomly, when we see someone being exceptionally helpful, we’ll contact them and send them a prize. This will most likely be in the form of a hackaday sticker, but we’ll see if we can’t find some other fun things as well.

Help us make Hack a Day great. Please.

[Update: we’re working on a comment flagging system currently]

[Update: threading and comment reporting have been added]

Hacking 14 Year Old Power PC Mac Back To Life

For a while now I have been battling a dying 2.6Ghz dual core computer, but due to laziness and budget I just let it ride. At first it would occasionally crash in games, then it got to where it would crash during routine activities. After a year of this it would nail 105 degrees C in like 20 seconds and that is where the drama starts!

I threw my 2ghz “electronics” computer into my main machine’s case and used that for a few months. It’s motherboard had suffered from every electrolytic capacitor on it being puffy, but it has worked fine for nearly 5 years. I was surprised by the sound of what ended up being 2 caps blowing off of the geforce 7600 video card. In shock and excitement I removed the blown caps, slapped her back in and got another 4 months out of it before 2 more capacitors blew and took out a voltage regulator (and who knows what else with it).

Only armed with the craptop, I was stuck in a pickle! Then a co-worker came up to me and said “hey man you want this mac I only want its zip drive”. Well of course, going bonkers without my avrgcc, datasheets, and calculators, I took on the 14 year old Apple Power Macintosh 9600/300 as my bench machine, and I will now show you how I turned it from a novelty relic to a daily useful machine after the break.

Continue reading “Hacking 14 Year Old Power PC Mac Back To Life”

Radio Shack Will Now Stock Cellphones, Cellphone Accessories, Arduinos

A few months ago, we covered Radio Shack’s efforts to suck less, and the Radio Shack DIY team has now come back with the top ten suggestions submitted. Of course Arduinos make the list at number 1, which we somewhat expected for beginner projects.  Here’s the entire list in order:

  1. Arduino
  2. More kits and project suggestions
  3. More introduction/instructional books
  4. Larger LED selection
  5. Larger resistor selection
  6. TONS more capacitors
  7. DIY audio and speaker equipment
  8. HAM radio gear
  9. More competitive pricing
  10. Stronger sales force