Download 4COM Manual

Appendix
4.6
113
Trouble-shooting
The purpose of this section is to provide assistance in interpreting the events and conditions that
are revealed using 4COM. The events are either 4COM generated events which are usually
identified by messages in the 4COM Audit Trail or site/PCC recorded events and found in the
events file from PCC's.
4.6.1
4COM events
How do I fill in the "holes" (missing transaction records) that have developed in the Dispenser
transaction data for a site?
If a hole exists you will be notified as soon as one develops by a warning in the audit trail. In
particular the warning will indicate the start timestamp of the hole and also the end timestamp. To
rectify this, using the 4COM Manager isolate all records for the site that are time stamped later (>)
the start timestamp of the hole. This can be done using the transaction filter functionality to view
only those transactions for a site greater than a nominated date time. When this has been done
select all the records (Ctrl -A) then delete them. Next use the Postec Data logger Logger Reader
utility to extract the Data logger contents and save the contents to disk (files). Next use the 4COM
Manager or process the extracted site transaction file (XXXXXX.trn) or extended transaction file
(XXXXXX.etf) using the PCC File import functionality. Note it is essential ONLY the correct file is
processed (if the Aux devices for the site in question contains a reference to X-fuel then process
the .etf file otherwise process the .trn file.
This topic is currently under construction. Postec are busy compiling a comprehensive list of not
only 4COM problems encountered but also a list of problems experienced at sites and how using
4COM the appropriate remedial action can determined and under-taken. You will be notified as
soon as this information is available.
4.6.2
PCC Events
The purpose of this section is to provide assistance in interpreting the PCC Event file reports as
can be uploaded and viewed by 4COM or other applications.
The PCC Event file consists of a structured record containing the following fields:
· Date
· Time
· Device Code
· Node number
· Event Code
· Description block
The Device and Event codes are predefined values that decode into specific descriptors. This
enables a lot of information to be recorded in the PCC using a minimum amount memory and also
provides a structure for applying complex filters in the viewing software.
The Node number identifies a specific device where multiple devices of the same type are used. eg
Dispenser number.
The Description block contains optional miscellaneous data that must be decoded with unique
rules determined by the Device and Event codes for that record.
When the PCC restarts, it establishes communications with all the devices it is connected to and
as a result of this Online Event records are recorded for each device. After this, the PCC records
event records for activities and events it schedules or observes.
For convenience the document is structured into Device blocks in alphabetic order. Each device
block contains a description of the possible events which apply to that specific device.
© 1987 - 2009 Postec Data Systems Ltd, all rights reserved.