A Daring Search For Answers In Soyuz Mystery

If you happened to tune into NASA TV on December 11th, you’d have been treated to a sight perhaps best described as “unprecedented”: Russian cosmonauts roughly cutting away the thermal insulation of a docked Soyuz spacecraft with a knife and makeshift pair of shears. Working in a cloud of material ripped loose during the highly unusual procedure, cosmonauts Oleg Kononenko and Sergey Prokopyev were effectively carving out their own unique place in space history. Their mission was to investigate the external side of the suspicious hole in the Soyuz MS-09 capsule which caused a loss of air pressure on the International Space Station earlier in the year.

That astronauts don’t generally climb out the hatch and use a knife to hack away at the outside of their spacecraft probably goes without saying. Such an event has never happened before, and while nobody can predict the future, odds are it’s not something we’re likely to see again. Keep in mind that this wasn’t some test capsule or a derelict, but a vehicle slated to return three human occupants to Earth in a matter of days. Cutting open a spacecraft in which human lives will shortly be entrusted is not a risk taken likely, and shows how truly desperate the Russian space agency Roscosmos is to find out just who or what put a hole in the side of one of their spacecraft.

Close inspection from the inside of the spacecraft confirmed the hole wasn’t made by an impact with a micrometeorite or tiny piece of space junk as was originally assumed. It appears to have been made with a drill, which really only allows for two possible scenarios: intentional sabotage or a mistake and subsequent cover-up. In either event, a truly heinous crime has been committed and those responsible must be found. As luck would have it the slow leak of air pressure was detected early and the hole was patched before any damage was done, but what if it hadn’t?

Continue reading “A Daring Search For Answers In Soyuz Mystery”

Ooops, Did We Just Close An Airport Over A UFO Sighting?

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].
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)
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]
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 ]
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.

IPv6 Christmas Display Uses 75 Internet’s Worth Of Addresses

We’ve seen internet-enabled holiday displays before, and we know IPv6 offers much more space than the older IPv4 addressing scheme that most of us still use today, but the two have never been more spectacularly demonstrated than at jinglepings.com. The live video stream shows an Internet-connected Christmas tree and an LED display wall that you can control by sending IPv6 ICMP echo request messages, more commonly known as pings.

Reading the page, you quickly parse the fact that there are three ways to control the tree. First, you can type a message in the box and press send – this message gets displayed on the crawl at the bottom of the LED screen.  Second, you can light up the tree by sending a ping to the IPv6 address 2001:4c08:2028:2019::RR:GG:BB, where RR, GG, and BB are 8-bit hex values for red, green, and blue. This is a neat abuse of the IPv6 address space, in that the tree has 224 (around 16.8 million) IPv6 addresses, one for each color you can set. We were impressed by this brute-force use of address space, at least until we read on a little further.

You can also make your own drawings on the LED wall, again by sending pings. In this case, the address to set a pixel to a particular color is: 2001:4c08:2028:X:Y:RR:GG:BB, where X and Y are the pixel coordinates. This seems easy enough: to set pixel (10, 11) to magenta, the RGB value (0xFF, 0x00, 0xFF), you’d simply ping the IPv6 address 2001:4c08:2028:10:11:FF:00:FF. Having  an array of addressable LEDs is commonplace in hacker circles today, although each of them having their own live IPv6 address on the Internet seems a little excessive at first. Then it hits you – each LED has an IPv6 address for every possible color, just like the tree: 16.8 million addresses for each LED. The LED display is 160×120 pixels in size, so the total number of IPv6 addresses used is 160x120x224, which is 75 times larger than all possible IPv4 addresses!  This is a hack of monstrous proportions, and we love it.

In case you’re not running IPv6 yet, we’ve got you covered. To send individual pings using your browser, you can use a site like Ipv6now. If you want to send pixels to the display wall, you’re better off using a 6in4 tunnel that lets you access IPv6 sites using your current IPv4 connectivity.  Hurricane Electric offers a free 6in4 tunnel service that we’ve found useful. Then it’s just a matter of writing some code to send pixel values as pings.  The python scapy module is perfect for this sort of thing. But, first you’ll have to fill out the form on jinglepings.com and wait to get your IPv6 address whitelisted before you can draw on the display; evidently the usual bad actors have found the site and started drawing inappropriate things.

If you think this use of addresses seems wasteful, you needn’t worry. There are around 3.4×1038 IPv6 addresses, enough for 1027 such displays. We’re going to go out on a limb here and say it: nobody will ever need more than 2128 IP addresses.

If you’re looking to build an LED holiday display on a smaller budget, check out this one that re-purposes normal LED strings.

Thanks to [Ward] for the tip!

Nintendo Does Sony, Better Than Sony

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).

Continue reading “Nintendo Does Sony, Better Than Sony”

Weather Forecasting Clock Makes An Almighty Racket

The old-fashioned alarm clock was a staple of cartoons in years past, with loud clanging bells and slap-to-shutoff functionality. Despite being an excellent dramatic device, these classic timepieces began to lose favor to the digital clock radio, and, in more recent times, the smartphone alarm. However, [LenkaDesign] has come up with this excellent build that combines the best of the old and the new.

The build starts with an old alarm clock. The clockwork internals are removed, but the bells remain, powered instead by a brushed DC motor. An Arduino Nano is the brains of the operation, interfacing with the now-ubiquitous temperature, humidity and barometric pressure sensors. Time is displayed on a Nokia 5110 LCD screen of the type popular a decade ago when options for small hobby project displays were significantly more limited then they are today.

As a nice touch, an old circuit board lends a new face to this clock, with a trio of big chunky buttons to act as controls. The LCD uses attractive icons to help convey information, making the most of the graphical capabilities available. There’s even a rudimentary weather forecasting algorithm that uses barometric pressure changes to predict the likelihood of rain.

Overall, it’s a tidy build that promises to serve as a great alarm clock, given the high volume of the original bells. Alarm clocks have always been a hacker staple, but if you’re still struggling to get out of bed this fire bell build should rattle your fillings loose on a daily basis. Video after the break.

[Thanks to Baldpower for the tip!]

Continue reading “Weather Forecasting Clock Makes An Almighty Racket”

Rise Of The Unionized Robots

For the first time, a robot has been unionized. This shouldn’t be too surprising as a European Union resolution has already recommended creating a legal status for robots for purposes of liability and a robot has already been made a citizen of one country. Naturally, these have been done either to stimulate discussion before reality catches up or as publicity stunts.

Dum-E spraying Tony StarkWhat would reality have to look like before a robot should be given legal status similar to that of a human? For that, we can look to fiction.

Tony Stark, the fictional lead character in the Iron Man movies, has a robot called Dum-E which is little more than an industrial robot arm. However, Stark interacts with it using natural language and it clearly has feelings which it demonstrates from its posture and sounds of sadness when Stark scolds it after needlessly sprays Stark using a fire extinguisher. In one movie Dum-E saves Stark’s life while making sounds of compassion. And when Stark makes Dum-E wear a dunce cap for some unexplained transgression, Dum-E appears to get even by shooting something at Stark. So while Dum-E is a robot assistant capable of responding to natural language, something we’re sure Hackaday readers would love to have in our workshops, it also has emotions and acts on its own volition.

Here’s an exercise to try to find the boundary between a tool and a robot deserving of personhood.

Continue reading “Rise Of The Unionized Robots”

Rigol MSO5000 Hacked, Features Unlocked

Rigol’s test gear has something of a history of being hacked. Years ago the DS1022C oscillocope was hacked to increase bandwidth, and more recently the DS1054Z was hacked to unlock licensed features. Now, it’s the MSO5000’s turn.

Over on the EEVBlog forums a group has been working on hacking another Rigol, the MSO5000, a 70 MHz oscilloscope which can be upgraded to 350 MHz via software licensing. Various other features including a two channel, 25 MHz arbitrary waveform generator are also built-in, but locked out unless a license key is purchased. The group have managed to enable all the locked options without license keys.

The hack is quite simple. The Linux system running on the scope has a default root password of, you guessed it, “root”. After logging in over SSH with these credentials, the user just needs to modify the startup file to add the “-fullopt” flag to the “appEntry” application. This starts the application in a fully unlocked state, which gives access to all the features.

The MSO5000 costs about $1000, and the bandwidth option alone adds over $3000 to the price. If you’re willing to risk your warranty, and you have the skills to edit a file with vi, this hack provides a serious upgrade for free.

If you have a DS1022C you’ll find our reporting on its hack here, and likewise DS1054Z owners will find theirs here.

Header image: EEVBlog.