| |
NO8M > KAM 04.03.96 02:30l 32 Lines 1424 Bytes #-11080 (0) @ WW
BID : 23162_NO8M
Read: DF7ML DF7NZ GUEST
Subj: KAM TOR Mode Lockup Problems
Path: DB0AAB<DB0SL<OE3XBS<OE6XHG<HG1KZC<HA1VH<OE1XGR<OK0NKT<OK0PBB<OK0PAB<
OH3RBR<VE4KV<KA6EYH<WB8BII<WA8BXN<NO8M
Sent: 960303/1700z @:NO8M.#NEOH.OH.USA.NA #:23162
I bet Kantronics will fix the KAM TOR-mode lockup problems. It is bad
enough here that we now run just a Pactor port. The lockups increase with
user load and we have quite a load of users.
When the lockups occur, the red LED on the front panel stays on.
For now, if I were to want to maintain the TOR port, I could run the
line from the red LED on the front panel to a 555 timer. That timer could
be set to run ONLY when the LED is on. Should the LED remain on for more
than a certain time ... say 5 minutes ... then the timer would trigger a
second timer that would drop power to the KAM (only) for about five seconds.
That would do a power-down reset on the KAM and things would be back to
normal.
I'm not interested in the above. I have connected from innumerable remote
locations and in each instance my mode of choice (to start with) was Pactor.
AMTOR is too slow and error-prone and GTOR, to work well, likes very good
band conditions. As such, I always started with a Pactor connect. Once
that connect was made, should the band be in great shape, I could then change
to GTOR if I wanted. But the time it took to disconnect and reconnect under
GTOR (due to the radio scanning) negated any time savings in the GTOR over
the Pactor.
73,
Steve
Internet: no8m@apk.net
Amateur Radio: no8m@no8m.#neoh.oh.usa.na
MSYS Mail List: msys-request@hamnet.org ('info' for title)
Read previous mail | Read next mail
| |
