Rather than re-invent the wheel, please visit the EchoLink web site for more information about EchoLink!
The KCØMKS-R Echolink Node runs 7x24 and is primarily on the LSAC 1 system. More information about both LSAC systems can be found at LSAC Repeater System web site. Thank you to Randy NØBZZ and Pat KBØQYC for their generosity and patience in making the LSAC systems available for EchoLink.
Nets on the LSAC 1 Repeater System:
Occasionally the node may be disabled or in receive only status. Generally speaking this occurs when there is a major event taking place and no interruptions to that event via EchoLink can be tolerated. Such events may be:
If you should notice problems with the KCØMKS-R EchoLink node, please report them promptly to Jeff KCØMKS via email or on the air.
The KCØMKS-R EchoLink node is a closed system and therefore all EchoLink nodes that connect need to be in the authorization list. Please contact Jeff KCØMKS to have your call sign added to the list. For security reasons, all connections are logged.
If you try to access the KCØMKS-R node from another repeater system, the EchoLink node on that other system would also need to be added to the authorization list.
Due to the available bandwidth at the node location, a maximum of 9 connections are allowed at any given time.
To prevent accidental interference with repeater operations, the repeater owners have allocated the use of DTMF key "C" to be used at the begininng of every EchoLink command. Please note that due to the total number of link radios in the path to the EchoLink node, DTMF access may be limited. For example, using the Moose Mtn. receive site, the path to EchoLink goes through 8 radios including your own...
To control EchoLink from the LSAC Repeater System, use the following commands:
Connect | Cxxxxxx | Connect to another node where "xxxxxx" is the node number |
Disconnect | C# | Disconnect the most recent connection |
Disconnect All | C## | Disconnect all connections (panic disconnect) |
Node status | CØ8 | Check to see if any nodes are connected |
Information | C* | On air help via a menu system |
Station shortcuts:
Shortcut | Node Name |
CDØØ | [available] |
CDØ1 | KCØTIU |
CDØ2 | KCØMKT |
CDØ3 | KCØMKU |
CDØ4 | [available] |
CDØ5 | [available] |
CDØ6 | [available] |
CDØ7 | [available] |
CDØ8 | [available] |
CDØ9 | N2RON-L |
CD1Ø | KBØP-L |
Other EchoLink repeater nodes that frequently connect to/from KC0MKS-R:
Node Number | Node Name | Description |
2Ø52 | KBØP-L | Ishpeming, MI (UP) |
453649 | KJ4IBS-L | Simplex, either from Walker MN or Naples FL. Uses simplex 147.480 CTCSS 100.0 |
51325 | N9QWH-R | NW Wisconsin N9QWH Repeater System |
9999 | ECHOTEST | EchoLink Test Server |
Every hour there is an on air announcement for EchoLink. Within that announcement is the instruction on how to access the on air help menu system. The help menu is an small piece of software I wrote that communicates to EchoLink through an API (Application Programming Interface).
The KCØMKS EchoLink node transmits and receives on the 7Øcm LSAC Hub Linking frequencies. EchoLink runs on the same machine as a number of other internet applications. The computer is dedicated to serving only internet applications. The computer-to-radio interface is a homebrew that is totally electrically isolated to reduce noise and hum problems. The Yaesu FT-1907R radio is powered by an Astron RS-2ØA and running at 25 watts. To eliminate background hiss in the 22 mile trip to Proctor, I use a tower mounted heavy duty Arrow Antennas 440-5S (5 element 44Ø) Yagi that 48' up the tower and is pointed at Proctor. Since our location here in Knife River is at the top of a ridge about 4ØØ' above Lake Superior, we get winds in excess of 6Ø mph four to five times a year whenever a "noreaster" blows in. Hence my reason for using the heavy duty Arrow Antennas. Our location is also line-of-sight to both LSAC Bayfield and Proctor Hub locations.