Справочник Пользователя для Kenwood TM-255A

Скачать
Страница из 100
8 EchoLink
44
TM-D710A/E
Figure 8-4   Finding Nearby EchoLink Nodes
Selecting “Online Only” in the pulldown list to the left of the “Find” button results in search results 
being displayed only for those nodes currently connected to the EchoLink server. 
“-L” at the end of a node callsign, such as “W4DJY-L”, indicates a link station (simplex operation). 
“-R” at the end of a node callsign, such as “W5DJY-R”, indicates a repeater station (semi-duplex 
operation). 
The frequency of the node is indicated in Freq (MHz).  Other node data is included too, such as 
access tone frequency, transmit power and height/ gain/ pattern for its antenna.
When “In Conference *xxxxxxxx*” is indicated under Description, the node is presently already 
connected to a conference (a round-table QSO room) called “xxxxxxxx”.
Once you verify that there is a node that may be accessible, you can verify access possibilities.  
Configure the frequency of your transceiver for the node frequency.  If a tone access frequency 
(e.g. 77.0 Hz) is shown, configure this frequency in order for the transceiver to send an encode 
tone.  Before transmitting, carefully listen on the frequency and first verify whether anybody is 
already communicating with the node.
Note: We recommend that you verify the state of nodes using the official EchoLink site via the Internet.  The information 
presented is kept up-to-date almost in real time. 
When no communication is heard, check if it’s possible to communicate with the node.  Press the 
PTT switch and use the keypad to transmit the “08” DTMF code (command for state verification).  
When the node is available to use, a signal will be returned from the node.  A “Not connected” 
announcement means the node is not connected to another station or a conference.  An 
“EchoLink disabled” announcement means the EchoLink software is inactive so you cannot use 
the node.  When there is no reaction at all from the node, it is possible that the node is not working 
or is outside communication range.  In that case, try verifying another node.