Mechanical Engineering Hack Chat

Join us on Wednesday, September 30 at noon Pacific for the Mechanical Engineering Hack Chat with Adam Zeloof!

Almost every non-trivial project involves some level of cross-discipline work. If you build a robot, for instance, you need to worry not just about the electronics but also the mechanical design. You need to make sure that the parts you use will be strong enough to deal with the forces that it’ll face, you have to know how much power it’ll take to move your bot, and you have to deal with a thousand details, from heat flow to frictional losses to keeping things moving with bearing and seals.

Unfortunately for many of us, the mechanical engineering aspects of a project are foreign territory. We lack the skills to properly design mechanical systems, and so resort to seat-of-the-pants decisions on materials and fasteners, or over-engineering in the extreme — the bigger the bolt, the better. Right?

Some of us, though, like Adam Zeloof, actually know a thing or two about proper mechanical engineering. Strength of materials, finite element analysis, thermodynamics — all that stuff that most of us just wing are Adam’s stock in trade. Adam brings a trained mechanical engineer’s skillset to his multi-discipline projects, like the Rotomill or his reverse-engineered ride-share scooter. And many of you will have been lucky enough to see Adam’s excellent 2019 Superconference talk on thermal design for PCBs.

Adam joins us on the Hack Chat to talk about anything and everything to do with mechanical engineering. Join us with your burning — sometimes literally — questions on how to make your designs survive the real world, where things break and air resistance can’t be ignored.

join-hack-chatOur Hack Chats are live community events in the Hackaday.io Hack Chat group messaging. This week we’ll be sitting down on Wednesday, September 30 at 12:00 PM Pacific time. If time zones baffle you as much as us, we have a handy time zone converter.

Click that speech bubble to the right, and you’ll be taken directly to the Hack Chat group on Hackaday.io. You don’t have to wait until Wednesday; join whenever you want and you can see what the community is talking about.

Continue reading “Mechanical Engineering Hack Chat”

Hackaday Links Column Banner

Hackaday Links: September 27, 2020

Hardly a week goes by without a headline screaming about some asteroid or another making a close approach to Earth; it’s only by reading the fine print that we remember what an astronomer’s definition of “close” means. Still, 2020 being what it is, it pays to stay on top of these things, and when you do the story can get really interesting. Take asteroid 2020 SO, a tiny near-Earth asteroid that was discovered just last week. In a couple of weeks, 2020 SO will be temporarily captured into Earth orbit and come with 50,000 km near the beginning of December. That’s cool and all, but what’s really interesting about this asteroid is that it may not be a rock at all. NASA scientists have reverse-engineered the complex orbit of the object and found that it was in the vicinity of Earth in late 1966. They think it may be a Centaur booster from the Surveyor 2 moon mission, launched in September 1966 in the runup to Apollo. The object will be close enough for spectral analysis of its. surface; if it’s the booster, the titanium dioxide in the white paint should show up loud and clear.

Lasers are sort of forbidden fruit for geeks — you know you can put an eye out with them, and still, when you get your hands on even a low-power laser pointer, it’s hard to resist the urge to shine it where you shouldn’t. That includes into the night sky, which as cool as it looks could be bad news for pilots, and then for you. Luckily, friend of Hackaday Seb Lee-Delisle has figured out a way for you to blast lasers into the night sky to your heart’s content. The project is called Laser Light City and takes place in Seb’s home base of Brighton int he UK on October 1. The interactive installation will have three tall buildings with three powerful lasers mounted on each; a smartphone app will let participants control the direction, shape, and color of each beam. It sounds like a load of fun, so check it out if you’re in the area.

We got an interesting story from a JR Nelis about a quick hack he came up with to help his wife stay connected. The whole post is worth a read, but the short version of the story is that his wife has dementia and is in assisted living. Her landline phone is her social lifeline, but she can’t be trusted with it, lest she makes inappropriate calls. His solution was to modify her favorite cordless phone by modifying the keypad, turning it into a receive-only phone. It’s a sad but touching story, and it may prove useful to others with loved ones in similar situations.

We pay a lot of attention to the history of the early computer scene, but we tend to concentrate on computers that were popular in North America and the UK. But the Anglo-American computers were far from the only game in town, and there’s a new effort afoot to celebrate one of the less well-known but still important pioneer computers: the Galaksija. Aside from having a cool name, the Yugoslavian Z80 computer has a great story that will be told in documentary form, as part of the crowdsourced Galaksija project. The documentary stars our own Voja Antonic, who was key to the computer’s development. In addition to the film, the project seeks to produce a replica of the Galaksija in kit form. Check out the Crowd Supply page and see if it’s something you’re willing to back.

There’s an interesting new podcast out there: the Pick, Place, Podcast. Hosted by Chris Denney and Melissa Hough, it comes out every other week and is dedicated to the electronic assembly industry. They’ve currently got eight episodes in the can ranging from pick and place assembly to parts purchasing to solder paste printing. If you want to learn a little more about PCB assembly, this could be a real asset. Of course don’t forget to make time for our own Hackaday Podcast, where editors Mike and Elliot get together to discuss the week in hardware hacking.

Twitter: It’s Not The Algorithm’s Fault. It’s Much Worse.

Maybe you heard about the anger surrounding Twitter’s automatic cropping of images. When users submit pictures that are too tall or too wide for the layout, Twitter automatically crops them to roughly a square. Instead of just picking, say, the largest square that’s closest to the center of the image, they use some “algorithm”, likely a neural network, trained to find people’s faces and make sure they’re cropped in.

The problem is that when a too-tall or too-wide image includes two or more people, and they’ve got different colored skin, the crop picks the lighter face. That’s really offensive, and something’s clearly wrong, but what?

A neural network is really just a mathematical equation, with the input variables being in these cases convolutions over the pixels in the image, and training them essentially consists in picking the values for all the coefficients. You do this by applying inputs, seeing how wrong the outputs are, and updating the coefficients to make the answer a little more right. Do this a bazillion times, with a big enough model and dataset, and you can make a machine recognize different breeds of cat.

What went wrong at Twitter? Right now it’s speculation, but my money says it lies with either the training dataset or the coefficient-update step. The problem of including people of all races in the training dataset is so blatantly obvious that we hope that’s not the problem; although getting a representative dataset is hard, it’s known to be hard, and they should be on top of that.

Which means that the issue might be coefficient fitting, and this is where math and culture collide. Imagine that your algorithm just misclassified a cat as an “airplane” or as a “lion”. You need to modify the coefficients so that they move the answer away from this result a bit, and more toward “cat”. Do you move them equally from “airplane” and “lion” or is “airplane” somehow more wrong? To capture this notion of different wrongnesses, you use a loss function that can numerically encapsulate just exactly what it is you want the network to learn, and then you take bigger or smaller steps in the right direction depending on how bad the result was.

Let that sink in for a second. You need a mathematical equation that summarizes what you want the network to learn. (But not how you want it to learn it. That’s the revolutionary quality of applied neural networks.)

Now imagine, as happened to Google, your algorithm fits “gorilla” to the image of a black person. That’s wrong, but it’s categorically differently wrong from simply fitting “airplane” to the same person. How do you write the loss function that incorporates some penalty for racially offensive results? Ideally, you would want them to never happen, so you could imagine trying to identify all possible insults and assigning those outcomes an infinitely large loss. Which is essentially what Google did — their “workaround” was to stop classifying “gorilla” entirely because the loss incurred by misclassifying a person as a gorilla was so large.

This is a fundamental problem with neural networks — they’re only as good as the data and the loss function. These days, the data has become less of a problem, but getting the loss right is a multi-level game, as these neural network trainwrecks demonstrate. And it’s not as easy as writing an equation that isn’t “racist”, whatever that would mean. The loss function is being asked to encapsulate human sensitivities, navigate around them and quantify them, and eventually weigh the slight risk of making a particularly offensive misclassification against not recognizing certain animals at all.

I’m not sure this problem is solvable, even with tremendously large datasets. (There are mathematical proofs that with infinitely large datasets the model will classify everything correctly, so you needn’t worry. But how close are we to infinity? Are asymptotic proofs relevant?)

Anyway, this problem is bigger than algorithms, or even their writers, being “racist”. It may be a fundamental problem of machine learning, and we’re definitely going to see further permutations of the Twitter fiasco in the future as machine classification is being increasingly asked to respect human dignity.

Ask Hackaday: Is Windows XP Source Code Leak A Bad Thing?

News comes overnight that the Windows XP source code has been leaked. The Verge says they have “verified the material as legitimate” and that the leak also includes Windows Server 2003 and some DOS and CE code as well. The thing is, it has now been more than six years since Microsoft dropped support for XP, does it really matter if the source code is made public?

The Poison Pill

As Erin Pinheiro pointed out in her excellent article on the Nintendo IP leak earlier this year (perhaps the best Joe Kim artwork of the year on that one, by the way), legitimate developers can’t really make use of leaked code since it opens them up to potential litigation. Microsoft has a formidable legal machine that would surely go after misuse of the code from a leak like this. Erin mentions in her article that just looking at the code is the danger zone for competitors.

Even if other software companies did look at the source code and implement their own improvements without crossing the legal line, how much is there still to gain? Surely companies with this kind of motivation would have reverse engineered the secret sauce of the long dead OS by now, right?

Spy vs. Spy

The next thing that comes to mind are the security implications. At the time of writing, statcount pegs Windows XP at a 0.82% market share which is still going to be a very large number of machines. Perhaps a better question to consider is what types of machines are still running it? I didn’t find any hard data to answer this question, however there are dedicated machines like MRIs that don’t have easy upgrade paths and still use the OS and there is an embedded version of XP that runs on point-of-sale, automated teller machines, set-top boxes, and other long-life hardware that are notorious for not being upgraded by their owners.

Continue reading “Ask Hackaday: Is Windows XP Source Code Leak A Bad Thing?”

Hackaday Podcast 086: News Overflow, Formula 1/3 Racer, Standing Up For Rubber Duckies, And Useless Machine Takes A Turn

Hackaday editors Elliot Williams and Mike Szczys peruse the world of hacks. There was so much news this week that we lead off the show with a rundown to catch you up. Yet there is still no shortage of hardware hacks, with prosthetic legs for your rubber ducky, a RC cart that channels the spirit of Formula 1, and a project that brings 80’s video conferencing hardware to Zoom. There’s phosphine gas on Venus and unlimited hacking projects inside your guitar. The week wouldn’t be complete without the joy of riffing on the most useless machine concept.

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (60 MB or so.)

Continue reading “Hackaday Podcast 086: News Overflow, Formula 1/3 Racer, Standing Up For Rubber Duckies, And Useless Machine Takes A Turn”

This Week In Security: UTorrent Vulnerable, Crowd-Sourcing Your Fail2Ban, And Cryptographers At Casinos

The uTorrent client was recently updated to fix a null pointer dereference (CVE-2020-8437), discovered by [whtaguy]. Triggering the dereference simply crashes the client — so far an actual RCE hasn’t been found. Given the nature of the null pointer dereference, it’s possible this bug is limited to denial of service. That’s extremely good, because the flaw is extremely easy to target.

BitTorrent is a clever protocol. It’s still used to distribute large files, like Linux ISOs. The concept is simple: Split a large file into small chunks. Send the chunks to a client one at a time. As each chunk is received, the client sends a copy of that chunk to the next client. As a result of this peer-to-peer (p2p) arrangement, the bandwidth available to the server is greatly multiplied. As with all other p2p arrangements, the sticking point is how to make those connections between peers, particularly when most of the world’s desktops are behind NAT routers. In practice, for two peers to share data, at least one of them has to have a port opened or forwarded to the client. This is often accomplished through Universal Plug-n-Play (UPnP) or the NAT Port Mapping Protocol (NAT-PMP). The idea of both protocols are the same; a client on an internal device can request a temporary port forward without manual intervention. Whether it’s a good idea to allow automatic port forwards is another issue for another day. Continue reading “This Week In Security: UTorrent Vulnerable, Crowd-Sourcing Your Fail2Ban, And Cryptographers At Casinos”

In Praise Of The DT830, The Phenomenal Instrument You Probably Don’t Recognise For What It Is

If we had to make a guess at the single piece of electronic bench equipment owned by the highest proportion of Hackaday readers, it would not be a budget oscilloscope from Rigol, nor would it be a popular portable soldering iron like the TS100. Instead we’re guessing that it’s a multimeter, and not even the most accomplished one.

The DT830 is a genericised Chinese-manufactured 3.5 digit digital multimeter that can be had for an astonishingly low price. Less than a decent hamburger gets you an instantly recognisable plastic case with a chunky rotary range selector switch, and maybe a socket for some kind of transistor or component tester. Make sure that there is a 9 volt battery installed, plug in the pair of test leads, and you’re in business for almost any day-to-day electrical or electronic measurement. They’ve been available in one form or another for decades and have been the subject of innumerable give-aways and loss-leader offers, so it’s a reasonsble guess that you’ll have one somewhere. I have three as far as I know, they make great on-the-go instruments and have proved themselves surprisingly reliable for what they are. Continue reading “In Praise Of The DT830, The Phenomenal Instrument You Probably Don’t Recognise For What It Is”