Archive for WinLink

You can send and receive Winlink messages using a terminal program such as Putty or AGW Terminal. I’ll assume you have your terminal program running and can use it to connect to local BBS’ such as N4SER-1

The numbers [564], which will be different each time you do this, are requesting you return the letters at those positions in your Winlink password.

If you password is PASSWORD you would type in WOS for the 5, 6 and 4 positions.

You must return a 6 letter code so add any 3 letters that you want

WOSDEN

They can be in any position and any order so

DONESW would also work.

Case insensitive.

If you entered your password letters correctly then the gateway will respond:

Hello W2DEN Wien CMS via N4SER >

The call will be yours and the CMS may be different…. you are now connected to the CMS!

Type h for help.

The CMS responds:

Winlink 2000 is designed for automatic message transfer using Airmail, Paclink, RMS Express or other client programs that support the B2F protocol. It will also accept limited keyboard commands on telnet and VHF connections.

Supported Telnet/VHF keyboard commands:

H or HELP gives you this file

LOGIN – If secure login is enabled for your account (or, in the future, required). Send any command to initiate login. The CMS will respond with a challengeconsisting of three digits who’s values represent positions of characters within your password. See <RESP>.

<RESP> – This is a six character response to the login challenge.

Respond with three password characters corresponding to the positions in the challengeplus three additional characters of your choosing (in any order). Example: Password is ABC123. Login challenge is: 425. You send ‘CR 1B2AZ5’. ABZ21TY would also be valid since it contains the characters 1, B, and 2.LM lists all traffic pending for your callsign. Shows message ID (MID), date, size, from and subject. Does NOT include messages SENT by you.

Where (MID) is the Message ID: The long random number assigned to the message (not including the call)

K <MID> Example: K 1234XYZRTG Marks the pending message as delivered. Message may still be read for 3 days using the R <MID> command.

KM Mark all messages as delivered. Message may still be read using R <MID> for 3 days.

B, BYE forces a disconnect of the link.

R <MID> Example: R 1234XYZRTG Read the specified message. Only MIDs addressed to your call or originated by you may be read. Attachments are not supported.

RM Read all pending unread messages to your callsign.

SP <Destination(s)> Send a message to the destination(s) indicated. Destinations may be a radio callsign or “SMTP:<email_address>” (NOTE! be sure to include the colon after the SMTP!) Multiple destinations should be seperated by “;” or “,”Example: SP W4ABC;SMTP:Johndoe@aol.com;W1AW;SMTP:sam@iam.us You will be prompted for a subject of the new message and then prompted for the message body. For the message body enter any text.

End with /EX on a separate line.

Acceptance of the message will be confirmed. You will be sent a service message if the message cannot be delivered.

UZ7HO version 0.96b and above has changed the Settings/Modem Mode from “VHF AX.25 1200bd” to “AFSK AX.25 1200bd”.

AGW Express by W2YG is no longer supported due to changes in Winlink Express (formerly RMS Express) that now allows the use of the UZ7HO Sound Modem.

The AGW Express / AGW PE setup had other uses such as running UISS by ON6MU to monitor the packet frequencies or to run TNCs not supported by WL Express such as the KPC-2. AGW Express is still available on this site in the original Soundcard WinLink post ( Link ) but is in no way supported by SERC, or anyone else. Unless you are an AGW PE die hard or have a real good reason to stick with AGW Express, it is recommended you migrate to the UZ7HO solution.

You can monitor all packets on frequency using the UZ7HO Soundmodem just as you did with AGW PE / UISS.

W6CCD’s instructions have been modified slightly to account for homebrew soundcard interfaces.

UZ7HO SoundModem Installation

This procedure applies to use of the SignaLink USB for VHF Packet. It assumes that the SignaLink USB has been set up correctly as shown in the SignaLink operation and instruction manual. Particularly with respect to the Windows system sound settings.

Check – Color waterfall. This can use a lot of computer resources, so you may not want to check this. It will depend upon your computer’s CPU.

Check – Stop waterfall on minimize.

Check – Enabled for KISS Server Port. Do not check AGWPE Server Port.

PTT Port:

For the SignaLink USB this should be NONE

Make sure neither box is checked.

For a homebrew soundcard interface, using a com port for PTT then select the port you are using to key your rig.

You may need to experiment with the ‘Dual PTT’ and ‘Swap’ check boxes to get your PTT to function.

Click OK

Click – Settings/Modems

Check – Default settings

Check – KISS Optimization

Check – non-AX25 filter

Under Modem type ch: A

Set Mode to AFSK AX.25 1200bd. Note this was “VHF AX25 1200 bd” prior to v0.96b.

Click OK

Leave the SoundModem running, and start RMS Express. SoundModem can be minimized if you don’t care about the waterfall.

Set to Packet WL2K

Click – Open Session:

Click – Setup

Set Packet TNC Type: to KISS

Set Packet TNC Model: to ACKMODE

Set Serial Port: to TCP

TCP Host / Port will be set to 127.0.0.1 / 8100

Under TNC Parameters, select 1200 Baud.

Check – Enable IPoll (Bottom of screen)

At this point you should be able to click Start and connect with a gateway. The normal sequence will be to plug in the SignaLink USB and turn it on. Then start the SoundModem and leave it running. Start RMS Express last and use it like you normally would. With RMS Express set up like this, you can switch back and forth between VHF Packet and Winmor without any changes, and not need a TNC for either one.

The WinLink whitelist was added a few years ago to help prevent spam from the internet. Incoming internet e-mail addresses (name@url.xxx) will be rejected by RMS Express if they are not in your whitelist. The whitelist has no effect on WinLink addresses (call signs). All messages from a WinLink address will NOT be rejected.

Here are some notes:

Add an e-mail to your whitelist:

Send a WinLink e-mail to an address to have it added to your whitelist. Or, add it using the SYSTEM as described below.

Allow an internet e-mal to by-pass the whitelist:

If someone’s internet e-mail is not in your whitelist they can still send you a message by adding //WL2K R/ in the subject line of the e-mail. (this really works!)

Editing your whitelist:

Your whitelist can be edited by use of WinLink e-mails to the SYSTEM.

Using WinLink, send the following message To: SYSTEM with Subject: WHITELIST

In the message body, the following options are available:

LIST: – will return a list of all whitelist entries for the user.

ACCEPT: jblow@somewhere.com – will allow messages from jblow@somewhere.com to be accepted. You may send multiple lines, each containing one e-mail address.

REJECT: jblow@somewhere.com – will reject any messages from jblow@somewhere.com. You may send multiple lines, each containing one e-mail address.

DELETE: jblow@somewhere.com – will remove jblow@somewhere.com from the your Whitelist. You may send multiple lines, each containing one e-mail address per line.

WinLink’s RMS Express client allows the use of templates to send and receive forms. To function both the sending station and all receiving stations must have the same templates available. This post will list common templates that may be used by SERC. Feel free to download and use them. Any additions, questions etc. please contact us at SERC@N4ser.org

Tactical addresses are associated with a ham’s call sign, they are addresses not call signs, not to be confused with tactical call signs used in voice communications.

Adding a Tactical address is the same as adding a new email account. Folders will be different for each email account.

When RMS Express checks for incoming mail, it receives mail addressed to the primary call sign and any aux call signs and tactical addresses that are enabled.

Tactical addresses stay registered with the CMS for 400 days. I believe they will go dormant after 90 days of nonuse.

All tactical addresses are maintained in the CMS database. If a client wishes to assume control of a tactical address, the current registered user must remove the address from the CMS.

After a tactical address is registered in the CMS, the address must be activated by sending a message into the WinLink system from that tactical address. This establishes a return route and will remain in force for at least 90 days.

Tactical addresses are registered with CMS over the internet from the client holding the tactical address.

Passwords are not required for tactical addresses, but it is strongly recommended that you assign a password to them

Thanks to Bob KJ4SV for this section on tactical addresses

Groups:

E-mail groups are created in the RMS Express program. Click ‘File’ then ‘Group Addresses…’

Enter a name for the group in ‘Group Name’ then add the addresses to the list to the right of the name. You can add existing addresses using the ‘Select From Contacts’ button. The group can be a combination of WinLink addresess (Call only) and e-mail addresses ( xxx@xxx.com).

Be sure and separate the addresses in the list with a semi-colon ( ; )

Click ‘Save & Close’ when done.

This same form can be used to manage existing address groups.

Forwarding WinLink to an Internet e-mail account:

It maybe inconvenient, or perhaps not possible due to travel etc., to use your RMS Express client to receive, and send, WinLink e-mails.

WinLink has created a way that you can have your WinLink e-mails forwarded to an internet e-mail; account, such as gmail, or Outlook.com.

Kantronics KPC-2

The KPC-2 was a great packet TNC in its day. With some help from the AGW software suite and W2YG’s AGW Express Interface the modem can be utilized by RMS Express and other packet radio applications.

RMS Express, the WinLink e-mail client, can not control a Kantronics KPC2 but must talk to the TNC via a serial port. The HW Virtual port fills in that rolle which in turns communicates to the TNC via the AGW PE program.

Hardware:

Kantronics KPC-2 V 3.00 (other versions may work…)

Kenwood TM-261 (any 2M radio will work)

Dell Latitude D600 Windows XP (any computer with a serial port, including a USB/Serial adapter and a soundcard will work.)

Radio to TNC Cable (This will vary from radio to radio.):

TNC

TM-261a

RJ45 (cat 5)

1

AFSK Out

6

Microphone

6

O1,G2

3

PTT

4

PTT

4

Blue

5

Audio

–

Speaker Out

–

–

6

GND

3

GND

3

W/O1, W/G2

Notes:

1. If Pin 1 is White/Green

2. If Pin 1 is White/Orange

TNC to Computer cable:

A male db-25 female db-9 adapter cable should work.

TNCDB25 (Male)

ComputerDB9 (Female)

Pin

Description

Pin

2

TXD

3

3

RXD

2

4

RTS

7

5

CTS

8

6

DSR

6

7

SG

5

8

DCD

1

20

DTR

4

TNC DB25: 11, 18, 25 do not connect

Software Installation:

Follow the instructions on the Soundcard WinLink page ( Link ).Accept the defaults as you go through the install. We will modify the settings when the install is complete.

This will install:

AGW Express Interface: This is the controling software that ties eveything together and gives you a single point of access.

AGWPE This will be the link between the virtual serial port and the KPC2 TNC. It controls the TNC.

HW Virtual Serial Port: The RMS Express software will connect to the AGWPE software through this port.

RMS Express: This is the WinLink e-mail client that you will use to create, send and receive e-mails. RMS Express intstructions are here: ( Link )

As installed AGW PE is set to ‘talk’ to a soundcard. This needs to be changed to the KP2 TNC as follows:

Editing AGW Express Interface:

Start the AGW PE Program

Right click the AGW PE icon in the work tray the click Properties.

The RadioPort Selection screen will open

Highlight the port you set up when installing AGW Express Interface. Most like it will be Port 1 and the only one on the list.

Click OK

The properties for Port 1 will appear.

Edit the Tnc Setup Tab: as follows:

Select Port: This should be the serial port connected to the KPC2

Tnc Type: Select KPC2.

Tnc Sub Type: KISS Simple

Tnc Control Commands:

IniKiss1: leave blank

IniKiss2: IN KISS

IniKiss3: RESET

Check ExitKiss On Exit

Select Single Port.

Tnc Radio Port: this is a description of the port. You can change this to any description you like.

Tnc Commands Tab:

To start select Program adjusts Parameters.

Select OnAir BaudRate: 1200Baud

You can Select Let me Control Parameters if you need to and know what you are doing.

Close the AGW PE program and the AGW Express Interface if it is open

Operation:

Turn on the radio and the KPC2 TNC.

Start the AGW Express Interface.

This will load:

AGW Express Interface.

HW Virtual serial port.

AGW PE

Then ask if you want to run RMS Express?

To use the WinLink system you would answer [YES] here and the RMS Express program will load and you will be able to send and receive e-mails.

If you answer [NO] then RMS Exprss will not be loaded but everything else will be. You can load RMS Express at anytime by clicking the icon on the desktop.

AGW Term

This set up allows you to use the AGW Terminal program is you wish to run in the standard packet mode.

Just close RMS Express and run the AGW Terminal Program.

The HW Virtual port is not really needed if this is all you wish to do but will not interfere with the AGW PE / AGW Terminal operations.

RigBlaster M8

This is written for the RigBlaster M8, now obsolete but available used.

The Soundcard WinlInk post pretty much covers how to make this work on the software side. Here’s the link the that post ( Link ). This section will cover the hardware needed for a RigBlaster 8M. Other commercial soundcard interfaces should work in a similar manner.

The ‘secret’ to a RigBlaster is the radio / RigBlaster interconnect cable. This cable is universal with a Din-8 (microphone plug) on one end and an RJ-45 on the other. Jumpers are used inside the RigBlaster to interconnect the RigBlaster with the 8 Pin DIN on the front and the RJ-45 on the back.

RigBlaster to radio interconnect cable:

Start with a Cat 5 cable with at least oneRJ-45 on it. Cat 5 has two standards, 568 A and B. The orange and green wires are switched on the two versions. The DIN-8 connector below is wired with a 568 B cable. Determine which type of Cat 5 cable you have and adjust accordingly.