Reporting to the Winlink database.

Winlink 2000 (WL2K) maintains a database of stations providing access to their system. If your system provides direct access to the WL2K system your frequencies can be included. Please only do this if you provide a 24/7 service.

If you are running RMS Packet, your packet frequences are configured within the RMS Packet Setup.

You define your reports using the WL2KREPORT configuration statement. This is included in the Packet, Pactor, ARDOP, Winmor or VARA configuration.

For this to work, you must have an Application called RMS, giving access to the WL2K system, either via an RMS Packet Server, or via the CMS Connect option of TelnetServer. For Winmor, ARDOP, VARA and Packet modes this application must have an APPLCALL, and for Pactor your configuration must include the APPL RMS statement to give direct access to it.

Note that if you report to the Database, your station details will be included in WL2K client programs' station selection lists, and you are likely to receive quite a few connects from them. If you want to preserve your HF bandwidth for BBS forwarding, you may be better not sending reports.

WL2K have recently (March 2012) introduced the concept of a user-defined "Service Code", so separate frequency lists may be maintained for different user groups (eg MARS, EMCOMM). The sevice "PUBLIC" is the default.

The BPQ32.dll console "Actions" Menu has an option to create or update your SYSOP informaton on the WL2K Database

The format of a report definition statement is:

WL2KREPORT Service, Host, Port, Callsign, Locator, Hours, Freq, Mode, Power, Ant Height, Ant Gain, Ant Direction

Host will normally be api.winlink.org, and Port 80. Callsign is the call used to access RMS, including an SSID if relevant.

Locator is your "Grid Square".

Frequency is specified in Hz, and is centre (not dial) frequncy.

The "Hours" field defines the time range the report is valid for, eg 00-23 for continuous. More than one range may be specifed, separated by colons, eg 00-08:17-23, meaning 00:00 to 08:59, 17:00 to 2359.

Mode can be PKTspeed, eg PKT1200, WINMOR500, WINMOR1600, ROBUST, P1, P12, P123, P1234, P2, P23, P234, P3, P34, P4, ARDOP200, ARDOP500, ARDOP1000, ARDOP2000, ARDOP2000FM, VARA, VARA500, VARAFM, VARAFM12 or VARAFM96.

Power is specified in watts, Antenna height in feet, Antenna gain in dB, and direction in degrees (0 = omni, 360 = North). Power, Height, Gain and Direction may be omitted - the WL2K system will apply default values

for example

WL2KREPORT PUBLIC, api.winlink.org, 80, GM8BPQ-10, IO68VL, 00-23, 144800000, PKT1200, 10, 20, 5, 0

If you are using Rig Control for scanning, you can include as many WL2KREPORT lines as you need to define all your Time/Frequency/Mode combinations. For example, for a PTC scanning two frequences for both Pactor and Robust Packet you could have:

WL2KREPORT PUBLIC, api.winlink.org, 80, GM8BPQ-10, IO68VL, 00-23, 28110000, P123, 50
WL2KREPORT PUBLIC, api.winlink.org, 80, GM8BPQ-10, IO68VL, 00-23, 28110000, ROBUST, 50
WL2KREPORT PUBLIC, api.winlink.org, 80, GM8BPQ-10, IO68VL, 00-23, 14103000, P123, 50
WL2KREPORT PUBLIC, api.winlink.org, 80, GM8BPQ-10, IO68VL, 00-23, 14103000, ROBUST, 50