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”→
Picture this: it’s late in the evening on a freezing cold, dark, and windy December night in southern England, and an airport worker at Gatwick — London’s second international airport — sees something fly past in the gloom above the floodlights. The weather and darkness makes it difficult to see what the object was, but the report is phoned in to security. What was it? A flock of birds? A piece of plastic litter caught by the wind and blown through the night? In this case, the call is recorded as a drone. Because the magic D-word has been uttered, a security plan swings into action, the airport is put on a high state of readiness, and flights are suspended.
Gatwick by night, on an evening far less inclement than last week. News Oresund [CC BY 2.0].Thousands of people across the site are put on alert, watching for the drone. And of course, the drone reports roll in, and the story takes on a life of its own. People who have no idea what a drone looks like in the air are now expecting to see one, so of course when a flock of birds or a plastic bag caught by the wind crosses their peripheral vision they too are convinced that it is the drone. Night turns into day, there is a lull in the reports so the airport re-opens, only to be closed again following a fresh spate of sightings. Flights are diverted all across the country, and tens of thousands of passengers are stranded in the terminals.
No, it’s not a speck of dirt on your screen, it’s a drone! BBC (Fair use)
There follows three days of airport closure drama. No photos emerge despite almost every one of the many thousands of people on the site having a camera phone from which they are Tweeting about the queues in the terminal. There is a grainy video, but it is indistinct, and crucially it doesn’t have anything in it that is identifiable as Gatwick. Meanwhile the police are frustrated in their search for the drone operators, who like their drone, prove difficult to pinpoint
During the third night a pair of arrests are announced, a local couple. The police have saved the day, the culprits are under lock and key. Everyone breathes a sigh of relief, the airport re-opens, and that’s the end of that. Except of course it isn’t, because inconveniently the pair are found to be blameless and released. When pressed during an interview, a police spokesman then makes the embarrassing admission that there is a possibility that there may never have been a drone at all.
You Couldn’t Make It Up
If these are the drone parts they’ve found, they’re doing it wrong. Francis Wood [CC BY-SA 3.0]You might imagine that this was the fictional plot of a thriller novel, but sadly not. All of the above is a tale of the last few days of events in the British news, save for most of the first paragraph which is our guess at how the first drone sightings may have happened. At the time of writing there remains the possibility that there could have been a drone over Gatwick, but given the current dearth of evidence it is one that seems tenuous. There are reports of drone wreckage, but since readers with long memories will recall UK police once identified RepRap parts as a 3D printed gun we’ll wait until we see it before we call it that.
If there was indeed a drone then of course we would like to see its operators brought to justice forthwith. But what concerns us at Hackaday are the implications the episode could still have for those of our community with an interest in multirotors. The usual clamour was made for Government to do something about it, and we know that would have meant a fresh set of onerous regulations for responsible multirotor owners while doing nothing about the criminals, because of course criminals have little regard for laws.
So if we are to glean anything from this sorry mess, we must examine it from several angles. Why is there a lack of drone detection technology in place? How should drone reports initially be treated and investigated on the ground? How should they be dealt with in official inquiries, and how then should lawmakers see them? This will inevitably have a British flavour to it because of the incident in question, but the points are just as valid worldwide.
When a Drone Report Comes In, We Need a Reliable Way to Evaluate It
An oft-shared drone identification guide for airline pilots, of uncertain provenance (phantompilots.com).
When we are told something new, it passes a process of evaluation in our minds. We look at the source, and weigh up the story itself. If a guy with crazy hair in the street tells us that the aliens have landed and are controlling the Prime Minister with a ray gun, it will probably be discounted. But if Hackaday tells us that someone has hacked a VGA chipset to work as a software-defined radio we’re guessing most of you would be very interested indeed.
When a fresh drone incident is reported it appears that this evaluation process has historically been defective. We have previously discussed official incident reports that come with no physical evidence of a drone, but contain descriptions of drones with capabilities unmatched even by jet fighter aircraft. It seems like any eyewitness report in which the culprit is named as a drone is automatically taken at face value no matter how unlikely it may be. The fact that a report may have come from a pilot is sometimes mentioned as a boost to its credibility, but that is a false assumption. A pilot who is not familiar with either how drones appear from a distance or what the capabilities of a drone are in the air can only be considered an unreliable witness, because while they may know a lot about aircraft they lack the required expertise for this judgement. So what can be done to help boost the quality of reporting and to immediately highlight credible reports while requiring more for dubious ones?
In the case of a near miss in open airspace there may be little effect on ground-based facilities, but at an airport such as Gatwick there can be no chances taken by the authorities. A drone collision on an aircraft on final approach could cause hundreds of fatalities, so upon receipt of a report they must have had little choice but to close the runways. There appears to have been a lack of drone detection technologies in place at Gatwick which means that the only source available to the airport would have been the eyewitnesses themselves, and since we have amply demonstrated the potential for eyewitness reports being unreliable then the current confusion becomes an inevitability. It is imperative that more reliable detection technologies be fitted or developed if necessary. This is especially true when precautionary shut-downs stretch past minutes or hours into world-news-making delays as happened in this instance.
Competent Police Investigations and Responsible Journalism on Drone Reports
The mass media tech story cycle. Our apologies to Gartner. Curve image: Jeremykemp [ CC BY-SA 3.0 ]Once an incident has started and news of it emerges there is a consequent effect upon members of our community. Legitimate drone fliers away from the airport will find themselves under more scrutiny, and since it is already a common tale to hear of police being called when flying is under way that means they could face harassment and wrongful arrest. Indeed though we do not know all the details of the pair arrested near Gatwick it smacks of their being arrested in a round-up of convenient local drone enthusiasts rather than as a result of meaningful investigation. That the names of the pair were leaked and they became the subject of a media frenzy further shows the danger in which they were placed, as well as the irresponsibility of the reporters who covered their plight.
Perhaps Most Importantly: We Need Accurate Official Incident Reports
Whatever happens in a drone report, whether it be an arrest or an embarrassing debacle, there will inevitably be an official incident report from the Civil Aviation Authority, the regulator of British civilian airspace. This will form the official record of the event, and thus should strive to be as accurate as possible, but here the process falls short for the final time. There appears to be no evaluation step performed on the available evidence and no requirement for physical proof. So if an eyewitness reports behaviors about the drone that no drone ever built could possibly be capable of, it is solemnly recorded as fact. Our previous article on this subject highlights multiple such accounts, and this is an important point because as the official record these reports are what informs legislators. When they make laws pertaining to drones it is imperative that their decisions are based upon accurate evidence, and it is clear that this is not the case. Given that they will no doubt be reviewing drone legislation in the wake of this fiasco it is particularly important that the investigators consult people with specialist knowledge in the field, demand physical proof rather than heresay, and most importantly question accounts that stretch credibility.
It seems obvious that the multirotor hobbyist is caught in a perfect storm of incompetent authorities, deeply flawed investigations, shoddy journalism, and clueless legislators. This incident has laid bare some of the shortcomings, and it is to be hoped that a few lessons might be learned to produce less of a debacle surrounding future drone incidents. It is still a developing story so there may be a breakthrough and the whole narrative will change, and if that turns out to be the case then we hope they find the correct perpetrator this time and send them away at Her Majesty’s pleasure for a very long time. We’re guessing though that every effort will be made to push it as far under the carpet as possible to save red faces among officialdom. As multirotor enthusiasts we must keep the issue of poor investigation alive though, for if we let it be buried once more it will come back to trouble us again.
Fans of game consoles from the golden era of TV game appliances have been in for a treat over the past couple of years as a slew of official reboots of the stars of the past have reached the market. These so-called “classic” consoles closely follow the styling of the originals, but under the hood they pack modern hardware running an emulator to play a selection of games from ROM. Even better, with a bit of hacking they can run more than just the supplied emulator, people have managed to use them to emulate completely different consoles. Even then, it’s unexpected to find that a PlayStation emulator on a Super Nintendo Classic runs PlayStation games better than the same emulator built in to Sony’s own PlayStation Classic console.
The feat from [8 Bit Flashback] is achieved despite both machines having near-identical hardware specifications based upon the Allwinner R16 system-on-chip. The Nintendo provides smoother action and more responsive controls, making for a far superior gaming experience. How is this achieved? The most significant difference is that the SNES Classic had the RetroArch front end installed upon it, which may have lent some optimisations and tweaks to make the system more efficient.
Readers with an eye for unusual consoles may remember another Nintendo/Sony hybrid, the ill-fated early-1990s prototype SNES with a CD-ROM which was the first machine to bear the name “PlayStation” (or “Play Station” as it was sometimes styled, leading Sony marketeers to be hot on writers using a space between the words a few years later).