String Notations

Top  Previous  Next

The major problem in designing a CAT facility which will operate with virtually all brands of recent...and future...transceivers is to adapt to a large variety of different


number representations,

command identifiers and structures,

string structures,

dummy characters,

communication parameters,



Another important aspect is to keep the CAT facility as simple as possible from the perspective of the user though flexible enough to allow the experienced user to connect even the oddest rig to TurboLog 4. In order to deal with this problem we have hidden all the bits and pieces from the user by creating dedicated text files which contain all the necessary handshake information which can easily be selected by the user from a menu list of all available transceivers.

Underneath the user interface, however, each transceiver has a xxx.CAT file, for example TS940.CAT, FT1KMP.CAT, etc.. These files contain the delicate transformations between the user, the transceiver world, the PC environment and TurboLog 4.


In order to carry out the necessary transformations the following string notations and special characters were defined:


R,rRIT Frequency
* or ;Characters that disable a text line if in the first column; the * otherwise serves as placeholder character
>.....>This data will be sent to the rig due to the master slave procedure
<.....<This data is the expected response back from the rig
~ Denotes an increment of the delay as specified in the menu


Further notations:


Data to be transmitted or received has to be set in '.....'

Data attached to a command as a parameter must be separated from the command by '!' in all SET commands, for example in SETMODE, SETFREQ, SETBANDWIDTH, etc.


The following example:


SETFREQ = >'FA!fffffff!'>   will set the VFO A of a KENWOOD transceiver to the frequency given as fffffff.


This topic was last edited on  Thursday, 17-Jun-2021,  at  10:49