The problem was brought about by a failing battery in the MacBook Pro 13″ from mid-2018, which swelled up and deformed the laptop’s case. Parts were unavailable, and the MacBook wouldn’t run at full speed without a battery fitted. That’s because with no battery present, the MacBook would send a BD_PROCHOT signal to the Intel CPU, telling it to slow down due to overheating, even when the chip was cool.
To get around the problem, [Christophe] used a tool called CPUTune. It allows fiddling with the various CPU settings of a MacBook. He deactivated the BD_PROCHOT signal, and also the CPU’s Turbo Boost feature. This ended the worst of the thermal throttling, and enabled semi-normal use of the machine.
It’s unclear why Apple would throttle the CPU with the battery disconnected. [Christophe]’s workaround got him back up and working again in the midst of a difficult period, regardless. We’ve seen some other great Macbook hacks before too, like this amazing save from serious water damage!
If you are a retrocomputer fan, you might remember when serial ports were a few hundred baud and busses ran at a few megahertz at the most. Today, of course, we have buses and fabric that can run at tremendous speeds. Quantum computing, though, has to start from scratch. One major problem is that jockeying quantum states around for any distance is difficult and slow. Part of it is that qubits decay rapidly, so you don’t have much time. They are also generally susceptible to noise and perturbation by outside forces. So many quantum machines today are limited by how much they can cram on one chip since there isn’t a good way to connect to another chip. The University of Sussex thinks it has improved the outlook for quantum interconnects with a technique they claim can move qubits around at nearly 2,500 links per second.
The technique, called UQ Connect, uses electric field links to connect multiple chips using trapped ions for qubits. If you want to read the actual paper, you can find it in Nature Communications.
If a hacker guardian angel exists, then we’re sure he or she was definitely AWOL for six long years from [Aaron Eiche]’s life as he worked on perfecting and making his Christmas Countdown clock. [Aaron] started this binary clock project in 2016, and only managed to make it work as expected in 2022 after a string of failures.
In case you’d like to check out his completed project first, then cut the chase and head over to his Github repository for his final, working version. The hardware is pretty straightforward, and not different from many similar projects that we’ve seen before. A microcontroller drives a set of LED’s to show the time remaining until Christmas Day in binary format. The LEDs show the number of days, hours, minutes and seconds until Christmas and it uses two buttons for adjustments and modes. An RTC section wasn’t included in the first version, but it appeared and disappeared along the six year journey, before finding a spot in the final version.
The value of this project doesn’t lie in the final version, but rather in the lessons other hackers, specially those still in the shallow end of the pool, can learn from [Aaron]’s mistakes. Thankfully, the clock ornament is not very expensive to build, so [Aaron] could persevere in improving it despite his annual facepalm moments.
The build relies on [Ivan]’s giant 3D-printed Lego-like assembly kit. It lets him simply bolt together a bunch of plastic girders to make the key parts of the excavator, including the base and the digger arm itself. The digger arm is controlled with linear actuators of [Ivan’s] own design, which uses servos and threaded rod to do the job. They’re not as cool as hydraulics or pneumatics, but they get the job done well. For propulsion, [Ivan] built a tracked drive system again using his unique Lego-like blocks. The tracks were tedious to assemble, but add a lot to the excavators Awesomeness Quotient (AQ).
The overall build is quite slow, and more than a little fragile. It’s not quite ready for hardcore digging tasks. In reality, it’s serving as a test bed for [Ivan]’s 3D-printed building blocks that get better every time we see them. Video after the break.
Repetitive strain injuries (RSI) can be a real pain. You’ve got a shiny new laptop, and everything’s going smoothly, but suddenly you can’t use it without agonizing (as in typing-speed reducing) pain caused by years of keyboard bashing or just plain bad posture. All of us hacker types will likely have or will experience this at some point, and luckily there are many potential solutions.
[Zihao Wang] writes to show us kseqi, another chord-like textual input method, with a focus on the input sequences, as opposed to any particular mechanical arrangement of keys. The idea is to make use of two sets of independent inputs, where the sequence of actuation codes for the keystrokes to be emitted into the application.
An example interface would be to arrange two sets of five keys as the input mechanism. One can arrange characters in a matrix. The left key is pressed and held first which selects a column (1 out of 5) then the right key is pressed to select a row, and thus a character. Next, you release in the same order, left, then right, to send the character.
Swapping left and right allows a different set of characters. In this simple scheme, fifty characters can be coded. Check out this web assembly demo for how this operates. Swapping out the physical inputs for a pair of joysticks is another option, which may be better for some folks with specific physical difficulties, or maybe because it just looks fun. As [Zihao] mentions in the write-up, the sequence order can be changed to code for other character sets, so this simple scheme can handle many more character codings than this simple example. All you have to do is remember them. Interested parties may want also wish to dig into the kseqi Rust crate for information.
Under the weather though they both were, Editor-in-Chief Elliot Williams and Staff Writer Dan Maloney got together to take a look under the covers of this week’s best and brightest hacks. It was a banner week, with a look at the changes that KiCad has in store, teaching a CNN how to play “Rock, Paper, Scissors,” and going deep into the weeds on JPEG.
We dipped a toe into history, too, with a look at one of the sexiest early hobbyist computers, seeing how citizen scientists are finding ancient burial mounds, and looking at the cryptography that cost a queen her head. Rather look to the future? We get it — which is why we talked about a greener, cleaner way of making hydrogen from methane, as well as a generatively designed five-axis 3D printer. From laser-precise knife sharpening to circuit simulation with Python to clear plastic TVs of the 1930s, there’s something for everyone!
Earlier versions of the Arduino IDE made uploading files to an ESP32’s SPIFFS filesystem easy via the ESP32FS plugin. Sadly, that’s no longer possible under the rewritten Arduino 2.0 IDE. Thankfully, [myhomethings] has stepped up to solve the problem with a new tool that also adds some new functionality.
The tool in question is the ESP32 Web Updater and SPIFFS File Manager. It features a web interface courtesy of the ESPAsyncWebServer library. Simply dialing into the ESP32’s IP address will grant one access to the interface. Once connected files can be uploaded to the ESP32, or deleted at will. Text files can be created and populated through the interface as well, and the SPIFFS file system can also be formatted if required. Plus, as a bonus, the interface allows for handy over-the-air firmware updates. One need only export a compiled binary from the Arduino IDE, and then load the resulting *.bin file into the ESP32 via the web interface. It does come with the caveat that if new firmware is uploaded that doesn’t include the ESP32 Web Updater itself, there will be no way to do further firmware updates in this manner.