Who can resist the insane deals on bizarre hardware that pop up on auction websites? Not [Dane Kouttron], for sure. He stumbled on Armor X7 ruggedized tablets, and had to buy a few. They’d be just perfect for datalogging in remote and/or hostile locations, if only they had better batteries and were outfitted with a GSM data modem… So [Dane] hauled out his screwdrivers and took stuff apart. What follows is a very detailed writeup of the battery management system (BMS), and a complete teardown of this interesting tablet almost as an afterthought.
First, [Dane] tried to just put a bunch more batteries into the thing, but the battery-management chip wouldn’t recognize them. For some inexplicable reason, [Dane] had the programmer for the BMS on-hand, as well as a Windows XP machine to run the antiquated software on. With the BMS firmware updated (and the manufacturer’s name changed to Dan-ger 300!) everything was good again.
Now you may not happen to have a bunch of surplus X7 ruggedized tablets lying around. Neither do we. But we can totally imagine needing to overhaul a battery system, and so it’s nice to have a peek behind the scenes in the BMS. File that away in your memory banks for when you need it. And if you need even more power, check out this writeup of reverse-engineering a Leaf battery pack. Power to the people!
Electricity comes in two basic forms: Alternating Current (AC) and Direct Current (DC). DC is handy to use and is easy to analyze. However, AC has some useful properties too. In particular, AC current can operate a transformer which can step it up or down easily. Power is conserved, of course (well, actually, you get less power because of losses in the transformer).
You can’t do that trick with pure DC. You can reduce a voltage, although that typically wastes power in heat (for example, a voltage divider or linear regulator). You can’t readily increase a DC voltage unless you convert it into some sort of AC first.
This was a particularly bad problem in the era of tubes–especially tubes in car radios. The car’s voltage was probably 12V but the tube’s plates might take hundreds of volts. What do you do? Some old car radios used what is called a dynamotor. This is just a motor and a generator in one box. You could spin the motor with 12V and have the generator produce a different voltage (even a DC voltage).
In a clever bit of miniaturization, [JediJeremy] has nearly completed a gyro-mouse controller for a Raspberry Pi Zero! Ultimately this will be a wearable Linux-watch but along the way he had some fun with the interface.
Using the MPU6040 gyroscope/accelerometer card from a quadcopter, [JediJeremy] spent a week writing the driver to allow it to function as a mouse. Strapping an Adafruit 1.5″ PAL/NTSC LCD screen and its driver board to the Zero with rubber bands makes this one of the smallest functional computer and screen combos we’ve seen. Simply tilt the whole thing about to direct the cursor.
It presently lacks any keyboard input, and [JediJeremy] has only added a single button for clicking, but look at this thing! It’s so tiny! In his own words: “I think this is the first computer that I can accidentally spill into my coffee, rather than vice versa.”
There is no CPU that is better understood than the 6502 and its cousins the 6510, 6507, 6509, and whatever we’re calling the CPU in the NES. With this vast amount of documentation, just about anything can be done. Want a discrete and un-discreet 6502? Sure thing. It’s the NMOS version, though. Want an emulated version. Sure. With libraries porting the 6502 to every platform ever, there’s only one place left to go: putting a 6502 in a Commodore 64. Make it dual-core, too, so we can run CP/M.
This build is based on one of [telmomoya]’s earlier builds – a soft-core 6510 running on an ARM Cortex M3. The inspiration for this build came from a 6502 emulator running on an Arduino, which got [telmomoya] wondering what would happen if he attached some external RAM, CIA or a SID. Doing this on an Arduino is hard, but there are a few 5 Volt tolerant ARM chips out there, and with a few banks of SRAM, [tel] quickly had an emulated 6502 running EhBasic.
Running an emulated 6502 on an ARM chip is nothing new. What makes this build spectacular is the adaptation to the C64 motherboard. Since [telmomoya] was already breaking out the data and address lines to go to the SRAMs, it didn’t take much extra work to simply build an adapter for the DIP40 CPU socket on a C64. A few 74-series logic chips made the interface easy, and after a bit of soldering, [telmomoya] had a Commodore 64 powered by an ARM chip.
If you’re emulating one chip, you can emulate two, and with the Commodore 64, this leads to a few interesting possibilities. The C64 had a CP/M cartridge — a cartridge that contained a Z80 CPU, sharing the data and address bus with the 6510. This cartridge allowed the ‘toy computer’ C64 to run the ‘business’ CP/M operating system (and the Z80 made the Commodore 128 much cooler). Since [telmomoya] was already emulating a CPU, emulating a second CPU wasn’t really that hard.
It’s a phenomenal build, and great if you’ve ever wanted to speed up VisiCalc.
What happens when you break a tap or a bolt in a component whose price tag sits in the tens of thousands. Just drilling it out and throwing in a nut insert stops being acceptable. Is there a way to remove the tap without damaging the master part at all?
Broken tap stuck in the hole it was threading
Well, that’s where [Tom Grafton] of Jerry’s Broken Drill and Tap comes in. He’s here to remove taps and chew bubblegum, and he’s definitely chewing bubble gum loudly the whole time. His primary work horse is a Metal Disintegration Machine.
A MDM is basically half of a typical wire EDM set-up. In EDM you used an electrode to punch a hole through the material. Then you thread a wire through the hole, thread it through a sometimes startling array of pulleys, and get going.
[Tom] used the MDM with an appropriately sized electrode to precisely disintegrate the middle of the tap out. After that it’s some careful work with a specially machined magnetic chisel. A quick chase of the threads with a tap and it’s back to the customer.
As you can see in the video after the break, the end result is a threaded hole that’s so indistinguishable from the rest he has to mark which one it was; presumably so the customer doesn’t forget why they’re paying him.
A few years ago, [Artem] learned about ways to focus sound in an issue of Popular Mechanics. If sound can be focused, he reasoned, it could be focused onto a plane of microphones. Get enough microphones, and you have a ‘sound camera’, with each microphone a single pixel.
Movies and TV shows about comic books are now the height of culture, so a device using an array of microphones to produce an image isn’t an interesting demonstration of FFT, signal processing, and high-speed electronic design. It’s a Daredevil camera, and it’s one of the greatest builds we’ve ever seen.
[Artem]’s build log isn’t a step-by-step process on how to make a sound camera. Instead, he went through the entire process of building this array of microphones, and like all amazing builds the first step never works. The first prototype was based on a flatbed scanner camera, simply a flatbed scanner in a lightproof box with a pinhole. The idea was, by scanning a microphone back and forth, using the pinhole as a ‘lens’, [Artem] could detect where a sound was coming from. He pulled out his scanner, a signal generator, and ran the experiment. It didn’t work. The box was not soundproof, the inner chamber should have been anechoic, and even if it worked, this camera would only be able to produce an image or two a minute.
8×8 microphone array (mics on opposite side) connected to Altera FPGA at the center
The idea sat in the shelf of [Artem]’s mind for a while, and along the way he learned about FFT and how the gigantic Duga over the horizon radar actually worked. Math was the answer, and by using FFT to transform a microphones signals from up-and-down to buckets of frequency and intensity, he could build this camera.
That was the theory, anyway. Practicality has a way of getting in the way, and to build this gigantic sound camera he would need dozens of microphones, dozens of amplifiers, and a controller with enough analog pins, DACs, and processing power to make sense of all of this.
This complexity collapsed when [Artem] realized there was an off-the-shelf part that was a perfect microphone camera pixel. MEMS microphones, like the kind found in smartphones, take analog sound and turn it into a digital signal. Feed this into a fast enough microcontroller, and you can perform FFT on the signal and repeat the same process on the next pixel. This was the answer, and the only thing left to do was to build a board with an array of microphones.
[Artem]’s camera microphone is constructed out of several modules, each of them consisting of an 8×8 array of MEMS microphones, controlled via FPGA. These individual modules can be chained together, and the ‘big build’ is a 32×32 array. After a few problems with manufacturing, the board actually worked. He was recording 64 channels of audio from a single panel. Turning on the FFT visualization and pointing it at a speaker revealed that yes, he had indeed made a sound camera.
The result is a terribly crude movie with blobs of color, but that’s the reality of a camera that only has 32×32 resolution. Right now the sound camera works, the images are crude, and [Artem] has a few ideas of where to go next. A cheap PC is fast enough to record and process all the data, but now it’s an issue of bandwidth; 30 sounds per second is a total of 64 Mbps of data. That’s doable, but it would need another FPGA implementation.
Is this sonic vision? Yes, technically the board works. No, in that the project is stalled, and it’s expensive by any electronic hobbyist standards. Still, it’s one of the best to grace our front page.
[jamesone111] bought a Transcend WifiSD card, presumably for photography, but it may just have been because he heard that they’re actually tiny Linux servers.
He read a post about these cards on the OpenWRT forums. They’re all a similar configuration of a relatively large amount of memory (compared to the usual embedded computer), a WiFi chip, and an ARM processor running a tiny Linux install. The card acts as a WiFi access point with a little server running on it, and waits for the user to connect to it via a website. It also has a mode where it will connect to up to three access points specified by the user, but it doesn’t actually have a way to tell the user what its IP address is; which is kind of funny.
[jamesone111] hacked around with the Transcend card for a bit. He found it pretty insecure, which as long as you’re not a naked celebrity, shouldn’t be a huge issue. For the hacker this is great as it opens up the chance of hacking the firmware for other uses.
Some have already pulled off some cool hacks with these cards. For example, [peterburk] hacked a similar card by PQI to turn his iPod into a portable file server.