KiCad 2022 Year End Recap

KiCad 2022 End-of-Year Recap And 7.0 Preview

[Chris Gammell] moderated the KiCad 2022 End-of-Year Recap with several KiCad developers and librarians. They reviewed what’s been bubbling up in the nightly KiCad 6 builds, what we can expect from KiCad 7, and even answered some questions from the user community. Over the course of 2022, the KiCad project has grown both its development team and library team. The project even has a preliminary support commitment from the CERN Drawing Office!

Improvements to the KiCad Schematic Editor include smart wire dragging that simplifies moving components around within schematic diagrams. Components selected in the schematic now remain selected while switching to the PCB Editor. Internal documentation of schematics has advanced with support for fonts, embedded graphics, and the inclusion of hypertext links to datasheets and other reference materials. New features for PDF generation offer interactive files and links between sheets.

A new search panel within the KiCad PCB Editor supports finding components by footprint, net, or text search. A property panel allows common properties to be edited across multiple selected items. While a full-blown auto-router remains outside of the scope for KiCad, “push and shove” routing is faster and easier. An “attempt to finish” feature routes a quick connection for the currently selected trace, and “pack and move” positions all selected footprints into proximity to simplify placing them as neighbors within the board layout.

The KiCad PCB Editor also adds support for the use of fonts and inverted “knockout text” which even works on copper zones. Bitmap graphics can be imported and scaled beneath layout work as reference illustrations. Private footprint layers can be used to place extra documentation within footprints. The design rule checker (DRC) now can catch more layout issues, especially those that may impact manufacturability.

These are just a sampling of the impressive improvements we can expect with KiCad 7.0. There are also additions to circuit simulation and modeling features, a new command line interface for script-based automation, ARM64 support for KiCad running on Apple silicon, and a huge number of additions to the default library including symbols, footprints, and 3D Viewer models.

The KiCad team suggests several ways to support the project. There are always needs for additional developers and librarians. Financial contributions can be made at kicad.org. As users, we can run the nightly builds, try to break them, and give feedback in the form of detailed bug reports. Community testing will help make KiCad 7.0 as solid as possible. The project team is also seeking open hardware projects to include with KiCad 7.0 as demos.  For example, the StickHub project was included with KiCad 6.0 as a demo.

The official release of KiCad 7.0 is currently scheduled for January 31, 2023. While we wait, let’s flashback to our January 2022 presentation of what features made it into the KiCad 6.0 release.

Continue reading “KiCad 2022 End-of-Year Recap And 7.0 Preview”

Robot Rebellion Brings Back BBC Camera Operators

The modern TV news studio is a masterpiece of live video and CGI, as networks vie for the flashiest presentation. BBC News in London is no exception, and embraced the future in 2013 to the extent of replacing its flesh-and-blood camera operators with robotic cameras. On the face of it this made sense; it was cheaper, and newsroom cameras are most likely to record as set range of very similar shots. A decade later they’re to be retired in a victory for humans, as the corporation tires of the stream of viral fails leaving presenters scrambling to catch up.

A media story might seem slim pickings for Hackaday readers, however there’s food for thought in there for the technically minded. It seems the cameras had a set of pre-programmed maneuvers which the production teams could select for their different shots, and it was too easy for the wrong one to be enabled. There’s also a suggestion that the age of the system might have something to do with it, but this is somewhat undermined by their example which we’ve placed below being from when the cameras were only a year old.

Given that a modern TV studio is a tightly controlled space and that detecting the location of the presenter plus whether they are in shot or not should not have been out of reach in 2013, so we’re left curious as to why they haven’t taken this route. Perhaps OpenCV to detect a human, or simply detecting the audio levels on the microphones before committing to a move could do the job. Either way we welcome the camera operators back even if we never see them, though we’ll miss the viral funnies.

Continue reading “Robot Rebellion Brings Back BBC Camera Operators”

Decentralized Chaos In Germany

When you’re planning an event with 15,000 hackers in a tight space these days, the COVID logistics can take the wind right out of your sails. And so the Chaos Computer Club decided, for one more year, to put aside plans for the traditional year-end Chaos Communications Congress. In it’s place this year? Everyone is doing their own thing, together but apart, for the “Dezentrale Jahresendveranstaltungen”.

Some local clubs are putting on local events, some of them have talk streams, and it’s all happening everywhere and at once. If you’re not near one of the roughly 30 locations in Europe that are doing something live – check out the streams. But be warned, there’s a lot to process!

Maybe it’s best to start with the schedule, where you can see what’s coming up next. Live streams are going on throughout, until Dec 30. If you missed a talk, you can check out the pre-release versions on Relive, but note that start times and end times are approximate, so you might need to seek around. And once they’re edited and polished up, they’ll show up on the permanent event playlist, which is still just getting started as we write this.

Right now, we’re watching a talk in German about how to program laser shows, but yesterday there were some great talks on subjects as varied as the history of the C language, how perimeter cybersecurity is dead, how to find the Norwegian prime minister in an “anonymous” dataset, and how Hackaday friend [Dave Darko] made his LED dodecahedron that he was showing off at Supercon.

In short, there’s a lot going on. Check it out.

Non-Replaceable Battery? Not If This Proposed EU Law Passes!

A disturbing trend in consumer electronics has been a steady disappearance of replaceable batteries on our devices. Finding a mobile phone with a swapable battery is a struggle, and many other devices follow the trend by sealing in a Li-Po cell. The result is an ever-shorter life for electronics, and a greater problem with devices going to recycling or worse still, landfill. Hope is at hand though, thanks to a proposed European Union law that would if passed make batteries in appliances “designed so that consumers can easily remove and replace them themselves“.

In case any readers in the rest of the world wonder what it has to do with them, the EU represents such a huge market that manufacturers can neither ignore it, nor in most cases afford to make separate EU and rest-of-world versions of their products. Thus if the EU requires something for sale in its territories, in most cases it becomes the de facto norm for anything designed to be sold worldwide. We’ve already seen this with the EU’s right to repair legislation, and while we have not doubt that manufacturers will do their best to impede this new law we don’t think they will ultimately prevail.

Via 9to5Mac.

A Hacker’s Christmas Story

Twas the night before Christmas, and because I decided to make everyone’s presents myself this year, I’m still working like mad to get everything done before the big deadline. Why do I do this to myself? Well, partly because I enjoy the process.

My wife had this idea that we can make the older folks some fun decorative blinky things, and picked some motives. My son then drew them out on paper, and I scanned those drawings in and traced them over in CAD. We then cut the shapes out of wood on the CNC router, which turned out to be incredibly successful. (Now that I’ve done it, I wouldn’t be surprised if all of those “quirky” decorative objects that the Swedish flat-packers sell aren’t initially sketched out by third graders.)

Then my son painted them, and it’s my job to insert the twinkling. I bought some of those three-wire “fairy lights” for the purpose, and they’re really fun to hack on. They’re like WS2812s, only instead of using four pins and shifting the data downstream, they’re on a bus, each with a hard-coded address – they know where they are in the string and each LED only listens for the Nth set of 24 bits. This means sending 200 color codes just to light up the 4 LEDs in Aunt Micki’s decorative tree, but so be it.

Last stop, and still to do as of the 23rd, route out some kind of wooden battery case, wedge in the LiPo and the charging circuits, and solder on an on/off switch. It’s down to the last minute, but isn’t that always the way?

Definitely would have been easier just to order something online. But is that the spirit of giving? No! The DIY way brings the family together, gets me some quality time with the CNC machine, and tones up my FreeCAD skills. My son even looked over my shoulder as we were coding some of the LED animations. And nothing says Christmas like hand-coded blinkies.

Happy Holidays, y’all!

How To Restore A Musical Amiga

Despite the huge strides in computing power and functionality that have been achieved in the past few decades, there are still some things that older computers can do which are basically impossible on modern machines. This doesn’t just include the ability to use older hardware that’s now obsolete, either, although that is certainly a perk. In this two-part restoration of an Amiga 500, [Jeremy] shows us some of these features like the ability to directly modify the audio capabilities of this retro machine.

The restoration starts by fixing some damage and cleaning up the rest of the machine so it could be powered up for the first time in 30 years. Since it was in fairly good shape he then started on the fun part, which was working with this computer’s audio capabilities. It includes a number of amplifiers and filters in hardware that can be switched on or off, so he rebuilt these with new op-amps and added some new controls so that while he is using his MIDI software he can easily change how it sounds. He also restored the floppy disk drives and cleaned up the yellowing on the plastic parts to improve the overall appearance, as well as some other general improvements.

These old Amigas have a lot going for them, but since [Jeremy] is a musician he mostly focused on bringing back some of the musical functionality of his childhood computer, although he did build up a lot of extra features in this machine as well. These types of audio circuits are not something found in modern computers, though, so to get a similar sound without using original hardware you’ll need to build something like this NES audio processing unit programmed in Verilog.

Continue reading “How To Restore A Musical Amiga”

This Week In Security: GitHub Actions, SHA-1 Retirement, And A Self-Worming Vulnerability

It should be no surprise that running untrusted code in a GitHub Actions workflow can have unintended consequences. It’s a killer feature, to automatically run through a code test suite whenever a pull request is opened. But that pull request is run in some part of the target’s development environment, and there’s been a few clever attacks found over the years that take advantage of that. There’s now another one, what Legit Security calls Github Environment Injection, and there were some big-name organizations vulnerable to it.

The crux of the issue is the $GITHUB_ENV file, which contains environment variables to be set in the Actions environment. Individual variables get added to this file as part of the automated action, and that process needs to include some sanitization of data. Otherwise, an attacker can send an environment variable that includes a newline and completely unintended environment variable. And an unintended, arbitrary environment variable is game over for the security of the workflow. The example uses the NODE_OPTIONS variable to dump the entire environment to an accessible output. Any API keys or other secrets are revealed.

This particular attack was reported to GitHub, but there isn’t a practical way to fix it architecturally. So it’s up to individual projects to be very careful about writing untrusted data into the $GITHUB_ENV file.

Continue reading “This Week In Security: GitHub Actions, SHA-1 Retirement, And A Self-Worming Vulnerability”