Monday, December 30, 2013

Saturday, December 28, 2013


Heavy overcast on the mountain....

Saturday, December 14, 2013

Friday, December 13, 2013

Remote ops with GALAXY S3

Talking to W4BXI on 60m from Hamilton Place mall in Chattanooga last night.

I used the same config to talk to the coffee club this morning from Nashville.

What a great phone and great apps!

Team viewer for remote connection
Skype for audio
FT2K homebrew app for rig control


Friday, November 29, 2013

Mentone Remote on Galaxy

The MicroRig version of my FT2K control program fits nice on the Galaxy screen.

WA5MLF Flex on his Galaxy S3

Wednesday, November 27, 2013


Captured this screen shot from WA5MLF this morning...

Friday, November 22, 2013

Test at 9:00 PM CST 11/22/2013 AT&T Tuscaloosa, AL

Tuscaloosa Speed Test

Don't you wish you lived in Tuscaloosa?   Tonight's AT&T LTE4G speed test.   Notice the upload speed is greater than the download and both are slower than my old acoustic couple! Why would anyone pay for this if they had a choice.

I can't get Verizon at the Cottage or I would be gone.

I'll run a second test as soon as I post this one.


Once again I failed to fully account for local technology. The previous picture was"cell" speed when it was connected to the Internet via the Micro Cell.

AT&T Best G4?

Yeah right!

Saturday, November 16, 2013

Wednesday, November 13, 2013

Thursday, November 7, 2013

Device Manager Windows 7

I use many virtual COM ports.  The microHAM USB Device Router managers COM4, COM5, and COM6 with no risk of conflicts.  However, when I install a serial to USB converter, many of the drivers for such devices will not "pay attention" to existing COMx ports, and as a result, assign a COMx port that has already been assigned.  The only "symptom" is the devices in conflict simply don't work.  Drilling down you will find the following dialogs.

In my case, the hardware now assigned to COM7 was initially assigned to COM5 by the driver.  Notice that COM5 was already used.  As a result, the COM5 and COM7 devices simply did not work.  

Right click on the conflicting COM point and you will reveal the Properties menu.  Clicking on Properties, will reveal the dialog shown immediately above.  Click on Advanced will reveal the dialog the second dialog which allows you to change the designated COMx port.  The dialog above shows this pull down box.  Once I selected COM7, a unique COMx, both devices worked properly.