G6NHU-2 is my DX cluster node, running DX Spider software and has been online since 2016. If you use my node, you are getting good quality, quick data because it’s always running the latest version with multiple levels of filtering to block cluster spam and abuse.
For security and to help protect the network, in order to be able to send spots, you will need to register. You can do that by by sending me an email, my email address is shown when you connect and is available via my qrz page.
g6nhu-2 is quick, with connections into other nodes from all continents. The backbone is very fast and efficient anyway but these multiple connections ensure that when a spot appears on the network, you will see it very quickly, no matter where it was submitted.
The multiple links mean that it does not depend on just one source for its data. If any link drops out for any reason, there are others to provide redundancy and ensure that no data is lost and no spots are dropped.
g6nhu-2 always has the most recent version of the current (mojo) branch of the DX Spider software. Every weekday evening, around 22:40, it checks for an update and if found, it will apply that update and restart the software. If you are connected at this time and you find your link has dropped, it’s because an update has just been installed. You can reconnect straight away. The node will not update at weekends so as not to cause any disruption to anyone who is connected during a contest.
The Country file and satellite Keplerian Elements are checked daily and if updates are available, they will be transparently applied in the background. The former means that if you use the g6nhu-2 DX cluster to filter by country or zone, you are always getting the most accurate information available. The FCC master database is updated weekly and g6nhu-2 takes that update a few hours later.
I welcome HamClock users to connect to g6nhu-2, please ensure your HamClock version is greater than 2.92 (as otherwise it can cause excessive traffic). If your HamClock version is shown in red, tap on the version number and follow the prompts to update.
g6nhu-2 takes a direct feed from the Reverse Beacon Network. This is a lot of data and so it’s disabled by default. You can enable it by using set/skimmer and disable it using unset/skimmer. Various options are available depending on the mode you want to see traffic for. For example, you could use set/skimmer rtty to see just RTTY spots, set/skimmer cw for CW spots, etc. For a full guide, use the commands help rbn and help set/skimmer once connected.
Because it’s hosted on a static IP address, there is no chance that you won’t be able to connect to it due to the DNS record being out of date.
How to connect
Some logging software already has g6nhu-2 built in as one of the available DX cluster nodes to connect to but if yours doesn’t, you should be able to manually enter the details. You can enter either g6nhu.getmyip.com, port 7300 or g6nhu.changeip.net, port 7300. The cluster is on a static IP address and hasn’t changed in years but I always give out a dynamic dns address in case the site it’s hosted at changes in the future.
Some of the available lookup commands
sh/qrz [callsign] – Lookup callsign at qrz.com
sh/heading [callsign] – Show beam heading to callsign (or country)
sh/usdb [callsign] – Show the city and state of any US callsign as per the FCC database
sh/wm7d [callsign] – Lookup callsign in the WM7D database
sh/db0sdx [callsign] – Look up callsign in the qslinfo.de database
sh/dxqsl [callsign] – Look up QSL routing via a database that has been built up by examining DX spots back to 2002
sh/ik3qar [callsign] – Look up QSL routing via the IK3QAR database
This is just a few of the commands available on g6nhu-2, for the user manual, see here.