6-24
•
If you are unsure of how to set up your IP configuration properly,
refer to your network administrator for help.
Client Utility
•
Make sure the Client Utility is properly installed on the client
computer and communicating with at least one Base Station. Test
the Client by cycling power on the Base Station. You should see a
"Base SignOn" message in the monitor window.
Server Communications
•
Run the Server Test Utility on the server computer. Now go to the
client computer, set the IP address for the server computer and a
unique "Base Name" for the Client Utility and attempt to connect
to the Server Test Utility. If the Client Utility connects, you are
configured properly. Go to the server computer, shut down the
Server Test Utility and begin work on your
PromptNET
server
application.
•
For Client/Server communications, the Client Utility is required to
be running on the PC that the serial Base Stations are attached to.
•
Before making any
WDIPterm
method calls in your application,
make sure to set the
ServerOn
property to "true".
Test For Good Communication
•
Implement an event handler for
OnTermBaseRegister
that causes
a beep or displays a message when called. If communication
between the host PC and the base station is good, your event
handler will fire when your program is running and you power up
an attached base station.
Multiple Base Stations
•
For installations using multiple base stations attached to a single
client PC, simply use the four "channels" provided by the Client
Utility program.
Terminal Tracking
•
Since you get only one set of event handlers, you will need some
scheme for keeping track of where each terminal (up to 64 per base
station, up to 4 base stations per client) is in its transaction
sequence. One possible solution is to use a "state" variable for each
terminal (perhaps stored in an array). Test the state variable to
determine the next prompt for any given terminal. See the samples
for more ideas.
•
It is very important to keep track of "login status" for each terminal.
Every SignOut event should have an associated SignIn event and a
given terminal should not be allowed to SignIn twice without and an
