home *** CD-ROM | disk | FTP | other *** search
-
-
-
- The following is a connect sequence to WA3DSP-5 (Netrom) on 221.01,
- connect to N3ET-1 (KPC-4) on 221.01, cross connect to KB3UD-1 (Netrom)
- on 145.01, connect to KB3UD on 145.01. Note the SX to do the cross
- connect. This would be SC if staying on the same frequency. Also
- note the R>###LINK MADE. The > is the KPC-4 prompt that is not
- followed by a carriage return. You have to pick it up AFTER you
- send the SX. It will be in the input buffer. For the KPC-2 the
- prompt character is a ? instead of a > but the missing carriage
- return means it must be handled the same way. You may have to
- modify the case of some of these statements.
-
- CC WA3DSP-5
- SC N3ET-1
- RCONNECTED TO
- R###CONNECTED TO NODE
- RENTER COMMAND
- SX KB3UD-1
- R>###LINK MADE
- SC KB3UD
- RCONNECTED TO
- FB0023C KB3UD
- @C:\PKT\RLI\KB3UD.FWD
- *** EOF
-
- The following is a connect to WA3DSP-5 (Netrom) on 221.01, connect
- to W3GJC-1 (KPC-2) on 221.01, connect to WB2GWD on 221.01. The line
- after R###CONNECTED TO NODE on a KPC-2 is user configurable. Pick
- a unique string from whatever is there. In this case it's the
- owners name. The tricky part when I figured this out was how to
- get by the KPC's hanging prompt line ie. > or ?. You must have an
- R line for each of the several lines sent by the KPC.
-
- CC WA3DSP-5
- SC W3GJC-1
- RCONNECTED TO
- R###CONNECTED TO NODE
- RCUSICK
- RENTER COMMAND:
- SC WB2GWD
- R?###LINK MADE
- FB0023C WB2GWD
- @C:\PKT\RLI\WB2GWD.FWD
- *** EOF
-
- I am using these scripts with the K3RLI supported version 4.6 of
- W0RLI's "C" program. I do not know if it works with W0RLI's new
- 8.xx version of the program.
-
- 73 John WA3TSW @ WA3TSW