Gasboy CFN III Config Mnl User Manual

CFN Series

CFN III Configuration Manual for Windows NT

Version 3.4

MDE-4316C

Computer Programs and Documentation

Federal Communications Commission (FCC) Warning

All Gasboy computer programs (including software on diskettes and within memory chips) and documentation are copyrighted by, and shall remain the property of, Gasboy. Such computer programs and documents may also contain trade secret information. The duplication, disclosure, modification, or unauthorized use of computer programs or documentation is strictly prohibited, unless otherwise licensed by Gasboy.

This equipment has been tested and found to comply with the limits for a Class A digital device pursuant to Part 15 of the 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 harmful interference in which case the user will be required to correct the interference at his own expense. Changes or modifications not expressly approved by the manufacturer could void the user’s authority to operate this equipment.

Approvals

Gasboy, Greensboro, is an ISO 9001:2000 registered facility. Underwriters Laboratories (UL):

UL File# Products listed with UL

MH4314

MH6418

MH7404 MH10581 Key con t r o l u n i t , M o d e l G K E - B S e r i e s

All dispensers and self-contained pumping units

Power operated Transfer Pump Models 25, 25C, 26, 27, 28, 72, 72S, 72SP , 72X, 73 and 1820

Hand operated Transfer Pump Models 1230 Series, 1243 Series, 1520 and 1720 Series

Card reader terminals, Models 1000, 1000P Site controller, Model 2000S CFN Series Data entry terminals, Model TPK-900 Series Fuel Point Reader System

New York City Fire Department (NYFD):

NYFD C of A # Product

4823 9100A, 9140A, 9152A, 9153A,

4997 9822A, 9823A 5046 9100Q, 9140Q, 9152Q, 9153Q,

5087 8753K, 8853K, 9153K, 9853K

9800A, 9840A, 9850A, 9852A, 9853A, 9140

9800Q, 9840Q, 9852Q, 9853Q

(restricted to diesel and nonretail gasoline sales)

National Conference of Weights and Measures (NCWM) - Certificate of Compliance (CoC):

Gasboy pumps and dispensers are evaluated by NCWM under the National Type Evaluation Program (NTEP). NCWM has issued the following CoC:

CoC# Product Model # CoC# Product Model # CoC# Product Model #

95-179A2 Dispenser

95-136A5 Dispenser 9800 Series 91-057A3 Controller

9100 Retail Series, 8700 Series, 9700 Series

91-019A2 Dispenser

9100 Commercial Series

1000 Series FMS, 2000S-CFN Series

California Air Resources Board (CARB):

Executive Order # Product

G-70-52-AM Balance Vapor Recovery G-70-150-AE VaporVac

Patents

Gasboy products are manufactured or sold under one or more of the following US patents:

Dispensers

5,257,720

Point of Sale/Back Office Equipment

D335,673

Trademarks

Non-registered trademarks

Atlas™ Consola™ Infinity™

Registered trademarks

ASTRA Fuel Point Gasboy Keytrol Slimline

Additional US and foreign patents pending.

Additional US and foreign trademarks pending.

Other brand or product names shown may be trademarks or registered trademarks of their respective holders.

This document is subject to change without notice. · For information regarding Gasboy Literature, call (336) 547-5661 E-mail: literature@gasboy.com · Internet: http://www.gasboy.com © 2007 GASBOY · All Rights Reserved

1 – Introduction 1

New Features in CFN III . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

How to Use this Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Related Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

How to Use the Configuration Programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

FRAMOS.CFG and FIX_CONF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

ESC Key with NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

How to Exit the Configuration Programs . . . . . . . . . . . . . . . . . . . . . . . . . .6

How to Print Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Checking Typing Mistakes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

2 – System Parameters 7

Page 1: System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Page 2: Club Card Format - Field Widths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Page 3: Club Card Format - Offsets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Page 4: Reader Verification and Miscellany . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Page 5: Console Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Page 6: Gate Verification and Miscellany . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Page 7: Fuel Point Verification and Miscellany . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Page 8: Serial Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Page 9: Miscellany . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Page 10: Tank Gauge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Page 11: Transaction Miscellany. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

Page 12: Receipt Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Page 13: Miles-Per-Gallon Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

3 – Pump Configuration 27

Pump Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Assign Pump to a PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Auto-configure PCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Tokheim Pumps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Items to Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Add Pump Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Chain Pumps - Fleet Package Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

4 – Table Sizes 37

Double Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Changing Table Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

The Memory Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

5 – Local Transaction Printout Format 45

Transaction Field Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page i

6 – Command Permission Levels 51

7 – Island Card Reader Configuration 55

Entering Alpha Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

ICR Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Options for ICR Program Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Displayed Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

ICR Steps. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Receipt Printer Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

ICR Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

8 – Selling Merchandise at the Island - Insight Setup 63

Turning on Merchandise at the Pump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Defining ITEMs and Department Numbers. . . . . . . . . . . . . . . . . . . . . . . 63

Load Product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Reversing a Sale. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Exceeding the Preset Amount. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

9 – Gate Configuration 65

Gate Submenus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Gasboy Gates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Gasboy Gate Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

10 – Unitec Wash Parameters 69

Unitec Wash Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Unitec Wash Discounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

11 – Console Configuration 73

How to Assign Products and Actions to Keys. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Default Key Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

How to Change Action Permission Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

How to Change POS Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Submenus 4 and 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

12 – Offroad 87

How to Set Up the Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Text Editor for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

13 – Fuel Point 89

Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Individual Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Available Hour/Odometer Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

14 – MIXCONF 95

15 – Key Option Configuration 97

Configuring the Site Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Page ii MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

System Parameters (SYS_PAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97

Island Card Reader (READER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .98

PIN Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .99

Appendix A - Configuring Reader Messages 1

Index Index-1

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page iii

This page is intentionally left blank.

Page iv MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

1 – Introduction

This manual explains how to configure a Gasboy® CFN III using the configuration programs

located in the BIN subdirectory on your hard disk.

The configuration programs, in the order they are explained in this manual, are:

• SYS_PAR (system parameters)

•PUMP

•TABLE

• TRFMT (local transaction printout format)

• PERM (permissions)

• READER

•GATE

• CONSOLE

• OFFROAD*

• FUELPT

• Key Option**

Introduction

The name of each of these files ends in the extension. BIN-for example, PUMP.BIN,

TABLE.BIN, and so on.

*OFFROAD.BIN is not used to change the configuration. It is used to calculate an offroad tax

discount for fuel only. You can “configure” the offroad discount by editing the parameter file

(default file name is OFFROAD.DTA). For more information, see the OFFROAD chapter of

this manual.

**Also contained in this manual are the configuration settings for the new Key Option

available from Gasboy.

New Features in CFN III

An on-line configuration manual is available for the CFN III. This can be used as a quick

reference. The on-line documentation is a duplication of this manual. The on-line system

allows you to take advantage of the PC’s ability to display several windows and shifting

between them. The window that is displayed in front (on top of other windows) will be the

“active” window.

“Active” means that it can receive and execute commands. Click in the box at the bottom of

your desktop to display the window you want to view. Or you can use a key sequence of ALT

TAB to shift between windows to review information.

To open the on-line documentation, double click on the SC3 HELP icon. The on-line library

page will open. Click on the Configuration Manual. The table of contents opens listing the

BIN programs available. Click on the BIN program you would like to review.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 1

Introduction

How to Use this Document

The configuration programs for the CFN III are designed to be self-explanatory. This manual does not duplicate all the information given by the programs.

This chapter contains general information about using the configuration programs. You should read it to learn how to use the programs most efficiently. The remaining chapters each contain information about the individual configuration programs and the information needed. Use these chapters as a reference when you need more information than is given by each program's HELP command.

How to Use the Configuration Programs

To use the configuration programs, first ensure that you are logged onto the root directory of your Site Controller . Alth ough the prog rams are located in the BIN subdirectory, do not log on to that subdirectory; remain in the root directory.

At the system prompt (P*), enter the name of one of the configuration programs to see the main menu for that program.

FRAMOS.CFG and FIX_CONF

FRAMOS.CFG contains configuration information for the site and is edited by all the configuration programs (except for OFFROAD.BIN). Site controllers are configured at the factory. A FRAMOS.CFG file will currently exist on the Site Controller. Make a copy of FRAMOS.CFG before changes are made. Use FIX_CONF when updating or in default.

If FRAMOS.CFG does not exist, the site will not boot. To create FRAMOS.CFG, if one does not exist, enter the command FIX_CONF. The screen prompt will say that the FRAMOS.CFG file was not found. Disregard this message.

Press Enter to continue. The default configuration will be used. A new FRAMOS.CFG file will be created.

Page 4 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

Introduction

FIX_CONF-D

You can also use the FIX_CONF command with the -D option to reset configuration

parameters to their default settings. The command looks like this:

FIX_CONF -Dconf_name [-Dconf_name [...]] filename

where conf_name is replaced either with:

• the name of the configuration parameter that is to be reset to defaults-such as READER, PUMP, SYS_PAR* - or

• ALL for all configuration parameters at once. ALL does not default to OFFROAD.

You may specify more than one parameter by repeating the -D option in front of the name of each configuration parameter you want to reset to its default.

Replace filename with the name of your configuration file. If no file name is given, the changes will be made to FRAMOS.CFG. When the site boots, it reads the FRAMOS.CFG file. If you make changes under another file name, they will not take affect unless you copy your file to FRAMOS.CFG.

ESC Key with NT

At this time, ESC only works with a few of the configuration programs. It is recommended that you review the list below to check the functionality. While in configuration programs, the ESC key usually opens the next line/parameter for modification/insertion. Since pressing ESC is similar in effect to pressing CTRL-C, any text entered at the prompt before ESC is pressed is ignored.

These configuration programs have these reactions to pressing ESC:

Pump: Does not work with this program. Table: Next table is opened. Perm: Next command is opened. Reader: ESC signs you off if pressed at the first prompt. Once a menu selection is made, ESC takes

Gate: ESC signs you off if pressed at the first prompt. Once a menu selection is made, the next

Console: Next entity (depending on the menu you are in) is opened for modification. Fuelpt: ESC signs you off if pressed at the first prompt.

you to next parameter.

Gate/Controller is opened for Gasboy only. ESC does not work with Unitec.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 5

Introduction

How to Exit the Configuration Programs

Whenever you are at a place in a configuration program where you are allowed to exit, the prompt will say you can enter q to quit. If you are in a submenu, typing q will get you back to the main menu. From there you can type another q to quit or select a new submenu.

If you type a q from the main menu, the prompt will ask you to type n to exit without saving or y to exit and save any changes.

Any time you are allowed to enter a q to leave a submenu or a main menu, you can enter a capital N to exit the program without saving any changes you may have made, or you can enter a capital Y to exit and save. By entering a capital N or Y, you will skip the prompt asking if you want to save your changes, and if you are in a submenu, you will bypass the main menu and be returned straight to the system prompt.

How to Print Values

Use the -P option to print the present configuration values without changing them. For example: CONSOLE -P prints the console configuration on the screen.

CONSOLE;> filename -P prints the console configuration to the designated file.

Help

The configuration programs have a context-sensitive help facility built in. Anywhere there is a prompt, you can enter a question mark (?) to have the screen display information about what your choices are. If there is no help available for that prompt, you will just see the original display.

Checking Typing Mistakes

If you make a typing mistake and notice it before you press Enter, you can erase the incorrect characters or the whole line.

Press BACKSPACE to erase the character to the left of the cursor. You can erase characters back to the prompt.

T o erase the current line, type a CTRL-U or a CTRL-X. (The h yphen means you are supposed to keep the CTRL key pressed down while you press the second key.)

Page 6 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

2 – System Parameters

The system parameter configuration program, SYS_PAR, has 13 pages that allow you to configure the operation of your Site Controller. The 13 pages are titled:

1 System parameters

2 Club card format - field widths

3 Club card format - offsets

4 Reader verification and miscellany

5 Console verification

6 Gate verification and miscellany

System Parameters

7 Fuel Point verification and miscellany

8 Serial port configuration

9 Miscellany

10 Tank gauge

11 Transaction miscellany

12 Receipt configuration

13 Miles per gallon package

The items on the 13 pages of the menu are discussed below in the order in which they appear on the pages.

Page 1: System Parameters

1 Power up: The Site Controller prints a specified power-up message whenever the AC power

is turned on or the system is rebooted. It can be up to 60 characters long. Enter a message that identifies your company and site.

2 Site ID: A unique number you assign to each of your sites. This number identifies the site

when it is polled by a remote computer . Default is 0, but you should change this if you already have a site using this number.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 7

System Parameters

3 System ID: A unique number assigned to your system by Gasboy. The System ID should be

the same for all of your company's sites. System ID is encoded on each privately issued card to limit the use of the card to the issuer's system and to protect the issuer's system from unauthorized cards. It is not a good idea to change the number assigned by Gasboy.

4 Second system ID: Allows your system to accept cards issued by another system.

5 Network poll address: The drop address of the Site Controller on an on-line CFN network.

The site will answer to this address when polled. The default address is 1, which should be used in all single Site Controller systems. The Gasboy PC communications package, PC Site Control, will work only with sites having a poll address of 1.

6 Manager key permission: Currently not functioning; site is set up with the highest

permission level. Determines what permission level the user will be promoted to while the key on the Site Controller is turned to the manager position.

7 PIN key: Used in the club card PIN calculation. It is always four digits, so leading zeros

should be used if necessary. It is assigned by Gasboy, and should be the same for all your sites that accept a particular club card. Keep this key confidential. When the four digits are entered, the screen will display ****. There is no default for the PIN key.

8 Backup password: Used if no password has been loaded for user 0, or if the backup password

switch is set.

The default backup password is GASBOY. It is recommended that you not change this password. If you do change the backup password, write it down in a safe place where it will never be lost.

9 Lockout: You can choose either bit-mapped lockout or limited lockout.

If you choose bit-mapped lockout, you may specify whether the table is maintained in memory (the usual arrangement) or in a disk file.

For bit-mapped lockout, you must specify the number of digits to use for lockout. Up to eight digits can be used for bit-mapped lockout. The numbers used for lockout are interpreted as numbers with leading zeros assumed.

With memory-based bit-mapped lockout the Site Controller stores 96 card numbers per record. (The first record is used for other information.)

The number of digits in the card number is also a limiting factor. If the card number is four digits, the highest card number that can be used is 9999, if it is five, the highest is 99,999, and if it is six, the highest is 999,999.

If a larger number of cards or longer card numbers are needed than can be provided with bitmapped lockout in memory, you have two choices: bit-mapped lockout on disk (which slows down card verification) or limited lockout.

For limited lockout, the number used for lockout can be up to 19 digits. The numbers used for lockout are stored as strings of digits and leading zeros are not assumed. When club card numbers are entered for lockout, a C must come before the number.

Page 8 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

System Parameters

With limited lockout, the Site Controller stores one account number per record. It is possible to use wildcards in digit positions to lockout more than one card with a single record. For example, if your card format includes subfields for customer number and employee number in the portion of the account number that is subject to lockout, then you can lock out all cards for a particular customer with a single lockout record containing wildcards. (See MDE-4315 CFN III Manager’s Manual for more details.)

When deciding if the space available for limited lockout is adequate to your needs, remember that it is not necessary to be able to lockout every single card you might issue, only the fraction of your outstanding cards that might realistically be locked out at any one time. Good lockout and card recovery policies can greatly reduce the number of accumulated lockouts.

The default is bit mapped, 4 digits, but your choice will depend on your card format, the maximum number of cards you intend to issue, and the maximum number of cards you intend to lock out.

10 Disk journal: Enter a Y or N to store transaction data in P: journal.log. If you are using the

shift reporting package, enter Y.

11 Send generic log messages to disk journal: Enter a Y or N to save all log messages (non-

transaction included) to the disk journal. Messages are of type “Event generic” as described in the disk journal document. Note that this makes the journal larger.

12 Locale code for site: Select the number corresponding to the site locale.

Number Locale Number Locale Number Locale 0 USA 5 Latin 1 10 Phillipines

1 China 6 Latin 2 11 South Africa 2 Ethiopia 1 7 Latin 3 12 Taiwan 3 Ethiopia 2 8 Latin 4 13 Turkey 4 Iceland 9 Latin 5

Hit RETURN when through reading.

Page 2: Club Card Format - Field Widths

13 Digits in system ID: The number of digits in the system ID number . The system ID number is

encoded on every privately issued card or Vehicle Module (VM). The system ID number encoded on the card will be compared with the system ID entered in card to work, the two numbers must match (leading 0s are allowed). Up to six digits are allowed. The default is 6 digits.

item 3 on page 8. For the

14 Digits in account #: The total number of digits in the card information (account) field on

privately issued cards used with the system.

If the card information field is divided into two or three fields (for example, customer number and card number), this is the total of all the card information fields. The default, as well as the maximum, is 19 digits.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 9

System Parameters

15 Digits in allocation: The number of digits in the allocation number part of the club card

16 Digits in vehicle #: The number of digits in the vehicle number part of the club card account

17 Digits in expiration date: The number of digits in the expiration date on privately issued

18 Digits in limitation code: The number of digits in the limitation code on privately issued

account number. The allocation number can have up to four digits, or up to five digits if the first digit is 3 or less (this is because the highest permissible allocation number is 32,766). The default is 2 digits. The number of digits on the card can be greater but only up to 5 are usable.

number. The number can have up to eight digits. Must have a number greater than 0 for the vehicle number to print on the receipt.

If manual-entry vehicle numbers are used, rather than having the vehicle numbers on the card, the number of digits for this parameter should be 0. The default is 4 digits.

cards used with the system. The expiration date is two digits if just the year is used, and four digits if the year and month are used. The default is 4 digits.

cards used with the system. The limitation code can have zero, one, or two digits. The default is 1 digit.

19 Digits in authorization code: The number of digits in the authorization code on privately

issued cards used with the system. The authorization code can have zero, one, or two digits. The default is 2 digits.

20 Digits in price level: The number of digits in the price level code on privately issued cards

used with the system. The price level can have zero, one, or two digits. The default is 1 digit.

21 Digits in restriction code: The number of digits in the restriction code on privately issued

cards used with the system. The restriction code can have zero, one, or two digits.

Depending on the value of the restriction code on the card, the mileage, auxiliary entry number, PIN, dollar amount, or some combination of these must be entered by the card user.

If PIN, auxiliary entry number, or odometer entry are required in the card reader program, they are always required, regardless of the value of the restriction code. Also, if the PIN entry is required for club card transactions in the system parameters, it is always required, regardless of the value of the restriction code. The default is 1 digit.

22 Digits used in PIN calculation: The number of digits in a club card account field, that is used

for the PIN calculation.

For systems that use two cards, these digits should be encoded only on the employee card, so that one employee may drive several vehicles without having to remember several PINs. The default, which is also the maximum, is 19 digits.

23 Digits in checking PIN: The number of digits to be entered by the customer for a checking

transaction PIN. This applies to debit cards only, not privately issued cards. The default is 4 digits; the maximum is 12 digits. Reader programs must be set to allow 12 digits if used. Refer to

“Island Card Reader Configuration” on page 55 for more information.

Page 10 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

24 Digits in savings PIN: The number of digits to be entered by the customer for a savings

transaction PIN. This applies to debit cards only, not privately issued cards. The default is 4 digits; the maximum is 12 digits.

25 Digits in credit PIN: The number of digits to be entered by the customer for a credit

transaction PIN. This applies to credit cards only, not privately issued cards. The default is 4 digits; the maximum is 12 digits.

Page 3: Club Card Format - Offsets

26 Allocation account offset: The offset into the club card account number of the allocation

number. For example, an of fset of 0 points to the first digit of the account number. The default offset is 4.

27 Vehicle account offset: The offset into the club card account number of the vehicle number.

For example, an offset of 0 points to the first digit of the account number. The default offset is

System Parameters

28 Limitation code offset: The offset following the expiration date that points to the first digit of

the limitation code. For example, an offset of 0 points to the first digit after the expiration date. The default offset is 0. If there is no expiration date, first digit after field separator.

29 Authorization code offset: The offset following the expiration date that points to the first

digit of the authorization code. For example, an offset of 0 points to the first digit after the expiration date. The default offset is 1.

30 Price level offset: The offset following the expiration date that points to the first digit of the

price level code. For example, an offset of 0 points to the first digit after the expiration date. The default offset is 3.

31 Restriction code offset: The offset following the expiration date that points to the first digit of

the restriction code. For example, an offset of 0 points to the first digit after the expiration date. The default offset is 4.

32 PIN calculation offset: The offset of the data used for PIN calculation in the account

information field. For example, an offset of 0 points to the first digit of the account information field. You may wish to assign special meanings to subranges of this field, such as customer number and employee number. The default offset is 0.

33 Extra card digit offset: Offset after expiration date for extra digit of card number. This option

was added to meet a specific need of a customer who had run out of card numbers to issue. The extra digit could be added to new cards without af fectin g old card s. The default is 0, which disables this feature.

34 CLUB bit-mapped account offset: In bit-mapped lockout, how far from the beginning of the

account number is the first digit in the club lockout number. The default is 0.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 11

System Parameters

Page 4: Reader Verification and Miscellany

35 Use remote verification (reader): This item specifies which types of cards are verified

remotely for transactions started from the island card reader. If local verification is also specified for a type of card, local verification will be done if remote verification cannot be completed.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 24 specifies checking and credit.

36 Use local verification (reader): This item specifies which types of cards are verified locally

for transactions started from the island card reader. If remote verification is also specified for a type of card, it will be tried first, and local verification will be done if remote cannot be completed.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies private issue (club) cards.

37 Require PIN (reader): This item specifies which types of cards require the customer to enter

a PIN for transactions started at the island card reader. This specification is in addition to restrictions encoded on the card. PINs should always be required for debit cards (savings and checking) if these cards are accepted at the site.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 123 specifies private- issue (club), checking, and savings cards.

38 Check PIN (reader): This item specifies which types of cards require the Site Controller to

check the PIN for transactions started at the island card reader. The Site Controller can check only privately issued card PINs, not PINs assigned by banks (which are checked remotely by the bank network). There are special occasions where bank PINs can be used. These numbers must be entered into a record that is checked by the Site Controller. However, you may assign privately issued PINs to credit cards for your own customers if you wish to limit credit card use to approved customers only. If using Record Lookup, the PIN is compared to the PIN loaded in the record.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

39 Check mod 10 (reader): This item specifies which types of cards require the Site Controller

to check the mod 10 check digit for transactions started at the island card reader. The mod 10 check digit is a special digit that is encoded on some types of cards and that

contains partial information about certain other digits on the card, usually the account number. Comparing the encoded check digit with the result of repeating the calculation at the site will detect most alterations or errors on the card.

If the Site Controller checks mod 10 for a card that doesn't have a mod 10 check digit, the card will be denied authorization. For cards that do have mod 10 check digits, you can decide not to check mod 10 if, for example, you wish to accept cards that were encoded with incorrect check digits.

Page 12 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

System Parameters

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit cards.

40 Check expiration date (reader): This item specifies which types of cards require the Site

Controller to check the expiration date when transactions are started from the island card reader. The expiration date on the card is compared to the current date (or to an alternate expiration date if one has been set by system parameter

item 137 on page 24, Transaction

Miscellany,) and the card is rejected if it has expired.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1234 specifies privately issued (club), checking, savings, and credit cards.

41 Lockout on local verification (reader): This item specifies which types of cards require the

Site Controller to check lockout on local verification for transactions started from the island card reader.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 14 specifies privately issued (club) and credit cards.

42 Lockout on remote verification (reader): This item specifies which types of cards require

the Site Controller to check lockout on remote verification for transactions started from the island card reader.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit.

43 Reader default payment: This item specifies which type of account should be used as the

default payment type if the “Which account step” is not in the island card reader program.

Account types are: 1 = checking, 2 = savings, 3 = credit.

44 Show product price on reader display: For which types of transactions should prices of

products purchased be shown to the customer on the island card reader display. Some sites may not wish to display prices for privately issued card transactions.

Types of transactions are : 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

45 Pump must be on hook for reader transaction: A hose can be required to be on-hook to be

activated from an island card reader.

46 Auto receipt: When re-entering card, ICR prints without asking: Are receipts printed

automatically on the island card reader when the customer swipes the card again after pumping? The default is no.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 13

System Parameters

47 Auto receipt: duplicate receipts printed: Will another receipt be printed if the card is swiped

48 Reader types that print receipt without asking after sale: Specifies what reader types will

49 Reader ignores PIN restriction on card: Specifies that a PIN is not needed even if the

50 Keypads: Holds 2 separate keypad layouts. The user may pick any 2 from the following

a second time after pumping. The default is no, which lessens the chance of the printer jamming on unclaimed receipts.

always automatically print a receipt when sale is completed. (0=None,1=CRIND,2=ICR,3=ALL). For all transactions on pumps with no internal reader, the receipt will automatically be printed on the lowest numbered ICR assigned to the same cluster as the pump.

restriction code requires a PIN provided that Check PIN is not set.

• CRIND

•WCAT

• CRIND/WCAT (like old setting when keypad length was 20)

• DPT (like old setting when keypad length was 24)

The keypads are loaded 1 at a time. The customer is first asked to select which keypad to load, and then is asked to load the keypad string for that reader type. He can then select the keypad again and enter the keypad layout for another type. The last 2 different types entered are saved.

The program only sends the keypad to the type of device specified.

51 Require clerk approval for reader transactions: Some fire marshals require that a clerk

approve all reader transactions before fuel can be pumped; this is a safety mea sure to prevent customers from dealing with materials like propane themselves. The default is no.

52 Reader requires attendant card for transactions (Y/N/cluster #): Y = all clusters, N =

none, 0 - 9 applies only to the specified cluster. The Attendant number from card becomes the clerk number for tracking.

If set to yes, a transaction from the reader will require an Attendant card to be swiped following any payment card. If swiped without a payment card, the access card will be treated as a Club and will not require an additional card swipe. This allows attendants to charge customer’s cash sales to their attendant account.

53 Reader requires Patr on/Loyalty card for transactions: Enter 0 = No, 1 = Before, 2 = After ,

3 = Maybe. Patron is not required, but if swiped before payment, it is assigned to the transaction and payment is prompted for. The default is no.

Page 14 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

Page 5: Console Verification

Console in this section refers to Profit Point and/or Check Point.

54 Use remote verification (console): Which cards are verified remotely for transactions started

from the console. If local verification is also specified for a type of card, local verification will be done if remote verification fails.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit.

55 Use local verification (console): Which types of cards are verified locally for transactions

started from the console. If remote verification is also specified for a type of card, it will be tried first, and local verification will be done if remote cannot be completed.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 14 specifies privately issued (club) and credit.

56 Require PIN (console): This item specifies which types of cards require the customer to enter

a PIN for transactions started at the console.

System Parameters

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 23 specifies checking and savings.

57 Check PIN (console): For which types of cards does the Site Controller check the PIN for

transactions started at the console. The Site Controller can check only PINs assigned for the system, not bank PINs. (There are special occasions where bank PINs can be used. These numbers must be entered into a lookup record that is checked by the Site Controller.)

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

58 Check mod 10 (console): For which types of cards does the Site Controller check for the mod

10 check digit on the card for transactions started at the console. If the Site Controller checks mod 10 for a card that doesn't have a mod 10 check digit, the card will be denied authorization.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit.

59 Check expiration date (console): For which types of cards does the Site Controller check the

expiration date when transactions are started from the console. The expiration date on the card is compared to the current date (or an alternate expiration date if one is set in system parameter Alternate Expiration Date, below), and the card is rejected if it has expired.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 14 specifies privately issued (club) and credit.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 15

System Parameters

60 Lockout on local verification (console): For which types of cards does the Site Controller

61 Lockout on remote verification (console): For which types of cards does the Site Controller

62 Where to send all Profit Point broadcast messages: Sending all Profit Point messages is

63 Console requires attendant card for transactions: If set to yes, a transaction from the

check lockout when doing local verification for transactions started from the console.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 14 specifies privately issued (club) and credit.

check lockout when doing remote verification for transactions started from the console.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit.

useful in video monitoring. The default is no.

console will require an Attendant card to be swiped following any payment card. If swiped without a payment card, the access card will be treated as a Club and will not require an additional card swipe. This allows attendants to charge customer’s cash sales to their attendant account.

64 Console requires Patron/Loyalty card for transactions: Enter 0 = No, 1 = Before, 2 =

After, 3 = Maybe. Patron is not required, but if swiped before payment, it is assigned to the transaction and payment is prompted for. Default is 0.

Page 6: Gate Verification and Miscellany

65 Use remote verification (gate): Which types of cards are verified remotely for transactions

started from the gate controller. If local verification is also specified for a type of card, local verification will be done if remote verification fails.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

66 Use local verification (gate): Which types of cards are verified locally for transactions started

from the gate controller. If remote verification is also specified for a type of card, it will be tried first, and local verification will be done if remote fails.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

67 Require PIN (gate): For which types of cards must the customer enter a PIN for transactions

started at the gate controller.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

Page 16 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

System Parameters

68 Check PIN (gate): For which types of cards does the Site Controller check the PIN for

transactions started at the gate controller. The S ite Controller can only check PINs assigned for the system, not bank PINs. Bank PINs can be used only if entered into the lookup table. Refer to MDE-4315 CFN III Manager's Manual for more information.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

69 Check mod 10 (gate): For which types of cards does the Site Controller check the mod 10

check digit for transactions started at the gate controller. If the Site Controller checks mod 10 for a card that doesn't have a mod 10 check digit, the card will be denied authorization.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

70 Check expiration date (gate): For which types of cards does the Site Controller check the

expiration date for transactions started from the gate reader. Expiration date is compared to current date (or alternate date if one is set in system parameter Alternate Expiration Date, below).

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

71 Lockout on local verification (gate): For which types of cards does the Site Controller check

lockout when doing local verification for transactions started from the gate controller.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

72 Lockout on remote verification (gate): For which types of cards does the Site Controller

check lockout when doing remote verification for transactions started from the gate controller.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 1 specifies privately issued (club) cards.

73 Log gate openings: Should the Site Controller print a message on the log printer each time the

gate opens?

74 All gate openings make transaction: Should the Site Controller treat each gate opening as a

transaction?

75 Select gate message: Enter message to be displayed when a customer is selecting a gate at the

reader.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 17

System Parameters

Page 7: Fuel Point Verification and Miscellany

76 Use remote verification (Fuel Point): Identifies which types of cards are verified remotely

for transactions started from a Fuel Point. Cards are not actually read at/by the Fuel Point. Data that is read is put into card formats. If local verification is also specified for a type of card, local verification will be done if remote verification fails.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit.

77 Use local verification (Fuel Point): Identifies which types of cards are verified locally for

transactions started from a Fuel Point. If remote verification is also specified for a type of card, it will be tried first, and local verification will be done if remote fails.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 14 specifies privately issued (club) and credit.

78 Require PIN (Fuel Point): Identifies which cards should require PIN (Fuel Point) entry.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 12 specifies privately issued (club) and checking.

79 Check PIN (Fuel Point): Identifies which cards should check the PIN (Fuel Point) entry.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 12 specifies privately issued (club) and checking.

80 Check mod 10 (Fuel Point): Identifies types of cards for which the Site Controller checks the

mod 10 check digit for transactions started at a Fuel Point. If the Site Controller checks mod 10 for a card that does not have a mod 10 check digit, the card will be denied authorization.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit.

81 Check expiration date (Fuel Point): For which types of cards does the Site Controller check

the expiration date for transactions started from a Fuel Point. The expiration date is compared to current date (or alternative date if one is set in SYS_PAR Alternate Expiration Date, below).

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 14 specifies privately issued (club) cards and credit.

Page 18 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

82 Lockout on local verification (Fuel Point): For which types of cards does the Site Controller

check lockout when doing local verification for transactions started from a Fuel Point.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 14 specifies privately issued (club) and credit cards.

83 Lockout on remote verification (Fuel Point): For which types of cards does the Site

Controller check lockout on remote verification for transactions started from a Fuel Point.

Types of cards are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 234 specifies checking, savings, and credit.

84 Require sys-ID match for track-II vehicle module: Require sys-ID match for track-II

vehicle module. If yes, the Vehicle module must have correct system-ID for track-II card.

Page 8: Serial Port Configuration

System Parameters

85 Remote Port channel: The channel used for remote modem. If the Remote Port is not set to

zero for "None", ensure that the Remote Port Channel number does not conflict with the Log Printer Channel or Host Handler Channel; else, a system lockup may occur.

86 Log printer channel: The channel used with the log printer. Ensure that the Log Printer

Channel number does not conflict with the Remote Port Channel or Host Handler Channel. If you assign the same (non-zero) number to multiple channels, a system lockup may occur.

87 Special pump handler channel: The number of the serial port used for a non-Gasboy, non-

Tokheim

, non-Gilbarco pump interface-for example, a Unidynamics or Wayne interface. Enter 4 if no special pump handler is used. If the Host Handler Channel is not set to zero for "None", ensure that the Host Handler Channel number does not conflict with the Log Printer Channel or Remote Port Channel; else, a system lockup may occur.

88 Remote port baud rate: The default baud rate is 9600.

89 Remote port terminal type: The default terminal type is VT52.

90 Remote port modem type: This is the type of modem that is used by the remote port:

0 = dumb modem (half-duplex) 1 = Hayes 2 = Hayes handshake 3 = direct or dumb modem (full-duplex)

91 Additional Hayes remote port command(s): Use to add commands to the default modem

instructions.

92 Pumps on first Tokheim channel: If you have Tokheim pumps, this parameter lets you

designate how many pumps are on channel 1. This designation lets you split the number of pumps evenly between channels 1 and 2, thereby increasing processing speed.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 19

System Parameters

93 Poll split Tokheim loops fast: The default is NO which uses less CPU time. Default polling is

94 Host handler channel: This is the host verification channel. Default is 0 (none).

95 Host handler baud rate: The baud rate used by the host handler. The baud rate is ignored for

96 Verification time-out (routers): The time (in seconds) that the Site Controller waits for

97 Verification time-out (CFN Host): The time (in seconds) that the Site Controller waits for

98 Host router data: Data the router uses to identify the site. The data to be entered depends on

99 More router data: More data used by the router. The data to be entered depends on the router

30 polls per second. Fast is 50 polls per second.

synchronous protocols.

verification from the host. The default verification time-out of 75 seconds is usually reasonable. Default is 75 seconds.

verification from the CFN host. Default is 0 seconds.

the router used. Check the specific router manual for more information.

used. Check the specific router manual for more information.

100 Send requests to host handler: For which types of cards should authorization requests be

sent to the host handler.

Types of cards are:

1 = club 2 = checking 3 = savings 4 = credit 0 = none.

Enter selected types as a string with no spaces; for example: 24 specifies checking and credit.

101 Host handler data: Enter the data for handler configuration. The data to use depends on

which handler is being used. The program will ask for handler data #1, handler data #2, and so on through all 16 entries. Enter each separately . For more details on handler data, see your specific Credit and Debit manual.

Page 20 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

Page 9: Miscellany

102 Null pad CR/LF: The number of null characters to pad after a carriage return/ linefeed. This

is used for log printers and data terminals that do not have buffers in order to briefly hold input during the time it takes the carriage to return to the beginning of the line.

103 Switch time-out: The number of seconds the pump control unit waits after a pump has been

activated for the hose switch to be activated. If the time-out is reached, the transaction is halted. The default value (80 seconds) is usually adequate.

104 Pulser time-out: The number of seconds the pump control unit waits for the next pulse after

fueling has started. If the time-out is reached, the transaction is halted. The default value (80 seconds) is usually adequate.

105 Fall-back price level: The price level that will display on dispensers when they are idle. Price

from previous sale will be replaced by fall-back price for that product a certain number of seconds after the sale is completed. This is also the level that the Site Controller will use when it cannot determine the method-of- payment of a transaction.

System Parameters

(For Gilbarco MPD dispensers, it is recommended that level 0 be your fall- back price level and that it be equal to your credit price, which should be price level 2.)

106 STOP pumps on RS-422 break: This item specifies whether any pumping transactions

should stop when a break occurs on an RS-422 loop.

107 Blank pump display after: The number of seconds the Site Controller waits after a sale is

paid before replacing the quantity sold and sale amount displays on a dispenser with zeros and displaying the fall-back price (the fall-back price level is set by system parameter Fall-back Price Level, above). The default is 600 seconds (10 minutes).

108 Blank pump price display: For T okheim pumps only, should the price display be blanked out

during pumping for club cards only. The default is no.

109 Command search path: Specifies which directories and drives-and in what order-the Site

Controller will search for programs.

110 Zero quantity disable after: The number of consecutive zero-quantity transactions that can

occur on a pump before the Site Controller disables it. This feature is intended to disable a pump in the event of total failure of the flow- sensing pulser. The default value (5 no-quantity transactions) is usually adequate.

111 Reuse current sale on POS if previous unpaid: Should a new transaction on a POS be

allowed to overwrite the current paid transaction if the previous transaction is still unpaid? Default is yes.

If you select no, you will not be able to start a new transaction until the previous transaction is paid off. If you select yes, you will be able to start the pump whenever either the current or previous transaction is paid off: however, occasionally a manual receipt may be unavailable because another transaction (say, started from a island card reader) overwrote the current transaction before the print-receipt button was pressed.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 21

System Parameters

112 Log remote port commands executed: Should commands sent to the Site Controller from

113 Unique shift #'s for every console: Allows the disk journal to track console shifts separately.

114 Hours r equir ed between NEXT SHIFT/DAY: How many hours from a NEXT SHIFT/DAY

115 Initial drawer value after NEXT SHIFT/DAY: The amount of cash in the drawer that each

116 Buffered cumulative totalizers on RESET TOTALS: Preserves the cumulative totals at the

117 Blank lines for page break: Number of blank lines to leave between pages on the log printer.

the remote port (for example, by a remote computer or terminal dialing in) be recorded on the log printer? Default is no.

Default is no.

command must pass before a subsequent NEXT SHIFT/DAY command will be carried out. Default is 0.

shift or day will start with. The default is $300.

point where the RESET TOTALS command is run. This allows you to figure out the totals (based on cumulative totalizers) for last shift/day without having to shut down the site. The default is no.

This allows you to skip perforations when using tractor-feed perforated paper in a dedicated log printer. Default is 0. The range is 0-10.

118 Lines of text per page on direct printout: Lines of text per page on the log printer . Default is

66 lines (11 inches times 6 lines per inch); the range is 11-127 lines.

119 Logger initialization: This is how you send an initialization string to your log printer, if

required by the printer you are using.

120 Pre 4.1 SCI compatibility for odometer and manual #: Maintain compatibility with the

pre-version 4.1 Site Controller I for odometer and manually-entered veh i cle number. Earlier systems inserted zeros when no number was entered by the customer; the current system uses spaces (blanks). Default is no (uses spaces).

Page 10: Tank Gauge

121 Log gauge delivery: Should deliveries detected by the tank gauge be recorded on the log

printer? The default is yes.

122 Transaction for gauge delivery: Should deliveries detected by the tank gauge generate

transactions? The default is no.

123 Add to tank inventory after gauge delivery: Should the amounts of deliveries detected by

the tank gauge be added to the tank inventory totals? The default is no.

124 Log fuel drop card: When the driver of a tanker uses his card to record a fuel drop at your

site, should this drop be added to the log, where it cannot be polled by a remote site? The default is no.

Page 22 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

125 Transaction for fuel drop card: When the driver of a tanker uses his card to record a fuel

drop at your site, should this drop be entered as a transaction, which can be polled from a remote site? The default is no.

126 Add to tank inventory after fuel drop card: When the driver of a tanker uses his card to

record a fuel drop at your site, should this drop automatically be added to tank inventory? The default is no.

127 Log dipstick reading: Should dipstick readings be added to the log, where they cannot be

polled by a remote site? The default is no.

128 T ransaction for dipstick reading: Sh ould dipstick readings be entered as transactions, where

they can be polled by a remote site? The default is no.

Page 11: Transaction Miscellany

129 Bank PIN D.E.S.: Should bank card transactions be Data Encryption Standard (D.E.S.)

encrypted?

System Parameters

130 CFN PIN unencrypted: Specifies that a PIN not be encrypted when it is sent to the CFN host.

This is for CFN hosts that cannot decrypt PINs.

131 Cumulative limit time: Over how long a period should the Site Controller keep track of the

cumulative fuel amount.

For example, if the time limit is 24 hours, the Site Controller keeps track of the amount of fuel accessed by a card within any 24-hour period. A customer cannot access more than the amount of fuel defined by the cumulative fuel limit in the 24-hour period.

Specify a time limit of 0 if there is no limit. The default is 0.

132 Cumulative fuel limit: What is the maximum amount of fuel a customer can have access to in

the cumulative limit time period? The amount can be in dollars or gallons.

133 Save cash transactions: Should the Site Controller save records for cash transactions in the

main transaction file?

134 Save HAND transactions: If you have configured the console to allow manually authorized

card transactions, should the Site Controller save the records of these transactions?

135 Allow supervisor cards: Should this site accept supervisor cards? The default is no.

136 Allow cardless use of code file: Should this site have code file codes that are entered

manually, not with a card? The default is no.

MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007 Page 23

System Parameters

137 Alternate expiration date: Allows a grace period for expired cards if a non-zero value is

138 Number to add to club price level: Allows club cards to use a different price level than the

139 T ransaction file full warning per centage: Determines how full the main transaction file may

140 Fuel authorization code for bank cards: Which types of fuel can be purchased by bank

141 Check fuel authorization codes on postpay: Should a postpay transaction be disallowed

142 Always request dollars from CFN host: Always request transaction authorization in dollars

entered. First value is the month; second value is the year. If either va lue is not zero, all cards will be compared with this month and year, rather than the month and year on the system clock, to determine whether each card has expired.

level encoded on the cards.

become before a warning message is logged. Enter as percentage full.

cards? Only one code can be entered; select one of the authorization numbers set up with the LOAD AUTHORIZATION command. Default is none.

because the customer pumped a product that was not one of the products permitted by the authorization code encoded on his card?

from the remote host for the specified type of transactions.

Types are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 0 = none. Enter selected types as a string with no spaces; for example: 24 specifies checking and credit.

143 Send transactions to CFN host: Which types of transactions should be sent to the CFN host?

T ypes are: 1 = club, 2 = checking, 3 = savings, 4 = credit, 5 = cash, 6 = unpaid, 0 = non e. Enter selected types as a string with no spaces; for example: 124 specifies club, checking, and credit.

144 Generate card swipe event: Should the system generate an event on every card swipe (Y/N)?

Page 12: Receipt Configuration

The receipt format determines the information that will appear in the core of a printed receipt. The receipt header and footer are entered with the Site Controller command LOAD HEADING. The date and time of the transaction and the site number, transaction number, authorization number, customer account number, pump number, and type of fuel pumped appear on receipts unless a format from the bank overrides the standard format.

145 System volume units: Units the system uses for fuel volume.

G = gallons; L = liters. Default is gallons.

146 Minutes until ICR expires (1440): This is the maximum amount of time, in minutes, that a

receipt may be printed for a transaction.The range is from 20 minutes to 24 hours. The other constraint of receipts not being available after 100 transactions are stored in the transaction file still pertains.

Page 24 MDE-4316C CFN Series CFN III Configuration Manual for Windows NT® · April 2007

+ 90 hidden pages

Gasboy CFN III Config Mnl User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Table of Contents

New Features in CFN III

How to Use this Document

Related Documentation

CFN III - Version 3.4 and Above

Forms, Quick Reference, Tutorials

Credit and Debit Card Networks

Pump Interface

Card Encoding and Miscellaneous

Remote Communications

Technical Publications

How to Use the Configuration Programs

FRAMOS.CFG and FIX_CONF

FIX_CONF-D

ESC Key with NT

How to Exit the Configuration Programs

How to Print Values

Help

Checking Typing Mistakes

Page 1: System Parameters

Page 2: Club Card Format - Field Widths

Page 3: Club Card Format - Offsets

Page 4: Reader Verification and Miscellany

Page 5: Console Verification

Page 6: Gate Verification and Miscellany

Page 7: Fuel Point Verification and Miscellany

Page 8: Serial Port Configuration

Page 9: Miscellany

Page 10: Tank Gauge

Page 11: Transaction Miscellany

Page 12: Receipt Configuration