CONNECTING EAS RECEIVERS DATA PORTS TO WIREREADY

Capturing print outs from EAS receivers provides station personnel with a handy way to see message data from any computer in the building running WireReady.  Moreover the WIRE BROWSER provides a day or more history and files may be printed on conventional paper or saved to disk.   In addition, the MANAGER program has the ability to automatically append a TXT file in a specified location on the LAN or local hard-drive.

Connecting EAS receivers follow the same guidelines for connecting any wire service to the CAPTURE station.  This includes
    Getting correct pin-out information for making a data feed cable between the receiver and the computer's
    available COM port.
    Knowing baud rate, parity,stop/start bits, i.e 9600n81
    Configuring either our DOS based manager capture program, or our 32 bit WINCAP capture program to
     capture the data on the port you have hooked up to  (some stations use the DOS based program some use the
     32 bit version - please note you may be running BOTH programs, but if BOTH are running, it's WINCAP that
    must be configured.

1) The major brands of EAS receivers generally have an RS-232 port that spits out the same text they put on the calculator paper they chew through.
2) Each EAS receiver's operator manual provides the pin out information
necessary, most receivers have a DATA and a GRND pin and that is all that
is required.
3) Data goes to Pin 3 and ground goes to Pin 7 on a WireReady 25 pin COM port (for example an available port on the 4 port card).
4) The IT person would then either run WIRE\INSTALL\SETUP if they use our DOS based MANAGER program to capture, or they would run WIRE\INSTALL\SETUP32 if they run the WINCAP program on their capture station. (if they have WINCAP and MANAGER running, WINCAP is still the
capturing program and they'd use SETUP32.)
5) There are two special considerations for this:

If they run the MANAGER based capture program, they will need to locate the $SER.DAT file in their WIRE\INSTALL folder. It can be opened with WORDPAD, and the following line must be present (or it can be added to the file).

GENERIC UR
It must be all caps, and atleast one space between GENERIC and UR
This file must be changed before going into WIRE\SETUP
If they run the WINCAP program, earlier versions of WINCAP may not show the
GENERIC driver choice in SETUP32. This is currently a beta version of
WINCAP and is not in general distribution but widescale availability is
expected sometime in November/December 2001. Anyone needing this before
then can contact WireReady.

6) EAS receivers spit the data out in a non formatted way, such that WireReady cuts a feed to the wirebrowser after 30 seconds of inactivity on the data line. Everytime an EAS receiver generates a message of any length, and there is idle for 30 seconds, a new headline which will say something GENERIC FEED#### and MISC MISC for category and priority will be generated. #### increments.
If a receiver spits out lots of small messages, it can clutter a customer's browser, but if they only spit messages a dozen or so times daily it will integrate nicely and not get in anyone's way. The WireReady alert and alarm searches can also be programmed using the MANAGER program to look for generic feeds based on the headline category and priority, or specific text within the message.