开云体育

I configured UI-View for "Host Mode NONE", setup the communication
parameters to talk to the right com: port, turned the transceiver and
TNC "on". (I didn't enter a callsign, locatoin or any other parameter
into UI-View...in effect, using it as an RX-only mode).

Immediately, icons appeared (the crowd applauded with approval <g>). It
was then that I attempted to run the terminal window and noticed that
it, too, was RX-only . . . meaning that I couldn't find a way to type in
my own commands that would be heard by the TNC . . . at least not in the
same window as was displaying the received packets. It that my
mistake? Is there another window that becomes "my" window for sending
commands to the TNC? Roger mentions a "single line at the bottom". Am
I simply overlooking it, possibly?

Regards,
Ev, W2EV
--
PropNET: an automated network, designed to
study propagation anomolies. Intreagued?

In article <386F56DB.B1E9B667@...>, Ev Tupis (W2EV)
<propnet@...> writes

Immediately, icons appeared (the crowd applauded with approval <g>). It
was then that I attempted to run the terminal window and noticed that
it, too, was RX-only . . . meaning that I couldn't find a way to type in
my own commands that would be heard by the TNC . . . at least not in the
same window as was displaying the received packets. It that my
mistake? Is there another window that becomes "my" window for sending
commands to the TNC? Roger mentions a "single line at the bottom". Am
I simply overlooking it, possibly?

Host mode NONE - there's a single line at the bottom of the Terminal
window for keying in. Host mode anything else - that line isn't there.
If you change mode, you may need to resize the Terminal window to get
the line to appear/disappear - the slightest resizing movement will do
it.

To reply to two messages at the same time - My main point in suggesting
how to fix the KISS problem was because, as UI-View develops, the use of
terminal mode becomes less desirable.

One of the most technically restrictive features of APRS is the fact
that most of the software works with TNCs in terminal mode. That has
resulted, for instance, in proper use not being made of the frame
destination address, because to change the destination address in
terminal mode means changing the TNC's UNPROTO setting - very clunky to
do dynamically. So the main use of the destination address in APRS is to
advertise the software product in use (although the APRS authors will
tell you that it's for debugging purposes... ;-)

As soon as you start using KISS, or a host mode, problems of this sort
completely go away. It also becomes possible to implement very
intelligent digipeaters in software.

--
Roger Barker, G4IDE roger@...
Boston, UK