Unreadable Binary Epoch clock is unreadable

binary-epoch-clock

What time is it? For that matter, what is the date? This clock can tell you both of those things, if only you could read it. The inspiration for this Binary Epoch kit came after a friend of [Maniaclal Labs] built an eight-bit binary clock. That’s a pretty common project that gets riffed on for things like mains-timed logic-driven clocks. They figured why not make it bigger? But even then you can make some sense out of the display after studying it for just a bit, you won’t be much closer to answering those two questions.

The problem is that this is unreadable in a couple of different ways. First off, how long did it take you to figure out in your head the decimal equivalent of the binary number displayed above? We gave up. But pounding the number into Google (search for: 0b01010010000010000001001010010011 in decimal) gives us 1376260755. meaningful? Again, not to a human. This is Unix time, which is the number of seconds elapsed since the Epoch: 8/11/13-22:39:15.

Check out the video below that shows how to set the clock, which uses a menu system for human-friendly input. But since it’s Arduino compatible you can also connect an FTDI cable and program it from a computer. Oh, and since this is Open Source Hardware (note the icon in the lower right) you can get all the info to build (or breadboard) your own from their Github repo.

Here’s another complicated clock that uses Nixie tubes to display time and date info which is actually of use.

37 thoughts on “Unreadable Binary Epoch clock is unreadable

  1. “since the Epoch: 8/22/13-22:39:15″

    Unix time, or POSIX time, is a system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, not counting leap seconds.

  2. It looks like 5:20 on August 12, 2013

    8-bit chunks is groups of 4.
    0101 0010 0000 1000 0001 0010 1001 0011
    5 2 0 8 1 2 1 3

    That’s without Googling it. I might be wrong, but if it’s a clock and calendar, that’s what I get out of it.

    1. I like your take on how you thought it was read. I like the idea, would make it *slightly* more readable by taking out the number of seconds since 1/1/1970 thing :) Might have to add that in a future firmware revision.

        1. Actually I’m retarded. You can take into account numbers up to 15 with a nibble. But what I just noticed is that Ran_D’s comment thinks the second-to-last nibble is 1 when it should be 9.

  3. Ok, I’ll be the ass.
    Straight from wiki guys: Unix time, or POSIX time, is a system for describing instants in time, defined as the number of seconds that have elapsed since 00:00:00 Coordinated Universal Time (UTC), Thursday, 1 January 1970, not counting leap seconds.
    Not 8/22/2013.

  4. Sooooooooo very stupid. A clock by it’s very nature is to TELL THE TIME. If you can’t figure out what time the clock is displaying (and do so in a very short period – before the time has changed), then the clock has FAILED.

    1. Can you read the mayan calendar stone without a reference? Probably not – but it was useful to them. This is a geek’s geekiest clock for geeky geeks. Just because it isn’t cheerfully singing the date and time in a familiar dialect at a comfortable volume doesn’t make it a failure. Not indicating if it’s big-endian or little-endian does though. ;-)

      1. MSB is the one on the left (it’s unsigned in this case) and if you use the silkscreen as the “memory address” the left LED is D32 therefore highest address and most significant, so it’s little-endian. In general though it was just built to show the value as we would write a binary value, that being MSB on left and LSB on right.

        1. Now I’m confused, you say the MSB is on the left then say it was designed to have the MSB on the right..

          ~scratches head~

        2. That’s what I assumed as well as it’s pretty much the dominant standard unless you’re writing for old Macintosh OS’s (and maybe some others?). Personally I think this has the same cool potential as a bit of sci-fi set / cock-pit blinking light niceness. Two flipped end to end would make an interesting display.

      1. And cue the whiny bitch society to chime in and lecture how everyone should join their circle jerk crowd and “ooh and ah” at how wonderful every little freaking thing posted on HAD is.

        Try having an original thought – don’t be scared – you might find you’re not as stupid as you sound.

    2. I agree. What it should be measuring is the total time wasted by himself creating it, hackaday for the write-up, the thousands of visitors all having to look at it.. and us in the comments. That might be a reasonable amount of time, a success? lol.

  5. This must be art. Nobody really understands it or understands why it was made and it’s pretty useless.
    I don’t like art.

  6. Ok so it’s a kit for a useless clock that tells time in an arcane (to the average person) system and displays it in binary in such a way that by the time you figure out what the time actually is it won’t be that time any more? I have just one question, can the kit be converted into a watch?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s