The new "BEACON ROBOT" made by radioamateurs

February 1997

Version: 1.0

Every 30 seconds the Beacon sends its identification message. This could start with a general interest message, if this has been scheduled to happen at selected times from the controlling station.

After the Beacon switches into the STAND-BY mode, it is open to receive user's CW command keys for an interval time of 30 seconds.

First, it is needed to allow the recognition of the user's CW speed, which has to be within 50 and 300 characters/min. To do so, the same letter, a "V'' for example, should be repeated a few times before sending the first command.

It is compulsory to terminate every command key with the letter "K"; this character has also to be sent well separated from the previous command key. If the command key is not recognised, the Beacon replies with "? ?". Then the command can be repeated (don't forget the final "K").

The Robot answers at the same speed of the current user, provided that it is not issued a command to change it.

List of the command key codes, available to the user, in CW:

DBM K

Request to send back the signal strength received by the Robot.

The Field Intensity scale is limited between 0 and 54 dBV.

To activate this function, after the beacon reply "R R", the user has to transmit a series of dots or dashes or a continuous carrier, for at least 5 seconds, but no more than 10 seconds.

Values in V are obtained as: V = 10 (dBV / 20) .

DBM "freq." K

Request to set the receiving frequency, for 10 seconds, within the following limits:

28000.0 - 29999.9 kHz, 24500.0 - 24999.9 kHz,

21000.0 - 21499.9 kHz , 18000.0 - 18499.9 kHz

The signal intensity (in dBV), received on that channel along those 10 seconds, is sent back on the nominal output frequency of the Beacon (28195.00 kHz). The decimal point can be entered as the character "point" or "comma" or "R" (for example 28005R5).

INFO K

Request to transmit info and operating conditions of the BEACON as:

UTC time and date

nominal output frequency

output power level in Watt

antenna type

QTH name and locator

current CW speed (in WPM)

internal temperature of the hardware box (°C)

external ambient temperature (°C)

address where to ask for more info and this list of command keys

LIST K

Request to send the list of the last 5 QSO.

LIST "n" K

Request to send the list of the last 10 QSO if "n"=1, 20 QSO if "n"=2 or 30 QSO if "n"=3, each with the following format: MMM DD HHMM CALL S R P BB

where:

MMM= month

DD = day of the month

HHMM = UTC time

CALL= callsign of the user station

S = S-units of the sent signal report

R = S-units of the received signal report

P = coded level (1-9) of the output power

BB = frequency band where the user has been received

PWR 1...9 K

Request to set the Beacon output power at the level of the following table:

CODE

1 = 32W

2 = 16W

3 = 8W

4 = 4W

5 = 2W

6 = 1W

7 = 0.5W

8 = 0.25W

9 = 0.125W

These are 9 levels in 3 dB steps. The absolute calibration is checked two times a day. The output power is reset at the maximum level at the beginning of each Identification Cycle.

PWR K

Request to know the current output power.

QRG K

Request to know the exact transmitting frequency.

QRO K

Request to set the output power at 32 W.

QRP K

Request to set the output power at 8 W.

QRPP K

Request to set the output power at 1 W.

QRS K

Request to slow down the beacon CW speed of 25% with respect to the user speed. This command can be repeated, to get still lower speed.

QRQ K

Request to rise the beacon CW speed of 25% with respect to the user speed. This command can be repeated, to get still higher speed.

QRR K

The Robot speed is reset equal to the user's CW speed.

QSA K

Request to know the user's signal strength in S-units, as received by the Robot. Same procedure as with the DBM command key.

S9 equals 34 dBV or 50V.

QSA "freq." K

Similar to the DBM "freq." Command key. The value returned is the signal strength of the user on the frequency "freq", in S-units, instead of dBV.

QSB K

Request to send a sequence of different output power levels, from 32W down to 0.125W, in 3dB steps. Each level is identified with a number from 1 to 9 (see the previous command key "PWR") and lasts for a few seconds.

QSY "band" K

The Beacon output frequency is moved for a while in the selected band (12, 15, 17 metres), where it sends a short version of the ID message, like with the command key "QTG". The actual frequencies on each band are chosen by the control station, which can also disable this feature.

The default values are: 18105.0 kHz - 21145.0 kHz - 24920.0 kHz

QTC K

Request to know which QTC are available. The QTC messages are recorded by the controlling station and numbered from 0 to 9.

QTC 0...9 K

Request to broadcast the (0-9) general QTC message.

QTG K

Request to transmit for a few seconds a short version of the ID message, with the current output power level.

QTH K

Request to transmit the LOCATOR and the name of the site where the Beacon is located.

QTR K

Request to send the Beacon date and time, kept within a few minutes from UTC by the controlling station.

TEMP K

Request to send the value of the internal temperature of the unit and the external ambient temperature, in °C.

WPM K

Request to send the CW speed of the user, in words per minutes (WPM) and the dot/dash ratio of the characters.

How to make a QSO with the BEACON ROBOT:

The QSO with IY4M is quite similar to a conventional connection with any radioamateur. It can proceed in a few different ways, with the exchange of signal reports, which are finally recorded in Beacon logbook.

After the Beacon has transmitted its ID message, and you have got the recognition of your CW speed, send this start sequence:

IY4M "mycall" "mycall" K

If your callsign is not properly received at the first trial, the start sequence can be repeated, with just one callsign, instead of two. After the "IY4M" you are also allowed to add a dummy "de", if you like.

Before starting a new QSO, the Robot has to recognise at least two times the same callsign. Any new entry is first checked against simple acceptance rules, to reject the "impossible" ones, also if they are repeated many times. In case of doubt, the Beacon replies "?? PSE AGN", asking for a new entry.

All uncertain callsigns are collected anyway, up to the last 16. The validation of a new entry can then make also use of this temporary list, or of a database of up to 2500 old confirmed callsigns.

Only when the Beacon is sure of the user callsign, the QSO proceeds.

· a welcome message is sent to the user; if the callsign database contains a record of the user's callsign, the message refers also to the last QSO with the Robot and to the operator's name (if this info is already available);

· if the operator's name is not available, you can (optionally) send it for at least two times, at the Robot request (remember to add the final "K");

· then it is asked the user's RST. This can be repeated just one or more times, followed by the end character "K", within 10 seconds (by the way, the letter "N" can be used instead of the number "9"; for example 5NN 5NN K, is equivalent to 599 599 K);

· now the Robot waits for a continuous or intermittent signal, lasting for at least 5(6 seconds, to measure the user's signal strength; the RST report is then transmitted by the Robot;

· the QSO is closed with various information and greetings, some in the mother tongue of the user.

To give a more human feeling to the QSO, the Robot selects at random the actual text of the answer among different options. There are two types of answers: verbose and quick. The longer expressions are used for the first QSO in the day with a particular user, while the shorter ones for all the following QSO.

The Team responsible for the Beacon Robot is committed to send a special QSL card to all the SWL reports and to all callsigns who had a successful QSO.

The present version of the software is open to further improvements and modifications, according to the experiences we will gain along the use of the Beacon Robot and the suggestions the users will let us now. Last updates will be available in real time to all users as QTC messages.