User's Manual
3-2
When the Server receives a SIGN ON message from a RF Terminal, the
Server transmits the SIGN ON information to the host application program..
The host application can then do one of two things:
1. If it has something for the Terminal to do, it can send a prompt to the
Terminal. The RF Terminal receives the prompt, waits for the
operator to enter the requested data, and then transmits the data back
to the application program.
2. If the host program does nothing within an allotted time, the
Terminal displays the message:
WAITING ON HOST PROMPT
Lets suppose that a RF Terminal and a host application program have been
processing data by sending prompts and data back and forth as described in
example 1. The host application program sends a data prompt to the RF
Terminal. The RF Terminal transmits the operator-entered data back to the
Server. If the host application program has another prompt for the
terminal, it sends it out, repeating the process above.
If the host application program doesn't respond immediately, the Terminal
Device displays:
WAITING FOR HOST PROMPT
until the prompt is received.
If the Terminal gets no response after several re-transmissions, it assumes it
is out of range from the Access Point with which it was communicating,
and attempts of establish contact with any Access Point. If the Terminal
can't establish communication with an Access Point, it displays:
TRANSMISSION FAILED
HIT ANY KEY_
Pressing a key on the Terminal starts the re-transmission process over
again. The RF Terminal will try to retransmit its data, displaying the
TRANSMISSION FAILED message after several unsuccessful tries.
Can I change a prompt after it has been sent?
Normally once the Terminal has received a prompt from the host, it goes to
sleep and waits (as long as it takes) for the operator to scan or key
something in response. The host cannot send another data entry prompt
without creating a "Sequence Error." However, you might want to change
the prompt or locate a lost terminal with beeping. You can send an advisory
message as long as it doesn't end with a request for data entry. For example,
maybe you want to send a message "See Supervisor" or 20 beeps to be sure
the unit has not been misplaced and to aid in finding it. It is the user
programmer's responsibility to no overwrite the last data entry prompt, (the
advisory message should go onto the display in lines that are different from
the last data entry prompt.