Running A Hackerspace Is Hard: Egypt Edition

It’s no secret that it’s difficult to run a hackerspace. Different personalities, different material requirements, and often constrained spaces can require continual negotiation. But if you think that having the metalworking types getting their shavings on your electronics bench is a problem, try having your entire hackerspace demolished on short notice.

The situation in Cairo is far from normal at the moment. The building that Cairo Hackerspace had recently moved to was raided, closed for two months, and then re-opened under strict surveillance in February.

All was well until a part of the building unexpectedly collapsed. Then they got a demolition order, followed by postponement, followed by armed police entering anyway and breaking stuff, followed by a further declaration of the building as safe, and now a heritage site. And all of this over a week’s time. While some of the art studios in the Townhouse were saved, the Cairo Hackerspace’s space is gone.

tumblr_inline_o5virriTeD1t3bbl6_500

The good news? Nobody got hurt in all of this, and the Cairo Hackerspace crew were able to get their gear out after the initial demolition notice. They’ve been working on a mobile hackerspace-in-a-van approach lately, so hopefully they’ll be able to keep on hacking.

So when you’re bickering over who didn’t clean up the hackspace’s coffee machine, or the proper location of your favorite soldering iron, think kindly about the Cairo crew and get back to doing what you do best — projects.

How about you? What hackerspace tales do you have? Contact us through the tips line — we’d love to hear.

Hacklet 106 – Robots That Teach

One of the best ways to teach electronics and programming is with hands-on learning. Get the concepts off the computer screen and out into the real world. Students of all ages have been learning with robots for decades. Many older Hackaday readers will remember the turtle robots. These little ‘bots would drive around drawing shapes created in the logo programming language. This week’s Hacklet is all about the next generation of robots that teach electronics, mechanics, programming, and of course, hacking. So let’s check out some of the best educational robot projects on Hackaday.io!

edubotWe start with [Tom Van den Bon] and Edubot Controller (Benny). Buying one or two robots can get expensive. Equipping a classroom full of them can break the bank. [Tom] is hoping to make robots cheaper and more accessible with Edubot, his entry in the 2016 Hackaday prize. Edubot rides on a 3D printed frame with low-cost gear motors for a drive system. Edubot’s brain is an STM32F042, a low-cost ARM processor from ST micro. The micro and motor drives are integrated into a custom board [Tom] designed. He’s has even begun creating lesson plans so students of various ages and skill levels can participate and learn.

microbotNext up is [Joshua Elsdon] with Micro Robots for Education. Big robots can be intimidating. They can also cause some damage when hardware and software created by budding engineers doesn’t operate as expected. Tiny robots though, are much easier to wrangle. [Joshua ] may have taken tiny to an extreme with these robots. Each robot is under 2 cm square. The goal is for each one to cost less than  £10 to produce. These micro bots have big brains with their ATmega328P micro controllers. [Joshua] is currently trying to figure out a low-cost way to produce wheels for these robots.

Next we have [shamylmansoor] with 3D printed mobile robot for STEM education. Robots are expensive, and international shipping can make them even more expensive. [Shamyl] is shooting for a robot which can be made locally in Pakistan. 3D printing is the answer. The robot’s chassis can be printed on any FDM printer. Wheels,and tires are low-cost units. Motors are RC servos modified for continuous rotation. The brains of the robot is an Arduino Mega 2560, which should provide plenty of inputs for sensors. [Shamyl] even included a solderless breadboard so students can prototype circuits and sensors right on the robot’s body.

 

plobotFinally we have [Rodolfo] with Plobot. Plobot is a robot designed for the youngest hackers – those from four to seven years old. [Rodolfo] designed Plobot to be programmed with RFID cards. Each card contains a command such as move forward, turn, start, and reset. Many of the language mechanics are inspired by the Scratch programming language. Plobot’s processor is a Sanguino, running [Rodolfo’s] custom code. An ESP8266 allows Plobot to be connected to the outside world via WiFi. [Rodolfo] has even created a custom over the air update system for Plobot’s firmware. Plobot has already been tested with students, where it made a great showing. We’re hoping both [Rodolfo] and Plobot do well in the 2016 Hackaday Prize!

If you want more mind hacking goodness, check out our brand new educational 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!

How To Design, Manufacture, And Document A Hardware Product

It’s pretty awesome to have a hardware design hero jump at the chance to work on a Hackaday conference badge. I am of course talking about Voja Antonic.

I’ve gotten to know him over the last two years when we were introduced and he agreed to work on some original articles. He’s long been a hacker and shared his story of technology despite politics and society changing around him. His Galaksija computer was the first personal computer available in Yugoslavia with over 8,000 kits sold. Since those days he never stopped refining his design and fabrication skills. For instance, his method of making cases from FR4 is beyond compare, and reading some of his wisdom from hardware design in the casino industry is the kind of fascinating stuff that rarely makes it out for others to enjoy.

But I digress — the point is Voja’s been around the block, he knows what he’s doing, and he does it at an amazingly high level. He did an incredible job with the Hackaday | Belgrade conference badge. It features a 16×8 LED display, IR comms hardware, 5 user buttons, USB programming, an option for an accelerometer module, and has spectacular life running on two AAA batteries. It was a hit at the conference, and so was his talk discussing the design and fabrication. Check it out below and then join me below the fold.

Continue reading “How To Design, Manufacture, And Document A Hardware Product”

Hackaday Dictionary: Transformers

Funny stuff, electricity. It’s all about the volts and the amps, and controlling these two factors. Most of the time, the electricity coming into your device is at a higher voltage than you need, so you have to convert it down to something more usable. The easiest way to do this is with a transformer.

The transformer in your power supply takes a high voltage from the mains and converts it down into a lower voltage to power your gadgets. You’ll find one in all power supplies, from the miniature USB version that powers your cell phone to the big ones hanging on a telephone pole that drive your home’s mains electricity. Although these transformers are different sizes, they share the same fundamental design.

Continue reading “Hackaday Dictionary: Transformers”

Fail Of The Week: ESP8266 Heats Temperature Sensor

[Richard Hawthorn] sent us in this interesting fail, complete with an attempted (and yet failed) clever solution. We love learning through other people’s mistakes, so we’re passing it on to you.

First the obvious-in-retrospect fail. [Richard] built a board with a temperature sensor and an ESP8266 module to report the temperature to the Interwebs. If you’ve ever put your finger on an ESP8266 module when it’s really working, you’ll know what went wrong here: the ESP8266 heated up the board and gave a high reading on the temperature sensor.

temp2Next came the clever bit. [Richard] put cutouts into the board to hopefully stop the flow of heat from the ESP8266 module to the temperature sensor. Again, he found that the board heats up by around four degrees Celcius or nine degrees Farenheit. That’s a horrible result in any units.

What to do? [Richard’s] first ideas are to keep hammering on the thermal isolation, by maybe redoing the board again or adding a heatsink. Maybe a daughterboard for the thermal sensor? We can’t see the board design in enough detail, but we suspect that a flood ground plane may be partly to blame. Try running thin traces only to the temperature section?

[Richard]’s third suggestion is to put the ESP into sleep mode between updates to reduce waste heat and power consumption. He should be doing this anyway, in our opinion, and if it prevents scrapping the boards, so much the better. “Fix it in software!” is the hardware guy’s motto.

But we’ll put the question to you electronics-design backseat drivers loyal Hackaday readers. Have you ever noticed this effect with board-mounted temperature sensors? How did you / would you get around it?


2013-09-05-Hackaday-Fail-tips-tileFail 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.

JIT Learning Using Expert Systems

Chris Gammell is a guy that should need no introduction around these parts. He’s a co-host on The Amp Hour, and the guy behind Contextual Electronics, a fabulous introduction to electronics and one of the best ways to learn KiCad. If you want to talk about the pedagogy of electronics, this is the guy you want.

Chris’ talk at the Hackaday | Belgrade conference was on just that – the pedagogy of electronics. Generally, there are two ways to learn how to blink an LED. The first, the bottom-up model taught in every university, is to first learn Ohm’s law, resistance, current, voltage, solve hundreds of resistor network problems, and eventually get around to the ‘electrons and holes’ description of a semiconductor. The simplest semiconductor is a diode, and sometime in the sophomore or junior year, the student will successfully blink a LED.

The second, top-down method is much simpler. Just wire up a battery, resistor, switch, and LED to a breadboard. This is the top-down model of electronics design; you don’t need to know everything to get it to work. You don’t need to do it with a 555, and you certainly don’t have to derive Maxwell’s equations to make something glow. Chris is a big proponent of the top-down model of learning, and his Belgrade talk is all about the virtues of not knowing everything.

Continue reading “JIT Learning Using Expert Systems”

Getting Ugly, Dead Bugs, And Going To Manhattan

Back in the 1980s I was a budding electronics geek working in a TV repair shop. I spent most of my time lugging TVs to and from customers, but I did get a little bench time in. By then new TVs were entirely solid-state and built on single PC boards, but every once in a while we’d get an old-timer in with a classic hand-wired tube chassis. I recall turning them over, seeing all the caps and resistors soldered between terminal strips bolted to the aluminum chassis and wondering how it could all possibly work. It all looked so chaotic and unkempt compared to the sleek traces and neat machine-inserted components on a spanking new 19″ Zenith with the System 3 chassis. In a word, the old chassis was just – ugly.

Looking back, I probably shouldn’t have been so judgmental. Despite the decades of progress in PCB design and the democratization of board production thanks to KiCad, OSH Park, and the like, it turns out there’s a lot to be said for ugly methods of circuit construction.

Continue reading “Getting Ugly, Dead Bugs, And Going To Manhattan”