Retrotechtacular: ASCII Art In The 19th Century

June 28, 2016 by Al Williams 43 Comments

Computer graphics have come a long way. Some video games today exceed what would have passed for stunning cinema animation only a few years ago. However, it hasn’t always been like this. One of the earliest forms of computer-generated graphics used text characters to draw on printers.

Early computer rooms were likely to have a Snoopy character on green and white fan-fold paper. Calendars with some artwork were also popular (see left, and find out about the FORTRAN that created it, if you like). Ham radio operators who use teletypes (RTTY, in ham parlance) often had vast collections of punched tape that held artwork. Given that most hams in the 1950s and 1960s were men and the times were different, a lot of them were more or less “R” rated.

Not all of them were, though. For example, Richard Nixon was decidedly “G” rated (see right). Simple pictures would use single characters, but sophisticated ones would use the backspace character to overprint multiple characters.

Ham Radio Art

You often hear this described as ASCII art, today, although hams usually use 5-bit BAUDOT code, so that’s a misnomer for those images, at least. Of course, today, people aren’t keen on storing roll after roll of paper tape (or even owning a tape reader) so there have been several projects to capture this art in a more modern format.

Although there is still some RTTY art activity, picture sending has been mostly replaced by slow scan TV (SSTV) which sends actual still images or other modes like FAX. Some of the newer digital modes even have the ability to send pictures. You can be discussing your radio for example, and then show the other ham a photo of the radio.

Continue reading “Retrotechtacular: ASCII Art In The 19th Century” →

Serially, Are You Syncing Or Asyncing?

June 28, 2016 by Rud Merriam 25 Comments

I know you’ve heard of both synchronous and asynchronous communications. But do you really know the differences between the two?

Serial communication was used long before computers existed. A predecessor is the telegraph system using Morse Code, one of the first digital modes of communication. Another predecessor is the teletype, which set standards that are still used today in your Arduino or Raspberry Pi.

All you need is two wires for serial communications, which makes it simple and relatively robust. One wire is ground and the other the signal. By interrupting the power with predefined patterns, information can be transferred over both short and long distances. The challenge is receiving the patterns correctly and quickly enough to be useful.

I was a bit surprised to find out the serial port on the Arduino Uno’s ATmega328P microcontroller is a Universal Synchronous Asynchronous Transmitter Receiver (USART). I’d assumed it was only a UART (same name, just leave out synchronous) probably because my first work with serial communications was with the venerable Intel 8251 “Programmable Communication Interface”, a UART, and I didn’t expect the microcontroller to be more advanced. Silly me. Later I worked with the Zilog 8530 Serial Controller Chip, a USART, the term I’ll use for both device types.

All these devices function in the same way. You send a byte by loading it into a register and it is shifted out one bit at a time on the transmit (TX) line as pulses. The receiver accepts the pulses on a receive (RX) input and shifts them into a register, which is then read by the system. The transmitter’s job is pretty easy it just shifts out the bits at a known clock rate. The receiver’s task is more complex because it needs to know when to sample the incoming signal. How it does this is the difference between asynchronous and synchronous communications.

Continue reading “Serially, Are You Syncing Or Asyncing?” →

Taking Killer Robots Seriously

June 27, 2016 by Elliot Williams 61 Comments

Killer robots are a mainstay of science fiction. But unlike teleportation and flying cars, they are something that we are likely to see within our lifetime. The only thing that’s stopping countries like the USA, South Korea, the UK, or France from deploying autonomous killing machine in the very near term is that they’re likely to be illegal under current international humanitarian law (IHL) — the rules of war.

But if you just sighed in relief that the fate of humanity is safe, think again. The reason that autonomous killing machines are illegal is essentially a technicality, and worse, it’s a technicality that’s based on the current state of technology. The short version of the story, as it stands right now, is that the only thing making autonomous robotic killing weapons illegal is that it’s difficult for a robot to tell a friend from an enemy. When technology catches up with human judgement, all bets are off.

Think I’m insane? The United Nations Office at Geneva (UNOG), the folks who bring you the rules of warfare, started up a working group on killer robots three years ago, and the report from their 2016 meeting just came out. Now’s as good a time as any to start taking killer robots seriously.

Continue reading “Taking Killer Robots Seriously” →

Hackaday Links: June 26, 2016

June 26, 2016 by Brian Benchoff 40 Comments

Solar Freaking Roadways. What is it? It’s technology that replaces all roadways with a smooth sheet of glass and solar panels. You know how asphalt is soooo easy to repair and soooooo cheap? Yes, this is the exact opposite of that. They’re coming to freaking Missouri. A parking lot for the Route 66 Welcome Center in Conway, MO will be paved with the solar freaking roadways that netted $2 Million in an Indiegogo campaign two years ago.

There is a National Potato Expo. As far as I can tell, this is a trade show for potatoes and potato-related paraphernalia. As with all trade shows you need a great demo, in this case one involving potatoes. How about a phone charging station powered by potatoes? It’s a bunch of potatoes, copper pipe, galvanized nails (neat design, btw), and a USB socket. Yes, it works, but not well.

The travelling hacker box is a USPS flat rate box filled to the brim with random bits and bobs of electronics, shipped back and forth between dozens of electron enthusiasts. It’s making one last trip around the US, and now the travelling hacker box needs destinations from Idaho to Michigan. Idaho, of course, is a fictional state created in 2004 for Napoleon Dynamite, but that still leaves Montana, the Dakotas, Wisconsin, Minnesota, and the UP. If you live in one of these states, there’s a travelling hacker box with your name on it. Request to join the project and PM me on hackaday.io.

It’s election year in the US, and that means half of the population hates one candidate, half of the population hates another candidate, and half of the population will vote. Don’t think about that for too long. Here’s an Arduino doing something topical with Twitter.

Hotends for 3D printers are getting more and more robust, but thermistors are fiddly little things. E3D just came up with the solution. It’s a standard, modular temperature ‘cartridge’ that fits in E3D’s heater blocks. You can already change out the heater cartridge on a 3D printer for a higher wattage model, and now you can change out a thermistor for a thermocouple just as easily. E3D sells their stuff in GBP, so considering recent events it might be a good time to pick up a new hotend for that Monoprice 3D printer you picked up

The 8-Bit Generation recently released their documentary The Commodore Wars, chronicling the stupendous rise and meteoric fall of Commodore. Now they’re working on the Atari version and they’re funding it with a Kickstarter. Rumor has it Hackaday’s own [Bil Herd] has been asked to narrate.

Here’s another Hackaday Retro Edition success story @KetturiFox pulled up the Hackaday Retro Edition on a Texas Instruments TravelMate 5000 laptop. That’s a relatively modern laptop with a 75MHz Pentium, PCMCIA slots, and a nub mouse.

Hacklet 113 – New Robots

June 25, 2016 by Adam Fabio 4 Comments

I start each day checking out the new and updated projects over on Hackaday.io. Each day one can find all manner of projects – from satellites to machine vision to rockets. One type of project which is always present are robots- robot arms, educational ‘bots, autonomous robots, and mobile robots. This week’s Hackaday.io had a few great robot projects show up on the “new and updated” page, so I’m using the Hacklet to take a closer look.

We start with [Jack Qiao] and Autonomous home robot that does things. [Jack] is building a robot that can navigate his home. He’s learned that just creating a robot that can get itself from point A to point B in the average home is a daunting task. To make this happen, he’s using the Simultaneous Localization and Mapping (SLAM) algorithm. He’s implementing SLAM with the help of Robotic Operating System (ROS). The robot started out as a test mule tethered to a laptop. It’s evolved to a wooden base with a mini ITX motherboard. Mapping data comes in through a Kinect V2, which will soon be upgraded to a Neato XV-11 LIDAR system.

Next up is [Tyler Spadgenske] with TyroBot. TyroBot is a walking robot with some lofty goals, including walking a mile in a straight line without falling down. [Tyler’s] inspiration comes from robots such as Bob the Biped and Zowi. So far, TyroBot consists of legs and feet printed in PLA. [Tyler] is going to use a 32 bit processor for [TyroBot’s] brain, and wants to avoid the Arduino IDE at any cost (including writing his own IDE from scratch). This project is just getting started, so head on over to the project page and watch TyroBot’s progress!

Next is [Mike Rigsby] with Little Friend. Little Friend is a companion robot. [Mike] found that robots spend more time charging batteries than interacting. This wouldn’t do for a companion robot. His solution was to do away with batteries all together. Little Friend is powered by super capacitors. An 8 minute charge will keep this little bot going for 75 minutes. An Arduino with a motor shield controls Little Friend’s DC drive motors, as well as two animated eyes. If you can’t tell, [Mike] used a tomato as his inspiration. This keeps Little Friend in the cute zone, far away from the uncanny valley.

Finally we have the walking robot king, [Radomir Dopieralski], with Logicoma-kun. For the uninitiated, a Logicoma is a robot tank (or “logistics robot”) from the Ghost in the Shell series. [Radomir] decided to bring these cartoon tanks to life – at least in miniature. The bulk of Logicoma-kun is built carefully cut and sculpted acrylic sheet. Movement is via popular 9 gram servos found all over the internet. [Radomir] recently wrote an update outlining his new brain for Logicoma-kun. An Arduino Pro Mini will handle servo control. The main computer will be an ESP8266 running Micropython. I can’t wait to see this little ‘bot take its first steps.

If you want more robotic goodness, check out our brand new mobile robot list! Did I miss your project? Don’t be shy, just drop me a message on Hackaday.io. That’s it for this week’s Hacklet, As always, see you next week. Same hack time, same hack channel, bringing you the best of Hackaday.io!

Fail Of The Week: Arachno∙fail∙ia

June 23, 2016 by Mike Szczys 84 Comments

Going down the list (FCC, CE, UL, etc.) we can’t think of a regulating body that will test for this failure mode. Reportedly, a $1M irrigation system was taken down by a spider. And an itsy-bitsy spider at that.

This fail turned up as a quick image post over on /r/mildlyinteresting but I wasn’t the only electronics person attracted like a moth to a flame. Our friend [Sprite_TM] popped in to answer a question about conformal coating. Seems this board was sealed in a waterproof enclosure but was obviously not conformally coated.

[Sprite_TM] also helped out with some armchair-engineering to guess at what happened. It’s not hard to tell that the footprint on the board looks like a set of mechanical relays all in a line. He looked up the most likely pinout for the relay.

We’ve superimposed that pinout on the board to help illustrate the failure. High voltage comes in on the pin shown with the red trace leading away from it. On either side of that pin are the connections for the low voltage coil which switches from normally closed (the pin in the upper right that is not connected to anything) to the normally open pin (which has the wide trace leading away from it).

So there sat the high voltage pin in between the coil pins when, along came a spider. It shorted the pins and presumably all the way back to the power supply for the low voltage rail. [Fugly_Turnip] (the OP) share some additional detail about the system and this failure; in addition to this card it fried the control module as well.

Another comment on the same thread shares a different story of two boards mounted next to each other with a bug shorting a 1/4″ air gap between two boards and causing similar carnage. Have you encountered Arachno-fail-ia of your own? Let us know below.

Fail of the Week is a Hackaday column which celebrates failure as a learning tool. Help keep the fun rolling by writing about your own failures and sending us a link to the story — or sending in links to fail write ups you find in your Internet travels.

Books You Should Read: The Car Hacker’s Handbook

June 23, 2016 by Brian Benchoff 44 Comments

I just had my car in for an inspection and an oil change. The garage I take my car to is generally okay, they’re more honest than a stealership, but they don’t cross all their t’s and dot all their lowercase j’s. A few days after I picked up my car, low and behold, I noticed the garage didn’t do a complete oil change. The oil life indicator wasn’t reset, which means every time I turn my car on, I’ll have to press a button to clear an ominous glowing warning on my dash.

For my car, resetting the oil life indicator is a simple fix – I just need to push the button on the dash until the oil life indicator starts to blink, release, then hold it again for ten seconds. I’m at least partially competent when it comes to tech and embedded systems, but even for me, resetting the oil life sensor in my car is a bit obtuse. For the majority of the population, I can easily see this being a reason to take a car back to the shop; the mechanic either didn’t know how to do it, or didn’t know how to use Google.

The two most technically complex things I own are my car and my computer, and there is much more information available on how to fix or modify any part of my computer. If I had a desire to modify my car so I could read the value of the tire pressure monitors, instead of only being notified when one of them is too low, there’s nowhere for me to turn.

2015 was the year of car hacks, ranging from hacking ECUs to pass California emissions control standards, Google and Tesla’s self-driving cars, to hacking infotainment systems to drive reporters off the road. The lessons learned from these hacks are a hodge-podge of forum threads, conference talks, and articles scattered around the web. While you’ll never find a single volume filled with how to exploit the computers in every make and model of automobile, there is space for a reference guide on how to go about this sort of car hacking.

I was given the opportunity to review The Car Hacker’s Handbook by Craig Smith (259p, No Starch Press). Is it a guide on how to plug a dongle into my car and clear the oil life monitor the hard way? No, but you wouldn’t want that anyway. Instead, it’s a much more informative tome on penetration testing and reverse engineering, using cars as the backdrop, not the focus.

Continue reading “Books You Should Read: The Car Hacker’s Handbook” →