The holy grail of display technology is to replicate what you see in the real world. This means video playback in 3D — but when it comes to displays, what is 3D anyway?
You don’t need me to tell you how far away we are from succeeding in replicating real life in a video display. Despite all the hype, there are only a couple of different approaches to faking those three-dimensions. Let’s take a look at what they are, and why they can call it 3D, but they’re not fooling us into believing we’re seeing real life… yet.
The explosion of cheap LED lighting products has given a never-ending array of opportunities for the resourceful hacker. A few dollars can secure strings of colourful illumination, but without further expenditure they lack the extra utility of electronic control. This is something that [Albert David has addressed] with his simple ESP8266-based WiFi switcher that he’s added to a string of USB-powered LEDs, and he’s neatly mounted the ESP-12 module it used atop a USB plug.
The circuitry is pretty straightforward, with only a couple of I/O lines being used. A transistor takes care of the heavy lifting, and the software comes courtesy of the Tasmota firmware for Sonoff (and similar) devices. We suspect with this economy of connection, the same task could be achieved even with the limited resources provided by the lesser ESP-01 module.
There was a time not so long ago when performing a task such as controlling a light over a wireless network involved significant cost, power, and complexity. In the nearly five years since we reported on the arrival of the ESP8266 we have progressed to the point at which that task is a simple project using commodity components, and that represents something of a miracle.
Many Hackaday readers will be settling back into their lives after a holiday period crammed into some family matriarch’s house along with too many assorted relatives, having given up their speedy internet connection for whatever passes for broadband wherever Granny lives. The bargain-basement router supplied by the telephone company will have spent the period wilting under the pressure of a hoard of teenagers watching other teenagers inanities on YouTube, and the Christmas ritual of Resetting The Router will have been performed multiple times.
A very simple schematic for the resetter.
Wouldn’t it be nice if your router simply reset itself every time it crashed or the Internet connection went down? [Cyb3rn0id] has a solution (Italian original here), in the form of an ESP8266 that pings an online service every few seconds, and turns the router off and on again via a power relay in the event that the ping attempt is repeatedly unsuccessful. It’s brilliantly simple, requiring only a single GPIO and a MOSFET to fire the relay with an LED indicator for good measure, and it’s built upon a piece of prototyping board. The router power is switched on the low-voltage side for safety.
The software is pretty basic and has the WiFi credentials hard-coded into it, so we’re guessing a version with a web interface could be built. But as a personal device for easing the pain of router crashes it gets our vote despite that shortcoming.
Should you ever pick up [Steve Wozniak]’s autobiography, you will learn that in the early 1970s when his friend [Steve Jobs] was working for Atari, [Woz] was designing calculators for Hewlett Packard. It seems scarcely believable today, but he describes his excitement at the prospects for the calculator business, admitting that he almost missed out on the emerging microcomputer scene that would make him famous. Calculators in the very early 1970s were genuinely exciting, and were expensive and desirable consumer items.
[Amen] has a calculator from that period, a Prinztronic Micro, and he’s subjected it to an interesting teardown. Inside he finds an unusual modular design, with keyboard, processor, and display all having their own PCBs. Construction is typical of the period, with all through hole components, and PCBs that look hand laid rather than made using a CAD package. The chipset is a Toshiba one, with three devices covering logic, display driver and clock.
The Prinztronic is an interesting device in itself, being a rebadged 1972 Sharp model under a house brand name for the British retailer Dixons, and that Toshiba chipset is special because it is the first CMOS design to market. It was one of many very similar basic calculators on the market at the time, but at the equivalent of over 100 dollars in today’s money it would still have been a significant purchase.
The last few days have seen drone stories in the news, as London’s Gatwick airport remained closed for a couple of days amid a spate of drone reports. The police remained baffled, arrested a couple who turned out to be blameless, and finally admitted that there was a possibility the drone could not have existed at all. It emerged that a problem with the investigation lay in there being no means to detect a drone beyond the eyesight of people on the ground, and as we have explored in these pages already, eyewitness reports are not always trustworthy.
Not much use against a small and mostly plastic multirotor. Sixflashphoto [CC BY-SA 4.0]
Radar Can’t See Them
It seems odd at first sight, that a 21st century airport lacks the ability to spot a drone in the air above it, but a few calls to friends of Hackaday in the business made it clear that drones are extremely difficult to spot using the radar systems on a typical airport. A system designed to track huge metal airliners at significant altitude is not suitable for watching tiny mostly-plastic machines viewed side-on at the low altitudes. We’re told at best an intermittent trace appears, but for the majority of drones there is simply no trace on a radar screen.
We’re sure that some large players in the world of defence radar are queueing up to offer multi-million-dollar systems to airports worldwide, panicked into big spending by the Gatwick story, but idle hackerspace chat on the matter makes us ask the question: Just how difficult would it be to detect a drone in flight over an airport? A quick Google search reveals multiple products purporting to be drone detectors, but wouldn’t airports such as Gatwick already be using them if they were any good? The Hackaday readership never fail to impress us with their ingenuity, so how would you do it?
Can You Hear What You Can’t See?
It’s easy to pose that question as a Hackaday scribe, so to get the ball rolling here’s my first thought on how I’d do it. I always hear a multirotor and look up to see it, so I’d take the approach of listening for the distinctive sound of multirotor propellers. Could the auditory signature of high-RPM brushless motors be detected amidst the roar of sound near airports?
I’m imagining a network of Rasberry Pi boards each with a microphone attached, doing some real-time audio spectrum analysis to spot the likely frequency signature of the drone. Of course it’s easy to just say that as a hardware person with a background in the publishing business, so would a software specialist take that tack too? Or would you go for a radar approach, or perhaps even an infra-red one? Could you sense the heat signature of a multirotor, as their parts become quite hot in flight?
Whatever you think might work as a drone detection system, give it a spin in the comments. We’d suggest that people have the confidence to build something, and maybe even enter it in the Hackaday Prize when the time comes around. Come on, what have you got to lose!
Over the years we have featured a huge array of projects featuring the Raspberry Pi, but among them there is something that has been missing in all but a few examples. The Raspberry P Compute Module is the essentials of a Pi on a form factor close to that of a SODIMM module, and it is intended as a way to embed a Pi inside a commercial product. It’s refreshing then to see [Eugene]’s StereoPi project, a PCB that accepts a Compute Module and provides interfaces for two Raspberry Pi cameras.
What makes this board a bit special is that as well as the two camera connectors at the required spacing for stereophotography it also brings out all the interfaces you’d expect on a regular Pi, so there is the familiar 40-pin expansion header as well as USB and Ethernet ports. It has a few extras such as a pin-based power connector, and an on-off switch.
Where are they going with this one? So far we’ve seen demonstrations of the rig used to create depth maps with ROS (Robot Operating System). But even more fun is seeing the 3rd-person-view rig shown in the video below. You strap on a backpack that holds the stereo camera above your head, then watch yourself through VR goggles. Essentially you become the video game. We’ve seen this demonstrated before and now it looks like it will be easy to give it a try yourself as StereoPi has announced they’re preparing to crowdfund.
So aside from the stereophotography why is this special? The answer comes in that it is as close as possible to a fresh interpretation of a Raspberry Pi board without being from the Pi Foundation themselves. The Pi processors are not available to third party manufacturers, so aside from the Odroid W (which was made in very limited numbers) we have never seen a significant alternative take on a compatible Raspberry Pi. The idea that this could be achieved through the Compute Module is one that we hope might be taken up by other designers, potentially opening a fresh avenue in the Raspberry Pi story.
The Raspberry Pi Compute Module has passed through two iterations since its launch in 2014, but probably due to the lower cost of a retail Raspberry Pi we haven’t seen it in many projects save for a few game consoles. If the advent of boards like this means we see more of it, that can be no bad thing.
There are a range of integrated circuits that most of us would regard as definitive examples of their type, devices which became the go-to for a particular function and which have entered our collective consciousness as electronics enthusiasts. They have been in production since the early days of consumer integrated circuits, remaining in use because of a comprehensive understanding of their characteristics among engineers, and the job they do well.
You can probably name the ones I’m going to rattle off here, the µA741 op-amp designed by David Fullagar for Fairchild in 1968, the NE555 timer from Hans Camenzind for Signetics in 1971, and a personal favourite, Bob Widlar’s µA723 linear regulator for Fairchild in 1967. There may be a few others that readers will name in the comments, but there’s one that until today it’s likely that few of you would have considered. Texas Instruments’ 5400 and 7400 TTL quad 2-input NAND gate has been in continuous production since 1964 and is the progenitor of what is probably the most numerous breed of integrated circuits, yet it doesn’t trip off the tongue when listing famous chips, and none of us can name its designer. So today we’re turning the spotlight on this neglected piece of silicon, and trying to bring it the adulation it deserves. Continue reading “The 7400 Quad 2-Input NAND Gate, A Neglected Survivor From A Pre-Microprocessor World”→
By using our website and services, you expressly agree to the placement of our performance, functionality and advertising cookies. Learn more
![Not much use against a small and mostly plastic multirotor. Sixflashphoto [CC BY-SA 4.0]](https://hackadaycom.files.wordpress.com/2018/12/788px-KCMH_Radar.jpg)
