DXNetHub Help

Every member gets a public reference such as UK0002: a two-letter country prefix plus a sequence number. It identifies your membership, never your person or your location, so it is safe to share. Your code is shown in the top-right user menu.

You can use a username and password, or Google. Accounts created with Google are asked to complete their country and handle on first visit. Password reset is only available for username/password accounts — Google accounts have no local password to reset.

Your home location is entered as a Maidenhead grid square, or derived from a town you pick. The platform stores an approximate point only. Nearby towns are used for distance sorting, never an exact address.

Choose whether you are shown by handle, callsign or first name. A last name is never displayed anywhere — not in logs, badges or map popups.

Three failed sign-in attempts locks the account temporarily. A password reset is offered automatically. Sessions last eight hours and extend every time you use the site.

A group is a permanent radio community, for example a regional PMR446 club or a 2m/70cm group. A group has members, a default frequency and mode, optional scheduled sessions, and a coverage area derived from where its members have actually operated.

1. Open the Groups tab.
2. Find a group in the list, or click its coverage polygon on the map.
3. Open the group page and choose Join.
4. Wait for an admin to approve if the group requires it.

Group admins can also invite you by email, or send a shareable invite link.

Members can hold roles: Admin (manage the group, its events and members), Controller (log contacts for the group's events), High Station (a recognised hilltop operator) and Member. Roles control what you can do inside that group only.

Signed-out visitors can browse groups and their coverage areas. Events, check-in logs and member rosters require an account.

Net events are scheduled sessions run by a group, usually on a fixed frequency and mode. DX events are activations — typically a hilltop or special-location operation, often worked on HF or via a repeater.

1. Open the Active Events view, or click a live event marker.
2. You land in the focused event log, with the map on the right.
3. Choose Check In to log yourself as present.
4. The event must belong to a group you are a member of; otherwise you are asked to join first.

When logging a contact, Heard By records which station heard the person you are logging. This is what draws the signal line on the map. If it is left blank, the line falls back to Net Control, or draws nothing at all — the platform never guesses an origin.

Be accurate here: a wrong "Heard By" makes every contact appear to come from one hilltop, producing a false starburst pattern.

• Relay / Net Control — runs the net.
• High Ground — operating from a summit or hill.
• Contact — a normal station checking in.

Two or more groups can co-host one joint net, up to ten groups. Contacts logged on a joint net are shared between the host groups, but coverage polygons stay strictly per-group so a combined net never inflates a single group's footprint.

Controllers and admins can log contacts on behalf of operators. Use Tag Member to link a logged contact to a platform account, or Tag as Myself if you recognise the name as your own.

• Groups — every group and its coverage area.
• Active Events — only events happening right now.
• Focused event log — one event, its contacts and signal lines.

Closed events disappear from the map entirely.

A polygon is the convex hull of where a group's members have actually operated. It is a record of real activity, not a claimed service area. Where there is not enough history to draw a hull, an approximate 25 km zone is shown instead, marked as generalised.

If several operators checked in from the same spot, you see one dot rather than a pile of overlapping ones. Hover it and the names are listed; click it for the full roster, with each operator's check-in number, distance and signal report.

A line joins a contact to the station that heard them. Line thickness does not encode signal strength. Hover a line is intentionally not used — details live on the dot instead, so lines never block clicks.

• Relay / High Ground / Contact — show or hide each station type.
• Show Contact Names — permanent name labels beside dots. In DX events this becomes Show Operator Names and is on by default.
• High Ground Links — the relay backbone between summits.
• Contact Lines — individual signal paths.
• Maidenhead Grid — grid square overlay.
• Dark / Light map mode — line colours adapt automatically.

Every coordinate is generalised to roughly a 1 km radius before it is stored. You can opt out of appearing on the global map at all. Beacons carry the same treatment.

A DX event is an activation of a location — a summit, a rare square, a coast or a special event station. It is separated from net events so two different kinds of activity never muddy each other's statistics.

1. Open your group and choose Create Event.
2. Set the event type to DX.
3. Enter the operating location, band and mode.
4. Open the event when you are on air — it then appears on the Active Events map.

A beacon advertises a summit activation to nearby operators: who is on the hill, which band they are monitoring, and an approximate grid reference. Beacons appear as ▲ markers and are generalised the same way as every other location.

DX events can be exported as ADIF for import into any logging program, or as CSV for a spreadsheet. Export is available to event admins.

1. Open your account menu → Edit My Profile.
2. Choose the Alerts tab.
3. Tick Enable notifications on this device and allow the permission prompt.
4. Press Send me a test notification to confirm it works.

Do this on each device you want alerts on — a phone and a laptop are separate.

• An event is about to start — a net or DX session you can see is going live.
• You are tagged as a contact — someone logged you on a net or DX session.
• You are invited to an event — including who invited you and the channel.

Each can be switched off individually. There is also Only groups I'm a member of, so you are not alerted about groups you do not follow.

• Check notifications are still allowed for the site in your browser or phone settings.
• Clearing your browser's site data removes the subscription — turn notifications off and back on.
• On iPhone, confirm DXNetHub is still on the Home Screen.
• Use Send me a test notification to check without waiting for a real event.

Turn off this device stops alerts to the phone or computer you are using, without affecting your other devices. Unticking the main switch turns your alerts off everywhere.

My Log is your personal record of every contact you have logged or been tagged in, across every group and event. It works as an independent logbook: you can add contacts that were never part of a platform event.

Choose Add Contact in My Log and enter callsign, date, band, mode, signal report and any notes. Personal contacts are private to your account and are never shown to other members.

Your log summarises total contacts, unique callsigns, bands worked and recent activity. Achievements are calculated across your whole log, not just platform events.

Export your whole log as ADIF (for logging software such as Log4OM or N1MM) or CSV (for spreadsheets). Exports contain only your own contacts.

If you administer several groups, the dashboard header has a Managing Group selector. Everything you change applies to whichever group is selected there.

The group's core identity: name, description, default band, predefined channel and mode, Facebook/website links, and schedule recurrence.

This tab also holds the public visibility controls — whether coordinates, grid squares, notes and distances are shown to non-members. Turning these off hides that data from the public API, not just the screen.

Who belongs to the group and what they may do. Prominent roles:

• Admin — full control of the group, its events and its members.
• Controller — can log and edit contacts for the group's events.
• High Station — a recognised hilltop operator for the group.
• Member — can attend events and check in.

You can also invite operators by email from here, and remove members who have left.

Create, edit, open and close the group's events. Opening an event publishes it to the Active Events map; closing it removes it entirely, which is why closed events never linger in view.

Joint nets are arranged here too — invite another group as co-host (up to ten).

In Events & Schedule, create the event as normal, then set a recurrence — weekly, fortnightly or monthly, chosen by day of week and time. The group then shows a recurring slot instead of you creating the same event by hand each week.

The scheduled slot is a template: each week you still open the actual event when the net begins, so the live map only ever shows sessions that are genuinely running.

Use 1-Tap Open Today's Event in the Groups menu to open the next scheduled session without filling in the form again.

Trends for the group: members over time, events held, total contacts logged, and how busy each event was. Useful for showing how much activity a group genuinely generates.

These are two different views of the same group, and they show different amounts on purpose:

• Groups view (everyone) — the group's name, coverage area, frequency and public description. No rosters, no event history.
• Admin dashboard (admins/controllers) — members and roles, every event including closed and cancelled ones, settings, and activity trends.

So a closed event disappears from the public map but remains in your dashboard's Events & Schedule list, marked Closed. That is expected, and is how you review a net afterwards.

While viewing one of the group's events, open Event Actions in the header. The Export options there give you ADIF (for logging software) and CSV (for spreadsheets). Only the group's admins and controllers see them.

A generalised grid square, an optional town name, your handle and callsign, and your contact log. Nothing more precise than that.

One cookie keeps you signed in. Display preferences — map labels, theme, collapsed panels — are stored on your device only and never sent to the server. There are no tracking or advertising cookies.

Donation records are pseudonymous. The donor's name and email are discarded and never stored; attribution happens only through a membership code quoted in your own message.

• Site name — the name people actually use, including local variants.
• Grid square — six characters ideally (e.g. IO83KI). Four is fine if that's what you have.
• Bands known to work — which bands you have actually made contacts on from there, not which ought to work.
• Access — parking, footpath, landowner permission, gates, anything that would stop someone arriving.
• Hazards — wind, exposure, livestock, poor phone signal, steep ground.
• Anything seasonal — the road is open in summer but not winter, a site is busy in lambing season.

1. Add a record — open High Ground Spots Database from your user menu. You can add a site directly: name, grid square, bands, access and notes.
2. Log a contact from the summit — during any event, mark the check-in as High Ground and enter the site name. That records real, proven activity from the site.

The two complement each other: the database holds what is known about a site, while logged contacts prove it works in practice and feed the group's coverage area.

One accurate, well-described site is worth ten vague entries. If you are unsure of a grid reference, say so rather than guessing — a wrong location sends people to the wrong hill.

All coordinates are generalised to roughly a 1 km radius when stored, which protects the exact spot without costing usefulness for net planning.

Reports are genuinely welcome — most of what has been fixed on this platform came from members saying something looked wrong.

What makes a report fixable:

• What you did — which group or event, which tab.
• What you expected and what actually happened.
• The page address — copy it from the browser bar, including any ?net=…&event=… part.
• A screenshot if it is visual.
• Your browser and device, especially if it works on desktop but not on a phone.

Where the error console is available, the Copy Report button produces a ready-to-paste summary including the page, browser and recent activity. Paste it into an email or forum message along with a sentence about what you were doing.

Please avoid including personal details of other operators in a report — call signs and membership codes are fine, home addresses are not.

• Membership codes — every member gets a shareable reference such as UK0001.
• Choose your country at registration; the map opens on it.
• Google sign-ups are asked to finish their country and handle.
• Joint nets can be co-hosted by up to ten groups.
• Contact lines are visible in light mode again, and keep their colour after hovering.
• Navigation now updates correctly after signing in.
• Anonymous donations are recorded without storing any personal details.
• Security hardening — automatic blocking of abusive traffic, and improved audit logging.