Western Digital Net

Western Digital Net

THURSDAYS at 1930 PST / 330 Zulu on 3.581 USB 1500 WF

Menu
  • WDN
  • About WDN
  • Forwarding Paths
  • Tools
  • Settings
  • NCS
  • Newcomers
  • FLNet

Tools

Here you will find macros, links and instructions for WDN. For FLDigi settings, check this link.

WDN CONVENTIONS

We highly encourage you to check out the ORCA Net if you are new to NBEMS or just want to brush up on your skills! The WDN is a spin-off from ORCA and most of the skills and conventions we use come from this parent net. In fact, the sole purpose of the WDN is to take what we learn on the ORCA Net and put it to use! So start with ORCA and join us here to use those skills to relay live traffic!

Please enable RXid (Reed-Solomon Mode ID recognition) and Net Control will send a TXid burst to assure all stations are in the proper mode. WDN uses MFSK, THOR and sometimes PSKR modes, but the “workhorse” mode on 80M is MFSK32. More settings here.

.


.

CHECKING IN:

.

Regardless of your skill level, all check-ins are welcomed! Please use the ORCA conventions for pre-tune (to prevent doubles), Video ID and KBD to send the following:

NCS < MYCALL MyName [ Priority | QRU | QNX | QST | (#) QTC for CALLSIGN | Relay ]

Priority = This message is urgent – please drop everything and deal with my needs immediately.
QRU = “No Traffic” but available to relay and may stay for Comments Round – Active on Net
QNX = Request to leave Net (In & Out) – may monitor the net or may leave the frequency – Not Active on Net
QST = “I have a bulletin or announcement for all stations”
QTC = “I have (x number of) traffic messages for (callsign of WDN station, WL2K, BBS, Email or NTS)” “TFC” is ok too.
Relay = “I’m relaying a check-in for a station Net Control can’t hear” (please continue to relay for that station!)

Yes, we use short hand and Q-Codes! We try to only use well-known or ‘mainstream’ Q-Codes in order to keep the net approachable to newer ops. Most new ops will only need to learn QTC and QNX.

If you have no traffic but you’re sticking around for Comments FLAmp fills and possible relays:
URCALL URName QRU 

If you are “In & Out” and will be inactive or off freq:
URCALL URName QNX

If you have a general announcement for the net:
URCALL URName 1 QST  (number changes depending on how many announcements you have)

If you have directed traffic to a station on frequency:
URCALL URName 1 QTC  >  THEIRCALL   (number changes depending on how many messages you have)

You will be acknowledged by NCS and may be asked to summarize in a few words your traffic if any. NCS will use QRZ.com to find your first name and location, so please send any corrections right away if either are incorrect.

If Your Traffic Needs to Be Forwarded Beyond Our Net

If you have traffic that you would like to have forwarded using Winlink, the Global BBS Network, regular email or NTS, your check-in will look like this:

If you have directed traffic to be sent via Winlink:
URCALL URName 1 QTC  >  WL2K (number changes depending on how many messages you have)

If you have a directed message to be sent via email:
URCALL URName 1 QTC  >  theiraddress@domain.com

For more information on these Forwarding Paths, see here.


The Traffic Round is prioritized by NCS and a roster will be sent showing your check-in status.

Following the conventions established by the ORCA Net, longer QSTs should be sent via FLAmp or FLMessage (ICS or plain text forms are optional). Shorter traffic may be sent by KBD or FLMsg.

Once the Traffic Round is complete (which should be short tonight), we will call each station who have QSTs in a sequence determined by NCS.

After the QST Round, we will call stations in the roster sequence to comment on the mission and format of this net, ask NCS any questions or volunteer to help with the new Net.

.


.

MACROs

MACRO FOR RELAY

<TX> < <MYCALL> Relaying Ck-In for Western Digital Net
Not copying NCS? Check in here… and list QRU, QTC, QST or QNX< <MYCALL>
<RX>

MACRO FOR VIDEO ID

<PUSH:m><LOCK:off>
<RXRSID:on><TXRSID:off>
<MODEM:NULL>
<GOFREQ:2000>
<VIDEO:URCALL>
<TX><RX>
<@POP>
<@GOFREQ:1500>
<@LOCK:on>

Note: Change “URCALL” above to your actual callsign.

Ck-In to the WESTERN DIGITAL NET
————————- Ck-In to Participate (Active but no traffic)

<LOCK:off><GOFREQ:1500>
<MYCALL> <MYNAME> QRU
<RXRSID:on><TXRSID:off><@LOCK:on><TX><RX>

——————— Ck-in QNX to Monitor (In&Out) or Ck-Out Early

<LOCK:off><GOFREQ:1500>
<MYCALL> <MYNAME> QNX
<RXRSID:on><TXRSID:off><@LOCK:on><TX><RX>

.


.

CONFIGURATIONS

Turn OFF AFC (located at bottom right of FLDigi) unless someone is using a PSK mode.

Click on “Locate flmsg” and find where your app lives. This will auto-launch it as needed.
Click on “Locate” next to “flamp” and find where FLAmp lives. This will launch it at startup so you don’t need to manually.
Make sure “Chars/Row” is set to 8 and these check boxes are checked.
Click on “Locate flmsg” and find where your app lives. This will auto-launch it as needed.
Click on “Locate” next to “flamp” and find where FLAmp lives. This will launch it at startup so you don’t need to manually.
Make sure “Chars/Row” is set to 8 and these check boxes are checked.
You will need to configure Rig Cat, Hamlib or use FLRig to get your particular rig control going. See Help menu for more info.

RESOURCES

Q-Codes
Short hand
Winlink
NTS
FLDigi Basics
FLDigi Quick Start
How to Identify Modes
In-Depth FLDigi Help
Tips for Working NVIS (close-in HF)
NCS Macros for WDN

Recent Posts

  • 3ca0f58bba4a46d81288b95439f27b72
  • 3ca0f58bba4a46d81288b95439f27b72
  • WDN Log 11-5-2020
  • WDN Log 10-29-2020
  • WDN Log 10-22-2020
  • WDN Log 10-15-2020
  • WDN Log 10-1-2020
  • WDN Log 9-17-2020
  • WDN Log 9-3-2020
  • WDN Log 8-27-2020
  • WDN Log 8-20-2020
  • WDN Log 8-13-2020
  • WDN Log 8-6-2020
  • WDN Log 7-23-2020
  • WDN Log 7-16-2020

Recent Comments

    Archives

    • May 2023
    • November 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • February 2020
    • January 2020

    Western Digital Net 2023 . Powered by WordPress