Morse code qualifies as a digital mode, although organic brains are somewhat better at copying it than electronic ones. Ham radio operators that did “phone” (ham-talk for voice) started out with AM modulation. Sometime after World War II, there was widespread adoption of single side band or SSB. SSB takes up less bandwidth and is more reliable than AM modulation. On the digital side, hams turned to different and more sophisticated digital transmission types with computers pushing bandwidth down and reliability up. However, a recent trend has been to encode voice over ham radio–sort of VoIP with radio instead of Ethernet–using an open source program called freedv.
[AA6E] made a very informative video where he carries on a QSO (a conversation) with a distant station using freedv. What makes it interesting, is towards the end when the two stations switch to regular SSB. The difference is dramatic and really points out how even with less bandwidth (roughly 3 kHz for SSB vs 1.25 kHz), the digital mode is superior. The freedv software (available for Windows or Linux) compresses audio to 700-1600 bits per second and spreads it over 16 QPSK signals.
Continue reading “Hams Talk Digital”
[Simon] has been using his home alarm system for over six years now. The system originally came with a small RF remote control, but after years of use and abuse it was finally falling apart. After searching for replacement parts online, he found that his alarm system is the “old” model and remotes are no longer available for purchase. The new system had similar RF remotes, but supposedly they were not compatible. He decided to dig in and fix his remote himself.
He cracked open the remote’s case and found an 8-pin chip labeled HCS300. This chip handles all of the remote’s functions, including reading the buttons, flashing the LED, and providing encoded output to the 433MHz transmitter. The HCS300 also uses KeeLoq technology to protect the data transmission with a rolling code. [Simon] did some research online and found the thew new alarm system’s remotes also use the same KeeLoq technology. On a hunch, he went ahead and ordered two of the newer model remotes.
He tried pairing them up with his receiver but of course it couldn’t be that simple. After opening up the new remote he found that it also used the HCS300 chip. That was a good sign. The manufacturer states that each remote is programmed with a secret 64-bit manufacturer’s code. This acts as the encryption key, so [Simon] would have to somehow crack the key on his original chip and re-program the new chip with the old key. Or he could take the simpler path and swap chips.
A hot air gun made short work of the de-soldering and soon enough the chips were in place. Unfortunately, the chips have different pinouts, so [Simon] had to cut a few traces and fix them with jumper wire. With the case back together and the buttons in place, he gave it a test. It worked. Who needs to upgrade their entire alarm system when you can just hack the remote?
[Warrior_Rocker’s] family bought a fancy new sign for their beach house. The sign has the word “BEACH” spelled vertically. It originally came with blue LEDs to light up each letter. The problem was that the LEDs had a narrow beam that would blind people on the other side of the room. Also, there was no way to change the color of the LEDs, which would increase the fun factor. That’s why [Warrior] decided to upgrade the sign with multi-colored LEDs.
After removing the cardboard backing of the sign, [Warrior] removed the original LEDs by gently tapping on a stick with a hammer. He decided to use WS2811 LED pixels to replace the original LEDs. These pixel modules support multiple colors and are individually addressable. This would allow for a wide variety of colors and animations. The pixels came covered in a weatherproof resin material. [Warrior] baked the resin with a heat gun until it became brittle. He was then able to remove it entirely using some pliers and a utility knife. Finally, the pixels were held in place with some hot glue.
Rather then build a remote control from scratch, [Warrior] found a compatible RF remote under ten dollars. The LED controller was removed from its housing and soldered to the string of LEDs. It was then hot glued to a piece of cardboard and placed into the sign’s original battery compartment. Check out the video below for a demonstration. Continue reading “LED Sign Brightens Up The Beach After Dark”
It’s been said that the best defense is a good offense. When aloft and en route to deliver a harmful payload to the enemy, the best defense is to plan your approach and your exit carefully, and to interfere with their methods of detection. If they can’t find you, they can’t shoot you.
As of May 1962, the United States military was using three major classifications of radar jamming technology as described in this week’s film: the AN/ALQ-35 multiple target repeater, the AN/ALQ-55 communications link disrupter, and the AN/ALQ-41 and -51 track breakers. The most important role of these pieces of equipment is to buy time, a precious resource in all kinds of warfare.
The AN/ALQ-35 target repeater consists of a tuner, pulse generator, transmitter, and control panel working in concert to display multiple false positives on the enemy’s PPI scopes. The unit receives the incoming enemy pulse, amplifies it greatly, repeats it, and sends them back with random delays.
The AN/ALQ-55 comm disrupter operates in the 100-210MHz band. It distinguishes the threatening enemy communication bands from those of beacons and civilians, evaluates them, and jams them with a signal that’s non-continuous, which helps avoid detection.
Finally, the AN/ALQ-41 and -51 track breakers are designed to break enemy lock-on and to give false information. It provides simultaneous protection against pulse ranging, FM-CW, conical, and monopulse radar in different ways, based on each method’s angle and range.
Continue reading “Retrotechtacular: Radar Jamming”
When [b.kainka] set out to make the world’s simplest RF detector, he probably didn’t realize it would be as easy as it was. Consisting of only a handful of components and thirty eight lines of code, he was able to make an RF detector that works reasonably well.
The microcontroller running the code is an ATtiny13 on a Sparrow board. He’s using an everyday LED as a detector diode and an internal pull-up resistor in the ATtiny13 for the bias voltage. The antenna runs off the LED’s anode. To make it sensitive enough, he switches on the pull-up resistor for a tiny fraction of time. Because an LED can act like a small capacitor, this charges it to a few volts. He then switches the pullup off, and the voltage across the LED will start to discharge. If there is an RF signal present, the discharge voltage will be less than the discharge voltage with no signal present. Neat stuff.
Be sure to check out his Hackaday.io page linked at the top for full source, schematics and some videos demonstrating his project.
Continue reading “Using an LED as a Simple RF Detector”
Hackers everywhere are having a lot of fun with SDR – as is obvious from the amount of related posts here on Hackaday. And why not, the hardware is cheap and easily available. There are all kinds of software tools you can use to dig in and explore, such as SDR# , Audacity, HDSDR and so on. [illias] has been following SDR projects for a while, which piqued his interest enough for him to start playing with it. He didn’t have any real project in mind so he focused on studying the methodology and the tools available for analyzing 433MHz RF transmission. He describes the process of using MATLAB to recover the transmissions being received by the SDR
He started off by studying the existing tools available to uncover the details of the protocol. The test rig uses an Arduino UNO with the rc-switch library to transmit via a common and inexpensive 433MHz module. SDR# is used to record the transmissions and Audacity allows [illias] to visualize the resulting .wav files. But the really interesting part is where he documents the signal analysis using MATLAB.
He used the RTL-SDR package in conjunction with the Communications System Toolbox to perform spectrum analysis, noise filtering and envelope extraction. MATLAB may not be the easiest to work with, nor the cheapest, but its powerful features and the fact that it can easily read data coming from the SDR makes it an interesting tool. For the full skinny on what this SDR thing is all about, check out Why you should care about Software Defined Radio.
[Tim] was looking for a way to control his power outlets using WiFi. He looked into purchasing a WeMo but he realized that he could build something even better with more bang for his buck. He started out by purchasing a five pack of Etekcity wireless remote control outlet switches. These are kind of like the WeMo, only they aren’t controlled via WiFi. Instead, they come with an RF controller. [Tim] just needed to find a way to bridge the gap between the RF remote and WiFi.
[Tim] decided to use a Raspberry Pi as the brains of the controller. He also purchased a SMAKN 433MHz RF receiver and transmitter for communicating with the wireless outlet switches. The wiring for the modules is pretty simple. There are only four wires. There are power and ground wires for each module. Then the transmitter needs two GPIO pins while the receiver only needs one.
[Tim] began with a fresh installation of Raspbian. He then installed Wiring Pi, which gives you the ability to interface with the GPIO pins in a way that is similar to Arduino. He also installed Apache and PHP to create a web interface for switching the outlets. The last step was to write some custom software. The software included a script that allowed [Tim] to sniff out the controls of his RF remote. The correct codes are entered into the “toggle.php” file, and everything is set. All [Tim] has to do now is browse to his Pi’s web server and click a button. All of the custom code is available via git.