Académique Documents
Professionnel Documents
Culture Documents
SAFETY CONSIDERATIONS
Read all warning notes and instructions carefully. They are included to help you installing the Product safely
in the highly flammable environment of the fuel station. Disregarding these warning notes and instructions
could result in serious injury or property damage. It is the installer responsibility to install, operate and
maintain the equipment according to the instructions given in this manual, and to conform to all applicable
codes, regulations and safety measures. Failure to do so could void all warranties associated with this
equipment.
Remember that the fuel station environment is highly flammable and combustible. Therefore, make sure
that actual installation is performed by experienced personnel, licensed to perform work in fuel station and at
a flammable environment, according to the local regulations and relevant standards.
WARNING
Components substitutions could impair intrinsic safety.
Attaching unauthorized components or equipment will void your warranties.
CAUTION
Do not attempt to make any repair on the printed circuit boards residing in the Product, as this will void all
warranties related to this equipment.
PROPRIETY NOTICE
This document contains propriety and confidential information. It is the property of ORPAK SYSTEMS
Ltd. It may not be disclosed or reproduced in whole or in part without written consent of ORPAK
SYSTEMS. The information in this document is current as of the date of its publication, but is subject to
change without notice.
DISCLAIMER
This document is provided for reference only. Although every effort has been made to ensure correctness,
ORPAK SYSTEMS does not guarantee that there are no errors or omissions in this document.
FCC Warning
Modifications not expressly approved by the manufacturer could void the user authority to operate the
equipment under FCC Rules.
TABLE OF CONTENTS
Paragraph
Page
1
1-1.
1-2.
1-2.1.
1-2.2.
1-2.3.
1-2.4.
1-2.5.
1-3.
1-4.
1-4.1.
1-4.2.
1-4.3.
1-4.4.
1-5.
1-6.
1-7.
INTRODUCTION .............................................................................................................. 21
SITEOMAT ........................................................................................................................ 22
Overview ........................................................................................................................ 22
Interfaces ........................................................................................................................ 22
Internal Communication Alternatives ............................................................................ 24
External Communication Alternatives........................................................................... 24
Data Access Methods..................................................................................................... 24
ORCU ................................................................................................................................. 24
SYSTEM WORKFLOW EXAMPLES ........................................................................... 26
General ........................................................................................................................... 26
Refueling Scenario with FuelPoint PLUS ..................................................................... 26
Refueling Scenario with Magnetic Cards ...................................................................... 26
Refueling Scenario with 2 devices (2 stage authorization)............................................ 26
MANUAL STRUCTURE .................................................................................................. 27
USING THIS MANUAL.................................................................................................... 28
REFERENCES ................................................................................................................... 29
2
2-1.
2-2.
2-2.1.
2-2.2.
2-3.
2-4.
2-4.1.
2-4.2.
2-5.
2-5.1.
2-5.2.
2-5.3.
GENERAL DESCRIPTION
PRE-SETUP INFORMATION
GENERAL.......................................................................................................................... 30
SETUP DEFINITION INFORMATION ........................................................................... 30
Required Setup Information........................................................................................... 30
Required Setup Information Example......................................................................... 30
SITE SURVEY ................................................................................................................... 31
ETHERNET NETWORK ADDRESSES ........................................................................... 32
Network Addresses for Controller Internal Devices...................................................... 32
Serial Addresses for Controller Devices ........................................................................ 32
NAVIGATION NOTES ..................................................................................................... 38
Not Saving Change ........................................................................................................ 38
Saving Data .................................................................................................................... 38
Errors.............................................................................................................................. 38
TABLE OF CONTENTS
Paragraph
Page
2-5.4.
Confirmation .................................................................................................................. 39
2-5.5.
Success ........................................................................................................................... 40
2-6. CONFIGURATION AND SETUP PROCEDURES .......................................................... 40
2-7. BYPASS FEATURE FOR MECHANICAL PUMPS ........................................................ 42
4
4-1.
4-2.
4-3.
4-3.1.
4-4.
4-4.1.
II
SETUP WIZARD
GENERAL .......................................................................................................................... 60
SOFTWARE REQUIREMENTS ....................................................................................... 61
ACCESSING THE WIZARD............................................................................................. 61
Microsoft Silverlight Installation ................................................................................... 62
SETUP WIZARD PROCEDURE....................................................................................... 65
Validation of Parameters ................................................................................................ 65
TABLE OF CONTENTS
Paragraph
Page
4-4.2.
Page 1 - Welcome .......................................................................................................... 65
4-4.3.
Page 2 Global Parameters ........................................................................................... 66
4-4.4.
Page 3 - Forecourt Controller Type ............................................................................... 67
4-4.5.
Page 4 - Forecourt Setting.............................................................................................. 70
4-4.6.
Page 5 - Products ........................................................................................................... 72
4-4.7.
Page 7 - Pumps............................................................................................................... 75
4-4.8.
Page 8 Payment ........................................................................................................... 77
4-4.8.1.
Product Map .............................................................................................................. 78
4-4.9.
Page 9 Printer .............................................................................................................. 80
4-4.10. Page 10 Series 1000 Upgrade ..................................................................................... 81
4-4.11. Page 11 Series 1000 Upgrade ..................................................................................... 82
4-4.12. Page 12 Backup........................................................................................................... 83
4-4.13. Finalizing the Wizard..................................................................................................... 84
4-5. MAIN SETUP SCREEN BASIC MODE........................................................................ 85
4-5.1.
Functional Buttons ......................................................................................................... 87
4-6. SETUP WIZARD DEFAULTS.......................................................................................... 87
4-6.1.
Ethernet Network Default Addresses............................................................................. 87
4-6.2.
Cluster Port Allocation .................................................................................................. 88
4-6.3.
Pump Clustering Conventions ....................................................................................... 88
4-6.4.
TLG Settings .................................................................................................................. 91
4-6.5.
Naming Conventions ..................................................................................................... 91
4-6.6.
Cluster Log Port Conventions........................................................................................ 91
4-6.7.
Loading Existing Setup .................................................................................................. 92
5-1. GENERAL.......................................................................................................................... 93
5-2. MANAGING USERS......................................................................................................... 93
5-2.1.
Login .............................................................................................................................. 96
5-2.1.1.
Password Change ...................................................................................................... 96
5-2.2.
Adding a User ................................................................................................................ 96
5-2.3.
Delete a User .................................................................................................................. 98
5-2.4.
Updating a User ............................................................................................................. 98
5-3. ACCESS LEVELS ............................................................................................................. 99
5-4. PASSWORD POLICY ....................................................................................................... 100
5-5. REGISTRATION ............................................................................................................... 102
III
TABLE OF CONTENTS
Paragraph
Page
7
7-1.
7-2.
7-3.
7-3.1.
7-3.2.
7-3.3.
7-4.
7-5.
7-5.1.
7-5.2.
7-5.3.
7-6.
IV
TABLE OF CONTENTS
Paragraph
Page
TABLE OF CONTENTS
Paragraph
Page
7-11.3.3.
Gilbarco Pump Specific Parameters .......................................................................... 161
7-11.3.4.
Tokheim Pump Specific Parameters ......................................................................... 162
7-11.3.5.
Wayne Dart Pump Specific Parameters .................................................................... 162
7-11.4. More Pump Options ....................................................................................................... 163
7-11.5. Finalizing Pump Settings ............................................................................................... 165
7-11.6. Deleting Pump................................................................................................................ 165
7-12. EXPORT/ IMPORT ............................................................................................................ 166
7-12.1. General ........................................................................................................................... 166
7-12.2. Exporting / Saving Setup................................................................................................ 166
7-13. APPLYING THE SETUP SETTINGS ............................................................................... 167
7-14. VERIFYING DEVICES STATUS ..................................................................................... 168
7-15. PIPE FLOW MEASUREMENT......................................................................................... 169
MAINTENANCE
VI
TABLE OF CONTENTS
Paragraph
Page
8-3.1.
Recovery ........................................................................................................................ 186
8-4. LOG FILES ........................................................................................................................ 188
8-4.1.
Log File Rotation ........................................................................................................... 188
8-4.2.
Log File Format ............................................................................................................. 188
8-4.2.1.
General ...................................................................................................................... 188
8-4.2.2.
Date/Time Stamp and Thread ID .............................................................................. 189
8-4.2.3.
Locating Object ID .................................................................................................... 189
8-4.3.
Critical log file ............................................................................................................... 189
8-4.4.
BOS Log Files................................................................................................................ 190
8-4.4.1.
BOS_REMOTE_HO.log........................................................................................... 190
8-4.4.2.
Database Logs (DATA.log, META_DATA.log, LANG.log)................................... 190
8-4.4.3.
Web Server Access Logs (WebAccessxxxx.log) ...................................................... 190
8-4.4.4.
Web Server Communications Logs (WebCommxxxx.log) ...................................... 190
8-4.4.5.
Debug Log (debug.log) ............................................................................................. 191
8-4.5.
FCC Log Files ................................................................................................................ 191
8-4.5.1.
FCC_AUTH.log ........................................................................................................ 191
8-4.5.2.
Database Logs (DATA.DB.log, META_DATA.DB.log)......................................... 191
8-4.5.3.
Bus Logs (BUS_xxx.log) .......................................................................................... 192
8-4.5.4.
Pump Server Log FIles.............................................................................................. 194
8-4.5.5.
FCC Loader Log (fccloader.log) ............................................................................... 194
8-4.5.6.
Web Server Monitor Log (WebAccess6000.log, WebComm6000.log) ................... 195
8-4.5.7.
Web Server Watchdog Log (WebAccess6001.log, WebComm6001.log) ................ 195
8-4.5.8.
Web Server Access Logs (WebAccessxxxx.log) ...................................................... 195
8-4.5.9.
Web Server Communications Logs (WebCommxxxx.log) ...................................... 196
8-4.5.10.
Debug Log (debug.log) ............................................................................................. 197
8-4.5.11.
Lock Miss use Log (DebugLock.log) ....................................................................... 205
8-5. FCC MONITOR ................................................................................................................. 206
8-5.1.
Basic Navigation ............................................................................................................ 206
8-5.2.
Starting the FCC Monitor from a putty Window ........................................................... 206
8-5.3.
Starting the FCC Monitor from the Windows Command Prompt ................................. 208
8-5.4.
FCC Monitor Command Menu ...................................................................................... 209
8-5.4.1.
Pumps Overview ....................................................................................................... 209
8-5.4.2.
Tanks Overview ........................................................................................................ 210
8-5.4.3.
Device Status ............................................................................................................. 210
8-5.4.4.
Monitor Buses ........................................................................................................... 214
VII
TABLE OF CONTENTS
Paragraph
Page
8-5.4.5.
Debug Log ................................................................................................................. 217
8-5.4.6.
Admin Commands..................................................................................................... 218
8-5.4.7.
System Information ................................................................................................... 219
8-5.4.8.
Change Password....................................................................................................... 219
8-5.4.9.
Exit ............................................................................................................................ 219
8-6. LINUX COMMANDS........................................................................................................ 220
8-6.1.
df (Displays file-system information) ............................................................................ 220
8-6.2.
ifconfig (Command line tool to check all network cards/interfaces) ............................. 220
8-6.3.
Ping (Sends test packets to a specified server to check if it is responding properly)..... 220
8-6.4.
ps (Lists all existing processes on the server) ................................................................ 221
8-6.5.
top (Displays many system statistics and details regarding active processes) ............... 221
8-6.6.
grep (Filter output of other programs)............................................................................ 221
8-6.7.
vim (Text editor) ............................................................................................................ 222
8-6.8.
less (Text file viewer)..................................................................................................... 222
8-6.9.
tail (Display continuously file added lines).................................................................... 222
8-6.10. cd (Change current directory) ........................................................................................ 222
8-6.11. pwd (Show current directory) ........................................................................................ 222
8-6.12. ls (List directory) ............................................................................................................ 223
8-6.13. history (Show last typed commands) ............................................................................. 223
8-6.14. telnet (Open connection to IP port) ................................................................................ 223
8-6.15. script ............................................................................................................................... 223
8-6.16. Useful Linux Files .......................................................................................................... 223
8-7. SQLITE HANDLING......................................................................................................... 223
8-7.1.
Getting Inside the Directory of the DB Files & Start a Session of SQLite .................... 224
8-7.2.
Display all the Tables that are Inside a DB file.............................................................. 226
8-7.3.
Display the Types of each Field inside the Table .......................................................... 227
8-7.4.
Display all the Content that is Stored inside a Table ..................................................... 228
8-8. FHO HANDLING FOR SMALL SITES ........................................................................... 231
8-9. EVENTS / ALARMS ......................................................................................................... 231
8-9.1.
Events ............................................................................................................................. 231
8-9.2.
Logs ................................................................................................................................ 232
8-9.3.
Alarms ............................................................................................................................ 233
8-10. ORCU BOX LEDS ............................................................................................................. 235
8-11. RS-232 CONNECTOR ....................................................................................................... 238
8-12. ORCU CONNECTION VIA RS-232 ................................................................................. 239
VIII
TABLE OF CONTENTS
Paragraph
8-12.1.
Page
10
GLOSSARY
IX
TABLE OF CONTENTS
Paragraph
Page
APPENDIX E
APPENDIX F
F-1.
F-2.
F-3.
F-4.
APPENDIX G
DISCOVERY MODE
LIST OF ILLUSTRATIONS
Figure
Page
Figure 1-1 Islander PLUS in Home Base Station - General Configuration Diagram .................... 23
Figure 1-2 - OrCU - General View.................................................................................................... 25
Figure 2-1. Setup Requirement Example (Pump) .......................................................................... 31
Figure 2-2. System Address Example - Islander PLUS .................................................................... 34
Figure 2-3. System Address Example CFN PLUS........................................................................ 35
Figure 2-4. System Address Example - Extension Box .................................................................... 36
Figure 2-5. System Address Example ICR PLUS .......................................................................... 37
Figure 2-6. Cancel Warning Message ............................................................................................... 38
Figure 2-7. Processing Message ........................................................................................................ 38
Figure 2-8. Same Name Error Message............................................................................................. 39
Figure 2-9. IP Port Error Message..................................................................................................... 39
Figure 2-10. Device with Same Address Error Message................................................................... 39
Figure 2-11. Cannot Delete Message ................................................................................................ 39
Figure 2-12. Confirmation Message .................................................................................................. 40
Figure 2-13. Operation Successful Message ..................................................................................... 40
Figure 3-1. Login Dialog Box ........................................................................................................... 44
Figure 3-2. OrCU Administrator Home Screen .............................................................................. 44
Figure 3-3. System Information Screen............................................................................................. 46
Figure 3-4. Versions Screen .............................................................................................................. 46
Figure 3-5. Largest Files Screen........................................................................................................ 47
Figure 3-6. Mini Terminal Screen ..................................................................................................... 48
Figure 3-7. Unit Reboot Warning Message....................................................................................... 48
Figure 3-8. Time Setup Screen .......................................................................................................... 50
Figure 3-9. OrCU Password Screen .................................................................................................. 50
Figure 3-10. Serial/Modem Settings Screen...................................................................................... 51
Figure 3-11. UPS Setup Screen ......................................................................................................... 52
Figure 3-12. W&M Security Plug Message ...................................................................................... 54
Figure 3-12. Install SiteOmat Screen ................................................................................................ 54
XI
LIST OF ILLUSTRATIONS
Figure
Page
LIST OF ILLUSTRATIONS
Figure
Page
XIII
LIST OF ILLUSTRATIONS
Figure
Page
XIV
LIST OF ILLUSTRATIONS
Figure
Page
Figure 7-34. Defining a Virtual Pump - Pump Server Settings Dialog Box ................................... 170
Figure 7-35. Defining a Virtual Pump Setup Pump Settings Dialog Box .................................... 171
Figure 7-36. Virtual Pump Status .................................................................................................... 171
Figure 8-1. SiteOmat Modules ........................................................................................................ 173
Figure 8-2. Scheduling LogRotate................................................................................................... 174
Figure 8-3. Sys Commands Screen ................................................................................................. 181
Figure 8-4. Logging Settings Dialog Box ....................................................................................... 182
Figure 8-5. Backup Screen .............................................................................................................. 185
Figure 8-6. Putty Configuration Screen - 1 ..................................................................................... 206
Figure 8-7. Putty Configuration Screen - 2 ..................................................................................... 207
Figure 8-8. Putty Configuration Screen - 3 ..................................................................................... 207
Figure 8-9. Putty Configuration Screen - 4 ..................................................................................... 208
Figure 8-10. FCC Monitor Command Menu................................................................................... 209
Figure 8-11. Pump Summary........................................................................................................... 209
Figure 8-12. Tank Summary............................................................................................................ 210
Figure 8-13. Device Status .............................................................................................................. 210
Figure 8-14. Pump Status - 1 ........................................................................................................... 211
Figure 8-15. Pump Status - 2 ........................................................................................................... 211
Figure 8-16. Pump Status - 3 ........................................................................................................... 212
Figure 8-17. OPOS .......................................................................................................................... 212
Figure 8-18. Printer - 1 .................................................................................................................... 213
Figure 8-19. Printer - 2 .................................................................................................................... 213
Figure 8-20. List of Busses.............................................................................................................. 214
Figure 8-21. Bus Running Logs in XML ........................................................................................ 214
Figure 8-22. Bus Running Logs in Hexadecimal ............................................................................ 215
Figure 8-23. Raw Logs - 1............................................................................................................... 216
Figure 8-24. Raw Logs - 2............................................................................................................... 216
Figure 8-25. Raw Logs - 2............................................................................................................... 217
XV
LIST OF ILLUSTRATIONS
Figure
Page
XVI
LIST OF ILLUSTRATIONS
Figure
Page
XVII
LIST OF ILLUSTRATIONS
Figure
Page
XVIII
LIST OF TABLES
Table
Page
XIX
XX
SECTION 1
GENERAL DESCRIPTION
1-1. INTRODUCTION
This manual provides the setup instructions for the SiteOmat software application. This software is
the heart of Gilbarcos solution for close monitoring, tight control and successful operation of
Home Base Fueling Stations and vehicle fleets.
The SiteOmat automation software, which runs on an embedded operating system on the OrCU
(Orpak Controller Unit) embedded platform is designed to survive the harsh gas station
environment. SiteOmat performs as a fuel control and data acquisition system, and is part of
Gilbarco family of solutions for Home Base Fueling Stations.
SiteOmat software can be installed in the following Island Controllers:
21
1-2.2. Interfaces
SiteOmat Station Controller provides the following operational features for a comprehensive Home
Base Station management:
Support of large variety of communication links: cellular dial-in modem, VPN, satellite,
ADSL and more
22
Interface to Head Office Systems - The system has an interface for authorization and
for sending transaction to 3rd party head office/ SiteOmat Fleet Head Office using a
single export format (Web Services).
Figure 1-1 Islander PLUS in Home Base Station - General Configuration Diagram
23
24
OrCU includes a Security Access Module (SAM) for enhanced data protection and safe security key
storage (Triple DES encryption). OrCU includes a built-in server for Web access through Internet
Explorer 7.0 or higher.
OrCU includes the following communication ports:
25
A motorist stops for fuel at the station. His authorization device for the fueling transaction is a
magnetic card. The client swipes the card through the magnetic card reader on the payment
terminal.
The magnetic card information is read and sent to the Site Controller (OrCU) for authentication
and approval. The client lifts the nozzle and inserts it into the cars fuel inlet. Upon approval,
the fueling transaction starts, once the refueling is completed, the motorist replaces the nozzle
back to the pump. At this point the transaction data is kept internally. Data is periodically
transferred to the Fleet Head Office (FHO) for future billing.
During the authorization process the motorist may be prompted to enter more data to the
transaction (PIN code, Odometer, Vehicle No., Etc.). This is done by manually entering the
information using the payment terminal keypad.
1-4.4. Refueling Scenario with 2 devices (2 stage
authorization)
A motorist stops for refueling at the gas station. His authorization devices for the refueling
transaction include any two devices. One represents the vehicle and the other represent the
driver (e.g. two cards, two tags, card and tag, card and manual entry, etc.). The refueling
scenario for each device is the same as with magnetic cards (see above). For each device, the
motorist may be requested to add more relevant data to the transaction (PIN for the driver,
Odometer recording for the vehicle, etc.). The OrCU opens the dispenser for refueling only after
successful authorization of the two devices.
For all options above, the motorist may print a transaction ticket from the Islander PLUS printer
(optional).
26
27
CAUTION
An operating procedure, practice, etc., which if not
strictly observed, could result in damage to, or
destruction of equipment.
TIP
A useful guidance intended to help use the system in
a more efficient way.
NOTE
A relevant and important comment.
INSIGHT
More detailed technical/ functional information
regarding relevant issues.
28
1-7. REFERENCES
For additional and complementary information regarding Gasboys home base solution, please refer
to the following manuals:
Islander PLUS installation Manual, Document No. MDE-4811
CFN PLUS installation Manual, Document No. MDE-4813
Fuel Truck Controller installation Manual, Document No. MDE-4814
Wireless Gateway installation Manual, Document No. MDE-4815
SiteOmat Station Controller Users Manual, Document No. MDE-4818
OrPT Users Manual, Document No. MDE-4819
8-Port CommVerter Users Manual, Document No. MDE-4820
29
SECTION 2
PRE-SETUP INFORMATION
2-1. GENERAL
This section provides the preliminary information required for configuring the SiteOmat software.
This procedure consists of defining the devices and communication buses in the system, necessary
for the installation and setup of SiteOmat.
2-2. SETUP DEFINITION INFORMATION
2-2.1. Required Setup Information
The Controller system Islander PLUS, CFN PLUS, and Fuel Truck Controller - is provided with
the SiteOmat software already installed in OrCU.
Therefore, the setup procedures consist of defining the different buses or communication channels
that transport data to/from the controller systems.
Then the devices connected to the Controller and their operating attributes must be defined. These
devices range from pumps, payment devices up to the optional printer.
2-2.2. Required Setup Information Example
Figure 2-1 shows the required setup information for the pump server and a pump.
First, the user is required to define the pump server bus that transports data to/from the OrCU. This
Pump Server is an internal software module within the OrCU. The user is required to enter its IP
address, port and frame. This information is provided in Table 2-1 and Table 2-2.
30
31
Default IP Address
Starting IP
Address
Ending IP
Address
TCP Ports
OrCU Ethernet 0
(FCC)
192.168.1.104
192.168.1.104
8 Port
CommVerter
192.168.1.111
192.168.1.111
192.168.1.130
3001-3008
WGT Master
192.168.1.170
192.168.1.170
N/A
N/A
WGT
192.168.1.171
192.168.1.171
192.168.1.190
3001-3008
OrPT
192.168.1.211
192.168.1.211
192.168.1.230
3000
Receipt Printer
192.168.1.211
192.168.1.211
192.168.1.230
3485
Where:
Starting IP Address is the first IP number in the range allocated for the device
Ending IP Address is the last IP number in the range allocated for the device
For example, the range to the OrPT is 211 to 230 or a maximum of 20 OrPT devices in the station.
NOTE
IP addresses can be modified according to local
network requirements.
2-4.2. Serial Addresses for Controller Devices
Table 2-2 lists the setup addresses of devices, required for the configuration of the Controller.
32
Default Address
Starting Serial
Address
Ending Serial
Address
0x61
0x61
0x69
0x46
0x46
N/A
Printer
0x70
0x70
0x74
Journal Printer
N/A
0x1
N/A
Wireless Gateway
0x31
0x31
N/A
NOTE
The HEX address configured in the controller must
match the device HEX address. Otherwise, the
device is not loaded.
An example of address configuration for Islander PLUS and CFN controllers is displayed in
Figure 2-2 and Figure 2-3 respectively; examples for an Extension Box and ICR PLUS in
Figure 2-4 and Figure 2-5.
33
System Address
Islander PLUS
Optional
ICR PLUS
----.,
Remote console
Head Office
- 192.168.1.212-----
WGT
+
IP
OrPT
.---1'92.168.1.10
10.0.0.1
5 port
switch
192.
Router
OrCU
111
HID reader
MPI-C
1-1 -
nS450
0-MPI-C (sub)
21
02
I01
tt
MP
I-C (sub)
2-1
Dispensers
Probes
34
Optional
ICR PLUS
-----,
System Address
CFN PLUS
Remote console
Head Office
Optional
OutdOJr
- 192.168.1.21:2- -
WGT
o--
RS-232
MPI-C
1-1--
n.s ...;o
o--
MPI-C (sub)
21
02
01
tt
MPI-C.
1-1
Dispensers
Probes
35
Svstem Address
Extension Box
Optional
Outdoor
WGT
Islander PLUS
or
CFN PLUS
192.168.1.171
5 port
switch
192.
12
MPI-C
1-1--
MPI-C (sub)
2
1
MPI-C.
1-1
Oi$pensers
36
System Address
ICR PLUS
WGT
Islander PLUS
or
CFN PLUS
OrPT
192.168.1.171
5 port
switch
192.
.112
HID reader
MPI-C
1-1-
MP
I-C (sub),
2-1
MPI-C(sub). --------
2-1
Dispensers
37
38
39
40
41
g. Set the Controller and wait for synchronization success in the station
status row (it may take a few minutes)
h. Set fleets and devices
2-7. BYPASS FEATURE FOR MECHANICAL PUMPS
Site Controllers configuration for mechanical pumps include bypass switches a switch per
dispenser (apart from TopKat PLUS which requires adding an external bypass switch, P/N
813104450 to the existing distribution board). These should be used in cases of system malfunction
to enable refueling. The switch is connected to Line (high voltage cable) and to the controller (low
voltage wires) so as to provide indication on bypass state.
While the system is in Bypass state, SiteOmat keeps capturing the total dispensed from the pumps
and generates an event displayed in Event Viewer screen.
42
SECTION 3
OrCU ADMINSTRATION SCREEN
3-1. GENERAL
The SiteOmat Station Controller is factory set with the general configuration required for its proper
operation. However, settings may be modified in the OrCU Administration screen (see
Figure 3-2) according to location or network specifications.
3-2. TECNICIAN PC SOFTWARE REQUIRMENTS
The following software must be installed on the technician's PC prior to the controller setup
process:
1. OS Microsoft Windows 2000/XP/2003
2. Microsoft Internet Explorer 7 or a higher version.
3. Sun Microsystems Java application (Can be downloaded from http://Java.com)
3-3. INITIAL SETUP PROCEDURES
To set the initial Controller configuration, proceed as follows:
1. Follow steps 1 to 10 described in section 2-6 above
2. Turn on the browser and type the default IP address for the OrCU Administrator screen:
o http://192.168.1.104:8090
o https://192.168.1.104:8090 (for BSP ver. 1.08 SP 9 and up)
The login dialog box appears (see Figure 3-1)
NOTE
For cases where the OrCU default IP was changed or
the IP is unknown, see paragraph 8-12.
43
44
Description
LAN1 IP
LAN2 IP
PPP0 IP
Date/Time
OS up time
OrCU FW Version
OrCU S/N
OS serial number.
SiteOmat Version
OrData Version
Disk Statistics
Processes
Versions
Largest Files
Mini Terminal
Reboot Unit
45
46
47
48
Networking
Time
Password
Serial/Modem
UPS
3-5.1. Networking
SiteOmat Station Controller has a default IP address, which may be changed to suit the
requirements of the local network.
NOTE
The default IP address at LAN 1 is 192.168.1.104.
To set up the network, proceed as follows:
1. Click on the Networking navigation button
2. Follow the steps described in paragraph 9-3.3
3-5.2. Time
To adjust the Controllers date and time to match the regional date and time, proceed as follows:
CAUTION
Verify that all station activities are ceased before
modifying clock settings.
1. Click on the Time navigation button
2. The Time Setup screen appears (see Figure 3-8). Enter the Date and Time in the
corresponding text boxes
3. Select the Time Zone from the drop-down list
4. Click on the Change time settings button to save the changes
5. Reboot the system (see paragraph 3-4.4) to apply the changes
49
50
51
Definition
Company
UPS manufacturer.
Model
Retries
Time Left
Check Interval
IP Address
Log enabled
52
SiteOmat
OrData
Pump Server
PAIS
Operating System
3-6.1. SiteOmat
As a rule the SiteOmat is pre-installed, at the factory level, in the OrCU. However, whenever
required, SiteOmat can be installed in the OrCU in the station.
NOTE
Before installing SO versions 6.4.42 and up, upgrade
BSP (OrCU Operating System) to version 1.08 SP 9
(see Section 3-6.5).
From this version on, OrCU Administrator setup
web connects to OrCU unit using a secure link
(HTTPS).
Prior to installing SiteOmat, proceed as follows:
1. Obtain the SiteOmat installation files. The SiteOmat installation file is named as:
FCC_ORCU_dd_mm_yy
a_b_ccc.exe
Where: dd_mm_yy is the date the files were built, and a_b_ccc is the version.
For example: File FCC_ORCU_28_02_11
number is 6.3.300.
53
5. If the controller is configured for mechanical pumps, verify that the Weight & Measures
security plug is installed. The following reminding message appears (see Figure 3-12)
54
5. Click Upgrade to update SiteOmat to the latest version, or click Install to perform a
fresh installation
CAUTION
Clicking on Install, deletes all setup and database if
a previous version is already installed. A warning
message appears (see Figure 3-14).
55
3. Click Upload
4. Wait until the upload is finished (this process may take few minutes)
5. Click Upgrade to update OrData to the latest version, or click Install to perform a fresh
installation
CAUTION
Clicking on Install, deletes all setup and database if
a previous version is already installed. A proper
warning message is displayed.
6. Reboot the system (see paragraph 3-4.4)
3-6.3. Pump Server
To install the Pump Servers needed for interfacing with the specific pumps deployed in the station,
proceed as follows:
1. Click on the Pump Server navigation button. The OrCU Install Pump Servers screen
appears (see Figure 3-16)
56
3-6.4. PAIS
To install the driver for a third party clearing system, proceed as follows:
1. Click on the PAIS navigation button. The OrCU Install PAIS screen appears (see
Figure 3-17)
57
58
59
SECTION 4
SETUP WIZARD
4-1. GENERAL
The Setup Wizard helps the technician to set up the station, guiding the user through the process
and initializing most of the system's setup parameters automatically. Once the Wizard is finished,
most standard stations are ready for fueling and no additional settings are required.
The wizard also allows selection of predefined templates for fully configuring the system according
to stations with similar characteristics. If a predefined template is selected, the wizard consists of
pages that contain specific station data only.
After the Wizard is finished, the Main Setup screen is displayed, enabling the user to complete the
process, or to change to the Advanced Mode in order to define more complex forecourt
configurations.
Rerunning of the wizard is allowed; however, the existing setup data is overwritten (fuelling data
such as transactions are not deleted). In such cases, the user is provided with a proper warning.
The Cancel button in each screen enables the user to cancel the process and return to the main
Setup window. In this case, no data is saved, and no changes are made to the system. The user is
alerted that all changes are lost if the process is cancelled in the middle.
In cases where the configuration is done without the wizard, the logic of the setup procedure should
be from top to bottom. That is, first define the physical configuration: Station Parameters, Alarms
and Communication (FCC) channels, etc. Once these parameters have been set, define the Setup
parameters. This Setup includes first the buses or communication channels, then the definition of
peripherals such as printers and tag readers. Setting the system in this order ensures the definition of
all the existing building blocks for each component.
NOTE
In cases where the Wizard is rerun after settings
were changed from SiteOmat Setup screens, the
Wizard may not reflect the changes made (i.e.
settings not supported by the Wizard).
60
61
62
63
64
65
66
67
Also, the user can define if a printer is available for each selected pedestal.
NOTES
The system supports a maximum of ten peripherals.
If a higher number is entered, the text box is marked
in red and the Wizard displays the following error
notification: Controller numbers cannot exceed
10.
68
69
70
71
72
73
c. Product (selected from the drop-down list including all products previously defined)
d. Capacity (must be higher than zero)
e. TLG Tank Number (by default is equal to the tank number, must be less than or equal to 16)
4. Edit the required fields
5. Click Next to continue
74
75
NOTES
Pumps with identical Head number cannot be
connected to the same Cluster (IP and Port) on an 8Port Module Card.
4. Select the OrPT terminal to be linked to the pump for prompts display from the Connected
to OrPT drop-down list (This setting is optional, the Wizard displays a warning notification
in cases where not all pumps were connected to an OrPT but does generate a validation
error)
5. Set the pump to the Tank the pump is actually connected to (Mandatory setting, if not set
the Wizard displays the following error notification: Select tank for all pumps)
6. Select the Product from the drop down list containing all products in use as defined on Page
5. This field is auto-populated based on tank selection
7. Select the Rate, namely the number of pulses per Liter/Gallon as required for mechanic
pumps setup only, using the drop-down list (10,100,1000)
8. Enter the F.P. Plus logical channel for communication with the controller (if F.P. Plus is in
use, as defined on page 4). Enter a different channel (between 1 and 16) for each pump. The
Wizard provides the user with the following error notifications in cases where an incorrect
value was entered:
a. VIS Channel must be less than 16
b. You connected same VIS channel to two pumps
9. For pumps that support Satellite linked nozzles (two nozzles connected to the same pump
head allowing simultaneous refuel from both sides of a truck), enter the second nozzle F.P.
Plus channel (between 1 and 16 and not previously used)
10. Click Next to continue
NOTE
The Setup Wizard supports one-grade dispensers
only. For other configurations, run the Wizard and
then set up the nozzles on the Main Setup screen
(refer to paragraph 4-5).
76
Tasks
App Log
Comm Log
Timeout
Prevents refueling with the same bank card within the selected
77
within
time frame
Pre-authorized amount
End of Day
Product Map
78
79
80
81
82
83
84
85
86
192.168.x.x
Table 4-2 lists the IP addresses for the internal devices in the Controller.
87
Default IP Address
Starting IP
Address
Ending IP
Address
TCP Ports
OrCU LAN1
(FCC)
192.168.1.104
192.168.1.104
8 Port
CommVerter
192.168.1.111
192.168.1.111
192.168.1.130
3001-3008
WGT Master
192.168.1.170
192.168.1.170
N/A
N/A
WGT
192.168.1.171
192.168.1.171
192.168.1.190
3001-3008
OrPT
192.168.1.211
192.168.1.211
192.168.1.230
3000
Receipt Printer
192.168.1.211
192.168.1.211
192.168.1.230
3485
8 Port Commverters are available on the Main Controller, Extension Boxes and ICR PLUS units
with Pump Controllers.
The Wizard allocates IP addresses first to Extension Boxes and then to ICR PLUS units. A
maximum of 10 peripheral controllers can be defined by the Wizard. In cases where more than
one peripheral is in use, configure the peripherals' IP (Extension Box and ICR PLUS factory set
default IP is 192.168.1.212).
For further details, please refer to 8-Port Commverter Operation and Installation Manual, P/N
MDE-4820.
NOTE
Cluster port allocation for Extension Boxes and ICR
PLUS pedestals is identical to 4-Mechanical
Dispensers Islander PLUS defaults.
88
all the pumps of the same type and populates the clusters. Then the Wizard continues to the next
defined pump type and uses the next available port to define the new cluster.
Table 4-3 lists the number of pumps per cluster and the default factors settings for common
electronic pump models.
NOTE
Mechanical Pump Interface cards support a
maximum of two (2) pumps per cluster.
89
Pump type
Wayne Dart
100
100
100
100
100
100
100
Gilbarco
1000
100
100
100
100
100
100
Midco
100
100
100
100
100
100
100
Tokheim
100
100
100
100
100
100
100
Nouvo
Pignone
100
100
100
100
100
100
100
L&T Zline
100
1000
1000
100
1000
100
100
Aplab
100
100
100
100
100
100
100
Wayne
Vista
100
1000
1000
100
1000
100
100
Tatsuno
100
100
100
100
100
100
100
L&T QPD +
MPD
100
1000
1000
100
1000
100
100
Mechanical
Pump
1000
100
100
100
100
100
100
Fuel Star
100
100
100
100
100
100
100
Shlumberger 2
100
100
100
100
100
100
100
Petrotec
CEM03
100
100
100
100
100
10
Mechanical
Pump - Card 2
1000
100
100
100
100
100
100
Bennett
USA
100
100
100
100
100
100
100
Gasboy
100
100
100
100
100
100
100
Orpak PIR
100
100
100
1000
100
100
100
Cetil
(EAS1)
100
100
100
100
100
100
100
Cetil (ER3)
100
100
100
100
100
100
100
Pumalan
100
100
100
100
100
100
100
Mepsan
100
100
100
100
100
100
100
Coptron
100
100
100
100
100
100
100
L&T Sprint
100
1000
1000
100
1000
100
100
Tokheim
100
100
100
100
100
100
100
90
Kaizen
4-6.4. TLG Settings
An external TLG (Tank Level Gauging) can be defined by the Wizard. The Wizard allows setting
of a TLG system controlling up to 16 probes (numbered 1 to 16), where a single probe is connected
to each tank (manifold tanks cannot be defined by the Wizard).
If serial communication between the TLG console and the Controller is selected, the TLG is
allocated on Main 8Port: 192.168.1.111 port 3005.
NOTE
8-Mechanical Dispensers Islander PLUS pedestals
do not support connection to external TLG consoles.
4-6.5. Naming Conventions
The following naming conventions are used by the Wizard when defining communication channels
and system peripherals:
a. All buses' names begin with BUS_
b. The name of the buses on 8Port Commverters of peripheral controllers (Extension Box/ICR
PLUS), which are used only for interfacing pumps, begins with BUS_[ps name]
c. OrPTs naming is ORPT_[type]_[number], where:
[type] is the type of the controller, i.e. ICRW stands for ICR PLUS with Pump
Controller, ICR stands for ICR PLUS without Pump Controller
[number] matches the setup sequence as shown to the user on Page 3 of the Wizard
d. The name of a Printer is identical to the one of the OrPT to which it is connected, with the
addition of the suffix _Printer (Main printer is named Printer)
4-6.6. Cluster Log Port Conventions
The following convention is used by the wizard when defining unique log ports per cluster on
OrCU IP:
9000+100+10+Cluster for Main Controller
9000+200+10*Extension No. + Cluster for Extension Boxes
9000+300+10*ICR PLUS No. + Cluster for ICR PLUS with Pump Controller
NOTE
For further information, please refer to paragraph 84.
91
92
SECTION 5
SPECIFIC PARAMETER SETTINGS
5-1. GENERAL
This section provides instructions for setting specific parameters required for completing the station
setup process. The section describes several processes:
Adding, removing and changing the properties of the users in the SiteOmat, and specifying
the content that can be viewed by each user, according to his access level
93
94
95
5-2.1. Login
To login to the system, enter the default user name and password (see Figure 5-3).
96
1. Enter the User Management window (seen in Figure 5-2) by clicking the
Administration button in the Navigation Bar, providing that the user has an
Administrator access level
2. Select the General tab
3. In the User login name text box, enter a username. A user must be given a unique login
name and it must be at least 4 characters long
4. In the User Password text box, enter a password, which the user must enter in every
login. The password must be at least 6 characters long
5. Type the password again in the Confirm Password box for confirmation
NOTE
The password cannot be recovered if forgotten.
6. Select the appropriate Group. The content available to this user depends on the user's
Group. Refer to paragraph 5-3 for access level groups
7. Click on the OK button
97
98
Access Rights
Administrator
The Admin access level is meant for the system developers and administrative
staff. Users with Admin access level have access to all data, including setup
screens, user management and model design.
External User
The External access level enables the users to view SiteOmat custom reports and
status only.
Station
Manager
The Station Manager access level provides all privileges not including setup and
Admin.
Station
Administrator
The Station Administrator access level provides all privileges not including
setup. The user cannot add an Admin group user.
HO
Communicator
Administrator
Translator
This access level is intended to enable the user to modify the translation of the
GUI into the language previously set on the first Page of the Setup Wizard (refer
to paragraph 4-4.1) or on the Global Parameters screen (refer to paragraph 6-2).
For further information on this feature, please see paragraph 6-9
99
100
Description
If this option is selected, the system forces all users to modify their
password on first login
Password must
contain at lest one
numeric character
Password must
contain at least one
special character
If this option is selected, passwords must contain at least one upper case
letter and one lower case letter
Minimum password
length
Defines the least number of characters that a password for a user account
may contain
Password history
Minimum user ID
length
Defines the least number of characters that a User ID for a user account
may contain
If this option is selected, the system forces the user to change the
password after the defined time interval has elapsed. The time interval is
measured from the last time the password was changed
Force
By clicking this button, the system forces all users to modify their
password on the next login
101
5-5.
REGISTRATION
The registration screen is intended for registration of the Wireless Programmer system which is part
of the FuelPoint PLUS solution (see Figure 5-7).
The installer establishes appropriate communication between the Programmer and the SiteOmat to
allow flow of data between the vehicles' installed units and the FCC.
NOTE
If running an FHO, registration should be performed
in the FHO. It is highly recommended to run
FuelPoint PLUS with Fleet Head Office.
Setting up of the home based systems requires the installer to conduct three phases as follows:
1. Installing the Wireless Programmer Tunnel S/W
2. Setting up communication between the Programmer and the FCC
3. Programming and configuring the vehicle units
For more details see Fuel Point PLUS Installation and Configuration Manual for home base P/N
MDE-4851.
102
103
5-6.1.
Price Lists
5-6.1.1. General
Fleets, departments and devices can be associated to a particular price list. Price lists are derived
from the base price defined for each product.
While refueling and after identification, the driver sees the specific price linked to the device on the
dispenser (on dispensers supporting price display). The price changes back to base price right after
the transaction is completed and the nozzle is placed back on the dispenser.
NOTE
Price lists can only be associated to hand held
devices.
If a driver lifts the nozzle first and then presents the
card/tag/key, he's notified and the process is stopped.
The transaction is not authorized in the following cases:
a. A device linked to a price list is recognized, but the pump price update has failed
b. A driver using a device linked to a price doesn't return the nozzle back to dispenser,
and consequently the system doesn't update the pump back to the base price
5-6.1.2. Setup
Departments and devices automatically inherit the fleet's price list; the association may still be
overridden by assigning departments or devices different price lists or none.
To define special discount lists, click on the Price Lists button. The Wet Price Lists dialog box
appears (see Figure 5-9).
104
105
106
SECTION 6
ADVANCED SETUP PROCEDURES GLOBAL PARAMETERS
6-1. GENERAL
This section provides instructions for configuring the main functional features of the SiteOmat
global parameters.
These configuration procedures consist of:
Station parameters
Communication definition
107
108
Parameter
Station Section
Description
Address
Code
Language
City
Date Format
Volume Measurement
Currency Measurement
Density
Height (measurement)
Flow Rate
Volume of fuel which passes per unit time (default: gallons per
hour).
Time Format
Odometer Consumption
EH Consumption
109
Temperature
Height (display)
VAT (percent)
Sets the time the OrPT displays the same message when waiting for
the user's input.
Department Color
Zero transactions
Authorization Timeout
These fields are in use in stations are not applicable to Home Base
stations and their default should not be changed.
110
Description
Configure Screen
Formats
Sets the display of the decimal point precision for currency, PPV
(Price Per Volume), volume, density and height values used in
reports and printed on receipts.
Payment Terminal
Auto Calibration
Schedules the daily check for auto calibration completion for all
probes actively executing the process ( by using the Time to check
if done drop-down (HH:MM)
111
Shift Details
General
112
changes
d. Enable manual totalizers: Select this checkbox to
manually enter mechanic pump totalizers. Please refer to
Section 6-7. of MDE 4818.
e. Card number automatically generated: Select this
checkbox to enable Card Numbers generation for not burned
devices. The vehicle is identified by its plate number and
automatically receives a device number after the first
refueling
f. Allow auto authorize pump from OrPT: Select this
checkbox to allow Shift Managers to switch the pump
operation modes from Need Authorize to Auto-Authorize
mode through ORPT
g. Record Fuel Start Flow Time: Select this checkbox to
include in transaction record the time stamp when the pump
started to supply fuel, namely changed to IN_USE state
TLG Update Intervals
Discovery Mode
OrPT Beeps
113
Click Modify to save the selections and Close to close the dialog box and return to the Global tab;
or click Close to exit the dialog box without saving the changes.
6-3.1. Open Door Detection
The FFC includes a feature for preventing unauthorized third parties from forcing the sealed FCC
box door.
The FCC generates an alarm in cases where the door was opened: "The door is open".
The function setup procedure comprehends:
a. Physical installation and setup of the detector (described in 8-Port Commverter
Operation and Installation Manual MDE-4820)
b. Feature activation in SiteOmat, as described below:
To activate open door detection, select the Enabled checkbox and set the detector's IP and Port as
defined in the 8-Port Commverter.
6-3.2. Payment Terminal Setup
To set the SiteOmat connection to a third party clearing system, click on the Setup button in the
Payment Terminal section in the Station Parameters screen. The Setup PAIS dialog box appears
(see Figure 6-3).
The various parameters are described in Table 6-3.
114
Description
Tasks
App Log
Comm Log
Timeout
Prevents refueling with the same bank card within the selected
time frame
Pre-authorized amount
End of Day
Credit Processor
Enable Log
Product Map
115
116
Description
Change Logo
Enables loading a PCX file for a logo printout at the top of the
receipt. The logo should be a monochrome (black and white)
PCX file, with a maximum size of 1 KB.
Header/Footer
Full Cut
Enter the time limit for storing the receipt in the system
memory, for tag transactions. If within this time the attendant
presents his tag, the receipt is printed automatically.
117
118
To remove a field from the report, click on the row in the right hand side grid and then click
Remove.
To remove a format from the system, select the format form the drop-down and then click Delete.
Description
Attendant
Credit Card
Customer ID
Driver Name
Dry PPU
Dry Price
Dry Quantity
Duplicate Number
Empty Line
Engine Hours
Fleet Code
Fleet Name
Hose
Night Charge
Nozzle
Odometer
PPV
Paymode
Product Name
Pump
Receipt ID
Reference Number
Signature
Terminal
119
Description
Total Price
Transaction Date
Transaction Driver
ID
ID of the driver
Transaction Time
VAT
Vehicle No.
Volume/Quantity
Wetsale
Description
Empty/Default
Float (%f)
Float 0-pad
(%0*.*f)
Integer (%d)
Decimal numbers
Hex (%x)
Hexadecimal numbers
Int/ 0-pad
Hex/ 0-pad
Int/exact/0-pad
Hex/exact/0-pad
Int/ 0-pad/LJ
Hex/ 0-pad/LJ
String (%s)
Alphanumeric characters
Right Part of String Right characters in the string, according out to the required
width
120
Description
Date Formats
Available formats:
YYYY-MM-DD
YYYYMMDD
DD-MM-YYYY
MM-DD-YYYY
DD/MM/YYYY
MM/DD/YYYY
DD/MM/YY
MM/DD/YY
DDMMYYYY
MMDDYYY
Time Formats
Available formats:
hh:mm:ss
hhmmss
hh:mm
hhmm
Click Save to save the settings and Close to exit the dialog box and return to the Global tab; or click
Close to exit the dialog box without saving the changes.
121
6-5. ALARMS
Click on the Alarms button to display the Alarms setup screen (see Figure 6-7), which enables users
to define the alarm attributes. The types of alarms are predetermined in the system, and they are
listed in the Alarm Code column by ascending number. The administrator can only change their
attributes.
To change an alarm attributes, first select the alarm by clicking on the corresponding row. The
selected alarm attributes are shown in the selection boxes (along with its name in the left box). Set
the attributes from drop-down lists:
Click Update to enter the selections. Verify that the new attributes are displayed in the alarms
corresponding row.
Click Close to exit the dialog box and return to the Station Parameters screen.
122
123
Description
Provides communication attributes of the Controller.
FCC IP: Identifies the IP address of the Controller in the network for view
only. The connection is identified at the FCC Port box (LAN1 or LAN2)
and the Control Port box.
Maintenance time: Sets the time of the day, Hours and Minutes after
midnight, at which the SiteOmat performs clean up operations of the
database and other activities. The duration of the maintenance procedure
depends on the workload of the OrCU, which is the number of transactions
not passed to Head Office. This process may take a few minutes, during
which the system may experience a delay in authorizing and other
operations. Therefore, it is highly recommended to select a time where no
activity or minor activity is expected in the station. Default procedure time
is five minutes after midnight.
Maximum transactions: Sets the Controller's transactions capacity
Delete transactions older than: Enables overriding of transactions in
FIFO method if transactions number is over the maximum set
Connected to HO: Deletes transactions only after data was transferred to
HO (in cases where overriding is selected)
Keep data for: Sets the time limit for storing the transactions. This field
enables users to delay the clean up, as it may be required for obtaining
local reports (request available data from the last days)
Communication
This section is set in cases where the Head Office is implemented. The
Trigger requires a message from the OrCU, through Web Services, to
activate the Head Office and update the OrCU. The feature is disabled by
default. As these are very specific settings, additional information is
provided for developers of Head Office on demand.
Remote
Authorization
This section is set in cases where the Head Office application provides
Web Services in a predefined format for authentication. Specific settings
are provided for these applications only.
Log Server
124
125
6-7. BACKUP
Click on the Backup button to display the Setup Backup screen (see Figure 6-9), which enables
users to define the database backup.
Backup can be enabled by clicking on the Enable automatic backup of database checkbox, or
disabled by leaving it blank.
126
127
128
SECTION 7
ADVANCED SETUP PROCEDURES - FORECOURT
7-1. GENERAL
This section provides the setup instructions for forecourt Controller peripherals and devices. The
setup process should be performed in the following order:
Buses
Printers
OrPT
Tag Readers
TLG (optional)
Tanks
VIS/FuelPoint PLUS (optional)
Pump Servers
Dispensers (main screen)
Use the Save and Reload button to finalize the setup.
Once all the definitions have been inserted, the setup process shall be implemented in the system
by clicking on Save and then Reload.
129
130
7-3. BUSES
7-3.1. General
To open the Buses dialog box (see Figure 7-2), select the Buses tab in the setup screen.
This screen displays the communication channels to the peripheral devices in use in the controller.
Regularly, these are TCP/IP buses in use in the 8-port CommVerter for communication with pumps
and RS-485 linked devices.
In this screen, define buses to a list of available communication protocols (New procedure) or
update the link (Modify procedure). Figure 2-2 describes the setup of communication Buses. For
example, an OrPT with IP address 192.168.1.211 and port 3000 is connected to the SiteOmat,
requires defining an OrPT Bus channel identified by IP and port 192.168.1.211:3000.
When defining an OrPT device in SiteOmat, that OrPT is bound to the pre-defined OrPT Bus.
In the example below (see Table 7-1), each OrPT device is linked to a dedicated Bus channel. The
TLG console is bound to a dedicated Bus channel, and the dispensers (pumps) to another dedicated
Bus channel.
Table 7-1. Bus Definition Example
Device
OrPT1
IP #
192.168.1.211
Port
3000
OrPT2
192.168.1.212
3000
Printer1
192.168.1.211
3485
Printer2
192.168.1.212
3485
TLG
192.168.1.111
3005
127.0.0.1
2502
WGT
192.168.1.170
3000
MPI-C
127.0.0.1
2501
Pump Server
The pump server is an internal process in the OrCU, Therefore, the bus IP should be 127.0.0.1
(localhost).
When defining a communication BUS channel, it is recommended to have a convention of buses
names (related to the device name). Each bus name should have a unique name and continue with
the target device name, as shown in Figure 7-2. For further explanation see MDE 4820.
131
Devices
Orpak
Printer, OrPT, uVIT, WGT, Journal Printer, OrTR, UPI, My tag reader
Pump Server
Pump server
Hectronic
Hectronic TLG
Veeder-Root
NOTE
Devices cannot be connected to a bus with a frame
incompatible to the device frame. For example, a
Pump server device cannot be connected to an
Orpak frame.
132
Next, verify that the TCP/IP radio button is selected, and enter the IP address and connection Port
for the selected bus, refer to Table 2-1 for IP address convention. Note that when configuring a
PumpServer IP address and port, they refer to the communication between the SiteOmat and the
PumpServer and not the communication between the PumpServer and the target pump connected
through an 8 port CommVerter port. This Bus communication is referred to as "localhost" and uses
the IP address 127.0.0.1 and a unique port number starting with 2501 and ending with 2509.
Serial (485): In asynchronous communication to peripheral devices, the following communication
parameters should be defined:
NOTE
The serial port is currently in use for TLG
connection only.
Serial COM: The physical connection to the controller. Currently only COM2 for the TLG
direct connection to the OrCU serial port RS232 is supported
The parameters below should be configured according to the serial device parameters:
Parity: Sets the parity of transmitted data for the purpose of error detection (NONE, ODD or
EVEN)
Clear host "read buffer" on connect: Select this checkbox to reset external devices (i.e. TLG)
communication buffer whenever the communication with the device is established.
Throughout the setup procedures, users are required to link a device to its bus from a drop-down list
(for example, see Figure 7-3). If the bus is not yet defined, an ellipsis () selection button is
available at the right. Click on this button to return to the Buses setup screen and define a new bus
for the device.
133
7-4. PRINTERS
To open the Printers dialog box (see Figure 7-4), select the Printers tab in the Setup screen.
A Printer definition is simple, requiring only a bus and an RS-485 address.
To define a printer, type its Name, then select its Bus. All printers supported in SiteOmat
communicate in Orpak frame, therefore the Bus selection is restricted.
The following printer Models are available: Pump printer and OrPT printer, both used for receipts.
and journal printer used for journaling important operations such as all transactions on hard copy.
Next, define its Hex Address in the appropriate box. Default is 70 for Pump printer and OrPT
printer, and 1 for Journal Printer refer to Table 2-2.
NOTE
Journal Printer is connected to the 8-Port
Commverter by way of an RS-485 Module. Set a
dedicated bus for the printer, with the corresponding
Port.
Click New or Modify (for update procedure) to enter the selection in the upper Printers list.
Automatically print receipts without opening door This option is not relevant for Islander
PLUS.
134
7-5. ORPT
7-5.1. General
To open the OrPT dialog box (see Figure 7-5), select the OrPT tab in the Setup screen.
The OrPT definition has several options. First, it requires a bus and an RS-485 addresses. Then,
additional features can be defined.
To define an OrPT, type its Name, then select its Bus. All OrPT supported in SiteOmat
communicate in Orpak frame, therefore the Bus selection is restricted.
Model field is not applicable and is disabled.
Next, define its Hex Address in the appropriate box. Refer to Table 2-2.
135
136
Orpak Tag Reader (OrTR): MiTag tags reading device, including an LCD screen
Next, define its Hex Address in the appropriate box. Refer to Table 2-2 for the serial address of the
Tag Readers.
Select the Association Model checkbox to use the Tag Reader for reading tag strings that define a
Fleet. This setup is necessary for Fleet Management. In this mode, the Tag Reader serves for fleet
authorization, and cannot be used for fuelling authorization.
Click New or Modify (for update procedure) to enter the selection in the upper Tag Reader list.
Click Close to exit from the Tag Reader screen and return to the Setup screen.
137
Veeder-Root TLS 350 and 450 (For all TLG systems using VR TLS protocol)
OPW
Hectronic
Start Italiana
Leak Detection: Select this checkbox to use the Leak Detection mechanism in an external TLG.
Password: The TLG password used for communication between SiteOmat and the TLG.
7-7.2. Probes
Once the TLG is defined, users are required to define the TLG physical probes. Click on the Probes
button. The Probes dialog box appears (see Figure 7-9).
Enter an address for each probe. Each probe must have an address that should match the address
defined in the TLG.
138
Next define the volume Capacity of the tank that the probe is controlling. The volume is set in
Liters/Gallons.
The Water Offset and Fuel Offset fields enable users to initialize the system when utilizing Start
Italiana probes, setting the actual height of water and fuel. For example, if a tank is empty and the
probe reads 3 cm. of water, enter the received reading to the Water Offset text box. The Controller
compensates the value.
The following parameters are required for the auto calibration process:
a. Diameter: Diameter of the tank
b. Min. level for calibration done alarm: Minimum low volume level to be covered
required for auto-calibration completion, set in percentage of tank capacity
c. Max . level for calibration done alarm: Minimum high volume level to be covered
required for auto-calibration completion, set in percentage of tank capacity
NOTE
In addition to coverage parameters, the auto
calibration is completed if the following condition is
met:
Maximum volume difference between two sampling
points should not be higher than the tank capacity
divided by the number of points required for the
specific TLG.
Since the system checks for Auto Calibration completion on a daily base, the alarm is
generated again each day until auto calibration is stopped for this probe (OFF).
d. Camber Radius: Radius of the tank cambers
e. Tank length: Length of the tank from side to side, not including cambers
f. Is divide: Select this checkbox if the tank has 2 compartments
139
140
The Strapping Files dialog box appears (see Figure 7-11), enabling users to browse the system for
the compatible CSV file.
141
142
143
144
145
c. Send to Device: Sends the strapping table to the TLG. It is highly recommended to inspect
the results and then update the device.
d. Refresh: Updates the data displayed on the screen
e. Graphs: See paragraph 7-7.5.1
f. Settings: Defines advanced setting parameters
g. Close: Closes the dialog box
146
147
7-8.3. Products
7-8.3.1. General
Before proceeding further in the tank setup, define the products. Click on the Ellipsis () button
next to the Fuel Type drop-down in the Tank Properties section. The Setup Fuel Products dialog
box appears (see Figure 7-19).
149
150
151
152
153
154
155
Description
Pump Communication:
Comm (FCC)
Communication:
Application:
By setting the ports the logs could be monitored with a Telnet terminal without enabling the logs.
156
NOTE
Since the OrCU has limited memory size, logs
should be enabled only if needed. Only Gasboy
certified technicians should enable this feature, in
response to a specific request.
Clusters bundle several pumps to a pump server via a common physical link. The physical link is a
port in the 8-port CommVerter, physically linked to the pump.
Ports are usually defined with TCP/IP parameters: 8-Port Commverter IP and Port (3001 to 3008)
Refer to Figure 2-2 and Figure 2-3 for examples of address configurations.
For IFSF pumps, define Serial connection parameters. The pump is connected directly to OrCU
COM2 port through serial to LON converter.
The Timeout box defines the waiting time for response from the pump. It is recommended to enter a
value in the range of 250 to 300 milliseconds.
Click on the Enable Echo checkbox to enable echo communication in the link with the pump (this
feature is applicable in specific cases, Refer to the separate pump list provided).
Define the Log Port for shipping the communication logs between the Pumps in the cluster and the
Pump Server.
NOTE
Please refer to MDE-4820 section 2.3 for additional
information on pump setup data.
7-10.3. Finalizing the Settings in the Pump Servers Screen
Once all the parameters have been defined, proceed as follows to insert the definitions:
1. Click New or Modify (in an update procedure) to return to the Setup Pump Servers dialog
box
2. Click New or Modify (in an update procedure) to return to the Setup screen
7-11. DISPENSERS
7-11.1. General
The Setup Pump Settings dialog box (see Figure 7-26) enables users to define the dispensers linked
to the Controller. To define a new pump, click the Add Pump button on the Advanced Settings
screen and fill the corresponding parameters in the General section of the screen, described in
Table 7-4.
157
Description
Pump Number
Identification number of the pump. The logical number defining the pumps.
Pump Head
Number of nozzles
Mode
Pump Server
158
Select the Pump Server from the drop down list, or click on the ellipsis ()
button to open the Pump Server dialog box (see paragraph 7-10).
Cluster
According to the selected Pump Server, select the cluster from the dropdown list (see paragraph 7-10.2).
Printer
Select the Printer to be linked to the pump from the drop-down list, or click
on the ellipsis () button to open the Printer dialog box (see paragraph 7-4).
Reader
Select the device Reader to be linked to the pump from the drop-down list,
or click on the ellipsis () button to open the Reader dialog box (see
paragraph 7-6).
OrPT
Select the OrPT terminal to be linked to the pump for prompts display from
the drop-down list, or click on the ellipsis () button to open the OrPT
dialog box (see paragraph 7-5).
This association applies for this function only; the terminal can serve and be
linked to several pumps in the station.
Description
Volume
Totalizer Volume
Preset Volume
Amount
Totalizer Amount
Preset Amount
7-11.3. Specific
Each dispenser type has specific parameters that need to be defined in this section.
159
Description
Default
Nozzle Polarity
Normal
Pulse Factor
Pulser Type
Virtual In Use
Single/Dual Valve
Mode
Flow Protection
timeout (Seconds)
60
Additional Flow
Protection timeout
(Seconds)
Maximum volume
rate per minute
160
Description
Default
0.5
Description
Use of five/six positions protocol
Default
No
161
Skip authorize
response?
No
Flow protection
timeout
Pump of a single
type?
No
Supports preset
money?
Yes
Description
Defines the pump calculator in use
Default
-
162
163
Description
Grade Type
Defines the nozzle state for authorization. This parameter selection must
match the fueling Method defined in the main Dispensers screen. The
default (Must always be lifted before authorization) should not be changed
for common dispensers.
Price Update
Policy
Allows defining when a new price is set at the pump. These selections are:
164
Do not allow fuelling if the price update did not succeed, as soon as
the new price is entered or after a number of retries for the update
that failed. Accordingly, set the Number of retries.
Update the price if the Price Per Volume (PPV) in the current
SiteOmat Setup and Maintenance Manual MDE 4817G
Flow Rate
Verifies that the flow is not larger than x gallons/litters per minute for
mechanical pumps only. The default is disabled and the flow rate is defined
as zero. In cases where the option is enabled and the flow exceeds the
predetermined value (i.e. actual flow is 100 gallon/min, defined flow rate is
60 gallon/min) the controller stops the fueling.
Authorization
Parameters
Defines the Number of Retries allowed to the customer and the maximum
delay between retries before the pump shuts off for the customer. Users
can also Force a pump check of its authorization definitions by defining its
rate in seconds.
External EFT
165
166
CAUTION
All the existing settings and data in the SiteOmat is
erased and replaced. This procedure is intended only
for a new station at the setup stage, or for a restored
system.
1. Click on the Import button in the Setup screen. A confirmation message is displayed (see
Figure 7-30).
2. Click OK. The Setup Import dialog box appears (see Figure 7-31), enabling users to browse
the system for the compatible xml file.
167
NOTE
It is highly recommended to export the setup data at
this stage. Save the data as a recovery backup file.
A processing message appears, displaying the various steps of the configuration procedure starting
from clearing the existing setup and ending with writing INI files for the pump server (see
Figure 7-32).
168
169
Figure 7-34. Defining a Virtual Pump - Pump Server Settings Dialog Box
3. Add a new pump (refer to paragraph 7-11). In the Setup Pump Settings dialog box, select
the Auto Authorize Mode, Enable Virtual In Use and set Flow Protection Timeout to 60
seconds, as shown in Figure 7-35
170
Figure 7-35. Defining a Virtual Pump Setup Pump Settings Dialog Box
The pump is always in "In Use" state (see Figure 7-36). When the system detects pulses, it
immediately starts to count. If no pulses are detected, the system waits 60 seconds to close the
zero transaction and automatically initiate a new transaction.
171
SECTION 8
MAINTENANCE
8-1. OVERVIEW
NOTE
This section contains instructions for advanced users
only.
The hardware platform to run SiteOmat is OrCU, it runs an embedded Linux Operating system.
The files systems is composed of two parts
To setup the system in a network or adjust the time, users need to use a special Web server on port
8090 as described in section 3.
The SiteOmat software is divided into two modules, each runs as a separate process inside the
OrCU box. The existence of two modules is important to understand log file names and database
locations in the OrCU file system:
FCC This module is responsible for all communication to the forecourt devices. It
controls, via pump server, pumps, authorize transactions and record them to the database
BOS Back Office management module is responsible for all interfaces to the outside
world. This includes browsing to the SiteOmat for setup, configuration and reports. It is also
the module that communicates with Head Office.
In addition to the FCC & BOS a watchdog process called fccloader is responsible for starting all
other processes, including pump servers. The watchdog verifies that all processes are running and
reruns them if needed. The fccloader is also responsible for updating the hardware watchdog. If the
fccloader fails for any reason, the hardware watchdog resets the OrCU (power) in ~2 seconds.
172
Putty PuTTY is a free implementation of Telnet and SSH for Win32 and Unix platforms,
along with an xterm terminal emulator
Putty should be used by advanced technician only
Download link: http://www.chiark.greenend.org.uk/~sgtatham/putty/
LogServer: Log server is a small Windows utility that is used as a server to collect
messages coming from stations. When a station is defined to use the log server each log line
is sent using the UDP protocol to the designated IP and port where the log server application
is running. The UDP messages are sent regardless of whether the log server runs or not. No
verification is made. The incoming log lines are reassembled to log files and placed in a sub
folder named as the originating IP. One log server can handle several stations
173
LogRotate: This utility enables the delimitation of logs by opening and closing the logger at
a predefined time, creating an accurate single log file per day.
In order to configure the LogRotate utility, proceed as follows:
1. Copy the content of the provided file logrotate.rar to C:\Orpak\logrotate
2. Open a command line and execute (see Figure 8-2) :
FileZilla: Free FTP application. Both a client and a server are available. FileZilla is an open
source software distributed free of charge under the terms of the GNU General Public
License
Download link: http://filezilla-project.org/
Telnet (cmd): Telnet at command line is a client software which can be used for connecting
to the FCC Monitor utility
Open the command line in a PC connected to the SiteOmat and execute the command: telnet
IP_ADDRESS 6000 (e.g. telnet 192.168.1.104 6000)
174
WinTail: Allows users to view the last 64K of a growing text file in real time under
Win32 operating systems
SiteOmat Setup and Maintenance Manual MDE 4817G
175
In all the cases above an Out of service message is displayed in all LCD display devices in the
station and an alarm is sent to the FHO.
8-1.3.3. Purging Old Data
SiteOmat has a configurable maintenance time. At that time of the day the database is cleaned up,
and any transaction and other data that was downloaded are deleted from the database, and the
database is compacted to free storage space.
This operation can take several minutes, depending on the amount of data that was deleted. During
the maintenance process stations can continue refueling without interferences, although transaction
processes may be slowed down.
The time defaults to 00:05, i.e. 5 minutes after midnight. This time can be altered by the user via the
Setup Comms screen (see paragraph 6-6). Users must save and reload to make changes effective.
The default definition of Keep data for is 2 days. This parameter can be modified by the user.
8-1.4. Management File Locations
8-1.4.1. /usr/local//orpak/BOS/bin
Contains various programs needed to run the management process, and some auxiliary files.
8-1.4.2. /usr/local/orpak/BOS/bin/log
This folder contains all of the BOS log files.
8-1.4.3. /usr/local/orpak/BOS/DB/patches
This folder contains the patches that are applied to upgrade to successive database versions.
8-1.4.4. /usr/local/orpak/BOS/htdocs/*
This folder and the various sub-folders under it hold the files necessary to construct and operate the
SiteOmat BOS screens.
8-1.4.5. /usr/local/orpak/BOS/reports
This folder, if exists, contains any CSV-format data files generated by the report screens ToFile
buttons.
8-1.5. FCC File Locations
On the FCC, the SiteOmat files reside in the directory /usr/local/orpak/FCC, and subdirectories.
The only location on the FCC that contains anything of interest for support purposes is
/usr/local/orpak/bin/log. This directory contains the FCC log files.
8-1.6. FCC Loader Watchdog
The FCC Loader runs a daemon on Linux\Windows and is responsible for:
Monitoring the FCC to see if its hung, and restarting it in that case
176
Performing the same operations (start-up, monitoring, and restart) for multiple pump
server processes
Log parameters
log_spec_output_dir
Common Output
Directory
String
log_stat_output_dir
String
start_up_log_name
String
log_app
String
Y/N
app_log_name
String
log_app_size
Integer
Integer
log_app_port
-1 unlimited
>0
log_spec_o
utput_dir
200000
> 1023
Unique within 'localhost'
0 not used
log_scucomm
Boolean
Y/N
scu_log_name
String
log_scucomm_size
Integer
log_scu_comm_port
Integer
Process
working
dir.
-1 unlimited
>0
> 1023
100000
0
177
[logging]
Log parameters
log
log_cluster_comm
Boolean
log_cluster_comm_size
Integer
Y/N
-1 unlimited
2000000
>0
Boolean
Y/N
Cluster parameters
Appears as many times
as total number of
clusters
[cluster_xx]
Cluster_log_name
log_cluster_port
'00' xx '99'
String
> 1023
Integer
0 not used
Aplab
Avery
Gilbarco
Midco
L&T
price_factor
100
100
100
100
volume_factor
100
100
1000
total_factor
100
100
totalizer_vol_factor
100
totalizer_money_factor
preset_volume_factor
178
NP
NP
Tatsuno
Wayne
100
100
100
100
100
100
100
100
100
100
100
100
100
1000
100
100
100
100
100
100
100
1000
100
100
100
100
100
100
100
100
1000
100
100
100
100
100
10
1000
100
100
100
100
100
100
Identical to
the volume
factor
except of
Avery
preset_amount_factor
100
100
100
1000
100
100
100
100
Identical to
the total
factor
except of
Avery
179
Description
Starts the FCC operation.
Click on the Start button to start FCC that was in stop state. Note that if
during the reload operation power failed, the FCC may be in stop state after
power is back, click Start to start communication.
Stop
Stops the operation of the FCC and all communication to peripheral devices.
After using this command, the FCC does not start until either the Start of the
Reload commands are invoked, even if the FCC computer is rebooted, it
remains in stopped state.
Reload
Sys Init
Recovery operation
Reset Pumps
Reset Pump
Sync FCC
This command must be invoked after the SysInit in the following cases:
A recovery operation
180
Activates the EOD process (Collects both tank levels and dispensers
meters.)
CAUTION
Reset Pump/s commands should only be used in
extreme cases where there are communications or
other serious state problems between the FCC and
the pump.
181
Specific Logs
In cases where the last option was selected, the following filters are available:
a. SiteOmat logs: application logs as described in Table 8-4. SiteOmat logs may also
be filtered by Log Level (see Table 8-5).
b. Web Comm Logs:
c. Database Logs:
182
NOTE
The Log Server should be used only when advised
by Orpak technical support and cannot be used for
low band networks such as dialup or GPRS.
Table 8-4. SiteOmat Logs
Log
Description
FCC System
FCC External
FCC Shift
FCC Fueling
BOS System
BOS External
Communication with HO
Level
Critical
Error
Abnormal system events causing wrong behavior (i.e. Fail to open shift,
Error write transaction to DB)
Warning
Events that do not affect system functionality but point out a problem (i.e.
Transaction already written which may indicate slowness of the system)
Information
Debugging
Trace
Very detailed debug level to be used in cases where the total flow of code
is required to analyze a problem (i.e. Enter and exit of each function)
183
NOTE
Log levels are arranged in ascending order. Any
high level automatically includes all lower levels.
184
Local management
In order to perform a DB back procedure, click Setup, select the Global tab and click on the
Backup button. The Setup Backup dialog box appears (see Figure 8-5):
185
186
# cd /usr/local/orpak/BOS
# chown R fcc:fcc *
c. FCC DB
1. Before FCC can start, it DB must be properly set do not start operating the
station and making transactions or any other operation before completing this
procedure
2. Reboot the OrCU to load all components
3. Verify that the BOS is operational and the setup looks OK (browse to the
SiteOmat)
4. From Admin menu run Sysinit
5. From Admin menu run Sync FCC - this command verifies that the FCC DB
indexes are matched
6. From Admin menu run Reload this must be the last action
187
NOTE
Log files are limited on the embedded platform.
Only critical logs are written locally, all other logs
are written on remote host using log server utility.
Both the BOS and the FCC make use of several types of log files to record information during the
running of the system.
Many annotated snippets from actual log files are included in the sections below.
When logs are disabled, logs are only written to debug.log, and with less detail.
188
O:(opos) T(tag)
or
V:(vit) T(tag)
or
M:(mitag) T(tag)
189
Then for each new authorized transaction it shows the authorization lines, when transaction is
competed it displays the TX lines, for example:
[2009-02-05 10:51:35.506 00023265] O:OrPT T8012107672337245
[2009-02-05 10:51:38.266 00023264] APS: 8012107672337245
atg=200000004||0|-1 P1 N2 L99999999.00 Tm
[2009-02-05 10:51:44.340 00023262] TX 8012107672337245 P1 N2 Q2.12 S4.24
[2009-02-05 10:51:51.506 00023265] O:OrPT T8012107672337245
[2009-02-05 10:52:32.645 00023264] APS: 0000000000000003517 atg=0|41|0|-1
P1 N2 L99999999.00 Tm
[2009-02-05 10:52:46.533 00023262] TX XXXXXXXXXXXXXXX3517 P1 N2 Q6.91
S13.82
190
8-4.5.2.1.2.
META_DATA.DB
WHERE
191
The SiteOmat only performs read operations on this database. On the FCC, META_DATA is
mostly used for OPOS messages and for density and temp compensations.
8-4.5.3. Bus Logs (BUS_xxx.log)
Bus logs show communications activities on busses.
There exists a separate log file for each bus defined in the setup configuration.
The name of the bus appears in the name of the log file so that it may be easily identified.
The log entries are in Hex format for the busses that use the Orpak protocol, and in XML format for
the busses used by the Pump Server protocol.
8-4.5.3.1.
8-4.5.3.1.1.
Examples - General
Communications Traffic & Errors
This is from the Bus log of Tag Readers showing both communication traffic and errors. Device
address 60 and 61 are not responding.
Note that in the Orpak protocol frame, the device address in the second Hex byte.
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
[2007-12-11
8-4.5.3.1.2.
11:08:30.366
11:08:32.866
11:08:32.866
11:08:32.866
11:08:32.866
11:08:32.881
11:08:32.881
11:08:35.381
11:08:35.381
11:08:35.381
11:08:35.381
11:08:35.397
11:08:35.397
11:08:37.897
11:08:37.897
11:08:37.897
11:08:37.897
11:08:37.912
11:08:37.912
11:08:40.412
11:08:40.412
11:08:40.412
11:08:40.412
11:08:40.428
11:08:40.428
11:08:42.928
11:08:42.928
11:08:42.928
11:08:42.928
11:08:42.944
11:08:42.944
11:08:45.444
11:08:45.444
11:08:45.444
00021180]
00021180]
00000880]
00000880]
00043340]
00043340]
00003848]
00003848]
00000880]
00000880]
00043340]
00043340]
00021180]
00021180]
00000880]
00000880]
00043340]
00043340]
00003848]
00003848]
00000880]
00000880]
00043340]
00043340]
00021180]
00021180]
00000880]
00000880]
00043340]
00043340]
00003848]
00003848]
00000880]
00000880]
SEND: FD 60 30 08 00 0C 17 FE
Bus: TrPr Not ready to Read at \fccBus.cpp
SEND: FD 71 30 08 01 00 9F 24 FE
RECV: FD 71 30 08 02 00 A0 2B C4 FE
SEND: FD 72 30 08 01 00 00 35 FE
RECV: FD 72 30 08 02 00 A0 D5 AA FE
SEND: FD 61 30 08 00 A9 21 FE
Bus: TrPr Not ready to Read at \fccBus.cpp
SEND: FD 71 30 08 01 00 9F 24 FE
RECV: FD 71 30 08 02 00 A0 2B C4 FE
SEND: FD 72 30 08 01 00 00 35 FE
RECV: FD 72 30 08 02 00 A0 D5 AA FE
SEND: FD 60 30 08 00 0C 17 FE
Bus: TrPr Not ready to Read at \fccBus.cpp
SEND: FD 71 30 08 01 00 9F 24 FE
RECV: FD 71 30 08 02 00 A0 2B C4 FE
SEND: FD 72 30 08 01 00 00 35 FE
RECV: FD 72 30 08 02 00 A0 D5 AA FE
SEND: FD 61 30 08 00 A9 21 FE
Bus: TrPr Not ready to Read at \fccBus.cpp
SEND: FD 71 30 08 01 00 9F 24 FE
RECV: FD 71 30 08 02 00 A0 2B C4 FE
SEND: FD 72 30 08 01 00 00 35 FE
RECV: FD 72 30 08 02 00 A0 D5 AA FE
SEND: FD 60 30 08 00 0C 17 FE
Bus: TrPr Not ready to Read at \fccBus.cpp
SEND: FD 71 30 08 01 00 9F 24 FE
RECV: FD 71 30 08 02 00 A0 2B C4 FE
SEND: FD 72 30 08 01 00 00 35 FE
RECV: FD 72 30 08 02 00 A0 D5 AA FE
SEND: FD 61 30 08 00 A9 21 FE
Bus: TrPr Not ready to Read at \fccBus.cpp
SEND: FD 71 30 08 01 00 9F 24 FE
RECV: FD 71 30 08 02 00 A0 2B C4 FE
:432
:432
:432
:432
:432
:432
If the problem is with connection to 8-port commvertor, e.g. port definition wrong or not available,
the following error maybe in the BUS log:
[2007-03-02 04:05:26.369 00011520] Connect not done rc=115 at src/fccTCPBus.cpp :98
192
8-4.5.3.1.3.
Read Error
In the case where the device may be available but not responding, in a manner that it gets data but
does not answer, the following read error would be in the BUS log:
[2007-03-02 04:07:11.259 00011520] Bus: ATG_ALL_232 Error in Read at src/fccBus.cpp :622
Disconnected pump
8-4.5.3.2.2.
Fuelling Cycle
The following log extract shows a full cycle of fuelling with pump 7. The sequence is: getting
CALL status, sending authorization, getting running progress volume and finally final payment.
[2007-12-10 18:26:30.257 00004496] RECV: <pump_status_report req_id="9" pump_num="7"
active_nozzle="1" status="idle"/> [2007-12-10 18:26:40.298 00007284] SEND: <assign_pump_price
pump_num="7" ppv_list="1,12.34;2,4.12;3,9.80;4,4.44;" req_id="1"/> [2007-12-10 18:27:04.765
00004496] RECV: <pump_status_report req_id="0" pump_num="7" active_nozzle="1" status="call"/>
[2007-12-10 18:27:04.765 00004496] SEND: <auth_req_message auth_tag="200000024||0|-1"
pump_num="7" nozzle="1" limit="0.000000" limit_type="none" />
[2007-12-10 18:27:04.781 00004496] RECV: <auth_accepted
auth_tag="200000024||0|-1"
pump_num="7"
result="0" />
[2007-12-10 18:27:04.796 00004496] RECV: <pump_status_report req_id="0" pump_num="7"
active_nozzle="1" status="ready"/> [2007-12-10 18:27:04.922 00007284] [2007-12-10 18:27:06.786
00004496] RECV: <pump_status_report req_id="0" pump_num="7" active_nozzle="1" status="inuse"/>
[2007-12-10 18:27:06.817 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.000"
sale="000000.00"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:07.146 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.019"
sale="000000.23"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:07.475 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.042"
sale="000000.51"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:07.788 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.062"
sale="000000.76"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:08.117 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.083"
sale="000001.02"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:08.430 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.103"
sale="000001.27"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:08.759 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.124"
sale="000001.53"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:09.073 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.143"
sale="000001.76"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:09.417 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.162"
sale="000001.99"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:09.746 00004496] RECV: <progress_payment_report
req_id="0"
pump_num="7"
nozzle="1"
volume="00000.185"
sale="000002.28"
trx_seq_no="553"
result="0"
/>
[2007-12-10 18:27:09.950 00004496] RECV: <pump_status_report req_id="0" pump_num="7"
active_nozzle="0" status="payable"/>
[2007-12-10 18:27:09.997 00004496] RECV: <final_payment_data_report
req_id="0"
auth_tag="200000024||0|-1"
pump_num="7"
nozzle="1"
product_id="0"
volume="00000.201"
sale="000002.48"
ppv="0012.34" time_and_date="2007/12/10 18:27:09"
trx_seq_no="553"
result="0" />
[2007-12-10 18:27:11.015 00006336] SEND: <clear_pump req_id ="200000022" pump_num="7"
trx_seq_no="553" /> [2007-12-10 18:27:11.031 00004496] RECV: <pump_status_report req_id="0"
pump_num="7" active_nozzle="0" status="idle"/> [2007-12-10 18:27:24.737 00007284] SEND:
<assign_pump_price pump_num="7" ppv_list="1,12.34;2,4.12;3,9.80;4,4.44;" req_id="1"/>
193
8-4.5.3.2.3.
Totalizer Reads
The next example shows that at shift open or close, the FCC asks for pump totalizer values:
[2007-12-10 09:50:33.475 00047856] SEND: <get_nozzle_totalizer req_id="1" pump_num="1"
nozzle="1" modifier="0" />
[2007-12-10 11:05:19.084 00021704] RECV: <pump_total_report req_id ="1"
pump_num ="1"
nozzle="1"
modifier="0"
total_volume="00084835.71"
total_sales="00145730.92"
ppv="1.23"
result="0"
/>
8-4.5.3.2.4.
Examples
Start & Loading
194
8-4.5.5.1.2.
Normal Check
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
[2007-02-11
8-4.5.5.1.3.
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
00006930]
Nonblock conn
Pinging FCC
FCC ping OK
Nonblock conn
Pinging FCC
FCC ping OK
Nonblock conn
Error: Recv select (sock=7) rc=115: Operation now in progress
Pinging FCC
Ping to FCC failed; retry=0
Nonblock conn
Pinging FCC
FCC ping OK
Nonblock conn
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
[2007-02-08
8-4.5.5.1.4.
09:40:45.291
09:40:45.361
09:40:45.361
09:40:50.614
09:40:50.732
09:40:50.732
09:40:55.966
09:41:00.959
09:41:00.959
09:41:00.959
09:41:06.193
09:41:06.299
09:41:06.299
09:41:11.537
20:29:07.460
20:29:17.720
20:29:17.720
20:29:27.980
20:29:27.980
20:29:38.380
20:29:38.380
20:29:48.740
20:29:48.740
20:29:48.740
20:29:50.870
00025928]
00025928]
00025928]
00025928]
00025928]
00025928]
00025928]
00025928]
00025928]
00025928]
00025928]
8-4.5.5.1.5.
195
8-4.5.8.1.
8-4.5.8.1.1.
Examples
WebAcess1443.log
Examples
196
cDDzzV9A7qEFV2KDnBUo.QnUPMIAsEt08K.EwJXgwL8K9.sLRU</SessionID><Version>6.01.001</Version></SOLogi
nResult></SOLoginResponse></soap:Body></soap:Envelope>
Examples
Starting Up
197
19:40:39.531
19:40:39.687
19:40:39.687
19:40:42.156
00003376]
00003376]
00003376]
00003376]
13:17:40.780
13:17:40.780
13:17:40.782
13:17:40.793
00028060]
00028060]
00028060]
00028060]
13:17:40.793
13:17:40.793
13:17:40.793
13:17:40.793
00028060]
00028060]
00028060]
00028060]
DB service: start
DB upgrade failed: see previous messages for reason tracking
System definition not found
FCC: Initialization failed on read configuration.
00005504]
00004212]
00005084]
00000288]
00005880]
00004556]
00002676]
00002480]
00004012]
00002852]
00000944]
00003232]
8-4.5.10.1.4. Stop
[2007-12-05 07:53:14.629
[2007-12-05 07:53:16.504
[2007-12-05 07:53:16.504
[2007-12-05 07:53:16.519
[2007-12-05 07:53:16.519
[2007-12-05 07:53:16.535
[2007-12-05 07:53:16.535
[2007-12-05 07:53:16.535
[2007-12-05 07:53:16.551
[2007-12-05 07:53:16.551
[2007-12-05 07:53:16.582
[2007-12-05 07:53:16.613
Proccess IDLE
[2007-12-05 07:53:16.613
198
[2007-12-05 07:53:16.644
[2007-12-05 07:53:16.676
[2007-12-05 07:53:16.738
[2007-12-05 07:53:16.801
[2007-12-05 07:53:16.941
[2007-12-05 07:53:17.019
Proccess IDLE
[2007-12-05 07:53:17.066
[2007-12-05 07:53:17.129
[2007-12-05 07:53:17.191
[2007-12-05 07:53:17.238
Proccess IDLE
[2007-12-05 07:53:17.254
[2007-12-05 07:53:17.316
[2007-12-05 07:53:17.519
[2007-12-05 07:53:17.551
Proccess IDLE
[2007-12-05 07:53:20.691
[2007-12-05 07:53:31.785
8-4.5.10.1.5.
00002236]
00002136]
00001644]
00005804]
00001380]
00003232]
10 CPU 4: Exited.
9 CPU 3: Exited.
3 CPU 3: Exited.
7 CPU 1: Exited.
2 CPU 2 From IDLE To INACTIVE
00004900]
00004728]
00003332]
00003232]
PUMP:
PUMP:
PUMP:
PUMP:
OID
OID
OID
OID
11 CPU 5: Exited.
6 CPU 6: Exited.
2 CPU 2: Exited.
3 CPU 3 From IDLE To INACTIVE
00001336]
00006032]
00002584]
00003232]
PUMP:
PUMP:
UPIVD
PUMP:
200000022
200000017
200000013
200000014
NUMBER
NUMBER
NUMBER
NUMBER
Start
8-4.5.10.1.6.
Reload
8-4.5.10.1.7.
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
199
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
[2007-12-04
15:57:21.941
15:57:21.941
15:57:21.941
15:57:21.941
15:57:21.941
15:57:21.941
00005504]
00005504]
00005504]
00005504]
00005504]
00005504]
FCC:
FCC:
FCC:
FCC:
FCC:
FCC:
Removing Products
Removing Tanks
Removing Probes
Removing Nozzles
Removing Ashrait
Reading configuration...
Shift Open
200
8-4.5.10.1.9.
Shift Close
8-4.5.10.1.10.
Reading Totalizers
8-4.5.10.1.11.
[2007-12-05 15:46:59.207 00005296] Close shift: creating receipts for shift 300000004 ...
[2007-12-05 15:46:59.332 00005296] Close shift: receipts for shift 300000004 created
201
8-4.5.10.1.14.
Pump Status
[2007-12-10 18:27:09.950 00004496] PUMP: OID 200000022 NUMBER 7 CPU 3 From IN_USE To PAYABLE
Proccess FUELING
IDLE
CALL
READY
IN_USE
PAYABLE
STOPPED
INACTIVE
IDLE
AUTH_DONE
FUELING
For each pump server, watchdog monitors pump server by checking status of first pump in cluster.
[2007-03-14
IDLE
[2007-03-14
IDLE
[2007-03-14
IDLE
[2007-03-14
IDLE
202
09:04:39.660 00009795] PUMP: OID 200000096 NUMBER 7 CPU 1 From IDLE To IDLE
Proccess
09:04:39.660 00009796] PUMP: OID 200000084 NUMBER 1 CPU 1 From IDLE To IDLE
Proccess
09:04:41.159 00009795] PUMP: OID 200000096 NUMBER 7 CPU 1 From IDLE To IDLE
Proccess
09:04:41.159 00009796] PUMP: OID 200000084 NUMBER 1 CPU 1 From IDLE To IDLE
Proccess
8-4.5.10.1.16.
For some operations, status needed not be checked, e.g. when in shift.
[2007-03-14 09:04:47.368 00009796] PSVD TAT_5_6_23 not sending status - shift op running
8-4.5.10.1.17.
[2007-12-11 14:17:55.966 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 From IDLE To CALL Proccess
IDLE
[2007-12-11 14:17:55.966 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Authorizing: No limit Auto authorized mode
[2007-12-11 14:17:55.966 00006488] PUMP 8 HEAD 4: sending request for authorize nozzle 4.
[2007-12-11 14:17:55.997 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 From CALL To READY
Proccess AUTH_DONE
[2007-12-11 14:17:57.966 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 From READY To IN_USE
Proccess AUTH_DONE
[2007-12-11 14:17:57.998 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.000
Price=
0.000
[2007-12-11 14:17:58.310 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.017
Price=
0.070
[2007-12-11 14:17:58.623 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.037
Price=
0.160
[2007-12-11 14:17:58.935 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.057
Price=
0.250
[2007-12-11 14:17:59.248 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.077
Price=
0.340
[2007-12-11 14:17:59.560 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.096
Price=
0.420
[2007-12-11 14:17:59.873 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.117
Price=
0.510
[2007-12-11 14:18:00.185 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.137
Price=
0.600
[2007-12-11 14:18:00.498 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.157
Price=
0.690
[2007-12-11 14:18:00.810 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
0.177
Price=
0.780
[2007-12-11 14:18:00.998 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 From IN_USE To PAYABLE
Proccess FUELING
[2007-12-11 14:18:01.013 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 - got final payment message
(final_payment_data_report
req_id="0" auth_tag="1||0|300000006"
pump_num="8"
nozzle="4"
product_id="0"
volume="00000.194"
sale="000000.86"
ppv="0004.44" time_and_date="2007/12/11
14:18:00"
trx_seq_no="638"
result="0" />)
[2007-12-11 14:18:01.045 00002136] PUMP: OID 200000023 NUMBER 8 CPU 4 INFO: checking transaction
- meanID=1 nozzle=4 mean_type=7
[2007-12-11 14:18:01.045 00002136] PUMP: OID 200000023 NUMBER 8 CPU 4 INFO: flow rate checks
skipped
[2007-12-11 14:18:01.342 00002136] DB: Added transaction: ID=300000868, PUMP=8, Vol=
0.194
Price=
0.860 TagID=1
[2007-12-11 14:18:01.529 00006488] PUMP: OID 200000023 NUMBER 8 CPU 4 From PAYABLE To IDLE
Proccess FUELING
8-4.5.10.1.18.
8-4.5.10.1.19.
[2007-12-05 09:59:27.003 00004684] Pump 7(3) - pump server failed to assign price - result=1
Pump may not have been in IDLE state - check specific pump.
8-4.5.10.1.20.
Running Volume
[2007-12-05 09:59:47.448 00004684] PUMP: OID 200000023 NUMBER 8 CPU 4 Running: Vol=
Price=
0.170
0.018
203
204
8-4.5.10.1.30.
[2007-12-11 14:29:28.218 00005436] ERROR: can't read totalizers from pump 1 - process is (1)
should be 1 status is (48) should be (49)
205
206
207
208
209
210
Now, after selecting a particular device (by using the arrow keys and Enter), a sub-menu is
displayed that allows functionality tailored to the specific device type, as shown in the following
examples:
8-5.4.3.1. Pumps
211
OPOS
212
8-5.4.3.3. Printer
213
214
Raw Logs
While the logs are being displayed, the FCC Monitor recognizes the R command, which causes
the logs to be displayed in raw form. Raw logs contain none of the display escape sequences that
the FCC Monitor uses to do scrolling and highlighting.
Raw logging is useful when used in conjunction with the session-recording feature of putty; this
allows the log to be captured to a file.
215
216
The R command works here too to enable the display of raw logs, so that they can be captured as
part of the putty session log.
217
218
8-5.4.9. Exit
Use this command to terminate the FCC Monitor.
Pressing the Escape key also exits.
SiteOmat Setup and Maintenance Manual MDE 4817G
219
Size
3.4G
23M
125M
eth1
lo
lo:1
220
VSZ
1312
0
0
0
0
0
RSS
484
0
0
0
0
0
TTY
?
?
?
?
?
?
STAT
S
SW
SW
SWN
SW
SW
START
20:09
20:09
20:09
20:09
20:09
20:09
TIME
0:03
0:00
0:00
0:00
0:00
0:00
COMMAND
init [3]
[keventd]
[kapmd]
[ksoftirqd_CPU0]
[kswapd]
[bdflush]
8-6.5. top (Displays many system statistics and details regarding active
processes)
Usage:
$ top
8:17pm up 7 min, 1 user, load average: 0.25, 0.13, 0.04
46 processes: 44 sleeping, 2 running, 0 zombie, 0 stopped
CPU states: 0.0% user, 0.1% system, 0.0% nice, 99.8% idle
Mem:
256412K av, 132016K used, 124396K free,
0K shrd,
Swap: 522104K av,
0K used, 522104K free
PID
1271
1
2
3
4
5
6
7
8
14
USER
root
root
root
root
root
root
root
root
root
root
PRI
15
15
16
15
34
25
25
15
25
16
NI
0
0
0
0
19
0
0
0
0
0
SIZE
908
484
0
0
0
0
0
0
0
0
TIME
0:00
0:03
0:00
0:00
0:00
0:00
0:00
0:00
0:00
0:00
31164K buff
30828K cached
COMMAND
top
init
keventd
kapmd
ksoftirqd_CPU0
kswapd
bdflush
kupdated
mdrecoveryd
kjourna
ESC - quit
221
q - quit
222
/var/log - System logs - show various system error including boot messages
223
The system is running under embedded Linux OS. Due to this In order to have an access to the
machine we have to log into the system via Putty as shown below: FCC IP (default :
192.168.1.104) + SSH protocol + Port 22.
224
225
226
227
228
Select
* from means
There are many more commands. lbis manual does not detail each command, for further
information, type ".help" command in order to show all the available commands in SQLite.
229
230
Authorization events: Events regarding refuel authorization incidents (i.e. Fleet credit has
been exceeded)
Screens events: Events regarding changes made in setup screens (i.e. Sysinit called)
Operation events: Events regarding the continuous operation of the system (i.e. Shift Start)
The Auto Refresh checkbox indicates whether the list should be refreshed automatically to include
new messages.
231
A list of all the successful and unsuccessful logins into the system, including the date and
time, username and result (see Figure 8-38)
A list of all the reports produced in the system, including the date and time, the user who
produced the report and the title of the report (see Figure 8-39)
To switch between the two lists, select "Login" or "Reports" in the drop-down list.
232
233
The last significant alarm is displayed on the bottom part of the main screen, all other alarms can be
viewed by clicking on the Alarms button. The Alarms screen is displayed (see Figure 8-40).
The upper part of the screen allows users to filter the alarm list by various parameters:
Report Type:
Select the Unacknowledged Alarm checkbox to display a summary of currently active
alarms any alarm that is not ended or ended and was not acknowledged is listed in the grid
Select Alarm History to see alarms that are both ended and acknowledged
Priority:
Choose the alarms to be displayed by priority. Select the required checkboxes: Urgent,
High, Low, Exceptional, Journal.
Device/ Type:
Filter the alarms to be displayed by the device which triggered them or by their type. Select
this option from the drop-down lists.
Date:
Select the time range, using the date and time combo boxes (From and To fields)
Click on the Refresh button, to refresh the display according to the selection made.
Select the Auto Refresh checkbox to allow auto-refreshing of the list to include new messages.
The lower part of the screen allows users to acknowledge the alarms displayed, adding an
acknowledgement is considered as closing the alarm.
It is possible to acknowledge a specific alarm, the page displayed or all alarms.
Occasionally, it is required to force end alarm. Select the alarm and click on the Force End Alarm
button. The alarm is acknowledged and forced to end
NOTE
The system activates a single alarm per event.
234
235
LAN
Power
Software
System
USB
236
Normal
LED
Behavior
LEDNumber
Description
DL1
On
DL2
On
DL3
Flashing
DL4
On
DL5
On
DL6
Flashing
DL7
5V pwr
On
DL8
3.3V pwr
On
DL9
1.8V pwr
On
DL10
1.3V pwr
On
DL11
N/A
Off
DL12
N/A
Off
DL13
Flashing
DL14
Off
DL15
Off
DL16
N/A
Off
DL17
Off
DL18
Bios Run OK
On
DL19
USB ON
Off
DL20
USB ON
Off
DL21
USB ON
Off
237
238
239
240
241
242
243
244
NOTE
To continue normal work, restart the OrCU.
8-12.1. OrCU Ethernet Failure Data Base
Recovery
In order to save the database, in cases where OrCU Ethernet connection doesn't work, technicians
may utilize Zmodem protocol.
Proceed as follows:
1. Run the 'run console' command
2. Type the following command: 'sz DATA.DB', in the correct folder in OrCU
(i.e. orcu: /usr/local/orpak/BOS/DB# sz DATA.DB)
3. Zmodem with Crash Recovery dialog box appears (see Figure 8-54) and the file is stored on
the PC
245
SECTION 9
ORCU EXTERNAL COMMUNICATION
9-1. GENERAL
This section is intended to show all possible communication between the OrCU, FHO and remote
consoles.
9-2. OVERVIEW
The OrCU supports a variety of communications methods for reports, maintenance and FHO.
The communications options are:
1.
2.
3.
4.
5.
ADSL/Intranet connections
Dial Up Modems
GPRS Modems
3G (HSDPA) Adaptors.
Connecting to OrCU from external PC.
247
NOTE
Use commands executed one time only and not
commands executed multiple times (such as Ping).
248
Station
Router
Interne
t
VPN Router
172.25.138.193
Switch
192.168.2.1
LAN2
192.168.2.104
172.25.138.195
Head Office
10.180.0.3
ORCU
LAN1
Switch
192.168.0.104
CWGT
192.168.0.1
MWGT
192.168.0.2
249
250
Cable connection - Siemens modem to OrCU serial port (see cable specification, paragraph 9-4.6).
Siemens DT9/M
OrCU DT9/M
251
3. Cable connection - Wavecom modem to OrCU serial port (connected via OrCU cross serial
cable - see serial cable specification, paragraph 9-4.6)
Wavecom 15P/M 1
OrCU Cross
Cable DT9/M
10
11
12
13
14
252
Cable connection - Siemens modem to OrCU serial port (see cable specification, paragraph 9-4.6)
US Robotics 25/M
OrCU DT9/M
10
25
253
D9 to D9 D9 to D25
23
22
32
33
87
75
78
84
55
57
9-4.7. AT COMMANDS
Command Description
AT&B1
AT&C0
AT&A3
Enable data compression result codes and add V.42bis and MNP 5 protocol indicators
AT&D0
Ignore DTR
AT&F
AT&W
Save Settings
ATZ
Resets Modem
254
Static IP address
APN name
9-6.
9-6.1.
3G MODEMS CONNECTIONS
Overview
The OrCU supports 3G cellular connection through a Router and a 3G adaptor (see Figure 9-10).
The OrCU is "Online" and can be connected at all times using a fix IP address.
The fix IP address is supplied by the ISP (Internet Serves provider).
255
256
257
2. The connection to the internet (APN, Phone Number, User ,Etc.) should be set according to
the user's 3G ISP instructions.
3. In order to have access to OrCU from a remote site, a NAT (Network Address Translation) or
Port Forwarding are required to be set for ports 443 and 22 (see Figure 9-2)
258
NOTE
Verify that the 3G ISP does not block these ports.
NOTE
Browsing to the OrCU from a remote site is done via
the public (ISP) IP address.
9-6.4. OrCU Settings
1. Browse to the OrCU admin screen (IP=xx.xx.xx.xx:8090). See Figure 9-3
2. Set the OrCU LAN2 IP address according to the Router class settings (e.g. 10.0.0.1)
3. Set the "Default Getaway" as the Router IP address (e.g. 10.0.0.46)
259
260
5. Select the Modem in use and click Next. The Connection Name screen appears (see
Figure 9-17)
261
262
263
264
SECTION 10
GLOSSARY
ADMIN
Administrator
BOS
BSP
ComVerter
LAN/232/485/422/C.L./Tokheim
Communication Converter
DataPass
EFT
FCC
Forecourt Controller
FHO
HO
Head Office
IP
Internet Protocol
LAM
Local Account
LAN
Mag
Magnetic card
MIFARE
MPI
MPI-C
OPOS
OrCU
OrCU 3000
Islander PLUS
265
OrIT
OrPT
OrTC
OrTR
PIN
POS
Point Of Sale
PPL
PPV
SAM
Sundries
VIU
Access Point
Ad Hoc
Backbone
BSS
Basic Service Set. An Access Point associated with several wireless stations.
DES
DHCP
ESS
Extended Service Set. More than one BSS can be configured as an Extended
Service Set. An ESS is basically a roaming domain.
ESSID
Ethernet
266
Infrastructure
LAN
Roaming
A function that allows one to travel with a mobile end system (wireless LAN
mobile station, for example) through the territory of a domain (an ESS, for
example) while continuously connecting to the infrastructure.
TCP/IP
Triple DES
WAN
WEP
WG
Wireless Gateway
267
APPENDIX A
SITE SURVEY FORMS
The following appendices are provided in order to enable users to plan the setup of the Controller
system.
These appendices contain a survey form that requires listing and defining the equipment installed in
the Isle. This information shall enable users to provide each unit a functional identification in
accordance with its type.
The site survey forms are provided in two appendices:
Appendix B Site Survey Form for all Controllers in Home Base gas Stations
Appendix C Site Survey Form for truck mounted Controller
268
APPENDIX B
SITE SURVEY FORM HOME BASE STATION
/
Date:
Prepared by:
e-mail:
Phone:
name
Address
Contact person:
Phone:
Mobile phone:
AC
220V
110V
Other
Type of Pumps:
Number of Pumps:
Number of nozzles:
Number of Authorizers required:
Electronic Pulser installed:
Yes
No
Yes
No
269
Yes
No
Yes
Yes
Yes
No
No
No
Site Planning
Provide drawings and/or photos of the site - Pay attention to the following features:
Distances
Location of:
Pumps
Nozzles
Valves
Pulsers
Cabinet
270
Definition of Equipment
Define the following parameters:
Definition of Buses: Refer to definition tables in Chapter 2
Name
Frame
IP
Name
Frame
IP
Name
Frame
IP
Name
Frame
IP #
Definition of Readers:
Name
Bus
Name
Bus
Name
Bus
Name
Bus
Definition of Pumps
Pump #1 Side #
Head #
No. of Nozzles
Cluster #
Pump #2
Side # Head
No. of Nozzles
Cluster #
Pump #3
Side # Head
No. of Nozzles
Cluster #
Pump #4 Side #
Head #
No. of Nozzles
Pump #5
Side # Head
No. of Nozzles
Cluster #
Pump #6
Side # Head
No. of Nozzles
Cluster #
Pump #7
Side # Head
No. of Nozzles
Cluster #
Pump #8 Side #
Head #
No. of Nozzles
Cluster #
Cluster #
# Side
# Pump
Hose
# Side
# Pump
Hose
# Side
# Pump
Hose
# Side
# Pump
Hose
# Side
# Pump
Hose #
Side #
Pump #
271
APPENDIX C
SITE SURVEY FORM FUEL TRUCK STATION
Date:
Prepared by:
@
e-mail:
Phone:
name
Address
Contact person:
Phone:
Mobile phone:
Truck Data:
Station name:
Site Name:
Power Supply:
12VDC
24VDC
Other
Number of nozzles
(To be connected to Fuel Truck Controller):
Number of Authorizers required:
Hose on:
Reel
Long hose
Other
Yes
No
Yes
No
Yes
No
Yes
No
(photo required)
272
Yes
No
Yes
No
Yes
No
3/4
Hose Thread :
Male
Female
Nozzle/Hose Thread:
Inch
Millimeter
Nozzle Equipment
Hose Diameter:
Other
Hose Length:
BSP
NPT
Manufacturer:
Model:
Yes
Yes
No
No
VIU:
Yes
No
FuelOpass:
Yes
No
Contactless TAG:
Yes
No
Vapor Recovery:
Site Inspection
Provide drawings and/or photos of the site - Pay attention to the following features:
Distances
Location of:
273
Pumps
Reel
Nozzles
Valves
Pulsers
Cabinet
Miscellaneous
Color schemes and Graphics that may affect the appearance of our equipment on the truck:
Description
274
APPENDIX D
HOW TO OPEN ZIP OR RAR FILES
ZIP FILES
ZIP is a popular archive format widely used to compress and package files. Like other archives, ZIP
files are data containers; they store one or several files in a compressed form. After downloading a
ZIP file, unpack/unzip its contents in order to use it.
HOW TO HANDLE ZIP FILES
WinRAR provides the complete support for ZIP files, so users may both create and unpack/unzip
them. If the user has installed WinRAR on the computer and downloaded a ZIP file from Internet,
double click on the ZIP file icon to open it in WinRAR, select all files, click on the Extract To
button, enter a destination path and click OK. Another way is to click on the ZIP file in the
Explorer using the right mouse button. If the user enabled the "Shell integration" option when
installing WinRAR, the file context menu contains the Extract to ... option.
RAR FILES
RAR is the native format of WinRAR archiver. Like other archives, RAR files are data containers,
they store one or several files in a compressed form. After downloading a RAR file from Internet,
unpack its contents in order to use it.
HOW TO HANDLE RAR FILES
WinRAR provides the complete support for RAR files, so users may both create and unpack them.
If the user has installed WinRAR on the computer and downloaded a RAR file from Internet,
double click on the RAR file icon to open it in WinRAR, select all files, click on the Extract To
button, enter a destination path and click OK. Another way is to click on the RAR file in Explorer
using the right mouse button. If the user enabled the Shell integration option when installing
WinRAR, the file context menu contains the Extract to ... option.
Several RAR files can be parts of multi-volume sequences. In WinRAR a huge archive can be
splitted into a few smaller files, which are called volumes. They may have extensions .rar (the first
volume), .r00, .r01, ..., or .part1.rar (the first volume), .part2.rar, ..., etc. To unpack the volumes,
place all of them in the same folder and start extraction from the first volume.
275
APPENDIX E
SETTING THE IP ADDRESS
To set the IP address on a PC, proceed as follows:
1. Go to the Start Menu
2. Select Settings ant then Control Panel. The Control Panel screen appears (see
Figure E-1)
276
4. Right click on the relevant Local Area Connection (the connection to be used for the
OrCU)
5. Click Properties. The Local Area Connection dialog box appears (see Figure E-3)
277
278
279
APPENDIX F
WEIGHT AND MEASURES SECURITY PLUG
F-1.
GENERAL
This appendix provides instructions for installing the Weight and Measures Security Plug (see
Figure F-1) in Gasboy Site Controllers.
In order to comply with W&M regulations and since pulses to volume conversion factor is defined
in FCC, the security plug connected directly to OrCU via RS-232 port, prevents miscalibration of
Mechanical Pumps.
NOTE
Since RS-232 port is used, remote communication
via dial-up modem will not be supported.
Once the W&M security plug is detected, fuelling from mechanical pumps is allowed but
modification of the pulse factor will be disabled (current value is shown).
This procedure should be performed in each controller (Islander PLUS, CFN PLUS, FTC, TopKAT
PLUS) that commands a mechanical pump.
NOTE
Controllers configured for mechanical pumps
become inoperable in cases where the W&M
security plug is missing / removed.
INSTALLATION KIT
280
F-3.
P/N
Description
819135510
Security Plug
Packs
Qty.
1
814935530
Bracket
815504611
Spacer
INSTALLATION PROCEDURE
281
282
SETUP
283
284
285
APPENDIX G
DISCOVERY MODE
G-1. GENERAL
Software version 6.4.x.x and above has a feature that allows SiteOmat to accept Devices
automatically prior of having these Devices loaded into the FHO database. This is an alternative
method of importing Device information into the FHO Devices database, rather than manual entry
or importing from an excel spread sheet.
NOTE
In order for this feature to operate correctly it is
necessary that you have access and knowledge of the
following information from the system being
replaced (i.e.: Series1000 System) Magnetic Card
or Key Layout, System ID, Product Limitations &
Authorizations, Number & Name of ID fields,
Single or Dual Card or Key operation.
G-2. SETUP
To allow the discovery mode to function properly you need to set up and configure the SiteOmat in
the two following locations:
1. Setup Advanced Global Advanced Select the Discovery Mode checkbox and
click Modify (see Figure G-1)
286
287
288
289
290
NOTE
If a device entered at the OrPT does not match the
card format information loaded in the Wizard setup,
including the System ID, number of fields and Field
size and Product Authorization, the OrPT will
display Device not Found or Auth Wrong
Product or Decline
5. Now go to the FHO and select the Stations screen, select the station you want to download
the Devices from. Verify the FHO is connected to the Station selected.
6. Observe the Status and Push Pending parameters while the Device data is being pushed to
the FHO (see Figure G-7 and Figure G-8)
291
292
Figure G-11. Devices Properties Dialog Validation Tab PIN Code Section
G.3.2. Odometer Feature
Magnetic cards or Data Keys that have a check digit that requires an Odometer entry, the Discovery
mode populates the Odometer information box in Validations (see Figure G-12)
293
294