Instruction Manual - Operating Guide PDF

REFCON
Operators Manual
Reefer
Container
Monitoring
System
Global Container Efficiency

Operators Manual
© 2009 Johnson Controls Denmark - Global Container Efficiency
All rights reserved. No parts of this work may be reproduced in any form or by any means - graphic, electronic, or
mechanical, including photocopying, recording, taping, or information storage and retrieval systems - without the
written permission of the publisher.
Products that are referred to in this document may be either trademarks and/or registered trademarks of the
respective owners. The publisher and the author make no claim to these trademarks.
While every precaution has been taken in the preparation of this document, the publisher and the author assume no
responsibility for errors or omissions, or for damages resulting from the use of information contained in this document
or from the use of programs and source code that may accompany it. In no event shall the publisher and the author be
liable for any loss of profit or any other commercial damage caused or alleged to have been caused directly or
indirectly by this document.
Manual version: Instruction Manual - Operating Guide - Ship, RDC MkII
Document Revision Record

Rev. Date Responsible Description
4.0 2007-05-03 Hans Peter Lund Original revision
5.0 2007-06-07 Hans Peter Lund ContHand, GMSdata, Maintain and ModemTSG updated
5.2 2007-11-12 Hans Peter Lund Layout redesign, general update
5.4 2009-01-22 Hans Peter Lund Minor corrections due to software adjustments
5.5 2009-05-20 Hans Peter Lund (/FA) Updates reg. RDC default walkroute and auto container deletion
5.6 2009-07-07 Hans Peter Lund Updates reg. auto container deletion
5.6a 2009-09-21 Hans Peter Lund Screen shot updated, def. walk route descr. corrected
PDF created: 21-09-2009 in Aarhus, Denmark by

Johnson Controls Denmark ApS
Jens Juuls Vej 28
8260 Viby J
Denmark
Phone: +45 8736 3500
Fax: +45 8736 3501
Mail: CG-EUR-DK-refcon-service@jci.com
www.myREFCON.com
Contents 3
Table of Contents
Part I Introduction to REFCON 8

1 About us ................................................................................................................................... 8
2 Using the ...................................................................................................................................
Online Help 9
Searching.........................................................................................................................................................
the Online Help 11
Part II Quick Introduction 14

1 Getting familiar
...................................................................................................................................
to REFCON 16
2 Using REFCON
................................................................................................................................... 17
Using the.........................................................................................................................................................
Bayplan/Stackplan 18
Using the.........................................................................................................................................................
Container Summary 19
Using the.........................................................................................................................................................
Container Report 20
Handling .........................................................................................................................................................
Log Files 20
3 Guidelines
...................................................................................................................................
for Daily Operations 21
Loading Phase
......................................................................................................................................................... 22
Discharge.........................................................................................................................................................
Phase 22
Supervision
.........................................................................................................................................................
and Logging Phase 23
4 Frequently
...................................................................................................................................
Asked Questions and Answers 23
How to Handle
.........................................................................................................................................................
Difference between Actual and Expected Setpoint? 24
Why is the
.........................................................................................................................................................
Number of Communicating Containers Incorrect? 25
How to Handle
.........................................................................................................................................................
a Ghost Container? 25
What does.........................................................................................................................................................
Owner Code LANG, LOSU, RAND or RMMU mean? 26
Why No Connection
.........................................................................................................................................................
to Loading Computer / Terminal System? 26
Why are Reefer
.........................................................................................................................................................
Containers Not Communicating with REFCON? 26
Part III User Interface Basics 28

1 Always Visible
...................................................................................................................................
Information 28
2 Picture and
...................................................................................................................................
Window Types 30
3 How to Operate
...................................................................................................................................
the System 32
4 Local Settings
................................................................................................................................... 34
Part IV Passwords 36
1 Passwords
...................................................................................................................................
in Daily Use 36
2 How Passwords
...................................................................................................................................
Work 38
3 Password...................................................................................................................................
Administration 38
Part V Basic container handling 42

1 Container...................................................................................................................................
statistics 42
2 Container...................................................................................................................................
handling mode (ships only) 43
3 Container...................................................................................................................................
Delete Function 44
4 REFCON...................................................................................................................................
Setup 46

4 Operators Manual
Library Setup
......................................................................................................................................................... 47
Alarm Setup
......................................................................................................................................................... 47
Automatic.........................................................................................................................................................
Container Deletion Setup 48
Data Obsolescence
.........................................................................................................................................................
Setup 50
REFCON .........................................................................................................................................................
Log Files Setup 50
Unit Setup
......................................................................................................................................................... 51
Part VI Container Report 54

1 Container...................................................................................................................................
Report Main Page 56
2 Sub-page...................................................................................................................................
Load Data 57
3 Sub-page...................................................................................................................................
Measurings 57
4 Sub-page...................................................................................................................................
Log Files 59
5 Sub-page...................................................................................................................................
Alarms 59
6 Sub-page...................................................................................................................................
Communication 60
7 Sub-page...................................................................................................................................
Operations 61
8 Sub-page...................................................................................................................................
Utility 63
Part VII The Container Summary 66

1 Container...................................................................................................................................
Summary Columns 67
2 Container...................................................................................................................................
Summary Special Menu 69
Pick Out Criteria
.........................................................................................................................................................
Syntax 71
Part VIII Bayplan - Stackplan 74

1 Bayplan -...................................................................................................................................
Stackplan Detail Pictures 76
Part IX The Alarm System 80

1 Alarm Summary
................................................................................................................................... 81
2 Alarm Information
...................................................................................................................................
window 83
3 Inhibit handling
................................................................................................................................... 85
4 Special reefers
...................................................................................................................................
- alarm group 3 (optional) 85
Part X Event Logging 88

1 Event List
................................................................................................................................... 88
Part XI Printing 92
1 Periodic Printout
................................................................................................................................... 92
2 Printing on
...................................................................................................................................
Demand 94
Part XII Handling Log Files 98

1 Log file activities
................................................................................................................................... 99
2 Log File...................................................................................................................................
Manager 101
3 Log Viewing
................................................................................................................................... 103
4 Log Trend
................................................................................................................................... 104
Log Trend
.........................................................................................................................................................
Button Panel 106

Contents 5
Part XIII Handling Load Data 110

1 Transferring
...................................................................................................................................
the Load Data File 111
2 Using the
...................................................................................................................................
Load Data dalog box 112
3 Automatic
...................................................................................................................................
Load Data File Transfer (optional) 113
4 Understanding
...................................................................................................................................
the Transfer Log File 114
5 Understanding
...................................................................................................................................
the Load Data File 115
Part XIV Clock System 118

1 Standard
...................................................................................................................................
Clock System 119
2 Master Clock
...................................................................................................................................
System (optional) 121
Operating
.........................................................................................................................................................
the Master Clock System 122
3 Clock System
...................................................................................................................................
Trouble Shooting 125
Part XV Modem Troubleshooting 128

1 Checking
...................................................................................................................................
Your Containers 129
2 Checking
...................................................................................................................................
the Symptoms 130
Symptom:
.........................................................................................................................................................
Never Communicated 131
Symptom:
.........................................................................................................................................................
Stopped Communicating 132
Symptom:
.........................................................................................................................................................
No Location - Wrong or No ID in Controller ("Ghost") 133
Finding ..................................................................................................................................................
a Ghost Container 135
Change..................................................................................................................................................
of Container ID 137
Symptom:
.........................................................................................................................................................
No Data from Container 138
3 Checking
...................................................................................................................................
the Power Cabling 139
4 Typical ...................................................................................................................................
Errors 140
5 Locating...................................................................................................................................
the Modem 141
6 RMM Modem
...................................................................................................................................
Facts 142
7 Malfunction
...................................................................................................................................
List 144
Part XVI Maintaining REFCON 148

1 System ...................................................................................................................................
Items List 148
2 Third-party
...................................................................................................................................
Software on the REFCON PC 149
Part XVII Data Transfer for Global

Monitoring 152
1 Transferring
...................................................................................................................................
data manually 152
2 Transferring
...................................................................................................................................
data automatically 154
Part XVIII RDC Mark II 158

1 Operating
...................................................................................................................................
RDC from REFCON 160
2 Operating
...................................................................................................................................
the RDC Hand-held Computer 165
Start pictures
......................................................................................................................................................... 167
Menus and.........................................................................................................................................................
Settings 170
The Psion.........................................................................................................................................................
RDC Container List picture 172

6 Operators Manual
Part XIX RDC Walk Route 178

1 Custom...................................................................................................................................
Walk Route 180
Index 183

REFCON
Introduction to
REFCON
8 Operators Manual
1 Introduction to REFCON
Welcome to REFCON
The REFCON system enables an operator to automatically monitor and control thousands of
reefer containers through a single computer system and provides following functions:
· Monitors alarm and temperature conditions, and notifies the user of any alarms generated
by the container controller.
· Registers the history of each container, recording all important parameters and storing the
data in an accurate, detailed log file.
· Send commands, such as “defrost” and “change of set point”, to the containers directly
from REFCON.
· Interfaces with the vessel's load calculator or the terminal's administrative system for
automatically transferring reefer container data and locations.
This makes REFCON the ideal solution for any terminal and any container vessel - large or
small.
Welcome to the User's Guide

Welcome to the REFCON User's Guide.
The Guide is available in these versions:
· An online help, which can be opened by selecting "User Help" from REFCON's Help menu.
· A printed manual, which can be purchased from your REFCON supplier.
1.1 About us
The REFCON application was developed and delivered by:
Johnson Controls Denmark ApS

Jens Juuls Vej 28,
8260 Viby J – Denmark.
Phone: +45 87 36 35 00
Fax: +45 87 36 35 01
E-mail: CG-EUR-DK-refcon-service@jci.com
www.myREFCON.com

Introduction to REFCON 9
1.2 Using the Online Help
Overview
In the Help menu, select the "User Help" option to have the online help displayed. The Help
window appears:
The Help window consists of three main parts:

· The command buttons at the top.
· The Navigation Pane to the left.
· The Information Pane to the right.
The Navigation Pane

You have four possible entrances to the help information:
· Click the Contents tab to scroll through a table of contents for Help.
· Click the Index tab to have all keywords listed in alphabetical order.
· Click the Search tab to be allowed to enter any free text search string.
· Click the Favorites tab to be allowed to use and build your own list of important topics.
Using the Help Contents Tab

In the Help window, selecting the Contents tab displays the table of contents for the Help
system.
As you see, the Help is organised in modules. In the example above, there are 6 modules, of
which "The REFCON Monitor" is open. Within each module, you will find a number of
sub-topics, in some cases organised in more levels.
Clicking a + sign makes sub-topics shown. Clicking a – sign makes sub-topics hidden.

10 Operators Manual
To display any topic, just click it. This also is true for the module titles.
Using the Help Index Tab

In the Help window, selecting the Index tab lists all keywords in alphabetical order.
In the textbox, type in the first characters in the keyword you're looking for. The list scrolls
automatically as you type, if the string is found.
Double-click the desired topic, or single-click and select the Display button.
Using the Help Favorites Tab

In the Help window, selecting the Favorites tab will allow you to use and build a list of
important topics. Note that you share the list with the other users of the PC.
To add a topic, you must first open it from one of the other tabs.
The Information Pane

In the larger right side of the Help window, the selected topic is shown. You will find the
following ingredients:
· The Title of the topic. You will recognize it from the Navigation Pane.
· The Link box, with the list of subject labels to the left, and a list of related topics to the right.
· The body of the topic, with text and graphics.
· The Topic navigation buttons at the bottom, see The Buttons.
The Buttons
At the top of the Help window, and at the bottom of the Information Pane, the following
buttons are available:
Buttons Explanation
The Hide button removes the Navigation Pane, making the Help
window smaller while the topic information is still visible. Click Show
to bring it back.
The Back and Forward buttons operate on your actual chain of
visited topic pages. Each time you open a new topic page, it is
inserted in the chain after the actually displayed page. The Back
button jumps to the page earlier in the chain. Having used the Back
button, you can use Forward to return to a page later in the chain.

Introduction to REFCON 11
Buttons Explanation
Jumps to the very first topic in the very first Help module
("Introduction to REFCON").
Prints the current topic or a number of topics on the printer you

select. To have a collection of topics printed, proceed as follows:
1. Click the Contents tab in the Navigation pane.
2. Select the heading of a topic with sub-topics.
3. Click the Print button and select "Print the selected heading and
all subtopics".
Jumps to the previous / next topic in the current Help module
according to the Contents table. If you are already on the first / last
topic, the respective button is not shown. Please do not confuse
with the Back and Forward buttons upperleft in the Help window.
Jumps to the first topic in the current Help module according to the
Contents table. Please do not confuse with the Home button at the
top of the Help window.
1.2.1 Searching the Online Help
Overview
You can find the information you are looking for in a number of ways:
· Use the Contents or the Index tab, see Using the Online Help.
· Use the Search function described below.
Using the Help Search Tab

In the Help window, selecting the Search tab will allow you to enter any free text search
string.
Proceed as follows:
Step Action
1 Enter a search criterion (see details below).
2 Maybe change the settings of the three checkboxes at the bottom.

12 Operators Manual
Step Action
3 Select "List Topics" to do the search – it might take a while.
4 If no hits are found, a dialog box informs about this, and you may try again.
5 If hits are found, a prioritised list appears in the listbox.
6 Double-click a topic to have it shown in the Information pane.
7 Note that your search criterion word(s) are highlighted.
Search Criteria Syntax

If you, as in the above example, type in more than one word, topics will be listed that contain
all the words, but they don't have to be in succession. Using the AND operator will have the
same function. For example, the criterion iso container and the criterion iso and container
will both find all topics where both the word iso and the word container are found.
Use quotation-marks (") to search for all the words in sequence. For example, the criterion
"iso container" will only find topics where the two words are found in succession.
Use the OR operator to search for any of the words, that is, topics are listed that contain
either the one or the other search word (or more). For example, the criterion iso or container
will find all topics where either the word iso or the word container are found.
Also you can use wildcard characters:
· Use the asterisk (*) to replace any sequence of characters. For example, wh* will find why,
who and when.
· Use the question-mark (?) to replace one character. For example, wh? will find why and
who, but not when.
Note that you can't combine the wildcard characters and the quotation-marks.
The List of Topics

In the list of found topics, the first column shows the topic headings. The second column
shows the titles of the Help modules to which the information topics relate.

REFCON
Quick Introduction
14 Operators Manual
2 Quick Introduction
Welcome to REFCON
This Quick Introduction is aimed at new REFCON users. We want to help you getting started
with REFCON, and to guide you to an understanding of the primary tasks that you can carry
out by means of REFCON.
Please be aware that the Quick Introduction describes a sub-set of the REFCON functions
only! For a complete description you should refer to the online help or to the optional
instruction book.
Actually, getting started is two things:
· Initially, the hardware and software must be installed – please study these procedures in
the Installation Instructions.
· With REFCON running, new users need to learn how to use it – which is the subject of this
Quick Introduction. You can read more in the online help.
We assume that you know a little about reefer containers and that you have some experience
with Microsoft Windows.
The Reefer Container

A reefer container is an independent unit that is completely self-sustained, being supplied with
3-phase power. An onboard piece of microprocessor-based electronics, called a controller,
controls the temperature and other parameters at their respective setpoint(s), and it
continuously logs the conditions.
Two main systems exist for remote monitoring of reefer containers: Power cable
communication and 4-pole signals.
The majority of newer reefer containers are equipped with a power cable modem, allowing the
container to communicate most parameters via the power line. The power cable modem can
be an independent unit or integrated with the controller. If the modem is manufactured by
Johnson Controls, it is named RMM (Remote Monitoring Module).
Older container types, as well as a minority of newer reefer containers, do not have the power
cable modem. For such a container, the 4-pole signal cable need to be connected, in addition
to the power cable, to facilitate remote monitoring. The 4-pole cable communicates three
status signals: "Compressor Run", "In Range" and "Defrost".
Some containers do have both a modem and a 4-pole signal cable.
The REFCON System Layout

REFCON is designed to handle a larger number of reefer containers. This primarily takes
places via the REFCON PC. There might be more than one REFCON PC, in which case you
can normally operate from any of them.
Additionally, REFCON includes two or more RMM master modems (Remote Monitoring
Module), as sketched in the following minimum configuration.

Quick Introduction 15
The RMM master modem enables REFCON to communicate with the reefer containers. Of
course this is only possible when the containers are equipped with power cable modems.
The specific REFCON system might include more than two RMM master modems. Also it
might include hardware for detecting the 4-pole signals. The specific configuration of your
REFCON system is described in the Instruction Manual - Hardware Descriptions.
Short Description of REFCON

REFCON is an alarm and monitoring system used in all kinds of container ships, container
terminals, PTI testpoints etc. It supervises reefer containers equipped with independent
electrical refrigeration units.
The REFCON system will, on the basis of the available data from the container, monitor and
supervise the current condition of the container and, in case of an error, indicate alarm.
It should be noted that, in general, REFCON does not control the system or create alarms,
rather it takes the reefer container functions and presents them in one central location
enabling one operator to supervise many hundreds of containers.
REFCON is supplied by Johnson Controls Denmark in various configurations depending on
the needs and requirements of the customer. The major configurations are:
· REFCON with power cable transmission (PCT) equipment for monitoring and controlling
reefer containers.
· REFCON with PCT like above, extended with a 4-pole reefer monitoring system.
· Any of the above extended with the RDC option. The REFCON Data Collector assists you
in fetching data from non-communicating containers manually. The RDC includes a
handheld computer that you can take to the containers for typing in temperatures etc. Then
by connecting the handheld computer to REFCON, data can be transferred and work in
REFCON exactly as if they were automatically communicated via the PCT.
· Any of the above extended with the LogMan / LogView option. LogMan allows you to
transfer log-files from container controller, while LogView allows you to inspect the logs
graphically.
· Any of the above extended with GMS option. The Global Monitoring Server interface
automatically transmits container data to a central database periodically, allowing owners
and customers to keep an eye on the conditions of the cargo.
REFCON with PCT collects temperature data and other parameters from the reefer
containers. These data can be stored on the harddisk for future inspection. Depending on the
controller type you can change parameters and give commands to the individual container
from REFCON.

16 Operators Manual
The Important Match with Load Data

Power Cable Transmission (PCT) can be seen as a kind of radio communication. As such, it
does not include information about the position (location) of the container. REFCON works
well without this – but for many of your tasks it is a great advantage to have REFCON show
the locations, and other offline information. For example, you can't use the Bayplan/Stackplan
if the location information is not available.
We call this offline information Load data. You need to transfer the load data from a Loading
Computer or Terminal System. In the most REFCON systems you need to trigger this transfer
manually. For further information, please refer to Loading Phase.
What could happen is that you transfer the load data before starting to actually load the
containers. Then, for the following hours, the containers will start communicating, one by one.
The key for the communication with each individual container is the Container ID – the 4-letter
and 7-digit code painted on the container box. The exactly same code is programmed into the
controller. In rare cases there is a mismatch, please refer to How to Handle a Ghost
Container?.
As soon as a container starts communicating, REFCON will attempt to match it to the load
data, that is, it looks for the container ID in the load data list. This also works when things
happen in opposite order: If the container already is communicating when load data is
transferred, REFCON will attempt to make the match as well.
2.1 Getting familiar to REFCON
Welcome to the new user

The REFCON screen pictures and menu system are quite overwhelming to many new users!
This section gives a few hints on how to get familiar with the system.
First a few words about the online help. In the online help, all information about all screen
pictures and computer functions are found, for instance, how the alarm system is working,
how containers are managed, and so on. If you have a certain question, try to look for the
answer in the online help.
However, most people don't get familiar to computer systems by reading instructions. The
best way is to sit down at the PC and try!
Password protection
The conscientious new user will probably be afraid of doing something wrong. Hopefully, the
following facts can help in this case:
· Yes, from certain screen pictures it is possible to manipulate things, eg. change setpoints or
information about containers.
· But to do so, you need to enter a password code. The code consists of 6 characters that
must be entered when the following dialog appears:
To be sure nothing is changed, just hit the [Esc] key or click the [Cancel] button in this case.
Therefore, it is impossible to change or damage anything by accident.
· The [Esc] key is in general available to "step back".

· No, it is not possible to damage any part of the computer system by hitting keys on the
keyboard or by clicking the mouse/trackball.
· Hitting a not legal key is simply ignored by the computer.
So, sit down at the PC and go through the pictures, using the menus and buttons found.
2.2 Using REFCON
Overview
In this section we will tell you about the primary tools available in REFCON. Please refer to
the online help for details and descriptions of other tools.
While working with REFCON you mainly do the things listed in the following headlines.
You get an overview of containers

REFCON includes two main tools for getting overview of the containers.
The Bayplan/Stackplan pictures show containers by location. A zoom facility is included so
that you have the whole scale – from a total overview with very little information about each
container – to the bay or stack segment with more information. The bayplan/stackplan
pictures only work when the containers have been given position information from the
Loading computer / Terminal System (or by other means).
The Container Summary is a list where you see one container a line. The Summary exists in
different versions, showing different sets of data for each container. It is possible to select a
sub-set of the containers (pick out), and to select the sort order.
You deal with a single specific container

By selecting a container in the Bayplan/Stackplan or in the Container Summary, you can
make the Container Report show up. The Report contains all information about the container
and is your tool for making any kinds of operations on the specific container.
You act on alarms

You are alerted by new alarms from reefer containers by a flashing field on the screen and by
an optional alarm extension system. Use the Alarm Summary to view details about the alarm.
Double-click the alarm to acknowledge it. Note that this does not affect the alarm in the
container controller.
You handle log files

While you are keeping the container it is your responsibility that the contents are treated
correct. The data log files can help you proving this.

18 Operators Manual
2.2.1 Using the Bayplan/Stackplan
Overview
You open the Bayplan/Stackplan from the menu. You can choose the overview picture or a
detail picture. This is an example of the overview picture:
In the overview, clicking a section twice brings up the corresponding detail picture:
In this picture you can click a container twice to have the Container Report displayed, or you
can use the buttons upper left, for example to zoom further in and get detailed information
about the containers.

Legends
When the overview or a detailed view is open, a summary of the colour codes and symbols
can be displayed by selecting Legends in the Bayplan/Stackplan menu:
In addition to the legends shown, another colour should be mentioned: A dark grey container
position means that it is vacant or occupied by a non-reefer, as far as REFCON is concerned.
2.2.2 Using the Container Summary
Overview
You open the Container Summary from the menu. You can choose between a number of
layouts. This is an example of the standard Summary:
You will sometimes see the special value “E0” in the Summary. The “E0” error code means
“unknown”, based on the fact that REFCON has never received any value for that field, or it
was received too long time ago (data obsolescence).
In the Summary you can click a row twice to have the Container Report displayed.

20 Operators Manual
The Container Summary menu

You should notice the special Container Summary menu available in the upper left corner:
For details on the options in the menu, please refer to the online help.
2.2.3 Using the Container Report
Overview
Selecting a container in the Bayplan/Stackplan or in the Container Summary makes the
Container Report appear:
You will very soon discover that the layout of the Container Report differs depending on the
controller type. The actual type is indicated in the caption line of the window (the top blue
line). In general, the Report displays all available information and allows you to do all available
commands and parameter changes.
ISO container
If you, as in the above example, see the type "ISO Container Report", the controller type is not
known to REFCON. All power cable transmission works according to an ISO standard, which
ensures that REFCON can communicate with any container equipped with power cable
modem, showing a smaller set of primary information. But also the ISO standard allows extra
data fields and functions. Each type of controller has it's own extensions, which have to be
programmed into REFCON. For new or rare controller types this might not have been done in
your REFCON version.
2.2.4 Handling Log Files
Overview
Being independent units, most reefer containers do their own data logging. What exactly is
logged depends on the controller type, but typically, events are logged as they occur, and
temperatures are logged periodically.

Alternatively you can have REFCON do it's own data logging, based on the data that are
periodically read via the PCT.
Inspecting controller logs

To inspect the logs in the controller you can use the optional LogMan handheld log retriever:
Connect it to the container and transfer the logs. Later, connect LogMan to the PC having
LogView installed, and inspect the data.
Handling REFCON logs

You enable or disable REFCON's own data logging in the setup window:
In the Log Files sub-window of the Container Report, you can view the collected data.
In the File Manager you can copy, move or delete log files. Open the File Manager by
selecting "Log Files…" in the Planning menu.
2.3 Guidelines for Daily Operations
Overview
While designing REFCON, assumptions were made on how you are going to use it for your
daily tasks. Many customers gave their contributions to this as well.
With REFCON you can handle a lot of containers in common, but basically you deal with each
one individually, as they are independent units.
A container's phases
Seen from your (and REFCONs) point of view, a reefer container runs through the following
"phases":
In many cases you have an amount of containers being loaded, an amount being discharged,
and an amount staying for supervision and logging – at the same time.

22 Operators Manual
2.3.1 Loading Phase
Overview
Basically, the user of the system does not have to do anything while loading containers. When
the reefer containers are connected they will automatically show up in REFCON, and alarm
supervision will begin.
Having loaded all or a reasonable number of containers, you need to do a few things. On
ships this typically happens when leaving the harbour.
Loading phase duties

After container load, please walk through the following checklist:
Step Action Result

1 Import the updated Load data file from The containers you just loaded can be
your Loading computer or Terminal matched with expected setpoint and
System (you can also do this even before location (to let them show on the Bayplan
loading the containers). screen picture).
This can optionally run automatically. If
you need to do it manually, proceed as
follows:
1. Generate the Load data file at your
Loading computer or Terminal
System.
2. Select "LoadData…" from the Planning
menu and start the file transfer.
2 On ships: Change to Sea mode. This enables the “Lost Communication”
alarms that could be due to a container
with no power.
3 On ships: Update the harbour name in This makes the Load Port field
the Current/next harbour dialog box. automatically updated with correct
abbreviation.
4 Check that the Number of Connected If you find a mismatch, please refer to
Reefer Containers is correct. Typically it Why is the Number of Communicating
must correspond to the figures in your Containers Incorrect?.
Loading manifest or Terminal System.
5 Check for errors, even if the Number of As described in The Important Match
Connected Reefer Containers is correct. with Load Data, the container ID stored in
the controller must be correct to have the
setpoint automatically checked.
6 Verify the Actual Setpoints, see How to You make as sure as possible that the
Handle Difference between Actual and cargo is treated at the correct
Expected Setpoint?. temperature.
7 Decide regarding logging, see Handling You may or may not collect data for later
Log Files. verification.
2.3.2 Discharge Phase
Overview
At some point of time, the container is disconnected "for good".
On ships: Just before you start disconnecting containers, change to Harbour mode (to
prevent the “Lost Communication” alarms).
As standard, disconnected containers stay in REFCON, mainly because it might be a

temporary disconnect. Therefore they need to be deleted. This can be done manually or
automatically.
Manual container deletion

To delete containers manually, you would enter the Container Summary Menu (see Using
the Container Summary). Here you can delete containers individually, or you might use the
“Delete non communicating containers” command. Note that it is never possible to delete
containers that are communicating. However, if you are using the RDC option, please be
aware that containers with data from RDC are non-communicating, so these could be
unintentionally deleted.
Automatic container deletion

To delete containers automatically, you have one or more options:
· In the REFCON Setup dialog box, available from the Options menu, you can enable
automatic deletion. This will make any non-communicating container disappear from
REFCON after the selected time. However, if you are using the RDC option, please be
aware that containers with data from RDC are non-communicating, so these could be
unintentionally deleted.
· If your REFCON includes the Automatic Load Data File Transfer option, you can enable this
function in the LoadData dialog box, available from the Planning menu. When the Load
data file is automatically read periodically, REFCON will check all containers after each file
transfer, and delete all containers that are not mentioned in the newest file. Note that this
works well with the RDC option.
· Even if you work with Manual Load Data File Transfer, containers that are no longer in the
file will be deleted. Of course, to be effective you must carefully remember to do the
transfer each time it is relevant.
· If your REFCON includes the Terminal Interface option, and it is running, it can take care of
the deletion automatically. Note that this works well with the RDC option.
2.3.3 Supervision and Logging Phase
Overview
While the reefer container is connected to REFCON, you will receive an alarm if an abnormal
situation occurs. In case of alarm, check the container and attempt to fix the problem.
Also, in this phase, you might give the data logging a thought. In particular, if a container
carries precious or sensitive contents, or if it caused special problems, you might wish to save
a log to prove that you kept it all right. If you want to save the log collected by the container
controller, remember to apply the LogMan before the container is disconnected! Please refer
to Handling Log Files.
Tip: In case of alarm, if you have enabled the REFCON Log Files, it might be useful to look up
the logs and trend curves and thereby get an idea of the reason for the alarm. To do so, open
the Container Report from the Alarm Summary (double-click and select the Info button), and
choose “Log Files”.
2.4 Frequently Asked Questions and Answers
Overview
This section contains a list of frequently asked questions and the corresponding answers.

24 Operators Manual
2.4.1 How to Handle Difference between Actual and Expected Setpoint?
Overview
REFCON operates with two setpoints:
· Actual Setpoint, stored in the container controller and automatically transferred to REFCON
by the power cable transmission or via the optional RDC.
· Expected Setpoint, received from Loading computer / Terminal System or typed in by you in
REFCON (not in controller).
When a container connects, the first check performed by REFCON is to compare the two
setpoints. If they differ by more than the Delta value you will get an alarm.
Delta value
The Delta value is selected in the Refcon Setup window:
Please be aware that both REFCON and the container controllers may miscalculate
Fahrenheit to/from Centigrade conversions by the last digit. To avoid that this causes alarms,
the Delta value should not be set to less than 0.2 degrees.
Checking the Expected Setpoint

If you get a setpoint difference alarm, you have to check the Loading computer / Terminal
System for mistypings or inaccuracies. You can make corrections there and retrieve the
loading data anew, or you can make a change in REFCON, from the appropriate Container
Report:
Checking the Actual Setpoint

When you are absolutely sure that the Actual Setpoint is incorrect, you can send a new
setpoint via REFCON (if supported by the controller). In the Operations window (see above),
write the correct value in the "New Setpoint" field and click Activate. After some time (maybe
minutes) the new setting should show up in the Actual Setpoint field.
If the Actual Setpoint in the container was considerably wrong, you can almost for certain

expect a claim after the container is discharged. If the container has a build-in Datalogger it is
a good idea to use LogMan to retrieve the Log files from it to keep as proof, see Handling Log
Files.
2.4.2 Why is the Number of Communicating Containers Incorrect?
Overview
From loading manifest or similar, you know exactly the number of reefer containers you are
keeping. However, it happens that the number of containers that are actually communicating
is smaller. This might be all right, but also the number might be too small. In such case you
have to find the reason.
Checklist
Think of the following possibilities:
a. The container has not connected yet. It might take an hour or more from the power cable is
plugged in until REFCON starts communicating with the container.
b. The container is not equipped with power cable modem. It should then not be included in
the expected number of communicating containers.
c. Something is wrong at the container. Please refer to the Modem Troubleshooting Guide
found in the online help and in the optional printed manual.
d. The power cable of the container is not connected. Fix it!
e. Due to electrical noise or the like, the master modem is not able to establish connection to
a container via the PCT. Try connecting the container power cable to another plug. Try
connecting another container being communicating all right to the plug. If this works, the
fault is on the non-communicating container, refer to above point c. Otherwise you might
have to call for assistance from your REFCON supplier.
f. You have one or more ghosts! Please refer to How to Handle a Ghost Container?.
Number of communicating containers

To see the number of communicating containers, click the "Number of containers" icon and
inspect the "Number of Connected Reefer Containers" reading in the dialog box.
2.4.3 How to Handle a Ghost Container?
Overview
A ghost container is a reefer container that communicates using an unexpected container ID.
When a reefer container starts communicating with REFCON, it identifies itself by the
Container ID, which has been typed into the controller. It should of course be the same as
painted on the box. REFCON attempts to find a match in the load data list (see The Important
Match with Load Data).
Checklist
Your routine schedule regarding ghost containers could be as follows:
1. Find out if you have any ghost containers at all. If not, don't proceed!
2. For each ghost, detect the physical location of that container.
3. Make 100 % sure you got the right one!
4. Fix the problem, or contact the PTI testpoint.
If REFCON finds no match, it could be a fault in the load data list. Are you sure it is updated?
Please refer to the Modem Troubleshooting Guide found in the online help and in the
optional printed manual for additional assistance.

26 Operators Manual
2.4.4 What does Owner Code LANG, LOSU, RAND or RMMU mean?
Overview
LANG, LOSU, RAND and RMMU are examples of "owner codes" that you will never find
painted on any container box. They are used for technical reasons by controllers / modems
and by the REFCON system.
For further details, please refer to the Modem Troubleshooting Guide found in the online help
and in the optional printed manual for the answer.
2.4.5 Why No Connection to Loading Computer / Terminal System?
Overview
The communication line to the Loading computer / Terminal System is established to get easy
access to the loading information file.
If there is no connection, check that the interface cable is OK and that the Loading computer /
Terminal System is running.
If still a problem, it is almost for sure a set up question (someone has changed something he
was not skilled to change) The “How to install REFCON" document describes the exact setup
on REFCON. It also gives a guidance in how to set up the Loading computer / Terminal
System.
If you can't make the interface work, it is possible to use diskettes as well.
2.4.6 Why are Reefer Containers Not Communicating with REFCON?
Overview
Be aware of reefer containers that are not equipped with power cable modems. These are of
course not able to communicate on the PCT. If REFCON receives information about such a
container from the Loading computer / Terminal system, it appears as a white position in the
Bayplan/Stackplan. If not so, it does not appear in REFCON at all.
There are other possible reasons that a container doesn't communicate, please refer to:
· Why is the Number of Communicating Containers Incorrect?
· How to Handle a Ghost Container?
· What does Owner Code LANG, LOSU, RAND or RMMU mean?

REFCON
User Interface Basics

28 Operators Manual
3 User Interface Basics

Overview
As a REFCON user, you mainly work with the containers through the REFCON PC – using its
screen, keyboard and mouse. You work through various pictures and dialog boxes that are
described in specific parts of the manual.
Certain common principles lie behind all the pictures and the way you operate the system.
First of all you will recognize principles origin from Microsoft Windows, that is, things basically
work like in most Windows applications.
But on top of this we have defined our own user interface basics, regarding how the screen
pictures are organised, and how you operate.
Screen Layout
All REFCON screen pictures are based on the Standard Screen Layout. This makes you
easily recognize the different items.
The Standard Screen Layout divides the REFCON screen into the basic areas indicated in the
following figure:
Area 1 is the standard Windows Caption Line, which is normally blue with white text. It
identifies the application, e.g. "REFCON 5.5", and the project/customer.
Area 2 is the standard Windows Menu Bar. The actual menu will depend on the context. Feel
comfortable to investigate the menu by clicking around!
Area 3, called the Variable Picture Area, is very much the largest area. This is where all lists,
mimic pictures and dialog boxes appear.
Area 4 is called the Icon Bar, see Always Visible Information.
Area 5 is the Event Line, displaying the newest "event".
3.1 Always Visible Information
Overview
All lists, mimic pictures and dialog boxes will appear in the Variable Picture Area. This means
that all the other areas of the screen are always visible to the user as long as the system is on
screen.
The always-visible areas contain menus and other control tools, making the user able to
operate the system. Further, these areas contain information that is generally useful and

User Interface Basics 29
sometimes even vital to the user. Most of this information is found in the Icon Bar.
The Icon Bar consists of easily recognized icons placed in a column in the right side of the
screen. Each icon displays some dynamical information and is at the same time a fast entry
key to a window or dialog box related to that information.
The layout of the Icon Bar varies from one REFCON system to the other; however, the icons
described below are usually included.
The LMT icon

The LMT icon displays the Local Mean Time:
· In the first line, the date: YYMMDD (year, month, day – two digits each).
· In the second line, the time: hhmmss (hours, minutes, seconds – two digits each).
Click the icon to open the Clock Settings dialog box.
The User icon

The User icon shows the user ID part of the active password.
If no password is active the icon is blank.

Click the icon to open the password Release/Setup dialog box.
The Alarms icon

The Alarms icon shows the general alarm status:
The Alarms icon shows the number of pending alarms and whether there are
unacknowledged alarms (flashing) or not (steady).
Click the icon to open the Alarm Summary.
The Containers icon

The Containers icon shows the total number of reefer-containers present in the system:
Click the icon to open a dialog box with detailed statistics.
The Setup icon

The Setup icon shows the selected temperature unit:
Click the icon to open the REFCON Setup dialog box.

30 Operators Manual
The Act.Master icon

The Act.Master icon indicates the PCT network status:
The figure in the middle of the icon shows the number of the active RMM Master. Below this it
is indicated whether the active RMM Master is right now running HDR (High Data Rate) or
LDR (Low Data Rate). The readings would normally change regularly, but rather slowly.
Clicking the icon makes it change to show other technical information. Clicking 4 times will
return to the original.
The Handling Mode icon (ships only)

The Handling Mode icon shows the actual handling mode (SEA or HARBOUR):
Click the icon to open the dialog box where you can change between Harbour and Sea mode.
The Curr./Next Harbour icon (ships only)

The Curr./Next Harbour icon shows the selected current harbour (in Harbour mode) or next
harbour (in Sea mode):
Click the icon to open the dialog box where you can change the name for the next destination.
3.2 Picture and Window Types
Overview
In the Variable Picture Area, various kinds of windows are displayed when selected by the
user. As known from Microsoft Windows, all windows have some common properties, but
there are differences as well.
The MIMIC Picture is a "full-size" window, that is, it obtains the complete Variable Picture
Area. MIMIC Pictures contain graphical depictions of the container locations, the REFCON
hardware or similar.
The List Window is also a "full-size" window. It displays one line of information for each of a
variable number of items, possibly more than can be displayed at once.
Dialog Boxes are normally smaller windows, covering only a part of the Variable Picture
Area. They give some information to the user and expect some response, like entering a
number or a text or choosing between a few options.
A special kind of Dialog Box is the Item Window. An Item Window displays all information
and offers all control facilities regarding a single Item, e.g. a measuring point or a container.
Window Type MIMIC Picture

MIMIC Pictures are windows that present graphical information. The MIMIC picture window is
fixed size and occupies all the Variable Screen Area. The picture is built up of static graphics
and dynamic items.
Dynamic items are those parts of a mimic picture that change look (e.g. colour) according to
measured values or other dynamic parameters. Clicking a dynamic item will in most cases
make the corresponding Item Window displayed.

Window Type List Window

The REFCON system includes a number of List Windows. Such a window is sketched in the
figure:
In the List Window, a number of items of identical type are listed with one item a line. The
information, which is always textual, is divided into columns, each column containing a
specific type of data, e.g. the alarm status. Clicking a row will in most cases make the
corresponding Item Window displayed.
Window Type Dialog Box

A Dialog Box is a fixed size window containing a number of so-called controls. Microsoft
Windows includes a number of types of controls, which can be found in REFCON Dialog
Boxes where suitable. The following figure shows a sample Dialog Box:
In REFCON, a Dialog Box can be modal or semimodal.

If modal, the user will not be able to click anything or otherwise select any command outside
the Dialog Box, that is, the user must respond to the Dialog Box before working with anything
else. Typically, warning messages are modal, like the following example:
Most REFCON Dialog Boxes are semimodal which means that certain commands can be
given outside the Dialog Box, while others are disabled. Typically, it will be possible to display

32 Operators Manual
the Alarm Summary on top of the Dialog Box in which the user selects parameters, but it will
normally not be possible to work in the window(s) under the Dialog Box.
Window Type Item Window

Item Windows are very much like Dialog Boxes. It can include the same kinds of controls,
however, also dynamical textual or graphical information can be shown.
An Item Window presents all information and offers all controls related to the corresponding
item, e.g. the container. If the amount of information or controls is large on an item, or if the
information and controls are preferably divided into two or more logical parts, the Item
Window might be the entrance key to sub-windows, which are of same nature as the Item
Window.
3.3 How to Operate the System
Overview
REFCON is basically operated like most Windows applications. We believe you are familiar to
this. In the following we describe the points where REFCON differs from "standard" Windows
or adds special functionality. This includes the setting of parameters internally and externally,
e.g. changing of setpoints.
REFCON is in general operated by means of the mouse/trackball and the keyboard.
Two-step Selection Principle

In several situations you need to do things in two steps. A reason for this is to reduce the risk
for mistakes or mistypings.
In List Windows and Mimic pictures, the two-step principle means:
· First you select an item by clicking it once. In the List Window the line gets highlighted. In
the Mimic, a yellow rectangle appears as a frame around the item.
· Second you open the Item Window by clicking once more.
In Dialog Boxes and Item Windows, the primary two-step principle is:
· First you change data, by changing numbers or text strings, or by clicking checkboxes etc.
The changed data are temporary – by selecting the [Cancel] button or the [Esc] key you can
abort.
· Second you click the [Activate] or the [Activate & Quit] button. This will, if relevant, validate
the data. If valid they are "applied", that is, your changes get operational.
In general the two-step principle means that if you by mistake take the first step, avoiding the
second step will ensure that nothing happens.
How to Operate a List Window

Any kind of List Window can be operated by keyboard or by mouse/trackball as described in
this section.
Changing page (= scrolling vertically) is done by means of the following keyboard keys:
[Page Up]: Moves up one page

[Page Down]: Moves down one page
[Ctrl]+[Page Up]: Moves to the beginning of the list
[Ctrl]+[Page Down]: Moves to the end of the list
Alternatively you can use the vertical scroll bar.

In most lists, it is possible to point out a specific line and open an item window or dialog box
relevant to that line. This is done by first highlighting the desired line and then giving a certain
command to open the window. Note that when opening the List Window, no line is
highlighted.
From the keyboard, highlight a line by means of the following keys:

[Tab] or [Down arrow] If no line is highlighted: Highlight the first (top) line
otherwise move the highlight one line down (if possible)
[Shift]+[Tab] or [Up arrow] If no line is highlighted: Highlight the first (top) line
otherwise move the highlight one line up (if possible).
Having highlighted, open the item window or dialog box by pressing the [F11] key.
By mouse/trackball, highlight a line by clicking it, and then open the item window or dialog box
by clicking the line once more.
To close the List Window, press the [Esc] key, or click the [X] rightmost in the List Window's
caption bar.
How to Change Input Data

Certain item windows and dialog boxes include controls by which the operator can change
data in the system.
When opening the window, the controls will display the data that are currently active. The
window can immediately be closed by clicking the [Cancel] button or by pressing the [Esc] or
the [Enter] key. Pressing the [Enter] key will always work like clicking the button that has the
bold frame.
As soon as you try to change anything, the system checks if a password must be entered. If
so, the password prompt appears. A User ID with necessary rights must be logged in to
proceed.
Data are changed by standard Windows editing rules. While editing, the system checks if the
entered data are valid, where possible and suitable. If for example the setpoint range is -30°C
to +30°C, typing '31' will cause no immediate reaction from the system because the user will
probably notice the misprint without any warning. If however the user tries to proceed with
another input field or activation, a warning message appears.
Having entered all changes, the [Activate] or the [Activate & Quit] button must be clicked in
order to make the system start using the edited values and settings. Also at this time the data
are checked, as there might be constrains between certain input data (e.g. high alarm limit
must be greater than low alarm limit). Only if the data check is successful, the data is stored
in the database and taken into use. The only difference between [Activate] and [Activate &
Quit] is that in the latter case the dialog box vanishes automatically after having accepted the
changed values.
The user can discard changes not yet activated by clicking the [Cancel] button. A warning
message appears in this case pointing out that some changes have been made that will be
lost if proceeding. Clicking [Cancel] without having made any changes simply closes the
dialog box.

34 Operators Manual
3.4 Local Settings
Overview
Selecting "Local Settings…" in the "Options" menu brings up the Local Settings dialog box:
Note that, contrary to all other dialog boxes, the Local Settings only affect the PC you are
being working at.
Automatic Password Release

In the Local Settings dialog box you can activate and deactivate the automatic release of
passwords. Also you can select the release delay: If the user does no actions for the selected
time, the password is released.
Select "Set On" to activate the automatic release of passwords.

Select "Set Off" to deactivate the automatic release of passwords.
Day and Night Colour Settings

In the Local Settings dialog box you can change between day and night colours. Night colours
are intended to be used on a dark bridge on ships.
Select "Set Day" to obtain a light picture background.

Select "Set Night" to obtain a black picture background and red text colours.

REFCON
Passwords
36 Operators Manual
4 Passwords
Overview
This section describes the standard password function used in REFCON.
Experience has shown that different customers have different views on the password idea.
Some customers find passwords needless, while others want a high security level. As shown
in the following, the REFCON password function can be set up to fit any of these viewpoints.
As the starting point, the following description covers the highest level of security.
Purpose of passwords
The purpose of the Password Function is to
· prevent unauthorized people from changing data;
· make it possible to log which operator made the change; and
· prevent data from being changed by mistake.
It is therefore possible to
· assign personal User ID and Pass Code to each individual user
· assign specific rights to each User ID.
Each time important operations are done, the User ID that was used is logged.
4.1 Passwords in Daily Use
Overview
The password is divided into two parts:
· The first part (3 characters) is called the User ID. It could be the user's initials or title.
· The second part is called the Pass Code, which always consists of three digits. It is
recommended that the Pass Code is kept secret.
It is possible to enter different User IDs from different workstations (PCs), but on one specific
workstation, there can be max one user active at a time. Further, it is possible to enter the
same User ID on more workstations at the same time, if desired.
The User Icon

The active user is shown in the icon bar to the right on the screen.
If the field is empty, no user is active.
Password Entry
When the user attempts to change data, the system checks if the active User ID gives the
necessary rights. If not so, or if no user is active, the Password Entry dialog box appears:

Passwords 37
In the dialog box, the title of the required Security Group is shown. Below this, you must type
in User ID and Pass Code as one single string of 6 continuous characters. You will see one
asterisk (*) appear for each character been typed. Mistyping will thus not be visible, but
nevertheless it can be corrected by usual means. When finished, click the [OK] button or
press the [Enter] key.
There are now the following possibilities:
· The entered password is correct and gives the required rights! The dialog box disappears
and lets you do the changing.
· The entered User ID is not defined, or the entered Pass Code does not match the User ID!
In this case, you will (maybe) hear a warning sound, all the asterisks will disappear, and you
will have to try again (or cancel).
· The password is correct, but the rights assigned to the entered User ID do not allow the
desired change! In this case, a warning will appear:
Releasing the Password

The User ID is active until it is released, that is, the user can keep on operating things without
being prompted for a password as long as the rights are sufficient.
The User ID can be released automatically and manually.
By setting up a time-out delay time in the Local Settings dialog box available from the Options
menu, the User ID is automatically released if no one attempts to do operations from that
workstation for the specified time.
By clicking the User icon in the Icon Bar (see above), or by selecting Release Password in
the Options menu, the Release Password dialog box is displayed:
In this dialog box, the user can click the [Release] button to release the current User ID, or he
can click the [Setup] button to enter the password administrator window.

38 Operators Manual
4.2 How Passwords Work
Overview
This section describes how the Password Function works.
Passwords come into question when the user does any kind of Action. Examples of Actions
would be:
· Acknowledging an alarm.
· Changing an alarm limit or a setpoint.
Note that opening and closing pictures do normally not require passwords.
Security Groups
Each individual Action that can be done in the entire system is assigned to a Security Group.
For example, the Alarm Acknowledge action would typically be assigned to the Alarm
Acknowledge Security Group.
Two groups should be specially noticed:
· The No Security Group. To this group, all Actions that need no password are assigned.
· The Superuser Group. To this group, the action to quit (stop) the program is assigned
together with possible other Actions that are "destructive" to the system.
The following list shows the Security Groups defined in REFCON:
Group Title Description of typical assigned Actions

No Security Group Activities needing no password.
Alarm Group 1 Acknowledge Acknowledge alarms in alarm group 1.
Alarm Inhibit Inhibit and Uninhibit "system" alarm points (not
related to containers).
Clock Setting Changing date and time.
Engineers Daily Operations Group Actions that require no special security, but need to
be logged.
Engineer's Protected Operations Actions that require special security.
Group
Manufacturers Not used.
Superuser Group Quitting the program etc.
It is not possible to change Security Group assignments on-line. For example, you are not
able to change some action from Engineer's Protected Operations Group to Engineers Daily
Operations Group.
4.3 Password Administration
Overview
To be able to do any secured Action, one or more passwords must be defined. On a ship, for
instance, password definitions could typically be done by the chief engineer or the chief
officer.
This password supervising person must have a certain Administrator Key to be able to open
the Password Administrator Window. It is important that only the persons that are going to
manage the passwords have access to the key.

Passwords 39
Password Administrator Key

When clicking the [Setup] button in the Release Password dialog box, you are requested for
an Administrator Key:
Note that there exist more keys, but normally you will only deal with (and have access to) the
USER ADMINISTRATOR key.
For safety reasons, you will not be able to watch on screen how the Administrator Key works.
It is recommended to keep the Administrator Key documentation in a safe place.
Password Administrator Window

When the system has accepted the Administrator Key, the relevant Administrator Window is
displayed:
To the left in the window, the list of User IDs defined by this Administrator is shown.
To the right of this, the data valid for the highlighted User ID are shown:
· The "Description" (Chief Engineer in the example) is any text to wish – it can even be
omitted.
· The "Pass Code" is described in Passwords in Daily Use. You must fill in exactly 3 digits.
· The "List of assigned Security Groups" is built up by highlighting Security Groups in the "List
of possible Security Groups" and then clicking the [Add] button to the right. It is also
possible to de-assign groups by highlighting in the "List of assigned Security Groups" and
clicking the [Delete] button.

40 Operators Manual
Below the "List of defined User IDs", it is possible to click the four buttons described below.
The Add button

The [Add] button will prompt for a new User ID:
Here, type in 3 characters and click [OK]. If the entered User ID does already exist, the dialog
box will stay open, and you must try again.
When a correct new User ID has been entered, the dialog box closes, and the new ID shows
up and is highlighted in the "List of defined User IDs". The Description, Pass Code and List of
assigned Security Groups are empty. It will not be possible to [Activate] before having typed in
a correct Pass Code and before having assigned at least one Security Group to the new User
ID.
Similarly, it will not be possible to delete the Pass Code or delete all assigned Security Groups
from an existing User ID.
The Delete button

The [Delete] button will ask you to confirm the choice:
Click [Delete] to have the User ID removed from the system. Note that all data regarding the
User ID will be lost!
The Copy button

The [Copy] button works similar to the [Add] button, with only one difference: The Description,
the Pass Code and the "List of assigned Security Groups" are copied from the "old" User ID.
The Rename button

The [Rename] button will ask you for a new ID for an existing user:
The existing Description, Pass Code and "List of assigned Security Groups" are all preserved.

REFCON
Basic container
handling
42 Operators Manual
5 Basic container handling

Overview
Depending on your equipment, on the contents of the containers, and on your "ambitions",
you can deal more or less with the containers. There are, however, certain minimum activities
that you should be aware of.
We think that your primary duty is to make sure that the cargo is treated well while you keep
the container. Your second duty is to make sure that you can later prove that the cargo was
treated well. To carry out these duties you will need to go through quite a number of activities.
The Quick Introduction intends to give you an overview of all this.
To carry out these duties, you would take advantage of the appropriate tools provided by
REFCON. Some of the tools are automatic, but might need some customisation, as described
in REFCON Setup. Basic tools are described in Container statistics and Container handling
mode (ships only).
5.1 Container statistics
Overview
REFCON provides a number of counters that are intended do help you making sure
everything is all right.
The Containers icon

The Containers icon shows the total number of reefer-containers currently registered by
REFCON:
The Container Counts dialog box

Clicking the Containers icon opens a dialog box with detailed statistics:
The Container Counts dialog is displaying statistics that cannot be changed by the operator.
Note that the third and the fourth counter are only shown on ships. The counters are:
Number of Containers This is the total count of containers known by REFCON, being the
same number displayed within the Number of Containers icon.
No. of Connected The total count of communicating containers (currently connected
Reefer Containers to REFCON by powercable or four-pole sockets).

Basic container handling 43
Number of This counter is incremented by one, every time a new container

Connections in connects to REFCON, provided that REFCON is in Harbour
this/latest harbour handling mode. This number reflects the number of newly arrived
containers loaded in the present harbour. When the container
handling mode is changed to Sea mode, this counter is frozen,
making the displayed number static until arriving at the next
harbour. When handling mode is set to Harbour again, the counter
is zeroed.
No. of Connections at This counter registers containers that connects to REFCON after
Sea having left a port (handling mode = Sea). Ideally all reefer
containers should be registered by REFCON before leaving a port,
so if this counter is incremented while in Sea mode, it indicates
that a container did not connect as it ought to do, and might need
attention. When the container handling mode is changed to
Harbour mode, this counter is frozen, making the displayed
number static until leaving the port again. When handling mode is
set to Sea, the counter is zeroed.
Note that you can only benefit by the two last-mentioned counters by carefully changing
between Harbour and Sea mode.
5.2 Container handling mode (ships only)
Overview
When loading and discharging containers in a port (Harbour mode), it is a normal occurrence
that a container looses its power supply. This usually happens when the power cable is
removed, due to the fact that the container is to be unloaded, or when all generated power is
required to operate the thrusters.
When a container is without power, REFCON looses its ability to supervise the container.
After a while, REFCON will generate a disconnect event and, if in Sea mode, an alarm. In
other words, if the handling mode is not set to Harbour mode before containers starts to
disconnect, there will be many "false" disconnect alarms.
When a container connects to REFCON the first time, REFCON will register in which port the
container was loaded. The name registered is the three letters IATA port name. You are
supposed to change the current/next port name whenever the handling mode is set to
Harbour mode – or before this.
The Handling Mode icon

The Handling Mode icon shows the actual handling mode (SEA or HARBOUR):
The Curr./Next Harbour icon

The Curr./Next Harbour icon shows the selected current harbour (in Harbour mode) or next
harbour (in Sea mode):
Click the icon to open the dialog box where you can change the name for the next destination.

44 Operators Manual
The Harbour/Sea Mode dialog box

Clicking the Handling Mode icon or the Curr./Next Harbour icon opens the following dialog
box:
Here you can:

· Change between Harbour mode and Sea mode.
· Select the current or next port's IATA code. The port name can be specified manually by
entering three characters from the keyboard, or it can be selected from the port library by
clicking the down arrow button.
5.3 Container Delete Function
Overview
As long as a certain reefer container is connected to REFCON, a corresponding Container
Data Record exists in the REFCON database. Even if the container is disconnected (= stops
communicating), the Record is kept because the disconnection could be temporary.
When a reefer container has been discharged, the Container Data Record must be deleted.
You can delete a container manually from the Container Summary, however, when REFCON
receives Load data from the Loading Computer/Terminal System, normal practice will be to
have deletion performed automatically.
Please also refer to the Automatic Container Deletion Setup describing the timer-based
deletion.
The Automatic Deletion mechanism

The Loading Computer/Terminal System knows when the container is leaving the ship or the
terminal. It informs REFCON about this in one of the following ways:
· When the Load data file transfer function is used - automatically or manually - the Loading
Computer/Terminal System simply omits the discharged container in the next file transfer.
· When the optional Terminal System Interface is enabled, the Terminal System sends the
Reefer Delete message to REFCON. This is done whenever relevant – one message for
each container.
When REFCON receives either of the above left-events, the corresponding Container Data
Record is handled by either the queued deletion function or the immediate deletion function
as described below.
The queued deletion function

On ships and in specifically selected terminals, the left-event causes the Container Data
Record to enter the deletion queue.
It stays in the queue until the container has stopped communicating and all possible alarms
related to the container have been acknowledged.
If these conditions are already fulfilled when it enters the queue, it is deleted immediately.

The Loading Computer/Terminal System may - at any time after reporting the container
discharged - include the same container ID anew. This could typically happen when the
container is moved. In this case, the container is immediately removed from the queue
without being deleted.
The advantage of the queued deletion function is that containers can be reported
"discharged" at any time, even long time before they are in fact disconnected. They will then
stay alarm supervised as long as possible.
The immediate deletion function

In terminals where not otherwise specifically selected, a Container Data Record is
immediately deleted upon the left-event, even if the container is communicating or has
unacknowledged alarms.
It is foreseen that the Loading Computer/Terminal System can report a container discharged
before it is in fact disconnected and therefore is still communicating. Deleting the Record in
this case will break the communication, but if the container stays connected, it will
automatically attempt to restart the communication, which would cause a new Record to be
created. To avoid this, deleted containers are added to the "List of Temporarily Blocked
Containers". You can inspect the list in the Status dialog box (available from the Planning
menu or, if enabled, the Terminal menu):
While on this list, the container is prevented from restarting the communication.
Any deleted container stays on this list for 3 hours. If still connected after this time, it will
cause a new Container Data Record to be created. Later, when the container is actually
disconnected, you must delete this Record manually from the Container Summary.
The Loading Computer/Terminal System may - at any time after reporting the container
discharged - include the same container ID anew. This could typically happen when the
container is moved. In this case, the container is immediately removed from the "List of
Temporarily Blocked Containers", and the communication will restart as soon as possible.

46 Operators Manual
5.4 REFCON Setup
Overview
The REFCON Setup dialog box is used for setting up system parameters.
As you see the dialog box consists of seven sections as described below.
The Setup icon

The Setup icon shows the selected temperature unit, either degrees Celsius (°C) or
Fahrenheit (°F):
Clicking the icon opens the REFCON Setup dialog box.

5.4.1 Library Setup
Overview
In the Library section of the REFCON Setup dialog box, three libraries are specified. On
ships, the third library is called "Port" while on terminals it is called "In/Outbound".
The libraries are:
Contents Library A list of the most commonly used contents descriptions. The library
can be used when noting the contents of a container.
Note Library A list of the most commonly used notes. The library can be used when
making additional notes on the contents of a container.
Port Library (ships A list of the most frequently used port names. One example of using
only) the port library is when the operator is setting the Current/Next
Harbour in the Harbour/Sea Mode dialog box.
In/Outbound A list of the most frequently used inbound and outbound designations.
Library (terminals This library can be used in the Container Report.
only)
In many cases, the Library function is useful when changing an input field. Instead of
manually typing in a text string, simply select from the Library! Note that to do so you need to
prepare the Library in advance, once for all or as the needs occur.
Editing the libraries

To add a new entry to a library, simply move the text cursor to the library's text field and type
the new text. For the Port Library you need to type exactly three letters, while for the other
libraries there are no such restrictions. Having completed, click the [Insert] button related to
the Library.
The libraries have a limited size as regards the number of entries. If the library is full, one text
must be deleted before a new text can be inserted. To delete a text, click the down arrow
button of the library, select (highlight) the entry to be removed, and click the [Delete] button.
When all corrections have been made, click the [Activate] or the [Activate & Quit] button, to
make the changes permanent.
5.4.2 Alarm Setup
Overview
In the REFCON Setup dialog box you see two Alarm Setup sections.
Alarm Setup PCT / General

In the first Alarm Setup section, two parameters are specified affecting containers
communicating on the PCT.

48 Operators Manual
The parameters are:
Disconnect delay This timer is used to avoid unwanted disconnect

Event/Alarm logging events/alarms. Only if REFCON has been unable to
communicate with a container for more than the time
specified, the container is regarded as disconnected. If a
container disconnects in Harbour mode, an event is
generated, whereas an alarm is generated if the handling
mode is Sea.
On terminals, disconnect alarms do not occur.
Delta temp. between When a container connects, REFCON compares the
Expected Setpoint and Expected Setpoint and the Actual Setpoint. If they differ by
Setpoint more than the Delta value you will get an alarm. Please be
aware that both REFCON and the container controllers may
miscalculate Fahrenheit to/from Centigrade conversions by
the last digit. To avoid that this causes alarms, Delta should
be set to no less than 0.2 degrees.
Alarm Setup Fourpole

In the second Alarm Setup section, three settings are specified affecting fourpole containers
only.
The parameters are:
Temperature Alarm Due to the fact that a container may have been without power
Inhibition after for some time before loading, temperatures within the
Connect/Defrost container might be out of range. When a fourpole container
connects to REFCON for the first time, and after defrost, the
container is given time, according to this delay, to normalise
its temperatures. Only after the delay time has elapsed,
Inrange alarms are given by REFCON.
Defrosting too long alarm If enabled, REFCON releases an alarm if any fourpole defrost
signal stays active for more than the selected time.
5.4.3 Automatic Container Deletion Setup
Overview
In the Automatic Container Deletion section of the REFCON Setup dialog box, you can enable
or disable timer-based automatic container deletion.
The REFCON database includes an amount of information for each container. Even when a
(communicating) container is disconnected, this information stays in the database – for two
reasons: It could be just a temporary disconnection, or you might need the data for your
record. But when you do certainly no longer keep the container, and you have certainly saved
data as needed, the container must be "deleted", that is, the corresponding data are removed

from the database. While not "deleted", the container will appear in the Bayplan and in the
Container Summary – so if you don't make sure containers are "deleted", you will very soon
have a confusing mix of relevant and irrelevant containers.
Regarding ships: Note that containers are automatically deleted by the timer-based function
only if REFCON is in Harbour mode.
Connection to Load data based deletion

Note that the timer-based automatic deletion function described in this topic is an addition to
the Container Delete Function based on data from the Loading Computer/Terminal System.
If the Load data based function runs, you should consider if you want the timer-based function
to run as well:
· Containers that are communicating on the PCT even they have never been reported by the
Loading Computer/Terminal System (for example a ghost container, see How to Handle a
Ghost Container?) will be automatically deleted only if timer-based function is enable -
otherwise you will have to delete these manually.
· Containers that stop communicating, maybe due to errors, are automatically deleted if the
timer-based function is enabled, even though they are still present according to the Loading
Computer/Terminal System.
If the Load data based function does not run, we strongly recommend that you use the timer-
based function, except if you use the optional RDC...
Special RDC precautions

If RDC (REFCON Data Collector) is a part of your REFCON system, and you do use the
RDC, it is strongly recommended that you disable timer-based automatic deletion. Containers
receiving data via the RDC are non-communicating, so they would be deleted after the
selected delay. If the container is staying on board during the harbour visit, this would be
inexpedient. Therefore, when using RDC you need to delete containers manually – unless you
take advantage of one of the optional automatic functions, named Automatic Load Data File
Transfer on ships and Container Delete Function when the Terminal Interface is applied. Both
functions will automatically delete irrelevant containers.
Deletion delay
If you enable automatic deletion, you also need to select the delay labelled "Automatic
deletion of container after disconnect".
Note that there are two delays involved:
1. The container is actually unplugged. Then, after the time "Disconnect delay Event/Alarm
logging", it is noted "disconnected" by REFCON.
2. Next, after the time "Automatic deletion of container after disconnect", the container's data
are removed.
Please notice that this delay has no influence on fourpole containers, which are deleted
immediately in Harbour mode when disconnected.

50 Operators Manual
5.4.4 Data Obsolescence Setup
Overview
In the Data Obsolescence section of the REFCON Setup dialog box, you see two values
relevant to this function.
The Data Obsolescence function makes sure that values received from containers, being
shown in screen pictures and used in logs, are up to date:
· If no data was received from the container via the power cables for 180 minutes, the
symbol “E0” will be shown on the screen and in the log, indicating “value unknown”. You
can’t change this setting.
· However, if data is received via RDC, the second time setting (24 Hrs in the above
example) is used in stead. You can change the second setting. Example: You type in data
on the RDC handheld for a certain container at 2 PM. At 3 PM you plug in the RDC
handheld in the docking station and transfer data. In this case, if you do not repeat this
operation within 24 hours, the value readings will change to “E0” at 3 PM the next day
(provided that you selected 24 hours above).
5.4.5 REFCON Log Files Setup
Overview
In the REFCON log files section of the REFCON Setup dialog box, you can enable or disable
the log files generated by REFCON.
Temperature logging
Select the "REFCON logfile enabled" checkbox if you want a separate REFCON log file to be
generated for each PCT container. These log files will hold temperature loggings for each
connected container.
The contents of the log will depend on the container type, but will usually hold loggings of
Actual Setpoint, Supply temperature and Return temperature.
The interval by which REFCON is to log these data is specified in the "REFCON logfile
sample interval" field.
The name of the REFCON log file is the container ID + _REFCON, e.g.
"MAEU1234567_REFCON".
Event logging
Select the "Container Eventlist logfile enabled" checkbox to have a separate eventlog file
generated for each PCT container. The log will hold the same information as the system
eventlist, except that the eventlist log for a container will hold loggings only concerning the
container.
The name of the Eventlist log file is the container ID + _EventList, e.g.
"MAEU1234567_EventList".

House-keeping required
Please notice that when enabling these log files, REFCON uses space on the computer
harddisk to store the logs. Because of this, the operator must remove / delete log files by
means of the File Manager at regular intervals, e.g. when leaving a port.
5.4.6 Unit Setup
Overview
In the Unit section of the REFCON Setup dialog box, you select the unit of measure for
temperatures.
All displaying and printing of temperatures will be in the preferred temperature unit.

REFCON
Container Report
54 Operators Manual
6 Container Report
Overview
The Container Report allows you to work with one single specific reefer container. It includes
all available information from and about the container, and it offers all possible commands
and parameter changes.
The amount of available information and possibilities depends on the connection type and
the controller type. The Container Report automatically adapts to both, that is, REFCON
detects the type and adjusts the contents of the Report correspondingly.
Controller manufacturers do, from time to time, release new controller types, and sooner or
later they will connect to your REFCON. As the controller type was unknown at the time when
your REFCON was installed, REFCON will categorize it as an ISO Container. The ISO
10368:1992(E) standard decides a set of data that any controller communicating on the
power cables must support. This is the set of data presented in the Container Report for an
ISO Container.
In contrary, when the controller type is known to REFCON, there normally is an extended data
set available, being different from one type to another. REFCON supports the complete set,
giving you the optimal means to handle the container.
Important note: You must think of the Container Report as nothing but a remote operating
panel, similar to the one at the container. In this manual, we are not able to tell you exactly
what happens in the controller when you enter commands and parameter settings. If you are
in doubt, please consult the container manual.
Container Connection Types

It is expedient to have the following connection types in mind:
From left to right, the potential amount of information increases.

Container Report 55
Four pole 3 status signals only.

RDC States and measured inputs, manually collected.
PCT, ISO PCT running the basic ISO 10368:1992(E) protocol, transferring a
certain minimum of information.
PCT, manufacturer PCT running an extended ISO 10368:1992(E) protocol, transferring
specific all available information, depending on the controller type.
For all connection types, there can be additional information available from the Loading
Note that in the Container Report, an RDC container is called a "non-RMM container".
Non-RMM Container
It will happen that you see the connection/controller type Non-RMM Container. RMM is short
for Remote Monitoring Module, being another designation for a power cable modem. Hence
we talk about a container without a power cable modem – but this is not the whole story!
Non-RMM containers can occur if REFCON is connected to a Loading Computer/Terminal
System. From time to time (as you decide), REFCON receives a load data file, including basic
information about all reefer containers (container ID, location etc).
A container on the new list might already be communicating. If it is not so, it is given the
stamp "non-RMM container". In many cases this stamp is temporary, because if/when the
container starts communicating, the stamp is replaced by the actual connection/controller
type. Note that even if the container later stops communicating, the stamp is not changed
back!
So, a non-RMM container is a reefer container reported by the Loading Computer/Terminal
System that never/not yet started communicating. There can of course be several reasons
why it is not communicating:
· It has no power cable modem and is therefore not able to communicate.
· It has not yet been loaded into the ship/terminal.
· It has not (yet) been plugged in.
· It carries non-refrigerated cargo and will therefore not be plugged in!
· It communicates using another container ID than the one painted on the container – we call
this a ghost container. This is a fault on the container.
· The container ID received from the Loading Computer/Terminal System is wrong.
When you have checked up that all containers that should communicate actually do so, you
might still have an amount of non-RMM containers. You might deal with these by means of
the RDC option (REFCON Data Collector).
Error Codes
In the Container Report, the Container Summary and elsewhere, you may see the error code
E0:
Data type Possible reasons for error code E0

Controller data · The sensor does not exist.
· No data were ever received from the container, neither by network
transfer nor by the optional RDC. You might just have to wait, if the
container not yet connected.
· Data went too old (obsolescence) – data once were received, but has
not been so within timeout.
· Sensor went unstable or disconnected – data once were received, but
now the controller (or RDC) reports something wrong.
Non-controller No data were ever received from the Loading Computer/Terminal System
data or typed in by the user.
Other error codes, like E1, might occur in rare cases. They should be interpreted like E0.

56 Operators Manual
6.1 Container Report Main Page
Overview
Selecting a container in the Bayplan/Stackplan or in the Container Summary makes the
Container Report appear:
The details of the Container Report differ depending on the connection/controller type;
however, you always find the areas indicated in the figure. The actual connection/controller
type is indicated in the caption line of the window.
The Button Bar

Some connection/controller types, such as the four pole container, do offer no more
information to REFCON than can be displayed in the Container Report Main Page at once.
Others, such as a Thermo King MPC3000 controller, have much more data available.
Therefore the Container Report is organised as a Main Page and a number of Sub-pages.
You find references to the Sub-page descriptions at the top of this page.
Clicking a button in the button bar at the top will make the corresponding Sub-page displayed.
Buttons that are not available have a dark shade – nothing will happen if such a button is
clicked.
The Primary Data Area

The following information is found in this area:
· The Container ID – being write-able only in the case of a four pole container, while for all
other types it is the unique read-only key identifying the container.
· The Communicating status is "Yes" or "No". For four pole containers it is "Yes" though
these are not actually communicating. For RDC containers it is "No".
· The Alarms count shows the number of alarms actually reported by the container controller.
· If you check the "All alarm inhibit" checkbox no more alarms will occur from this container –
but they will still occur on the controller!
The Setpoint/measurements Area

In the right part of the Container Report Main Page you can inspect the actual values of the
temperature setpoint and the primary temperature sensors. Also you can see what is the
expected setpoint – in many cases this information comes from the Loading Computer/
Terminal System.
Supply and Return temperatures are measured at the cooling unit. The possible USDA
temperatures are measured by probes that can be placed within the cargo.
Note that for four pole containers, the area shows the state of the 3 status signals in stead.

Container Report 57
The Additional Data Area

The larger lower left part of the Container Report Main Page displays data that do not
originate in the container controller itself. In general these data come from the Loading
Computer/Terminal System or are typed in by an operator.
You will observe that the details of this area depends on whether you are on a ship or in a
terminal, and whether it is a four pole container or not. For four pole containers you can read
the unique identification of the plug to which the four pole cable is connected.
6.2 Sub-page Load Data
Overview
The "Load Data" sub-page shows a sub-set of the container's data as a list:
All data shown in this list are also available in other Container Report pages, so probably you
will never be using this list!
Please do not confuse the list title "Load Data" with the data received from the Loading
Computer/Terminal System. The two have very little in common!
Opening the Sub-page

You open the sub-page from the Container Report Main page by clicking the "Load Data"
button:
6.3 Sub-page Measurings
Overview
The "Measurings" sub-page lists all signal-like data regarding the container:

58 Operators Manual
The contents of the Measurings list differ from one connection/controller type to another. In
general the page lists all signal-like data available from the container as well as a number of
data normally originating from the Loading Computer/Terminal System, for example, the
Expected Setpoint.
For four pole containers and Non-RMM containers, a few or no data are available. In these
cases the list has been extended with signal-like records where you can type in data. If you
use the RDC option, data can be entered via the RDC hand-held computer.
Error codes might occur, as in the above example.

You open the sub-page from the Container Report Main page by clicking the "Measurings"
button:
Defining alarm limits

For analog input values, you can normally select a low alarm limit and/or a high alarm limit. If
you do so, REFCON will alarm supervise the input and release an alarm if the value exceeds
a limit. This happens independently of the controller. It works even in the case that the Value
is typed in manually (maybe via RDC). A limit reading "E0" disables the alarm check at that
limit.
Editing data
Certain fields in the Measurings list are editable. Simply double-click a field to edit it. If it is not
editable, the double-click is ignored – though the field gets grey, but this means nothing.
Double-clicking an editable field changes to edit mode: A white rectangle appears "on top" of
the field, and you see the text cursor flashing. Type in your value, or correct the existing.
Terminate by pressing the [Enter] key, or return to the old value by pressing the [Esc] key.
Changed values are active immediately – note that they are never sent to the container in this
case.
Log-in inhibit
The "Inh" (Inhibit) column might show an "L", which is short for "Log in inhibit". It indicates that
the alarm suppression timer is running, avoiding alarms because the container might have
been without power for some time before connection.

Container Report 59
6.4 Sub-page Log Files
Overview
The "Log Files" sub-page lists the two log files that can be generated by REFCON:
Select the relevant "View log" button to inspect the log. For further details on this, please refer
to Log Viewing

You open the sub-page from the Container Report Main page by clicking the "Log Files"
button:
6.5 Sub-page Alarms
Overview
The "Alarms" sub-page lists the actual alarm(s) related to this specific container:
The container alarm list is used exactly as the system Alarm Summary, meaning that alarms
can be inspected and acknowledged. Do, however, note that unacknowledged alarms are not
flashing here. In stead, look for the "--" in the "Ini." column.
Note that in the system Alarm Summary, the container appears in one line only, no matter the
number of alarms on the container. The Container Alarm List is the tool for viewing the
details.

60 Operators Manual

You open the sub-page from the Container Report Main page by clicking the "Alarms" button:
Acknowledging
Double-click a line to acknowledge it. This makes the following dialog box appear:
Here you can select:

· [Marked] to have the highlighted alarm acknowledged.
· [Whole page] to have all visible alarms acknowledged.
6.6 Sub-page Communication
Overview
The "Communication" sub-page shows system information:
You would typically open this sub-page in connection with communication errors between the
reefer controller and REFCON. The dialog box shows the following information:
· Communication: Yes or No.
· RMM serial number: The serial number of the power cable modem at the container.
· Connected to master number: Which power cable master modem that communicates with
the container.

You open the sub-page from the Container Report Main page by clicking the
"Communication" button:

Container Report 61
6.7 Sub-page Operations
Overview
The "Operations" sub-page lists the commands and parameter changes relevant to the
specific container:
The contents of the Operations dialog box differ from one connection/controller type to
another. In general the page lists all commands and parameter changes that are accepted by
the specific container. Below you find descriptions of the fields that can occur in the
Operations dialog.
Important note: You must think of the Container Report as nothing but a remote operating
panel, similar to the one at the container. In this manual, we are not able to tell you exactly
what happens in the controller when you enter commands and parameter settings. If you are
in doubt, please consult the container manual.

You open the sub-page from the Container Report Main page by clicking the "Operations"
button:
Expected Setpoint Field

In the Operations dialog box you will normally find the following field:
The Expected Setpoint is typed in by you or received from the Loading Computer/Terminal
System. It is compared to the Actual Setpoint, if known. If the difference is greater than the
delta value selected in the REFCON Setup, an alarm is released. This field is the only one in
the Operations sub-page that is not sent to the container – it is included for easy compare.
New Setpoint Field

In the Operations dialog box you will in many cases find one or more fields for changing
setpoints. The most common example is the temperature setpoint:
The "Actual Setpoint" is the value read from the controller, for easy compare.
To change the setpoint in the controller, enter the desired value in the "New Setpoint" field,
and then click the [Activate] or the [Activate & Quit] button. The following happens:
· The "Expected Setpoint" automatically changes to the "New Setpoint" value.
· The selected value is sent to the controller, as soon as possible.
· If accepted by the controller, the "Actual Setpoint" changes, reflecting the selection. You
might have to be patient!

62 Operators Manual
Rename Container Field

In the Operations dialog box you will normally find the following field:
To change the Container ID of a container, type in the 4 letters and 7 digits painted on the
container box, and then click the [Activate] or the [Activate & Quit] button. The new ID is sent
to container. If accepted it is stored in non-volatile memory, and the power cable
communication on this container is restarted.
Note that it is extremely important that the selected ID matches the print on the container
box. Normally, ID changes come into question only for ghost containers. You must make
sure the container you are dealing with is the right one!
Datalogger Time Field

In the Operations dialog box you will in some cases find a field for changing the time running
in the datalogger on the container:
You must carefully follow the syntax described above the input fields: Four-digits year, slash,
two-digit month etc. Example: "2003/03/03" and "06:55".
Defrost Selection Fields

In the Operations dialog box you will in many cases find one or more fields for operating
defrost. Basically there are two versions:
In the left version you can make defrost start immediately by checking the "Start Defrost"
checkbox. When the defrost has completed it will not start again until a user selects so.
In the version to the right you can enable automatic defrost. In the above example you select
the interval from a drop down list of options. In other cases you simply type in the number of
hours.
PTI Test Selection Fields

In the Operations dialog box you will in some cases find one or more fields for running test
functions. Here, four examples are shown:
In general you start the PTI or function test by checking the checkbox or selecting a radio
button, and then clicking the [Activate] or the [Activate & Quit] button.

Container Report 63
As you see above, the dialog box in some cases inform you if the test is "static" or "dynamic".
If you are not sure, assume it is dynamic, that is, the conditions inside the container might be
affected by the test.
Set Trip Start Field

In the Operations dialog box you will in some cases find a field for setting trip start:
Select the checkbox and click the [Activate] or the [Activate & Quit] button to initiate the trip.
6.8 Sub-page Utility
Overview
The "Utility" sub-page can be used to generate an alarm on the container:
Enter a descriptive text of max 30 characters, check the checkbox, and click the [Activate] or
the [Activate & Quit] button – and you will immediately have the alarm. The alarm description
will be the container ID having your selected text appended. Having acknowledged this, you
can remove it by unchecking the checkbox.
You should avoid changing the Alarm text while the alarm is pending, because it will change
the alarm description in the Alarm Summary and the Event List. This could be quite confusing
when inspecting the events.

You open the sub-page from the Container Report Main page by clicking the "Utility" button:

REFCON
The Container
Summary
66 Operators Manual
7 The Container Summary

Overview
The Container Summary is a list showing data for a number of reefer containers. It can be all
containers, or a specified subset.
Each line in the Summary represents one container. Because of the limited length of a line,
not all information for a container can be displayed. Therefore, REFCON normally provides
two or more versions of the Summary. Each version has a unique combination of columns
and thereby shows a specific part of the information available for each container.
Colour code of the list

The Container Summary is marked by a green ribbon at the top of the list.
Opening the Container Summary

All versions are available from the Container Summary menu, as shown in the example:
The Container Summary window

An example of the Standard Information version is shown here:
In the Container Summary it is possible to double-click a line to have the corresponding

Container Report displayed. You can also use the up and down arrow keys etc to have a line
highlighted, and then press F11 to open the Report.

The Container Summary 67
Selecting "Print Current Window" from the Service menu, or pressing the [F9] key, will print
the Summary.
Note that the Container Summary is automatically updated, that is, containers appearing or
disappearing will be reflected.
In general the reading "E0" means "value unknown". For detailed information, please refer to
Error Codes.
7.1 Container Summary Columns
Overview
In the various versions of the Container Summary, you find subsets of the following possible
columns.
Column header
/abbreviation Explanation
A.Setp Actual Setpoint according to container controller, in selected unit of
measure. Read via PCT, RDC or manually typed in.
Al Alarm Status. Empty field = Normal. Red square = Acknowledged
alarm(s). Square flashing red/yellow = Alarm(s), at least one not
acknowledged.
Alms No. of alarms on this container.
Client Max 4 characters identifying the owner, data received from Loading
Computer / Terminal System.
Com Communication Status, Yes or No. On PCT, "Yes" means that REFCON
has connection to the container. On fourpole, "Yes" means that the
fourpole plug is plugged in.
Commodity Short description of the goods in the container.
Comp Compressor Running, fourpole status signal.
Container ID 4 letters + 7 digits.
D.P Discharge Port, 3 letters code.
Data “Yes” means that data was received from the container via PCT within
the latest 90 minutes.
“RDC” means that data was received from the container via RDC within
the latest ZZ hours, ZZ being a number selected by the user, default 24
hours.
“No” means neither of the above, that is, data never was received, or it
was too long ago (data obsolescence).
Defr Defrosting, fourpole status signal.
Drain "Open" or "Closed".
Err % Shows how many of the above counted messages (column "Msg Cnt")
that did fail. Power cables are quite noisy, so a positive error rate must
be expected, however, if it is very high it might indicate a problem that
should be solved.
Note that the percentage changes very slowly, so if you correct an error
you might discover that it takes hours for the percentage to reach a low
level.
E.Setp Expected Setpoint, temperature setpoint according to Loading Computer
/ Terminal System, or manually typed in (in REFCON). Should match
A.Setp.

68 Operators Manual
Column header
/abbreviation Explanation
Gr. Alarm Group.
Hum. Humidity.
In R In Range, fourpole status signal.
Inbound Identification of the means of transport taking the container to the
terminal.
Inh Inhibit Status.
L.P Load Port, 3 letters code.
L.Time Load Time, YYMMDD hh:mm.ss = Year Month Day Hour Minute Second.
Location The container's location.
Logs Four characters, of which the first two are not used. The last two
characters relate to the log files that can be generated by REFCON.
o means that this log file has not (yet) been created
E means that an Event log file is present
T means that a Temperature log file is present
Example: "oooT".
Master The number of the RMM Master that communicates with the container.
Modem The type of modem installed on the specific container.
Modem Class The class of modem installed on the specific container: HDR (High Data
Rate) or LDR (Low Data Rate).
Modem Serial The serial number of the container modem. “E0” means that it is
unknown.
Msg Cnt Shows the total number of PCT messages sent to the container since it
logged in (if it logs out and logs in anew, the counter is reset).
Note Text string received from RDC or typed in manually.
Outbound Identification of the means of transport expected to take the container
from the terminal.
Plug Fourpole plug number.
Remarks Text string typed in manually.
Return Return temperature according to container controller, in selected unit of
measure.
Software A code identifying the software version running in the container controller.
Station ID Identification of hardware substation with fourpole plug.
Supply Supply temperature according to container controller, in selected unit of
measure.
Type The reported type of the container controller.
Unit Unit of ventilation.
Vent. Ventilation.

7.2 Container Summary Special Menu
Overview
In the Container Summary, a special menu is available:
In the menu you can Close the Container Summary or select one of the options described
below.
Pick and Sort in Container Summary

Selecting "Pick & Sort" in the Container Summary special menu makes the following dialog
box appear:
In the first column, "Col. Dec.", the names of the columns in the actual Container Summary
version are listed.
In the second column, "Pick out Options", you can enter criteria to specify a subset of the
containers to be displayed, see Pick Out Criteria Syntax. Only containers matching all criteria
will be displayed. The "*" criterion means "include all".
In the third and fourth column you can select the sorting order. Click the [<] and [>] buttons to
change priority. When a row is included in the sorting decision, its priority is shown as a
number between the [<] and [>] buttons. Priority = "1" means "most important". The
containers are sorted alphabetically / in numerical order. Checking "Backward" will make it
reverse order.

70 Operators Manual
Find Function in Container Summary

Selecting "Find" in the Container Summary special menu makes the following dialog box
appear:
The find function will look through the containers presently shown in the Container Summary,
looking for one matching the selected Find Option. Note that you can only enter one option at
a time.
If a match is found, it is highlighted, otherwise a message shows up.
If the "Search from cursor" checkbox is selected, the search starts from the already
highlighted container; otherwise it starts from the top of the Summary. The search direction is
always from top and down.
The Find Option syntax is exactly like the Pick Out option syntax.
Deleting Containers in Container Summary

In the Container Summary special menu you find two commands for deleting containers:
· "Delete Selected Container" will affect the highlighted container only (white text on blue
background). Remember to highlight a container first.
· "Delete Non Comm. Containers" will affect all containers reading "No" or “E0” in the "Com"
column.
Selecting any of these commands will display a warning like this:
Click [OK] to proceed. Please note:

· You can't "undo" the command!
· Containers that are communicating ("Com" = "Yes") can't be deleted.
· Deletion takes some time. You may continue your work in the meanwhile.
· Containers with data from the optional RDC are always non-communicating, so be careful
when using the "Delete Non Comm. Containers" function.

7.2.1 Pick Out Criteria Syntax
Overview
When selecting pick out criteria in the Pick and Sort dialog box, you must be aware of the two
basic data types, numeric data and text string data. Different rules apply to these two types,
however, on certain criteria you can use both set of rules. In general, if you enter an incorrect
criterion, you will get a message like this:
Combining criteria
No matter the data type, it is possible to select a combined criterion by applying the AND or
the OR operator.
· "Criterion 1 OR criterion 2" will pick out all containers that match one of the two criteria.
· "Criterion 1 AND criterion 2" will pick out all containers that match both criterion 1 and
criterion 2.
Example: ">=1.5 AND <=2.5" will pick out values in the range 1.5 to 2.5.
Text string field syntax

In case of a String field, the question mark "?" can be used as "Don't Care" character
(wildcard). For example, specifying "MAEU?32" would Pick Out strings like "MAEU432" and
"MAEUk32", but not "MAEU32" nor "MAEU4332".
The asterisk "*" can be used as "Don't Care" marker. When "*" is found in the criterion string,
the Pick Out function will first look for the piece of text preceding the "*". When found, it will
check if the piece of text succeeding the "*" is found somewhere later in that particular field.
For example, specifying "MAEU*32" would pick out any of the strings "MAEU432",
"MAEUk32", "MAEU32" and "MAEU4332".
Note: Text string criteria are case sensitive.
Numeric field syntax

In a numeric field the operators <, >, <=, >= and <> can be used.
< means "less than".
> means "greater than".
<= means "less than or equal to".
>= means "greater than or equal to".
<> means "different from".
Example: Specifying "<10" would pick out all the containers where the field has a numeric
value less than 10.
Special case: Alarm Status criterion

In the Alarm Status field:
· Insert any numeric value to display containers that are not in alarm only.
· Insert any numeric value preceded by the "<>" operator to display containers that are in
alarm only.
Example: "<>1" displays all containers in alarm.

REFCON
Bayplan - Stackplan
74 Operators Manual
8 Bayplan - Stackplan
Overview
REFCON provides a set of graphical container overview pictures. On ships these are called
Bayplans, while on terminals they are called Stackplans. They are accessed through the
second entry in the main menu, called Bayplan on ships and Stackplan on terminals. The
layout of these graphical pictures is tailored for the specific application.
Generally there is no difference between a bayplan and a stackplan. In the following you will
find illustrations origin from a typical ship application – these should just be seen as
examples.
The pictures display all container positions or just all reefer container positions, as decided by
the owner.
Zoom levels
In general the bayplans/stackplans are presented in three zoom levels. The two top levels are
available from the Bayplan/Stackplan menu, as shown in the example:

Bayplan - Stackplan 75
Bayplan - Stackplan Overview

Select "Bay Overview"/"Stack Overview" in the Bayplan/Stackplan menu to have the container
overview picture displayed.
In the overview you can click a bay/stack twice to have the detail picture displayed.
Legends
When the Bayplan / Stackplan overview or a detailed view is open, a summary of the colour
codes and symbols can be displayed by selecting Legends in the Bayplan/Stackplan menu:
The legends can be explained as follows. Note that many of the legends can be combined.
Symbol Legend text Explanation

Dark grey - The position is vacant or occupied by a
non-reefer, as far as REFCON is concerned
White Non RMM Slave The container was included in load data but did
not (yet) start communicating

76 Operators Manual
Symbol Legend text Explanation

Green Communicating The container is or has been communicating,
and the controller type has been determined.
Small x Non communicating The container is not communicating at the
moment. Note that there is some delay in the
change of this state.
Small * Position conflict Two or more containers have been given the
same location
Red or Alarm There is at least one alarm on the container. If
red/yellow flashing flashing at least one has not been
acknowledged
Rectangle half size 20 ft. Container The location is/can be occupied by a 20 ft.
aft/for reefer container
3 small squares Four pole… Indicates the 3 digital inputs from a 4pole
container. Blue means active signal (24V)
8.1 Bayplan - Stackplan Detail Pictures
Overview
Click twice in the container overview picture, or select a bay/stack in the Bayplan/Stackplan
menu, to have the container details picture displayed.
The information on this, the second, zoom level is the same as in the overview picture,
however, row/tier numbering or similar has been added, and you have a small panel of
buttons upper left.
In the zoom level 2 picture, you can click a container twice to have the Container Report
displayed.

Bayplan - Stackplan 77
Navigation buttons
The two navigation buttons:
will display the previous/next bay/stack.
Zoom buttons
The two zoom buttons:
will zoom out and in, respectively.
Zoom level 3
Selecting the Zoom in button will change to zoom level 3:
At zoom level 3, five lines of information are shown for each container:
Line If RMM Container If Non-RMM Container If 4-pole container

1 Container ID Container ID Container ID if
available
2 Actual setpoint A.Set: E0 – setpoint is Compressor Run, Yes
unknown or No
3 Supply temperature Sup: E0 – temperature Defrost, Yes or No
unknown
4 Return temperature Ret: E0 – temperature In Range, Yes or No
unknown
5 Ships: Load / Discharge port Load / Discharge port Load / Discharge port
Terminals: Inbound / Outbound Inbound / Outbound Inbound / Outbound
In general the reading "E0" means "value unknown". For detailed information, please refer to
Error Codes.

REFCON
The Alarm System

80 Operators Manual
9 The Alarm System

Overview
A vital part of REFCON is the Alarm System. Please look at the following sketch:
There are in fact three main parts:

· Alarm generation = the decision that an alarm must be given. Alarms are generated in two
places, the container controller and REFCON.
· Alarm handling = maintaining a list of actual alarms and event logging.
· Alarm propagation = attracting your attention, or just showing on the screen that an alarm is
present.
A number of tools are available at REFCON for your alarm handling. The primary tool is the
Alarm Summary in which you can always inspect all the actual alarms.
Alarms generated by the controller

Reefer container controllers are independent alarm systems. Alarms can be inspected on the
container – which you will have to do if the container is not connected to REFCON by either
four pole or PCT (Power Cable Transmission).
Each controller has a certain number of alarm points, each corresponding to an alarm reason.
The specific list of possible alarms depends on the controller type.
In case of PCT, the states of all the alarm points are periodically transmitted to REFCON. In
case of four pole, only the "In Range" signal can cause alarm.
In REFCON, changes are detected, causing the Alarm Summary and Event List to be
updated and the alarm to be propagated, if relevant.
Alarms generated by REFCON

REFCON provides the following types of alarms:
· All REFCON hardware is supervised. In case of malfunction an alarm is released, unless it
is inhibited.
· Lost communication (ships only). If a container stops communicating in Sea mode, an
alarm is released (delayed).
· Actual setpoint differs from expected setpoint (by more than "delta" value).
· If selected by the user, REFCON makes range check on analog inputs, releasing an alarm
if the alarm limits are exceeded.
· A free text alarm can be given. You select this in the Utility sub-page of the Container
Report.
Alarm handling
Your main activities regarding alarms would be:
· Inspecting the Alarm Summary, to find the reason for a new alarm and more.
· Acknowledging alarms.
· Taking action to solve the problem causing the alarm.
· In special cases, inhibit and uninhibit alarms.

The Alarm System 81
Alarm propagation
In the basic REFCON version, you need to watch the REFCON PC screen at intervals to
discover new alarms. The Alarms icon (see below) is flashing when a new alarm has
occurred.
REFCON provides a number of Alarm Extension options. For information, please refer to the
Installation Instructions.
Alarms Icon
The Alarms icon is always visible to the right on the screen:
The icon continuously displays the number of alarms currently present in the system.
Furthermore the background colour changes as follows:
Background colour Explanation

Green There are no alarms in the system. The number shown is 0.
Flashing red/yellow At least one alarm is unacknowledged.
Steady red One or more alarms are present. All have been acknowledged.
Clicking the Alarms icon opens the Alarm Summary.
9.1 Alarm Summary
Overview
The Alarm Summary is a List Window showing all the actual alarms, both the container
alarms and the system alarms.
Each line in the Summary represents one alarm. If more than one alarm on same container, it
is still just one line, as the Alms column shows that there are more.
The Alarm Summary includes a fixed number of columns. The contents of the columns are
described in Column specifications.

82 Operators Manual
The Alarm Summary is sorted chronologically, the newest alarm being shown first.
The caption line shows the number of alarms, and which of them are currently displayed.

The Alarm Summary is marked by a yellow ribbon at the top of the list.
Opening the Alarm Summary

To open the Alarm Summary, do either of the following:
· Click the Alarms Icon.
· Press F5 on the keyboard.
· Select Alarm Summary from the Service menu.
Acknowledging alarms
Alarms can be acknowledged from the Alarm Summary. Container alarms can also be
acknowledged from the Container Report.
In the Alarm Summary, to acknowledge an alarm, double-click the line or use the up and
down arrow keys etc to have a line highlighted, and then press F11. This makes the following
dialog box appear:

· [Marked] to have the highlighted alarm acknowledged.
· [Whole page] to have all visible alarms acknowledged.
· [Info.] to display detailed information. If it is a container alarm, the Container Report
appears, otherwise it will be the Alarm Information window.
When [Marked] or [Whole page] is selected, REFCON checks each of the related alarm lines
(if [Marked] it is only one!). In most cases the alarm simply is acknowledged, but if it is a
container alarm, and there are two or more unacknowledged alarms on that container, the
container alarm list shows up with a special acknowledge dialog box on top:

The Alarm System 83
· [Whole page] to acknowledge all the alarms on the container and return to the main Alarm
Summary.
· [Cancel] to be able to treat the alarms individually. The Acknowledge All dialog disappears,
and you are back in the container alarm list.
Column specifications
The Alarm Summary includes the columns described below. Note that the Origin column
shows where the information comes from. In this column, the abbreviation "LC/TS" is short for
"Loading Computer / Terminal System".
Column header Explanation Origin

/ abbreviation
Location If a container: It's location, if known, otherwise LC/TS or REFCON
the location of the system item, if known.
Description Description of the alarm cause. If a container, Controller
also the ID (4 letters + 7 digits) is included if manufacturer /
known. REFCON
Status The text indicates the type of the alarm. The REFCON
colour of the text indicates the acknowledge
state:
· Flashing: There are one or more
unacknowledged alarms on this container.
· Steady red: There are one or more alarms on
this container, they have all been
acknowledged.
Alms Number of alarms on this container / item. If Controller / REFCON
container: If more than one, the alarms must be
acknowledged from the container alarm list.
Ini The initials (user ID) of the user acknowledging REFCON
the alarm.
LMT Date & The time when the alarm occurred. REFCON
Time
Gr. Alarm group. 1 = System (hardware) alarm. 2 = REFCON
Normal reefer container alarm. 3 = Special reefer
(can only occur when a certain option is included,
see Special reefers).
9.2 Alarm Information window
Overview
The Alarm Information window relates to non-container alarms. Select [Info.] in the
Acknowledge dialog box to open it. Here is a typical example:

84 Operators Manual
Field descriptions
The various fields in the Alarm Information window are:
Field Explanation
Alarm State Shows ALARM if the device is in alarm, otherwise NORMAL.
The Alarm State field is also displayed in the Alarm Summary
in the Status column. This field cannot be edited.
Alarm Time/Alarm Date Shows the LMT time and date of alarm occurrence. If no alarm,
the fields are blank. These fields are also shown in the Alarm
Summary in the LMT-Date & Time column. The fields cannot
be edited.
Initials The initials (user ID) of the operator who acknowledged the
alarm. If still unacknowledged the field is blank. This field is
also shown in the "Ini." column of the Alarm Summary and
cannot be edited.
CutOff State/CutOff These fields are not used in REFCON. Do not change the
Group CutOff Group, it should always be 0.
Alarm Type Shows "Func.Ctrl" (= function control). This field cannot be
edited.
Delay – On Tells the amount of time (in seconds) that the alarm will be
delayed. Note, that the conditions causing the alarm must be
present for the whole duration of the delay in order for the
alarm to occur.
Delay – Off Tells the amount of time (in seconds) that the alarm will stay
after the alarm conditions have disappeared. Note, that the
alarm conditions must be absent for the whole duration of the
delay in order for the alarm to disappear.
Alarm Group Tells which alarm group this alarm point belongs to. Cannot be
changed.
Low Limit/High Limit These fields are not used in REFCON.
Max. High Limit/Min. Low These fields are not used in REFCON.
Limit
Inhibit Action Select "Set On" to inhibit the alarm. Select "Set Off" to enable
the alarm. Remember to select "Activate (& Quit)".
Inhibit State The two indicators show whether the alarm point is inhibited or
not.

The Alarm System 85
9.3 Inhibit handling
Overview
Inhibiting an alarm prevents it from showing up in REFCON. An existing alarm will not
disappear when inhibited. If it is container alarms, the inhibit will not affect the container
controller, that is, alarms will still occur on the container.
Container alarms can be inhibited from the Container Report. The inhibit status is shown in
the "Inh" column in the standard Container Summary. Inhibited containers do not appear in
the System Inhibit List (see below).
Other alarms can be inhibited from the Alarm Information window. They will in such case
show up in the System Inhibit List.
System Inhibit List

The System Inhibit List is available from the Service menu:
In fact, only the Description column provides useful information, as it identifies the alarm
point.
You can double-click an alarm point to have the Alarm Information window displayed. In this
you can uninhibit the alarm.
9.4 Special reefers - alarm group 3 (optional)
Overview
If your REFCON system includes the "Special Reefers" option, it is possible to change the
alarm priority of individual containers. Normally, all container alarms belong to Alarm Group 2.
You select the "special reefer" priority by changing to Alarm Group 3.
Within REFCON, the Alarm Group change makes no difference, except that you can see the
different number in the Alarm Summary. The purpose of the option is to distinguish externally,
that is, on the main alarm system, on the REFCON alarm panel or whatever is attached to
your REFCON system. The idea is that the special reefer alarms alert the user at a high
priority level, while standard container alarms alert at normal priority.
For example, if a PCI-7250 relay card is included in the REFCON PC (only in one if there are
more), output channel 2 relates to Alarm Group 2 (normal container alarm), while output
channel 3 relates to Alarm Group 3 (special reefer container alarm). Similarly, it will be two
different lamps in the optional REFCON Alarm Panel.
Selecting "Special reefer"

To change the Alarm Group, please enter the Container Summary named "Extended
Information":
You find the alarm group column rightmost:

86 Operators Manual
To make the change, double-click in the column at the relevant container – or use the arrow
buttons and the F11 button. The editing cursor shows up:
Change the value to 3, or back to 2. You can change to 1, but you should not do so, as this
value relates to non-container alarms. Complete by pressing the Enter button, or cancel by
selecting the Esc button.

REFCON
Event Logging
88 Operators Manual
10 Event Logging
Overview
Events are being logged in two places: In the container controllers and in REFCON.
REFCON logs events on:
· Alarms appearing and disappearing.
· Alarms being acknowledged.
· The operator requesting some action.
· The operator changing some settings.
· Automatic subsystems initiating some action.
These are the general rules, exceptions may occur.
For each event, the following data are stored:
· What has changed.
· What has it changed to.
· When did it happen.
· Who initiated the change (if any).
Event data are stored on the REFCON server harddisk in a "first in – first out" list. This means
that a certain number of events are stored. When a new event occurs, the oldest is deleted.
It is possible to have events printed as they occur.
Event Line
The Event Line is permanently visible at the bottom of the screen. It always shows the newest
event, arranged in columns exactly like the Event List.
10.1 Event List
Overview
The Event List is a List Window showing all the newest events:

Event Logging 89
The Event List shows:

· One line for each event.
· All events sorted chronologically, having the newest event topmost on the first page.
· The number of events, and which of them are currently displayed, in the caption line.
You can't make any selections in the Event List.

The Event List is marked by a cyan ribbon at the top of the list.
Opening the Event List

To open the Event List, do either of the following:
· Click the Event Line.
· Select Event List from the Service menu.
Column specifications
The Event List includes the following columns:
Header Explanation
Location The container's location, if known/relevant.
Description The item that was influenced by the event. If container, the ID is
included if known.
Status The type of event.
Value The value that caused the event, if relevant.
Unit The unit of measure of the number in the Value field, if relevant.
Ini. The initials (user ID) of the user causing the event, if relevant.
LMT Date & Time The time when the event occurred.

REFCON
Printing
92 Operators Manual
11 Printing
Overview
Depending on your configuration, you have one or more printers available from REFCON.
The printer can be a dedicated REFCON printer, placed close to the REFCON PC, or it can
be a network printer anywhere on the LAN.
At the time of installation, the printers were configured in Windows. From REFCON itself
there are no functions for changing the basic printer settings. If you change printer type or
connection you will have to ask your REFCON supplier for assistance!
In REFCON there are basically two ways of getting printed output:
· Automatic printing.
· Printing on demand.
There are two types of Automatic printing: Periodic printout and Event printing. Both can be
disabled. When enabled and configured, these functions automatically sends information to
the printer. All you have to do is to check the printer paper etc. from time to time.
Printing on demand means that you give a command to have the screen picture, or parts of
this, printed.
Printer Setup in REFCON

The basic printer settings are selected in Windows. What you can do from REFCON is to
select which printer to use, and how to use it.
By selecting "Event/Log Printer Setup" from the File menu, the following dialog box appears:
The 4 lines Page Header is printed at the top of any list print page.
Lower right you select whether to Print Events (Set On) or not (Set Off). Note that no matter
the selection, all events are collected in the Event List and stored on the REFCON server
harddisk.
If event print is selected, the Event Printer chosen lower left is used. Note that if the printer is
a page printer (laser, inkjet or the like), the events are buffered in the printer memory until the
page is full or another type of print is triggered.
11.1 Periodic Printout
Overview
Periodic Printouts allow you to have lists of containers printed automatically. Also you can
generate files on the REFCON server harddisk.

Printing 93
In the Service menu you find a number of Periodic Printout entries, numbered 1, 2, 3… You can
have a similar number of Periodic Printout configurations, working independently.
The Periodic Printout dialog box

Selecting a Periodic Printout menu entry in the Service menu makes the following dialog box
appear:
You may enter a List name, maybe to describe the selected Sorting and Filter options. The
List name is shown in the header of the print/file.
Remember to select a Printer, and to click [Activate] or [Activate & Quit] when you are done.
Click [Print Now!] to have the configured list printed or file-generated at once.
When to print
In the When to print section you select when to print/create file. Selecting 0 Times per day will
disable the automatic function. Select a number between 1 and 24 Times per day to have the
automatic function enabled, and choose a "Fixed time" to decide exactly when to print/create
file.
For example, suppose it is 7 in the morning when you enable the function. You select 6 Times
per day and the Fixed time 12:00. Then prints/files will be generated every 4 hours, starting at
8:00.

94 Operators Manual
Sorting options
By configuring the Sorting options, you decide the order of appearance in the list. The
containers are first sorted according to option No. 1. If this results in more identical, option
No. 2 is used etc. The containers are sorted alphabetically due to the option(s). Select
"Reverse" to obtain the order Z to A. Note that you don't need to select any Sorting options.
Filter options
In the Filter options section you can select a specific Filter column and then enter a Filter
condition to have only a subset of the containers included. Use the following rules when
selecting the Filter condition:
· The condition is not case sensitive – using lower and upper case letters give the same
result.
· The question mark (?) can be used as "Don't Care" character (wildcard). For example,
specifying "MAEU?32" would select strings like "MAEU432" and "MAEUk32", but not
"MAEU32" nor "MAEU4332".
· The asterisk "*" can be used as "Don't Care" marker. When "*" is found in the criterion
string, the print function will first look for the piece of text preceding the "*". When found, it
will check if the piece of text succeeding the "*" is found somewhere later in that particular
field. For example, specifying "MAEU*32" would select any of the strings "MAEU432",
"MAEUk32", "MAEU32" and "MAEU4332".
· Less than (<) and Greater than (>) can be used to specify an alphabetic range. For
example, specifying ">MH*" would select any string starting with "MHA" or later in an
alphabetical sort.
Output destinations
In the Output destinations section, select one of the options:
To printer only The specified list is printed at the printer selected in the Destination
settings, at the times specified and when clicking [Print Now!].
To file only (CSV) At the times specified and when clicking [Print Now!], a file is
generated containing the specified list. The file is placed on the
REFCON server harddisk with name and location as shown in the
Destination settings. The file is a CSV file (comma separated
values), however, semi-colon is used as separator.
To printer and file A combination of the above two.
Disabled You won't have any prints or files created, even if "Times per day" is
non-zero.
11.2 Printing on Demand
Overview
There are a number of ways that you can generate an immediate print. One way is the [Print
Now!] button in the Periodic Printouts dialog box.
Print screen
By selecting [Ctrl]+[F9] or "Print Screen" from the Service menu, you can at any time create a
print of exactly what you see on the screen. The following dialog box shows up:

Printing 95
Select "Landscape" to have the paper format match the screen format, resulting in a
maximum size image. If you select "Portrait", the image will be considerably smaller.
Click [Change Printer] to change the "Current Printer". If only one is available, the click is
ignored.
Click [Print now] to generate the print.
Print Current Window

By selecting [F9] or "Print Current Window" from the Service menu when a mimic picture or
list picture is displayed, you can have the picture printed.
If a mimic picture is displayed, the following dialog box appears:
It is very much similar to the Print Screen dialog box, and is operated the same way (see
above). The difference is that in this case, only the variable picture area of the screen is
included in the print.
If a list picture is displayed, the following dialog box appears:
A list can consist of more than one page. Therefore, in the Print this section, you choose
whether to print only the part shown on the screen, or the whole list.
Click [Change Printer] to change the "Current Printer". In contrary to the above example, you
here have the "Disk file (.CSV file)" option. If you select this, clicking [Print now] will display
the "Save As" dialog box, allowing you to choose a location and filename for the file. The file
is a CSV file (comma separated values), however, semi-colon is used as separator.
If a printer is selected, the Print options section allows you to choose the orientation of the

96 Operators Manual
paper. "Landscape" might be a good idea if the list contains many details. Also you can have
line numbers applied, and you can select to have the grid printed. A grid can make it easier to
see the dividing lines between the columns, and to identify the items of a row.
Click [Print now] to generate the print.

REFCON
Handling Log Files

98 Operators Manual
12 Handling Log Files

Overview
The purpose of log files is to prove that the cargo in the containers has been treated correct.
Normally, events such as alarms and setpoint changes are logged as they occur, while
temperatures and maybe other parameters are logged periodically.
When a container reaches its final destination, the documentation for the whole journey
would be requested by the recipient and/or by the authorities. This is why most reefer
containers are equipped with dataloggers. A modern datalogger includes a battery that allows
logging even when the container is without power. Note that in many cases the datalogger is
an integrated part of the container controller.
As a REFCON user you probably keep the container only for a part of its journey.
Depending on which part, and of your company policy, you might not worry at all about the
log files! You could rely totally on the container dataloggers, and maybe use the LogMan
handheld computer and the LogView PC program to inspect the logs. Thus avoiding having
REFCON making any recordings at all, no log files would be stored on the harddisk, and you
would not have to make any backups or housekeeping.
If your REFCON system includes the Global Monitoring Server (GMS) option – and it is
running – data will periodically be sent to a common database that can be accessed from the
Internet (password protected). This would be a supplementary datalogging that, depending on
the available equipment, could cover the whole journey – and at least it would cover your part.
REFCON's data logging

Additionally to the above, REFCON offers to create its own log files. A benefit to you is that
you can immediately see trend curves for a container, and thereby get, for instance, an
indication of the reason for an alarm. However, if you decide to enable the REFCON log files,
you will need to apply to certain guidelines.
You enable or disable the REFCON log files function in the REFCON Setup window.
Note regarding the REFCON log files:
· If this function is enabled, all connected containers will be covered.
· With the RDC option, you can even have REFCON log data from containers that are not
connected. This requires that the REFCON log files are enabled.
All log files are stored on the harddisk of the REFCON server PC, allowing you to inspect the
logs at any time. You must manually take care of backups and housekeeping.
Make backups to ensure that the log files are available when you need them. Remember that
a file stored on just one harddisk hardly is safe enough!
Housekeeping means deleting files from the harddisk when they are no longer needed. If you
don't do so, there will be a continuously increasing number of files, taking up harddisk space.
Eventually this could make logging and other vital REFCON functions fail.

Handling Log Files 99
Log File Locations

It might be expedient to have the following illustration in mind:
The file shown leftmost, LOGFILES.REF, is the REFCON system file where all log files are
being created. Do never delete or change this file (e.g. from Windows Explorer).
Moving log files is not possible from a REFCON Client PC due to the fact that the files are
actually situated on the Server PC.
12.1 Log file activities
Inspecting Log Files

Once a log file has been stored on the REFCON server harddisk, it can be inspected on any
REFCON PC. As standard, the Log File Manager is used for this. Log files still being stored in
the system file can further be inspected in the Container Report. In both cases, the Log
Viewing window and, where relevant, the Log Trend window are available.
Move of Log File

While log files are being logged, data are being stored in a single REFCON system file. If no
precautions were taken this would grow and grow, and eventually it would cause REFCON to
get slow.
The "Move of Log File" function is a permanent background task that moves data from the
REFCON system file to files in the C:\REFCON.LOG folder.
By selecting "Move of Log File…" from the "Planning" menu, the following dialog box opens:

100 Operators Manual
In this dialog box you can decide when to move the Log File contents, but you cannot cancel
the function, and you cannot change the destination (Log base directory).
In the "Automatic Move" field you select the time of the day that the next move will happen
(Fixed hour and minute), and you decide how many days between moves.
You can use the [Move Now] button to force a move at once. Watch the "Status" field: It
shows the data transfer progress, and then the date and time for the next move updates –
unless you already moved once today! In other words, you can use [Move Now] to select a
more expedient time for the move.
Backing Up Log Files

Once log files have been stored on the REFCON Server harddisk, they can be backed up by
means of the Log File Manager. Note that this can be done from the REFCON Server PC
only!
1. In the Log File Manager, select the log files to be backed up.
2. Use the Export function (the [Copy selected] or the [Copy/Del selected] buttons).
3. In the File Open dialog, select a location for the backup. It could be a diskette or another
PC on the LAN. Remember that the REFCON Server harddisk itself is hardly a safe
backup location.
4. Also in the File Open dialog, select a file name. Remember that even when more than one
log file is backed up, they will be packed into one backup file.
5. If relevant, remove the backup diskette or similar and put it in a safe place.
Harddisk Housekeeping
If log files are being created, and/or if you are using various "Print to file" options, you must be
aware that the files are occupying harddisk space on the REFCON Server PC. Normally
harddisks are very large compared to the size of log files, but nevertheless, some day the
harddisk will be full if you don't do the necessary housekeeping.
Housekeeping in general means deleting files or moving files away from the harddisk.
REFCON includes no tools for this – you need to use the Windows Explorer. Be very careful!
Plenty of files on the harddisk are not allowed to be deleted or moved! You should normally
do the work at the PC having the harddisk installed – typically, at the REFCON Server PC.
Log files are stored in compressed files. All log files being immediately shown in the Log File
Manager and in the Container Report Log Files sub-page are stored in one common file.
Creating log files means that this common file grows. The "Move of Log File" function takes
care of the housekeeping by periodically moving all log contents and starting a new log file.

Log File Management Events

When deleting, copying and moving log files, you will find that corresponding events are
generated in the Event List. Here are some examples:
12.2 Log File Manager
Opening the Log File Manager

Selecting "Logfiles…" in the Planning menu opens the Log File Manager:
Note that the list of log files can be very long, and take some time to open. While opening, the
buttons in the window are greyed, and a "BUSY" sign is shown.
Log File Operations Take Time

In general you need some patience to work with log files.
In particular, when copying or moving log files between harddisk locations, over networks or
to and from external disks (floppy, CD), you should be aware that the operation time is
proportional to the amount and size of the log files. While doing such operations, the
REFCON Server PC still needs to run its primary tasks, such as communicating with
containers and checking for alarms. The log file operations are considered "secondary" in this
context and are therefore only allowed to run in small pieces at a time – which makes the
operations last even longer.
When attempting to start such a log file operation, you are getting a warning:

As you see, the number of involved files is shown, giving some indication of the duration to
expect. You can do no other log file operations in the mean time – but you are free to work
with all other parts of REFCON.
Displaying and sorting the list of log files

The File Manager displays all log files that are stored in REFCON. They appear in the list in
the selected order:
· Cont. ID (1) = alphabetically by container ID
· Type (2) = alphabetically by type (see below)
· Date/Time (3) = in chronological order, the oldest shown first (topmost).
The log file types

Two different types of logs can be found:
· Refcon = temperature log file created by REFCON.
· EventList = event log file created by REFCON.
The Search function

By means of the Search function you can look for a certain log file in the list. In the "Search
for" textbox, type any string of characters, and then click any of the four buttons. The Search
function checks for your string in all three columns. For example, typing "31" would find both a
container ID including the digits "31" and a date being the thirty-first in some month. When
found, the characters in the line turn red (or cyan if the line is already highlighted). This does
not mean that the line is selected (highlighted).
Selecting log files

To select (highlight) one or more log files (lines), simply click the lines. Clicking once more de-
selects. You can select the whole list by using the [Select all] button, and you can de-select all
by using the [Select none] button.
Note that the number of selected files is shown above the [Select none] button. This would
include highlights that are not shown because they are on another page.
Deleting and exporting log files

Having selected one or more log files, you can:
· Delete it/them all by clicking the [Delete selected] button. You will receive a warning for
extra safety.
· Export it/them all by clicking the [Copy selected] button. Note that this is possible from the
REFCON Server PC only! The "File Open" dialog appears, prompting you for a location and
a file name. Note that the file extension is .REF. It is a packed file format that can only be
read by REFCON. Hence, the purpose of the export is solely backup. Note that even when
exporting more than one log file, they are all packed into one single file.
· Move it/them all by clicking the [Copy/Del selected] button. Note that this is possible from
the REFCON Server PC only! It results in a combination of the above Delete and Export
actions.

Inspecting log files

To view the contents of a log file, click it with the right mouse button. This makes the Log
Viewing window appear.
Importing and inspecting stored log files

From the File Manager, click the [View] button to deal with log files that have once been
exported or moved.
In the resulting "File Open" dialog box, select the location where the log file was stored. In
case of automatically moved log files, select C:\REFCON.LOG (this is possible from the
REFCON Server PC only).
You will see that a new version of the File Manager window appears, though missing the
[View] button and having two buttons renamed. It works very much like the original File
Manager.
The [Import selected] and the [Import/delete sel.] buttons can be used on the REFCON
Server PC only. These buttons do copy/move the log files back to the REFCON Server
harddisk and thereby back to the original File Manager. But you don't have to copy or move
the log files; you can inspect them immediately by using the right mouse button.
12.3 Log Viewing
Overview
In different ways you can select a log file and have the Viewing window displayed. The layout
of the Viewing window depends on the type of log and datalogger. Here is an example:
Note that the list is static. To update with new logs, close the window and re-open.
Type of log
In the caption of the Log Viewing window, the ID of the container is shown together with a
type indication:
· Refcon = temperature log file created by REFCON.
· Eventlist = event log file created by REFCON.

Print the log

Select the [Print] button to have the log printed. The following dialog box appears:
Upper left you see the printer to be used. If you have more than one, you can make a change.
Upper right you can have data sent to a file rather than to a printer. If you do so, clicking [OK]
displays the "Save As" dialog box, prompting you for a file location and file name. The file is a
plain text file that can be inspected by means of, for instance, Windows' Notepad.
The log might occupy several pages. Therefore it can be expedient to select the Print range:
· Whole log: The whole log is printed.
· Page: Only the visible page is printed.
· Lines: A selected range of lines is printed.
· Trip start: All lines until Trip start are printed (only possible if the log file has trip start
information).
· Date: Only loggings in the selected time frame are printed (only possible if the log is time
stamped).
Select [OK] to start the print or file generation.
Trend
Click the [Trend] button to have temperature logs displayed as curves, see Log Trend.
Loginfo
Select the [Loginfo] button to display information about the contents of the log.
12.4 Log Trend
Overview
For any log files that contain time stamped, periodically recorded numerical logs, you can
have data displayed as trend curves:

The Trend window is divided into three main parts:

1. Status information at the top.
2. The curves section in the middle.
3. The button panel at the bottom.
Status Information
In the upper part of the Trend window, the following fields are found:
Status field This field shows the ID and the Status.

The ID is the container ID succeeded by the string "_Refcon", indicating
that it is a temperature log generated by REFCON.
On opening the Trend window, the Status shows "Fetching Data...", the
curves section is blank and the button panel is greyed. After a little while,
when data have been fetched, the Status changes to "Ready", all curves
available from the container in question are displayed in the curves
section, and the button panel is enabled.
Cursor box This box shows the current vertical position of the mouse cursor,
provided that it resides somewhere inside the curves section. By moving
the mouse cursor on top of some curve, one can measure the exact
value of the curve at that point.
Marker Time box This box shows the absolute time position of the yellow marker (if in
use), which is brought up by clicking the left mouse button somewhere
inside the curves section.
Time Reference This box shows the absolute time of the latest measurement in the data
box set. Since the data set is static, the Time Reference will not change
during the trend session.

Curves Section
The Time Axis:
Below the grey area, the time axis (X-axis) is found. The time axis always shows values in
absolute time. The values are shown in two rows. In the upper row, time is shown in hours:
minutes. In the lower row, two dates are shown. The leftmost date shows the date when the
oldest part of the data was collected. The rightmost date (in a variable position at the midnight
hour count) shows the date when the newest part of the data was collected. When zooming
out there will be more dates shown.
The Y-Axes:
The curves section has two Y-axes – one to the left and one to the right of the grey area. The
left axis shows temperatures in the preferred unit (°C or °F). The right axis shows relative
measurings in percent. For each curve, only one of the axes is valid. Which curves use which
axes can be determined by opening the Legends window. The Y-axes are normally scaled
from -40 to +40 °C (-40 to +104 °F) and 0 - 120%, respectively; however, if data are outside
these areas, the system will attempt to adjust the scales. The Y-axes scales and units cannot
be changed manually.
12.4.1 Log Trend Button Panel
Overview
The button panel in the Log Trend window contains 10 buttons, which are explained in details
below. Buttons that are irrelevant in the situation will be greyed.
Zooming
You can zoom in and out on the curves using these buttons:
The zooming only affects the time axis – the ranges of the Y-axes always remain the same.
When zooming, the system normally chooses the rightmost time point displayed as fix point
for the zoom, i.e. this point stays unaffected, while more (Zoom Out) or less (Zoom In) of the
curve is displayed to the left.
It is possible (and often convenient) to define an alternative fix point for the zoom, typically in
situations where you have zoomed out a great deal and notice a strange behaviour for some
curve. To do so, click the left mouse button at the desired time. This brings up a vertical
yellow marker, which now defines the fix point for future zoom operations. When zooming
around the yellow marker, the system will always (if possible) try to place the marked time
point in the middle of the grey area after the zoom operation has completed.
Note that the yellow marker only acts as fix point as long as it is displayed in the grey area.
Moving the marker outside the displayed part will not delete it, just make it inactive until visible
again. Note also that zooming is done in steps. The size of each step is determined by the
system.
Scrolling
Consider the grey area as a window onto the curves lying behind. Using the [<] and [>]
buttons, you can move the window to the left and to the right thus exposing different parts of
the curves:
The window is moved left/right by an amount of 1/6 of the window width.

Reset View
Reset the X-axis to the default settings using the following button:
The default settings are defined as the closest zoom level and the newest measurements.
Show Grid
The following button toggles the dotted grid lines on and off:
Style
Use this button to toggle the curves between coloured, solid lines and black, patterned lines.
Coloured lines are preferred when watching the curves on a colour monitor, whereas
patterned lines are optimal for printing (unless a colour printer is attached).
Legends
The following button toggles the Legends window on and off:
The contents of the Legends window depend on what information is available in the log file.
This is an example:
For each curve available, the window shows

· the colour of the curve
· whether the curve is currently displayed (the checkbox)
· the title of the curve
· the unit of measure.
When switching from coloured curves to patterned curves by means of the [Style] button of
the Trend window, the colours in the Legends window are replaced by respective line patterns
as well.
Curves that are greyed are not available in the actual situation, and can not be chosen.
On entry, all available curves are shown in the curves section of the Trend window. If more
than three or four curves are available, you might want to switch off some curves of your own
decision. This can be done by toggling the checkboxes for those curves in the Legends
window. Toggling a checkbox takes effect immediately.
The Legends window will always "float" on top of the screen whenever visible, but note that
despite of this the Trend Window beneath can still be operated. Pressing the "Legends"
button while the Legends window is displayed will close the Legends window.

Print
Select the Print button to have the trend curves printed:
The button displays the following dialog box:
Note that printers are set up during installation / in Windows. If more printers are available you
can change the selection.
Closing the Log Trend

Use this button to close the Trend window (and the Legends window, if visible):

REFCON
Handling Load Data

13 Handling Load Data

Overview
The majority of container companies are using computers to manage the positioning of the
containers. We call these computers Loading Computers (on ships) or Terminal Systems.
In the most cases, the Loading Computer/Terminal System stores
· the container ID
· if it is a reefer
· and other information
for each individual container. We call this information Load data, opposed to the data
available online from the containers.
It is a great advantage to have the Load data transferred from the Loading
Computer/Terminal System to REFCON. In particular, the following data are valuable:
· The container location, as it allows REFCON to show the containers graphically.
· The expected setpoint, as it allows REFCON to check the setpoint actually running in the
container controller.
Other information can be valuable as well for specific purposes.
Understanding the Data Flow

The following figure illustrates how data enter the Container Data Record:
There is one Container Data Record for each container known to REFCON – no matter if it is
· reported by both Load Data File and power line transmission, or by only one of them
· communicating or not.
Container Data Records are dynamically created and deleted. For example, if a container
appears in the Load Data File that has not been known to REFCON before, a new record is
created, and the Load data is inserted.
All data in any Container Data Record can be inspected, and if relevant changed, by means of
the Container Report window.
You can transfer the Load Data File any time you wish:
· If the container ID is not known to REFCON in advance, a new Container Data Record is
created.
· If the container ID is known to REFCON in advance, it is checked if Load data have
changed. If so, they are updated in the existing Container Data Record.

Handling Load Data 111
13.1 Transferring the Load Data File
Overview
The Load Data file must be transferred to the REFCON PC. You can use a diskette or, if
available at your specific REFCON system, the LAN network connection:
File transfer procedure

To have the Load data transferred to REFCON, you must proceed as follows:
Step Action Comments

1 At the Loading Computer/Terminal The file must be in the decided format, which
System, execute the command that in the most cases is called Baplie 1.5 or Baplie
stores the Load data as a file. 2.0 (specified by the SMDG group, see
www.smdg.org).
Further, the file must be stored at an
appropriate location, which can be a diskette
(A:) or a folder on the LAN network,
accessible from both REFCON and Loading
-> If your REFCON includes the See Automatic Load Data File Transfer
“Automatic Load Data File Transfer” (optional)
function, and you have enabled it,
don’t do more.
2 If using a diskette, move it to the
REFCON PC.
3 At the REFCON PC, open the
Loaddata dialog box.
4 Select the file stored in step 1, and The last used location and filename appears
the decided format. automatically, so normally you need to do
nothing.
Normally there is only one format available.
5 Select the "Read loaddata file" If you don't do this, the file is not transferred.
checkbox.
6 Select "Activate (& Quit)" to start If you select "Activate", leaving the dialog box
the file transfer. open, you may watch the Status line showing
the progress.
7 If you have any reason to doubt that Does the number of updated containers
the data transfer was successful, match your expectation? If not you should
inspect the Status line (if watch the Transfer Log File (View Log button).
necessary, re-open the Loaddata
dialog box).

Checking the Load Data File

As soon as a Load Data file has been read, whether it happened manually or automatically,
REFCON checks it for changes:
· All unchanged container records are kept untouched.
· New containers in the file cause container records to be generated.
· Changed data, eg. locations or setpoints, are imported to the existing records.
· Any container that has been removed from the file is immediately deleted or queued for
deletion, see Container Delete Function.
Hence, this function implies an Automatic Container Deletion function. We recommend that
you always use this function, if available.
Establishing Online Connection

Below you find a little information necessary to establish the Local Area Network connection
between the Loading Computer/Terminal System and REFCON.
REFCON is running under Microsoft Windows, and is supporting all communication protocols
that Windows is supporting. As network driver, Microsoft's TCP/IP is used. This means that it
is not important which operating system the Loading Computer/Terminal System PC is using,
as long as it can exchange data using TCP/IP.
The communication hardware is standard Ethernet, 10/100 Mbit. RJ 45 connectors can be
used.
13.2 Using the Load Data dalog box
Overview
To transfer the Load data file, select "LoadData…" from the Planning menu. The following
dialog box opens:
Please note: The dialog box might optionally include an extra checkbox as described in
Automatic Load Data File Transfer (optional).
In the "Loaddata file name" textbox, enter the location and name of the load data file. You will
see that the last used location and filename appears automatically. You may click the "New
Loadfile name" button to use the standard File Open dialog box.
In the "Loaddata format" listbox, select the format that was selected when storing the load

data file. You may find that there is only one format available.
Select the "Read loaddata File" checkbox to have the file loaded. You may forget this step
from time to time, and find it needless; however, it is necessary with this extra step to avoid
unintended double file readings.
Select the "Add Dry Reefers" dialog box to include reefer containers used for non-refrigerated
cargo.
View log
Once a load data file has been read, you can use the "View Log" button to inspect the log file
regarding the latest load data file reading. Among others, the log file will show possible
excluded dry reefers.
File transfer status

Keeping the Load Data dialog box open while reading the load data file allows you to see the
"Status" progress. The possible Status readings are:
Status reading Explanation

Not active No file was ever read.
Error : Not able to open No file with the selected name was found at the selected
file location.
Active The load data file is being read.
030430 06:49.30. The load data file reading was completed at the stated date and
792 Containers updated. time (YYMMDD hh:mm.ss). The shown number of containers
was included from the file. Depending on the situation before
reading, each included container data record was
· left unchanged – if no new information
· updated – if existing data were changed
· created – if not know to REFCON before.
13.3 Automatic Load Data File Transfer (optional)
Overview
If the option is included in your REFCON system, you will see the following checkbox in the “
Read Loaddata File” dialog box – on the Server PC only:
If you do not enable this function, you must handle the transfer manually, as described
elsewhere.
When the function is enabled, REFCON will look for the file that you have named in the
location that you selected – so, the name and location must always be the same. Please be
aware that at the Loading Computer, the file still has to be generated, manually or
automatically.
At the time interval you select (30 minutes in the above example), REFCON reads and
checks the file, see Checking the Load Data File.
Please note that you can’t work with this function from the possible REFCON Client PC –
changes must be done at the Server.

13.4 Understanding the Transfer Log File
Overview
When a Load data file has been transferred to REFCON, a Transfer Log File has been
created. You can view it from the Load data dialog box.
The Transfer Log File Header

The first part of the Transfer Log File is a header, looking like this:
Import date is Thu May 08 09:41:01 2003
Filename=G:\REFCON\BAPLIE.DAT
Baplie version=20, Add Dry Reefers=NO
NAME,BBRRTT,SIZE,LP,DP,SETPOINT,CONTENTS,REMARK
eqd+cn,loc+147,iso6346,loc+6/9,loc+12/11,tmp+2,gds+,ftx+
Interpret the header as follows:
Line Explanation
1 Shows day of week (Thursday), month (May), day (08), hours:minutes:seconds
(09:41:01) and year (2003).
2 The filename and path selected in the dialog box.
3 Shows the file format (Baplie 2.0) and whether dry reefers are included (YES or
NO).
4+5 Shows the data fields that REFCON are looking for. In line 4 it is shown what the
fields are called (NAME = Container ID, BBRRTT = Bay, Row, Tier, LP = Load Port,
DP = Discharge Port). In line 5 the corresponding Baplie identifiers are listed.
There might be more than this. In particular, if the file was not of the expected format, you will
find the statement "Baplie header missing".
The Transfer Log File Body

Divided from the header by a single empty line, the body of the log file follows, with one line
for each container identified in the Load Data file.
For a container that was actually imported into REFCON, the data that were read are shown,
for example:
HDMU0000010,090882,40,CPH,HAM,-18.0:C,Contents,AAA+++Remark
For a container that was not imported into REFCON, the line shows the reason. The following
examples show the possible reasons:
If the container is not recognized as a reefer, or if it is recognized as a dry reefer and you
have selected to exclude such, the line looks as follows, stating the specific container ID:
No Reefer,LOSU0000010
If the container ID is not legal, the line looks somehow like this:
ERROR( Reefer Name),HDU0000090
If the line says "ERROR( Container Name)" in stead, the container was not identified as
reefer, or it was a dry reefer not to be included.
The Transfer Log File Footer

The last two lines of the Transfer Log File summarizes the result:
· How many containers were actually imported.
· How many containers should have been imported, but they were not due to illegal container
ID.

13.5 Understanding the Load Data File
Overview
Normally you won't have to worry about the format and contents of the Load data file, as it is
created and read by pre-prepared software functions. However, should a special case occur,
you might find the following information useful.
How REFCON Identifies Reefers

The Load data file contains all containers, both dry, empty and reefers. REFCON needs to
pick out only the reefers and, if selected, the dry reefers. This is done by investigating each
container record in the Load data file according to the following rules:
1. If the string “TMP+2” (Temperature setpoint) is found, the container is always imported,
even if the value for the expected setpoint is missing.
2. If the string “RNG+4” (Temperature Range) is found, the container is always imported,
even if the limits are missing.
3. If the container has the owner name LOSU, it is never imported, as this is a restricted
name for an RML device.
4. The line reading the container ID also shows the container type according to ISO
6346:1995(E). Any of the following types means that it is a Reefer container:
- R0 to R9 and H0 to H9.
- The old ISO types 30 to 39 and 40 to 49.
If it is a reefer, but no "TMP+2" string is found, it is recognised as a dry reefer.
5. Refcon regards any container name holding 4 letters and 6 or 7 digits as a valid name,
even if it contains spaces (these are simply stripped, before validation).
The Baplie format

The Baplie 1.5 and the Baplie 2.0 file starts with a one-line file header.
The Baplie version 1.5 has the following identification inside the header:
BAPLIE:1:911:UN:SMDG15’
The Baplie version 2.0 has the following identification inside the header:
BAPLIE:D:95B:UN:SMDG20’
Fields are separated by tokens: UNH, ‘+’, ‘:’ and ‘.
A specific container is represented by a variable number of lines of data, as illustrated in the
following example:

REFCON
Clock System
14 Clock System
Overview
All time recordings made by REFCON (not by the container controllers!) are based on the
date and time maintained by the Clock System. REFCON can be purchased in a number of
configurations – please refer to Clock System Options below to identify your specific version.
In general, two dates and times are available:
· UTC (Universal Time), previously known as GMT.
· LMT (Local Mean Time).
In fact, the LMT is identical to the UTC with the addition of an offset, called the LMT Offset.
The LMT Offset is an integer number of minutes, up to +/- 12 hours.
The time recordings in the Alarm Summary and the Event List are based on the LMT, while
the historical data recordings are based on the UTC.
Do never change the UTC unless it is strongly required! If you are changing time zone or
daylight saving time, always adjust the LMT only! Note that a major UTC time change can
cause the historical data recording to be interrupted.
The actual LMT is always visible on the screen as shown in Always Visible Information.
Clock System Options

In the case that you need to interact with the Clock System, you should be aware of the
specific configuration. The following figure illustrates all relevant options:
REFCON always includes at least one PC, the server. The REFCON server communicates
with the containers, however, it does not automatically synchronise the local clocks in the
container controllers.
If there are more than one REFCON PCs, one will be the server while the other(s) are
client(s). The clock on each client is always automatically synchronised with the server clock.
The date and time on the REFCON Server PC (and thereby on the optional REFCON
client(s), too) works in one of the following ways:
1. As standard, the clock is based on the hardware clock found in the REFCON server PC,
see Standard Clock System. This is always true when REFCON runs in a terminal.
2. On ships, the REFCON clock can be controlled by some external master clock, see
Master Clock System (optional). There are two options:
· The pulse signals from the master clock are read by the REFCON server PC.
· The pulse signals from the master clock are read by another PC on the LAN (typically a
MEMAC PC).
3. On ships, the REFCON clock can be controlled by an internal master clock, see Master
Clock System (optional). In this case the REFCON clock is controlled by another PC on the
LAN (typically a MEMAC PC).

Clock System 119
When Do I Need to Interact with the Clock System?

In the following situations you will need to take action as regards the Clock System:
Situation 1: When changing time zone or daylight saving time.
If Standard Clock System If internal Master Clock If external Master Clock

(internal REFCON PC clock) system system
(synchro between more Johnson (pulse signals to specific Johnson
Controls systems) Controls PC, REFCON or MEMAC)
Change LMT time in Clock Change LMT time in Master Change LMT time on Master
Settings dialog, see Clock server dialog box (on Clock unit, see Master Clock
Standard Clock System the selected server PC), see manual.
Operating the Master Clock
System
Situation 2: When the time shown on the screen is not correct.

Change LMT time or UTC Change LMT time in Master 1. Check (and correct) the
time in Clock Settings dialog, Clock server dialog box (on Master Clock unit.
see Standard Clock System. the selected server PC), see 2. If mismatch between
If the rate of the clock keeps Operating the Master Clock REFCON and Master
wrong, repair or replace the System. If the rate of the Clock unit, update time in
PC clock keeps wrong, repair or Master Clock server dialog
replace the PC box, see Operating the
Master Clock System
Situation 3: When the connection to the optional Master Clock is or has been broken.

Not relevant! Not relevant! 1. Check cable connection

and I/O card in Master
Clock server PC.
2. If mismatch between
REFCON and Master
Clock unit, update time in
Master Clock server dialog
box, see Operating the
Master Clock System
14.1 Standard Clock System
Overview
The standard clock system is based on the hardware clock found in the REFCON server PC.
If you want the clock to be synchronised with any external clock system, either you must do
this manually, or you must purchase the master clock option, see Master Clock System
(optional).
To adjust the date or time, click the LMT time icon or select "Clock Settings" from the Options
menu. The resulting dialog box depends on whether you are on a ship or in a container
terminal.

Clock Settings Dialog Box Terminal Version

In terminals, clicking the LMT time icon or selecting "Clock Settings" from the Options menu
makes the following dialog box appear:
Always type in the new date or time in the shown format: Year/Month/Day and Hours:Minutes.
Clock Settings Dialog Box Ship Version

On ships, clicking the LMT time icon or selecting "Clock Settings" from the Options menu
makes the following dialog box appear:
First, notice the "Master Clock in control" indicator. If it is highlighted (= blue), you can make
no selections in this dialog – please refer to Master Clock System (optional) for instructions.
If the "Master Clock in control" indicator is not highlighted (= grey), editing in the dialog is
possible.

Clock System 121
Always type in the new date or time in the shown format: Year/Month/Day and Hours:Minutes.
We recommend that you use the Advance and Retard buttons to change the LMT time while
passing time zones.
14.2 Master Clock System (optional)
Overview
The optional Master Clock System is relevant when
· the date/time on the REFCON PC(s) needs to be controlled by an external clock system
(Option 1),
· and/or two or more PCs in REFCON and at least one more system (MEMAC) delivered by
Johnson Controls need to be time synchronised (Option 2).
In both cases, a specific PC delivered by Johnson Controls is appointed Master Clock Server.
With Option 1, the Master Clock Server is equipped with an input card that allows it to read
the signals from the master clock hardware. If Option 1 is not included, the Master Clock
Server uses it's internal hardware clock.
With Option 2, a number of additional PCs on the LAN are time synchronised from the
Master Clock Server.
Master Clock Server Identification

In certain cases you need to find out, which PC is running as Master Clock Server. The
answer depends on your specific configuration.
The Master Clock Server is an independent software program that can be installed on any
PC. Normally it is installed on the REFCON Server PC or on a MEMAC Server PC, but other
solutions are possible.
The Master Clock Server exists in two versions:
· External: Pulse signals from the ship's master clock are read through the Adlink PCI-7250
board (see figure below). Note that this board can also be used for other purposes, such as
alarm interface.
· Internal: The timing is based on the internal hardware clock in the Master Clock Server. The

Adlink PCI-7250 board might be found in the PC anyway, being used for other purposes.
The Master Clock Server dialog box is available on the Master Clock Server only. Thus, if the
dialog box is not available, you are at the wrong PC!
To find out if you are interfacing an external master clock, run through the relevant steps as
regards the PC providing the Master Clock Server dialog box:
1. Is the PC equipped with the Adlink PCI-7250 board? If No: Internal version.
2. Is a cable connecting the Adlink PCI-7250 board to the junction box supplied by Johnson
Controls? If not so (and this is not a fault): Internal version.
3. In the junction box, are the terminals 17, 18, 19 and 35, 36, 37 connected to the master
clock? If not so (and this is not a fault): Internal version.
In the REFCON documentation package, you will find a drawing named "card008", showing
the master clock connections if relevant.
14.2.1 Operating the Master Clock System
Overview
In daily use, when an external Master Clock is present, all you normally do as regards date
and time is that you change time zones at the Master Clock, if and when relevant. You don't
do anything at the Master Clock Server PC or at any REFCON PC.
In case it is an internal Master Clock, or the PC time is not properly synchronised with the
external Master Clock, you will have to locate the Master Clock Server PC (see Master Clock
Server Identification) and then look at the Master Clock Server dialog box:

Clock System 123
Please find descriptions of the various parts of the dialog box below.
Synchronisation Field
The large font time fields usually show (with black figures) the most recent time as received
from the master clock. Though, for pulse-based systems a special problem exists:
Since the Master Clock Server really can’t tell the absolute time from the master clock pulses
alone, the operator is occasionally required to tell the server the exact time of day. This will be
the case right after program start and whenever the connection to the master clock hardware
has been down. The process of telling the system the correct time is called entering the
reference time.
Entering the reference time is done by modifying the displayed time figures by means of the
up/down buttons until the displayed values match those displayed on the master clock
hardware. As figures are being changed they turn red to indicate that they have been edited
but not yet applied. Having finished editing the operator must finally press the “Set reference
time” button. This causes the Master Clock Server to synchronise to the nearest half minute
upon arrival of the first pulse.
The reference time can at any time be pre-set to the value of the PC System Clock by
pressing “Preset” button. If this time is accurate (it will most probably be) then just click “Set
reference time” button to apply. Otherwise correct the time using the up/down buttons before
applying.
PC System Time Field

In the field lower left, the actual date and time of the internal PC clock is shown. Below this,
two checkboxes can be changed:
Synchronise PC to MCS UTC:
When this checkbox is checked, the PC’s internal clock will be kept synchronised with the
Master Clock UTC (within a dead band of xxxx ms as selected in the edit field). This feature is
useful because the PC time will then most probably be sufficiently accurate to be used as
reference time after a period with no master clock connection.
Automatically enter reference time:
When this checkbox is checked, the PC will automatically enter the PC system time (and the
last LMT offset used) as a reference time whenever such is needed. Though, doing so also
means accepting the risk that the PC system time has ‘run away’, or that the LMT offset has

been changed while the connection was down. Whenever the reference time has been
automatically set, the system will warn you that you should verify the current setting.
System Name and Events

The Master Clock System Name field indicates the type of the external hardware clock – in
the example, MCS-970 (or compatible).
The Events field shows the list of the most recent Master Clock events.
Show and Hide

The Master Clock Server program runs in the background, no matter if the Master Clock
Server dialog box is visible or not.
Having completed your work, you can click the “Hide this window” button (at the top of the
dialog box) to have it disappear.
The dialog box automatically displays whenever a requirement for user interaction is detected
by the program (e.g. in case of lost connection to the Master Clock).
Also, you can have the dialog box displayed by simply attempting to restart the program –
which can normally be done by activating the "MCS Server" icon at the PC desktop.
When doing so, the program discovers that it is already running and then offers to redisplay
it's dialog box. If you answer "No", the dialog box simply stays not shown.
Likewise it is not possible to terminate the program by normal means. If you attempt to close
the Master Clock Server, a message box pops up, informing you that the window will only be
hidden (though it looks like the application closes).
The Interface Dialog Box

Clicking the “Toggle Interface Dialog” button opens a dialog box, which is hardware
dependent, that is, it's contents depend on the type of Master Clock. The following example
shows the dialog box associated with the MCS-970 Master Clock and compatibles:
Upper left, the dialog box shows the current UTC date and time and the current LMT offset.
At the bottom, you can at any time inspect the states of the three associated digital inputs on
the I/O board (ADVANCE, RETARD and PULSE): Grey means no signal, blue means a
voltage of at least +/- 3 Volts across the relevant digital input’s terminals.
Because pulses come with 30-sec. intervals, and because the LMT-offset is kept in whole
minutes only, the DLL keeps track of ‘odd’ pulses by means of flags. The states of these flags
are displayed as grey or blue “½” symbols.
Finally the operator can manually ‘enter’ artificial pulses by pressing one of the buttons. This
is useful for test purposes (e.g. when no physical master clock is available).

Clock System 125
14.3 Clock System Trouble Shooting
Overview
The following table includes hints for various trouble situations.
If this situation: Try this:

The time shown 1. Select the Clock Settings dialog box (see Standard Clock System).
on the REFCON If enabled, change the time, otherwise…
screen is wrong. 2. If an external Master Clock is present, check if the time of this is
correct. If not, correct it, otherwise…
3. If mismatch between REFCON time and Master Clock time, or if no
external Master Clock is present, locate the Johnson Controls
supplied PC reading the pulse signals (see Master Clock Server
Identification). On this PC, change time, see Operating the Master
Clock System.
The rate of the 1. If an external Master Clock is present, check if the rate of this is
clock is correct. If not, solve the problem at the unit.
considerably 2. If an external Master Clock is present, and the rate of this is correct,
wrong. check that the pulses are read all right:
a. Locate the Johnson Controls supplied PC reading the pulse signals
(see Master Clock Server Identification).
b. In the Master Clock dialog box on that PC, inspect the pulse signal
indicators – do they change periodically as expected?
3. If no external Master Clock, the problem would be in the hardware
clock of the PC. This should be repaired or replaced.
The REFCON 1. Does your REFCON system include the Master Clock option? If not
time does not so, you have to synchronise manually!
follow the other 2. Please locate the Johnson Controls supplied PC reading the pulse
clocks on board / signals (see Master Clock Server Identification). Is the cabling from
in the area. the Master Clock all right? In the Master Clock dialog box on that
PC, inspect the pulse signal indicators – do they change periodically
as expected?
3. If the pulse reading PC is not a REFCON PC, is the LAN connection
between the PCs all right?
A message box or 1. Please locate the Johnson Controls supplied PC reading the pulse
event appears in signals (see Master Clock Server Identification). Is the cabling from
REFCON, saying the Master Clock all right? In the Master Clock dialog box on that
that the PC, inspect the pulse signal indicators – do they change periodically
connection to the as expected?
master clock has 2. If the pulse reading PC is not a REFCON PC, is the LAN connection
broken. between the PCs all right?
The REFCON 1. Please locate the Johnson Controls supplied PC reading the pulse
time does not signals (see Master Clock Server Identification). Is the cabling from
advance or retard the Master Clock all right? In the Master Clock dialog box on that
as expected when PC, inspect the advance/retard signal indicators – do they change
changing time as expected?
zone on the
external master
clock.

REFCON
Modem
Troubleshooting
15 Modem Troubleshooting
Overview
To have the full benefits of your REFCON system, it is very important that the highest
possible number of reefer containers are communicating on the PCT (Power Cable
Transmission).
To achieve this, the electronics – modem, controller etc – on every single container must be
maintained. This Guide intends to show you how to check the containers, and how to act in
case of troubles.
Please note that the guide was written with container ships in mind. On ships you can
normally take advantage of the fact that for considerable amounts of time (between two
ports), the container situation is stable, which is valuable as it might take some time to do the
detective work to find faulty containers. Also we assume that you have complete
information from Loading Computer/Terminal System, as it is essential to know exactly
which containers to find where when troubleshooting. If you do not match these assumptions,
we hope you will find parts of the Guide useful, anyway.
Communication path
The communication only works if the entire communication path is OK:

Modem Troubleshooting 129
15.1 Checking Your Containers
Overview
The container-check is based on the Malfunction List. The Malfunction List only works if the
load data file is updated. Please run through the following procedure in each port. Also check
the Malfunction List regularly.
Check procedure

15.2 Checking the Symptoms
Overview
When a container appears on the Malfunction List, you should check it and fix the problem, if
possible:
Check procedure

15.2.1 Symptom: Never Communicated
Overview
The following figure shows the most common reasons when a container does not
communicate, and tips for diagnoses and repairs.
Check and repair procedure
Another possible reason is described in Symptom: No Location - Wrong or No ID in Controller

("Ghost").

15.2.2 Symptom: Stopped Communicating
Overview
The following figure shows the most common reasons when a container used to
communicate but does not do so anymore, and tips for diagnoses and repairs.
Check and repair procedure

15.2.3 Symptom: No Location - Wrong or No ID in Controller ("Ghost")
Overview
A so-called “ghost container” is most likely a container with wrong container ID, or no ID at all.
It is communicating but has no valid location. Correspondingly, a container reported by the
Loading Computer / Terminal System has got a location, but it never started communicating.
The two are one and the same - but how do you match them?

Ghost explanation
Please refer to Finding a Ghost Container below to solve the problem.

15.2.3.1 Finding a Ghost Container
Overview
If you have (at least) one ghost container, how do you physically locate it?
In the ideal situation, all your reefer containers are equipped with power cable modems, and
the number of communicating containers is as expected. Then you would look in the
Malfunction List for non-communicating containers with valid location. Or you would open the
bayplan/stackplan overview and look for white container positions. In both cases we will refer
to white positions in the following. The number of such positions would match the number of
ghosts. This number is usually very small, so the further investigation would be practicable.
In many cases you will, however, face a non-ideal situation. Just a few reefer containers
without modems will make your job much more difficult because these will appear as white
positions, exactly like the ghosts. So rather than deciding which white position is which ghost,
you must find out which of the white positions are actually ghosts!
Looking for container ID similarity

Some wrong IDs are caused by misprint when the ID was originally entered into the controller
– maybe just a single character out of 11 is wrong (note: the check digit also must be correct).
Look for white position IDs that are similar to the Ghost ID. If there is only one, you probably
found it.
Comparing Actual Setpoint and Expected Setpoints

In some cases, controller data like actual setpoint, temperatures and controller type are
available. You would discover this in the Malfunction List. In this case, maybe try going
through the white positions, looking for expected setpoint values that are close to the actual
setpoint. Do not expect an exact match. In some cases this would reduce the number of
"suspects" dramatically.
Using the RMM Master number

Note: This method is only possible for certain REFCON systems.
The communication on the power lines is similar to radio communication. On some REFCON
systems, signals from any point on the power lines are reaching literally any other point – and
then the RMM Master number is useless. On certain other REFCON systems, there are
barriers so that a certain RMM Master modem only covers a limited area. In the latter case,
you may take advantage of this to find your ghost.
To know if your REFCON system provides this advantage, proceed as follows:
1. Inspect the System Layout drawing. Do you have only one or two RMM Masters in the
system? If so, the RMM Master number is useless – please jump to Manual inspection
below.
2. Look in the Bayplan/Stackplan. Walk through the Bays/Stacks one by one.
3. In each Bay/Stack, look up the Container Report for at least 10 communicating containers
(green positions) – click the "Communic" button and write down the "Connected to master
number".
4. Are the master numbers different in one Bay/Stack? If so, the RMM Master number is
useless – please jump to Manual inspection below.
5. Having walked through all Bays/Stacks, do you see a clear correlation between Bay/Stack
numbers and RMM Master numbers (one master may cover more than one Bay/Stack)? If
so, the RMM Master number can be useful – please keep your notes for future use.
If the above test is successful in your REFCON system, you might open the Container Report
for the Ghost, and click the "Communic" button. Notice the "Connected to master number".
From your notes written above, you should now be able to decide in which Bay(s)/Stack(s) to
look for the Ghost.

Manual inspection
Eventually you have a number of white positions that can be your ghost. Now you have to
manually inspect the containers. It is a great advantage to be two with walkie-talkies, one at
the REFCON PC and one at the container.
For each suspected container, try using the exclusion method:
If you know the controller type of the ghost (controller data available), does it match the actual
container?
If you know the actual setpoint of the ghost (controller data available), does it match the
Actual Setpoint read on the controller of the actual container. Remember: If the one is in
Celsius, and the other in Fahrenheit, there might be a small conversion error.
Check the Communication sub-page of the Container Report of the ghost. Does the "RMM
Serial Number" match the serial number of the modem at the actual container?
If the first 4 letters of the container ID read "LANG", "LOSU" or "RMMU", the digits in the
container ID will reflect the serial number of the modem of the actual container. However,
please note that the serial number is longer than 7 digits, so only a part is used.
Final check for 100 % certainty

How many containers do you have that matches those criteria? Typically there will be only
one.
To be absolutely sure you suspect the right one, do a final test: Try sending a setpoint change
of 0.1 degree from REFCON, and then go to the container and check that it has responded.
Or try making the change at the container, and check that it updates in REFCON (it might
take a few minutes). If so, you got it! Remember to change back the setpoint!
Please refer to Change of Container ID below to clear the ghost.

15.2.3.2 Change of Container ID
Change procedure
When you are absolutely sure which container to rename to what ID, proceed as follows:

15.2.4 Symptom: No Data from Container
Overview
The figure below shows the most common reasons when no data are read from a container,
even though it is communicating. Note that the container ID might be correct (and thereby the
location probably is known) because certain modems remember the ID even if the connection
to the controller fails. If the location is unknown, please refer to Symptom: No Location -
Wrong or No ID in Controller ("Ghost").
Check procedure

15.3 Checking the Power Cabling
Overview
The power cable communication only works if the internal cabling at the container is correct:

15.4 Typical Errors
Overview
The following picture illustrates two typical errors that have been observed on containers:

15.5 Locating the Modem
Overview
The modem can be an integrated unit (MPC2000 / MP-3000) or an independent unit attached
to various controller types. The following figure shows the most common examples:

15.6 RMM Modem Facts
Overview
Below you find facts about the three most common modem types.
LED interpretation
The LEDs can be interpreted as follows:
LED Color Status Description

POWER Green On 24V AC or DC power on. Power cable is correct wired.
Off No power.

LED Color Status Description

ACTIVITY Green Flashing High Data Rate activity is detected at the power line.
On High Data Rate activity is detected at the power line.
Off No power cable communication is detected.
TRANSMIT Yellow Flashing Communication in progress with a Master on the PCT
network.
Off No communication in progress.
ERROR Red On Internal malfunction has occurred.
Off Normal operation.
RESET Red Off Normal operation.
On The RMM is reset. Turns off after a while.
CTRL Green Off Searching for a connected controller.
Flashing Controller connected – controller does not have a valid
ID.
On Controller connected – valid container ID found.
USER or Green On The container is logged on to a master, with normal
PCT parameters.
Flashing Ready to log on.
Off Between 15 and 60 minutes has passed since last
device poll. As 60 minutes is reached, the unit resets
and gets ready to log on.
LED appearance examples

You often can obtain useful information simply by watching the Light Emitting Diodes (LEDs)
of the RMM modem.
The following figures show the most common examples. Note, however, that in case of
malfunctions, the LED behaviour can not always be foreseen.

Connector Specifications RMM Mk4b

The connectors on the modem RMM Mk4b are specified as follows. For other modem makes,
please refer to the respective manuals.
J1: 3-phase power and earth connection
Terminal (pin) Description Terminal (pin) Description

1 Earth/Ground 5 AC Phase 2
2 No connection 6 No connection
3 AC Phase 1 7 AC Phase 3
4 No connection
J3: Communication connection to controller

1 GND 5 RxD
2 De-select 6 TxD
3 RTS 7 No connection
4 CTS
J5: 24 V power inlet

1 AC/DC input 3 AC input/DC ground
2 No connection
15.7 Malfunction List
Overview
The purpose of the Malfunction List is to let the user easily:
· Spot containers that (probably) need repair or other manual interaction.
· Watch the symptoms and thereby get a good idea of the likely reasons for the malfunction.
The Malfunction List is a special version of the Container Summary.
Important notes
Please note:
· The Malfunction List does only show containers with problems related to remote
monitoring. The word malfunction does thus not cover all faults that can possibly occur to a
container.
· Reefer containers without modem will appear in the Malfunction List (unless they are
eliminated in the Load Data file). You may write “No modem” in the Note field for later

recognition.
· If the Load Data file is not used or not updated, you probably will see a number of well-
functioning containers in the List.
Selection criteria
A container appears on the Malfunction List if (and only if) one or more of the following criteria
are met:
Criterion Explanation
Location = “E0” = unknown Location is as standard included in the container data that are
(*) normally imported from the Load Calculator / Terminal
System. “E0” means that no such information is available for
this container ID.
Container ID prefix = Illegal ID – either nobody ever entered an ID into the
“LANG”, “LOSU”, “RAND” controller, or the modem is unable to read the ID from the
or "RMMU" controller.
No PCT data received for This occurs when the container has not been communicating
180 minutes for 180 minutes, but also in certain cases if the
communication between the RMM Master and the container is
poor.
(*) Note: REFCON can be configured to not include the “E0” criterion, please consult your
installation documentation.
When a container is on the List, the data in the columns should give you an idea of the
reason.
Opening the Malfunction List

The Malfunction List is available from the Container Summary menu:
Malfunction List Columns

When a container is on the Malfunction List, the data in the columns should give you an idea
of the reason.
Column Explanation
Location If Location reads E0 = “unknown”, it usually means that the container data
have not been transferred from the Load Calculator/Terminal System.
If you are sure that all reefer containers were actually included in the latest
data transfer, you most likely have a “ghost container”: The container ID
painted on the box and known to the Load Calculator/Terminal System
does not match the ID stored in the container controller. In this case you will
(after some time) also have another container on the List, with known
location but no communication.
Container ID If the container ID prefix is “LANG”, “LOSU”, “RAND” or "RMMU", it is illegal
and therefore shown in the List. The reason can be:
· No ID was ever programmed into the container controller.
· The communication cable between the modem and the controller is
missing or failing.

Column Explanation
· The modem malfunctions (first: check the fuse!).
· The controller malfunctions (first: check the fuse!).
Type The reported type of the container controller.
Note You may open the Container Report and write your note to be shown in this
column, max 20 characters.
Data “Yes” means that data was received from the container via PCT within the
latest 180 minutes.
“RDC” means that no data was received from the container via PCT within
the latest 180 minutes, and that data was received from the container via
RDC within the latest ZZ hours, ZZ being a number selected by the user,
default 24 hours.
“No” means neither of the above, that is, no data ever was received, or it
was too long ago (data obsolescence).
Com “E0” means that the container never has communicated.
“No” means that the container did communicate, but is does no longer do
so.
“Yes” means that the container does communicate.
Master The number of the RMM Master that communicates with the container.
A.Setp. “E0” means that no setpoint reading was received from the container within
the latest 180 minutes. “A.Setp.” = “E0” and “Data” = “No” usually indicates
that we have no connection to the controller. The reasons can be:
· The communication cable between the modem and the controller is
missing or failing.
· The modem malfunctions (first: check the fuse!).
· The controller malfunctions (first: check the fuse!).
Modem Serial “E0” means that the serial number of the container modem is unknown.
Msg Cnt Shows the total number of PCT messages sent to the container since it
logged in (if it logs out and logs in anew, the counter is reset).
Err % Shows how many of the above counted messages (Msg Cnt) that did fail.
Power cables are quite noisy, so a positive error rate must be expected,
however, if it is very high it might indicate a problem that should be solved.
Note that the percentage changes very slowly, so if you correct an error you
might discover that it takes hours for the percentage to reach a low level.

REFCON
Maintaining REFCON
16 Maintaining REFCON
Overview
To be able to fully rely upon your REFCON system, you will from time to another need to do
some maintenance of the included hardware: The PC(s), the network(s) and the attached
equipment. REFCON includes a few pictures etc to help you.
System Overview
You find the System Overview drawing in the Hardware Descriptions, which is normally
available from the Help menu and, optionally, in the printed REFCON manual.
The System Overview shows how the REFCON network is configured, which should help you
to identify the individual units shown in the System Items List. In the Hardware Descriptions,
you also can find the explanations.
16.1 System Items List
Overview
The System Items List shows all units that are communicating with the REFCON server PC,
except the possible REFCON client PC(s). This allows you to check if everything is all right. In
case of troubles, the List should help you deciding what is wrong.

The System Items List is marked by a brown ribbon at the top of the list.
Opening the System Items List

The System Items List is available from the Service menu:
The System Items List window

In the System Items List you find one line for each unit:

Maintaining REFCON 149
The normal situation is that:

· The Status column reads OK for all units.
· The “fish” in the Activity column moves irregularly, maybe with a delay of several minutes;
however, always max two masters at a time.
· The ContID and the Text columns changes, sometimes rapidly, showing the container
being worked with and what actually happens right now. This is true for RMM Masters only.
The Status column might in stead show:
· OK (DOWNLOAD) – meaning that software is being downloaded to the unit (triggered
manually).
· OFFLINE – meaning that the communication has stopped to this unit.
If Status is OFFLINE, you normally would check the unit. You might find the System Overview
drawing useful to locate it.
Network Node Info

If you double-click a line in the System Items List, the related Network Node Info dialog box
appears as standard:
In this dialog box it is possible to change the Description of the item, if you wish. The
Description appears in the Alarm Summary if an alarm occurs for the item, among others.
Also you can open the standard Alarm Information window from which it is possible to change
the alarm delay.
16.2 Third-party Software on the REFCON PC
Overview
Your system includes a REFCON Server PC and maybe one or more REFCON Client PC(s).
As standard the REFCON Server PC is reserved for the task of running REFCON. Being a
demanding task, you should not install additional software on the REFCON Server PC
without acceptance from Johnson Controls, with the exceptions described below. Be aware
that REFCON is using COM ports and other PC resources in special ways, which might
conflict with third-party software. In worst case this could cause REFCON to malfunction.
In contrary, the REFCON Client often runs on a PC that also runs other applications. As the
Client is less critical and less demanding, this rarely causes troubles; however, if your Client
does not work well, please try closing the other applications.

REFCON on public networks

Many REFCON systems are stand-alone systems that are not connected to the Internet or
similar. If your REFCON is such a system, please stop here, as virus software etc. is not an
issue in this context.
If, however, your REFCON PCs are somehow connected to a public network, please be
aware of the following:
Protection against computer viruses and similar

We strongly recommend that you – the REFCON customer – make sure the PC (or PCs)
running REFCON software is protected against all kinds of damaging threats. If necessary
you should install and run anti-virus programs, firewalls and similar on each REFCON PC.
If such software is installed, you should update it periodically as recommended by the vendor.
Note, however, that full harddisk scans and similar functions should be disabled, as such
activities will significantly influence REFCON’s performance.
Windows updates
When Microsoft does release Windows upgrades due to security reasons, we recommend
that you perform the update. Do always reset the PC after an update.
Should this cause troubles to REFCON – and Windows upgrades sometimes do cause
troubles on PCs – please uninstall the upgrade and inform Johnson Controls about the
experience.

REFCON
Data Transfer for

Global Monitoring
17 Data Transfer for Global Monitoring

Background
The Global Monitoring concept makes it possible for container owners and other interests to
establish automated and centralised remote monitoring of the reefer containers, covering the
whole journey.
The central part of the concept is the Global Monitoring Server (GMS). The GMS is an
internet based database that regularly receives data from most REFCON systems worldwide
about the connected reefer containers. Using standard internet PCs, interested parties can
log in to www.reefers-online.com and inspect data. The value of this highly depends on the
regularity and the coverage. You may visit www.myREFCON.com for further information.
Your ship’s owner has decided that data regularly must be transferred from your REFCON
system to the GMS.
Overview
REFCON is expected to log data on the GMS once an hour. However, most REFCON
systems on ships are not continuously connected to the internet. In stead, a connection is
established maybe once or twice a day.
Therefore, the REFCON Server PC creates a “GMS file” on its local harddisk once an hour,
containing the complete set of data that needs to be transferred to the GMS at that point of
time.
Data transfer takes place by attaching files to E-mails. This can work automatically or
manually. If, in your case, there is no automatic connection between REFCON and your
E-mail system, your manual action is needed, please, as described in Transferring data
manually. A possible automatic connection should work as described in Transferring data
automatically.
Checking the type

You should normally have been instructed if your manual interaction is required. Further, if
data are not received by GMS for a longer time, we would normally contact you to find the
reason.
If you are not sure and want to check if your manual participation is required, check the folder
C:\GMSlogif on the REFCON Server PC (see Procedure for data transfer). If there are no
more than 24 files in the folder (and REFCON is in fact running continuously), it indicates that
automatic file transfer is running, in which case you need to do nothing.
17.1 Transferring data manually
Overview
Data transfer to GMS takes place by attaching files to E-mails. If there is no automatic
connection between REFCON and your E-mail system, your manual action is needed, please.
Principle sketch
The involved elements and responsibilities can be sketched as follows:

Data Transfer for Global Monitoring 153
Procedure for data transfer

Regularly, at least once a day, you should run through the following procedure:
Step Action
1 Plug a removable storage into the REFCON Server PC.
Note 1: You would typically use a USB memory key or floppy diskette.
Note 2: If you have more than one REFCON PC, make sure it is the Server, not
a Client – notice the reading lower right on the screen.
2 Move all files from C:\GMSlogif to the removable storage.
Note 3: Make sure the files are deleted from C:\GMSlogif as soon as they have
safely been moved to the removable storage.
3 If you use a USB key, make sure to use the Remove command available from
the taskbar – DO NOT just pull it out!
4 Carry the removable storage to the E-mail system and plug it in.
5 Create a new E-mail addressed to logif@reefers-online.com
6 Attach the files from REFCON to the E-mail and send it.
Note 4: You may alternatively create more E-mails and maybe attach only one
file for each.
7 Delete the files from the removable storage to make sure you do not send any
file twice.
E-mail regularity
Please make sure E-mails with attached REFCON files are sent to logif@reefers-online.com
regularly as follows:
· Preferred frequency: 4 – 6 E-mails per 24 hours.
· Minimum frequency: 1 E-mail per 24 hours.
Note: More files may be attached to one E-mail.
REFCON’s file naming

The REFCON Server PC generates a packed “GMS file” every hour. The “GMS files” are
created in the folder “C:\GMSLogIf” on the REFCON Server harddisk.
The files are named “REFCON.001”, “REFCON.002” up to “REFCON.999”. Each time the
folder is emptied, numbering restarts from “REFCON.001”.
Other information
· The files in “C:\GMSlogif” have been packed (zip’ed) by REFCON. DO NEVER make any
further packing or other changes to the files.
· Always send the REFCON files at least once a day, for the data in the Global Monitoring

Server to be reasonably up-to-date and thereby useful.

· Please note: Setting up the E-mail system is not a part of Johnson Controls’ delivery.
17.2 Transferring data automatically
Overview
Data transfer to GMS takes place by attaching files to E-mails. You may find the information
below useful to trouble-shoot or establish an automatic connection. Maybe you would show it
to the IT responsible.
Principle sketch
The involved elements and responsibilities can be sketched as follows:
REFCON Server facts

You would need to know the following data about REFCON:
Computer name: pc01refcon

IP address: 192.168.0.22 as standard. Can be changed if required by customer.
REFCON support static IP addresses only.
Shared file folder: C:\GMSLOGIF shared as GMSLOGIF
User (login): Refcon, no password
E-mail regularity
Please make sure E-mails with attached REFCON files are sent to logif@reefers-online.com
regularly as follows:
· Preferred frequency: 4 – 6 E-mails per 24 hours.
· Minimum frequency: 1 E-mail per 24 hours.
Note: More files may be attached to one E-mail.
Customer’s responsibility
It is your job to set up the Ship’s E-mail system to run the described schedule automatically.
Some E-mail programs do include functionality for this.
Regularly, at the frequency you decide, the E-mail system should:
1. Move all files from the shared folder “GMSlogif”.
2. Make sure the files that have been moved are deleted from “GMSlogif”.
3. Attach the files to one or more E-mails; however, make sure each file is only attached and
sent once.
4. Send the E-mails to logif@reefers-online.com.

Data Transfer for Global Monitoring 155
REFCON’s file naming

The REFCON Server PC generates a packed “GMS file” every hour. The “GMS files” are
created in the folder “C:\GMSLogIf” on the REFCON Server harddisk. The files are named
“REFCON.001”, “REFCON.002” up to “REFCON.999”. Each time the folder is emptied,
numbering restarts from “REFCON.001”.
When your E-mail system works as described, there will normally never be more than 24 files
in the folder.
If the files are for some reason not removed, the limit of 999 files will be reached in almost 6
weeks. REFCON then attempts renumbering from “REFCON.001”. If an old file with the same
name exists at that time, REFCON saves the file in a local, temporary folder, which also holds
up to 999 files. If both folders run “full”, the oldest file is overwritten – so, if it has not been
transmitted, the data are lost.
Should for some reason a number of files (but not all) be removed, REFCON will attempt to
use free numbers, meaning that numbering might no longer match the chronological order.
Probably you will not have to think about these special cases – simply send all the files found
in the “GMSlogif” folder, and remove each file when sent.
Other information
· The files in “C:\GMSlogif” have been packed (zip’ed) by REFCON. DO NEVER make any
further packing or other changes to the files.
· Always send the REFCON files at least once a day, for the data in the Global Monitoring
Server to be reasonably up-to-date and thereby useful.
· Please note: Setting up the E-mail system is not a part of Johnson Controls’ delivery.

REFCON
RDC Mark II
18 RDC Mark II
Overview
The RDC (REFCON Data Collector) allows systematic data collection from
non-communicating reefer containers, including possible containers having the four-pole
signal cable connected. Also it allows you to check the temperature setpoints of the
containers.
The hand-held computer

Both are done by means of a hand-held computer equipped with RDC software. In your
REFCON system, the RDC Mark II is used. This is normally based on the hardware unit
named Psion Workabout PRO S G2, being described in the following.
The Psion needs to be connected to REFCON for data transfer. Normally this takes place
through a docking station connected to a USB port of the REFCON PC. If you have more than
one REFCON PC, any of them can be used.

RDC Mark II 159
Recommended schedule
Your normal data collection and setpoint-checking schedule would look like this:
1. You receive container load data from the Loading Computer / Terminal System.
2. Do await that all relevant containers defined in the load data list have had time to start
communicating – as with RDC you will only deal with containers that don't do so.
3. You place the Psion in the docking station, being connected to REFCON.
4. From that particular REFCON PC you select the order in which you intend to visit the containers,
called the walk route. You then send the sorted list of RDC-monitored containers to the Psion.
5. You carry the Psion to the containers, in the order stated in the display.
6. For each container, you check the setpoint, making a change on the controller if relevant, and/or
you type in setpoint, primary temperatures and alarm state on the RDC.
7. Having completed all containers, you return and place the Psion in the docking station.
8. From the REFCON PC, you retrieve the collected data, which can then be read and logged in
REFCON just like data received via the PCT. Note that only containers with updated data are
affected, and only if they still meet the conditions for RDC-monitored containers.
Usually you would repeat the schedule periodically.
Why Use the RDC?

Normally, most containers communicate with REFCON over the power cables (PCT),
however, it will happen that a number of containers don't. This can be because of defects, or
simply because the containers are not equipped with power cable modems. In REFCON we
refer to such containers as Non-RMM Containers, Remote Monitoring Module being another
designation for a power cable modem.
If your REFCON includes a four-pole signal network, even non-communicating containers can
be supervised remotely by applying the four-pole cables; however, still you need to check
manually that the setpoint is correct, among others.
Thus, containers that do not communicate will have to be supervised manually, to some
extent. With the RDC this manual task gets easier, and it allows data to be integrated in
REFCON.
The main advantage is that RDC shows you the list of containers that you need to visit in the
order you have chosen. This can considerable reduce your manual inspection time.
Another advantage is that data from the non-communicating containers get into REFCON,
making these containers work similar to any communicating container. Of course this will
depend on your inspection interval.
RDC-monitored Containers
When you send the sorted list of containers to the Psion, REFCON automatically decides
which containers to include according to the conditions mentioned below. We refer to these
as the RDC-monitored containers.
Also, when you retrieve data from the Psion to the PC, REFCON checks the conditions anew.
This means, for instance, that if a container has started communicating on the power line
while performing the manual inspection, the data that you collected by means of the RDC are
discarded for that particular container.
The following conditions must all be fulfilled for a container to be RDC-monitored:
· The container was included in the latest load data file (transferred from Loading Calculator /
Terminal System) – or it was included in an earlier load data file and was not deleted in the
mean time.
· The container ID read in the load data file must comply with the standard – 4 characters, 7
digits.
· The location (bay/row/tier or similar) must be legal. As the location is the key for sorting the
RDC-list, REFCON will not include containers with illegal locations. Normally the location is

read in the load data file, however, you could type it in the Container Report.
· The container has never been communicating via the PCT, or data from the container was
not received for at least 90 minutes (data obsolescence).
Note: If a container meets the above conditions, it is included in the RDC list, no matter if it is
connected by four-pole signals or not.
Precautions regarding RDC and Container Deletion

RDC is relevant for containers that are not able to communicate over the power cables.
Consequently, when REFCON sends the container list to the Psion, only the selected
RDC-monitored containers are included.
You must be aware of REFCON's automatic deletion function. When a container has
been discharged, it must be deleted. Unfortunately, the automatic deletion function does not
distinguish between an RDC-monitored container and a container having stopped
communicating due to discharge.
Therefore, using the REFCON function for automatic deletion of non-communicating
containers will not be expedient. You can disable this function in the REFCON Setup dialog
box.
If the Automatic Load Data File Transfer option or the Terminal Interface option is included in
your REFCON system, and it is running, it will take care of the container deletion without
interfering with the RDC function.
If, however, none of the automatic deletion functions are running, it is very important that you
remove containers manually by routine. You can do this from the Container Summary.
18.1 Operating RDC from REFCON
Overview
If the REFCON PC is configured to include the RDC, an additional menu is found. The menu
consists of six plus one menu items as shown below:
Note: If RDC is not enabled, only the seventh option is active, see Enabling RDC Mark II.

RDC Mark II 161
RDC Menu "Send Container List"

Select "Send Container List" from the RDC menu to have the actual list of RDC-monitored
containers transferred to the RDC hand-held computer. This makes the following dialog box
appear:
The transferred list is sorted. In the dialog box it is possible to choose whether the container
list should be sorted by container ID or by location. Furthermore it is possible to choose if the
sort order should be normal (ascending = B after A) or reverse (descending = A after B).
If you sort by container ID, it will be alphabetical. If you sort by location, you select if it will be
according to:
· The default walk route (not changeable),
· The Custom walk route (changeable from the "Edit Custom Walk Route" menu), or
· Alphabetically.
Hint: If you have two Psion units equipped with RDC, you may find it expedient to sort the list
for the first Psion ascending, and for the second Psion descending. Then the two RDC
operators can start from each end and meet near the middle, or at a decided position. Note
that only updated container records (green markings on Psion) are transferred to REFCON,
so data will be safe even with two RDCs.
Before proceeding, make sure you don't have manual data on the Psion that should be
retrieved. Sending the file will overwrite the possible existing file and all manual
changes without warning.
When clicking “Send File” you get an extra warning:
Click OK to have the container list generated and sent to the Psion. As a result of this a
message-box indicating the result of the action comes up. Possible results are:
Result message Comment

Container list transferred You can now remove the Psion from the docking station
successfully. and start your data collection round.
Handheld not ready to receive Make sure the Psion is in RDC mode. Check power and
data. Please make sure it is cable. Check that the Psion is correctly mounted in the
connected and switched on. docking station.

Result message Comment

No containers suited for RDC This means that all your containers are not
use. RDC-monitored – which normally means that they are all
communicating all right.
Container list transfer failed. Transfer was started but could for some reason not be
completed. Check the Psion and try again.
Simply select OK to continue.
RDC Menu "Receive Updated Container List"

To have the collected container data transferred from RDC to REFCON, insert the RDC into
the docking station and select "Receive Updated Container List" from the RDC menu. This
makes the data transfer start immediately, and should result in the following dialog box:
Please note that:

· Only data from RDC-monitored containers are transferred, that is, should any container on
the RDC list have changed status in the mean time, data for that particular container is not
transferred. This could, for example, be because the container has started communicating
via the PCT.
· Receiving a container data file from the Psion is a password-protected operation that
results in an entry in the REFCON event log. The entry shows how many containers were
actually updated. If, for example, you have changed data on two containers, the reading will
normally be 2.
RDC Menu "Update Status"

Select "Update Status" from the RDC menu to inspect the data collection status. This makes
the following dialog box appear.
· The fields “Last Update” contains the time of the latest data transfer from the Psion.
· The field “Containers In List” contains the total number of containers in the list read from
the Psion.
· The field “Containers updated” contains the number of containers with manually updated
information, now stored in REFCON.
These data are read-only. To make a change you need to do another data transfer.

RDC Mark II 163
RDC Menu "Update Handheld Software"

Select "Update Handheld Software" from the RDC menu to transfer the RDC software to the
Psion. This makes the following dialog box appear:
Before proceeding, make sure the Psion displays the start picture, see The Psion Start
Picture.
When you click "OK", REFCON checks the software versions:
· If the available version is identical to the one already found in the Psion, software update is
not possible, which you are informed in a message box.
· If the available version is older than the one in the Psion, you will have the following
warning:
You should normally cancel the update in this case.

· If the available version is newer than the one in the Psion, you will have the following
warning:
Selecting Yes will start the software file transfer. You can see the progress in a REFCON
dialog box.
When the software update has completed, you receive a message:
The Psion is now ready to run the updated RDC software.
RDC menus regarding Custom Walk Route

Please refer to Custom Walk Route.

Enabling RDC Mark II

If the REFCON PC is prepared for RDC Mark II, but this has not been enabled, the six normal
options in the RDC menu are greyed, while the seventh is available:
Selecting “Enable use…” displays the following dialog box:
In the dialog box, type the license key that you received from Johnson Controls, and click
“Activate & Quit”. You should now see this:
Troubleshooting the connection

Should you experience problems with the connection between the RDC handheld computer
and the PC, you might switch (Alt+Tab) to the ActiveSync window. This window shows if the
device is connected (left) or not connected (right).
In the terminology of Microsoft's ActiveSync, the RDC in your REFCON is supposed to

appear as a Guest.

RDC Mark II 165
18.2 Operating the RDC Hand-held Computer
Overview
In the following it is shown how to operate the Psion Workabout PRO S having the RDC
software installed.
Please note: The LogMan mentioned in various places might not be installed on your Psion.
To exchange data with REFCON, simply connect the Psion – normally by placing it in the
docking station – and then enter the appropriate commands from the REFCON PC.
Handling the Psion Hardware

You can turn on and off and reset the Psion as follows:
Action Result Comments

Keep ENTER key pressed for The Psion is If out of battery, nothing happens.
a few seconds turned on Please place in docking to have
batteries charged.
Press the blue FN key (short) The Psion is Similar to “standby” on a PC, that is, still
and then the ENTER key turned off power on RAM. If not in docking the
(short) batteries will slowly decharge.
Press and keep the blue FN The Psion is Similar to “restart” on a PC, that is,
key and the ENTER key for restarted programs and files are reloaded.
several seconds
To save battery power you should turn off when the unit is not to be used for a few minutes.
The background light automatically turns off when not used for 1 minute. Any keystroke turns
back on.
If the Psion cannot be turned on please check the batteries.
Do only use rechargeable batteries. Do always keep the Psion in the docking station when not
used to have the batteries automatically charged.
If you have two RDC units and just one docking station, remember to exchange the two in the
docking station to have both batteries charged.
The Psion touch screen and keyboard

The RDC Mark II can be operated solely by means of the keys, or you can take advantage of
the touch screen, using the special pen or simply your finger. As regards the touch screen,
use pen/finger as you would use the mouse on a Windows PC.
The keys on the Psion Workabout PRO S G2 are in general used as follows:

Note that when you press one of the FN keys, a window opens at the top of the display,
saying either “Blue FN (F-key) pressed” or “Yellow FN (alfa) locked”. The first mentioned
disappears at the next keystroke, while the last mentioned is removed by pressing the yellow
“FN” once more.
The function keys F1..F10 (obtained by pressing the blue “FN” and then a numeric key) can
be used for various purposes. In general, F2 displays a menu where you can see the
meaning of all relevant function keys. In most cases, some of the function key definitions are
shown in the bottom line of the display.
In certain dialog boxes you will have the OK and the Cancel options:

RDC Mark II 167
In the above case, the Cancel button is in focus (bold frame), meaning that if you press
ENTER, the dialog box will close without applying your possible changes. If you want to
apply changes using the keyboard, you must first use the arrow key or the TAB key to bring
focus to the OK button:
After this, pressing ENTER will apply your changes and close the dialog box.
18.2.1 Start pictures
Overview
Below you find descriptions of the start pictures available on the RDC hand-held computer.
The Psion Start Picture

There will be one or two software programs installed on your Psion – the RDC software and
then maybe the LogMan software as well. Therefore, the following start menu will appear on
the Psion upon power-up:
In this menu you can press “1” to activate the REFCON Data Collector (RDC) software, or “2”
to activate the LogMan Data Retriever Unit software. Also you can use the Up and Down
arrow keys to highlight the desired entry and then press ENTER, or you can use the touch
screen.
The Psion RDC Start Picture

When the RDC software is launched, you will first maybe see the “please wait” icon:
Also, if an existing container data file exist when launching the RDC software, a loading
indicator will appear for a while:

After this, the RDC Start Picture appears. If no existing container data file was found, it looks
like this:
The four hyphens (-) indicate that the RDC application was launched without any container list
available. In this state, the Psion RDC can do no further work except await a container list
from REFCON.
When you start sending the container list from REFCON, you can observe progress in the
Psion display:

RDC Mark II 169
After a short time, depending on the length of the container list, the RDC Start Picture re-
appears, indicating that the data transfer was successful:
After loading the list, the picture shows the following read-only information:
· List transferred (LMT and UTC): These time stamps origin from the transferred file and
therefore reflect the REFCON PC time when the file was generated.
· Containers in list: Be aware that REFCON never transfers reefer containers that
communicate on the PCT (power cable transmission) – therefore the “Containers in list”
count typically is smaller than the total number of reefer containers.
· Containers checked: The number of containers that you have updated with manual data
(green marks in Container list picture).
When the list is loaded, you can:
· Press ENTER to open the Container List picture.
· Press F2 to open the Menu picture.

· Press F3 to open the Settings picture.

· Press F8 to open the About box.
· Pres Esc to exit.
Note: In the last example above, the Psion has in fact been removed from the docking station
– you see that the battery indicator does no longer say “Charging”.
18.2.2 Menus and Settings
Overview
Below you find descriptions of the menus and settings available on the RDC hand-held
computer.
The Psion RDC Menu picture

You can at any time select F2 to display the Main menu. The contents depend on the context.
The following example applies to the Start picture:
In the Menu picture you can select any of the shown options.
The Psion RDC Settings picture

Selecting “Settings” from the main menu, or pressing F3, will open the following picture:

RDC Mark II 171
In this picture you can make the following general choices. Use Up and Down key to jump to
previous/next setting, and Left and Right key to change.
· Temperature unit: Celcius or Fahrenheit.
· Display all input fields and Include USDA temps: Together, these two checkboxes
decide the occurrence of the editing part of the Container List picture.
Display all input Include USDA Result

fields temps
Unchecked Don’t care The Container List picture shows the
Setpoint and the Supply and Return
temperatures only.
Checked Unchecked The Container List picture shows the above
plus 2 text fields, Note and Alarm
Checked Checked The Container List picture shows the above
plus 3 USDA temperatures
· Select when scrolling: This setting is relevant when using the vertical scrollbar in the
Container List picture – which you can only do by means of the touch screen (pen/finger).
· When unchecked, the already selected container remains highlighted (standard in
Windows).
· When checked, the selection (highlight) changes to one of the visible containers when
releasing the scrollbar.
· Cursor at setpoint, all entries: Suppose you enter Setpoint first, Supply temperature next,
and then Return temperature. This setting decides what happens when you jump to another
container:
· When unchecked, the cursor remains in the field where it was – in the example, the Return
temperature field.
· When checked, the cursor always moves to the Setpoint field.
· Key delay: This setting decides how soon the Psion accepts the same key pressed again in
the Container List picture. For example, if the setting is “Fast”, pressing the Down arrow key
twice quickly will result in two cursor moves, while “Slow” will ignore the second key stroke if
it comes too soon.
To apply your changes, you must select the OK button. Note that the ENTER key does not
automatically invoke the OK button – you must move the selection first by means of Up and

Down key, or TAB key.

To close the picture without applying, select Cancel or press ESC.
18.2.3 The Psion RDC Container List picture
Overview
Press ENTER in the RDC Start Picture to inspect the current container list.
Showing max 9 containers at a time, this picture displays the complete list, in the order
selected from REFCON when sending the list. The selected container is highlighted (light text
on a dark background). In the lower part of the picture, the data related to the highlighted
container are shown and can be edited.
Two columns are displayed:
1. Container location.
2. Container ID.
When the container has been updated with manual input it is marked with green in the list:

RDC Mark II 173
Basically you can do the following things in this picture:

· Jump to the container of interest – by using the white side buttons, or the scrollbar, or the
search function.
· Edit data for the selected container.
· Change settings using the function keys or the menu – note that more function keys are
available as shown in the menu.
· Exit to the Start picture by pressing the ESC key.
The Psion RDC Search Function

Select F4 in the Container List picture to search for a location or a Container ID:
Note that selecting F4 again will repeat the search, finding the next match. If no match is
found, you are asked if you want to search from top of list. If you answer No, your next F4 will
open the above Search dialog box. If you want to open the dialog box even if F4 would find
the next match, use F7.

When first opened, the Search dialog is blank. It displays the total number of containers
known to the RDC.
The three fields in the Search can be used individually or in combination.
The first two fields, ContainerID and Location, are text string fields. Use alphabetic and
numeric keys when entering the criteria. The search is NOT case sensitive. Type any part of
the string you are searching for. Examples:
· Typing “omu” in the ContainerID field finds any ID starting with “SOMU”, but also “DOMU”,
“NOMU” etc.
· Typing “06” in the Location field finds any container in bay 06, but also those in row 06 in
any bay, and those in tier 06 in any row in any bay. You might, for instance, wish to type
“b02” to find the bays only.
In the Updated field you can by means of the Left and Right buttons choose the following
options:
· All: Search through all containers (as decided in the other two fields).
· No: Search for containers that have not yet been updated.
· Yes: Search for containers that have been updated.
Note that while entering your search criteria, the number of matches changes. If it gets “0
matches”, your search will produce no hits.
Entering Container Data

Having selected a container in the Container List, the text cursor is placed in one of the input
fields in the lower part of the screen.
To move the cursor to another field, use the Tab key or the Up and Down arrow keys – or use
pen/finger.
To edit a value:
To insert a minus sign Press the large white key.

To copy Setpoint value to Press Left or Right white side key when in Alpha mode
other field (only if reading is E0).
To step value up by 0.1 Press Right white side key when in Alpha mode.
To step value down by 0.1 Press Left white side key when in Alpha mode.
To enter a numeric value Use numeric buttons and period.
To enter a text (in Note or Use yellow FN key to toggle between numeric and alpha
Alarm field) keys.
To cancel your changes in Press Esc button (while still red reading).
present field
To store your change Move to another field or another container.
Temperatures must be in the range -80°C to +40°C, corresponding to -112°F to +105°F. If

you enter a value outside this range, the value changes back to the previous reading.
Values are rounded to one decimal.
If the sensor is in error, or the value is otherwise unknown, or you for some other reason don't
want to enter a value, type "E0".
Please note the typical starting situation:
· The setpoint reads a valid number, originating from the Loading Computer / Terminal
System. You may compare with the actual setpoint of the controller. In case of difference,
correct this if you are sure the RDC reading is correct, or make a change (or a Note) on the
Psion.
· Each of the five temperatures reads "E0", meaning "Not initialised". You may type in the
correct values.
· The Note and the Alarm both are empty, indicating that no Note or Alarm was entered. You
may do so!

RDC Mark II 175
Once you have typed in data in a field, it will stay until you make a new change, even during
file transfers. This also means that if data are changed on the REFCON PC, and the file is
transferred afterwards, the changed data will appear in the Psion.
In this case, if all the shown values for some container are still valid, you may simply press the
Enter button while the cursor is in any input field. When you afterwards move to another
container, you will see that the “confirmed” one has turned green in the list.
All temperatures are signed decimal values in the unit (°C or °F) shown in the bottom of the
screen. If you change the unit in the Settings picture, you will see that all temperature
readings for all containers change correspondingly.
The field “Note” is a text field into which you can enter a text containing a maximum of 20
characters. The field “Alarm” is a similar 20 characters text. The difference is that if you enter
an Alarm text, it will cause an alarm in REFCON once the container list has been transferred
to the REFCON PC program. The related alarm/event description will be the text you enter.

REFCON
RDC Walk Route

19 RDC Walk Route

Overview
When sending the container list to the RDC hand-held computer (Psion), you may decide to
sort by location. In such case the list on the Psion will be organised according to:
· either the default walk route
· or the custom walk route.
In both cases, the intention is to make it as fast and easy as possible to visit the containers.
However, the user is free to select another order than proposed by the Psion.
Description of Default Walk Route

The default (= standard) walk route described below only relates to ships.
The calculation of the default walk route is based on the assumption that the ship's containers
are organised according to the ISO 9711-1:1990 standard, however, it also handles certain
exceptions from this.
How the default walk route is organised

The order of the locations in the default walk route is decided by the following rules/
assumptions:
· All 40' containers are placed with the machinery end pointing astern.
For example, a 40' container in bay 06 and a 20' container in bay 07 will have the
controller displays accessible side by side, while a 20' container in bay 05 will have the
controller display at the other end (ahead) of the 40' bay.
· The walk route starts ahead, on deck.
· You inspect all containers on deck first, and then all containers below deck.
· Far most ahead you might have 20' containers in bay 01. You inspect these first, starting
just above deck in starboard side. Having finished the first tier, you continue at the tier just
above, starting again in starboard side. Etc.

RDC Walk Route 179
· Having completed bay 01 above deck, you continue with bay 02/03, starting just above
deck in port side. When you reach the starboard side, you turn around and inspect possible
20' containers i bay 05, starting in starboard side. Back in port side, you continue to the tier
just above. Etc.
· Having completed bay 02/03/05, you repeat this in bay 06/07/09, 10/11/13, etc.
· Having completed the last bay astern on deck, you continue with the last bay astern below
deck. If for example the last bay below deck is bay 54, you first inspect bay 54/55, starting
in port side just below deck. Having completed the uppermost tier, you step down to the tier
just below, starting in port side. Etc.

· Having completed bay 54/55 (in the example), you continue with bay 53, starting just below
deck at starboard side. When you reach the port side, you turn around and inspect bay
50/11, starting in port side. Back in starboard side, you continue to the tier just below. Etc.
· Having completed bay 53/50/51 (in the example), you repeat this in bay 49/46/47, 45/42/43
etc.
19.1 Custom Walk Route
Overview
From the RDC menu you can edit and validate the custom walk route.
RDC Menu "Edit Custom Walk Route"

Select "Edit Custom Walk Route" from the RDC menu to start editing the customised walk
route. First you get a dialog box with important information:

RDC Walk Route 181
Clicking OK makes the actual user defined walk route appear in the standard Notepad text
editor. The first time after installing REFCON, this will be identical to the default walk route.
The walk route is a list including all possible reefer container locations, each identified by a
string of characters, for example, "B06R12T82" meaning Bay 06, Row 12, Tier 82.
To change the walk route, you must move lines. Do this as follows:
1. Place the cursor at the beginning of the first line to be moved.
2. Keep the Shift key down, and use the "Down" arrow button to highlight the one or more
lines to be moved.
3. Select "Cut" from the "Edit" menu, or use the shortcut "Ctrl"+"X", to move the lines to the
clipboard.
4. Place the cursor at the beginning for the line that is going to succeed the moved lines.
5. Select "Paste" from the "Edit" menu, or use the shortcut "Ctrl"+"V", to insert the lines from
the clipboard.
Having done your changes, select "Save" from the "File" menu, and then close Notepad. After
this, always use the "Validate Custom Walk Route" to make sure that the result of your work
is still a valid walk route.
Note: Be careful that, after your work, all reefer container locations are still represented, and
still each only once!
RDC Menu "Validate Custom Walk Route"

Select "Validate Custom Walk Route" from the RDC menu to have the customised walk route
validated. After a while, the result shows up. If all right:
If the walk route is not valid, it is shown what is wrong, for example:

In this case, the default walk route is used until you have corrected the error(s) and validated
anew!

Index 183
Alarm Summary 82
Index Container Summary 66
Event List 89
System Items List 148
-A-
Communication path 128
About us 8 Connector specifications RMM Mk4b 144
Acknowledging alarms 82 Container Connection Types 54
Actual Master icon 30 Container Counts dialog box 42
Address 8 Container delete function 44
Alarm Information window 83 Container handling basics 42
Alarm propagation 81 Container handling mode 43
Alarm Setup 47 Container Report 54
Alarm Summary 81 Acknowledging 60
Opening 82 Additional Data Area 57
Alarm limits 58
Alarm System
Introduction 80 Button Bar 56
Main Page 56
Alarms
Acknowledge 82 Primary Data Area 56
Alarm Summary 81 Setpoint and Measurements Area 56
Information window 83 Sub-page Alarms 59
Sub-page Communication 60
Alarms icon 29, 81
Sub-page Load Data 57
Always Visible Information 28
Sub-page Log Files 59
Automatic container deletion 23 Sub-page Measurings 57
Automatic Container Deletion Setup 48 Sub-page Operations 61
Automatic Load Data File Transfer (optional) 113 Sub-page Utility 63
-B- Container statistics 42
Container Summary 66
Backing Up Log Files 100 Container Summary Columns 67
Basic container handling 42 Container Summary Special Menu 69
Bayplan 74 Containers icon 29, 42
Bayplan Detail Pictures 76 Containers Not Communicating 26
Bayplan Overview 75 Current harbour 43
-C- Current/Next Harbour icon 30, 43
Custom Walk Route 180
Change of Container ID 137
Changing ID in controller 62
-D-
Changing setpoint in controller 61 Data Obsolescence Setup 50
Checking the Power Cabling 139 Data transfer 152
Checking the Symptoms 130 Day and Night Colour Settings 34
Checking Your Containers 129 Deleting containers
Clock Settings Dialog Box Ship Version 120 Automatically 23
Clock Settings Dialog Box Terminal Version 120 Manually 23
Clock System 118 Deleting Containers in Container Summary 70
Clock System Options 118 Deletion delay 49
Clock System Trouble Shooting 125 Delta value 24
Colour code Description of Default Walk Route 178

Dialog Box type 31 Alarms 29, 81

Discharge Phase 22 Containers 29, 42
Current/Next Harbour 30, 43
-E- Handling Mode 30, 43
LMT 29
Email address 8
Setup 29, 46
Enabling RDC Mark II 164
User 29, 36
Entering Container Data 174
Inhibit handling 85
Error Codes 55
Inspecting Log Files 99
Event Line 88
Introduction 8
Event List 88
ISO Container 54
Event Logging 88
Item Window type 32
-F- -L-
FAQ 23
LANG Owner Code 26
Fax number 8
LED appearance examples 143
Find Function in Container Summary 70
Legends 19
Finding a Ghost Container 135
Legends in bayplan/stackplan 75
-G- Library Setup 47
List Window 31
Ghost container 133, 135
LMT icon 29
Global monitoring 152
Load Data
GMS 15, 152 Automatic File Transfer (optional) 113
GMS data 152 Baplie format 115
Guidelines for Daily Operations 21 Establishing Online Connection 112
-H- Handling 110
How REFCON Identifies Reefers 115
Handling Load Data 110 Transferring the File 111
Handling Log Files 20, 98 Understanding the Data Flow 110
Handling mode 43 Understanding the Load Data File 115
Handling Mode icon 30, 43 Understanding the Transfer Log File 114
Handling the Psion Hardware 165 Using the Dialog Box 112
Harbour mode 43 Load data match 16
Harddisk Housekeeping 100 Loading Phase 22
House-keeping required 51 Local Settings 34
How Passwords Work 38 Locating the Modem 141
How to Log file activities 99
Change Input Data 33 Log File Locations 99
Handle a Ghost Container 25 Log File Management Events 101
Handle Difference between Actual and Expected Log File Manager 101
Setpoint 24 Log File Operations Take Time 101
Operate a List Window 32
Log Files handling 98
Operate the System 32
Log Trend 104
-I- Button Panel 106
Close 108
Icons Curves Section 106
Actual Master 30 Fix point 106

Index 185
Log Trend 104 Searching 11

Grid 107 Operating RDC from REFCON 160
Legends 107 Operating REFCON 32
Print 108 Operating the Master Clock System 122
Reset View 107 Operating the RDC Hand-held Computer 165
Scrolling 106 Overview of containers 17
Status Information 105
Style 107 -P-
Zooming 106
Password Administration 38
Log Viewing 103
Password Administrator Key 39
Log-in inhibit 58
Password Administrator Window 39
LOSU Owner Code 26
Password Entry 36
-M- Password protection 16
Passwords 36
Maintaining REFCON 148
Passwords in Daily Use 36
Malfunction List 144
PCT 15
Manual container deletion 23
Periodic Printout 92
Master Clock Server Identification 121
Phases of a container 21
Master Clock System 121
Phone number 8
Modem Symptom
Pick and Sort in Container Summary 69
Pick Out Criteria Syntax 71
No ID in controller 133 Picture and Window Types 30
No Location 133 Postal address 8
Stopped Communicating 132 Power Cabling check 139
Wrong ID in controller 133 Precautions regarding RDC and Container Deletion
160
Print Current Window 95
Move of Log File 99
Print screen 94
-N- Printer Setup in REFCON 92
Printing 92
Network Node Info 149
Printing on Demand 94
Next harbour 43
Protection against computer viruses 150
No communication 26
Psion 158
No Connection to Loading Computer / Terminal Entering Container Data 174
System 26 Handling the hardware 165
Non-RMM Container 55 RDC Container List picture 172
Number of Communicating Containers Incorrect 25 RDC Menu picture 170
Number of containers 42 RDC Menus and Settings 170
-O- RDC Search Function 173
RDC Settings picture 170
Online help RDC Start Picture 167
Buttons 10 RDC Start pictures 167
Contents Tab 9 Start Picture 167
Index Tab 10 Touch screen and keyboard 165
Navigation Pane 9 PTI 62
Search Criteria Syntax 12 Public networks 150
Search Tab 11

Purpose of passwords 36 RMM 14

RMM Mk4b connector specifications 144
-Q-
RMM Modem Facts 142
Quick Introduction 14 -S-
-R-
Screen Layout 28
RAND Owner Code 26 Sea mode 43
RDC 15, 158 Security Groups 38
Default Walk Route 178 Setting up REFCON 46
Enabling 164 Setup icon 29, 46
Entering Container Data 174 Short description of REFCON 15
Hand-held computer 158 Special reefer selection 85
Handling the Psion Hardware 165 Special reefers 85
Menu "Edit Custom Walk Route" 180 Stackplan 74
Menu "Receive Updated Container List" 162
Stackplan Detail Pictures 76
Menu "Send Container List" 161
Stackplan Overview 75
Menu "Update Handheld Software" 163
Standard Clock System 119
Menu "Update Status" 162
Supervision and Logging Phase 23
Menu "Validate Custom Walk Route" 181
Operating from REFCON 160 Symptom
Operating the Hand-held Computer 165
Precautions regarding Container Deletion 160
No ID in controller 133
Psion 158
No Location 133
Psion Container List picture 172
Stopped Communicating 132
Psion Menu picture 170
Wrong ID in controller 133
Psion Menus and Settings 170
Psion RDC Start Picture 167 System Inhibit List 85
Psion Search Function 173 System Items List 148
Psion Settings picture 170 System layout 14
Psion Start Picture 167 System Overview 148
Psion Start pictures 167 -T-
Psion touch screen and keyboard 165
Recommended schedule 159 Telephone number 8
Why Use? 159 The Psion RDC Container List picture 172
RDC and container deletion 49 The Psion RDC Menu picture 170
RDC walk route 178 The Psion RDC Search Function 173
RDC-monitored Containers 159 The Psion RDC Settings picture 170
Reefer container 14 The Psion RDC Start Picture 167
Reefer container counts 42 The Psion Start Picture 167
REFCON The Psion touch screen and keyboard 165
Short description 15 Third-party Software on the REFCON PC 149
System layout 14 Troubleshooting the PC-RDC connection 164
Using 17 Two-step Selection Principle 32
REFCON Log Files Setup 50 Typical modem errors 140
REFCON on public networks 150
REFCON Setup 46
-U-
Releasing the Password 37 Unit Setup 51

Index 187
User Icon 29, 36

User Interface basics 28
Using passwords 36
Using REFCON 17
Using the Bayplan/Stackplan 18
Using the Container Report 20
Using the Container Summary 19
-V-
Viruses 150
-W-
Web site 8
Welcome to new users 16
When Do I Need to Interact with the Clock System?
119
Why Use the RDC? 159
Window Types 30
Windows updates 150

Instruction Manual - Operating Guide PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Instruction Manual - Operating Guide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

REFCON

Global Container Efficiency

© 2009 Johnson Controls Denmark - Global Container Efficiency

Manual version: Instruction Manual - Operating Guide - Ship, RDC MkII

Document Revision Record

PDF created: 21-09-2009 in Aarhus, Denmark by

Part I Introduction to REFCON 8

Part II Quick Introduction 14

Part III User Interface Basics 28

Part V Basic container handling 42

© 2009 Johnson Controls Denmark - Global Container Efficiency

Part VI Container Report 54

Part VII The Container Summary 66

Part VIII Bayplan - Stackplan 74

Part IX The Alarm System 80

Part X Event Logging 88

Part XII Handling Log Files 98

© 2009 Johnson Controls Denmark - Global Container Efficiency

Part XIII Handling Load Data 110

Part XIV Clock System 118

Part XV Modem Troubleshooting 128

Part XVI Maintaining REFCON 148

Part XVII Data Transfer for Global

Part XVIII RDC Mark II 158

© 2009 Johnson Controls Denmark - Global Container Efficiency

Part XIX RDC Walk Route 178

© 2009 Johnson Controls Denmark - Global Container Efficiency

Welcome to the User's Guide

Johnson Controls Denmark ApS

© 2009 Johnson Controls Denmark - Global Container Efficiency

1.2 Using the Online Help

The Help window consists of three main parts:

The Navigation Pane

Using the Help Contents Tab

© 2009 Johnson Controls Denmark - Global Container Efficiency

Using the Help Index Tab

Using the Help Favorites Tab

The Information Pane

© 2009 Johnson Controls Denmark - Global Container Efficiency

Prints the current topic or a number of topics on the printer you

1.2.1 Searching the Online Help

Using the Help Search Tab

© 2009 Johnson Controls Denmark - Global Container Efficiency

Search Criteria Syntax

The List of Topics

© 2009 Johnson Controls Denmark - Global Container Efficiency

The Reefer Container

The REFCON System Layout

© 2009 Johnson Controls Denmark - Global Container Efficiency

Short Description of REFCON

© 2009 Johnson Controls Denmark - Global Container Efficiency

The Important Match with Load Data

2.1 Getting familiar to REFCON

Welcome to the new user

© 2009 Johnson Controls Denmark - Global Container Efficiency

2.2 Using REFCON

You get an overview of containers

You deal with a single specific container

You act on alarms

You handle log files

© 2009 Johnson Controls Denmark - Global Container Efficiency

2.2.1 Using the Bayplan/Stackplan

© 2009 Johnson Controls Denmark - Global Container Efficiency