Worth Data 701 RF Owner's Manual download pdf (Page 55)

Programming Considerations

Network Setup

The network settings on both client and server must support TCP/IP communications.

It is critical that the client and server computers are "visible" to each other across your network. Both computers must have an IP

address in the same subnet. The server requires a static IP address while the Client can either have a static address or use an as-

signed IP address via a DHCP server or equivalent. Refer to your Windows networking administration utility in the Control Panel

to configure computer IP address settings.

PromptNET uses ports 54123 (server) and 54124 (client).

You can link server and client through a dial-up or DSL Internet link as long as the server has a static IP address and your router

passes the above ports.

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 serv-

er 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 intervening SignOut. Multiple SignIns from one termi-

nal without appropriate SignOuts indicate either:

• A terminal going out of range and having its power cycled before returning within range OR

• Two (or more) terminals using the same ID (terminal ID conflict).

1 2 ... 50 51 52 53 54 55 56 57 58 59 60 ... 86 87

No comments

Worth Data 701 RF Owner's Manual Page 55