Google Earth an aid to DX’ing

November 3, 2009

The more I use Google Earth, the more uses I find for it relating to DXing.  Case in point- I’ve been looking at some vacant land behind the house with the anticipation of laying out a pair of BOGs (beverage on ground antennas).  Google Earth’s satellite view allows me to visualize the antenna layout (to work around obstacles, etc.) and provides a tool to measure length and heading.  With this information, I can figure out exactly how long of an antenna I can layout and the true direction it will “aiming”.  Knowing the antenna heading, I can then extend a theoretical path from my QTH along this heading to see where the end results are, and tweak as needed for the intended target stations.

I’ve also been using Google Earth to create a DX map of stations received here as a better way for me to visualize what I’ve been logging (in addition to spreadsheet logging).  From Google Earth, this data can easily be exported as a KMZ file and brought into Google Maps to share with the public.  Here is how my DX map is looking (still populating fields, but you get the idea), QTH is West Michigan, blue placemarks are night catches, yellow are afternoon catches, and red are some LW beacons logged:


View Larger Map

Clicking on the colored placemarks will popup more information about the logging including station call letters, frequency, time of logging, etc.


DXing the ’80s

October 3, 2009

I just started DXing again this year after being out of the hobby since about 1990.  I was active during my teenage years in the 1980s and was affiliated with such radio clubs as IRCA and the ACE.  I was primarily interested in shortwave pirate radio DXing, mediumwave DXing, and shortwave utility monitoring.  My equipment was modest and included various old tube “boat anchors” that usually gave poor results but kept the room warm on winter nights.  Antennas used were nothing more than a long wire strung through some tree branches outside.  At some point I got a little more serious and saved enough money to buy a General Electric #7-2990A “World Monitor”.  Finally – a receiver with a digital frequency counter!  Never mind the fact that the VFO drifted like a log down a river – I could finally “see” what frequency I was on with some degree of accuracy!

Microlog_SWL_1986The next major purchase was a Microlog “SWL” cartridge for my Commodore 64 computer.  The “SWL” allowed digital mode reception to be captured and decoded using the C64 allowing clear text viewing and printing of non-encrypted RTTY, CW, etc.  In 1986, this was indeed high tech stuff, or at least it seemed like it to me!

Electronic messages with other DXers occurred through computer bulletin board systems and many long distance telephone charges to Kansas City’s ANARC BBS.  Cassette tapes of recorded DX receptions were happily traded with other DXers across the country and from overseas..  I have numerous air checks of shortwave pirates, numbers stations, and other curiosities that I’m slowly migrating to MP3.  The same goes for my humble collection of ’80s pirate QSL cards which I’m beginning to digitize.

By about 1990 I left the hobby and moved on to other things, but the DX bug has struck again twenty years later, and here I am writing about it.  I have a lot good memories “DXing the ’80s” and I’ll be revisiting them here from time to time while learning how the hobby has changed since then.  This thing called IBOC sounds very evil…

1986 WRNO QSL

1986 WRNO QSL


Diskless frontend on a Dell Inspiron 8200

October 3, 2009

One reason that I chose MythTV early on was for its ability to interface with other “satellite” frontend machines that I could place around the house in various locations where I have already installed hardwired Ethernet jacks.  Unless I wish to stream demanding high definition content, the frontend machines do not need to be equipped with expensive or modern hardware.

Here’s a case in point example.  I’ve had an old Dell Inspiron 8200 kicking around for a while that has a bad IDE controller.  It refuses to boot from the hard disk or the optical drive.  By most consequences, this machine is pretty much useless as is.  Enter PXE booting.  A BIOS setting in the 8200 allows for network booting.

I have experimented with linux and network booting in the past and have had joy using Diskless Remote Boot in Linux (DRBL) to network boot a DSL iso file from my Linux server to other computers around the house.  NFSRoot is a popular alternative and requires a dedicated box running a DHCP & TFTP servers and PXELINUX to boot a root filesystem over NFS.  My experience with this method has been frustrating and I never did get it working correctly using Debian.

I thought I would give it another shot and attempt to create a diskless frontend using the Inspiron.  I skipped all the manual configuration and opted to use a script available with the Knoppmyth distro to create a diskless frontend.  Basically the script sets up and configures the DHCP and TFTP servers on the myth backend and does all the hard work.  The Knoppmyth wiki has a good entry on how to get this going:

http://www.knoppmythwiki.org/index.php?page=DisklessFrontend

One thing that must be considered is that your frontend hardware will most likely be different from the backend hardware where the script was executed.  In my situation, from the backend, I had to reconfigure /nfsroot/dell8200/etc/X11/xorg.conf to get it play nicely with the Inspiron.  After a lot of googling and trial and error, I came up with a working xorg.conf that was compatible with the Inspiron’s 1600×1200 display.  Once changed, I had a diskless frontend working on the Inspiron with recorded programs available and live TV from the Motorola 6200 cable box.

Below is my xorg.conf for the Dell Inspiron 8200.  Note that I haven’t been successful getting an updated Nvidia driver installed for the older Nvidia graphics in the 8200.  One other issue involves navigating menus on the frontend.  When cycling through the menu using the arrow keys on the keyboard, it seems that two button clicks are being registered causing the menu to skip ahead one extra level – an annoying issue.  More time needed but it’s a good start…

# File generated by xorgconfig.

#

# Copyright 2004 The X.Org Foundation

#

# Permission is hereby granted, free of charge, to any person obtaining a

# copy of this software and associated documentation files (the “Software”),

# to deal in the Software without restriction, including without limitation

# the rights to use, copy, modify, merge, publish, distribute, sublicense,

# and/or sell copies of the Software, and to permit persons to whom the

# Software is furnished to do so, subject to the following conditions:

#

# The above copyright notice and this permission notice shall be included in

# all copies or substantial portions of the Software.

#

# THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR

# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,

# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL

# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,

# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF

# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE

# SOFTWARE.

#

# Except as contained in this notice, the name of The X.Org Foundation shall

# not be used in advertising or otherwise to promote the sale, use or other

# dealings in this Software without prior written authorization from

# The X.Org Foundation.

#

# **********************************************************************

# Refer to the xorg.conf(5x) man page for details about the format of

# this file.

# **********************************************************************

# **********************************************************************

# Module section — this  section  is used to specify

# which dynamically loadable modules to load.

# **********************************************************************

#

Section “Module”

# Alps Touchpad

#    Load   “synaptics”

# This loads the DBE extension module.

Load        “dbe”  # Double buffer extension

# This loads the miscellaneous extensions module, and disables

# initialisation of the XFree86-DGA extension within that module.

SubSection  “extmod”

Option    “omit xfree86-dga”   # don’t initialise the DGA extension

EndSubSection

# This loads the font modules

#    Load        “type1″

Load        “speedo”

Load        “freetype”

#    Load        “xtt”

# This loads the GLX module

Load       “glx”

# This loads the DRI module

#    Load       “dri”

EndSection

# **********************************************************************

# Files section.  This allows default font and rgb paths to be set

# **********************************************************************

Section “Files”

# The location of the RGB database.  Note, this is the name of the

# file minus the extension (like “.txt” or “.db”).  There is normally

# no need to change the default.

RgbPath “/usr/X11R6/lib/X11/rgb”

# Multiple FontPath entries are allowed (which are concatenated together),

# as well as specifying multiple comma-separated entries in one FontPath

# command (or a combination of both methods)

#

#

FontPath   “/usr/share/fonts/misc/”

FontPath   “/usr/share/fonts/TTF/”

FontPath   “/usr/share/fonts/Type1/”

#    FontPath   “/usr/share/fonts/CID/”

FontPath   “/usr/share/fonts/75dpi/”

FontPath   “/usr/share/fonts/100dpi/”

FontPath   “/usr/share/fonts/local/”

#    FontPath   “/usr/share/fonts/Speedo/”

#    FontPath   “/usr/share/fonts/TrueType/”

#    FontPath   “/usr/share/fonts/freefont/”

# The module search path.  The default path is shown here.

#    ModulePath “/usr/X11R6/lib/modules”

EndSection

# **********************************************************************

# Input devices

# **********************************************************************

# **********************************************************************

# Core keyboard’s InputDevice section

# **********************************************************************

Section “InputDevice”

Identifier    “Keyboard1″

Driver  “kbd”

Option “AutoRepeat” “500 30″

Option “XkbRules”   “xorg”

Option “XkbModel”   “pc101″

Option “XkbLayout”  “us”

EndSection

# **********************************************************************

# Core Pointer’s InputDevice section

# **********************************************************************

Section “InputDevice”

Driver            “mouse”

Identifier  “USB-Mouse”

Option            “Device”    “/dev/input/mice”

Option            “Emulate3Buttons” “true”

Option            “ZAxisMapping”    “4 5″

EndSection

#Section “InputDevice”

#  Driver  “synaptics”

#  Identifier     “Alps”

#  Option   “Device”          “/dev/psaux”

#  Option   “Protocol”        “auto-dev”

#  Option   “LeftEdge”        “120″

#  Option   “RightEdge”       “830″

#  Option   “TopEdge”         “120″

#  Option   “BottomEdge”            “650″

#  Option   “FingerLow”       “14″

#  Option   “FingerHigh”            “15″

#  Option   “MaxTapTime”            “180″

#  Option   “MaxTapMove”            “110″

#  Option   “EmulateMidButtonTime”  “75″

#  Option   “VertScrollDelta” “20″

#  Option   “HorizScrollDelta”      “20″

#  Option   “MinSpeed”        “0.4″

#  Option   “MaxSpeed”        “0.8″

#  Option   “AccelFactor”           “0.02″

#  Option   “EdgeMotionMinSpeed”    “15″

#  Option   “EdgeMotionMaxSpeed”    “15″

#  Option   “UpDownScrolling” “1″

#  Option   “CircularScrolling”     “1″

#  Option   “CircScrollDelta” “0.1″

#  Option   “CircScrollTrigger”     “2″

#EndSection

#######################This is old touchpad

#Section “InputDevice”

#    Identifier   “Mouse1″

#    Driver “mouse”

#    Option “Protocol”    “GlidePointPS/2″

#    Option “Device”      “/dev/input/mouse0″

#    Option “Emulate3Buttons”

#EndSection

# **********************************************************************

# Monitor section

# **********************************************************************

# Any number of monitor sections may be present

Section “Monitor”

Identifier  “Monitor0″

# HorizSync is in kHz unless units are specified.

# HorizSync may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR’S

# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync   31.5 – 90.0

#    HorizSync    30-64         # multisync

#    HorizSync    31.5, 35.2    # multiple fixed sync frequencies

#    HorizSync    15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.

# VertRefresh may be a comma separated list of discrete values, or a

# comma separated list of ranges of values.

# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR’S

# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 59.0 – 85.0

EndSection

# **********************************************************************

# Graphics device section

# **********************************************************************

# Device configured by xorgconfig:

Section “Device”

Identifier  “Card0″

Driver      “nv”

# unsupported card

#VideoRam    65536

# Insert Clocks lines here if appropriate

EndSection

# **********************************************************************

# Screen sections

# **********************************************************************

# Any number of screen sections may be present.  Each describes

# the configuration of a single screen.  A single specific screen section

# may be specified from the X server command line with the “-screen”

# option.

Section “Screen”

Identifier  “Screen 1″

Device      “Card0″

Monitor     “Monitor0″

DefaultDepth 24

Subsection “Display”

Depth       8

Modes       “1600×1200″ “1280×1024″ “1024×768″ “800×600″

“640×480″

ViewPort    0 0

EndSubsection

Subsection “Display”

Depth       16

Modes       “1600×1200″ “1280×1024″ “1024×768″ “800×600″ “640×480″

ViewPort    0 0

EndSubsection

Subsection “Display”

Depth       24

Modes       “1280×1024″ “1024×768″ “800×600″ “640×480″

ViewPort    0 0

EndSubsection

EndSection

# **********************************************************************

# ServerLayout sections.

# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes

# the way multiple screens are organised.  A specific ServerLayout

# section may be specified from the X server command line with the

# “-layout” option.  In the absence of this, the first section is used.

# When now ServerLayout section is present, the first Screen section

# is used alone.

Section “ServerLayout”

# The Identifier line must be present

Identifier  “Simple Layout”

# Each Screen line specifies a Screen section name, and optionally

# the relative position of other screens.  The four names after

# primary screen name are the screens to the top, bottom, left and right

# of the primary screen.  In this example, screen 2 is located to the

# right of screen 1.

Screen “Screen 1″

# Each InputDevice line specifies an InputDevice section name and

# optionally some options to specify the way the device is to be

# used.  Those options include “CorePointer”, “CoreKeyboard” and

# “SendCoreEvents”.

#InputDevice “Mouse1″ “CorePointer”

#InputDevice “Alps” “CorePointer”

InputDevice “USB-Mouse” “AlwaysCore”

InputDevice “Keyboard1″ “CoreKeyboard”

EndSection

# Section “DRI”

#    Mode 0666

# EndSection


HTPC power consumption

October 27, 2008

I was slightly concerned about overloading the outlet that services my home theater components.  Thinking the HTPC might add more draw than I was comfortable with, I grabbed my “kill a watt” meter and took a few readings of the HTPC.  Here are the results for anyone interested:

HTPC off / PSU switch on…………4 watts

HTPC on / Idle state………………51 watts

HTPC on / DVD rip………………..60 watts

HTPC on / DVD playback……….67 watts

HTPC on / HD video playback…70 watts


Getting 1080p HD output

October 22, 2008

Prior to this build, getting 1080p output from my old Nvidia FX5200 card was a long process, but I eventually got it working fine.  I was prepared for the same experience this time around with the GeForce7050PV on the Abit board.  The process went much smoother, and I’m not sure why, but I’m not complaining either!  Here’s an excerpt taken from the relevant portions of my xorg.conf that I’m using to achieve 1080p video via HDMI with Nvidia’s driver (version 173.14.09) to a Sony KDS-55A2000:


Section “Monitor”
        Identifier      ”Monitor0″
        Option  ”DPMS”  ”true”
        Option “UseEdidDpi” “FALSE”
        Option “DPI” “100 x 100″
        VendorName “SONY”
        ModelName “KDS-55A2000″
        HorizSync    30 – 110
        VertRefresh  60.0
        ModeLine “1920×1080″ 148.5 1920 2008 2056 2200 1080 1084 1089 1125 +HSync +VSync
EndSection

Section “Device”

        Driver      ”nvidia”
        Option “XvmcUsesTextures” “false”
        Option “UseEvents” “true”
        VendorName  ”All”
        BoardName   “All”
EndSection
Section “Screen”
        Identifier “Screen0″
        Device     “Card0″
        Monitor    ”Monitor0″
        DefaultColorDepth 24
        SubSection “Display”
                Depth     1
                Modes “1920×1080″
        EndSubSection
        SubSection “Display”
                Depth     4
                Modes “1920×1080″
        EndSubSection
        SubSection “Display”
                Depth     8
                Modes “1920×1080″
        EndSubSection
        SubSection “Display”
                Depth     15
                Modes “1920×1080″
        EndSubSection
        SubSection “Display”
                Depth     16
                Modes “1920×1080″
        EndSubSection
        SubSection “Display”
                Depth     24
                Modes “1920×1080″
        EndSubSection
        SubSection “Display”
                Depth     32
                Modes “1920×1080″
        EndSubSection
EndSection


There was some overscan which was easily corrected using Myth’s appearance wizard setting.

1080p goodness on the big Sony:

Sony confirming 1080p input

Miro player scaled to full screen running within MythTV. HD video from Nasa's Jet Propulsion Laboratory

HD content looks stunning!


Installing MythTV

October 19, 2008

I chose to install Knoppmyth (R5.5) since it’s Debian based and it’s somewhat familiar to me from having messed around with it three years ago.  There’s also a good community forum built around Knoppmyth for support.  Mythbuntu also looks nice and I will probably try it out later when I have more time to see how each distro compares with one another.

Installation on the new system was a breeze but I did run into some minor snags.  The installation was done with the HTPC connected to my Westinghouse 22″ LCD, and subsequent tweaks are being done via VNC on my Window’s box.  Once I feel comfortable with the install, I will reconfigure xorg.conf to play nice with my Sony KDS-55A2000 HDTV @1080p.

A nice feature of the Knoppmyth installer is the remote control script.  During installation, I was prompted to select a remote control to use with Myth, and I choose the Imon-Pad option to match the Moneual’s Imon pad remote.  Without any issues, I was able to use my remote immediately without hassling with recompiling LIRC or config files – nice!

Soundgraph Imon VFD
The VFD wasn’t working out of the box.  A few minutes on the Knoppmyth forum yielded a quick solution.  As root, running this script brought the VFD to life:

/usr/local/bin/vfd_install.sh

When prompted to configure, hit “y”.  A reboot was then required before the VFD would activate.  Note: the large clock mode isn’t compatible with my VFD’s two line display so I had to disable this option under the Appearance > LCD settings within MythTV.

EDIT: The VFD install script has broken the pad function on the Imon remote.  All other buttons function normally, however the pad is no longer responsive.  The “pad” on this remote provides up, down, left and right navigation and is essential for myth menu navigation.  After spending several hours trying to resolve this, I gave up and mapped some other buttons to perform the same function by editing:

/home/mythtv/.lircrc

DVD Playback
DVD’s aren’t working out of the box with my system either.  Xine throws this error at me when trying to play a DVD (both unencrypted and encrypted):

Per Myth’s general settings, the DVD device is set to /dev/dvd which didn’t exist on my system:

Creating a symbolic link fixed the problem allowing me to view a DVD when inserted in the drive:

ln -s /dev/scd0 /dev/dvd

with “scd0″ being my optical drive and “/dev/dvd” the location of the DVD device as defined in Myth’s general settings.  However, when rebooting the machine, the symbolic link is lost every time.  I fixed this by modifying (as root):

/etc/udev/rules.d/z25_persistent-cd.rules

The lines that contained the string “SYMLINK+=”cdrom1″  were changed to “SYMLINK+=”cdrom”, and similiarly for SYMLINK+=”cdrw1″SYMLINK+=”dvd1″, and SYMLINK+=”dvdrw1″ – the “1″ had to be dropped from each instance.

EDIT: After writing the above, and after a fresh “re-install” (long story), the DVD issue did not manifest itself and the DVD functionality works as expected the second time around.  I have no explanation for the DVD problem on the initial install…

Fix Myth Gallery mount failure messages

When myth starts, I was greeted with the following each time:

“Failed to mount device /dev/sde, showing default myth gallery directory”

This is probably caused by myth trying to mount the empty slots of the USB card reader.  For the meantime, I disabled them by adding the following to the “Ignore Devices” list:

/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde
 
Tweaks

Make Samba autostart on reboot so I can copy files to the HTPC at anytime from a Window’s box.  From a terminal as root:

update-rc.d samba defaults

Connecting from Window’s, the default username and password are both mythtv 

X11VNC  - get it working correctly with Nvidia and install TightVNC on my Window’s box.  I’m using VNC on my Window’s box to control the Myth frontend while I setup and tweak things.  Remember, I don’t have xorg.conf configured yet to communicate with my HDTV, and I don’t have a spare monitor sitting around to use to connect to the HTPC.  The HTPC at this point is a headless box – meaning it does not have a monitor, keyboard, or other peripherals connected to it at this point.  VNC is not practical for video streaming but well suited to navigate the myth frontend menus. There are issues with nvidia, so first edit:

/home/mythtv/.fluxbox

uncomment and alter the following line (change is in red):

[startup] {/usr/bin/x11vnc -nap -wait 50 -noxdamage -passwd fubar -display :0 -forever -o /var/log/x11vnc.log -bg}

Next, turn off OpenGL flipping by right clicking on the Fluxbox desktop & Apps > Tools > nvidia-settings to bring up the settings panel.  Uncheck “Allow Flipping”:

Results: Remote access to the new headless HTPC from Windows: