User Manual

Before you connect

This manual describes AR-Cluster 6.6 commands for logging programs, DX cluster clients and Telnet terminals. Your node’s feeds, saved settings and access policies determine what is available. Use HELP for command help and SHOW VERSION when reporting a problem to the sysop.

Use your own callsign and a permitted SSID. A node or peer callsign is reserved for its node connection. Coordinate your client profiles to avoid duplicate logins, and wait for any stated retry interval before reconnecting.

Saved filters, human/skimmer choices and FT-mode opt-in are explained in their respective chapters. RBN/skimmer reports are delivered only to eligible local users and are not forwarded to cluster peers.

Server-side PC9X topology performance work is transparent to connected users: ordinary remote-user membership changes remain immediate, and command, routing, saved-filter and spot-delivery choices are unchanged. If a node upgrade changes what you receive, compare SHOW VERSION, SHOW DX OPTIONS and the node’s feed status before replacing a saved filter.

01 / Start with the idea

What the feed does

A DX spot is a short report that a station was heard on a particular frequency. Someone might report a rare country, a contest station, or an opening on six meters. A DX cluster collects those reports and delivers them to connected users.

A node is the particular cluster server you connect to. Its operator is the sysop. Nodes exchange ordinary cluster reports with other nodes, so you can hear about activity well beyond the sysop’s local area.

Real-time means new reports arrive while your connection stays open. You do not need to refresh a web page or keep typing a command. Reports can be delayed, repeated, mistaken, or already old by the time you tune to them. Treat them as leads, then confirm what you hear.

The logger and the cluster have different jobs

The node supplies reports and accepts commands. Your logging program may turn those reports into a band map, highlight stations you need, or tune your radio when you select a spot. Those presentation features belong to the client program, and vary by application.

A Telnet terminal shows the text conversation directly: welcome messages, commands, replies and spots. Your logger’s cluster window often contains the same conversation behind its list or band map. You can use this guide’s commands in either, through the client’s command entry field.

02 / Get connected

Your first connection

Obtain three things from a node’s published listing or sysop: its hostname, its user port, and any login instructions. A hostname locates the server; the port identifies the service accepting your connection.

1. Open your client’s cluster connection settings. Your logger may call this its DX Cluster, Telnet or spotting window. A terminal client usually asks for a host and port.
2. Enter the advertised endpoint. If your client offers a server type, select AR-Cluster. Select Telnet/TCP rather than SSH unless the sysop gives different instructions.
3. Connect using your own callsign. The node may prompt for it, or your client may send it automatically. Follow the node’s instructions about passwords or suffixes. The node’s callsign is not your login.
4. Read the welcome message. It can explain feed availability, local policies and how to contact the sysop.
5. Type HELP, then SHOW DX 10. Help proves commands and replies can travel both ways; the history request asks for up to ten recent reports matching your settings.

For example, a listing might say “host cluster.example.org, user port 7300.” Those are illustrative values, not a node to connect to. Use the real values provided by the sysop.

Check what this node remembers

SHOW VERSION
SHOW DX OPTIONS

The first command identifies the software version. The second displays your saved DX settings: filter, mode, output, history count and comment extensions. ARC6 retains these on that node, so a reconnect may restore earlier choices. Another node can have different settings for the same callsign.

Your client can also send startup commands on every connection. If a filter unexpectedly changes when you reconnect, check that list before changing it again on the node.

Disconnect when you finish

Send BYE or QUIT, or use your client’s disconnect control. Turn off automatic reconnect if you want to stay disconnected. To return later, reconnect through the same saved client profile.

Callsign and SSID refusals

Use your own station identity and an SSID permitted by the sysop. Numeric aliases normalize: W1ABC-0 is W1ABC, and W1ABC-04 is W1ABC-4. A node’s configured or known peer identity cannot be used as a human login. A refusal should explain whether the cause is node identity, a local duplicate, network limit or a separate security policy.

03 / Understand the stream

Reading spots

This invented line illustrates the format. It is not a live report:

DX de W1AAA:     14025.0  ZL2BBB       CQ                       1832Z

Comments such as “up 2” or “QSX 14027” describe where a station is listening. The main frequency normally describes where the spotted station is transmitting. Listen to confirm split operation before calling. History listings may include a date and arrange the fields differently; your logger may place them into columns.

Human reports and skimmer reports

A human spot is an operator’s observation. A skimmer uses an automatic receiver and decoder. A spotter callsign ending in -# identifies a skimmer report. The Reverse Beacon Network (RBN) collects such observations from receivers around the world.

Automatic reports can include a mode, signal-to-noise ratio (SNR), CW speed in words per minute, a CQ indication, or a grid locator. What appears depends on the report. The SNR describes reception at that receiver, not at your antenna. A missing grid is simply missing information.

A CQ indication says what was reported at that time; it does not guarantee the station is still calling. Decoders can misread callsigns. A filter helps you choose reports, but does not prove the reports are correct.

04 / A small useful toolkit

Everyday commands

Type one command and press Enter. Commands are case-insensitive. Spaces and slashes are accepted between command words: SHOW DX and SHOW/DX mean the same thing. This manual uses full names to keep examples clear.

Pausing DX output does not erase your filter or stop all other kinds of messages. A client can continue to display old entries already in its band map. Its own “pause” or “clear” button may have a different effect from a command sent to the node.

Built-in help shows permitted abbreviations with required letters capitalized. For example, SHow Dx allows SH DX. Follow the help from your connected ARC6 node rather than assuming shortcuts from another cluster product will work.

05 / Catch up or investigate

Recent spot history

History is a way to ask “What has this node heard recently?” It is not a complete record of everyone on the air. The node’s retained data, feed availability, filters and query limit determine the result.

Your saved DX filter normally also applies to these requests. Adding BAND=20 to a query does not replace a saved filter that admits only 40 meters; their combination can return nothing.

Bypass the saved filter for one request

SHOW DX 10 - BAND=20

The standalone - after the count skips your saved filter for this request. It does not erase it or change live filtering. The request still uses available node history and does not bypass the FT Modes opt-in rule.

Request history in the live spot format

SHOW DX 10 @ BAND=20

The @ option uses the real-time spot format for this history reply. Some clients recognize that format more readily. These are still past reports, not newly heard activity, and the saved filter still applies.

Start with a modest count. Repeated large queries rarely help your operating and use additional server resources. An empty result means no matching records were returned; it is not proof the band was closed.

06 / Make the stream fit your station

Choose your spots

Useful filtering begins with a plain question: “Which reports will help me right now?” You might choose a band, nearby spotters, only human reports, or a skimmer feed family.

Save the old settings first

Run SHOW DX FILTER or SHOW DX OPTIONS and save the reply. The filter line starts with set dx filter, so you can copy, edit and paste the complete command. Equivalent list shorthand is restored where safe; original spacing and case are not preserved. An unset filter reports No DX filter is set. Keep a separate record of Mode and Output.

Each SET DX FILTER replaces the entire saved DX expression. It does not add another condition to the existing filter. Write the complete choice you want, including any band or geographic conditions you intend to keep.

Use SET DX MODE FILTER so the saved expression controls ordinary live reports. Choose one recipe below, check the server’s confirmation, then inspect SHOW DX OPTIONS again.

SET DX MODE FILTER
SET DX FILTER NOT SKIMMER AND BAND=20

SET DX FILTER SPOTTERCONT=NA

SET DX FILTER CONT=EU AND SPOTTERCONT=NA

SET DX FILTER (BAND=20 OR BAND=40) AND SPOTTERCONT=NA

Match any value in a list

Fields such as SPOTTERSTATE can match several values in one condition. Put the values inside square brackets and separate them with commas. A report matches when the field equals any one of the listed values.

SET DX FILTER SPOTTERSTATE=[CA,NV,UT,OR,WA,NM,ID,MT]

This selects reports from spotters in California, Nevada, Utah, Oregon, Washington, New Mexico, Idaho or Montana. It tests the spotter location, not the DX station location. The state must be known to the node. Uppercase and lowercase are accepted.

The list is shorthand for joining individual equality tests with OR. Use AND to add a restriction that every selected report must also satisfy:

SET DX FILTER SPOTTERSTATE=[CA,NV,UT,OR,WA,NM,ID,MT] AND BAND=20

This keeps the same spotter states and limits the reports to 20 meters. A supported numeric field such as BAND can also use a list:

SET DX FILTER SPOTTERSTATE=[CA,NV,UT,OR,WA,NM,ID,MT] AND BAND=[20,40]

Now a report must come from a listed state and be on either 20 or 40 meters. These examples do not opt into FT Modes. Each command replaces your entire saved filter; copy the old expression before changing it.

Lists also work with country entities, continents, grids and zones. Use the normal value for each field:

SET DX FILTER CTY=[K,VE]
SET DX FILTER SPOTTERCTY=[K,VE]
SET DX FILTER CONT=[EU,AS] AND SPOTTERCONT=[NA,EU]
SET DX FILTER GRID=[FN31*,FN32*] AND CQZONE=[3,4,5]

CTY, CONT, GRID and CQZONE describe the DX station. Their spotter counterparts describe the reporting station: SPOTTERCTY, SPOTTERCONT and SPOTTERCQZONE. Country values use cluster entity prefixes, not country names or ISO codes. GRID=[FN31,FN32] matches those exact locators; GRID=[FN31*,FN32*] also matches longer locators beginning with those four characters. Missing field values cannot satisfy a positive list match.

To exclude every value in a list, use <>:

SET DX FILTER CTY<>[K,VE,XE]

This means NOT (CTY=K OR CTY=VE OR CTY=XE). The older form NOT (CTY=[K,VE,XE]) remains valid. Re-enter a filter saved on an older build using a literal <>[list]; the upgrade does not silently rewrite it.

Lists also support >, <, >= and <= on fields that support those comparisons. Those list comparisons are joined with OR: FREQ>=[14000,21000] means either threshold, not a range. For an interval, use FREQ>=14000 AND FREQ<=14350. The shared list syntax applies to applicable DX, announcement and weather filter fields. Lists are not numeric ranges. Keep list entries to single values separated by commas, without empty entries. Boolean choices such as SKIMMER or SKIMVALID are clearer as ordinary Boolean conditions, rather than lists.

Clear just the filter

SET DX FILTER

Leave off the expression. This clears the saved DX filter and leaves your other DX settings in place. A blank filter can admit ordinary human and CW / RTTY skimmer reports; it still does not request FT Modes.

Restore what you had

Send SET DX FILTER followed by the complete expression you saved. Restore the saved Mode and Output if you changed them too. For example, if the old filter was BAND=40 AND NOT SKIMMER, resend that complete expression.

SET DX DEFAULT is a broader reset of DX options, including output and display choices. Use it deliberately, rather than as a routine way to clear one expression.

Use ARC6 query syntax

For 40-meter history, use SHOW DX BAND=40. Other cluster dialects, such as SH/DX ON 40M, are not translated. A malformed query receives an invalid-expression message and examples; it does not change your saved filter.

Frequency selections with WITHIN

FREQ WITHIN (...) selects a comma-separated list of exact reported frequencies and/or inclusive frequency intervals. All values are in kHz. Use a decimal point for fractions and a slash between the lower and upper limits; commas separate entries. Examples:

SET DX FILTER FREQ WITHIN (7000/7074,7078/7100)
SET DX FILTER FREQ WITHIN (7074,14074)
SET DX FILTER FREQ WITHIN (7100/7101.0)
SET DX FILTER NOT (FREQ WITHIN (7074/7078))

• 7000/7074,7078/7100 selects either interval, including all four endpoints. It includes exactly 7074; it does not exclude that FT8 base-frequency report.
• 7074,14074 selects exactly those two reported frequencies, with no implicit tolerance or receiver passband.
• 7100/7101.0 selects 7100 through 7101 kHz, including both limits. Every value inside the interval matches, not just its endpoints.
• NOT (FREQ WITHIN (7074/7078)) excludes the closed interval 7074 through 7078 kHz, including both endpoints, and otherwise leaves frequency selection open.

The first example is equivalent to the following existing ARC expression, using ordinary comparisons:

SET DX FILTER (FREQ>=7000 AND FREQ<=7074) OR (FREQ>=7078 AND FREQ<=7100)

The last example is equivalent to:

SET DX FILTER NOT (FREQ>=7074 AND FREQ<=7078)

Examples: human, skimmer and FT frequency selections →

Frequency selection does not identify a transmission mode. A human, CW, FT or other report at the same frequency matches the same frequency predicate. FT reports often give a USB base frequency, but reports can use other frequencies and precision. To combine this selection with another condition, use ordinary AND, OR and NOT, with parentheses where needed. Existing output and FT/skimmer opt-in rules still apply: WITHIN itself does not enable an FT feed.

A range may have equal endpoints, such as 7074/7074. Reversed bounds, empty entries, missing delimiters, negative/nonfinite values and oversized input are rejected without replacing the active filter. A list supports up to 128 entries, within the existing 16,384-character filter limit. Scientific notation and regional decimal commas are not shorthand formats; write 7100.5, not 7100,5 when you mean a fractional value.

Existing comparison operators, numeric lists, arithmetic and quoted text keep their meanings. In particular, FREQ=7000/2 remains division, and FREQ IN (7000/2) remains a numeric expression; neither becomes a range. The new shorthand is expanded once into ordinary ARC predicates when prepared. Saved filters and history queries use those predicates; there is no range parser running for each delivered spot. The filter confirmation or a saved recipe may therefore display the expanded comparisons.

Suggestion: Dave N3RD. Requirements, implementation and testing: NG7M. This is an ARC convenience, not a new DXSpider command or a claim of complete dialect compatibility.

Learn the units and operators

BAND is in meters: BAND=20. FREQ is in kHz: FREQ>=14000 AND FREQ<=14350. That range is an example filter, not advice about permitted operation in your jurisdiction.

= means equal; <> means not equal; >= and <= compare numeric values. NOT excludes a condition. AND binds before OR; parentheses make mixed expressions easier to understand and safer to edit.

A rejected filter does not replace the previous saved expression. Read the error, correct the complete expression and check the confirmation. Do not assume a change happened simply because you typed it.

Restore the current listener default

SET DX FILTER DEFAULT

This restores the current Telnet listener’s current validated default, not a factory-wide preset. A blank or invalid default leaves your filter unchanged. Save your old expression first if you want to return to it.

Keep and share your filter recipes

Saved DX filters for contests and everyday operating

Contest operators often want a different filter for each event: CQ World Wide CW, its SSB contest, or a weekly CWT session. DX chasers might keep separate lower- and higher-HF-band filters, while other operators keep a POTA filter. Save your working expression under a name such as CQWWCW, CQWWSSB, CWT Mini, POTA, Low HF or High HF, then load it when you need it. These are examples of personal names, not built-in contest presets; each name stores the expression you chose. ARC6 does not infer contest rules or switch filters on a schedule. The WA7BNM Contest Calendar provides event schedules and links to rules.

Previously you might have kept one filter under your callsign, another under callsign-1, and another under callsign-2. Named filters let you keep several choices under one login. Existing SSID profiles remain independent: AA3B and AA3B-3 each have their own active filter and saved collection. Filters are stored on this cluster node; they do not automatically follow you to other nodes.

Pause spot output while working

In a single scrolling Telnet window, incoming DX spots can interrupt filter lists and help replies. You can pause live DX output before working, then resume it when finished. This is optional; filter commands never toggle output for you.

SET DX OUTPUT OFF
SHOW DX FILTER
LIST DX FILTERS
SET DX OUTPUT ON

Remember the final SET DX OUTPUT ON so the feed resumes. This pauses DX spots, not every announcement or other stream.

Save, load, list and delete

LIST DX FILTER and LIST DX FILTERS work alike. Standard abbreviations and slashes work, for example SA/D/F CWT Mini and LI/D/F. Use HELP SAVE DX FILTER for the complete built-in help.

Build your collection

First set and check an expression using the usual SET DX FILTER command. The following example stores two band/spotter choices; choose expressions suited to your activity.

SET DX OUTPUT OFF
SET DX FILTER BAND=20 AND SPOTTERCONT=NA
SAVE DX FILTER High HF
SET DX FILTER BAND=[40,80] AND SPOTTERCONT=NA
SAVE DX FILTER Low HF
LIST DX FILTERS
LOAD DX FILTER High HF
SET DX OUTPUT ON

Names can contain 1–25 ASCII letters, digits, spaces, hyphens and underscores. Spaces need no quotes; leading/trailing spaces are removed and repeated spaces collapse to one. Names are case-insensitive. A name cannot consist only of digits because numbers select listed entries. You may save up to 50 filters per complete callsign/SSID; an existing name can still be overwritten at that limit. Expressions have the same 16,384-character limit as a normal DX filter, separate from the 25-character name limit. Only the filter expression is saved, not DX mode, output or other settings.

If no DX filter is set, SAVE reports No DX filter is set. Use SET DX FILTER before saving a named filter. It creates no empty entry and will not erase an existing saved expression. Deleting a saved entry and clearing your active filter are separate actions.

Borrow a club member’s filter

A club’s filter expert might use AA3B-3 for CWT. View that exact identity’s current filter or its saved collection:

SHOW DX FILTER AA3B-3
LIST DX FILTERS AA3B-3

The optional callsign/SSID is always read-only. Viewing changes no active filter, collection, output setting or login timestamp. It can read a user’s retained profile even while that user is offline. An unknown identity or unreadable profile gets a clear message; no new profile or default filter is created. SHOW DX FILTER with no callsign continues to show your DX options.

Each listed name includes the full SET DX FILTER command. Copy the expression you want, issue it under your own login, then use SAVE DX FILTER CWT Mini to keep your own independent copy. This does not link your saved entry to the other user’s entry; later changes to either copy do not affect the other.

LOAD and DELETE always use your own collection. Numbers in another user’s list are for reference. Looking at that list does not replace the number mapping from your most recent own list. You cannot save, load or delete another identity’s entries through these commands.

07 / Automatic receiver reports

FT Modes and RBN

ARC6.6 can offer both CW / RTTY and FT Modes RBN reports through one node. The sysop decides which incoming feeds are enabled. Your personal filter decides which available reports reach your session.

FT Modes require an explicit FTSKIMMER choice in your filter. A blank filter, SKIMMER alone, or choosing FT8 in your logger does not request the FT Modes feed.

These replace your whole filter. Keep shared band, location or other restrictions outside the grouped feed choice. Simply appending OR FTSKIMMER to a restricted expression can create an unrestricted way for FT reports to match.

A term is not the same as a complete way to match

A term is one test, such as FTSKIMMER, BAND=20 or SKIMVALID. An AND group requires its terms together; OR creates separate ways a report can match. Detailed explanations call each alternative a filter branch. Parentheses make the intended groups visible.

For an FT report, the way it matches must positively request FTSKIMMER. Having that word somewhere else in the expression is not enough:

SET DX FILTER (FTSKIMMER AND BAND=20) OR BAND=40

This admits 20-meter FT reports through the first alternative. A 40-meter FT report cannot enter solely through BAND=40: that alternative has no FT opt-in, and the FT alternative does not match its band. Ordinary 40-meter reports can still match the second alternative.

If you want FT reports on either band, keep the FT choice common to both alternatives:

SET DX FILTER FTSKIMMER AND (BAND=20 OR BAND=40)

This is why a feed term, band test or quality condition should be read in the context of the complete way a report can match, rather than as an independent switch.

Narrow the FT reports further

SET DX FILTER FTSKIMMER AND MODE=FT8 AND SNR>=-10

This requests FT8 reports at −10 dB or stronger at the reporting receiver. Negative SNR values are normal. The feed’s friendly name is FT Modes; MODE=FT8 intentionally selects just FT8, and MODE=FT4 selects just FT4.

SET DX FILTER FTSKIMMER AND GRID=FN*

This requests FT Modes reports with a reported locator beginning FN. * matches the remaining characters. A report with no grid will not match. This is not a worked-grid tracker, and your own station’s saved grid does not fill in a missing DX grid.

Choose an FT transmit offset

When your node receives the RBN FT-mode feed on port 7002, TXOFFSET gives the reported transmit offset in Hz above the bottom of the USB FT segment. It is not an absolute RF frequency and is not restricted to 3,000 Hz; wider receive bandwidths can produce larger offsets.

SET DX FILTER FTSKIMMER AND TXOFFSET>=0 AND TXOFFSET<=1000

This requests FT reports in the lower 1,000 Hz. Reports without TXOffset fail these numeric comparisons. To include FT reports with no offset, use FTSKIMMER AND (TXOFFSET<=1000 OR TXOFFSET IS NULL). Retain any band/spotter restrictions you need. Port 7001 and other spot sources may lack the field; ask your sysop about feed availability. The offset is retained in history and client XML when present.

Look at FT history

SHOW DX 10 - FTSKIMMER AND BAND=20

This asks for FT Modes history on 20 meters while bypassing your saved filter for this request. The explicit FT opt-in remains necessary, and it does not change your live settings.

SET DX FILTER (SKIMVALID) OR (FTSKIMMER AND BAND=20)

SET DX FILTER ((SKIMVALID) OR (FTSKIMMER AND BAND=20)) AND SPOTTERCONT=NA

08 / Contribute useful observations

Share what you hear

A useful human spot contains a verified callsign, transmitting frequency and a short factual comment. It helps another operator find a real station, rather than simply repeating a report you have not checked.

The command form is DX frequency callsign optional-comment. HELP DX explains it. Use kHz to keep the units unambiguous, and enter the actual station you heard.

If the station is working split, spot its transmitting frequency and put a verified listening instruction in the comment. Keep comments short and useful. Follow applicable contest rules about assistance and spotting.

For ordinary conversation or an announcement, use the appropriate messaging features and the node’s policies. RBN ingestion is read-only: your user commands do not transmit spots or configuration to RBN receivers.

09 / Personalize your node account

Your station settings

SHOW STATION displays your saved station information, including available profile details and macros. Share only information you are comfortable making available through the cluster.

A descriptive QTH or grid setting is not a substitute for the latitude/longitude settings used by heading calculations. Use HELP SET STATION LATLON for supported formats.

A small shortcut you can inspect and remove

SET STATION MACRO 1 SHOW DX 10

This stores a command in macro slot 1. Sending 1 followed by Enter runs it. Inspect macros with SHOW STATION; remove this one with SET STATION MACRO 1.

Choose an unused slot first. Macro definitions are limited to 200 characters, so a very long filter expression should not be stored without checking what was saved. Client-side buttons or macros are separate from the macros saved on the node.

HELP STATION describes more settings. The complete command reference covers needs lists, position settings and other profile commands.

10 / Explore when useful

More than DX spots

You do not need these features to receive DX spots. They are useful when you want node information, propagation reports or operating calculations.

Reports depend on incoming traffic; lookup data depends on the node’s database. Heading and sun calculations need appropriate position information. Read the calculation’s stated basis: a country-level position is not the exact location of every station in that country.

WWV and WCY report measured indices and propagation information, not a promise that a particular path will be open. This manual focuses on retrieving those reports rather than duplicating an authoritative solar-science reference.

Reference data and country names

Country/entity prefixes come from the node’s loaded CTY data, which can resolve portable calls and special exceptions. State/province information depends on the US/Canadian callbook; an unknown prefix does not prove a callsign is invalid. LOTW selects listed LoTW participants, without promising a recent upload or QSL. TOP100 uses the node’s cached Most Wanted ranking. SCP and FOC depend on the node’s loaded membership lists. Download failures can leave previous working data in use.

SHOW DXCLUSTERS K lists matching cluster-directory entries from this node’s cache. Check the advertised hostname/user port and the remote node’s policy before connecting; a cached entry is not a live availability test. SHOW HAMQTH callsign depends on the sysop’s configured lookup account, separate from local SHOW HAM callbook data.

One-line messages

TALK callsign message addresses a user and CHAT group message addresses a subscribed group where routing is available. SET ANNOUNCE CHATROOMS SOLAR,MBAND replaces your subscription list; no group clears it. These are one-line messages, not a dedicated terminal session. SHOW PC9X reports this node’s routing/queue status; it does not authenticate another user.

Control another message stream separately

SET ANNOUNCE OUTPUT OFF pauses live announcements; SET ANNOUNCE OUTPUT ON restores them. WX, WWV and WCY have their own output controls too. Turning off DX output does not turn off those streams.

Use HELP ANNOUNCE, HELP WX, HELP WWV, HELP WCY, HELP OPERATING and HELP NETWORK to explore their commands. Messaging and local access policies can vary; do not assume a command from a different cluster product has identical syntax or routing here.

11 / Find the missing link

Troubleshooting

Briefly inspect filter decisions

SET DX MODE DEBUG prefixes ordinary reports with + when they pass and - when rejected. Use it in a text view; the additional prefixes can confuse a logger’s parser. Return to SET DX MODE FILTER when finished.

FT reports that fail the explicit FT/filter check are suppressed before this debug display. DEBUG is therefore not a complete trace of rejected FT reports. OPEN mode also does not remove the FT opt-in requirement.

Send the sysop useful evidence

Include your client name/version, node, approximate UTC time, exact command and reply, plus SHOW VERSION and SHOW DX OPTIONS. Explain whether the problem is connecting, receiving text, or displaying received spots. Remove passwords and other private information.

12 / Keep this nearby

Quick reference

For all user commands, aliases and help topics, open the complete user command reference.

Before replacing a filter, save it. Every filter recipe above is a complete replacement, not a line to append. Normal blank-filter delivery does not include FT Modes.

This manual covers everyday user operation and selected advanced features. Built-in ARC6 help remains useful for further commands. A sysop installation/configuration guide is a separate document.