MegaTrak MCU-9000 Setup

Transcription

1 MegaTrak MCU-9000 Setup Guide Micro Control Unit Setup Guide with Example Screens, Menus and Commands Models MCU-9000 and MCU9000R200 The MCU-9000 is a Green Product of MegaTronics International Corporation San Antonio, Texas, USA Revision January 22, 2011 Patented and/or Patents Applied For Copyright 2010 by Megatronics International Corporation On the web at Customer SharePoint Site at (mega, M9000!) MegaTrak is a registered trademark All Rights Reserved Connex, ConnexLink and Connex 4790 are trademarks of Aerocomm/Laird Technology

2 M e g a t r a k M C U S e t u p G u i d e P a g e 2 Table of Contents Using the MCU Setup Key... 5 Restore Factory Defaults... 5 System ID... 6 Enter System ID... 6 Default Language... 7 Site Number... 7 MCU is a Gate?... 7 Fall-Back Level... 7 Pump Daily Schedule... 8 MCU Timeout... 9 Meter Override... 9 Stop At Amount?... 9 Ask If Highway?... 9 Keyless Fueling Visitor Vehicle Mode Card Is Type Facility Codes Card Meter Allow Datakeys Veh Credential Offline Limit Communications Method/Medium TCP/IP Networking Configuration DHCP Mode MCU Network Settings Server Network Settings MHz Radio Configuration Radio Channel Selection Radio Server MAC Address Radio Signal Strength Testing... 17

3 M e g a t r a k M C U S e t u p G u i d e P a g e 3 Server Side Radio Configuration Hard-Wired Configuration Hard-Wired to External Radio Telephone Modem Configuration MTiButton Mode Setting-Up Pumps Primary Pump Number Pump to Set-Up Fuel Type Pulser Resolution Pulser Calibration Pulser De-Bounce MCU Door Switch Hook Switch Set-up Off-Hook-To-Fuel Mode Anti-Spill Mode Flow and Hook Timers Re-Pump Mode Ending the Setup Mode Settings Transfer Keys Making a Settings Key Injecting Settings from a Settings Key Fall-Back Levels Meter Check Codes MCU-9000 with HID Proximity Cards Key Types with Read-Only Cards MCU-9000 Behavior with Cards Appendix A: MTiButton EB Mode General About MTiButtons in EB Mode Set-up for EB Mode... 36

4 M e g a t r a k M C U S e t u p G u i d e P a g e 4 INDEX... 37

5 M e g a t r a k M C U S e t u p G u i d e P a g e 5 Using the MCU Setup Key The MCU-9000 setup key is used to alter the settings and configuration of the MCU. A SETUP key for any system can be made using the Megatrak Pro system software. The SETUP key requires that a special password be used to gain access. Without the password, the setup menus cannot be accessed. (The default factory password is SPACEAGE ) Setup Key PASSWORD: ******** Enter the secret password for your system (using the RED and BLUE keys if you need to make letters of the alphabet). The password characters will not be displayed for privacy. Press ENTER when the password has been keyed in. When the correct password has been provided, the MCU enters the Setup Mode and begins to ask series of questions in order to configure the operating parameters ofmcu As you move through the SETUP screens, note that you can use S1 + ESC and then ENTER to move backwards through most selections, and the letter X and then ENTER to quickly exit the setup process. Also, using the DELETE key followed by ENTER will in most cases cause any changes to be erased and the current value of the entry to be restored. If the door is opened or the Datakey is removed, the setup mode will be abandoned and any changes that were made will be lost. Restore Factory Defaults If the correct password is keyed-in, the SETUP system first asks if you want to reset the MCU to the factory-default settings. To answer NO to this request, simply press ENTER. Answer Y (Yes) to this ONLY if you want ALL the settings in the MCU to be discarded and returned to the like-new values. This is a good way to begin when an MCU has been used elsewhere before, or when possible bad settings have been entered and the MCU needs to be returned to a known state. If you respond with a Y to this question, the system will ask if you are sure. Answer Y again to restore the MCU to the factory settings, or press ENTER or N and Enter to proceed. Restore Defaults ARE YOU SURE? N N

6 M e g a t r a k M C U S e t u p G u i d e P a g e 6 There is a secret (hidden) option available at the Restore Defaults prompt. If the user enters exactly P then the system will delete (purge) all the transactions is has stored in Flash memory. This SHOULD ALMOST NEVER BE DONE because vital transaction data may be lost. However, the P (purge) function could be used to clear an old MCU for use in a new assignment, or to clear-up a corrupted transaction issue. System ID When a valid SETUP key and password have been provided, the MCU will take the system ID in the setup key and make that the MCU system ID, and it will also read the password from the SETUP key and make that the new MCU setup password. It will briefly display the new or current system ID at this point. System ID: Note: The new system ID and setup password will not be stored until the setup process is exited properly. If setup is abandoned by removing the setup key or opening the door, these new settings will be lost and the original settings will be reinstated when the MCU is next restarted. Enter System ID If the SETUP key is a Universal type, the MCU will not display the System ID but will ask for the user to enter the desired System ID. It will default to the current System ID setting of the MCU-9000, so just press enter to keep the same system ID and move on. At this step, the user may enter any System ID number they wish to assign to the MCU. Note: A Universal SETUP Key is one in which the System ID has been programmed to Do not use this key in an MCU-3000 or the System ID will be set to Enter Date: The MCU will now ask for information with which to set its internal clock and calendar. Press ENTER to skip these steps. Note that on-line MCUs obtain this information at regular intervals from the server, so entering the information here is not important unless the MCU will be operating off-line. However, any transactions performed before the MCU goes on-line and the clock and calendar get properly set could have an incorrect timestamp, so always set the time and date if you are not sure. (MMDDYY) Enter Time: (HHMMSS)

7 M e g a t r a k M C U S e t u p G u i d e P a g e 7 Default Language The MCU-9000 is capable of operating using a variety of menu languages. The next question asks which language should be used by the MCU as its default, or stand-by language. When a user s key requests a different Default Language language, the MCU will change at once for that user and then revert back to this default language setting when the fueling session is over. (E,S,?) E Note that the language selections may vary, and the language list will grow as translations are made. Site Number Next, the MCU will ask what fueling Site it will be a member of. The site identifier is a number, and must match exactly the other MCUs at the same site and the database site identifier. Enter Site ID: MCU is a Gate? (NNNNN) 1 If this MCU is operating a gate, answer Y to this question. The MCU will inquire as to the gate status at regular intervals, and the control output will be a pulse rather than constant state as required to operate an electric gate control system. MCU is a Gate? N Fall-Back Level The Fall Back Level determines how the MCU will handle things when communication failures occur. The fall back levels are defined as follows: Fall Back Level: 1) Even if communications are non-functional, any valid Datakey will allow the user to fuel. 2) A valid Datakey and working MCU-9000 will allow (1-4) 3 the user to fuel, even if the communications are not functional. Fueling schedules and limits known to the MCU will be in play. 3) This mode allows fueling only if a connection to the first-tier (i.e. local) computer is possible, even if the master database cannot be reached.

8 M e g a t r a k M C U S e t u p G u i d e P a g e 8 4) This mode does not allow fueling unless all the system communications are working and the proper authorization can be handed down through the system from the central server. Note: If there is no local site computer, then Fall Back Level 3 is essentially the same as Level 4. Pump Daily Schedule Next the MCU will ask for the hours during which it should allow fueling. Use 00 and 24 for 24-hour operation. This time schedule applies to all the pumps being controlled by this MCU. Note that the default values of 00 and 24 are used to enable the pump at all times (24/7). Pump On Hr (NN) 00 Pump OffHr (NN) 24

9 M e g a t r a k M C U S e t u p G u i d e P a g e 9 MCU Timeout The MCU-9000, unlike previous model MCUs, has the ability to operate multiple pumps or hoses in the same fueling session through the use of expander modules. In order to do this, the MCU must turn all the pumps or hoses on and then allow each one to manage its own fueling session. During this time, the MCU-9000 monitors the status of the individual pumps or hoses, but the MCU cannot know when fueling has completed on all the pumps or hoses. The MCU will shut-down all the pumps or hoses if a preset amount Timeout (secs): of time has elapsed and no pumping action has been (NNN) 180 reported by any of them. This is where you set that time limit. (Entering zero will prevent any time out from occurring.) Meter Override The MCU9000 will next ask if the meter request (odometer or hour meter) should be omitted. When the MCU is used No Meter? for gate control or other special functions, it may not be applicable for a meter value to be collected even though the key is programmed to ask for a meter value at fueling locations. Setting this override value to a Y will cause the MCU9000 to NOT ask the driver for an odometer reading, and to not update the Datakey stored meter value. N Stop At Amount? When using the MCU-9000 to control some fluids, it might be desirable to let the operator key-in an amount at which the fluid should be stopped. Answer Y here if you want the driver to be asked when the fluid Stop At Amount? should stop. N Ask If Highway? Answer Y if the driver should be asked if the fuel is to be used for highway (public road use) or track (private road use). This will affect a marker in the fuel transaction that can be used to determine the fuel use for Ask if Highway? tax or accounting reasons. N

10 M e g a t r a k M C U S e t u p G u i d e P a g e 10 Keyless Fueling If you wish to allow users to press the F1 key to initiate a keyless fueling session, answer yes ( Y ) to this question. Otherwise, answer N and keyless fueling will not be allowed. Keyless mode asks the driver to enter his own ID and the vehicle ID, and does not require a physical Datakey or other key device. Keyless Fueling? Y Keyless Meter? (N,M,H),H) N When keyless fueling is used, the MCU can be programmed to ask for the number of miles (M), the number of hours (H), or no meter at all (N) from the driver. Keyless PIN? Keyless fueling has the disadvantage of being far less secure than fueling using a physical key. To add some degree of security, a PIN number can be added for keyless (NNNN) NNNN fueling to restore at least a little security to the system. Enter four spaces to disable the Keyless Fueling PIN number. Visitor Vehicle Mode The MCU-9000 may be programmed to accept unknown Vehicle (Equipment) IDs and other information in order to allow visiting (out-of-network) vehicles to be fueled. This means that a vehicle ID can be entered that is Visitor Mode? unknown to the system, and a valid operator may fuel it. To allow this mode of operation, answer Y (Yes) to the Visitor Mode setting. N If Visitor Mode is enabled, then the MCU will ask if the visitor vehicle department should be required. Next, the MCU will ask if the visitor vehicle reason code should be required. This code can be used to convey information about why the vehicle is fueling out-ofnetwork. Ask for Dept? N Ask for Reason? N

11 M e g a t r a k M C U S e t u p G u i d e P a g e 11 Card Is Type The MCU-9000 can accept Wiegand signals from proximity or other card or electronic token readers. Because these cards or tokens are read only and contain only a serial number, the MCU cannot determine the type of key that the card or token represents (Driver or Equipment). Instead, the MCU can be set to assume that a card presented is one of these types and treat is as such. The answers to this Card is Type? question can be: N for None (no card will be accepted) E for Equipment (card represents vehicle or equipment ID) A for Administrator (card is assumed to be administrator ID) S for Special Person (card is assumed to be Special Person ID) D for Driver (card is assumed to be driver ID) F for Card Type per Facility Code (N,E,A,S,D,F),F) D If the answer to the Card Is Type question is D or E, then the MCU-900 next asks what the Facility Code on the cards will be. Entering zero (0) will cause the MCU to allow any and all card facility codes to be accepted. Facility Code? (NNN) 0 If the answer is F then the card s facility code will be used to determine how the card is processed. Facility Codes If the Card Is Type answer is F above, then the MCU-9000 needs to know the Facility Codes that will specify the Key Types that the cards represent. Enter the facility code that will represent each key Type. Where Driver Fac Code? zero is entered, no cards will represent that card type. Card Meter (NNN) Equip Fac Code? 0 (NNN) Specl Fac Code? 0 Admin Fac Code? (NNN) 0 (NNN) 0 When a Card or other read-only key token is used, the MCU-9000 needs to know if it should ask the driver for a meter (Odometer or Hour meter) reading or not, and which type of meter is used. Answer N if no meter should be collected, M for miles, H for hours or K for kilometers. Card Meter? (N/M/H/K) N

12 M e g a t r a k M C U S e t u p G u i d e P a g e 12 Allow Datakeys When using cards or other electronic key tokens, Datakeys may also be used to begin a fueling session. If the MCU should not accept a Datakey to begin a fueling session, enter a N here. (If a card is used to begin a fueling Allow Datakeys? session, and the source of the Vehicle ID has been selected as a Datakey, the Datakey will still function in that role even if it is disabled here.) Y Veh Credential This setting determines how the MCU-9000 will accept vehicle identification after a Driver type card is presented. The MCU-9000 can use a Datakey ( K ), a second card or token ( C ), or a key pad ( P ) entry for the Veh Credential? vehicle ID credential. (P,K,C) See the Appendix for more details on Cards, Key Types and Facility Codes. The EB Mode uses the card mechanism for MTiButtons. See Appndix A for more information about setting-up and using the EB Mode and MTiButtons. K Offline Limit When the MCU-9000 goes into offline mode and fueling is allowed, the use of cards or Keyless operation offers no dispenser fuel limit to control how much fuel is dispensed in any one fueling session. The MCU-9000 can OffLine Limit? be set to assume a limit in gallons for these situations. (NNNN) N

13 M e g a t r a k M C U S e t u p G u i d e P a g e 13 Communications Method/Medium The next screen is used to tell the MCU how it will communicate with the server. Unlike older MCU models, the MCU-9000 can communicate using hardwired methods (W), radio (R), network (N), telephone Communications? (dial-up) modem (M)or on any of a variety of bridges to a standard TCP/IP network. The MCU may also be set to the (W/R/N/M/S) N Stand-Alone (S) mode if it uses NO communications and operates stand-alone. The mode selected here will alter the next few screens, as they will ask the questions required to configure the communications method that has been selected. If you select the S option, which means that the MCU-9000 is working stand-alone with no server communications at all, you will be informed that the MCU is forcing the Fall Back Mode to 1, which is always Fall-Back Mode required for stand-alone operation. Has Been Set = 1 The next sections will follow each communications mode selection.

14 M e g a t r a k M C U S e t u p G u i d e P a g e 14 TCP/IP Networking Configuration First, we will follow the screens given a selection of N (Network). Networking requires some specific information that is usually provided by the network administrator. Some of this information is used to give the MCU a network identity and to tell it how to communicate, and other information tells the MCU the identity of the server computer that it should report to. Network ID numbers are always formed as four numbers, each between 0 and 255, separated by dots, as in this example: When entering a network address, subnetwork mask or gateway IP address into the MCU-9000, use the SPACE key to represent the dots. DHCP Mode The first screen will ask if DHCP should be enabled. DHCP stands for Dynamic Host Configuration Protocol and will allow the MCU to obtain some of its network settings automatically if the network has a DHCP server present (as most do). While this is often simpler than using Enable DHCP? N assigned numbers for the MCU, it is generally not advised for fixed equipment, like an MCU, to use DHCP. Instead, the system network administrator should provide the numbers needed.

15 M e g a t r a k M C U S e t u p G u i d e P a g e 15 MCU Network Settings If DHCP mode is selected, the next three screens will be skipped. If not, the next screen will ask for the IP address to be assigned to the MCU itself. Enter the correct IP address over the default address and press ENTER. The next screen asks for the Subnetwork Mask and then the Gateway IP Address. Enter the numbers provided by your administrator for this MCU. (Each MCU must have a unique MCU IP Address.) Server Network Settings After the MCU network values are entered, or if DHCP mode was selected, the MCU will ask for the server information. The server must be located at a fixed (unchanging) IP address, although it can be anywhere on the local area network or on the Internet. (The values shown are examples only.) The server listens for connections on a TCP port number Server IP Addr? Server TCP Port? 4040 between 1 and 65,535. The default port number used by MCUs is 4040, but some networks may require that this port number to be different for security, firewall or routing reasons. If the MT PRO server is located behind a NAT (Network Address Translation) router or firewall, the TCP port used will need to be allowed to pass-through for the MCUs to be able to reach the server (sometimes called port forwarding ), and the exposed IP address of the router will need to be programmed into the MCU as the server address. Some content management proxy servers may block the MCU communications. In this rare event, the MCU communications will need to be allowed by proxy server configuration to bypass the proxy server. This is not uncommon and is usually easily done by your network administrator. These are typical networking issues, and your network administrator can easily advise you how to handle these common router and firewall configuration details.

16 M e g a t r a k M C U S e t u p G u i d e P a g e MHz Radio Configuration If you have selected option R, for radio (wireless) communications, the screens will be different than for networking. The 910 MHz commercial radios supported by the MCU-9000 have their own settings that will be configured here. Radio Channel Selection The first screen will ask you to enter a radio channel number. Valid channels numbers are 16 through 32 (inclusive). The default channel number is 16. All radios in a system need to be on the same channel as the Radio Channel? central server radio. If there are multiple, independent networks operating in proximity to one another, different channels should be used for each network. (NN) 16 Also, if interference from other commercial 910 MHz radio signals is suspected, a change of channel will likely allow you to avoid it. Radio Server MAC Address The next question is a request for the radio MAC (Media Access Control) address of the server side radio. If this value is entered as exactly FFFFFF, then the MCU-9000 will use system-wide broadcasts to reach the server. While broadcasting will work, more reliable and efficient messaging can be had by entering Enter Server MAC the unique radio MAC address of the server radio here. (HHHHHH) FFFFFF This will be a HEXADECIMAL number unique to the radio module in use at the server and should be printed in the server-side radio case or found by running the radio configuration program on the server computer (See Server-Side Radio Configuration below for more details) or using the Radio Test mode.

17 M e g a t r a k M C U S e t u p G u i d e P a g e 17 Radio Signal Strength Testing Those installations that use radio (wireless) communications often need to know how well the radio signals are working, and if the antennas are properly connected or aimed. A feature of the MCU-9000 in the Radio ( R ) mode is a signal strength test. In the Setup menus, after setting the radio channel and the server MAC address, the Radio Test option will be presented. If the answer is Yes ( Y ) then the MCU-9000 will send a test message to the server radio and receive a response. It will then display the MAC Radio: address of the responding radio, the signal strength last received by the MCU from the server (In), and the signal Please Wait strength last received by the server from the MCU (Out). Radio: These values will be displayed as values between 0 and 255. Poor radio signals will display lower values, and In: 122 Out: 95 healthy signals will result in higher values. (See Server-Side Radio Configuration below for more details) Radio signals in the range of 90 or higher are very strong and reliable. Signals below this level may also work, but will be affected more by obstacles or background noise. The antennas and cables used, the terrain and elevation, antenna aiming, distance, and the finer points of the installation are critical to reliable radio operation. Signal levels as low as 50 have been seen to function intermittently, and levels above 80 are generally considered acceptable for reasonable communications. Every seconds, the MCU-9000 will send another test message and get another set of signal strength values to display. An affirmative beep sound is issued each time a new test message is sent and returned and new values are displayed. Removing the SETUP key will terminate the Radio Test mode and exit setup. Note that selecting Y to enter the Radio Test mode saves the settings that have been provided up to this point in the SETUP process, including the server MAC address and radio channel number. It should be understood that getting authorization to fuel from the server via radio must occur in a reasonable amount of time, or the MCU will go to Offline mode and allow fueling based on the Fall Back level setting. However, even in poor communications situations where the radio connection to the server is intermittent, transaction delivery is very persistent and it is likely that transactions will get through to the server in time. Also, remember that the radio at the server side may be a 1000mw while the radio in the MCU-9000 is probably 200mw. This means that the In signal strength may be greater than the Out signal. None the less, radio communications require a strong connection in both directions, and so the lower value of the two will define the performance of the system.

18 M e g a t r a k M C U S e t u p G u i d e P a g e 18 Server Side Radio Configuration Laird, Aerocomm and related Laird Technology Corporation product names are the sole property of Laird Technology Corporation, and are used herein with their express permission. To configure the free-standing radio module located at the server side, use the third-party Laird Technology Configuration/Test Utility, available on the CD ROM, the MegaTrak website or from Install this utility normally and then execute it. Using this utility, do the following: 1. Execute the Laird OEM.exe utility Select product Connex On the opening screen, select the PC Settings tab 3. Under Product, drop-down and select the Connex4790 product option 4. Set the Port Settings as-per your PC port, always 2400 baud, etc. 5. Under the Configure tab, press the Read Radio button and see if you can read the current data from the radio (make sure the radio is connected to the PC serial port). If you don t get the Read Successful response, check your radio settings and connections. You must get the Read Successful box before you can proceed.

19 M e g a t r a k M C U S e t u p G u i d e P a g e 19 Channel Number you are using (usually 16) Select only Auto Destination 6. Be sure that Max Transmit Retries is set to 4 7. Set RF Channel Number to 16 (or whatever channel your system is using) See Note below. 8. Be sure that Random Backoff is set to 1-4 packet times 9. Make sure all the Radio Features boxes are NOT checked, except Auto Destination which SHOULD be checked 10. Drop-down and select Interface Baud to 2400 Note: Some versions of this program specify the RF Channel Number in HEXADECIMAL. If the RF Channel Number box says Hex on the right side instead of Dec, then enter 10 for channel 16, because 10 in hex equals 16 in decimal.

20 M e g a t r a k M C U S e t u p G u i d e P a g e 20 Baud rate 2400 Write changes to the radio 11. Click the Write Radio button and allow the radio to be updated 12. After the write-back of the settings to the radio, the utility will ask you for an optional comment. You may enter a note here that will go into the log file to explain your changes, like Set up radio, or you may enter nothing if you wish, and click OK. Note: Until the radio settings match the ones shown in these examples and the radio has been successfully updated with these settings, proper operation will not occur.

21 M e g a t r a k M C U S e t u p G u i d e P a g e 21 Hard-Wired Configuration If you have selected the option W for hard-wired communications, the screens will ask for the basic settings required for hard-wired operation. Note: Settings for hard-wired mode are in development and will soon provide variable data rates and other features. At the time of this writing, the data rate (default) is 2400 baud with no flow control. Note: The hard-wired mode uses RS485 balanced-pair wiring between MCUs. Please refer to the technical document MCU-9000 Hard Wired Installation Guide, or contact Megatronics, for more information on the correct methods for installing hard-wired communications systems. Hard-Wired to External Radio In situations where the 200mw, 910 MHz radio option available inside the MCU-9000 is not enough, it is also possible to wire the MCU to an external radio transceiver if it supports an RS485 protocol connection. The MCU-9000 is set to the Hard-Wired ( W ) mode. This scheme can also be used when connecting several MCU-9000s together using hard-wire and then using a single radio and antenna to relay this to the server computer. High-power 900 MHz, RS485 Radio Transceiver To other MCUs RS485 Serial Coaxial Cable Long-range directional antenna Any radio, microwave or other communications system that can support 2400 baud bi-directional (halfduplex) data rates can be used. The radio transceiver will require a weatherproof enclosure and 120 VAC power. A wide variety of antenna types and capabilities are available. Antennas mounted above surrounding structure and terrain should have adequate lighting protection included.

22 M e g a t r a k M C U S e t u p G u i d e P a g e 22 Telephone Modem Configuration Note: In the older MegaTrak systems, a local site computer was installed near the MCUs and then the computers were linked using telephone modems. With the MCU-9000, a simple Hayes-compatible modem unit at the MCU can be controlled and will dial-up the central MT PRO computer and exchange fueling authorization and transaction data directly, which greatly simplifies the system and eliminates the site computer. If you have selected the option M for telephone line modem communications, the screens will ask for the settings required to dial-up the server modem. First, the MCU will require a phone number that it should dial to reach the server. This string can be 16 characters long and may include pause characters (commas) as shown in the second example for a system where 9 must be dialed, followed by a wait, for an outside line. Please omit dashes, dots or spaces from phone numbers. Server TP Number Server TP Number 9,,,, Next, the MCU will ask for any modem initialization string that should be issued to the telephone modem at start-up. This string can be up to 16 characters long. Items separated by spaces will be issued to the modem in separate AT command sequences. This is used to configure the modem properly, and may vary depending DT ATA on the modem type selected. Modem Initialize Note: The Modem interface is currently in development and will include selectable data rates and other features as well, depending on the modem hardware selected for use with the MCU9000.

23 M e g a t r a k M C U S e t u p G u i d e P a g e 23 MTiButton Mode The MCU-9000 can use MTiButtons as an alternative to Datakeys or cards for various types of operations. The setup screen for MTiButton Mode should be set to N if MTiButtons are not used or to C if they will be used in the same way as proximity or other cards. MTiButton Mode: (N/C/E) N The E option is for the special EB Mode. See Appendix A for more information about setting up and using the EB Mode..

24 M e g a t r a k M C U S e t u p G u i d e P a g e 24 Setting-Up Pumps The MCU-9000 can manage as many as sixteen pumps or hoses, each with its own unique Pump number, fluid type, tank affiliation and logs. This means that each pump must be configured for the way it should operate. Primary Pump Number The MCU-9000 will first ask for the pump number to be assigned to the primary pump, which means the pump that is controlled by the MCU itself. The display will show the current Primary pump number. Press ENTER to leave it the same. Primary Pump? 01 When using expander modules to add more pumps, hoses or reels to the MCU-9000, there will be multiple pumps under the control of the MCU. The next screens allow the user to set-up the operation of the primary pump and any of the added expander pumps. Pump to Set-Up The MCU will next ask which pump you wish to configure, starting with the primary pump, which is the pump that is controlled by the MCU itself. If you press ENTER here then the primary pump is selected. Pump to Setup? At this point you can select another pump that has been already configured on this MCU, or you can enter a new 10 pump number. If the pump number you enter already exists, you will be allowed to configure it. If you enter a new pump number, the new pump will be created and then you will be able to configure it. Pressing the CLEAR button at this prompt will bring-up the next already existing pump in the MCU Use this method to cycle through the pumps known to the MCU and select one to change its settings. To delete a pump from the MCU-9000, see the Fuel Type section below. You cannot delete the primary pump, although you can change the primary pump number. If the pump number you enter is new, the MCU will ask if it should add the new pump to the system. When new pumps are added using expansion modules plugged into the MCU, they will have a code that is either New Pump BUS ID? fixed (for some type expanders) or set in the expansion module using small switches. This code is called the BUS 23 ID of the device. The MCU will need to know the BUS ID of the expansion device in order to communicate with it. (See the documentation accompanying the expansion devices for more details.) After the new pump is added, the MCU will proceed to let you configure the new pump.

25 M e g a t r a k M C U S e t u p G u i d e P a g e 25 Pump numbers must be unique in any given fueling site. So remember that if one MCU controls pumps 01, 02 and 03, then another MCU in the same site must not have any of the same pump numbers. The database on the server treats each pump as if it is independent and associates each with a tank and fluid type. Authorization for all the pumps or hoses under the control of one MCU-9000 is based on authorization for the primary pump. In other words, if the MCU-9000 has control of pumps 10, 11, 21 and 22, then the authorization for pump 10 (the primary pump) will control access to all the others as well. Fuel Type The MCU will next ask for the three-letter fuel type code for the pump or hose being configured. This should match the Database fuel type code for this pump number. Common codes are DSL (Diesel) and Fuel Type? UNL (Unleaded). (CCC,-) If this pump needs to be deleted from the MCU-9000, type only a dash -, followed by ENTER, at this prompt and the pump will be removed. Note that the primary pump cannot be deleted. DSL Pulser Resolution High Res Pulser: The pulses obtained from some electronic dispensers may be as high as 1000 pulses per unit of fuel. To handle these high resolution pulse sources, set the High Res Pulser mode to Y. This will reduce the pulser calibration by a factor of ten (10). N) N Pulser Calibration When fuel is flowing, a device called a pulser counts the amount of fuel that is delivered and the MCU-9000 Pulses/Unit: keeps count of this to report how much fuel was dispensed, as well as to prevent the delivery of (NNN) _10 unreasonable amounts of fuel. Different pulser units may have different ratios of pulses-generated-per-unit-pumped, so the MCU has to know this ratio to count the fuel correctly. The next screen asks for the pulser factor, or the number of pulses per unit (gallon, liter, etc.). Enter the pulser factor here.

26 M e g a t r a k M C U S e t u p G u i d e P a g e 26 Pulser De-Bounce The pulser is usually a relay contact, and contacts tend to bounce, which can cause false readings. The MCU-9000 applies a debounce algorithm to eliminate this problem. The default debounce value of 100 is usually sufficient for most systems. However, in pumps with high-ratio pulsers (like 250:1) it is possible Pulser Debounce? that pulses could be missed, and so the debounce may need to be set lower. If the fuel count is intermittently higher than it should be, use a larger debounce setting. (NNN) 100 If the fuel count is intermittently lower than it should be, try a lower debounce setting. The maximum debounce setting is 255, and the minimum is 1. (Note: When a high-resolution pulse source is being used, set the Pulser De-Bounce to a low value to prevent missed pulses.) MCU Door Switch The MCU may operate with or without the door switch playing a role. The door switch often provides a safety shut-off, but not all installations require it. The next menu allows the door switch input to be disabled. Door Sw Present? Y The Door Switch question will only be asked for the Primary Pump.

27 M e g a t r a k M C U S e t u p G u i d e P a g e 27 Hook Switch Set-up The hook switch tells the MCU when the fuel nozzle is on the hook, or off the hook and ready to fuel. A hook switch may be used in some systems and may not be used in others. The next screen asks if this Hook Sw Present? pump or hose has a hook switch present. If there is a hook switch present, the MCU then needs to know if the switch is wired in normal or inverted fashion. If the hook Y switch appears to register as on-hook when it is actually Hook Sw Invert? off-hook, invert the polarity of the hook switch signal by answering Y here. Off-Hook-To-Fuel Mode Systems that have a hook switch may be programmed to turn on the pump or valve as soon as authorization is received, or to wait until the nozzle is taken off-hook before starting the pump. If the next question Off Hook To Fuel is answered Y then the pump will start, or the valve will open, only when Off-Hook To Fuel fueling has been authorized and when the nozzle is lifted Y off-hook. Y Note: In previous systems, there was no option for Off-Hook To Fuel, and so the pump was sometimes wired in series with the Hook Switch to accomplish the same result. Anti-Spill Mode The MCU-9000 has some new features that are intended to prevent fuel spills in many commercial installations. In the Anti-Spill mode the MCU will detect if fuel is flowing too soon after the pump or valve is turned on, which usually indicates that a spill is taking place. The fueling cycle will be quickly stopped if Anti-Spill Mode? this is detected. Use this screen to turn the anti-spill features ON or OFF. Y

28 M e g a t r a k M C U S e t u p G u i d e P a g e 28 Flow and Hook Timers When fueling is authorized, the MCU allows a limited amount of time for the fueling to begin. If fuel flow is not observed in the time determined by the Flow Timer (in seconds) then the fueling session will be ended Flow Timer? for this pump or hose. (Setting a zero value for the Flow Timer disables the timer.) (NNN) _60 Once fuel begins to be dispensed and then fuel flow stops, a limited amount of time is allowed before the nozzle must be returned to the hook or fuel flow must begin again. If no fuel flows and the nozzle is not restored to the on-hook position in the time allowed by the Hook Timer (seconds) then the fueling session will be ended for this pump or hose. Hook Timer? (NNN) 180 There is no Hook Timer function in systems where the hook switch is disabled. (Setting a zero value for the Hook Timer disables the timer.) Re-Pump Mode Each pump may also be set to allow fueling to begin and end, and then to begin again, as long as authorization remains valid (i.e. the Datakey remains in the drive and a timeout has not occurred). This feature Re is useful in lube-reel applications where a reel may be used once, and then used again, during one authorized fueling session. N Re-Pump Enabled? Note that each fueling session is reported to the database as a separate transaction.

29 M e g a t r a k M C U S e t u p G u i d e P a g e 29 Ending the Setup Mode When you reach the end of the set-up process, or if you enter only X and Enter at almost any setup mode prompt, you will be asked if you wish to exit the setup mode and store the changes that you have made into permanent memory. If you select N then you will be Exit Setup? Y returned to the start of the set-up mode and none of your changes will be saved into the permanent memory. This will allow you to proceed through the setup menus and make changes or adjustments to your settings. When you respond with a Y, the changes you have made will be stored to the permanent memory, changes made to the pumps will be issued out to them, and the MCU will be re-started. When changes are made during SETUP, some of them take place at once and others have to be sent-out to the various subsystems before they will take effect. Any changes that you make during SETUP may be discarded if you do not answer Y at the Exit Setup screen to save the changes to permanent memory. The permanent memory is flash-based storage that retains data even during extended power loss. If you get an error message during this final step, then most likely one or more pumps on the expansion bus could not be reached to be updated. This pump will not function properly, and changes you may have made to its settings will not take effect until the communication problem is corrected. To cause the settings to be sent out to the expansion modules again after the problem is corrected, enter SETUP and then exit again, or simply power-cycle the MCU The MCU always sends the pump settings out to the pumps when it starts-up and upon exiting the setup mode when changes have been made.

30 M e g a t r a k M C U S e t u p G u i d e P a g e 30 Settings Transfer Keys The MCU-9000 also supports a special Datakey type called a Settings Key. This key is generated by the MCU when the user provides an ADMINISTRATOR key and uses the special function F3. It is used to collect all the settings from an MCU into a Datakey, or to install settings into an MCU from a Datakey. Making a Settings Key When the user with an ADMIN key presses F3, the MCU displays the Write Settings to Key message, and then asks ARE YOU SURE?. If the user answer is Y then the MCU will ask that the ADMIN key be removed and a 16K bit key, like a Transfer Key, be inserted. (Note that any and all data already on this key will be erased, including any transactions! Use Caution!) ARE YOU SURE? N Remove ADMIN Key When the new Datakey is inserted, the MCU and Pump settings will be written to the key, creating a Settings Key. Injecting Settings from a Settings Key To inject these saved settings from a Settings Key into the same or another MCU-9000, insert the Settings Key. The saved settings on the Settings Key MUST have the same System ID as the system you are about to set-up. (The MCU System ID can only be changed using a SETUP key that contains the new System ID, and the correct SETUP key password.) Settings Written To Key Will Reload ALL Settings frm Key Enter Password: You will be asked for the existing system SETUP KEY password (Factory: SPACEAGE). Once the password has been properly provided, the MCU will announce that it will soon restore all the MCU settings and Pump settings from the Datakey you have provided, and it will ask ARE YOU SURE?. *******_ ARE YOU SURE? N

31 M e g a t r a k M C U S e t u p G u i d e P a g e 31 If the response is Y then the Settings Key will be read and all the setting stored therein will be copied into the MCU Next, the MCU will announce that the load is completed, and then ask if you wish to Exit the Setup mode. Your must answer Y (or press ENTER) to commit the settings you have loaded from the Settings Key to permanent memory in the MCU. Settings Loaded From Key Exit Setup? Y Important Note: When any or all setting changes are made manually using the SETUP key, or down-loaded from a Settings Key, they may take effect but may be lost when the MCU is restarted. Only a proper exit from the SETUP mode wherein the MCU says Settings Saved and then Pumps Updated will guarantee that the changes are all stored in the MCUs flash memory and will be used after future restarts. You can cause the MCU-9000 to re-start by using the SETUP key, entering the password, saying N to the RESTORE FACTORY question, and then ending the set-up process by entering X. Set-up always ends by storing all the changes and re-starting the MCU-9000 system.

32 M e g a t r a k M C U S e t u p G u i d e P a g e 32 Fall-Back Levels The MegaTrak system uses a Fall Back Level code, between 1 and 4, in Datakeys to specify the behavior of the MCU-9000 when communications or server failures occur. The fall-back levels are defined as follows: Level: Function: 1 Communication with the site server is attempted, and if it fails then the MCU goes into OFFLINE mode, and fueling is allowed (based on Meter Check and data entered by driver). Transactions are stored in the MCU until communication is restored or they are collected by Transfer Key. 2 Communication with the site and central servers is attempted. If it fails, fueling is allowed (based on the site server, Meter Check and data entered by driver). Transactions are stored in the MCU until communication is restored or they are collected by Transfer Key. 3 Communication with the server is required to fuel. If the server cannot be reached in several attempts or the MCU is already off-line, fueling is denied. 4 Communication with the server is required to fuel. If the server cannot be reached in several attempts or the MCU is already in OFFLINE mode, fueling is denied. Note: In past systems with older technology, local site servers were used with a central server. Newer systems do not use a site server, so Fall-Back level 1 and 2 are essentially the same, as are levels 3 and 4.

33 M e g a t r a k M C U S e t u p G u i d e P a g e 33 Meter Check Codes The meter (odometer or hour meter) entered by the driver on the MCU keypad is tested and fueling is allowed based on the Meter Check setting for that Datakey. The testing of the meter value is based on the MIN and MAX fuel amounts provided in the Datakey. The Datakey holds the meter reading last used to fuel. If the new meter entry is less than the previous reading plus the minimum, the meter is said to be Out of Range. If the new meter entry is more than the previous reading plus the maximum, the meter is said to be out of range. Meter check codes are as follows: Code: Behavior: 0 No meter value is requested, no meter value is required to fuel, Datakey is not updated 1 Meter value is requested, but not tested. Any meter value is accepted. Datakey is updated. 2 Meter value is requested and tested. If the meter is out-of-range, the driver is asked to try again. If the driver makes three attempts and all are out-of-range, then fueling is allowed and the meter in the Datakey is updated. 3 The meter value is requested and tested. If the meter is out-of-range, fueling is not allowed. Setting the Meter Check value to zero (0) allows fueling without regard for odometer or hour meter entries, and the meter is not even requested by the MCU. Setting the Meter Check value to one (1) causes the driver to be asked to enter the meter reading, but allows fueling no matter what value is provided. Setting the Meter Check value to two (2) causes the driver to be asked to enter the meter reading, and the value entered is tested to see if it in range. If the meter entered is not in the acceptable range, then the driver receives an Invalid Meter, Please Retry message. If the meter value is retried three times, fueling is allowed and the Datakey meter value is updated. Setting the Meter Check value to three (3) causes the driver to be asked to enter the meter reading, and the value entered is tested to see if it in range. If the meter entered is not in the acceptable range, fueling is not allowed. Note: If the MCU9000 is set for No Meter (answer Y ) in the SETUP menus, then the Meter Check in the Datakey is ignored and a meter value is never requested nor tested by this MCU, and no meter value is written back to the Datakey. This mode is for MCUs in control of gates or other non-fueling functions.

34 M e g a t r a k M C U S e t u p G u i d e P a g e 34 MCU-9000 with HID Proximity Cards The popular and ubiquitous HID brand proximity cards used in access control and security systems can also be used with the MCU The card reader is attached to the side of the MCU-9000 housing or anywhere that the user prefers. The card ID is generally used as the Driver ID in the system. Other brands of Proximity cards or tokens may be used if appropriate readers are provided with Wiegand or serial data outputs. Key Types with Read-Only Cards When using proximity cards, the card serial number and facility code are fixed and there is now way to write additional data to the card. This means that cards used with the MegaTrak MCU-9000 cannot be programmed with Key Type information. The MCU-9000 must therefore assume that all cards represent a specific key type. In the SETUP process, the administrator tells the MCU-9000 what key type is represented by cards. A special feature of the MCU-9000 allows the Facility Code (sometimes called Site Code) in the cards to be used to differentiate them if desired. The MCU can be programmed with a specific Facility Code that will represent each key type, and cards can be purchased that have these facility codes. For example: A system can have cards that have facility codes of 100 to use as Driver cards, and also cards that have facility codes of 101 to use as equipment cards. When the card is presented, the MCU-9000 examines the facility code and assigns a Key Type to the card based on the programmed facility code values. MCU-9000 Behavior with Cards MCU Setting: First Credential: Second Credential: N (None) Cards not allowed N/A D (Driver) Card is Driver Equipment/Vehicle per Card, Datakey or Keypad Entry E (Equipment) Card is Equipment Driver ID per Keypad Entry F (Per facility Code) (See D,E,S,or A above)

35 M e g a t r a k M C U S e t u p G u i d e P a g e 35 Appendix A: MTiButton EB Mode General The MCU-9000 supports a special mode in which MTiButton key devices are used in special ways. This is called the EB Mode. In this mode, MTiButtons can be used for Attendant, Driver and Vehicle identification, and the vehicle is tethered to the MTiButton reader probe while fueling proceeds. The fueling session proceeds in this manner: 1) The service station attendant touches his personal MTiButton to the pump probe 2) The driver touches his personal MTiButton to the pump probe 3) The driver enters the Fuel Order Number on the keypad 4) The driver enters the odometer reading on the keypad 5) The attendant secures the pump probe to the vehicle MTiButton 6) Authorization is requested 7) Fueling proceeds 8) If the vehicle MTiButton is disconnected during fueling, the fueling session stops About MTiButtons in EB Mode There are many types of MTiButton devices, and each device serial number begins with a code that tells what type it is, called a Family Code. These Family Codes are similar to the Facility Codes that are programmed into cards, and we use this code to determine if the MTiButton is a Driver, Attendant or Vehicle type. (Vehicles are typically type 1 devices.) The MCU-9000 assumes that station Attendants fall into the category of Special users. So, to clarify the settings used: Drivers = Driver Keys Attendants = Special Keys Vehicle = Equipment Key