| |
ZL4CW > TPK 17.08.96 12:07l 31 Lines 1315 Bytes #-11054 (0) @ WW
BID : 13_ZL4CW
Read: GUEST
Subj: RE TPK BEACONs.
Path: DB0AAB<DB0PV<DB0WGS<OE3XBS<OE6XHG<HG1KZC<HA1VH<HA5KDF<OM0PBB<OK0PKR<
OK0PBB<OK0PAB<OH3RBR<VE4KV<KE0WO<KB0HLO<N0RSE<M0DEM<ZL2TZE<ZL2TZE<
ZL2WA<ZL4AA<ZL4TAY
Sent: 960815/0101Z @:ZL4TAY.#95.NZL.OC #:25224 Bluff 5.15c $:13_ZL4CW
From: ZL4CW@ZL4TAY.#95.NZL.OC
To : TPK@WW
ZL4CW/TPK 1.82 Msg #:13 Date:15-08-96 Time:13:02Z
I should have mentioned in my previous bulletin on TPK BEACONs & CTEXTs
that it is possible to test your beacons manually by typing EX BEACON when
not connected. This will send the beacon, and display it and the sync
request, but please remember that you will now have two timers setup to
send beacons! The first timer was sent by the CONFIG.TPK and the second
timer was sent manually by you.
If you do more manual tests you will have more timers setup!! You could
conceiveably have beacons transmitting at every few minutes, depending on
how many timers you have set up while testing!!!
To list the timers that are waiting type A followed by a carriage return.
If more than one shows up as a beacon timer, then delete them till you have
only one listed as a beacon timer. Don't delete your other script timers if
you have any set up.
To remove the extra timers use the EFA command. If you are deleting a timer
that displays at A 12H25 EX BEACON for example, type EFA 12H25. The other
method is to exit TPK and then re-start it, allowing the CONFIG.TPK file
to set up one beacon timer from scratch, as mentioned in my previous
bulletin.
73 de Geo. ZL4CW@ZL4TAY.#95.NZL.OC
Read previous mail | Read next mail
| |