Mysterious Files PH

Hackaday Europe is approaching, and we’re putting tickets on sale now. “But wait, you haven’t selected the talks yet!” we hear you saying. Indeed! And that’s why we discount the first round of entries for our True Believers – the hard core who know that it’s going to be a fantastic event and turn up regardless. So if you want to come to Hackaday Europe on the cheap, go snap up your ticket before they’re gone.

Call for Participation Extended

Of course, giving a talk is always the best way to attend a hacker gathering like this. And we know that we said that today was the deadline for talk submissions. But we also know that many of you have advanced degrees in procrastineering, so we’re giving you a week’s extension.

Selected speakers get in free, and we’ll reserve you an early-bird ticket for putting together a legit talk proposal either way. So if you’re a first-time presenter or a wizened pro, and you have something that you’d like to say to an audience of like-minded hackers, we’d all like to hear from you. We won’t extend the deadline twice, though, so get your proposal in before March 25.

(A few people have reached out to us, wanting to avoid the Google login that the above form requires. If you’re in the same camp, write to us directly and let us know!)

Hackaday Europe

In case you don’t know, Hackaday Europe started out as a bi-annual event that we first held a decade ago in Belgrade. It has been such a success that we’re now doing it every year, and leap-frogging around Europe to spread the love. The last two events have been in Berlin, and this is our first time in Lecco, Italy. This year, it runs the weekend of May 16th and 17th, with a pre-event on the evening of the 15th, to be announced.

What stays the same? We have a fantastic crowd who bring their passion projects with them, a fun badge to hack on, and of course food, drink, music, and merriment all along. Oh, and the talks. (You are submitting your talk, right?)

We’ll have more details coming your way in the next few weeks, so stay tuned. After March 25th, we’ll get to selecting talks, and let you all know. Get your tickets now – we can’t wait to see you all in eight-and-a-half weeks!

How often have you pulled out old MCU-based project that still works fine, but you have no idea where the original source code has gone? Having the binary image and the source code as separate things to keep track of usually isn’t a problem, but there’s something to be said for adding the source — and documentation — to this image if you have some flash to spare. This is basically what the Forgetfulino Arduino library by [Nader Al Khatib] does.

Essentially, the library compresses the source files and assigns it to be burned onto the flash alongside the binary. There is also a bit of code added to the firmware so that this code can be retrieved via the serial port at any time, negating the need for a firmware dump and manual disassembly. For ease of use, the library has an Arduino IDE extension that automates the process. The basic idea could also be adapted to different environments should anyone wish to take up the challenge.

You probably wouldn’t want debug builds to feature this additional payload as writing it to flash will eat up time and write cycles. But for a release build that will be put out in the (literal) field for a few years or even decades, it could be very convenient. After all, you never know when that Git repository that you relied on might go AWOL.

Although the term ‘Iron Curtain’ from the Cold War brings to mind something like the Berlin Wall and its forbidding No Man’s Land, there was still active trade between the Soviet Union and the West. This included devices like the M4100/4 insulation tester that the [Three-phase] YouTube channel recently looked at, after previously poking at a 1967 USSR resistance bridge.

This particular unit dates to 1985, and comes in a rather nice-looking case that somewhat looks like bakelite. It’s rated for up to 1 gigaohm, putting out 1,000 V by using the crank handle. Because of the pristine condition of the entire unit, including seals, it was decided to not look at the internals but only test its functionality.

After running through the basic usage of the insulation tester it’s hooked up to a range of testing devices, which shows that it seems to be mostly still in working condition. The first issue noticed was that the crank handle-based generator was a bit tired, so that it never quite hit the maximum voltage.

With no parallax correction and no known last calibration date, it still measured to about 10% of the actual value in some tests initially, but in later tests it was significantly off from the expected value. At this point the device was suspected of being faulty, but it defied being easily opened, so any repair will have to be put off for now. That said, it being in such good condition raises the prospect of it being an easy repair, hopefully in an upcoming video.

Continuing the restoration of the #1 Lancashire boiler at the Claymills Pumping Station in the UK, the volunteers are putting on the final touches after previously passing the boiler inspection. Although it may seem that things are basically ready to start laying down a fire after the boiler is proven to hold 120 PSI with all safeties fully operating, they first had to reassemble the surrounding brickwork, free up a seized damper shaft and give a lot of TLC to mechanisms that were brand new in the 1930s and last operated in 1971.

The damper shaft is part of the damper mechanism which controls doors that affect the burn rate, acting as a kind of throttle for the boilers. Unfortunately the shaft’s bearings had seized up completely, and no amount of heat and kinetic maintenance could loosen it up again. This forced them to pull it out and manufacture a replacement, but did provide a good look at how it’s put together. The original dial indicator was salvaged, along with some other bits that were still good.

Next was to fit the cast-iron ash boxes that sit below the boiler and from where ash can be scraped out and deposited into wheelbarrows. The automatic sprinkler stokers are fitted above these, with a good look at their mechanism. The operator is given a lot of control over how much coal is being fed into the boiler, as part of the early 20th-century automation.

The missing furnace doors on the #1 boiler were replaced with replicas based on the ones from the other boilers, and some piping around the boiler was refurbished. Even after all that work, it’ll still take a few weeks and a lot more work to fully reassemble the boiler, showing just how complex these systems are. With some luck it’ll fire right back up after fifty years of slumbering and decades of suffering the elements.

It seems that for as long as there have been readily available 3D printers, there have been moral panics about their being used to print firearms. The latest surrounds a Washington State Legislature bill, HB2320, which criminalises the printing of unregistered guns. Perhaps most controversially, it seeks so impose a requirement on printers sold in the state to phone home and check a database of known firearms and refuse to print them when asked.

This has drawn a wave of protest from the 3D printing community, and seems from where we are sitting to be a spectacularly ill-conceived piece of legislation. It’s simply not clear how it could be implemented, given the way 3D printers and slicing software actually work.

Oddly This Isn’t About Firearms

The root of the problem with this bill and others like it lies in ignorance, and a misplaced belief in the power of legislation. Firearms are just the example here, but we can think of others and we’re sure you can too. Legislators aren’t stupid, but by and large they don’t come from technology or engineering backgrounds.

Meanwhile they have voters to keep happy, and therefore when a moral panic like this one arises their priority is to be seen to be doing something about it. They dream up a technically infeasible solution, push to get it written into law, and their job is done. Let the engineers figure out how to make it work.

How To Hack Public Scrutiny When It Matters

Our governments have a mechanism in place to curtail this, public scrutiny. In short, when they embark on something stupid the public is supposed to push back. It comes as in this case from the people themselves, but perhaps most effectively it comes from the press corps which surround the legislatures.

A politician doesn’t really care much if a bunch of 3D printer enthusiasts are angry about something, but I promise you he’s all over it if it’s lead story on the local news. This should protect us, but the flaw when it come to tech stories is that the ignorance is not confined to the legislature. You don’t get to be a political press corps journalist without being pretty good at your job, but unfortunately for us, being pretty good at that job doesn’t include knowing anything about tech. Instead they have finely tuned noses for politics, public policy, and other things that are central to that beat, so when they encounter a tech story they are more likely to follow received opinion than what’s really going on.

Over the years here at Hackaday we’ve seen it time and time again, with respect to drones, right to repair, the DMCA, and even from time to time, 3D printed fiearms. We’ve even wished for technology-aware political journalists in the past too, but inevitably they don’t read Hackaday. Perhaps we should therefore examine how our community approaches stories like this in the first place, and change what we do. We’re good at complaining using our channels, perhaps it’s time to try theirs instead.

The Press Release As A Magic Bullet

There exists a tried and tested method for getting things in front of journalists, it’s called a press release. It’s a standardised form for making a point to a journalist, and when done correctly it can be very effective. How to write one is beyond the remit of Hackaday, but there are many resources online to help you. An appropriate one here is the UK Crafts Council’s one for makers. Take your concerns, distil them into a well-written and reasoned paragraph, and package it up as a press release.

Don’t send them personally, instead send them as an organisation, for example I wouldn’t write one as Jenny List. Instead I’d represent my hackerspace or my 3D printing society. As someone who’s written a few in my time as well as editing other people’s ones, I’d advise you to avoid writing either a rant or a manifesto, be factual and concise. If you appear to be a random crazy, your release will go in the round file.

When you have your press release, identify the channels where it will have the most impact. I might start with the local and regional papers and broadcasters, and find the journalists whose beat intersects with my target. The trick is writing up the technical aspects of the issue clearly enough that everyone can understand it, which is no mean feat, but it is infinitely easier when you already understand the tech than when you don’t.

This may seem like an odd departure from a 3D printing story, but perhaps like many of you I am tired of seeing badly thought out tech legislation passing without question. Perhaps it’s time our community learned some of the techniques used by the people who do mange to have influence, after all it can be easier than you think. We have the knowledge. It’s our responsibility to bring it to the people when necessary.

Assembler syntax is a touchy subject, with many a flamewar having raged over e.g. Intel vs AT&T style syntax. Thus when [Humberto Costa] recently acquired an MSX system for some fun retro-style ASM programming, he was dismayed to see that the available Z80 assemblers did not support the syntax of his favorite ASM tool, NASM. Thus was born the HC SDK project, which seeks to bring more NASM to the Z80, 8085 and a slew of other processors.

There’s both a project site and a GitHub repository, from where both source and pre-compiled releases can be obtained. Supported host platforms are macOS, Windows, OpenBSD, FreeBSD, and Linux, with currently supported targets the 8080, 8085, 8086 and Z80. Support for the 6502 is currently in progress.

The Netwide Assembler (NASM), targets only the x86 architecture, being one of the most popular assemblers for Linux and x86. It uses a variant of the Intel ASM syntax, which contrasts it strongly with the GNU Assembler (GAS) that uses AT&T syntax. Of course, in an ironic twist of fate NASM now also supports AT&T syntax and vice versa, albeit with some subtle gotchas.

Regardless, if ASM for these retro architectures is your thing, then the HC SDK may be worth checking out. [Humberto] also says that he’s looking at adding higher-level language support to make it a more complete development environment for these old systems and new takes on them.

Thanks to [Albert Wolf] for the tip.

Every ham radio shack needs a clock; ideally one with operator-friendly features like multiple time zones and more. [cburns42] found that most solutions relied too much on an internet connection for his liking, so in true hacker fashion he decided to make his own: the operator-oriented Ham Clock CYD.

The Ham Clock CYD is so named for being based on the Cheap Yellow Display (CYD), an economical ESP32-based color touchscreen LCD which provides most of the core functionality. The only extra hardware is a BME280 temperature and humidity sensor, and a battery-backed DS3231 RTC module, ensuring that accurate time is kept even when the device is otherwise powered off.

It displays a load of useful operator-oriented data on the touchscreen LCD, and even has a web-based configuration page for ease of use. While the Ham Clock is a standalone device that does not depend on internet access in order to function, it does have the ability to make the most of it if available. When it has internet access over the built-in WiFi, the display incorporates specialized amateur radio data including N0NBH solar forecasts and calculated VHF/HF band conditions alongside standard meteorological data.

The CYD, sensor, and RTC are very affordable pieces of hardware which makes this clock an extremely economical build. Check out the GitHub repository for everything you’ll need to make your own, and maybe even put your own spin on it with a custom enclosure. On the other hand, if you prefer your radio-themed clocks more on the minimalist side, this Morse code clock might be right up your alley.