The KrakenSDR in its metal case, with five small antennas connected to it

Open-Source Passive Radar Taken Down For Regulatory Reasons

Open-source technology brings a world that laws and regulations are not quite prepared for. As a result, every now and then, open projects need to work around governmental regulations. In today’s news, KrakenRF team has stumbled into an arms-trafficing legal roadblock for their KrakenSDR-based passive radar code, and is currently figuring it out. There’s no indication that there’s been any legal action from the USA government – the team’s being proactive, as fas as we’re told.

KrakenSDR hardware, to simplify it a lot, is five RTL-SDRs on one PCB – with plenty of work put in to do it the right way. It gets you much further than a few dongles – there’s shielded case, suitable connectors, reliable power distribution, a proper USB hub, and importantly, receiver synchronization hardware. Naturally, there’s nice things you can build with such a hefty package – one of them is passive radar, which was a prominent selling point on both KrakenSDR’s pre-launch page back in 2021, and on their crowdfunding page just a week ago. How does that work?

There’s RF emissions floating around you in the air, unless you’re at sea or in the desert. Whether it’s airplane transponders, cell towers, or a crappy switch-mode PSU, the radiowaves emitted interact with objects all around you. If you have multiple receivers with directional antennas, you can catch waves being reflected from some object, compare the wave reflected wave to the wave received from the initial source, and determine the object’s properties like location and speed. If you’d like to know more, IEEE Spectrum has covered this topic just a week ago, and the previously-deleted KrakenSDR wiki page has more details for you to learn from.

Through exposure in IEEE Spectrum, the KrakenSDR work has received plenty of attention and comments. And this is where the International Traffic in Arms Regulations (ITAR) laws come in. We’re not lawyers, but it does look like passive radar is on the list. Today, the code repository and the documentation pages are scrubbed clean while the team is talking to legal experts.

Dealing with this is intimidating, and we wish them luck in clearing this with legal. In the bad old days, certain encryption algorithms were famously in scope, which appeared absolutely ridiculous to us at the time. The laws did eventually change to better reflect reality, but the wheels of justice turn slowly.

Screenshot of the Arduino Lab for MicroPython

Arduino Brings A MicroPython IDE

Both Arduino and MicroPython are giants when it comes to the electronics education area, and each one of them represents something you can’t pass up on as an educator. Arduino offers you a broad ecosystem of cheap hardware with a beginner-friendly IDE, helped by forum posts explaining every single problem that you could and will stumble upon. MicroPython, on the other hand, offers a powerful programming environment ripe for experimentation, and doesn’t unleash a machine gun fire of triangle brackets if you try to parse JSON slightly incorrectly. They look like a match made in heaven, and today, from heaven descends the Arduino Lab for MicroPython.

This is not an Arduino IDE extension – it’s a separate Arduino IDE-shaped app that does MicroPython editing and uploads code to your board from a friendly environment. It works over a serial port, and as such, the venerable ESP8266-based boards shouldn’t be be left out – it even offers file manager capabilities! Arduino states that this is an experimental effort – it doesn’t yet have syntax checks, for instance, and no promises are made. That said, it already is a wonderful MicroPython IDE for beginner purposes, and absolutely a move in the right direction. Want to try? Download it here, there’s even a Linux build!

High-level languages let you build projects faster – perfect fit for someone getting into microcontrollers. Hopefully, what follows is a MicroPython library manager and repository! We’ve first tried out MicroPython in 2016, and it’s come a long way since then – we’ve seen quite a few beginner-friendly MicroPython intros, from a gaming handheld programming course, to a bipedal robot programming MicroPython exploration. And, of course, you can bring your C libraries with you.

The demo toot screenshot, showing a text-only message sent from the ESP32 using the library.

Moved Off Twitter? Make Your ESP32 Toot

Since Twitter was officially taken over by Elon Musk a few days ago, there’s been significant staff cuts, a stream of questionable decisions, and uncertainty about the social media platform’s future. So it’s little surprise that a notable number of people, those in the tech and hacker scenes in particular, have decided to move over to (or at least bridge their accounts with) the distributed and open source Mastodon service.

Of course, the hacks would follow closely, and [Toby] shares a simple ESP32-based Mastodon client library for us to start with. Instead of “tweets”, messages on Mastodon instances are called “toots”, in line with the platform’s mammoth-like mascot. The library, called Luyba, is able to send toots and includes a demo firmware. Built using C++ and with support for Platform.IO, it should fit into quite a few projects out there, letting you easily send toots to whichever instance you find your home, as the library-aided demo toot shows.

What could you do with such a library on your MCU? Turns out, quite a few fun things – a home automation interface, a critter trap, an online BBC Basic interpreter, or, given image support, a camera that tweets whatever it’s pointed at. There’s quite a bit of fun hackers can have given a micro-blogging service API access and a bit of code that works with it. That said, for all the good that Twitter brought us over the years, there’s a lot that Mastodon can easily do better, between easily game-able “Trending” sidebar, bias found in auto-cropping algorithms and disarrayed internal security policies.

Photo of the back of a slingbox appliance, with ports shown and arrows going to them describing what each of the ports does.

Slingbox Getting Bricked – You Have Less Than 24 Hours

The Slingbox devices used to let you catch up with the programming on your TV when you weren’t near it, using your Internet-connected mobile device. As cable TV became less popular, their business model faded away, and in 2020, they scheduled a service shutdown for November 9th, 2022. If you own a Slingbox, it’s getting bricked tomorrow – for those reading this in EU, that’ll be today, even. Do you have a Slingbox? You might still be able to repurpose it, let’s say, for local media streaming – but only if you waste no time.

[Gerry Dubois] has been developing the “Slinger” software for the past few months, a small app you run locally that proxies commands and video for your Slingbox, thanks to reverse-engineering communications with Slingbox servers. However, it needs a “hardware password” alphanumeric string, that you need to get from the Slingbox service web interface – which is to be promptly shut down. If you think you might have a use for what’s essentially a network-connected analog/digital video capture card with decent hardware, the GitHub repo has a lively discussion tab for any questions you might have.

One one hand, Slingbox shouldn’t be bricking the devices in a way that requires you act fast – perhaps, releasing a final update that makes the device hacker-friendly, like O2 did with their Joggler appliance back in the day, publishing the hardware documentation, or at least setting up a service up that lets anyone retrieve their hardware password indefinitely. On the other hand, at least they gave us two years’ notice, something less than usual – the amount of time between bricking and an announcement can even be a negative number. For those of us stuck with no operational device, a hardware exploration might be in order – for instance, we’ve torn down the Sling Adapter and even ran simple custom code on it!

Four M.2 cards of different sizes on a desk surface

M.2 For Hackers – Cards

Last time, I’ve explained everything you could want to know if you wanted to put an M.2 socket onto your board. Today, let’s build M.2 cards! There’s a myriad of M.2 sockets out there that are just asking for a special card to be inserted into it, and perhaps, it’s going to be your creation that fits.

Why Build Cards?

Laptops and other x86 mainboards often come with M.2 slots. Do you have a free B-key slot? You can put a RP2040 and bunch of sensors on a B-key PCB as an experimental platform carried safely inside your laptop. Would you like to do some more advanced FPGA experiments? Here’s a miniscule FPGA board that fits inside your laptop and lets you play with PCIe on this same laptop – the entire setup having a super low footprint. Are you looking for an extra PCIe link because you’re reusing your laptop as a home server? Again, your WiFi slot will provide you with that. Want to get some PCIe out of a SteamDeck? Building a M-key 2230 card seems to be your only hope! Continue reading “M.2 For Hackers – Cards”

PSU charging an externally connected supercapacitor bank that's powering the phone. There's a current clamp on one of the wires to measure charging current, and a multimeter measuring the charging voltage.

Just How Fast Could You Charge An IPhone?

An iPhone 8, now a relatively cheap model, can charge its battery fully in two hours’ time. There’s hardly ever a need for faster charging, but it’s fair to ask – how much faster could it really go? [Scotty Allen] from [Strange Parts], back after a hiatus, is back to stretching the limits of what a regular iPhone can do, and decides to start off with an exploration of battery technologies.

What people commonly encounter is that charging speed depends on the charger involved, but even one hundred chargers in parallel won’t speed up this iPhone’s charging rate, so what’s up? First off, the phone’s charger chip and the battery’s BMS will both limit charging current, so for experiment purposes, those had to be bypassed. First attempt was using a hefty DC power supply with the original cell, and, unsatisfied with the lack of fire and still relatively slow charging, [Scotty] decides to up the ante.
Continue reading “Just How Fast Could You Charge An IPhone?”

Screenshot from the video showing comparisons between diffused light pictures at different brightnesses and diffusers applied

LED Diffusers Confusing? Organize A Practical Contest

We all want a nice and shiny LED strip that doesn’t actually look like it consists of individual LEDs – a bar of uniform light is just that much more attractive. There’s all kinds of diffusion options available out there, but they can be confusing – sometimes you’d just like to know, which one is better? If there’s one thing that could easily settle this, it’s a practical test, and that’s what [The Hook Up] has devised for us to learn from.

First off, he talks about LED strips available – between 30, 60 and 144 LED per meter variations, the latter is going to be easier to diffuse than the former. From there, there’s a few different kinds of diffuser covers and aluminum profiles you can get, and [The Hook Up] pairs them in combinations, filming them from a distance and giving us concise visuals of how each combination works at different duty cycles, as well as making brightness measurements every now and then to evaluate losses of different diffuser layers. He proposes a simple rule – when picking a diffuser, distance between the LEDs and the diffuser has to be larger than the between-LED distance, and experiments confirm that. In the end, one of the takeaways is that the differences between 60LED/m and 144LED/m strips are not significant enough that they can’t be compensated for with a decent diffuser.

Continue reading “LED Diffusers Confusing? Organize A Practical Contest”