Picking a HAM radio

Now that I've decided to go further with HAM radio, I have to pick a radio. My BaoFeng BF-F8HP is usable, but hard to program and not the best radio. I've decided that I want to get a handheld (VHF/UHF) radio as well as a base station radio that does HF/VHF/UHF. The base station radios that do HF/VHF/UHF have been referred to as "shack in the box" and don't perform as well as standalone HF and VHF/UHF radios, but for starting out I'm fine with the limitations.

My criteria for picking a radio is:

• HF/VHF/UHF
• Reasonable cost
• Made by one of the big 3, Icom, Kenwood or Yaesu
• Compact as I have limited space on my desk.
• Has to do a digital mode.

With that list, it helped me narrow down the choices. I've asked a few people and I've gotten different answers on what to get. All say to check for used equipment which is a great suggestion.

In looking at the Kenwood options, they have one current radio, the TS-2000 to consider. Unfortunately it only meets two criteria and that is made by one of the big 3 and is a HF/VHF/UHF radio. Moving onto Yaesu...Yaesu's digital mode is System Fusion which seems proprietary to me (more so than D-Star and DMR though some argue that the encoder for D-Star is proprietary) which discounts all their radios. That leaves me with Icom.

I really like the looks of the Icom radios and they have one, the IC-7100 that meets my criteria. The radio was introduced in 2012, so it has been around awhile. Originally it cost about $1600 and now they are about $800 (with rebate). Looking for a used one shows that they are in a similar price range, so there is little reason to get a used one without a warranty.

Picking a radio was a lot easier than I thought even though I have very little knowledge of radios. I figure that the IC-7100 will be a decent entry level radio that won't break the bank.

If anyone has thoughts about my choice, please drop me a comment!

HAM Radio in today's world

When I was in middle school, our principal came to talk to the science club about HAM radio (yes, I was in science club). The most interesting part of his talk was when he demonstrated making a phone call via a phone patch. Since it was amateur radio, the phone call could be heard by anyone monitoring the frequency so it wasn't a replacement for the phone. However, this made an impression on me, but not enough to get licensed.

Eleven years ago I was part of CERT (and still am) and someone offered a course to become licensed as an amateur radio operator. As the FCC had dropped the requirement for morse code for the Technician license and was dropping the requirement for the higher level classes as well, passing the test was less difficult. The question bank for all the classes is published which makes it easy to study. I passed and was issued the call sign KI6FRM. I did nothing with my license until two years ago when I was laid off from work. I had nothing to do so I decided to study for the General Class license. I spent about a month reading and studying the ARRL General Class License Manual. In addition to reading the book, I used an iOS app to take practice test after practice test until I had high confidence that I could pass. I passed and still did nothing with the license. I bought a BaoFeng BF-F8HP radio which is a cheap Chinese radio and figured out how to program it with CHIRP. I listened a bit, but never pushed the transmit button.

Fast forward another year and a half. I've been searching for a hobby for awhile and as I approached my 45th birthday, I realized that I'll be "retiring" in 20 years and will have to find something to do with my time. HAM radio popped into my head and thought that I might as well try to pass the Extra Class test while my brain still worked and I could memorize the answers. I studied the ARRL Extra Class License Manual and used an iOS app by the same author as the other app (the app is functional, but not pretty). I was extremely nervous as there is a lot of material that I just couldn't wrap my head around. While a lot of the material was familiar (I have an engineering degree and studied electronics), I didn't know if I would be able to do it. My wife kept telling me that I had nothing to worry about; she was right, I passed on the first try and only missed 5 (you can miss 13 or 50 and pass)!

This time I'm determined to do something with my license. After my license came through the FCC, I decided to get a vanity call sign. The FCC dropped the fee for doing it a few years ago, so what did I have to lose? As an extra class operator, I had a lot more choices for call signs. Many people seem to like keeping their region in their call sign (California is region 6), but I just wanted something that sounded cool. My wife thinks that I'm a dork or a geek and keeps comparing HAM radio to CB by saying "breaker, breaker 1-9". I'm OK with that, so I applied for and was granted KD0RK. Yup, I'm KD0RK and proud of it.

Now that I'm licensed for all amateur frequencies, I'm trying to put together all the pieces. There is a lot of information out there and a lot of different ways to use amateur radio. I'm particularly interested in emergency communications, so I'm exploring a radio (HT) to purchase and have my eye on the Icom ID-51A Plus2. This radio is a 2m/70cm radio (VHF/UHF) and only requires a technician license. I did purchase a Diamond Original X50A Antenna to help with my radio and am waiting to try it out.

My plan after getting used to local communications (through repeaters and such) is to explore HF. This is what interests me because I'll be able to communicate without the Internet and talk to people all over the world. I read stories about HAM radio use in Puerto Rico after the hurricane and would potentially like to help out with something like that in the future. However, HF brings another aspect to the hobby that I have to learn including what antenna to get, what radio to buy, what frequencies to use, how does the weather affect propagation (yes, the manual went over this, but until it is used it is just theory), etc.

Back to the title of this article. Does HAM radio have a place in today's society? I think it definitely has a place in emergency communication when cell phones may not be available or the circuits are simply jammed. In addition, while some think that the Internet has brought people together by always being in touch, I think written communication is less personal than voice communication. People seem to have no problem bullying others in public forums, but would likely never say what they write to someone. Is that true? I have no idea, but I'm willing to give it a try. A lot of aspects of radio communications have been replaced by the Internet, so many people don't think it has a place. When the Internet comes crumbling down, what are we going to do? 😀

Scott


KD0RK

Review: UVC-G3-AF and UVC-NVR-2TB

[Updated 2/28: Added camera images]

As anyone that reads my blog can tell, I really like Ubiquiti networking gear. When I saw that they also had a video/NVR platform, I really wanted to try it. However, since I already had a working surveillance system, I couldn't justify the cost to convert. Recently my father wanted a recommendation on a surveillance system and I started looking at options. There were a few complete systems at Costco, but they all received pretty mixed to poor reviews. I could point him to Nest cameras or a similar system, but each system was cloud based with a yearly fee. In addition, the cost of the cameras was a bit on the high side. With the Costco systems, I was concerned about ease of use and security of the cameras; many of the Chinese made/designed cameras have major security flaws that keep getting exposed. Securing these systems would take a lot of work and they would likely never receive firmware upgrades.

Once I added up the cost of 4 Ubiquiti UVC-G3 Cameras and a UVC-NVR, the Ubiquiti solution didn't cost much more. The solution would have cost more, but I had a spare 8-Port UniF Switch (US-8-150W) sitting around that I gave my dad. My dad was onboard and he ordered all the components and some patch cords. We decided using 25 ft and 50 ft patch cords was easier than running structured wiring, so all we had to do was mount the cameras and string the patch cords in the attic.

I left most of the physical install to my dad and brother-in-law. Running the wires is never a straightforward task, but we got it done after a number of hours of work. We mounted the cameras so that they could be seen as I think it is a valuable deterrent.

While my dad doesn't have an equipment rack like I do, his collection of equipment keeps gettin bigger!

While the physical install was in process, I started the software setup and install. The initial setup was pretty straight forward. I hard reset the UniFi switch (it had my config on it) and adopted it. Then I set the switch to do 24V passive PoE (it is a UniFi switch) so that I didn't have to use PoE adapters. Plugging in the NVR was easy and it started up without problems.

The NVR setup wizard had me setup a Ubiquiti account for my dad and then it locally discovered the NVR (using Chrome). I probably should have read the instructions, but I didn't and had a little trouble with this. I thought that creating the Ubiquiti account would go through a process to adopt the local NVR; it really didn't and I had to connect the NVR to my dad's Ubiquiti account later.

Once I was able to access the NVR, it should have been a simple process to plug in each camera and adopt it. Unfortunately I didn't read that I had to use ubnt/ubnt as the username and password. I simply left it blank and got no where. After a few resets of the camera and a web search, I properly entered the username and password and the cameras adopted without problems.

After the software setup, I installed the iOS app, connected my Ubiquiti account (for testing I added a user for me) and was able to use the app to help adjust the cameras. The app needs work, but it is usable. As WiFi coverage on the outside of the house was spotty, the image kept freezing until I realized that I should just turn off WiFi and let the image stream over cellular.

Once we completed the install, I turned over the "keys" to my dad and let him configure the recording, motion detection, etc. I only gave him a basic overview as the software is pretty self explanatory which is great.

With the install completed, I decided to use the last camera for my own system and setup the UniFi video software on an Ubuntu virtual machine. The install was pretty straightforward and I decided to store the recordings on a Shared Folder (VMWare). I had to add the following to /etc/fstab:

    ./host:/ /mnt/hgfs fuse.vmhgfs-fuse allow_other,defaults,uid=109,gid=117 0 0

Where 109 and 117 are the uid and gid respectively of the unifi-video user. I also followed the instructions for installing a custom SSL certificate. I had some problems initially setting up the software as the UniFi Discovery Tool wouldn't locate it, but after I connected directly to it instead of using https://video.ubnt.com, I was able to get it working. Will I keep it running? I still haven't decided.

Pros

• Unified interface for camera management including being able to change white balance, contrast, etc. on each camera.
• Regular updates of the camera firmware and recording software.
• A company concerned about security.
• Free remote viewing system.
• iOS app.
• Decent video quality.
• NVR is compact.

Cons

• Remote browser viewing seems to require/prefer Chrome.
• If you don't already have a PoE switch, there is an extra cost involved. The 5 pack of cameras doesn't come with PoE injectors. The PoE injectors are unwieldy if you have more than one camera as each requires an outlet.
• Some discussion in the forums about quality of the iOS software.
• Timeline won't show multiple recordings at once.
• Timeline feature needs some work.

Now that I have my dad's whole system setup, I have to decide if it is worth replacing my 7 cameras with the UVC-G3 cameras. Since I already have a switch to power them and I'd run the software on a virtual machine, my cost is under $900. That's a lot of money to spend when I have something that already works. I would get a better interface, easier remote viewing (right now I VPN into my home network to view the cameras), better video quality (my cameras are 720p), less concern over security issues in the cameras as Ubiquiti regularly updates the firmware and the recording software, and unified management of all the cameras (if I want to change the brightness or contrast on a camera, I have to connect directly to that camera and change the setting). However, the software I use now has a better timeline feature.

I'll probably wait until something breaks before doing something; my system has been running (different hardware and software versions, but same cameras) for almost 5 years without a hiccup.

If you're shopping for an NVR/camera setup, the Ubiquiti offering is interesting, but I think it needs a little work around the timeline feature and the iOS app before I can completely recommend it. While I don't have much experience with other systems, this system takes a little technical know how as the switch has to be configured and the cameras adopted. For an installer to install this, I think it would be fine; for the average consumer I'd look elsewhere at least for now.

Cobbling Together a Home Automation System

I was introduced to home automation at a young age when my father installed an X10 system hooked to our alarm system. The basic gist of the automation was to turn on lights when we were away and to have all the lights in the house turn on if the alarm system activated. This was more than 30 years ago and was pretty simple in what he wanted to accomplish. Since then I've dabbled with the X10 Firecacker hooked to a Linux box, but really didn't get serious about home automation until about four and a half years ago when we purchased our current house. We were remodeling the house we purchased, so I used the opportunity to design an automation system and briefly wrote about it.

Many lights, several outlets, and the thermostat in our house are using the ZWave protocol. This only covers part of the automation. All of the sensors (motion, window, and door) are on a standard DSC security system hooked up with an Envisalink module. The brains of the system is a VeraEdge with several third party plugins. Out of the box, the VeraEdge won't talk to the sensors and has very basic decision making capability, so the Program Logic Event Generator plugin is needed. In addition, I put together a plugin for controlling my Russound audio distribution units that works by sending commands to a PortServer TS 4 MEI and then to the Russound's RS-232 serial ports.

This whole system worked well for several years, but I wasn't happy with the iOS app, so I created my own app a few years ago.

If this sounds like a lot of pieces and a lot of work, it has been a labor of love and an interesting hobby. Of course having a system working well isn't a lot of fun if you like tinkering! When I received my first Amazon Echo two years ago, I was intrigued by the ability to control things by voice. My Vera (at the time) had no integration with the Echo, so I turned to a third party solution called HA Bridge by BWS Systems. It required more setup, but exposed scenes and devices so that they could be controlled by the Echo. (Vera now has native Echo support, but the way it is setup creates a delay in the response so I continue to use HA Bridge.) The new Routines in the Amazon Echo like adding one for "Good night" are an excellent addition, but has me scratching my head on if I should set that kind of thing up on the Echo, use the Vera natively, or use HA Bridge.

As an Apple fan, you'll probably notice that I haven't mentioned HomeKit, yet. HomeKit has been interesting, but due to the lack of interoperable components and hackability, I've pretty much ignored it. Some enterprising developers have created Homebridge which I've also setup. Why HomeKit and Echo support? Simple, with the HomeKit app on iOS 11 and the widget, I can easily turn lights on or off right from my iPad without switching to my app and without having to yell at the Echo. In addition, this allows me to control lights with my Apple Watch. I run HA Bridge and Homebridge on a Raspberry Pi so that it can easily sit on my IoT VLAN (I separate out IoT traffic from my main network).

This automation setup has been about 5 years in the making and I'm sure I'm not completely done with it. I keep looking at ways to simplify it with different components like maybe a new hub or new switches. However, every time I start looking into it I realize that I'd lose functionality. My wife tolerates my hobby and kind of likes some of the aspects of it as she warms up to them. Changing anything would be a change for the worse.

The more time and effort I put into my automation system, the more I realize that turnkey home automation is still a pipe dream. If someone has very simple needs then maybe he or she can get away with one system. The moment you want a choice in your components or want to do something that the major companies that do automation don't want you to do, you have to either give up or cobble together a system.

Products used in my system:

Hardware

• VeraEdge - main automation hub
• DSC alarm system
• Envisalink - alarm system to network
• PortServer TS 4 MEI
• Russound audio distribution units (no longer made) with RS-232 ports
• Squeezebox audio units (no longer made)
• Raspberry Pi for running Homebridge and HA Bridge
• Amazon Echo
• iPad/iPhone/Apple Watch

Software

• Program Logic Event Generator plugin for Vera
• HA Bridge - Echo to Vera
• Homebridge - HomeKit to Vera
• VeraAutomation - iOS app for controlling Vera
• Custom Lua plugin for Vera to control audio

Feel free to ask questions about my system. I'm always open to ideas and will keep actively exploring ways to improve my life through automation!