The QU notification is only issued ONCE until its sent flag is cleared by the host computer
executing CAT commands to read the changed data. In this way, the host computer is not flooded
by a long stream of identical QU notifications in instances such as the operator quickly turning the
tuning knob.
In the event that a QU notification was sent, and the QCX+ operator made more changes, which
the host computer does not know about, then when the host computer sends CAT commands, the
QCX+ will send a new QU notification to inform the host of the new events.
Note also that in the ordinary execution of CAT commands by the host, which may change
parameters such as the VFO frequencies etc., no QU notification is sent back to the host for these
changes. Only changes which are initiated by the QCX+ operator at the QCX+ controls, generate
a QU notification.
TB: QCX+ Text Buffer Decoded CW retrieval
There is now a special 40-character buffer, where incoming decoded CW is stored for sending to
CAT. This buffer is NOT a circular buffer. When it fills up, it simply discards any new incoming
characters. Therefore if the host application wishes to receive decoded CW from the QCX+, it
should ensure that it reads the buffer sufficiently often that it does not fill up.
TB;
This GET command reads the contents of the decoded CW buffer to the CAT host, and empties
the buffer, so decoding CW will CW filling it up again.
The format of the response is:
TBtnns;
where the field meaning is:
TB
two-character result code, the same as the command i.e. “TB”
t
indicates whether message sending is in progress via the KY command, and how many
characters remain to be sent. If more than 9 characters remain to be sent, then this
parameter is 9. If this character is 0 then the QCX is in receive mode
nn
the number of decoded characters
s
the string of nn decoded characters
;
CAT response terminator
You can also have the presence of decoded CW characters in the buffer indicated to you by the
unsolicited QU notification message, if you wish, and if you have enabled the unsolicited
notifications via a QU1; command. The QU notification is sent as soon as there is are least one
character waiting on the buffer, and if QU notifications are enabled, and if the QU notification flag
for decoded CW is enabled.
TB1;
This SET command enables the CW decode flag in the unsolicited notifications QU message (bit
event flag 64)
TB0;
This SET command turns off the CW decode flag in the QU notifications.
Therefore in order to receive QU notifications for decoded CW, you must have issued CAT
commands QU1; and TB1; first.
QCX operating manual, firmware 1.07, manual edit 0.03
49
