FCC ID: JEH7730GAI Electronic Pricing Transmitter

 

1 Chapter 1: Introduction About This Guide This guide, for DecisioNet System installers and technicians, describes how to install, configure, and service the following DecisioNet System components:

Communication Base Station(s) (CBSs) CBS Power Supply(s) Transmit and receive antennas DecisioNet System software 1-2 Chapter 1: Introduction Chapter Summaries The following is a brief description of each chapter in this guide:

Chapter 1 - Introduction: This chapter provides a brief description of each chapter in this guide and lists additional DecisioNet System documents that are available. Chapter 2 - Preparing the Installation Site: This chapter lists the customer responsibilities, power and environmental requirements, as well as the DecisioNet hardware specifications. Chapter 3 - Installing the Hardware Infrastructure: This chapter describes how to prepare and install CBSs, power supplies, antennas and cabling. Chapter 4 Installing DecisioNet Software on a Windows NT or Windows 2000 System: This chapter contains software installation instructions specific to a Windows NT or a Windows 2000 operating system. Chapter 5 Installing DecisioNet Software on an NCR UNIX System: Delayed Deliverable. Chapter 6 - Configuring the DecisioNet System Environment: This chapter describes how to configure the installed DecisioNet software on Windows NT and Windows 2000 operating systems. Chapter 7 - Testing and Troubleshooting: This chapter describes how to use the available diagnostic tools to analyze and isolate DecisioNet System problems. Chapter 8 - Maintenance: This chapter describes DecisioNet hardware maintenance and replacement procedures. Appendix A - Parts Order Information: This appendix provides information on model codes, available kits and part order numbers. Appendix B - DecisioNet Configuration Files: Listings of the DecisioNet configuration files that may require modification to meet site-specific requirements. Chapter 1: Introduction 1-3 Information Sources If you need additional information about the DecisioNet System, refer to the following documents:

Title DecisioNet User's Guide Document ID B005-0000-1317 DecisioNet Implementation Guide B005-0000-1250 Description This guide, for DecisioNet System software users, describes how to use the software's features and functions. Also included is a section on error messages, error explanations, and corrective actions. This CD provides project management and planning information for site installations. The following document is for NCR internal use only and is available at http://merlin.atlantaga.ncr.com/

Certification/Re-

certification Site Survey Policy 497-0410343 This policy describes how to certify and document a completed installation's site configuration for support purposes. 1-4 Chapter 1: Introduction

 

 

2 Chapter 2: Preparing the Installation Site Preparing the Site This chapter provides the following information:

A summary of customer responsibilities prior to installation Power, grounding, and distribution requirements of the DecisioNet System DecisioNet System environmental requirements DecisioNet System component characteristics 2-2 Chapter 2: Preparing the Installation Site Customer Responsibilities The customer must do or provide the following:

When required by NCR, provide the NCR customer service representative with appropriate drawings that indicate:

Fixture Plan showing the location of store fixtures Floor Plan showing the location of all interior walls, ceiling heights, and firewalls Site wiring diagrams for power and communication Location of other equipment capable of generating electrical noise, electromagnetic interference, heat, etc. Environmental conditions that could affect RF communication Make building alterations necessary to meet wiring and other site requirements Provide and install all communications cables, wall jacks, special connectors, and associated hardware Provide and install necessary power distribution boxes, conduits, grounds, lightning protection, and associated hardware Provide and install auxiliary power or other equipment as required Provide storage or service areas as required Make sure that the environmental requirements discussed in this chapter are met Provide floor coverings and environmental systems that limit or control static electricity build-up and discharge Warning: Make sure all applicable codes, regulations, and laws

(including, but not limited to, electrical, building, safety, and health) are met. Chapter 2: Preparing the Installation Site 2-3 Power, Grounding and Distribution Requirements Voltage transients, line noise, surges, sags, impulses, and spikes can happen routinely or sporadically. When such phenomena occur, protective devices such as surge protectors may help to ensure proper operation of the equipment. Power Requirements The CBS does not have an internal power supply. It receives DC power from an external power supply that can support up to five CBSs. The power supply's output is +24 VDC. Note: Power requirements in EU/EC countries limit the number of CBSs on one power supply to three (3). For maximum system integrity, install the power supply(s) on a dedicated branch circuit from a distribution panel that does not supply any switched inductive loads (motors, air conditioners, etc.). Do not connect anything else to this branch circuit except other DecisioNet System equipment. This branch circuit must remain "live" at all times. Each power supply circuit should consist of three conductors, including separate wires for the line, neutral, and insulated ground connections to the distribution panel. The following are the specifications for the CBS power supply:

Voltage (in) Current (in) Power (in) Frequency Voltage (out) Current (out) 100 to 240 Volts AC 3 Amps 100 Watts 50 or 60 Hz 24 Volts DC 4.5 Amps 2-4 Chapter 2: Preparing the Installation Site Grounding Requirements Because the DecisioNet System connects logic reference ground to safety ground, a noise-free grounding circuit is necessary for good system integrity. Use an isolated ground receptacle, such as a Hubbell IG-5262 or equivalent. Make sure the ground conductor is insulated from conduit and neutral wire, and that it is connected to an insulated terminal strip at the distribution panel. DO NOT use this dedicated insulated ground wire as a neutral. DO NOT use a conduit as a ground. Resistance at the conduit joints may create multiple ground levels within the electrical power distribution system and degrade the reliability of the DecisioNet System. Power Distribution Requirements Be aware of the following power distribution requirements:

All wire connections must be electrically and mechanically sound and protected from deterioration. Deterioration due to corrosion or electrolysis, especially in humid or corrosive atmospheres, may result in electrical noise and/or a safety hazard. Electrical equipment such as wiring and circuit breakers cause voltage drops in the power distribution system. Verify that the voltage at each AC power outlet is within specification. Install AC power outlets in locations that are easily accessible and as close as possible to the equipment they serve. Do not route power cords through openings with sharp edges or in areas where they are exposed to sharp edges or pointy objects. Verify that all applicable national, state, and local codes are met. Chapter 2: Preparing the Installation Site 2-5 The following illustration shows an example of site wiring. Hubbel IG5262 Receptacle or equivalent is recommended Power Supply for CBS 1 through CBS 5 Power Supply for CBS 6 through CBS 10 Power Supply for CBS 11 through CBS 15 Power Supply for CBS 16 through CBS 20 Circuit Breaker 15 A Black (Li) Green (Ground) White (Neutral) Conduit Li N Building Service Entrance Neutral 14494 Note: The distribution panel must not furnish power to any inductive loads such as refrigeration equipment, ovens, and motors. 2-6 Chapter 2: Preparing the Installation Site Environmental Requirements DecisioNet components operate across a wide range of environmental conditions as shown in the following tables. Do not install these components in locations where the temperature or humidity may go beyond the limits indicated. Due to lower atmospheric pressure and air rarefaction at high altitudes, the maximum dry bulb temperature for each working range is decreased linearly by a value of 3.3 C /1,000m (1.8 F /1,000 ft.) between the altitude of 500m (1,640 ft.) and 3,000 m (9,840 ft.). Temperature and Humidity The environmental requirements for the CBS and ESLs are shown in the following tables. CBS Operating 5C to 45C

(40F to 113F) 10C (18F) Transit (1 week maximum)

-40C to 60C

(-40F to 140F) 20C (36F) Storage

-10C to 50C

(14F to 122F) 15C (27F) No Condensation 10%

5% to 95%

No Condensation 10%

10% to 90%

No Condensation 10%

Temperature

(Dry bulb) Max. Temp. Change per Hour Relative Humidity 10% to 90%

Max. Humidity Change per Hour Barometric Pressure 105 to 70 kilo pascals

(up to a max. of 3,000 m [9,850 ft.]) 105 to 70 kilo pascals

(up to a max. of 3,000 m [9,850 ft.]) 105 to 70 kilo pascals

(up to a max. of 3,000 m [9,850 ft.]) Chapter 2: Preparing the Installation Site 2-7 ESL (Standard Size and Small Size) Operating Temperature

(Dry bulb) Max. Temp. Change per Hour Relative Humidity Max. Humidity Change per Hour Barometric Pressure 0C to 40C

(32F to 104F) 10C (50F) 5% to 90%

No condensation 10%

70 kilo pascals (up to a max. of 3,000 m [9,842 ft.]) Transit (1 week maximum) and Storage (3 months maximum)

-30C to 60C

(-22F to 140F) 15C (59F) 5% to 90%

No condensation ESL (Freezer) Temperature

(Dry bulb) Max. Temp. Change per Hour Relative Humidity Max. Humidity Change per Hour Barometric Pressure Operating

-30C to 10C

(-22F to 50F) 40C (104F) 5% to 100%

Condensation 10%

Transit (1 week maximum) and Storage (3 months maximum)

-30C to 60C

(-22F to 140F) 15C (59F) No condensation 5% to 90%

70 kilo pascals (up to a max. of 3,000 m

[9,842 ft.]) 105 kilo pascals (up to a max. of 3,000 m [9,842 ft.]) 2-8 Chapter 2: Preparing the Installation Site ESL (Signage) Temperature

(Dry bulb) Max. Temp. Change per Hour Relative Humidity Max. Humidity Change per Hour Barometric Pressure Operating 0C to 40C

(32F to 104F) 10C (50F) 5% to 90%

No condensation 10%

70 kilo pascals (up to a max. of 3,000 m [9,842 ft.]) Transit (1 week maximum) and Storage (3 months maximum)

-30C to 60C

(-22F to 140F) 15C (59F) 5% to 90%

No condensation Altitude and Temperature The following graph shows how altitude affects the operating temperature of CBSs and ESLs. As altitude increases, the maximum operating temperature decreases. Chapter 2: Preparing the Installation Site 2-9 Maximum operating temperature C ( F) 45 (113) 40 (104) 35 (95) 30 (86) 25 (77) 500

(1,640) 1,000

(3,280) 2,000

(6,560) 3,000

(9,840) Altitude meters

(feet) Health and Safety CBSs meet the following safety and radio frequency interference requirements. ANSI C95.1-1990 UL 1950 3rd Edition UL 2043 CSA CAN/CSA-22.2 No. 950-93 CE mark per TULV FCC CFR, Title 47, Part 15.247 FCC Class A Radiated Emissions FCC Class B Conducted Emissions and CFR 47 Parts 2 and 15 RSP-100, RSS210, ICES-003, C108.9-M1983 MPT 1349 DOC Class A ETS 300 - 440 ETS 300 - 328 ETS 300 - 826 CEPT 70 03 TS 04-1 2-10 Chapter 2: Preparing the Installation Site Component Characteristics CBS The CBS weighs 1.13 kg (2.5 lb.). The following illustration shows the dimensions of the CBS. 287.3 mm

(11.31 in.) Back

.. 38.6 mm

(1.52 in.)

. Top 140.4 mm

(5.53 in.) Front The CBS does not have ventilation holes, but it does require the service clearances indicated in following table. 18827 Direction Top Bottom Right Left Front Back Distance in mm Distance in inches Not applicable Not applicable 127 101.6 101.6 101.6 101.6 5 4 4 4 4 Chapter 2: Preparing the Installation Site 2-11 CBS Power Supply The CBS power supply weighs .85 kg (1.88 lb.). The following illustration shows the dimensions of the CBS power supply. 179 mm

(7 in.) Back 48.8 mm

(1.9 in.) 96 mm

(3.8 in.) Front Top 17069 The CBS power supply has rear ventilation holes, so it requires the air flow and service clearances indicated in the following table. Direction Top Bottom Right Left Front Back Distance in mm 50.8 50.8 50.8 50.8 50.8 50.8 Distance in inches 2 2 2 2 2 2 2-12 Chapter 2: Preparing the Installation Site Antennas Transmit Antenna The transmit antenna has a threaded female standoff and weighs .085 kg (0.19 lb.). The following illustration shows the dimensions of the transmit antenna. 45 mm 1.75 in. 45 mm 1.75 in. 13 mm

.5 in. 17100 Receive Antenna The receive antenna has a threaded female standoff and weighs .085 kg

(0.19 lb.). The following illustration shows the dimensions of the receive antenna. 45 mm 1.75 in. 45 mm 1.75 in. 13 mm

.5 in. 17065 ESLs Chapter 2: Preparing the Installation Site 2-13 ESLs are available in variety of sizes and LCDs. This section describes the physical characteristics of the available ESLs. ESL, Standard Size The 1x8 and 4+8-character standard-size ESLs weigh 0.031 kg (0.068 lb.). Physical dimensions are shown below. Standard-size 1x8 and 4+8-character "freezer" ESLs are available at GCA. They have the same dimensions and weight as non-freezer standard-size ESLs. The text on the serial number label of the freezer ESL is blue. The text on the serial number label of the non-freezer ESL is black. 35 mm

(1.38 in.) 94 mm

(3.70 in.) 7.5 mm

(.29 in.) 9.52 mm

(.37 in.) 14.02 mm

(.55 in.) 18868 2-14 Chapter 2: Preparing the Installation Site ESL, Small Size The 2x5-character small size ESL weighs 0.023 kg (0.05 lb.). Physical dimensions are shown below. 35 mm

(1.38 in. ) 60 mm

(2.36 in.) 7.5 mm

(.29 in.) 9.52 mm

(.37 in.) 14.02 mm

(.55 in.) ESL, Small Signage The 1x6-character small signage ESL weighs 0.068 kg (0.15 lb.). Physical dimensions are shown below. 58.3 mm

(2.3 in.) 160 mm

(6.3 in.) 14.1 mm

(.56 in.) 45 mm

(1.7 in.) 18869 17062 Chapter 2: Preparing the Installation Site 2-15 ESL, Large Signage The 2x6-character large signage ESL weighs 0.16 kg (0.36 lb.). Physical dimensions are shown below. 58.2 mm

(2.3 in.) 12.5 mm

(.49 in.) 84.5 mm

(3.33 in.) ESL Displays and Symbols 216 mm

(8.5 in.) 18870 The ESL displays are shown in the following illustrations. The symbols on the displays are explained in the table following the illustrations. 1x8-Character, Standard Size SALE ENDS kg 18871 2-16 Chapter 2: Preparing the Installation Site 4+8-Character, Standard Size PROMO kg 2x5-Character, Small Size SALE ENDS kg 1x6-Character, Small Signage SALE ENDS kg 18872 18873 18874 Chapter 2: Preparing the Installation Site 2-17 2x6-Character, Large Signage PROMO SALE ENDS UNIT PRICE kg 18875 G Lights when the ESL is out of synchronization for RF communication Lights when the battery is low Customer defined symbol

(Accessible from the Promotions option in ESL Maintenance or from a custom application) UNIT Customer defined symbol PRICE Customer defined symbol SALE Customer defined symbol Customer defined symbol ENDS PROMO Customer defined symbol Cents currency symbol Euro currency symbol kg Kilogram symbol Liter symbol 2-18 Chapter 2: Preparing the Installation Site For ESL configuration information refer to the DecisioNet User's Guide

(B005-0000-1317).

 

 

3 Chapter 3: Installing the Hardware Infrastructure Chapter Overview This chapter describes how to install the DecisioNet hardware infrastructure. This includes the following components:

CBSs CBS power supplies Data and power cables Transmit and receive antennas For information about ordering these parts, refer to Appendix A. After the DecisioNet hardware is installed, the DecisioNet software must be configured and the site must be RF certified. For configuration information, refer to "Chapter 6: Configuring the DecisioNet System Environment" in this guide and the "Certify RF Infrastructure" section of the DecisioNet Implementation Guide (B005-0000-1250). 3-2 Chapter 3: Installing the Hardware Infrastructure Installation Recommendations The most efficient way to install the DecisioNet hardware infrastructure is in one pass through the store. Install the CBSs, antennas, power cables, and data cables all at the same time Label all cables and document labeling for future reference. Neatness makes servicing the system much easier. Allow slack in cables, especially in receive antenna cables. Test the system as it is being installed. Refer to Chapter 7, "Testing and Troubleshooting," for information on testing. Provide AC power that meets NCR requirements for the power supplies. Test wiring as it is installed. Some installation problems are extremely difficult to diagnose later. DecisioNet Release 3.0 requires the RF infrastructure to be connected to the site's DecisioNet Software Controller to test the infrastructure. Refer to the following for information on testing the infrastructure and site certification:

DecisioNet Implementation Guide (B005-0000-1250) DecisioNet RF Certification Utility Guide Certification/Re-Certification Site Survey Policy (497-0410343) Chapter 3: Installing the Hardware Infrastructure 3-3 General Layout Instructions The cable length between any two devices (hub to CBS or CBS to CBS) cannot exceed 100 m (328 ft.). The maximum number of Ethernet levels beyond the primary CBS is three (3). The maximum total cable length is as follows:

Cable Ethernet (primary CBS to last CBS in chain) Power supply to last CBS in the chain Maximum Cable Length 300 m (984 ft.) 162 m (532 ft.) Use only NCR authorized communication cable. Communication cables must be secure and locked into their connectors. The maximum number of CBSs per store is 40 except for model 7730-1013-9090 (Netherlands) which has a maximum of 12 CBSs per store. If the communication cable is routed through an elevator shaft, it must be in a conduit and the conduit must be connected to the building ground. The minimum distance between a communication cable and a fluorescent, neon, or incandescent light is 30 cm (12 in.). Note: The minimum distance from red blown neon-type signs is 9.1 m

(30 ft.). See the Neon Signs section in Chapter 2 of the DecisioNet Implementation Guide for information. All communication cable connections must be protected from electrical and mechanical deterioration. The deterioration of communication cable connections due to corrosion or electrolysis, especially in a humid or corrosive atmosphere, may result in electrical noise. 3-4 Chapter 3: Installing the Hardware Infrastructure The minimum distances between a communication cable and electrical equipment/associated power cables are as follows:

Maximum Rated Circuit Power 1 kVA 2 kVA 5 kVA Over 5 kVA Unshielded Power Cables 30.5 cm (14 in.) 45.7 cm (18 in.) 60.9 cm (24 in.) 152.4 cm (60 in.) Shielded Power Cables 2.54 cm (1 in.) 5.08 cm (2 in.) 15.24 cm (6 in.) 30.48 cm (12 in.) All interconnecting wiring between the Ethernet hub, CBSs, and power supplies is low voltage wiring. This wiring must conform to all local and national electrical codes for the routing of commercial signal wire. Do not route communication cables outside the building. Tools and Supplies DecisioNet infrastructure installers must have access to the tools typically found in an electrician's tool box. Additional tools and supplies an installation team may require are shown in the following table. Tool/Supply Cable ties RJ45 Modular Jacks Ideal Modular RJ45 crimp kit Milwaukee 2.4 V low-torque electric screw driver ESL removal tool Lift truck Ideal LinkMaster CAT5 cable tester Ideal Cat. No. 62-200 Quantity 10 per CBS 2 per cable plus spares 1 1 1 per installer 1 1 Chapter 3: Installing the Hardware Infrastructure 3-5 CBS Installation The following sections describe the preparation, cabling, and installation of the CBS and its related components. CBS Ethernet Cable Connections The Release 3.0 CBS uses a star topology and has an integrated Ethernet hub that can connect to three other CBSs. DecisioNet III supports up to three (3) levels below the primary CBS. This topology results in the 40 CBS maximum mentioned in the General Layout Guidelines section. The following illustration shows an example 40 CBS configuration, its Ethernet cable connections, and the maximum number of CBSs on each level. Primary CBS Uplink C D 1 D C D 2 C D 3 C

+24VDC Power CBS 1 11 87654321 Out 87654321 In 87654321 Out 87654321 In 87654321 87654321 Out Out 87654321 87654321 Out Out Ground 12 87654321 In 87654321 87654321 Out Out Ethernet Hub WS WS WS WS 13 87654321 Out 21 87654321 87654321 87654321 87654321 In Out Out Out 22 87654321 In 87654321 Out 87654321 Out 87654321 Out 87654321 In 87654321 Out 87654321 87654321 Out Out 23 CBS 24-26 CBS 27-29 31 87654321 Out 87654321 In 87654321 87654321 Out Out 32 87654321 Out 87654321 Out 33 87654321 87654321 87654321 87654321 In Out Out Out 87654321 87654321 In Out 34 87654321 87654321 87654321 In Out Out 87654321 Out 87654321 In 35 87654321 Out 87654321 In 87654321 87654321 Out Out 87654321 87654321 Out Out 36 87654321 Out CBS 40-48 CBS 49-57 87654321 In 87654321 Out 87654321 87654321 Out Out 37 38 87654321 87654321 87654321 87654321 In Out Out Out 87654321 In 87654321 Out 87654321 Out 39 87654321 Out 18885 Level 1

( 3 CBSs) Level 2

( 9 CBSs) Level 3

( 27 CBSs) 3-6 Chapter 3: Installing the Hardware Infrastructure CBS Numbering CBSs are identified in the CBS Manager section of the DecisioNet CBS configuration file (DNCBSCONFIG.XML) with a unique number (1-99) and a host name or IP address. Using the numbering scheme shown in the illustration helps identify the level in which the CBS is connected in the topology when running diagnostic tests and analyzing diagnostic logs. This scheme is as follows:

Primary CBS = always 1 Level 1 = CBS 11-13 Level 2 = CBS 21-29 Level 3 = CBS 31-57 CBS configuration details are described the Setting the CBS IP Address section of Chapter 6, Configuring the DecisioNet System Environment. Chapter 3: Installing the Hardware Infrastructure 3-7 CBS Power Supply Cable Connections The CBS Power Supply can support up to five (5) CBSs, however, power requirements in EU/EC countries limit the number of CBSs connected to a power supply to three (3). The following illustration shows an example power supply wiring scheme for a 14 CBS non-

EU/EC configuration. CBS Power Supplies Primary CBS Uplink C D 1 2 3 D C D C D C

+24VDC Power Ground Level 1 Level 2 Level 3 18886 3-8 Chapter 3: Installing the Hardware Infrastructure EU/EC Installations Power requirements in EU/EC countries limit the number of CBSs connected to a power supply to three (3). The following illustration shows power supply cable connections for a 12 CBS configuration using 4 power supplies. This cabling scheme may be extended to support 40 CBSs. CBS Power Supplies Primary CBS Uplink D C 1 D C D 2 C D 3 C

+24VDC Power Ground Level 1 Level 2 Level 3 18887 Chapter 3: Installing the Hardware Infrastructure 3-9 Sample Store Cabling The following illustration shows a non-EU/EC country store layout with 13 CBSs and 3 power supplies. Ethernet and power supply cables originate in the back office and are bundled together to accomplish this configuration. Checkout 21 22 24 25 11 23 12 26 Bakery 27 13 1 Back Office PS1 PS2 PS3 Legend 27 PS1 CBS Cable Power Supply Cable 29 28 Produce Dairy Meat and Deli 18961 3-10 Chapter 3: Installing the Hardware Infrastructure CBS Cables The following cables are supplied by NCR. Cable ID

(Part Number) 1424-Cxxx-0018

(230-0146539) 1424-C057-0180

(230-0134951) 1416-C520-0150

(230-0134953) 1416-C463-9999

(497-0413234) Bulk cable from third-party Bulk cable from third-party Description Transmit antenna cable

(plenum rated) Receive antenna cable

(plenum rated) Receive antenna cable

(plenum rated) CBS power supply pigtail Power cable Data cable Connect From Length m (ft.) 1.8 (5.9) CBS transmit antenna connector 18 (59) CBS receive antenna connector A, B, C, or D 15 (49) CBS receive Connect To Comments Transmit antenna TNC screw-on connector Receive antenna BNC connector Receive antenna BNC connector antenna connector A, B, C, or D CBS power supply AWG 14/2 bulk CBS power supply pigtail CBS CBS cable First of up to five CBSs CBS CBS Included with power supply kit Refer to tables in next section Refer to tables in next section Note: All cables conform to type CL2P. Chapter 3: Installing the Hardware Infrastructure 3-11 Power and Data Cables The power and data cables must be purchased in bulk from a third party. NCR recommends using the Belden cables described in the following table. Comparable cables from other manufacturers are acceptable. The wire colors referenced in the text and illustrations that follow are consistent with the recommended Belden cables. If you are using a comparable cable from another manufacturer, your wire colors may be different. Cable Use Manufacturer Manufacturer Part Number 6100UE Belden Power Power Belden 5100UE Data Data Belden 1585A Belden 1583A Description 2 conductor, 14 AWG stranded, unshielded, plenum rated 2 conductor, 14 AWG stranded, unshielded, non-plenum rated 4 pair, CAT5, 24 AWG solid, unshielded, plenum rated 4 pair, CAT5, 24 AWG solid, unshielded, non-plenum rated Note: When installing into a plenum type ceiling, plenum rated wire may be required by local or national electrical codes. Most suspended ceilings are considered plenums; open ceilings are not. Plenum rated wire typically costs twice as much as non-plenum. Choose the correct wire type based on your applicable local and national electrical codes. For general reference, CBS wiring falls under NEC (National Electrical Code) Class 2 type. 3-12 Chapter 3: Installing the Hardware Infrastructure Power Cable Connectors Each CBS is shipped with a 4-wire connector that plugs into the 8-wire power receptacle. The only tool required to install the power cable into the connector is a small screwdriver. Data Cable Connectors An RJ45 connector is required for each of the CBSs data connectors. The RJ45 connectors must be purchased from a third party. A crimp tool is required to install the data cable into the RJ45 connector. The following table provides information about RJ45 connectors and crimp tools. AMP Manufacturer Manufacturer Part Number 5-557315-1 5-557315-2 5-557315-3 5-557315-4 1-231666-1 33-652 30-560 AMP Ideal Ideal Quantity Description 10,000 (loose) 500 (loose) 1,000 (10 boxes of 100) 1,000 (40 bags of 25) 1 1 1 RJ45, 8-position, unshielded type1 Crimp tool2 Crimp tool2 AMP die for Ideal crimp tool3 1 Use any comparable RJ45 connector compatible with your crimp tool. 2 Use any crimp tool compatible with your RJ45 connector. 3 Necessary only when using AMP connectors and Ideal crimp tool. CBS Connectors and Status Lights Chapter 3: Installing the Hardware Infrastructure 3-13 Uplink C D 1 D C D 2 C D 3 C

+24VDC 87654321 87654321 87654321 87654321 Ground 1 2 3 4 5 6 7 8 Power 18877 Data Connectors The CBS has four data connectors:

Uplink used to connect the in-store hub or a higher level CBS hub 1, 2 and 3 used for downlink connections to lower level CBS hubs Data connector pin and signal use is as follows:

Pins 1, 2, 3, and 6 carry standard Ethernet transmit and receive data between the Ethernet Hub and the primary CBS and between all CBS's as defined in ISO/IEC Standard 8802.3 paragraph 14.5.1. Pins 4, 5, 7, and 8 are used for DecisioNet transmit and receive timing signals between all CBSs. Power Receptacle The following table provides information about the CBS power receptacle. Pins 1, 3, 5, 7 2, 4, 6, 8 Description

+24 VDC Ground Connection Belden Wire Color From CBS power supply to White primary CBS, and CBS to CBS Black 3-14 Chapter 3: Installing the Hardware Infrastructure CBS Status Lights The Ethernet status lights (LEDs) are in the top corners of the data connectors. The Power status light is a red LED shown to the right of the power receptacle in the previous illustration. The CBS status lights indicate the following conditions. LED Power (red) C (green) Ethernet link status D (yellow) Ethernet activity State On Off Blinking On Off Blinking On Off Blinking Meaning OK (power is on) PROBLEM (no power) PROBLEM (intermittent power) OK (good link) PROBLEM (no link) PROBLEM (intermittent link) NOT DEFINED PROBLEM (no receive activity) OK (receive activity) Chapter 3: Installing the Hardware Infrastructure 3-15 CBS Identification NCR Corporation Made in U.S.A Class:

Model:

Part Number:

Date of Mfg:

Serial #:

MAC Address:

24 VDC 0.5A 7730 1011 497-1234567 May 2001 50-1234567 080001357942 19015 The CBS product label identifies the model number, serial number, and unique MAC address of the CBS. The last 6 hexadecimal characters of the MAC address are used to specify the hostname for each CBS in the CBS Manager section of the DecisioNet CBS Configuration file

(DNCBSCONFIG.XML). The hostname format is NCRDNETXXXXXX where XXXXXX is the 6 characters from the MAC address. When you complete the RF infrastructure installation, you need to assign IP addresses and verify CBS communications. Refer to "CBS Hardware Configuration" section at the end of this chapter for details about assigning CBS addresses in your Ethernet network. How to enter the CBS configuration information in the CBS Configuration File is described in the Setting the CBS IP Address section of Chapter 6, Configuring the DecisioNet System Environment. 3-16 Chapter 3: Installing the Hardware Infrastructure CBS Installation Install the CBSs at the same time you install the power cables, data cables, and antennas. The most efficient way to install the DecisioNet hardware is in one pass through the store. The following table and illustration show the CBS and associated hardware. Item Quantity Description 1 CBS 1 2 3 4 5 6 1 2 2 2 2 CBS mounting bracket Universal beam clamp Lock washer Screw ( -20 x Phillips head) Power connector

(installed on CBS ) 2 1 3 4 5 The CBS can be mounted in any position. The mounting bracket and universal beam clamps permit a wide variety of installations. Position the CBS for easy LED and connector access. The following example illustrations show a CBS mounted to a roof truss. 18879 Chapter 3: Installing the Hardware Infrastructure 3-17 Transmit A B C D Receive Warning: The CBS must be mounted securely and installed in accordance with local building codes. The mounting surface must be able to withstand a minimum weight of 2.26 kg (5 lbs.). Caution: DO NOT install a CBS by placing it on a ceiling tile. 18829 The following steps describe a typical installation in which a CBS is mounted to a roof truss as shown in the previous illustration. 1. Use the screws and lock washers to secure the clamps to the mounting bracket. Caution: Vibrations could loosen the screws holding the mounting bracket to the clamps. It is extremely important to place the lock washers on the screws before installing the screws into the clamps. 2. Position the clamps on the roof truss and tighten the clamp screws. 3. Install the CBS into the mounting bracket. Caution: To prevent damage to the transmitter, the transmit antenna must be connected to the CBS before power is applied to the CBS. 3-18 Chapter 3: Installing the Hardware Infrastructure Preferred CBS Mounting Solution 1. 2. D C e v i e c e R B A t i m s n a r T e v i e c e R D C B A t i m s n a r T 1. Attach the CBS Mounting Bracket to the universal beam clamp using the phillips head screws and the tabs on the side of the CBS Mounting Bracket. 19014 2. Attach the clamp to the beam. 3. Insert the CBS as shown in figures 1 and 2. Connecting Ethernet Data Cables From the primary CBS, a data cable connects every secondary CBS in the system as shown previously in CBS Ethernet Cable Connections section. Note that the Uplink data connector is used to connect to a higher level CBS and the data connectors 1, 2, and 3 are used to connect to lower level CBSs. Connecting the Ethernet Hub to the Primary CBS Each store configuration has only one primary CBS. All other CBSs are secondary CBSs. The primary CBS is the one connected directly to the Chapter 3: Installing the Hardware Infrastructure 3-19 Ethernet Hub. Standard 4 pair, CAT5, 24 AWG solid, unshielded, plenum rated cables are required for all Ethernet communications. 1. Locate the Ethernet hub. 2. Cut a length of data cable that is long enough to reach from the hub to the primary CBS. 3. On each end of the data cable, install the wires into an RJ45 connector as shown in the following illustration and then crimp the connector onto the cable. To Ethernet Hub or CBS III Hub RJ45 Connector e 1 To CBS III Hub 8 t e B r o w n / W h i B r o w n t e G r e e n / W h i e B l u e / W h i t e B l u n e

\ W h it G r e g n e a g n O r a O r e 8 t e t e B r o w n / W h i B r o w n G r e e n / W h i e B l u e / W h i t e B l u n e e G r e g n a O r O r a

\ W h it e n g RJ45 Connector e 1 Note: Colors shown are for recommended Belden cables. Your wire colors may be different. 18959 Belden Wire Colors RJ45 Pin 1 2 3 4 Color Orange Orange/White Green Blue/White RJ45 Pin 5 6 7 8 Color Blue Green/White Brown Brown/White 4. Plug the data cable into the Uplink data connector on the primary CBS. 3-20 Chapter 3: Installing the Hardware Infrastructure Connecting Secondary CBSs Follow these steps to connect the secondary CBSs:

1. Cut a length of data cable that is long enough to reach from one CBS to the next CBS. 2. On each end of the data cable, install the wires into an RJ45 connector as shown in the previous illustration and then crimp the connector onto the cable. 3. Plug the RJ45 connector into data connector 1, 2 or 3 and into the Uplink data connector of the next CBS. 4. Repeat steps 1 3 until all secondary CBSs are linked by a data cable. Chapter 3: Installing the Hardware Infrastructure 3-21 Connecting Power Supply Cables Refer to the illustrations in the CBS Power Supply Cable Connections section. Power supply cable routing is store dependent. The power connector provides flexibility to connect additional CBSs in series from one CBS to another or in parallel from a CBS to three other CBSs. Connecting CBS Power Supplies to AC Power Place the CBS power supplies with the host computer system, if possible. Plug all power supplies into a common power strip so that you can power them on and off at the same time for reset purposes. In some cases, cable length restrictions may prevent you from installing all power supplies in the same location. In this case, you need to install a separately switched AC main circuit so that you can still control the power supplies at the same time. If local electrical codes or special circumstances require you to install more than one switched AC main circuit for the power supplies, all the main circuit switches should be in the same easily accessible location. Do not install the CBS power supply in the ceiling. 1. Have an electrician install new AC receptacles if needed. 2. Do not plug the CBS power supply into an AC receptacle until steps 1 6 in the next section are complete and the transmit antenna is connected to the CBS. Connecting CBS Power Supplies to CBSs Each CBS power supply can power up to five CBSs as shown previously in the store configuration illustration. The wiring is the same for each group of up to five CBSs. Follow these steps to connect a CBS power supply to each group of up to five CBSs:

1. Cut a length of power cable that is long enough to reach from the power supply to a CBS. 3-22 Chapter 3: Installing the Hardware Infrastructure 2. Splice the power cable wires to the pigtail supplied with the power supply (black to black and red to white) and then install the provided crimp connectors over the splices. 8 7 3 Black Red 2 White Black White Black 5 4 6 1 Note: Colors shown are for recommended Belden cables. Your wire colors may be different. 18878 3. Plug the connector into the power supply. 4. On the CBS, unplug the power connector. 5. Install the power cable wires into the connector (white into pin 1, 3, 5 or 7 [24 V] and black into pin 2, 4, 6 or 8 [Ground]). Use pins in pairs: 1-2, 3-4, 5-6, 7-8 for each power cable connection at the CBS. 6. Plug the connector back into the CBS. 7. Insert the AC power cable into the power supply's AC receptacle. 8. Connect the AC plug to the AC power source. Caution: To prevent damage to the transmitter, the transmit antenna must be connected to the CBS before applying power to the CBS. CBS Antennas Chapter 3: Installing the Hardware Infrastructure 3-23 Two types of antennas are available for the CBS:

Transmit Receive The transmit and receive antennas look similar, but have the following differences:

The transmit antenna has a screw-on reverse polarity SMA connector and uses cable 1424-C424-0018 to connect to the CBS. The other end of this cable has a reverse polarity TNC connector. The receive antenna has a BNC connector and uses cable 1424-C057-0180 to connect to the CBS. This cable has two BNC connectors. Note: With 100 mW CBSs, a 15 m (49 ft.) receive antenna cable 1416-C520-0150 must be used instead of the usual 18 m (59 ft.) receive antenna cable. Consider the following when installing antennas:

Install the antennas at the same time you are installing the CBSs. On a dropped ceiling, mount the antennas from the T-bars. In an open ceiling, hang the antennas from the roof trusses. When mounting the antenna, face the front of the antenna (the side opposite the cable connector) towards the ESLs, with as few obstructions between it and the ESLs as possible. 3-24 Chapter 3: Installing the Hardware Infrastructure Installing CBS Antennas The transmit antenna and receive antenna kits include the same mounting hardware. The installation procedures for the transmit and receive antennas are the same. Mounting an Antenna on a T-bar Note: Maintain a minimum distance of 9.2 m (30 ft.) between a CBS's transmit and receive antennas. To install an antenna on a dropped ceiling's T-bar:

1. At the desired location, install a T-bar hanger on the T-bar. 2. Screw the antenna onto the T-bar hanger. 3. Route the antenna cable through a 13 mm (1/2 in.) hole in the ceiling tile or route it between the T-bar and the edge of the ceiling tile. Note: Do not allow debris from the ceiling tile to fall into the antenna connector. 4. Install the cable onto the antenna connector. 5. Connect the other end of the antenna cable to the CBS. 6. Use cable ties to secure the antenna cable. Chapter 3: Installing the Hardware Infrastructure 3-25 17203 3-26 Chapter 3: Installing the Hardware Infrastructure Securing an Antenna to a Wall Note: Maintain a minimum distance of 9.2 m (30 ft.) between a CBS's transmit and receive antennas. To install an antenna on a wall (or other flat object):

1. Place the lock washer on the bolt, put the bolt through the appropriate hole in the bracket and screw the bolt into the antenna. 2. Screw the bracket into the wall. 3. Connect the antenna cable to the antenna. 4. Connect the antenna cable to the CBS. 5. Use cable ties to secure the antenna cable to the structure. 17204 Chapter 3: Installing the Hardware Infrastructure 3-27 Hanging an Antenna from a Roof Truss Note: Maintain a minimum distance of 9.2 m (30 ft.) between a CBS's transmit and receive antennas. To hang an antenna from a roof truss (or other object) refer to the illustration on the following page and these instructions:

1. Screw the threaded rod into the antenna. 2. Connect the antenna cable to the antenna. 3. Secure the antenna cable to the threaded rod using three equally spaced cable ties. 4. In the desired location, hold the antenna cable against a roof truss and lower the antenna to the desired height. 5. Use a cable tie to hang the antenna cable from the roof truss. Caution: Antenna cables must be secured to a roof truss as shown in the following illustration. Do not allow an antenna to hang from a CBS's connector as the connector cannot withstand the weight of the threaded rod, cable, and antenna. 6. Connect the antenna cable to the CBS. 7. Use cable ties to secure the antenna cable. Caution: This device is required to comply with FCC RF exposure requirements for mobile transmitting devices. A separation of 20 cm (8 inches) or more must be maintained between the antenna and all persons during device operation to satisfy RF exposure compliance.

3-28 Chapter 3: Installing the Hardware Infrastructure 17202 CBS Hardware Configuration Chapter 3: Installing the Hardware Infrastructure 3-29 After all RF infrastructure components have been installed and the Ethernet cabling and power supply cabling has been circuit tested for continuity, the system can be powered-up to establish the connection between an Ethernet network and the DecisioNet CBS units. Configure the DHCP Service Obtain the MAC address from each CBS product label. Use one of the following to obtain IP addresses for the CBS Units. Dynamic or automatic IP allocation where there exists an automatic DNS link. Manual IP allocation is there is no automatic DNS link. For these stores, a block of addresses are assigned to the site. Select a unique IP address from the site block to identify each CBS. Manual Allocation on a Windows NT Server 1. Start the system and Log in as Administrator. 2. Click the Start icon at the bottom left of the screen. 3. Select Programs > Administrative Tools (Common) > DHCP Manager The DHCP Manager (Local) screen displays. 3-30 Chapter 3: Installing the Hardware Infrastructure 4. Highlight the Server IP address and select Scope > Add Reservations. The Add Reserved Clients dialog displays. Chapter 3: Installing the Hardware Infrastructure 3-31 5. Enter the next available IP Address in the IP Address entry box. 6. Enter the MAC address from the CBS serial number label in the Unique Identifier field 7. Enter the DecisioNet Host Name in the Client Name field. 8. Click the Add button. 9. Repeat steps 5 - 8 for each installed CBS. 10. When finished with the last CBS, click the Close button. 11. On the DHCP Manager screen, highlight the Server IP address and select Scope > Active Leases. The Active Leases dialog displays showing IP address reserved for your site. 3-32 Chapter 3: Installing the Hardware Infrastructure 12. Click the OK button. 13. Enter these IP addresses or host names in the DecisioNet CBS Configuration file. Refer to the Setting the CBS IP Address section of Chapter 6, Configuring the DecisioNet System Environment. Verify Communication Links Use the following procedures to verify your communication links. 1. Power-up each CBS. 2. Verify that each CBS link status LED is lit. 3. Use the Ping utility to verify connectivity. 4. Use Notepad and view the hosts file in the

\WINNT\system32\drivers\etc\ directory to determine if all the CBS IP Addresses and host names are listed in the file. Chapter 3: Installing the Hardware Infrastructure 3-33 Sample HOSTS file:

# Copyright (c) 1993-1995 Microsoft Corp.

# This is a sample HOSTS file used by Microsoft TCP/IP for Windows NT.

# This file contains the mappings of IP addresses to host names. Each

# entry should be kept on an individual line. The IP address should

# be placed in the first column followed by the corresponding host name.

# The IP address and the host name should be separated by at least one

# space.

# Additionally, comments (such as these) may be inserted on individual

# lines or following the machine name denoted by a '#' symbol.

# For example:

# 102.54.94.97 rhino.acme.com # source server

# 38.25.63.10 x.acme.com # x client host 127.0.0.1 localhost 172.164.48.3 SERVER 172.164.48.10 NCRDNETXXXXXX

 

 

4 Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System System Environment for Windows NT The DecisioNet System requirements are as follows:

A PC with an Intel 800 MHz or higher processor Minimum memory: 128 MB Minimum hard disk space: 10 GB CD-ROM Drive Color CRT (VGA) Mouse RS-232 Port Ethernet Wedge Keyboard Scanner (for reading ESL serial numbers) Windows NT 4.0 (Service Pack 6) or Windows 2000 (Service Pack 1) Remote access software, such as Timbuktu or pcAnywhere 4-2 Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System

`DecisioNet Software for Windows NT and Windows 2000 The DecisioNet software for Windows NT and Windows 2000 is provided on CD-ROM. Name DecisioNet Base Software for NT/2000 DecisioNet Base Runtime Package DecisioNet Standalone Item Maintenance DecisioNet Scan-Merge Package for Windows NT/2000 DecisioNet Merge Utility DecisioNet OPC Utility DecisioNet Application Development Environment for Windows NT/2000 LPIN G370-1938-0000

(GCA deliverable) G370-1944-0000 G370-1941-0000

(Controlled) DecisioNet Software Installation The following sections describe how to install DecisioNet software on a Windows NT or a Windows 2000 system. After installation, refer to Chapter 6, Configuring the DecisioNet System Environment for any additional information you may need. Before installing the DecisioNet software, make sure the hard disk has at least 35 megabytes of free space. Additional space is required for the DecisioNet MySQL database. Make sure all programs are stopped before installing the software. Note: Before installing new DecisioNet 3.0 software, remove any old DecisioNet 3.0 software from the system. Refer to the Uninstalling DecisioNet Software section for details. Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System 4-3 Installing the Base Software Package Follow these instructions to install the Base Software Package. These instructions assume that Windows NT or Windows 2000 is already installed. 1. Log in as Administrator. 2. Click the Start icon at the bottom left of the screen. 3. Select Run. 4. Insert the Base Software for Windows NT/2000 CD in your CD-

ROM drive. 5. Use the Browse button to locate the SETUP.EXE file on the CD. Select this file and select Open. The path and file name display in the Run dialog. 6. Select the OK button or press Enter to start the installation. The installation displays a series of screens in the following sequence. A Welcome screen appears. Click Next to continue the installation or Cancel to quit. A License Agreement screen appears. Click Accept to continue the installation or Decline to quit. Enter the destination Install Folder. Select the default (dnet/) or select Browse to locate the destination directory of your choice. It is recommended to accept the default. If all your information is correct, click Install on the Ready to Install screen or Cancel to quit. The software begins installing to the destination directory. If DecisioNet was previously installed on your system, you are prompted about replacing three configuration files

(dncbsconfig.xml, dnconfig.xml, and dnhostbridge.xml). At each prompt, click Yes to replace the existing file or No to keep you existing files. Keeping the existing files eliminates the need to re-configure following installation. 4-4 Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System After all files are installed, the Finished screen displays indicating a successful install. Customer-specific configuration settings are required before rebooting the system to Chapter 6, Configuring the DecisioNet System Environment, for instructions on how to configure and start the DecisioNet software. Click Finish or press Enter. Installing the Scan-Merge Package Install the Scan-Merge Package software using the following set of instructions. 1. Click the Start icon at the bottom left of the screen. 2. Select Run. 3. Insert Scan-Merge Package CD in your CD-ROM drive. 4. Use the Browse button to locate the SPSETUP.EXE file on the CD. Select this file and select Open. The path and file name display in the Run dialog. 5. Select the OK button or press Enter to start the installation. The installation displays a series of screens in the following sequence. A Welcome screen appears. Click Next to continue the installation or Cancel to quit. A License Agreement screen appears. Click Accept to continue the installation or Decline to quit. Enter the destination Install Folder. Select the default (\dnet) or select Browse to locate the destination directory of your choice. It is recommended to accept the default. A Print Package Executable screen appears. Enter the location and executable name of the print package program installed on your PC. Click Next to accept the default (c:\program files\bartender\bartend.exe), or select Browse to locate and identify the print package on your PC. Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System 4-5 On the Serial Device Port Assignment screen, you may select the default scanner port (COM1) or identify a different serial device port where the scanner is to be connected when downloading scan files. Click Next to continue or Cancel to quit. If all your information is correct, click Install on the Ready to Install screen or Cancel to quit. The software installs to the destination directory. After all files are installed, the Finished screen displays, Click Finish or press Enter. Installing the Application Development Environment Package Note: This is a controlled software package intended for NCR and NCR Partner software developers who are integrating DecisioNet into an existing price management system. Install the Application Development Environment Package software using the following set of instructions. 1. Click the Start icon at the bottom left of the screen. 2. Select Run. 3. Insert Application Development Environment Package for Windows NT/2000 Package CD in your CD-ROM drive. 4. Use the Browse button to locate the ADESETUP.EXE file on the CD. Select this file and select Open. The path and file name display in the Run dialog. 7. Select the OK button or press Enter to start the installation. The installation displays a series of screens in the following sequence. A Welcome screen appears. Click Next to continue the installation or Cancel to quit. 4-6 Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System A License Agreement screen appears. Click Accept to continue the installation or Decline to quit. Enter the destination Install Folder. You may select the default

(dnet\) or select Browse to locate the destination directory of your choice. If all your information is correct, click Install on the Ready to Install screen or Cancel to quit. The software installs to the destination directory. After all files are installed, the Finished screen displays, Click Finish or press Enter. Uninstalling DecisioNet Software Perform the following steps to uninstall DecisioNet 3.0 Base Software package. 1. Click on the Start icon. 2. Select Programs > DecisioNet > Stop DecisioNet Applications. 3. Stop the MySql application. At a DOS prompt enter the following:

net stop mysql A message displays to indicate MySql is stopped. 4. Click on Start. 5. Select Programs > DecisioNet > Uninstall DecisioNet Base Software. Perform the following steps to uninstall the DecisioNet Scan-Merge package. 1. Click on Start. 2. Select Programs > DecisioNet > Uninstall DecisioNet Scan process. Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System 4-7 Configuring the DecisioNet System After the software is installed, refer to Chapter 6, Configuring the DecisioNet System Environment, for instructions on how to configure and start the DecisioNet software.

 

 

5 Chapter 5: DecisioNet Software Installation on an NCR UNIX System (Delayed Deliverable) System Environment for NCR UNIX The DecisioNet System requirements are as follows:

A PC with an Intel 800 MHz or higher processor Minimum memory: 128 MB Minimum hard disk space: 10 GB CD-ROM Drive Color CRT (VGA) Mouse RS-232 Port Ethernet NCR UNIX SVR 4, MP-RAS (Ver. 3.02 or later) Remote access software, such as Timbuktu or pcAnywhere 5-2 Chapter 5: DecisioNet Software Installation on an NCR UNIX System (Delayed Deliverable) DecisioNet Software for NCR UNIX The DecisioNet software for NCR UNIX is provided on tape cartridges. Name DecisioNet Base Software for MP-RAS Base Runtime Package Standalone Item Maintenance Package Name eplbaseap saplumexe LPIN G370-1940-0000

 

 

6 Chapter 6: Configuring the DecisioNet System Environment Overview This chapter describes how to configure the DecisioNet System environment after the software is installed. Configuration is accomplished using an ASCII editor, such as Windows Notepad, and editing the parameters in the configuration files listed below. All of these files are located in the /dnet/data directory following installation. DecisioNet CBS Configuration files (dncbsconfig.xml) DecisioNet Configuration File (dnconfig.xml) DecisioNet Host Bridge Conguration file (dnhostbridge.xml) DecisioNet Task Manager Configuration file (taskman.cfg) Three of these files are in XML format. XML is a mark-up language that enables different programs to understand the structure of a file. This facilitates the exchange of information between programs. When editing these XML format files, care must be taken to only modify the parameter or option setting. The fourth file listed is the Task Manager file. This is not an XML format file, but still may be modified using an ASCII editor. Details are provided in the following sections on how to access and change parameters in these files. 6-2 Chapter 6: Configuring the DecisioNet System Environment XML File Format XML files use element tags to identify the specific entries or sections within the file. It is very important that the element tags not be modified. When changing parameters with an ASCII editor, you need to locate the parameter in the file and change the parameter setting to one specific to your site. The following shows the first part of the DecisioNet Configuration file (dnconfig.xml). The shaded areas identify the formatting information that should not be changed.

<?xml version="1.0"?>

<!DOCTYPE config SYSTEM "dnconfig.dtd">

<config>

<section name="Ipc">

<!-- <param name="ServerIP">127.0.0.1</param> -->

<param name="TraceLevel">0</param>

</section>

<!-- * LogTally Manager Configuration parameters * -->

<section name="LogTally Manager">

<!-- Section: LogTally Manager -->

<!-- SystemLogging -->

<!-- Specifies whether or not to log to the OS system log. d -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

<param name="SystemLogging">Y</param>

Identifying a Parameter in an XML Format File All information inside of a greater than (<) and less than (>) symbol is part of the mark-up language and should not be changed. Only the parameter entry can be changed and still have the file function properly. A parameter entry is identified as follows:

<param name="SystemLogging">Y</param>

Chapter 6: Configuring the DecisioNet System Environment 6-3 Notice the parameter that may be changed is pointed to by the ending less than symbol (>) of the parameter name tag and the beginning greater than symbol (<) or the parameter close tag (</param>). In this example, the parameter that can be changed is the bolded Y character . Commented Information Comments are identified with comment tags, <!-- at the start of a line and --!> at the end of the line. Some parameters are commented out as is shown in for the ServerIP parameter in the previous example. Before you can use a commented out parameter, you must remove the comment tags at both ends of the line. Using an Editor to Locate a Parameter This section described how to use Notepad to open the DecisioNet Configuration file (dnconfig.xml) and use the search option to locate and change a specific parameter. 1. Click the Start icon at the bottom left of the screen. 2. Select Programs > Accessories > Notepad. 3. In Notepad, select File > Open 4. Use the Open dialog to locate the dnet/data directory. 5. Use the drop down arrow and change the Files of Type: selection to All Files (*.*). 6. Select the dnconfig.xml file and click Open. 7. Select Search > Find and then enter the parameter name you want to locate and change in the Search dialog Find What: entry box. 8. Click the Find Next button. If you locate the parameter name in the comments area of the parameter you are looking for, click the Find Button again. For example, if you searched for MaxNumberUpdateRetries, the parameter name entry that you are looking for would look as follows:

6-4 Chapter 6: Configuring the DecisioNet System Environment

<param name="MaxNumberUpdateRetries">10</param>

9. Edit the parameter as needed and click File > Save to save the change. Configuration File Comments Configuration files contains comments to describe each parameter. The following example shows the "Maximum Number of Bedcheck Retries"

parameter from the ESL Manager section of the DecisioNet Configuration file.

<!-- Section: ESL Manager -->

<!-- MaxNumberBedcheckRetries -->

<!-- Maximum number of times an Bedcheck request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 10 -->

<param name="MaxNumberBedcheckRetries">10</param>

All of the configuration file parameters and their defaults are listed in this chapter to assist you to search, locate and change site-specific parameters. Refer to Appendix B: DecisioNet Configuration Files and read the specific parameter comment section for details about each parameter. Chapter 6: Configuring the DecisioNet System Environment 6-5 Setting Performance Boost in Windows NT 4.0 Following installation, set the foreground and background applications to get equal time. 1. Select the Control Panel from the Settings menu from the Start icon. 2. Choose the System icon. 3. Click on the Performance tab. 4. Slide the Boost Selector to None to indicate No Performance Boost. 5. Click on Apply to accept these changes. 6. Click on OK in the Performance Dialog Box. 7. Close the Control Panel. Configure the system as described in this chapter, beginning with the section Configuring the CBS Communications. 6-6 Chapter 6: Configuring the DecisioNet System Environment Configuring the DecisioNet System After installing new software, you must configure the following DecisioNet System parameters for your store's environment:

CBS address configuration Site-specific DecisioNet software application configuration CBS Configuration DecisioNet 3.0 uses Ethernet to communicate with CBSs installed at your site. Each CBS must have a unique number and host name or IP address specified in the DecisioNet CBS Configuration file

(dncbsconfig.xml). Refer to the "CBS Hardware Configuration"

section in Chapter 3, Installing the Hardware Infrastructure for details about setting IP addresses and host names. Hostname The hostname format is as follows:

ncrdnetnnnnnn.<domain>

where:

nnnnnn is the last 6 digits of the MAC address that is listed on the serial number label of the CBS. IP Address The IP address format is as follows:

xxx.xxx.yyy.z where, depending on the type of IP adressing:

xxx represents network IDs yyy is the subnet ID z is the host ID Chapter 6: Configuring the DecisioNet System Environment 6-7 A unique number (1-99) is assigned to the CBS during RF infrastructure installation as described in the CBS Installation section of Chapter 3 in this guide. Whether you use a hostname or IP address is determined by the type of Ethernet environment in your store. Static IP Addressing For stores that use static IP addressing, a block of addresses are assigned to the site. Check with the local IT Administrator concerning the network addressing scheme used in the store. Unique IP address are selected from the site block to identify each CBS used at the site. Dynamic IP Adressing For sites that use a DHCP Server and use Auto DNS to dynamically assign IP addresses, hostnames would be used to identify the CBSs used at the site. Setting CBS Parameters Use an ASCII text editor as described earlier in this chapter to open the DecisioNet CBS Configuation File (dncbsconfig.xml). The default file looks as follows:

<?xml version="1.0"?>

<!DOCTYPE cbsconfig SYSTEM "dncbsconfig.dtd">

<cbsconfig>

<cbs>

<id>1</id>

<hostname>ncrdnetnnnnnn.atlantaga.ncr.com</hostname>

</cbs>

</cbsconfig>

1. Depending on the number of CBSs that you have at your site, copy and paste the outlined section of the file to create a <cbs> section for each CBS. 6-8 Chapter 6: Configuring the DecisioNet System Environment 2. Edit the <id> parameter to identify a unique number (1-99) for each CBS. 3. Edit the <hostname> parameter to identify the IP address and domain name, or a host name and domain name for each CBS. 4. Save the file. CBS Number 1 11 12 13 CBS MAC Address 08000E382EE7 08000E383B45 08000E39412E 08000E39C245 For example, if your site had a domain name of STORENET and CBSs installed as shown in the table above, the DNCBSCONFIG.XML file would be as follows:

<?xml version="1.0"?>

<!DOCTYPE cbsconfig SYSTEM "dncbsconfig.dtd">

<cbsconfig>

<cbs>

<id>1</id>

<hostname>ncrdnet382EE7.STORENET</hostname>

</cbs>

<cbs>

<id>11</id>

<hostname>ncrdnet383B45.STORENET</hostname>

</cbs>

<cbs>

<id>12</id>

<hostname>ncrdnet39412E.STORENET</hostname>

</cbs>

<cbs>

<id>13</id>

<hostname>ncrdnet39C245.STORENET</hostname>

</cbs>

</cbsconfig>

Chapter 6: Configuring the DecisioNet System Environment 6-9 Application Configuration Site-specific application parameters are defined in the following three files:

DecisioNet Configuration file (dnconfig.xml) DecisioNet Task Manager configuration file (taskman.cfg) Decisionet Host Bridge Configuration file (dnhostbridge.xml) Note: This section identifies the parameters in the first two files. Changes to the Host Bridge Configuration file are typically done by the programming team to match the site-specific requirements of the Custom Data Reader. Details about changing the Host Bridge Configuration file are included in the "Host Bridge Utility Guide" on the DecisioNet Implementation Guide (B005-0000-1250). Inter-Process Communication (IPC) DecisioNet Configuration file (dnconfig.xml) The DecisioNet Configuration contains the following sections with parameters specific to the individual DecisioNet software module. Log and Tally Manager CBS Manager ESL Manager DecisioNet Console Data Reader The following tables show each parameter and the default value following software installation. IPC Section Parameter ServerIP TraceLevel Default 127.0.0.1 0 6-10 Chapter 6: Configuring the DecisioNet System Environment Log and Tally Manager Section Parameter SystemLogging CheckAction MaxTallies TallyUpdateFrequency TraceLevel TraceFile EventsMax EventsNumberToRemove EventsDaysToRemove HandleEmail HandleAlarm HandleConsole HandleSystemTray HandleExecProcess HandlePager HandleEslTag HandleThirdParty HandleSnmpTrap ManualTagLinkID ManualTagLinkType PagerTagLinkID PagerTagLinkType CBS Manager Section Parameter MaxWorkerThreads MaxConnectionsPerCBS TODUpdateFrequency NumberCBSAttempts NumberESLAttempts BroadcastSends Default Y Y 50 10 0 dnltmanager.trc 10000 1000 30 Y Y Y Y Y Y Y N N MANUAL 99 PAGER 98 Default 20 10 60 3 5 5 Chapter 6: Configuring the DecisioNet System Environment 6-11 Parameter ConnectTimeout ResponseTimeout MaxFailureFrequency TallyUpdateFrequency ResultTableExpirationTime BufferFullAttempts BufferFullPause CBSBusyAttempts CBSBusyPause QuickFind SimulationMode StoreID TraceLevel TraceFile Default 10 15 15 60 60 20 2 20 2 1 0 255 0 cbsmanager.trc ESL Manager Section For all recurrence or lifetime settings:

P=period xY=year xM=month T=time xH=hour xM=minutes xS=seconds xD=day where x = length of time For all start date settings, format is YYYYMMDDhhmmss Parameter PeriodicVerify VerificationRecurrence VerificationStartDate PeriodicExistenceBedcheck ExistenceBedcheckRecurrence ExistenceBedcheckStartDate PeriodicHardwareBedcheck HardwareBedcheckRecurrence HardwareBedcheckStartDate Default 0 P0Y0M0DT1H0M0S 20000101000000 0 P0Y0M7DT0H0M0S 20000101000000 0 P0Y1M0DT0H0M0S 20000101000000 6-12 Chapter 6: Configuring the DecisioNet System Environment Parameter PeriodicSumcheckBedcheck SumcheckBedcheckRecurrence SumcheckBedcheckStartDate TransactionRecordLifetime SuccessfulSpoolRecordLifetime ErroredSpoolRecordLifetime MaxNumberUpdateRetries MaxUpdateRetryPeriod MinNumberUpdateRetries MinUpdateRetryPeriod MaxNumberBedcheckRetries MaxBedcheckRetryPeriod MinNumberBedcheckRetries MinBedcheckRetryPeriod MaxNumberFindRetries MaxFindRetryPeriod MinNumberFindRetries MinFindRetryPeriod MaxNumberAssignRetries MaxAssignRetryPeriod MinNumberAssignRetries MinAssignRetryPeriod MaxNumberForceSearchModeRetries MaxForceSerchModeRetryPeriod MinNumberForceSearchModeRetries MinForceSerchModeRetryPeriod MaxCBSUpdateResponseWait SumcheckCorrectiveAction PingUnresponsiveTags IgnoreUnresponsiveTags AutoFindAfterNoResponse SearchModeAfterNotFound AutoAssignAfterFind ForceSearchModeAfterFindFail UnresponseTagRecurrence Default 0 P0Y0M1DT0H0M0S 20000101000000 P0Y0M0DT2H0M0S P0Y0M0DT0H1M0S P0Y0M3DT0H0M0S 10 PT10M 2 PT1S 10 PT10M 2 PT1S 2 PT5M 0 PT1S 10 PT10M 2 PT1S 10 PT10M 2 PT1S PT5M 1 1 1 1 1 1 1 P0Y0M1DTH0M0S Chapter 6: Configuring the DecisioNet System Environment 6-13 Parameter UnresponsiveTagStartDate PriceChecking DefaultUpdatePriority DefaultBedcheckPriority DefaultVerifyPriority DefaultFindPriority DefaultAssignTimeslotPriority DefaultForceSearchModePriority TransactionResolveSleepTime TransactionThreadSleepTime SpoolLogThreadSleepTime ProcessingThreadSleepTime MaxHistoryDepth MaxAutofindSequence MaxPricecheckCorrectiveDepth MaxTransactionRecordBlock MaxESLTransactionRecordBlock MaxESLRecordBlock MaxUpdateImageBeforeRefresh OperatingMode Default 20000101000000 1 3 5 7 10 3 3 50 500 200 0 10 1 3 128 128 128 P0Y0M7DTH0M0S NORMAL DecisioNet Console Section Parameter TraceFileName TraceLevel PrintOverlaysEnabled ForcePrintEnabled PriceLevelPresent ProductUnitPresent ESLDefaultToProduct ReportSQL1 ReportSQL1SelectColumn ReportSQL1KeyColumn Default dnConsoleTrace.trc 0 1 0 1 1 1

(Details for Report 1) 1 3 6-14 Chapter 6: Configuring the DecisioNet System Environment Parameter ReportSQL1Button ReportSQL2 ReportSQL2SelectColumn ReportSQL2KeyColumn ReportSQL2Button ReportSQL3 ReportSQL3SelectColumn ReportSQL3KeyColumn ReportSQL3Button ReportSQL4 ReportSQL4SelectColumn ReportSQL4KeyColumn ReportSQL4Button ReportSQL5 ReportSQL5SelectColumn ReportSQL5KeyColumn ReportSQL5Button Data Reader Section Parameter PriceDecimalPosition UnitPriceDecimalPosition DebugFilename DebugLevel PriceLessThanDollar UnitPriceLessThanDollar DecimalSymbol RoundingType Default 1

(Details for Report 2) 1 4 1

(Details for Report 3) 0 2 0

(Details for Report 4) 0 3 0

(Details for Report 5) 0 3 0 Default 2 2 DataReaderServer.log 2 CentSign LeadingZero Comma Normal Chapter 6: Configuring the DecisioNet System Environment 6-15 DecisioNet Task Manager (taskman.cfg) The DecisioNet Task Manager starts as a service and automatically starts DecisioNet applications as tasks. The Task Manager configuration file (taskman.cfg) specifies how to manage the DecisioNet tasks. The table lists each parameter and the installed default. This is not an XML format file. You can still use an ASCII editor to search for the parameter and then change the default. The format of the parameter setting is:

<PARAMETER>=<SETTING>

For example:

KILLINTERVAL=15 Parameter FREQUENCY KILLINTERVAL DEADCHECK EXCEPTION CONTEXT TFILES CONTEXT TFILES Default Setting 1 15 3 excphdlr.exe -v DNET dnet.tm\*.inf TASK_MANAGER taskman.tm\*.inf Starting a Windows NT DecisioNet System DecisioNet Release 3.0 software is configured to start as an automatic service when you re-boot your system. When you have finished setting configuration parameters, re-boot the system so all DecisioNet environment variables and system options at set. After the system re-boots, use the following procedure to start the DecisioNet Console. 1. Click on the Start icon. 2. Select Programs > DecisioNet > DecisioNet Console. 6-16 Chapter 6: Configuring the DecisioNet System Environment Chapter 6: Configuring the DecisioNet System Environment 6-17 About Passwords You must enter a Username and Password to access the DecisioNet Console. The default Username is system and the default password is manager. To protect the DecisioNet System from unauthorized access, it is recommended that you change the password on the system Username to a password other than manager once you have installed the system. Maintaining Username/ Password You can add, change, or delete a Username and Password by using a MySQL database editor and editing the User table in the DNET database. The following example shows how to use the FreeMascon database editor to add a new user. 1. Start the FreeMascon database editor. 2. Select localhost to display the available databases. 6-18 Chapter 6: Configuring the DecisioNet System Environment 3. Select DNET to display the DecisioNet database tables. 4. Do one of the following to open the DecisioNet users table:

Double-click on the users table icon, or Click the users table icon to highlight it and then click Open at the lower left corner of the screen. The initial entry in the table is the default Username

(OS_USER_NAME), system, and the default Password (PASSWORD), manager. 5. Click the + (plus) icon on the bottom of the screen to add a new record. 6. Enter the new user information. The maximum length of each field is 25 characters. Chapter 6: Configuring the DecisioNet System Environment 6-19 7. Enter other users as needed. 8. Close the FreeMascon editor when finished.

 

 

7 Chapter 7: Testing and Troubleshooting CBS Diagnostics and Troubleshooting The information in this chapter assists trained NCR Customer Service personnel or other trained personnel in analyzing and isolating problems with the DecisioNet System. Ethernet Communication Diagnostic Tools Tools available for diagnosing Ethernet communication include the Windows NT utilities such as:

arp (ARP table query) Displays ARP table contents (ARP cache association between MAC Address and IP Address) Permits permanent ARP table entries ipconfig (IP configuration query) Displays current PC IP configuration for the system (Not the CBS) netstat (network status query) Displays protocol statistics and current connection information ping (connection query) Displays network traffic at the packet level Network Monitor Displays network traffic at the packet level Performance Monitor 7-2 Chapter 7: Testing and Troubleshooting Displays network performance information graphically CBS Communications Diagnostic Tools The following DecisioNet diagnostics are available:

Status lights (LEDs) on the CBS dncbsmtest (CBS manager test tool) Obtain configuration information from CBS Obtain CBS diagnostic information Obtain CBS tallies Configure CBS parameters Configure RF parameters Configure frequency hopping tables System Error Log Windows NT/2000 System Event Log For error code descriptions refer to Chapter 10, "DecisioNet System Messages," in the DecisioNet User's Guide (B005-0000-1317). Site-specific RF Certification Reference During the initial installation, site-specific documents are created as specified in the Certification/Re-Certification Site Survey Policy

(497-0410343). These documents, provided to the DecisioNet Technical Support Specialist at your area Managed Care Center, include the following information:

Store blueprint with RF infrastructure Site certification test data Site photos Installation site survey forms Chapter 7: Testing and Troubleshooting 7-3 The Managed Care Center can perform the DecisioNet System software testing and troubleshooting described in this chapter. For additional information about site certification, refer to the RF Certification Utility Guide on the DecisioNet Implementation Guide

(B005-0000-1250). Available training for the DecisioNet System includes a class on hardware and a class on implementation. 7-4 Chapter 7: Testing and Troubleshooting Ethernet Communication Diagnostic Tools arp (ARP table query) This Windows NT utility is run from the command line and displays ARP table contents showing the ARP cache association between MAC Addresses and IP Addresses. You can also make permanent ARP tables entries. Command line parameters are as follows:

ipconfig (IP configuration query) This Windows NT utility displays current IP configuration for the In-

store processor or computer where DecisioNet is installed. It does not show IP configuration information for the DecisioNet CBS units. Chapter 7: Testing and Troubleshooting 7-5 netstat (network status query) This Windows NT utility displays protocol statistics and current connection information. 7-6 Chapter 7: Testing and Troubleshooting ping (connection query) This utility can be used to display network traffic at the packet level. Network Monitor This Windows utility is typically available on network servers and graphically displays network traffic at a packet level. Station Statistics Chapter 7: Testing and Troubleshooting 7-7 Detail Screen 7-8 Chapter 7: Testing and Troubleshooting Performance Monitor The Performance Monitor is a Windows NT/2000 Utility that displays NT/2000 performance information graphically. To access this utility click on the Start button on the lower left of the screen, select Programs

> Administrative Tools (Common) > Performance Monitor. Chapter 7: Testing and Troubleshooting 7-9 CBS Communications Diagnostic Tools The following DecisioNet diagnostics are available:

CBS Status Lights Uplink C D 1 D C D 2 C D 3 C

+24VDC 87654321 87654321 87654321 87654321 Ground 1 2 3 4 5 6 7 8 Power The Ethernet status lights (LEDs) are in the top corners of the data connectors. The Power status light is a red LED shown to the right of the power receptacle in the previous illustration. The CBS status lights indicate the following conditions. 18877 LED Power (red) C (green) Ethernet link status D (yellow) Ethernet activity State On Off Blinking On Off Blinking On Off Blinking Meaning OK (power is on) PROBLEM (no power) PROBLEM (intermittent power) OK (good link) PROBLEM (no link) PROBLEM (intermittent link) NOT DEFINED PROBLEM (no receive activity) OK (receive activity) 7-10 Chapter 7: Testing and Troubleshooting dncbsmtest This is the CBS Manager test tool that exercises all CBS Manager functionality. This tool is most useful in isolating CBS problems or failures. Start this utility by typing dncbsmtest at the system prompt. Caution: Some of the dncbsmtest options are intended for NCR internal use only. The following options are suggested to review and analyze CBS problems and also set various parameters if required. Select Option 2 to access the CBS menu. Chapter 7: Testing and Troubleshooting 7-11 Obtain CBS Configuration Information To view configuration information for CBS 1, enter 17 (Get CBS Parameter) and then 1 when prompted for the CBS ID. 7-12 Chapter 7: Testing and Troubleshooting To view the IP address for CBS 1 enter 31. Obtain CBS Diagnostic Information To view diagnostic information for CBS 1, on the CBS Test menu enter 10 (Get Diagnostic Status) and then 1 when prompted for the CBS ID. Chapter 7: Testing and Troubleshooting 7-13 Obtain CBS Tallies To view tallies for a CBS 1, on the CBS Test menu enter 12 (Get Tallies) and then 1 when prompted for the CBS ID. Configure CBS Parameters You can set the following CBS parameters by entering 18 (Set CBS Parameters) on the CBS Test Menu. 7-14 Chapter 7: Testing and Troubleshooting Configure RF Parameters You can set the following RF parameters by entering 19 (Set RF Parameters) on the CBS Test Menu. Configure Frequency Hopping Tables You can modify the Frequency Hopping Table entries by entering 8

(Set Frequency Hopping Table) on the CBS Test Menu. Chapter 7: Testing and Troubleshooting 7-15 System Error Log The DecisioNet Log and Tally Manager controls event logging. All DecisioNet events (errors and status information) are sent to the Windows NT or Windows 2000 Event Log. Error code (event) descriptions are documented in Chapter 10,

"DecisioNet System Messages," of the DecisioNet User's Guide (B005-

0000-1317). Windows NT System Event Log To access the event log, click on the Start button on the lower left of the screen, select Programs > Administrative Tools (Common) > Event Viewer. The following illustration shows a DecisioNet event. Double-

clicking on a line in the window displays the Event Detail screen. 7-16 Chapter 7: Testing and Troubleshooting Bedcheck Bedcheck verifies that ESLs are working properly. This function is intitiated using the ESL Manager Test utility (dneslmtest). You can do hardware checks and existence checks. Enter dneslmtest at a system prompt. The ESL Manager Test menu displays. Enter a 2 to select the Send Bedcheck ESL Request option. You can send Bedcheck requests by one of 4 methods: Query, Serial Number, Location ID, or Location Name. Chapter 7: Testing and Troubleshooting 7-17 Sending a Bedcheck Request by Serial Number Enter a 2 and then complete each prompt as required to send the request. The following screen shows a Hardware check sent to an ESL with serial number of 1000cd. The results of the request display followed by the ESL Manager Test Menu. 7-18 Chapter 7: Testing and Troubleshooting Troubleshooting DecisioNet System Problems The following tables help you troubleshoot the DecisioNet System. Causes Defective ESL. Defective ESL. Battery is low. Defective ESL. Poor coverage. ESL Troubleshooting Problem ESL displays dashes. ESL flashes power-

on diagnostics. ESL displays low

). battery symbol (

ESL displays broken characters or missing segments. ESL displays are severely scrambled. Single ESL does not synchronize. ESL displays sync dot

(G). Multiple ESLs do not synchronize. ESLs display sync dot (G). Possible Remedies Replace ESL. Replace ESL. Release I ESL: replace ESL. Release II ESLs: replace batteries. Replace ESL. Refer to tables in the following section, Coverage Problems. Replace ESL. Poor coverage. Defective ESL. ESL outside coverage area. Bring ESL into coverage area. Wait. A ESL can take several CBS was recently power minutes to re-synchronize after cycled. CBSs have been power cycled. Refer to tables in the following section, Coverage Problems. Add or modify infrastructure to cover area. Refer to tables in the following section, Coverage Problems. Turn on CBS system. Re-start software. ESLs outside coverage area. Poor coverage. CBSs are turned off. CBS communications are closed or software is not running. Chapter 7: Testing and Troubleshooting 7-19 Problem Causes CBS was recently power cycled. Possible Remedies Wait. ESLs can take several minutes to re-synchronize after a CBS power cycle. Replace ESL. Debug software. Make sure you are following the wireless LAN co-existence guidelines. Make sure price verifier is running. Check for duplicate ID numbers in ESL table and resolve. Defective ESL. Software problem. Store contains 2.4 GHz LAN device, and 7730 system does not conform to co-existence guidelines. ESL has duplicate ID number due to incorrect initload. Defective ESL. Software problem. ESL outside coverage area. Bring ESL into coverage area. Poor coverage. Refer to tables in the following section, Coverage Problems. Replace ESL. ESL does not exist. ESL outside coverage area. Move ESL back into coverage area. Poor coverage. Replace ESL. Debug software. Defective ESL. Standard ESL used in freezer. Refer to tables in the following section, Coverage Problems. Replace ESL. Replace standard ESL with freezer ESL. Standard ESL used in freezer. Replace standard ESL with freezer ESL. ESL shows wrong price, but software reports ESL successfully acknowledged last price update. Software reports ESL did not acknowledge price update. Cannot initialize a new ESL. ESLs in freezers fail more frequently than ESLs in other parts of store. Promotional messages in freezer look dim or sluggish. 7-20 Chapter 7: Testing and Troubleshooting General Performance Troubleshooting Problem Promotional messages frequently fail. Price updates seem to work okay. Initload is extremely slow. Causes ESLs outside coverage area. Poor coverage. ESLs outside coverage area. Poor coverage. Promotional updates are very slow. ESLs outside coverage area. Poor coverage. Possible Remedies Move ESLs back into coverage area. Refer to tables in the following section, Coverage Problems. Move ESLs back into coverage area. Refer to tables in the following section, Coverage Problems. Move ESLs back into coverage area. Refer to tables in the following section, Coverage Problems. Note: If troubleshooting fails to diagnose the problem, power cycle the CBSs and ISP. Problem Cannot communicate with primary CBS. RX/TX lights on Ethernet Hub or primary CBS are not blinking. CBS Troubleshooting Step 1. Do any CBSs communicate?

Causes Primary CBS is defective. Defective Power or communications cabling to primary CBS or between primary and secondary CBSs. CBS power is off. CBS communications are closed or software is not running. Possible Remedies Replace primary CBS. Check cabling. Power up CBS system. Initiate CBS communications on start software. Chapter 7: Testing and Troubleshooting 7-21 Possible Remedies Check cables. Check CBS address settings. Replace CBS. Check cable length guidelines. Shorten cable run if necessary. Replace CBS. Check communication cabling. Decrease power cable length. Step 2. Do some CBSs communicate and some not?

Causes Defective cable or incorrectly wired connector caused a break in communication somewhere in CBS chain. Two CBSs are configured with the same address. CBS is defective. Power or communication cable run is too long. CBS is defective. Communication cabling is damaged or defective. Excessive power cable length. Problem Primary CBS communications are OK, but other CBSs do not communicate at all. CBS communication is unreliable. CBS shows RF Off and RF Power low diagnostics while other CBSs operate correctly. Step 3. Are the CBS diagnostics OK?

Problem All secondary CBSs report "sync lost"

diagnostic. Single CBS reports CBS sync lost. Causes Primary CBS sends a timing signal that is used by all secondary CBSs. Bad communication cable. Bad primary CBS. Bad communication cable. Bad CBS. Possible Remedies Check communication cabling. Replace primary CBS. Check communication cabling. Replace CBS. 7-22 Chapter 7: Testing and Troubleshooting Problem Causes RX and TX antennas are too close together. Possible Remedies Move antennas to maintain minimum RX to TX distance of 9.1 m (30 ft.), except for the 100 mW EIRP CBS which can be 3.7 m (12 ft.). This problem is common in back offices. Replace TX cable or antenna. Replace CBS. Damaged TX cable or antenna. Defective CBS. CBS reports intermittent or continuous low output power diagnostic without RF power off diagnostic. CBS reports low output power diagnostic and RF power off diagnostic. dncbsconfig.xml not configured to include problem CBS. CBS communications are closed. CBS system has not fully powered up and initialized. Power cable run length exceeds guidelines. Fix dncbsconfig.xml. Re-start software. Wait 30 seconds and re-check diagnostics. Check cable length guidelines. Shorten cable run if necessary. Coverage Troubleshooting Step 1. Do any CBSs communicate?

Causes ISP or CBS in quasi-state due to unknown problem. Problem Cannot communicate with primary CBS. RX/TX lights on Ethernet hub or Primary CBS not blinking. Primary CBS is defective. Defective Power or communications cabling to primary CBS or between primary and secondary CBSs. CBS power is off. CBS communications are closed or software is not running. Chapter 7: Testing and Troubleshooting 7-23 Possible Remedies Re-start base software. If no improvement, power the CBS hardware off and then on. If no improvement, re-boot ISP. Replace primary CBS. Check cabling. Power up CBS system. Initiate CBS communications on start software. Step 2. Check for sources of RF noise. Problem Site planning did not follow wireless LAN or microwave oven co-existence guidelines. Store contains 2.4 GHz wireless LAN system that was missed during the site survey or added after infrastructure install. Possible Remedies Verify that the site conforms to the wireless LAN co-existence guidelines in the Implementation Guide. Locate the wireless LAN access points and modify the infrastructure according to the wireless LAN co-existence guidelines in the Implementation Guide. 7-24 Chapter 7: Testing and Troubleshooting Problem All secondary CBSs report "sync lost"

diagnostic. Step 3. Improve the infrastructure. Causes Primary CBS sends a timing signal that is used by all secondary CBSs. Bad communication cable. Bad primary CBS. Antenna not connected. Antenna damaged or missing. RX antenna configuration diagnostics do not match site plan. Some CBSs report RF board sync lost. Problem may be intermittent. CBS reports DSP ROM version V0 with checksum V0. CBS reports intermittent or continuous low output power diagnostic without RF power off diagnostic. CBS reports low output power diagnostic and RF power off diagnostic. Bad communication cable. Bad CBS. CBSs were powered on while communications were closed. Bad communication cable. Defective CBS. Damaged TX cable or antenna. Power or communication cable run is too long. Defective CBS. dncbsconfig.xml not configured to include problem CBS. Possible Remedies Check communication cabling. Replace primary CBS. Connect antenna. Replace antenna. Check communication cabling between CBSs, in particular the MCLK wire pair. Replace CBS. Open CBS communications using DNCBSMTEST. Check communication cabling between CBSs, in particular MCLK wire pair. Replace CBS. Replace TX cable or antenna. Check cable length guidelines. Shorten cable run if necessary. Replace CBS. Fix dncbsconfig.xml. Chapter 7: Testing and Troubleshooting 7-25 Problem Causes CBS communications are closed. CBS system has not fully powered up and initialized. Power cable run length exceeds guidelines. Possible Remedies Re-start software. Wait 30 seconds and re-check diagnostics. Check cable length guidelines. Shorten cable run if necessary. 7-26 Chapter 7: Testing and Troubleshooting

 

 

8 Chapter 8: Maintenance Replacing DecisioNet Hardware Except for the ESL battery replacement described in this chapter, the DecisioNet System hardware does not require any preventive maintenance. If there is a problem, trained NCR Customer Service personnel or other trained personnel can use the information in Chapter 7, "Testing and Troubleshooting," to analyze and isolate the problem. DecisioNet hardware is not field repairable. If it is determined that a CBS, antenna, power supply, or ESL is defective, use the procedures described in this chapter to replace the unit with a new one. If appropriate, contact your NCR representative for information on where to send the defective unit for repair. Important Information: After removing or replacing the CBS or a transmit antenna, it is recommended that you re-certify RF communications. It is also recommended that the change in the site configuration be noted for support purposes. For more information, contact your NCR representative and reference the following:

DecisioNet Implementation Guide (B005-0000-1250) Certification/Re-Certification Site Survey Policy (497-0410343) 8-2 Chapter 8: Maintenance Replacing a CBS Use this procedure to replace a suspected malfunctioning CBS with another one. 1. Stop CBS communication using the DNCBSMTEST > 2. CBS Test

> 6. Disable Communications option. 2. Power off all the CBSs in the system by powering off the power supplies. 3. After noting its switch positions, disconnect and remove the malfunctioning CBS. 4. Set the switches in the new CBS to match the switches in the CBS you are replacing. 5. Install the new CBS and reconnect the cables where they were connected before. 6. Power up all CBSs in the system. 7. Re-start CBS communication using the DNCBSMTEST DNCBSMTEST > 2. CBS Test > 3. Enable Normal Mode Communications option. 8. Confirm that errors related to the replaced CBS are no longer being logged. Replacing Antennas Chapter 8: Maintenance 8-3 Replacing a Receive Antenna Use this procedure to replace a suspected malfunctioning receive antenna. 1. Disconnect and remove the malfunctioning receive antenna. 2. Install and re-connect the new receive antenna. 3. Confirm that errors related to the replaced antenna are no longer being logged. Replacing a Transmit Antenna Use this procedure to replace a suspected malfunctioning transmit antenna. You MUST remove power from the CBSs during this procedure. Removing a transmit antenna from a powered CBS can damage the CBS transmitter circuitry. 1. Stop CBS communication using he DNCBSMTEST > 2. CBS Test >

6. Disable Communications option. 2. Power off all the CBSs in the system by powering off the power supplies. 3. Disconnect and remove the malfunctioning transmit antenna. 4. Install the new transmit antenna. 5. Power up all CBSs in the system. 6. Re-start CBS communication using the DNCBSMTEST DNCBSMTEST > 2. CBS Test > 3. Enable Normal Mode Communications option. 8-4 Chapter 8: Maintenance Replacing a Power Supply Use this procedure to replace a suspected malfunctioning power supply. 1. Stop CBS communication using the DNCBSMTEST > 2. CBS Test

> 6. Disable Communications option. 2. Power off all the CBSs in the system by powering off the power supplies. 3. Disconnect and remove the malfunctioning power supply. 4. Install a new power supply. 5. Power up all power supplies in the system. 6. Re-start CBS communication using the DNCBSMTEST DNCBSMTEST > 2. CBS Test > 3. Enable Normal Mode Communications option. 7. Confirm that errors related to the replaced power supply are no longer being logged. Battery Replacement Chapter 8: Maintenance 8-5 When an ESL's battery becomes weak, the battery symbol in the display lights indicating that its lithium battery must be replaced. After removing the ESL from the shelf, follow these steps to replace the batteries:

1. Open the battery cover by inserting a coin in the slot and turning counter-clockwise to its detented position as shown in the following illustration. 2. Attach the Power Saver Tool. Note: This tool is planned for GCA . It serves as a temporary power source while replacing ESL batteries. 3. Remove the battery cover. 4. Remove the battery. 5. Place a new battery in the battery cavity, remove the Power Saver Tool, and replace the battery cover. Caution: Danger of explosion if battery is incorrectly replaced. Replace only with same or equivalent type as recommended by the manufacturer. Discard used batteries according to the manufacturer's instructions. 8-6 Chapter 8: Maintenance Updating a CBS's Firmware Images Periodically updates may be required to add enhancements or correct problems in the CBS firmware. Firmware updates are distributed on diskette as a self-extracting executable file that automatically updates all CBS firmware images. Instructions for performing the update are included with the diskette.

 

 

NCR DecisioNet System Release 3.0 Hardware Installation and Service Guide B005-0000-1247 Issue A The product described in this book is a licensed product of NCR Corporation. NCR is a registered trademark of NCR Corporation. It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and firmware become available. NCR, therefore, reserves the right to change specifications without prior notice. All features, functions, and operations described herein may not be marketed by NCR in all parts of the world. In some instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your NCR representative or NCR office for information that is applicable and current. To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and value of this book. Address correspondence to:

Manager, Information Products NCR Corporation 2651 Satellite Blvd. Duluth, GA 30096 Copyright 2000 By NCR Corporation Dayton, Ohio U.S.A. All Rights Reserved Spine: 3/4 inch or smaller one-line, all types NCR DecisioNet System B005-0000-12471247 Issue AA Spine: 3/4 inch or smaller two-line, all types NCR DecisioNet System Hardware Installation and Service Guide B005-0000-12471247 Issue AA Spine: 3/4 inch or smaller three-line, all types NCR DecisioNet System Release 3.03.0 Hardware Installation and Service Guide B005-0000-1247 Issue AA Spine: 3/4 inch or smaller four-line, all types NCR DecisioNet System Release 3.00 Hardware Installation and Service Guide B005-0000-1247 Issue AA Spine: 3/4 to 1 inch, all types NCR DecisioNet System Release 3.00 Hardware Installation and Service Guide B005-0000-1247247 Issue AA Spine: 1 to 1-1/4 inch, all types NCR DecisioNet System Release 3.0 Hardware Installation and Service Guide B005-0000-1247 Issue AA Spine: 1-1/4 inch or larger, all types NCR DecisioNet System Release 3.00 Hardware Installation and Service Guide B005-0000-1247247 Issue AA B005-0000-1247 Aug. 2000 Printed on recycled paper

 

 

NCR DecisioNet System Release 3.0 Installation and Service Guide B005-0000-1247 Issue A The product described in this book is a licensed product of NCR Corporation. NCR is a registered trademark of NCR Corporation. DecisioNet is a trademark of NCR Corporation. Microsoft Windows NT, Windows NT, and Windows 2000 are registered trademarks of Microsoft Corporation. pcAnwhere is a trademark of Symantec Corporation. UNIX is a registered trademark in the United States and other countries, exclusively licensed through X/OPEN Company Limited. Timbuktu is a registered trademark of Netopia, Inc. BarTender is a registered trademark of Sea Gull Scientific Systems, Inc. It is the policy of NCR Corporation (NCR) to improve products as new technology, components, software, and firmware become available. NCR, therefore, reserves the right to change specifications without prior notice. All features, functions, and operations described herein may not be marketed by NCR in all parts of the world. In some instances, photographs are of equipment prototypes. Therefore, before using this document, consult with your NCR representative or NCR office for information that is applicable and current. To maintain the quality of our publications, we need your comments on the accuracy, clarity, organization, and value of this book. Address correspondence to:

Retail Solutions GroupAtlanta NCR Corporation 2651 Satellite Blvd. Duluth, GA 30096 Copyright 2001 By NCR Corporation Dayton, Ohio U.S.A. All Rights Reserved Installation and Service Guide iii Preface This guide describes the installation, configuration, and service of the NCR DecisioNet System hardware and software. iv Installation and Service Guide Installation and Service Guide v Table of Contents Chapter 1: Introduction About This Guide....................................................... 1-1 Chapter Summaries ............................................. 1-2 Information Sources............................................. 1-3 Chapter 2: Preparing the Installation Site Preparing the Site....................................................... 2-1 Customer Responsibilities.......................................... 2-2 Power, Grounding and Distribution Requirements.. 2-3 Power Requirements............................................ 2-3 Grounding Requirements .................................... 2-4 Power Distribution Requirements ....................... 2-4 Environmental Requirements.................................... 2-6 Temperature and Humidity................................. 2-6 CBS ................................................................... 2-6 ESL (Standard Size and Small Size)................. 2-7 ESL (Freezer).................................................... 2-7 ESL (Signage) ................................................... 2-8 Altitude and Temperature ................................... 2-8 Health and Safety................................................. 2-9 Component Characteristics.......................................2-10 CBS ......................................................................2-10 CBS Power Supply ..............................................2-11 Antennas .............................................................2-12 Transmit Antenna ...........................................2-12 Receive Antenna .............................................2-12 ESLs.....................................................................2-13 ESL, Standard Size ..........................................2-13 ESL, Small Size................................................2-14 vi Installation and Service Guide ESL, Small Signage..........................................2-14 ESL, Large Signage .........................................2-15 ESL Displays and Symbols..................................2-15 1x8-Character, Standard Size..........................2-15 4+8-Character, Standard Size .........................2-16 2x5-Character, Small Size ...............................2-16 1x6-Character, Small Signage .........................2-16 2x6-Character, Large Signage.........................2-17 Chapter 3: Installing the Hardware Infrastructure Chapter Overview...................................................... 3-1 Installation Recommendations............................. 3-2 General Layout Instructions ................................ 3-3 Tools and Supplies ............................................... 3-4 CBS Installation .......................................................... 3-5 CBS Ethernet Cable Connections ........................ 3-5 CBS Numbering ............................................... 3-6 CBS Power Supply Cable Connections ............... 3-7 EU/EC Installations ......................................... 3-8 Sample Store Cabling....................................... 3-9 CBS Cables ......................................................3-10 CBS Connectors and Status Lights .....................3-13 Data Connectors..............................................3-13 Power Receptacle............................................3-13 CBS Status Lights ............................................3-14 CBS Identification................................................3-15 CBS Installation ...................................................3-16 Preferred CBS Mounting Solution..................3-18 Connecting Ethernet Data Cables.......................3-18 Connecting the Ethernet Hub to the Primary CBS....................................................3-18 Installation and Service Guide vii Connecting Secondary CBSs...........................3-20 Connecting Power Supply Cables ......................3-21 Connecting CBS Power Supplies to AC Power........................................................3-21 Connecting CBS Power Supplies to CBSs ......3-21 CBS Antennas .....................................................3-23 Installing CBS Antennas .....................................3-24 Mounting an Antenna on a T-bar...................3-24 Securing an Antenna to a Wall.......................3-25 Hanging an Antenna from a Roof Truss ........3-26 CBS Hardware Configuration.............................3-28 Configure the DHCP Service..........................3-28 Manual Allocation on a Windows NT Server.3-28 Verify Communication Links..........................3-31 Chapter 4: Installing DecisioNet Software on a Windows NT or Windows 2000 System System Environment for Windows NT...................... 4-1

`DecisioNet Software for Windows NT and Windows 2000 ............................................................ 4-2 DecisioNet Software Installation.......................... 4-2 Installing the Base Software Package............... 4-3 Installing the Scan-Merge Package.................. 4-4 Installing the Application Development Environment Package ...................................... 4-5 Uninstalling DecisioNet Software........................ 4-6 Configuring the DecisioNet System .................... 4-6 Chapter 5: DecisioNet Software Installation on an NCR UNIX System (Delayed Deliverable) System Environment for NCR UNIX......................... 5-1 DecisioNet Software for NCR UNIX ......................... 5-2 viii Installation and Service Guide Chapter 6: Configuring the DecisioNet System Environment Overview.................................................................... 6-1 XML File Format .................................................. 6-2 Identifying a Parameter in an XML Format File .................................................................... 6-2 Commented Information ................................. 6-3 Using an Editor to Locate a Parameter............ 6-3 Configuration File Comments.............................. 6-4 Setting Performance Boost in Windows NT 4.0 .. 6-5 Starting a Windows NT DecisioNet System........ 6-5 Configuring the DecisioNet System .......................... 6-6 CBS Configuration ............................................... 6-6 Hostname ......................................................... 6-6 IP Address........................................................ 6-6 Static IP Addressing ......................................... 6-7 Dynamic IP Adressing ..................................... 6-7 Setting CBS Parameters ................................... 6-7 Application Configuration ................................... 6-9 DecisioNet Configuration file

(dnconfig.xml).............................................. 6-9 DecisioNet Task Manager (taskman.cfg)........6-14 About Passwords.......................................................6-16 Maintaining Username/ Password.....................6-16 Chapter 7: Testing and Troubleshooting CBS Diagnostics and Troubleshooting....................... 7-1 Ethernet Communication Diagnostic Tools..... 7-1 CBS Communications Diagnostic Tools........... 7-2 System Error Log ............................................. 7-2 Site-specific RF Certification Reference........... 7-2 Ethernet Communication Diagnostic Tools............... 7-4 Installation and Service Guide ix arp (ARP table query) .......................................... 7-4 ipconfig (IP configuration query)......................... 7-4 netstat (network status query) ............................. 7-5 ping (connection query)....................................... 7-6 Network Monitor ................................................. 7-6 Station Statistics................................................ 7-6 Detail Screen .................................................... 7-7 Performance Monitor........................................... 7-8 CBS Communications Diagnostic Tools..................... 7-9 CBS Status Lights ................................................. 7-9 dncbsmtest...........................................................7-10 Obtain CBS Configuration Information..........7-11 Obtain CBS Diagnostic Information................7-12 Obtain CBS Tallies...........................................7-13 Configure CBS Parameters .............................7-13 Configure RF Parameters................................7-14 Configure Frequency Hopping Tables ...........7-14 System Error Log ......................................................7-15 Windows NT System Event Log .........................7-15 Bedcheck .............................................................7-16 Sending a Bedcheck Request by Serial Number ...........................................................7-17 Troubleshooting DecisioNet System Problems.........7-18 ESL Troubleshooting...........................................7-18 General Performance Troubleshooting ..............7-20 CBS Troubleshooting ..........................................7-20 Coverage Troubleshooting..................................7-23 Chapter 8: Maintenance Replacing DecisioNet Hardware ............................... 8-1 Replacing a CBS ................................................... 8-2 x Installation and Service Guide Replacing Antennas............................................. 8-3 Replacing a Receive Antenna .......................... 8-3 Replacing a Transmit Antenna ........................ 8-3 Replacing a Power Supply................................... 8-4 Battery Replacement .................................................. 8-5 Updating a CBS's Firmware Images .......................... 8-6 Appendix A: Parts Order Information CBS ............................................................................ A-1 Model Number.................................................... A-1 Major Model Code .............................................. A-1 Sub Model Code.................................................. A-1 Language Code ................................................... A-2 Power Code......................................................... A-2 Kit Numbers........................................................ A-3 Cable Numbers ................................................... A-4 Appendix B: DecisioNet Configuration Files DecisioNet CBs Configuration file

(dncbsconfig.xml)........................................... B-1 DecisioNet Configuration file (dnconfig.xml). B-1 DecisioNet Task Manager Configuration file

(taskman.cfg).................................................. B-43 DecisioNet Host Bridge Configuration file

(dnhostbridge.xml)....................................... B-44 Glossary Index Installation and Service Guide xi xii Installation and Service Guide Revision Record Issue A Date Apr 01 Remarks First printing Installation and Service Guide xiii Radio Frequency Interference Statements Federal Communications Commission (FCC) This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause interference in which case the user will be required to correct the interference at his own expense. NCR is not responsible for any radio or television interference caused by unauthorized modification of this equipment or the substitution or attachment of connecting cables and equipment other than those specified by NCR. The correction of interference caused by such unauthorized modification, substitution or attachment will be the responsibility of the user. The user is cautioned that changes or modifications not expressly approved by NCR may void the users authority to operate the equipment. Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures. Canadian Department of Communications This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus set out in the Radio Interference Regulations of the Canadian Department of Communications. Le prsent appareil numrique nmet pas de bruits radiolectriques dpassant les limites applicables aux appareils numriques de la classe A prescrites dans le Rglement sur le brouillage radiolectriques dict par le ministrre des Communications du Canada. Voluntary Control Council For Interference (VCCI) xiv Installation and Service Guide

 

 

G Glossary A Antenna A device used to transmit and receive RF communication between a CBS and ESLs. One transmit and up to four receive antennas may be attached to each CBS. Antennas are usually installed on the ceiling. API (Application Program Interface) A set of functions that can be used by the application software to access the functionality of the DecisioNet Software. Attachments Mounting devices used to attach ESLs to shelf rails. B Base Runtime Software A software application for the DecisioNet System that runs on the DecisioNet Software Controller and is not dependent on the type of POS system used. The Base Runtime Software controls the core DecisioNet functionality such as initialization of a ESL, display of price on an ESL, and diagnostics. This software also provides a set of standard API functions that can be used to interface with the ESL Application Software and other software controlling the POS system. Bedcheck A background function that verifies ESLs are working properly. If an ESL does not respond to a bedcheck message, an error is recorded. G-2 Glossary C CBS (Communication Base Station) CBSs receive and transmit data and control functions to the ESLs. Up to 40 CBSs can be installed in a store. One CBS is defined as the primary CBS and the others as secondary CBSs. CBSs are usually installed in the ceiling. CBS Power Supply This external AC/DC converter supplies DC power to a maximum of five CBSs. An additional CBS Power Supply is required for each additional group of 5 CBSs. Power requirements in the EU/EC countries limit the number of CBSs connected to a power supply to three (3). Coverage Area An area within a store where there is reliable RF communication between CBSs and ESLs. More than one CBS is required in a large store to attain adequate transmission reliability. D Descriptor Symbols One symbol on the ESL's LCD indicates when the ESL and CBS are out of synchronization, and another symbol indicates when the ESL's battery is low. The other symbols on the display are available for the retailer's use. DecisioNet Database A MySQL database used to store information relative to all ESL management. DecisioNet Software Controller This refers to the In-Store Processor (ISP) or a Dedicated PC (DPC). This is the computer physically connected to the primary CBS that sends price information from the PLU file to the DecisioNet System for display on ESLs. Glossary G-3 Downlink A CBS sends data to an ESL in a downlink message. Examples of downlink messages are Bedcheck, Price Update, Load Memory, and Change Display Register. DPC (Dedicated Personal Computer) This PC, acting as the ESL controller, reads the customer's PLU file from the In-Store Processor/POS system via a LAN connection and communicates the information to DecisioNet System. E Error Log This module of the DecisioNet Software records and displays communication errors between the ISP or DPC and an ESL. ESL (Electronic Shelf Label) An ESL is the device attached to the store shelf that displays information for the customer. ESL Removal Tool Also called an ESL puller, this tool is used to remove ESLs from shelf rails and clips. ESL Serial Number During manufacture, a distinct 8-digit (32-bit binary code) number is assigned to each ESL and stored in the ESL's RAM. The serial number and its barcode equivalent (Code 39) are printed on the right side of the ESL. The serial number and the bar code are blue on a freezer ESL and black on all other ESLs. ESL Standalone System A system that runs the DecisioNet Software on a dedicated PC separate from the ISP. In this situation the DPC has a copy of the store data base and communicates with the ISP to receive maintenance (price update) data. G-4 Glossary ESL Table An area in the DecisioNet Database created during the initial DecisioNet System installation that links ESLs to PLU items. This table also contains other data used to define the attributes of each ESL. I Initialization The process by which an ESL is registered in the DecisioNet data base, associated with a particular product, and synchronized. IP (Internet Protocol) IP Addresss An address format (xxx.xxx.xxx.x) used to communicate with devices or components in an network. The format includes network IDs, subnetwork IDs, and host IDs. ISP (In-Store Processor) The computer in the store that contains the price database used by the POS system. The ISP integrates PLU information into the DecisioNet System. L M P LCD (Liquid Crystal Display) The type of display in an ESL. MAC (Medim Access Control) A communications protocol. The MAC protocol is used to provide the data link layer of an Ethernet LAN system. PC (Personal Computer) Pre-ESL Table A data file used to is create an ESL Table. Glossary G-5 Promotional Message Promotional message(s) such as "SAVE," "OFF," and "FOR SALE"

can be displayed on the ESL alternately with the price R Register Data These messages, such as stocking information and aisle number, may be used by store personnel. They can be displayed on the ESL by pressing a micromotion button hidden behind the front label or by transmitting an instruction from the processor. RF (Radio Frequency) S Shelf Rail A device which can be attached to the existing shelf/gondola to secure several ESLs to the shelf and protect them from accidental damage and from theft. Store ID A unique number is assigned to each store and used by the DecisioNet System to prevent unintentional transmission of signals between stores. T Tag A tag, also referred to as an Electronic Shelf Label (ESL), is the device attached to the store shelf that displays information for the customer. Time Slot A unit of time assigned to each ESL during which a CBS transmits either a downlink message to an ESL, or receives acknowledgements (ACKs) back from an ESL. Each CBS is assigned 2 time slots. G-6 Glossary TOD (Time Of Day) A clock used by the DecisioNet System to trigger display changes. U Uplink An uplink is an acknowledgment message (ACK) sent from an ESL to a CBS in response to a downlink burst.

 

 

Index A Altitude and temperature, 2-8 Antennas Characteristics, 2-12 Installing, 3-23, 3-24 Overview, 3-23 C Cables CBS Cable usage table, 3-10 Recommended cables, 3-11 Cable usage table, 3-10 Characteristics, 2-10 Connecting secondary CBSs, 3-18 Data connectors, 3-13 Installing, 3-5, 3-16 Kit numbers, A-3 LEDs, 3-14 Model number and codes, A-1 Parts order information, A-1 Power connectors, 3-13 Power supply characteristics, 2-11 Recommended cables, 3-11 System cable connections, 3-5, 3-7 Type 1 (lab) installation, 3-18 Chapter summaries, 1-2 Characteristics Antennas, 2-12 CBS, 2-10 CBS power supply, 2-11 ESLs, 2-13 Customer responsibilities, 2-2 E Electrical requirements, 2-3 Environmental requirements, 2-6 Altitude and temperature, 2-8 Health and safety, 2-9 Temperature and humidity, 2-6 ESL Characteristics, 2-13 Displays and symbols, 2-15 G Grounding requirements, 2-4 H Hardware installation, 3-1 Health and safety, 2-9 I Installation Antennas, 3-23 CBS, 3-5 CBS power supply, 3-21 CBS power supply to primary CBS, 3-21 Index-2 Hardware, 3-1 Recommendations, 3-2 Windows NT software, 4-2 K Kit numbers, A-3 L Licensed Product Identification Numbers

(LPINs) NCR UNIX, 5-2 Windows NT, 4-2 LPINs NCR UNIX, 5-2 Windows NT, 4-2 N NCR UNIX LPINs, 5-2 System environment, 5-1 P Power requirements, 2-3, 2-4 R Reference materials, 1-3 S Site certification tools, 1-3 Site preparation, 2-1 Software NCR UNIX, 5-2 Windows NT, 4-2 Software installation Windows NT, 4-2 System environment NCR UNIX, 5-1 Windows NT, 4-1, 5-1 T Temperature and humidity, 2-6 Tools and supplies, 3-4 W Windows NT LPINs, 4-2 Software installation, 4-2 System environment, 4-1, 5-1

 

 

A Appendix A: Parts Order Information CBS Model Number The CBS's twelve-digit model number is located on its name plate. The model number contains important information used to ensure that a replacement CBS matches the site's requirements. The twelve-digit model number is defined in following illustration. 7730 10 11 90 90 Class Number Major Model Code Language Code Power Code Sub Model Code 18671 Major Model Code Major Model Code 10 Sub Model Code Description CBS III The following sub model codes identify the CBS. Sub Model Code 11 12 13 14 15 Description/Version CBS III, 2W EIRP, U.S. & Canada CBS III, 500 mW EIRP, EMEA CBS III, 500 mW EIRP, Netherlands CBS III, 100 mW EIRP, France CBS III, 100 mW EIRP, Denmark, Italy, Norway A-2 Appendix A: Parts Order Information Language Code The following is the language code. Language Code 90 Description No language characteristics Power Code The following is the power code. Power Code 90 Description The CBS does not have an internal power supply. It receives power from the CBS power supply. Kit Numbers Appendix A: Parts Order Information A-3 The following kits support DecisioNet System installations. Category Kit Number Part Number Description CBS 7730-K011-V001 497-0413259 Central power supply kit with U.S. cord 7730-K012-V001 497-0413260 Central power supply kit, intl wire plug 7730-K050-V001 497-0414017 Receive antenna kit, 7730-K053-V001 497-0415013 plenum rated Transmit antenna kit, plenum rated 7730-K054-V001 497-0415927 Receive antenna kit for 100 mW CBS, plenum rated ESL 7730-K200-V001 7730-K300-V001 7730-K301-V001

(4/30) 7730-K310-V001 7730-K311-V001

(4/30) 7730-K400-V001

(4/30) 7730-K500-V001

(4/30) ESL, Small 2x5 (10 PCS.) ESL, Standard, 4+8 (10 PCS.) ESL, Standard, 4+8, Freezer (10 PCS.) ESL, Standard, 1x8 (10 PCS.) ESL, Standard, 1x8, Freezer (10 PCS.) ESL, Small Signage, 1x6

(20 PCS.) ESL, Large Signage, 2x6

(20 PCS.) A-4 Appendix A: Parts Order Information Cable Numbers The following cables support DecisioNet System installations. Category Cable Number Part Number Description CBS 1416-C465-0018 230-0134973 Cable Transmitting antenna, CBS III 1416-C057-0180 1416-C520-0150 230-0134951 Cable Receiving antenna, 18 meters 230-0134953 Cable Receiving antenna, 15 meters, for 100 mW Power Supply 1416-C463-9999 497-0413234 Cable Central power supply pigtail

 

 

B Appendix B: DecisioNet Configuration Files This appendix contains listings of the following DecisioNet Configuration files:

DecisioNet CBS Configuration file (dncbsconfig.xml) DecisioNet Configuration file (dnconfig.xml) DecisioNet Task Manager Configuration file (taskman.cfg) DecisioNet Host Bridge Configuration file (dnhostbridge.xml) DecisioNet CBs Configuration file (dncbsconfig.xml)

<?xml version="1.0"?>

<!DOCTYPE cbsconfig SYSTEM "dncbsconfig.dtd">

<cbsconfig>

<cbs>

<id>1</id>

<hostname>ncrdnetnnnnnn.atlantaga.ncr.com</hostname>

</cbs>

</cbsconfig>

DecisioNet Configuration file (dnconfig.xml)

<?xml version="1.0"?>

<!DOCTYPE config SYSTEM "dnconfig.dtd">

<config>

<section name="Ipc">

<!-- <param name="ServerIP">127.0.0.1</param> -->

<param name="TraceLevel">0</param>

</section>

<!-- * LogTally Manager Configuration parameters * -->

B-2 Appendix B: DecisioNet Configuration Files

<section name="LogTally Manager">

<!-- Section: LogTally Manager -->

<!-- SystemLogging -->

<!-- Specifies whether or not to log to the OS system log. d -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

<param name="SystemLogging">Y</param>

<!-- Section: LogTally Manager -->

<!-- CheckAction -->

<!-- Specifies whether or not to check for any actions -->

<!-- required before sending event to the dnltmanager. -->

<!-- Values: Y - Send only if action required. -->

<!-- N - Send always. -->

<!-- Default = Y (yes) -->

<param name="CheckAction">Y</param>

<!-- Section: LogTally Manager -->

<!-- MaxTallies -->

<!-- Maximun number of tallies allowed per modue. -->

<!-- Values: 1+ -->

<!-- Default = 50 -->

<param name="MaxTallies">50</param>

<!-- Section: LogTally Manager -->

<!-- TallyUpdateFrequency -->

<!-- Interval to request tally dumps in minutes. -->

<!-- Values: 1+ -->

Appendix B: DecisioNet Configuration Files B-3

<!-- Default = 10 -->

<param name="TallyUpdateFrequency">10</param>

<!-- Section: LogTally Manager -->

<!-- TraceLevel -->

<!-- Specifies level of verbose tracing. -->

<!-- Values: 0-4 -->

<!-- Default = 0 -->

<param name="TraceLevel">0</param>

<!-- Section: LogTally Manager -->

<!-- TraceFile -->

<!-- Specifies file name to write trace information. -->

<!-- Values: Valid file and or dir/file name. -->

<!-- Default = None -->

<!-- <param name="TraceFile">dnltmanager.trc</param> -->

<!-- Section: LogTally Manager -->

<!-- EventsMax -->

<!-- Specifies maximum number of records allowed -->

<!-- in EVENT table. -->

<!-- Values: 1000+ -->

<!-- Default = 10000 -->

<param name="EventsMax">10000</param>

<!-- Section: LogTally Manager -->

<!-- EventsNumberToRemove -->

<!-- Specifies number of records to delete when EventsMax -->

<!-- is reached. -->

<!-- Values: 100+ -->

B-4 Appendix B: DecisioNet Configuration Files

<!-- Default = 1000 -->

<param name="EventsNumberToRemove">1000</param>

<!-- Section: LogTally Manager -->

<!-- EventsDaysToRemove -->

<!-- Specifies maximum retention days for EVENTS. -->

<!-- All EVENTS older than this number of day will be deleted.-->

<!-- Parameter superseeds EventMAx. -->

<!-- Values: 1+ -->

<!-- Default = 30 -->

<param name="EventsDaysToRemove">30</param>

<!-- Section: LogTally Manager -->

<!-- HandleEmail -->

<!-- Specifies whether to handle email type actions. -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

<param name="HandleEmail">Y</param>

<!-- Section: LogTally Manager -->

<!-- HandleAlarm -->

<!-- Specifies whether to handle alarm type actions. -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

<param name="HandleAlarm">Y</param>

<!-- Section: LogTally Manager -->

<!-- HandleConsole -->

<!-- Specifies whether to handle console type actions. -->

<!-- Values: Y(yes) or N(no) -->

Appendix B: DecisioNet Configuration Files B-5

<!-- Default = Y (yes) -->

<param name="HandleConsole">Y</param>

<!-- Section: LogTally Manager -->

<!-- HandleSystemTray -->

<!-- Specifies whether to handle systemtray type actions. -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

<param name="HandleSystemTray">Y</param>

<!-- Section: LogTally Manager -->

<!-- Specifies whether or not to handle the action. -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

<param name="HandleExecProcess">Y</param>

<!-- Section: LogTally Manager -->

<!-- Specifies whether to handle Esl Pager Tag type actions. -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

<param name="HandlePager">Y</param>

<!-- Section: LogTally Manager -->

<!-- HandleEslTag -->

<!-- Specifies whether to handle Esl Manual Tag type actions. -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = Y (yes) -->

B-6 Appendix B: DecisioNet Configuration Files

<param name="HandleEslTag">Y</param>

<!-- Section: LogTally Manager -->

<!-- HandleThirdParty -->

<!-- Specifies whether to handle ThirdParty type actions. -->

<!-- Values: Y(yes) or N(no) -->

<!-- Default = N (No) -->

<param name="HandleThirdParty">N</param>

<!-- Section: LogTally Manager -->

<!-- ManualTagLinkID -->

<!-- Specifies Manual Tag Link ID. -->

<!-- Values: AlphaNumeric -->

<!-- Default = MANUAL -->

<param name="ManualTagLinkID">MANUAL</param>

<!-- Section: LogTally Manager -->

<!-- ManualTagLinkType -->

<!-- Specifies Manual Tag Link Type. -->

<!-- Values: Numbeic -->

<!-- Default = 99 -->

<param name="ManualTagLinkType">99</param>

<!-- Section: LogTally Manager -->

<!-- PagerTagLinkID -->

<!-- Specifies Pager Tag Link ID. -->

<!-- Values: AlphaNumeric -->

<!-- Default = PAGER -->

<param name="PagerTagLinkID">PAGER</param>

Appendix B: DecisioNet Configuration Files B-7

<!-- Section: LogTally Manager -->

<!-- PagerTagLinkType -->

<!-- Specifies Pager Tag Link Type. -->

<!-- Values: Numeric -->

<!-- Default = 98 -->

<param name="PagerTagLinkType">98</param>

</section>

<!-- * CBS Manager Configuration parameters * -->

<section name="CBS Manager">

<!-- Section: CBS Manager -->

<!-- MaxWorkerThreads -->

<!-- The maximum number of threads the CBS Manager is allowed -->

<!-- to create to communicate with CBS's. This parameter -->

<!-- will limit the number of connections to CBS's that the -->

<!-- CBS Manager can create. -->

<!-- Values: 1+ -->

<!-- Default = 20 -->

<param name="MaxWorkerThreads">20</param>

<!-- Section: CBS Manager -->

<!-- MaxConnectionsPerCBS -->

<!-- The maximum number of connections the CBS Manager is -->

<!-- allowed to have open to each individual CBS. -->

<!-- Values: 1+ -->

<!-- Default = 10 -->

<param name="MaxConnectionsPerCBS">10</param>

<!-- Section: CBS Manager -->

B-8 Appendix B: DecisioNet Configuration Files

<!-- MaxChainedMessages -->

<!-- The maximum number of ESL commands that should be -->

<!-- chained together in a single ESL message (downlink). -->

<!-- Values: 1-8 -->

<!-- Default = 5 -->

<param name="MaxChainedMessages">5</param>

<!-- Section: CBS Manager -->

<!-- MinChainedMessages -->

<!-- The minimum number of ESL commands that should be -->

<!-- chained together in a single ESL message (downlink). If -->

<!-- fewer than this number need to be sent to process a -->

<!-- request NOP commands are appended to increase the number -->

<!-- of chained messages. -->

<!-- Values: 1-8 -->

<!-- Default = 1 -->

<param name="MinChainedMessages">1</param>

<!-- Section: CBS Manager -->

<!-- TODUpdateFrequency -->

<!-- Specifies how often (in minutes) the time of day should -->

<!-- be broadcast to all ESL's. -->

<!-- Values: 1+ -->

<!-- Default = 60 (minutes) -->

<param name="TODUpdateFrequency">60</param>

<!-- Section: CBS Manager -->

<!-- NumberCBSAttempts -->

<!-- Specifies how many times the CBS Manager should attempt -->

<!-- to connect to a CBS or send a command to a CBS before -->

<!-- giving up. -->

<!-- Values: 1+ -->

Appendix B: DecisioNet Configuration Files B-9

<!-- Default = 3 -->

<param name="NumberCBSAttempts">3</param>

<!-- Section: CBS Manager -->

<!-- NumberESLAttempts -->

<!-- Specifies how many times the CBS Manager should attempt -->

<!-- to send a message to an ESL before giving up. The CBS -->

<!-- Manager will retry sending a message to an ESL up to -->

<!-- this limit when no response is received from the ESL. -->

<!-- Values: 1+ -->

<!-- Default = 5 -->

<param name="NumberESLAttempts">5</param>

<!-- Section: CBS Manager -->

<!-- BroadcastSends -->

<!-- Specifies the number of times the CBS Manager should -->

<!-- send broadcast messages to ESL's. -->

<!-- Values: 1+ -->

<!-- Default = 5 -->

<param name="BroadcastSends">5</param>

<!-- Section: CBS Manager -->

<!-- ConnectTimeout -->

<!-- The number of seconds the CBS Manager should wait while -->

<!-- attempting to open a connection to a CBS before giving -->

<!-- up. -->

<!-- Values: 1+ -->

<!-- Default = 10 seconds -->

<param name="ConnectTimeout">10</param>

<!-- Section: CBS Manager -->

<!-- ResponseTimeout -->

B-10 Appendix B: DecisioNet Configuration Files

<!-- The number of seconds the CBS Manager should wait for a -->

<!-- response from a CBS before disconnecting and retrying. -->

<!-- Values: 1+ -->

<!-- Default = 15 seconds -->

<param name="ResponseTimeout">15</param>

<!-- Section: CBS Manager -->

<!-- MaxFailureFrequency -->

<!-- The maximum frequency in seconds that diagnostic -->

<!-- failures from each CBS should be logged. The CBS -->

<!-- Manager will accept no more than one diagnostic failure -->

<!-- from each CBS during this window. -->

<!-- Values: 1+ -->

<!-- Default = 15 seconds -->

<param name="MaxFailureFrequency">15</param>

<!-- Section: CBS Manager -->

<!-- ResultTableExpirationTime -->

<!-- Specifies how long (in minutes) the CBS Manager should -->

<!-- keep results of completed requests in it's result table -->

<!-- for retrieval by clients. -->

<!-- Values: 1+ -->

<!-- Default = 60 minutes -->

<param name="ResultTableExpirationTime">60</param>

<!-- Section: CBS Manager -->

<!-- BufferFullAttempts -->

<!-- Specifies how many times the CBS Manager should try -->

<!-- sending a message to an ESL when a CBS returns "buffer -->

<!-- full." -->

<!-- Values: 1+ -->

<!-- Default = 99 -->

Appendix B: DecisioNet Configuration Files B-11

<param name="BufferFullAttempts">99</param>

<!-- Section: CBS Manager -->

<!-- BufferFullPause -->

<!-- Specifies how many seconds the CBS Manager whould wait -->

<!-- before resending a message to a CBS after receiving a -->

<!-- "buffer full" error. -->

<!-- Values: 1+ -->

<!-- Default = 10 -->

<param name="BufferFullPause">10</param>

<!-- Section: CBS Manager -->

<!-- CBSBusyAttempts -->

<!-- Specifies how many times the CBS Manager should try -->

<!-- sending a message to an ESL when a CBS returns "busy," -->

<!-- Values: 1+ -->

<!-- Default = 99 -->

<param name="CBSBusyAttempts">99</param>

<!-- Section: CBS Manager -->

<!-- CBSBusyPause -->

<!-- Specifies how many seconds the CBS Manager whould wait -->

<!-- before resending a message to a CBS after receiving a -->

<!-- "busy" error. -->

<!-- Values: 1+ -->

<!-- Default = 10 -->

<param name="CBSBusyPause">10</param>

<!-- Section: CBS Manager -->

<!-- QuickFind -->

<!-- If enabled the CBS Manager will return the results of a -->

<!-- find immediately after recieving a response from the ESL -->

<!-- being located. If disabled the CBS Manager will -->

B-12 Appendix B: DecisioNet Configuration Files

<!-- continue trying to find the specified ESL -->

<!-- 'BroadcastSends' times to make sure the find returns -->

<!-- the CBS that received the strongest response from the -->

<!-- ESL. -->

<!-- Values: 1 (enabled) or 0 (disabled) -->

<!-- Default = 1 -->

<param name="QuickFind">1</param>

<!-- Section: CBS Manager -->

<!-- SimulationMode -->

<!-- If set to 1 the CBS Manager will simulate communications -->

<!-- with CBS's and ESL's. If set to 2 the CBS Manager will -->

<!-- send ESL messages to CBS's but always return a good -->

<!-- uplink from the ESL, whether or not the actual received -->

<!-- uplink was good. -->

<!-- Values: 0, 1, or 2. -->

<!-- Default = 0 -->

<param name="SimulationMode">1</param>

<!-- Section: CBS Manager -->

<!-- StoreID -->

<!-- The StoreID for the system. When the CBS Manager starts -->

<!-- it will ensure that all CBS's use the specified store ID -->

<!-- in beacons and all downlinks. -->

<!-- Values: 0-255 -->

<!-- Default = 255 -->

<param name="StoreID">255</param>

<!-- Section: CBS Manager -->

<!-- TraceLevel -->

<!-- Specifies the default trace level to use if none -->

<!-- specified on the command-line. -->

<!-- Trace level 0 = No trace output. -->

<!-- Trace level 1 = Trace output for errors only. -->

Appendix B: DecisioNet Configuration Files B-13

<!-- Trace level 2 = Level 1 + CBS communications trace -->

<!-- output. -->

<!-- Trace level 3 = Level 2 + API-level function entry/exit. -->

<!-- Trace level 4 - 6 = More function entry/exit output. -->

<!-- Values: 0-6 -->

<!-- Default = 0 -->

<param name="TraceLevel">0</param>

<!-- Section: CBS Manager -->

<!-- TraceFile -->

<!-- Specifies the name of a file where trace output should -->

<!-- be written if none specified on the command-line. -->

<!--<param name="TraceFile">cbsmanager.trc</param>-->

</section>

<!-- End CBS Manager Section -->

<!-- * ESL Manager Configuration parameters * -->

<section name="ESL Manager">

<!-- Section: ESL Manager -->

<!-- PeriodicVerify -->

<!-- Whether the ESL Manager is enabled to schedule automatic -->

<!-- periodic verifies. -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="PeriodicVerify">0</param>

<!-- Section: ESL Manager -->

<!-- VerificationRecurrence -->

B-14 Appendix B: DecisioNet Configuration Files

<!-- How often automatically scheduled Verifications take -->

<!-- place (Price Verifier) -->

<!-- Values: valid time period specification -->

<!-- default = hourly (P0Y0M0DT1H0M0S) -->

<!-- Note: only used if PeriodicVerify is enabled -->

<param name="VerificationRecurrence">P0Y0M0DT1H0M0S</param>

<!-- Section: ESL Manager -->

<!-- VerificationStartDate -->

<!-- The effective start date of automatic verifications. -->

<!-- Note that this parameter just gives a starting -->

<!-- point for the recurrence. It does not have to be -->

<!-- absolute, nor does it have to be continuously updated. -->

<!-- It simply gives A start date and time as a jumping off -->

<!-- point for use with the associated recurrence. -->

<!-- For example: If the action is desired every Monday at -->

<!-- 1am, then the recurrence would be P0Y0M7DT0H0M0S, and -->

<!-- the start date could be ANY date in the past that -->

<!-- happened to be a Monday, along with a time of 1am, -->

<!-- say 20010205010000 -->

<!-- Values: valid time stamp (YYYYMMDDhhmmss) -->

<!-- default (if missing or invalid) = time config file read -->

<!-- Note: only used if PeriodicVerify is enabled -->

<!-- <param name="VerificationStartDate">20000101000000</param> -->

<!-- Section: ESL Manager -->

<!-- PeriodicExistenceBedcheck -->

<!-- Whether the ESL Manager is enabled to schedule automatic -->

<!-- periodic existence bedchecks. -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="PeriodicExistenceBedcheck">0</param>

Appendix B: DecisioNet Configuration Files B-15

<!-- Section: ESL Manager -->

<!-- ExistenceBedcheckRecurrence -->

<!-- How often automatically scheduled Existence Bedchecks -->

<!-- take place -->

<!-- Values: valid time period specification -->

<!-- default = weekly (P0Y0M7DT0H0M0S) -->

<!-- Note: only used if PeriodicExistenceBedcheck is enabled -->

<param name="ExistenceBedcheckRecurrence">P0Y0M7DT0H0M0S</param>

<!-- Section: ESL Manager -->

<!-- ExistenceBedcheckStartDate -->

<!-- The effective start date of automatic ExistenceBedchecks -->

<!-- Note that this parameter just gives a starting -->

<!-- point for the recurrence. It does not have to be -->

<!-- absolute, nor does it have to be continuously updated. -->

<!-- It simply gives A start date and time as a jumping off -->

<!-- point for use with the associated recurrence. -->

<!-- For example: If the action is desired every Monday at -->

<!-- 1am, then the recurrence would be P0Y0M7DT0H0M0S, and -->

<!-- the start date could be ANY date in the past that -->

<!-- happened to be a Monday, along with a time of 1am, -->

<!-- say 20010205010000 -->

<!-- Values: valid time stamp (YYYYMMDDhhmmss) -->

<!-- default (if missing or invalid) = time config file read -->

<!-- Note: only used if PeriodicExistenceBedcheck is enabled -->

<!-- <param name="ExistenceBedcheckStartDate">20000101000000</param> -->

<!-- Section: ESL Manager -->

<!-- PeriodicHardwareBedcheck -->

<!-- Whether the ESL Manager is enabled to schedule automatic -->

<!-- periodic hardware bedchecks. -->

<!-- Values: 0(=disabled)/1(=enabled) -->

B-16 Appendix B: DecisioNet Configuration Files

<!-- default = 1 (enabled) -->

<param name="PeriodicHardwareBedcheck">0</param>

<!-- Section: ESL Manager -->

<!-- HardwareBedcheckRecurrence -->

<!-- How often automatically scheduled Hardware Bedchecks -->

<!-- take place -->

<!-- Values: valid time period specification -->

<!-- default = monthly (P0Y1M0DT0H0M0S) -->

<!-- Note: only used if PeriodicHardwareBedcheck is enabled -->

<param name="HardwareBedcheckRecurrence">P0Y1M0DT0H0M0S</param>

<!-- Section: ESL Manager -->

<!-- HardwareBedcheckStartDate -->

<!-- The effective start date of automatic HardwareBedchecks -->

<!-- Note that this parameter just gives a starting -->

<!-- point for the recurrence. It does not have to be -->

<!-- absolute, nor does it have to be continuously updated. -->

<!-- It simply gives A start date and time as a jumping off -->

<!-- point for use with the associated recurrence. -->

<!-- For example: If the action is desired every Monday at -->

<!-- 1am, then the recurrence would be P0Y0M7DT0H0M0S, and -->

<!-- the start date could be ANY date in the past that -->

<!-- happened to be a Monday, along with a time of 1am, -->

<!-- say 20010205010000 -->

<!-- Values: valid time stamp (YYYYMMDDhhmmss) -->

<!-- default (if missing or invalid) = time config file read -->

<!-- Note: only used if PeriodicHardwareBedcheck is enabled -->

<!-- <param name="HardwareBedcheckStartDate">20000101000000</param> -->

<!-- Section: ESL Manager -->

Appendix B: DecisioNet Configuration Files B-17

<!-- PeriodicSumcheckBedcheck -->

<!-- Whether the ESL Manager is enabled to schedule automatic -->

<!-- periodic sumcheck bedchecks. -->

<!-- Values: valid time period specification -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="PeriodicSumcheckBedcheck">0</param>

<!-- Section: ESL Manager -->

<!-- SumcheckBedcheckRecurrence -->

<!-- How often automatically scheduled Sumcheck (data) -->

<!-- Bedchecks take place -->

<!-- Values: valid time period specification -->

<!-- default = daily (P0Y0M1DT0H0M0S) -->

<!-- Note: only used if PeriodicSumcheckBedcheck is enabled -->

<param name="SumcheckBedcheckRecurrence">P0Y0M1DT0H0M0S</param>

<!-- Section: ESL Manager -->

<!-- SumcheckBedcheckStartDate -->

<!-- The effective start date of automatic SumcheckBedchecks -->

<!-- Note that this parameter just gives a starting -->

<!-- point for the recurrence. It does not have to be -->

<!-- absolute, nor does it have to be continuously updated. -->

<!-- It simply gives A start date and time as a jumping off -->

<!-- point for use with the associated recurrence. -->

<!-- For example: If the action is desired every Monday at -->

<!-- 1am, then the recurrence would be P0Y0M7DT0H0M0S, and -->

<!-- the start date could be ANY date in the past that -->

<!-- happened to be a Monday, along with a time of 1am, -->

<!-- say 20010205010000 -->

<!-- Values: valid time stamp (YYYYMMDDhhmmss) -->

<!-- default (if missing or invalid) = time config file read -->

B-18 Appendix B: DecisioNet Configuration Files

<!-- Note: only used if PeriodicSumcheckBedcheck is enabled -->

<!-- <param name="SumcheckBedcheckStartDate">20000101000000</param> -->

<!-- Section: ESL Manager -->

<!-- TransactionRecordLifetime -->

<!-- How long after a transaction completes does -->

<!-- the transaction record remain in the transaction log -->

<!-- table? -->

<!-- Values: valid time period specification -->

<!-- default = 2 hours (P0Y0M0DT2H0M0S) -->

<param name="TransactionRecordLifetime">P0Y0M0DT2H0M0S</param>

<!-- Section: ESL Manager -->

<!-- SuccessfulSpoolRecordLifetime -->

<!-- How long after a successful spool record completes -->

<!-- does the spool log record remain in the spool log table? -->

<!-- Note that update image requests associated with spool -->

<!-- records being deleted are deleted from the update image -->

<!-- table -->

<!-- Values: valid time period specification -->

<!-- default = 1 minute (P0Y0M0DT0H1M0S) -->

<param name="SuccessfulSpoolRecordLifetime">P0Y0M0DT0H1M0S</param>

<!-- Section: ESL Manager -->

<!-- ErroredSpoolRecordLifetime -->

<!-- How long after a spool record completes with errors -->

<!-- does the spool log record remain in the spool log table? -->

<!-- Note that update image requests associated with spool -->

<!-- records being deleted are deleted from the update image -->

<!-- table -->

<!-- Values: valid time period specification -->

<!-- default = 3 days (P0Y0M3DT0H0M0S) -->

Appendix B: DecisioNet Configuration Files B-19

<param name="ErroredSpoolRecordLifetime">P0Y0M3DT0H0M0S</param>

<!-- Section: ESL Manager -->

<!-- MaxNumberUpdateRetries -->

<!-- Maximum number of times an update request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 10 -->

<param name="MaxNumberUpdateRetries">10</param>

<!-- Section: ESL Manager -->

<!-- MaxUpdateRetryPeriod -->

<!-- Maximum amount of time an update request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 10 minutes (P0Y0M0DT0H10M0S) -->

<param name="MaxUpdateRetryPeriod">PT10M</param>

<!-- Section: ESL Manager -->

<!-- MinNumberUpdateRetries -->

B-20 Appendix B: DecisioNet Configuration Files

<!-- Minimum number of times an update request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 2 -->

<param name="MinNumberUpdateRetries">2</param>

<!-- Section: ESL Manager -->

<!-- MinUpdateRetryPeriod -->

<!-- Minimum amount of time an update request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 1 second (P0Y0M0DT0H0M1S) -->

<param name="MinUpdateRetryPeriod">PT1S</param>

<!-- Section: ESL Manager -->

<!-- MaxNumberBedcheckRetries -->

<!-- Maximum number of times an Bedcheck request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

Appendix B: DecisioNet Configuration Files B-21

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 10 -->

<param name="MaxNumberBedcheckRetries">10</param>

<!-- Section: ESL Manager -->

<!-- MaxBedcheckRetryPeriod -->

<!-- Maximum amount of time an Bedcheck request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 10 minutes (P0Y0M0DT0H10M0S) -->

<param name="MaxBedcheckRetryPeriod">PT10M</param>

<!-- Section: ESL Manager -->

<!-- MinNumberBedcheckRetries -->

<!-- Minimum number of times an Bedcheck request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 2 -->

B-22 Appendix B: DecisioNet Configuration Files

<param name="MinNumberBedcheckRetries">2</param>

<!-- Section: ESL Manager -->

<!-- MinBedcheckRetryPeriod -->

<!-- Minimum amount of time an Bedcheck request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 1 second (P0Y0M0DT0H0M1S) -->

<param name="MinBedcheckRetryPeriod">PT1S</param>

<!-- Section: ESL Manager -->

<!-- MaxNumberFindRetries -->

<!-- Maximum number of times an Find request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 2 -->

<param name="MaxNumberFindRetries">2</param>

<!-- Section: ESL Manager -->

Appendix B: DecisioNet Configuration Files B-23

<!-- MaxFindRetryPeriod -->

<!-- Maximum amount of time an Find request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 5 minutes (P0Y0M0DT0H10M0S) -->

<param name="MaxFindRetryPeriod">PT5M</param>

<!-- Section: ESL Manager -->

<!-- MinNumberFindRetries -->

<!-- Minimum number of times an Find request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 0 -->

<param name="MinNumberFindRetries">0</param>

<!-- Section: ESL Manager -->

<!-- MinFindRetryPeriod -->

<!-- Minimum amount of time an Find request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

B-24 Appendix B: DecisioNet Configuration Files

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 1 second (P0Y0M0DT0H0M1S) -->

<param name="MinFindRetryPeriod">PT1S</param>

<!-- Section: ESL Manager -->

<!-- MaxNumberAssignRetries -->

<!-- Maximum number of times an Assign request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 10 -->

<param name="MaxNumberAssignRetries">10</param>

<!-- Section: ESL Manager -->

<!-- MaxAssignRetryPeriod -->

<!-- Maximum amount of time an Assign request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 10 minutes (P0Y0M0DT0H10M0S) -->

Appendix B: DecisioNet Configuration Files B-25

<param name="MaxAssignRetryPeriod">PT10M</param>

<!-- Section: ESL Manager -->

<!-- MinNumberAssignRetries -->

<!-- Minimum number of times an Assign request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 2 -->

<param name="MinNumberAssignRetries">2</param>

<!-- Section: ESL Manager -->

<!-- MinAssignRetryPeriod -->

<!-- Minimum amount of time an Assign request is retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 1 second (P0Y0M0DT0H0M1S) -->

<param name="MinAssignRetryPeriod">PT1S</param>

B-26 Appendix B: DecisioNet Configuration Files

<!-- Section: ESL Manager -->

<!-- MaxNumberForceSearchModeRetries -->

<!-- Maximum number of times an ForceSearchMode request is -->

<!-- retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 10 -->

<param name="MaxNumberForceSearchModeRetries">10</param>

<!-- Section: ESL Manager -->

<!-- MaxForceSearchModeRetryPeriod -->

<!-- Maximum number of times an ForceSearchMode request is -->

<!-- retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 10 minutes (P0Y0M0DT0H10M0S) -->

<param name="MaxForceSearchModeRetryPeriod">PT10M</param>

<!-- Section: ESL Manager -->

<!-- MinNumberForceSearchModeRetries -->

<!-- Maximum number of times an ForceSearchMode request is -->

<!-- retried -->

Appendix B: DecisioNet Configuration Files B-27

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: non negative integer -->

<!-- default = 2 -->

<param name="MinNumberForceSearchModeRetries">2</param>

<!-- Section: ESL Manager -->

<!-- MinForceSearchModeRetryPeriod -->

<!-- Maximum number of times an ForceSearchMode request is -->

<!-- retried -->

<!-- at the ESL Manager level when errors occur. After -->

<!-- retries are exhausted, spool record is marked with last -->

<!-- error received. The record is always retried so that -->

<!-- both the minimum number of retries have been done and so -->

<!-- that the minimum retry period has elapsed, but retrying -->

<!-- stops when either the maximum number of retries have -->

<!-- have been done or the maximum retry period has elapsed, -->

<!-- whichever comes first. -->

<!-- Values: valid time period specification -->

<!-- default = 1 second (P0Y0M0DT0H0M1S) -->

<param name="MinForceSearchModeRetryPeriod">PT1S</param>

<!-- Section: ESL Manager -->

<!-- MaxCBSUpdateResponseWait -->

<!-- How long does the ESL Manager wait for a "fire event" -->

<!-- from the CBS Manager before explicit requesting the -->

<!-- results of a spool log transaction? -->

<!-- Values: valid time period specification -->

<!-- default = 5 minutes (P0Y0M0DT0H5M0S) -->

B-28 Appendix B: DecisioNet Configuration Files

<param name="MaxCBSUpdateResponseWait">PT5M</param>

<!-- Section: ESL Manager -->

<!-- SumcheckCorrectiveAction -->

<!-- When a sumcheck (data) bedcheck fails, should corrective -->

<!-- action be taken automatically? If so, a FORCED update -->

<!-- is issued for the ESL that failed. -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="SumcheckCorrectiveAction">1</param>

<!-- Section: ESL Manager -->

<!-- PingUnresponsiveTags -->

<!-- When tags fail to respond to a find command, should -->

<!-- the tags be periodically "pinged" (i.e. another find -->

<!-- issued) to see if the ESL comes back into communication? -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="PingUnresponsiveTags">1</param>

<!-- Section: ESL Manager -->

<!-- IgnoreUnresponsiveTags -->

<!-- When tags fail to respond to a find command, they are -->

<!-- marked as unresponsive. Should such unresponsive tags -->

<!-- be ignored for future updates, bedchecks, and verifies? -->

<!-- It may be desirable to continue to send commands to -->

<!-- unresponsive tags in cases of high noise, etc. -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="IgnoreUnresponsiveTags">1</param>

Appendix B: DecisioNet Configuration Files B-29

<!-- Section: ESL Manager -->

<!-- AutoFindAfterNoResponse -->

<!-- When a tag gives no response after an update, bedcheck, -->

<!-- or verify, should there be an automatic find to try to -->

<!-- locate these tags? It may be desirable to turn off auto -->

<!-- find in coordination with turning off the -->

<!-- IgnoreUnresponsiveTags flag in situations with high -->

<!-- noise. -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="AutoFindAfterNoResponse">1</param>

<!-- Section: ESL Manager -->

<!-- SearchModeAfterNotFound -->

<!-- When a tag gives no response after a find has been -->

<!-- issued, should the ESL Manager send a command to try -->

<!-- to place the tag in to search mode in an effort to -->

<!-- reestablish communications (under the assumption that -->

<!-- the tag may be able to hear the CBS but not vice versa)? -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="SearchModeAfterNotFound">1</param>

<!-- Section: ESL Manager -->

<!-- AutoAssignAfterFind -->

<!-- When a tag is found after a find is issued, should an -->

<!-- automatic assign be issued? -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="AutoAssignAfterFind">1</param>

B-30 Appendix B: DecisioNet Configuration Files

<!-- Section: ESL Manager -->

<!-- ForceSearchModeAfterFindFail -->

<!-- When a tag does not respond to a find, should the ESL -->

<!-- Manager send a command to force the tag to go into -->

<!-- search mode? -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="ForceSearchModeAfterFindFail">1</param>

<!-- Section: ESL Manager -->

<!-- UnresponsiveTagRecurrence -->

<!-- How often does the ESL Manager ping unresponsive tags? -->

<!-- Values: valid time period specification -->

<!-- default = daily (P0Y0M1DT0H0M0S) -->

<!-- Note: only used if PingUnresponseTags is enabled -->

<param name="UnresponseTagRecurrence">P0Y0M1DTH0M0S</param>

<!-- Section: ESL Manager -->

<!-- UnresponsiveTagStartDate -->

<!-- The effective start date of automatic UnresponsiveTags -->

<!-- Note that this parameter just gives a starting -->

<!-- point for the recurrence. It does not have to be -->

<!-- absolute, nor does it have to be continuously updated. -->

<!-- It simply gives A start date and time as a jumping off -->

<!-- point for use with the associated recurrence. -->

<!-- For example: If the action is desired every Monday at -->

<!-- 1am, then the recurrence would be P0Y0M7DT0H0M0S, and -->

<!-- the start date could be ANY date in the past that -->

<!-- happened to be a Monday, along with a time of 1am, -->

<!-- say 20010205010000 -->

<!-- Values: valid time stamp (YYYYMMDDhhmmss) -->

Appendix B: DecisioNet Configuration Files B-31

<!-- default (if missing or invalid) = time config file read -->

<!-- Note: only used if PingUnresponseTags is enabled -->

<!-- <param name="UnresponsiveTagStartDate">20000101000000</param> -->

<!-- Section: ESL Manager -->

<!-- PriceChecking -->

<!-- When tags receive successful notification of an update, -->

<!-- should a follow-up sumcheck (data) bedcheck be issued -->

<!-- to ensure the correct information is on the tag? -->

<!-- Values: 0(=disabled)/1(=enabled) -->

<!-- default = 1 (enabled) -->

<param name="PriceChecking">1</param>

<!-- Section: ESL Manager -->

<!-- DefaultUpdatePriority -->

<!-- Default Priority to use for update transactions when -->

<!-- no priority is specified. -->

<!-- Values: integer 1 through 10, 1 being highest priority -->

<!-- default = 3 -->

<param name="DefaultUpdatePriority">3</param>

<!-- Section: ESL Manager -->

<!-- DefaultBedcheckPriority -->

<!-- Default Priority to use for Bedcheck transactions when -->

<!-- no priority is specified. -->

<!-- Values: integer 1 through 10, 1 being highest priority -->

<!-- default = 5 -->

<param name="DefaultBedcheckPriority">5</param>

B-32 Appendix B: DecisioNet Configuration Files

<!-- Section: ESL Manager -->

<!-- DefaultVerifyPriority -->

<!-- Default Priority to use for Verify transactions when -->

<!-- no priority is specified. -->

<!-- Values: integer 1 through 10, 1 being highest priority -->

<!-- default = 7 -->

<param name="DefaultVerifyPriority">7</param>

<!-- Section: ESL Manager -->

<!-- DefaultFindPriority -->

<!-- Default Priority to use for Find transactions when -->

<!-- no priority is specified. -->

<!-- Values: integer 1 through 10, 1 being highest priority -->

<!-- default = 10 -->

<param name="DefaultFindPriority">10</param>

<!-- Section: ESL Manager -->

<!-- DefaultAssignPriority -->

<!-- Default Priority to use for Assign transactions when -->

<!-- no priority is specified. -->

<!-- Values: integer 1 through 10, 1 being highest priority -->

<!-- default = 3 -->

<param name="DefaultAssignTimeslotPriority">3</param>

<!-- Section: ESL Manager -->

<!-- DefaultForceSearchModePriority -->

<!-- Default Priority to use for forcing an ESL into search -->

<!-- mode. -->

<!-- Values: integer 1 through 10, 1 being highest priority -->

Appendix B: DecisioNet Configuration Files B-33

<!-- default = 3 -->

<param name ="DefaultForceSearchModePriority">3</param>

<!-- Section: ESL Manager -->

<!-- TransactionResolveSleepTime -->

<!-- The amount of time (in milliseconds) that the ESL -->

<!-- Manager sleeps between ESL record processing during -->

<!-- a transaction resolution. -->

<!-- Values: non-negative integer -->

<!-- default = 50 -->

<param name="TransactionResolveSleepTime">50</param>

<!-- Section: ESL Manager -->

<!-- TransactionThreadSleepTime -->

<!-- The amount of time (in milliseconds) that the ESL -->

<!-- Manager sleeps between transactions during high-level -->

<!-- transaction processing. -->

<!-- Values: non-negative integer -->

<!-- default = 500 -->

<param name="TransactionThreadSleepTime">500</param>

<!-- Section: ESL Manager -->

<!-- SpoolLogThreadSleepTime -->

<!-- The amount of time (in milliseconds) that the ESL -->

<!-- Manager sleeps between spool log transaction processing -->

<!-- Values: non-negative integer -->

<!-- default = 200 -->

<param name="SpoolLogThreadSleepTime">200</param>

B-34 Appendix B: DecisioNet Configuration Files

<!-- Section: ESL Manager -->

<!-- ProcessingThreadSleepTime -->

<!-- The amount of time (in milliseconds) that the ESL -->

<!-- Manager sleeps between processing CBS Manager requests -->

<!-- Values: non-negative integer -->

<!-- default = 0 -->

<param name="ProcessingThreadSleepTime">0</param>

<!-- Section: ESL Manager -->

<!-- MaxHistoryDepth -->

<!-- The maximum history depth for any type of transaction -->

<!-- sequence. -->

<!-- Values: unsigned integer -->

<!-- default = 10 -->

<param name="MaxHistoryDepth">10</param>

<!-- Section: ESL Manager -->

<!-- MaxAutofindSequence -->

<!-- The maximum number of "autofind" sequences to be issues -->

<!-- before stopping. An autofind sequence consists of a -->

<!-- find followed by an assign followed by an appropriate -->

<!-- repeat of the original transaction (update,bedchk, etc.) -->

<!-- Note that this is affected by MaxHistoryDepth, in that -->

<!-- MaxHistoryDepth counts EVERY individual transaction and -->

<!-- could cause stopping before MaxAutofindSequence is -->

<!-- exhausted. -->

<!-- Values: unsigned integer -->

<!-- default = 1 -->

<param name="MaxAutofindSequence">1</param>

<!-- Section: ESL Manager -->

Appendix B: DecisioNet Configuration Files B-35

<!-- MaxPricecheckCorrectiveDepth -->

<!-- The maximum number of pricecheck/corrective action tasks -->

<!-- to process before stopping. Price checks and corrective -->

<!-- actions on sumchecks are related, in that one can -->

<!-- eventually cause the other. -->

<!-- Note that this is affected by MaxHistoryDepth, in that -->

<!-- MaxHistoryDepth counts EVERY individual transaction and -->

<!-- could cause stopping before this parameter is exhausted. -->

<!-- Values: unsigned integer -->

<!-- default = 3 -->

<param name="MaxPricecheckCorrectiveDepth">3</param>

<!-- Section: ESL Manager -->

<!-- MaxTransactionRecordBlock -->

<!-- The maximum record block size for Transaction record -->

<!-- sets. The larger the number, the greater the memory -->

<!-- usage, but the faster the processing. -->

<!-- Values: unsigned integer -->

<!-- default = 128 -->

<param name="MaxTransactionRecordBlock">128</param>

<!-- Section: ESL Manager -->

<!-- MaxESLTransactionRecordBlock -->

<!-- The maximum record block size for ESLTransaction record -->

<!-- sets. The larger the number, the greater the memory -->

<!-- usage, but the faster the processing. -->

<!-- Values: unsigned integer -->

<!-- default = 128 -->

<param name="MaxESLTransactionRecordBlock">128</param>

<!-- Section: ESL Manager -->

B-36 Appendix B: DecisioNet Configuration Files

<!-- MaxTransactionRecordBlock -->

<!-- The maximum record block size for ESL record -->

<!-- sets. The larger the number, the greater the memory -->

<!-- usage, but the faster the processing. -->

<!-- Values: unsigned integer -->

<!-- default = 128 -->

<param name="MaxESLRecordBlock">128</param>

<!-- Section: ESL Manager -->

<!-- MaxUpdateImageAgeBeforeRefresh -->

<!-- When update requests are posted to the spool file, an -->

<!-- update image is also posted to the update image file and -->

<!-- represents the data obtained from the data reader. -->

<!-- Since the update image can get out of date, this -->

<!-- parameter gives the ability to specify how old an update -->

<!-- image may get before the ESL Manager refreshes the -->

<!-- update image with a fresh read from the data reader. A -->

<!-- setting of all 0's forces the ESL Manager to request the -->

<!-- data from the data reader each time the update is sent. -->

<!-- Values: valid time period specification -->

<!-- default = 7 days (P0Y0M7DT0H0M0S) -->

<param name="MaxUpdateImageAgeBeforeRefresh">P0Y0M7DTH0M0S</param>

<!-- Section: ESL Manager -->

<!-- OperatingMode -->

<!-- Mode the ESL Manager is operating in. -->

<!-- Values: INSTALL or NORMAL -->

<!-- default = NORMAL -->

<!-- THIS PARAMETER IS MAINTAINED BY THE ESL MANAGER AND -->

<!-- SHOULD NOT BE MODIFIED. -->

<param name="OperatingMode">NORMAL</param>

</section>

Appendix B: DecisioNet Configuration Files B-37

<!-- End ESL Manager Section -->

<!-- DecisioNet Console Section

<section name="DecisioNet Console">

<!-- TraceFileName -->

<!-- TraceLevel -->

<!-- Specifies the trace log filename and the logging level. -->

<param name="TraceFileName">dnConsoleTrace.trc</param>

<param name="TraceLevel">0</param>

<!-- ForcePrintEnabled -->

<!-- GCA parameter -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<param name="ForcePrintEnabled">0</param>

<!-- PrintOverlaysEnabled -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether the system provides the capability to -->

<!-- print overlays or reprint overlays -->

<param name="PrintOverlaysEnabled">1</param>

<!-- PriceLevel -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether the system provides input fields for -->

<!-- price level at the Link/Modify/Unlink screens -->

<param name="PriceLevel">0</param>

<!-- PriceUnit -->

<!-- Valid Values = 0 1 -->

<!-- Default = 1 -->

<!-- controls whether the system provides field for -->

<!-- unit at the Link/Modify/Unlink screens -->

<param name="ProductUnit">1</param>

<!-- ESLDefaultToProduct -->

<!-- Valid Values = 0 1 -->

<!-- Default = 1 -->

<!-- controls whether the which field recieves input focus -->

<!-- Product Number or Serial Number on the -->

B-38 Appendix B: DecisioNet Configuration Files

<!-- Link/Modify/Unlink screens -->

<param name="ESLDefaultToProduct">1</param>

<!-- Report Sub Section -->

<!-- After changing the SQL statement, please ensure to chg. -->

<!-- displayed column headings in the verbage xml file too. -->

<!-- ReportSQL1 -->

<!-- SQL query to generate the report -->

<param name="ReportSQL1">select DATE_FORMAT(esl.LASTNORESPONSE,"%Y/%m/%d

%H:%i"), item.item_desc, HEX(esl.SERIAL_NUMBER), location_description.location_name, esl.LINK_ID, esl.LINK_SUB_ID, DATE_FORMAT(esl.LASTACKTIME,"%Y/%m/%d %H:%i"), ELT(FIELD(esl.UNRESPONSIVE_FLAG,"1","0"),"UNRESPONSIVE","COMMUNICATING") from location_description, esl, item WHERE location_description.location_id = esl.esl_location_id AND esl.UNRESPONSIVE_FLAG = "1"

AND item.item_id = esl.link_id AND item.item_sub_id = esl.link_sub_id</param>

<!-- ReportSQL1SelectColumn -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether the checkbox is present in the first -->

<!-- column of the report -->

<param name="ReportSQL1SelectColumn">1</param>

<!-- ReportSQL1KeyColumn -->

<!-- Valid Values = 0 .. nbr of columns in SQL query - 1 -->

<param name="ReportSQL1KeyColumn">3</param>

<!-- ReportSQL1Button -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether there is a button in addition to the -->

<!-- 'Cancel' button on the screen -->

<param name="ReportSQL1Button">1</param>

<!-- ReportSQL2 -->

<!-- SQL query to generate the report -->

<param name="ReportSQL2">select DATE_FORMAT(spool_log.record_complete_date,"%Y/%m/%d %H:%i"), DATE_FORMAT(spool_log.start_date,"%Y/%m/%d %H:%i"), item.item_desc, Appendix B: DecisioNet Configuration Files B-39 HEX(spool_log.SERIAL_NUMBER), location_description.location_name, spool_log.LINK_ID, spool_log.LINK_SUB_ID, ELT(spool_log.record_type,"UPDATE","BEDCHECK","VERIFY","FIND","ASSIGN","SEARCH")

, HEX(spool_log.record_Status + 1) from location_description, spool_log, item, esl WHERE esl.serial_number = spool_log.serial_number AND location_description.location_id = esl.esl_location_id AND item.item_id = spool_log.link_id AND item.item_sub_id = spool_log.link_sub_id AND spool_log.record_status &lt; 0</param>

<!-- ReportSQL2SelectColumn -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether the checkbox is present in the first -->

<!-- column of the report -->

<param name="ReportSQL2SelectColumn">1</param>

<!-- ReportSQL2KeyColumn -->

<!-- Valid Values = 0 .. nbr of columns in SQL query - 1 -->

<param name="ReportSQL2KeyColumn">4</param>

<!-- ReportSQL2Button -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether there is a button in addition to the -->

<!-- 'Cancel' button on the screen -->

<param name="ReportSQL2Button">1</param>

<!-- ReportSQL3 -->

<!-- SQL query to generate the report -->

<param name="ReportSQL3">select DATE_FORMAT(esl.LASTNORESPONSE,"%Y/%m/%d

%H:%i"), item.item_desc, HEX(esl.SERIAL_NUMBER), esl_type_description.esl_type_name, location_description.location_name, esl.PREV_LINK_ID, esl.PREV_LINK_SUB_ID, DATE_FORMAT(esl.LASTACKTIME,"%Y/%m/%d

%H:%i"), ELT(FIELD(esl.UNRESPONSIVE_FLAG,"1","0"),"UNRESPONSIVE","COMMUNICATING") esl_type_description.esl_type_high_serial</param>

from location_description, esl, item, esl_type_description WHERE location_description.location_id = esl.esl_location_id AND esl.Link_type_id = 0 AND item.item_id = esl.prev_link_id AND item.item_sub_id = esl.prev_link_sub_id AND esl.serial_number &gt; esl_type_description.esl_type_low_serial AND esl.serial_number &lt;

B-40 Appendix B: DecisioNet Configuration Files

<!-- ReportSQL1SelectColumn -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether the checkbox is present in the first -->

<!-- column of the report -->

<param name="ReportSQL3SelectColumn">0</param>

<!-- ReportSQL3KeyColumn -->

<!-- Valid Values = 0 .. nbr of columns in SQL query - 1 -->

<param name="ReportSQL3KeyColumn">2</param>

<!-- ReportSQL3Button -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether there is a button in addition to the -->

<!-- 'Cancel' button on the screen -->

<param name="ReportSQL3Button">0</param>

<!-- ReportSQL4 -->

<!-- SQL query to generate the report -->

<param name="ReportSQL4">select DATE_FORMAT(spool_log.record_complete_date,"%Y/%m/%d %H:%i"), DATE_FORMAT(spool_log.start_date,"%Y/%m/%d %H:%i"), item.item_desc, HEX(spool_log.SERIAL_NUMBER), location_description.location_name, spool_log.LINK_ID, spool_log.LINK_SUB_ID, ELT(spool_log.record_type,"UPDATE","BEDCHECK","VERIFY","FIND","ASSIGN","SEARCH")

, ELT((spool_log.record_Status + 1),"SUCCESS","IN PROGRESS","PENDING") from location_description, spool_log, item, esl WHERE esl.serial_number = spool_log.serial_number AND location_description.location_id = esl.esl_location_id AND item.item_id = spool_log.link_id AND item.item_sub_id = spool_log.link_sub_id AND spool_log.record_status = 0</param>

<!-- ReportSQL4SelectColumn -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether the checkbox is present in the first -->

<!-- column of the report -->

<param name="ReportSQL4SelectColumn">0</param>

<!-- ReportSQL4KeyColumn -->

<!-- Valid Values = 0 .. nbr of columns in SQL query - 1 -->

Appendix B: DecisioNet Configuration Files B-41

<param name="ReportSQL4KeyColumn">3</param>

<!-- ReportSQL4Button -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether there is a button in addition to the -->

<!-- 'Cancel' button on the screen -->

<param name="ReportSQL4Button">0</param>

<!-- ReportSQL5 -->

<!-- SQL query to generate the report -->

<param name="ReportSQL5">select DATE_FORMAT(spool_log.record_complete_date,"%Y/%m/%d %H:%i"), DATE_FORMAT(spool_log.start_date,"%Y/%m/%d %H:%i"), item.item_desc, HEX(spool_log.SERIAL_NUMBER), location_description.location_name, spool_log.LINK_ID, spool_log.LINK_SUB_ID, ELT(spool_log.record_type,"UPDATE","BEDCHECK","VERIFY","FIND","ASSIGN","SEARCH")

, ELT((spool_log.record_Status + 1),"SUCCESS","IN PROGRESS","PENDING") from location_description, spool_log, item, esl WHERE esl.serial_number = spool_log.serial_number AND location_description.location_id = esl.esl_location_id AND item.item_id = spool_log.link_id AND item.item_sub_id = spool_log.link_sub_id AND spool_log.record_status &gt; 0</param>

<!-- ReportSQL5SelectColumn -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether the checkbox is present in the first -->

<!-- column of the report -->

<param name="ReportSQL5SelectColumn">0</param>

<!-- ReportSQL5KeyColumn -->

<!-- Valid Values = 0 .. nbr of columns in SQL query - 1 -->

<param name="ReportSQL5KeyColumn">3</param>

<!-- ReportSQL5Button -->

<!-- Valid Values = 0 1 -->

<!-- Default = 0 -->

<!-- controls whether there is a button in addition to the -->

<!-- 'Cancel' button on the screen -->

<param name="ReportSQL5Button">0</param>

B-42 Appendix B: DecisioNet Configuration Files

</section>

<!-- End DecisioNet Console Section -->

<!-- Data Reader Configuration Parameters -->

<section name="Data Reader">

<!-- Number of digits after the decimal postion for the -->

<!-- unit price field. -->

<!-- Valid Values: 0, 2, 3 -->

<param name="PriceDecimalPosition">2</param>

<!-- Number of digits after the decimal postion for the -->

<!-- price field. -->

<!-- Valid Values: 0, 2, 3 -->

<param name="UnitPriceDecimalPosition">2</param>

<!-- Name of the debug file. This will be created in -->

<!-- DecisioNet data directory. -->

<param name="DebugFilename">DataReaderServer.log</param>

<!-- Debug level -->

<!-- 0 - None -->

<!-- 1 - Errors -->

<!-- 2 - Function Entry Points -->

<!-- 3 - Messaging Trace -->

<!-- 4 - Full Trace -->

<param name="DebugLevel">2</param>

<!-- What should the tag display when prices are < 1.00?-->

<!-- Valid Values: CentSign, LeadingZero, NoLeadingZero -->

<!-- For instance, if the price is .90 in the U.S. -->

<!-- CentSign would display 90c where c is the cent sign-->

<!-- LeadingZero would display 0.90 -->

<!-- NoLeadingZero would display .90 -->

<param name="PriceLessThanDollar">CentSign</param>

<!-- What should the tag display when unit prices are -->

<!-- less than < 1.00? -->

<!-- Valid Values: CentSign, LeadingZero, NoLeadingZero -->

<!-- For instance, if the unit price is .90 in the U.S. -->

<!-- CentSign would display 90.0c where c is the cent -->

<!-- sign. -->

<!-- LeadingZero would display 0.90 -->

<!-- NoLeadingZero would display .90 -->

<param name="UnitPriceLessThanDollar">LeadingZero</param>

<!-- What is the character used for a decimal separator -->

<!-- Valid Values: Comma, Period -->

<param name="DecimalSymbol">Comma</param>

<!-- What king of rounding method should be used for -->

Appendix B: DecisioNet Configuration Files B-43

<!-- price and unit price. -->

<!-- Valid Values: Normal, Up, Down -->

<!-- For instance, the price or unit price is 3.555 -->

<!-- Normal would display 3.56 -->

<!-- Up would display 3.56 -->

<!-- Down would display 3.55 -->

<param name="RoundingType">Normal</param>

</section>

</config>

DecisioNet Task Manager Configuration file (taskman.cfg)

# This is the configuration file for the DecisioNet 3.0 Task Manager.

# FREQUENCY

# specifies the number of MINUTES between each check of the

# context directories for new or updated Task files.

# Default if not specified is 1 minute. FREQUENCY=1

# KILLINTERVAL

# When Task Mgr. is requested to shut down, it first sends REQUESTS

# to all the apps. to close themselves. If after a while the apps

# still have not closed themselves, TM kills them with an NT

# "TerminateProcess()". KILLINTERVAL specifies how many seconds to wait

# between asking the apps to close themselves and killing the remaining

# alive apps.

# Default if not specified is 15 seconds. KILLINTERVAL=15

# DEADCHECK

# specifies the number of seconds between each time TM checks to see

# if any tasks have died. This is needed because currently TM uses

# a polling method to determine if tasks have died. Normally, in NT

# a "WaitForMultipleObjects()" would be executed on the process handles

# of all the tasks, but that API can only handle a max of 64 handles. So

# in order for TM to handle > 64 tasks, this method is used. The number

# should be an even divisor of 60 (number of seconds in a minute), and if

# it is not, TM will round it UP to the NEXT even divisor of 60.

B-44 Appendix B: DecisioNet Configuration Files

# Default if not specified is 5 seconds. DEADCHECK=3

# EXCEPTION

# Specifies a default exception handler for tasks which don't have one

# defined to that task in the task file. Exception handlers are programs

# which are run immediately if the main task dies and exits with a

# non-zero status. The exception handler will be run with the following

# args passed to it (in addition to whatever args are specified in the

# config file):

# <exception hldr [any args]> <task exit code> <task #> <task cmd line>

# Default is to NOT have a default exception handler

# EXCEPTION=excphdlr.exe -v (for example only - no such program exists)

# CONTEXT

# Specifies a new context to Task Manager. The context name must be

# unique and not have any whitespace in it. It MUST be followed by

# a TFILES= keyword to specify where to get the task files for this

# context.

# TFILES

# Specifies a path and a file mask for finding valid task files for

# the preceeding context. If the path specified is not ABSOLUTE, ie.

# it doesn't start with either a drive letter or a \, then the path

# is relative from the DNET Data Directory (usually c:\DNET\data)

# The mask specifies which files in that directory will be scanned for

# task information. Each file can have information about one or more

# tasks, and there can be multiple task files in the directory. Files

# in the directory that do not match the mask are ignored. CONTEXT=DNET TFILES=dnet.tm\*.inf CONTEXT=TASK_MANAGER TFILES=taskman.tm\*.inf DecisioNet Host Bridge Configuration file

(dnhostbridge.xml)

<?xml version="1.0" standalone="yes"?>

<!DOCTYPE HostDataBridge SYSTEM "dnhostbridge.dtd">

<HostDataBridge>

<General Appendix B: DecisioNet Configuration Files B-45 DatabaseName="dnet"

MaxRecordLength="4096"

MaxFields="999"

MaxFieldLen="256"

Delimiter=","

SleepTime="5"

Verbose="No"></General>

<FileDefinition TypeID="KVAT"

FileName="KVATMOD"

Description="Host Modification Data"

Delimiter=",">

<SendESLData Enabled="No"

LinkID_Offset="1"

LinkID_StripCheckDigit="No"

LinkID_ZeroFill="Yes"

LinkID_Default=""

LinkSubID_Offset="2"

LinkSubID_StripCheckDigit="No"

LinkSubID_ZeroFill="Yes"

LinkSubID_Default=""

LinkType = "1"></SendESLData>

<UpdateLabelRecord Enabled="No"

LinkID_Offset="1"

LinkID_StripCheckDigit="No"

LinkID_Default=""

LinkID_ZeroFill="Yes"

LinkSubID_Offset="2"

LinkSubID_StripCheckDigit="No"

LinkSubID_ZeroFill="Yes"

LinkSubID_Default=""

LinkType = "1"></UpdateLabelRecord>

<RecordDefinition Table="ITEM"

Audit="Yes">

<Field Offset="1"

Name="ITEM_ID"

Type="CHAR(24)"

Default=""

PrimaryKey="Yes"

ZeroFill="No"

Length="24"

OverlayPrint="Yes"

IsLinkID="Yes"

Required="Yes"></Field>

<Field Offset="0"

B-46 Appendix B: DecisioNet Configuration Files Name="ITEM_SUB_ID"

Type="CHAR(24)"

Default="0"

SecondaryKey="Yes"

ZeroFill="No"

Length="24"

IsLinkSubID="Yes"

OverlayPrint="No"

Required="Yes"></Field>

<Field Offset="15"

Name="PACKAGE_SIZE"

Type="DECIMAL(10,4)"

Default="1.00"

OverlayPrint="Yes"

IsPackageSize="Yes"></Field>

<Field Offset="0"

Name="CONVERSION_FACTOR"

Type="DECIMAL(10,4)"

Default="1.00"

OverlayPrint="Yes"

IsMeasure="Yes"></Field>

<Field Offset="7"

Name="UOM_ID"

Type="INT"

Default=""

OverlayPrint="Yes"

IsHex="Yes"

IsUnitOfMeasure="Yes"></Field>

<Field Offset="4"

Name="ITEM_DESC"

Type="VARCHAR(50)"

Default=""

OverlayPrint="Yes"

IsDescription="Yes"></Field>

<Field Offset="8"

Name="UOM_DESC"

Type="VARCHAR(50)"

Default=""

OverlayPrint="Yes"

IsDescription="Yes"></Field>

</RecordDefinition>

</FileDefinition>

<FileDefinition TypeID="ITEM"

FileName="ITEMMOD"

Appendix B: DecisioNet Configuration Files B-47 Description="Host Modification Data"

Delimiter=",">

<SendESLData Enabled="No"

LinkID_Offset="1"

LinkID_StripCheckDigit="No"

LinkID_ZeroFill="No"

LinkID_Default=""

LinkSubID_Offset="2"

LinkSubID_StripCheckDigit="No"

LinkSubID_ZeroFill="No"

LinkSubID_Default=""

LinkType = "1"></SendESLData>

<UpdateLabelRecord Enabled="No"

LinkID_Offset="1"

LinkID_StripCheckDigit="No"

LinkID_Default=""

LinkID_ZeroFill="No"

LinkSubID_Offset="2"

LinkSubID_StripCheckDigit="No"

LinkSubID_ZeroFill="No"

LinkSubID_Default=""

LinkType = "1"></UpdateLabelRecord>

<RecordDefinition Table="ITEM"

Audit="Yes">

<Field Offset="1"

Name="ITEM_ID"

Type="CHAR(24)"

Default=""

PrimaryKey="Yes"

ZeroFill="No"

Length="24"

OverlayPrint="Yes"

IsLinkID="Yes"

Required="Yes"></Field>

<Field Offset="0"

Name="ITEM_SUB_ID"

Type="CHAR(24)"

Default="0"

SecondaryKey="Yes"

ZeroFill="No"

Length="24"

IsLinkSubID="Yes"

OverlayPrint="No"

Required="Yes"></Field>

<Field B-48 Appendix B: DecisioNet Configuration Files Offset="2"

Name="PACKAGE_SIZE"

Type="DECIMAL(10,4)"

Default="1.00"

OverlayPrint="Yes"

IsPackageSize="Yes"></Field>

<Field Offset="4"

Name="CONVERSION_FACTOR"

Type="DECIMAL(10,4)"

Default="1.00"

OverlayPrint="Yes"

IsMeasure="Yes"></Field>

<Field Offset="3"

Name="UOM_ID"

Type="INT"

Default=""

OverlayPrint="Yes"

IsUnitOfMeasure="Yes"></Field>

<Field Offset="5"

Name="ITEM_DESC"

Type="VARCHAR(50)"

Default=""

OverlayPrint="Yes"

IsDescription="Yes"></Field>

</RecordDefinition>

</FileDefinition>

<FileDefinition TypeID="PRICE"

FileName="PRICEMOD"

Description="Price Modification Data"

Delimiter=",">

<SendESLData Enabled="Yes"

LinkID_Offset="1"

LinkID_StripCheckDigit="No"

LinkID_ZeroFill="No"

LinkID_Default=""

LinkSubID_Offset="2"

LinkSubID_StripCheckDigit="No"

LinkSubID_ZeroFill="No"

LinkSubID_Default=""

LinkType = "1"></SendESLData>

<UpdateLabelRecord Enabled="No"

LinkID_Offset="1"

LinkID_StripCheckDigit="No"

LinkID_Default=""

Appendix B: DecisioNet Configuration Files B-49 LinkID_ZeroFill="No"

LinkSubID_Offset="2"

LinkSubID_StripCheckDigit="No"

LinkSubID_ZeroFill="No"

LinkSubID_Default=""

LinkType = "1"></UpdateLabelRecord>

<RecordDefinition Table="ITEM"

Audit="Yes">

<Field Offset="1"

Name="ITEM_ID"

Type="CHAR(24)"

Default=""

PrimaryKey="Yes"

ZeroFill="No"

Length="24"

OverlayPrint="Yes"

IsLinkID="Yes"

Required="Yes"></Field>

<Field Offset="0"

Name="ITEM_SUB_ID"

Type="CHAR(24)"

Default="0"

SecondaryKey="Yes"

ZeroFill="No"

Length="24"

IsLinkSubID="Yes"

OverlayPrint="No"

Required="Yes"></Field>

</RecordDefinition>

</FileDefinition>

<FileDefinition TypeID="ESL"

FileName="PREEPLMOD"

Description="PRE ESL Tag Modification Data"

Delimiter=",">

<SendESLData Enabled="No"

LinkID_Offset="2"

LinkID_StripCheckDigit="No"

LinkID_ZeroFill="No"

LinkID_Default=""

LinkSubID_Offset="2"

LinkSubID_StripCheckDigit="Yes"

LinkSubID_ZeroFill="No"

LinkSubID_Default=""

LinkType = "1"></SendESLData>

<RecordDefinition B-50 Appendix B: DecisioNet Configuration Files Table="ESL"

Audit="No">

<Field Offset="2"

Name="LINK_ID"

Type="VARCHAR(24)"

Default="0"

ZeroFill="No"

StripCheckDigit="No"

Length="24"></Field>

<Field Offset="0"

Name="LINK_SUB_ID"

Type="VARCHAR(24)"

Default="0"

ZeroFill="No"

StripCheckDigit="No"

Length="24"></Field>

<Field Offset="8"

Name="SERIAL_NUMBER"

Type="INT"

Default=""

PrimaryKey="Yes"></Field>

<Field Offset="6"

Name="ESL_LOCATION_ID"

Type="INT"

Default=""

IsLocation="Yes"></Field>

<Field Offset="0"

Name="INSTALL_DATE"

Type="DATETIME"

Default="$(DATETIME)"></Field>

<Field Offset="0"

Name="ORPHAN_FLAG"

Type="ENUM"

Default="F"></Field>

</RecordDefinition>

</FileDefinition>

<FileDefinition TypeID="ESL"

FileName="ESLMOD"

Description="Front Back Tag Modification Data"

Delimiter=",">

<SendESLData Enabled="No"

LinkID_Offset="1"

Appendix B: DecisioNet Configuration Files B-51 LinkID_StripCheckDigit="No"

LinkID_ZeroFill="No"

LinkID_Default=""

LinkSubID_Offset="0"

LinkSubID_StripCheckDigit="Yes"

LinkSubID_ZeroFill="No"

LinkSubID_Default=""

LinkType = "1"></SendESLData>

<RecordDefinition Table="ESL"

Audit="No">

<Field Offset="1"

Name="SERIAL_NUMBER"

Type="INT"

Default=""

PrimaryKey="Yes"></Field>

<Field Offset="2"

Name="LINK_ID"

Type="VARCHAR(24)"

Default="0"

ZeroFill="No"

StripCheckDigit="No"

Length="24"></Field>

<Field Offset="0"

Name="LINK_SUB_ID"

Type="VARCHAR(24)"

Default="0"

ZeroFill="No"

StripCheckDigit="No"

Length="24"></Field>

<Field Offset="0"

Name="LINK_TYPE_ID"

Type="SMALLINT"

Default="1"></Field>

</RecordDefinition>

</FileDefinition>

</HostDataBridge>

B-52 Appendix B: DecisioNet Configuration Files