09:31 – It was 65.4F (18.5C) when I took Colin out around 0645 this morning, bright and sunny. When I looked a few minutes ago, we were up to 81.7F (27+C). Barbara is washing her car and doing other outside stuff this morning. This afternoon we do still more science kit stuff.
My Amazon order arrived yesterday morning, with a name-brand programming cable and a Nagoya NA-771 whip antenna for the UV-82. I plugged the cable into a USB port, connected and turned on the radio, and fired up CHIRP to program it. CHIRP didn’t see the UV-82. Ruh-Roh.
So I brought up a terminal and typed:
dmesg | grep FTDI
That returned the following, which told me the driver was installed and working.
[4329131.762676] usb 1-22.214.171.124: Manufacturer: FTDI
[4329131.765293] ftdi_sio 1-126.96.36.199:1.0: FTDI USB Serial Device converter detected
[4329131.765800] usb 1-188.8.131.52: FTDI USB Serial Device converter now attached to ttyUSB0
As it turned out, the problem was that my account wasn’t in the dialout group, so I had no access to ttyUSB0. That was easy enough to fix. I just added my account to the dialout group, logged out and back in, and everything worked as expected. CHIRP recognized that the UV-82 was connected, so I downloaded and saved a copy of the default channel programming. That was kind of weird, incidentally. It looked pretty much random.
I then attempted to upload to the radio that CHIRP template that had 99 emergency frequencies pre-defined. It blew up with ERROR in every field. Hmmmm. Now that I think about it, it did the same thing two or three years ago when I first tried to program one of my UV-82 radios. IIRC, the problem then was that that template wasn’t formatted correctly. It was in CSV format, which CHIRP expects, but there were errors in the way the fields were laid out.
So I next uploaded one of the default templates that’s supplied with the CHIRP package, which included FRS/GMRS frequencies. That one uploaded fine to the radio. When I disconnected it, turned it off and then back on, the FRS/GMRS frequencies displayed as expected. So now I need to bring up the emergency frequencies template in a text editor and figure out again what the problem is.