I/A Series Intelligent SCADA - Error! Reference source not found.– Error! Reference source not found.

RTU50/RTU10/CLS
Configurator Release
Note

1101050-Y3

COPYRIGHT RESERVED

The information and design as detailed in this document is the property of Foxboro
Australia Pty Limited, and / or its Associates and must be returned on demand. It is
issued on the strict condition that, except with our written permission it must not be
reproduced, copied or communicated to any third party, nor be used for any purpose
other than that stated in the particular inquiry, order or contract with which it is issued.
The reservation of copyright in this document extends from each date appearing thereon
and in respect of the subject matter as it appeared at the relevant date.

© Foxboro Australia Pty. Ltd. 2002

ACN 000 522 261
 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

DOCUMENT REVISION HISTORY:

Rev: Date: Comments: Prep: Check: App:
X3 29-5-2001 2 IDF’s, IRIG-B added. Conitel S. Dando S. Major O. Traynor
updated. Modbus master fix
X4 26-7-2001 Backup/Restore enhanced, S. Major B. Atchison P. Holloway
intelligent directories added. IEC Shashi A.
60870-5-101 Slave fix, Batch P. Holloway
generation fix, TOOL fix & Install
fix. Mods to IEC 60870-5-101
Slave, DNP3 Slave & DNP3
Master.
X4.1 23-8-2001 TCP/IP Ver 5 added, Install fix & S. Major B. Atchison O. Traynor
DNP3 Slave fix. Shashi A.
P. Holloway
X5 5-11-2001 AndSOE, DiCount and S. Dando B. Atchison O. Traynor
SetDiCount IDF’s added, Shashi A.
SOE_queue_size parameter P. Holloway
added to optonet card, DNP slave
event buffer disablement support
added, new collision backoff
parameters added to DNP Master
and slave.
X6 27-03-2002 Modbus Master fix & DNP3 Slave S. Major B. Atchison C. Sloane for
Dial up support added. C. Sloane O. Traynor
P. Holloway
X7 24-10-2002 DNP3 Master HLSI added. S. Dando M. Gugl P Holloway
J. McDonald
Shashi A.
X8 19-Dec-02 Sirs 41902, 43008, 43124 and A. Hanlon B. Atchison O. Traynor
43127. Fixes to Conitel C. Sloane
configuration generation, sub- P. Holloway
directory naming under buildsal,
v2load procedure and running of
Riaf utility
X9 26-Mar-2003 SIR’s 43375, 43468, 43319, A. Hanlon B. Atchison P. Holloway
43127, 43124 and 42919 C.Sloane
Added DNP3 Master Custom A. West
Polling and other fixes
Y1 Not
Released
Y2 Not
Released
Y3 16-Sep-2003 SIR’s 43685, 43719 and CR A. Hanlon J. McDonald P. Holloway
FW#205 C. Sloane

I/A Series Intelligent SCADA System Page 3 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

Table of Contents
1. INTRODUCTION...............................................................................................................................5

2. FUNCTIONALITY AND COMPATIBILITY .......................................................................................5

2.1 CONFIGURATOR SOFTWARE ................................................................................................................5
2.2 VERSION COMPATIBILITY .....................................................................................................................6
2.3 SUPERCEDED VERSIONS....................................................................................................................11
3. CHANGES SINCE PREVIOUS RELEASE.....................................................................................11
3.1 NEW FUNCTIONALITY .........................................................................................................................11
3.2 ENHANCED FUNCTIONALITY ...............................................................................................................11
3.3 DEFECT CORRECTION........................................................................................................................11
3.4 DELETED FUNCTIONALITY ..................................................................................................................12
4. SPECIAL ADVICE AND KNOWN BEHAVIOUR ...........................................................................12

5. INSTALLATION/UPGRADE INSTRUCTIONS...............................................................................12
5.1 SAVING DATA FROM AN EXISTING INSTALLATION. .................................................................................13
5.2 INSTALLING RTUCFG .......................................................................................................................14
5.3 CONFIGURING THE W ORKSTATION .....................................................................................................15
5.4 USING THE RTU CONFIGURATOR WITH MULTIPLE RTU SOFTWARE PARTS...........................................15
6. VALIDATION AND VERIFICATION STATEMENT........................................................................15

7. RELATED DOCUMENTATION ......................................................................................................15

8. CUSTOMISATIONS........................................................................................................................16
8.1 CUSTOMISING C50CFG.BAT ............................................................................................................16
8.2 CUSTOMISING RUNTOOL.BAT..........................................................................................................16

I/A Series Intelligent SCADA System Page 4 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

1. Introduction
This release note describes the release of the RTU50/ RTU10/ CLS Configurator Software identified
as part number 1101050, revision Y3 (built from internal baseline 3.18). In particular, this note
describes:
• The functionality provided in this part number,
• Compatibility information,
• Changes made since the last release of this part number (both defect fixes and additional
functionality),
• Special advice and known behaviour,
• Installation and upgrade procedure,
• The assurance activities that have been conducted to demonstrate that the product is fit for
release, and
• Related documentation.
Users should be aware that, at the time of product release, there remain outstanding incidents (see
Section 4 for details). The incidents selected for rectification in revision Y3 have been chosen with
the specific aim of reducing risks to projects worldwide. Project managers and customers requiring a
more detailed assessment of the advantages and disadvantages of adopting 1101050-Y3 for their
specific projects should contact the SCADA Product Support Manager (email: sps@invensys.com).

IMPORTANT NOTE: Updating the RTU Software on a PC using InstallShield will cause the RTUCFG
to be UNINSTALLED AND REINSTALLED automatically. This means that all RTUCFG data will be
deleted even if a RTUCFG upgrade is not meant to take place. Following one of the procedures
outlined in section 5.1 to backup and restore the data avoids this problem.

2. Functionality and Compatibility

This release is installed using a graphical Windows installation program, rather than the DOS-based
installation program provided in earlier releases. In most cases, other components, such as specific
RTU Software releases, are bundled in the same installation program. The appropriate release notes
for those components are also provided on the release media.
In accordance with Microsoft guidelines, the default installation directory was changed and may differ
from some earlier releases. The default installation directory is now:
C:\Program Files\Foxboro\RTU Configurator

2.1 Configurator Software

This release supports C2025 Conitel Slave, C2025 Conitel Master, C300 Conitel Slave, Baker Slave,
LN57 Slave, Harris 5000/5500/6000 Slave, Modbus Slave, Modbus Master, FoxCom Master, DNP3
Master, DNP3 Slave, IEC 60870-5-103 Master, IEC 60870-5-101 Slave, WISP+ Slave and WISP+
Master Communications protocols, the RTU50 OptoNet Node Card, Communications Line Server,
IDF Calculations, SALL, IRIG-B, all RTU50 I/O cards and the RTU10.

PARADOX Runtime 4.5 part number 1101035 (rev A or rev B) is required for running RTU
Configurator and is included as part of this release. The files contained in this release are all used by
"Paradox" (Borland's database product) to create and edit databases for the RTU/CLS. This release is
compatible with Paradox 4.5 (1101035 rev A or B).

I/A Series Intelligent SCADA System Page 5 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

Users wishing to create SALL (State And Logic Language) applications will also need to install the
SALL Support Files in the “buildsal” subdirectory of the installation directory. These files are RTU
Software version specific and are supplied with each RTU Software release.

The following file categories are used by RTUCFG:

*.bat Batch
*.db database table
*.exe DOS/Windows executable program
*.f* data entry form
*.h ‘C’ program header
*.ico windows icon
*.lib program library
*.mak command script
*.mb memo table
*.pif program info
*.px table index
*.sc Script
*.set data setting
*.x* secondary index
*.y* secondary index
*.val validation files

Within the installation directory, all user-configured RTU/CLS data is stored in the “RTUDATA”
subdirectory. All Configurator and data validation information is stored in the “TYPE” subdirectory.
All RTU Configurator program modules are stored in the installation directory itself.
RTUCFG requires the “buildsal” directory and contents to build SALL applications from within the
RTUCFG menus. These files may also be used to build SALL applications from the Windows
Command Prompt.
SALL calculation support files are typically stored in the buildsal subdirectory of the installation
directory. Users wishing to use the RTU Configurator with more than one RTU Software part number
must move the SALL support files to part number specific subdirectories, e.g. “buildsal\1101155”.
This can be done using the ‘multpart’ batch file supplied with the RTU Configurator.
Some previous releases of RTUCFG have contained a set of utilities with the release media to
achieve compatibility with older RTU Software sets. No such utilities have been included with this
release of RTUCFG.
The ‘multpart’ tool is found in the RTU Configurator installation directory. It copies SALL, IDF and
RIAF support files for the specific RTU Software part number to an appropriate folder in the buildsal
directory. Using this tool allows RTUCFG to support the compilation of SALL and IDF source files for
many RTU Software part numbers. ‘Multpart’ must be run every time a new version of the RTU50
Software and Utilities is installed. Type ‘multpart’ and hit Enter for some command line examples.
Intrinsic Database Functions (IDF’s) will only be available if the IDFC.EXE utility has been installed
and is available to RTUCFG. This file is normally installed to the Utilities directory during the
installation of the RTU50 Software and Utilities. For an explanation of IDF usage see the RTU50
Intrinsic Database Function User Manual (part number, 2005604).

2.2 Version Compatibility

The Configuration File Specification has not been updated for this release with only maintenance
activities undertaken. For further details please contact the SCADA Product Support Manager (email:
sps@invensys.com).

I/A Series Intelligent SCADA System Page 6 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

The following table indicates the RTU50/ RTU10/ CLS Software versions, modules and features
supported by the various releases of RTUCFG. Configuration files (.CFG) produced by RTUCFG
should only contain definitions for those modules actually supported by the RTU Software in use. If
any module defined in the configuration file is not supported by the RTU Software, the RTU/CLS will
not run on-line.
RTU Software Module Support Added RTUCFG Version
Version
1101019- up to -D C2025 Conitel, ADi, TDO Not applicable—use DBE
1101019-E & later Gas Calcs, AO All
1101019-F & later 20Ai, CP1 All
1101024- up to -H LN57, ADi, TDO Not applicable—use DBE
1101024-J & later 20Ai, AO, CP1 1101050-C (Rev 1.3) & later
1101024-L & later LN57 Raise/Lower controls added 1101050-C (Rev 1.3) & later
1101036- & later C2025 Conitel, ADi, AO, CP1, TDO All
1101036-C & later 20 Channel Ai Card All
1101036-E & later C2025 Conitel Raise/Lower controls 1101050-B & later
added
1101036-J & later C2025 Conitel Bi/Unipolar analogs, 1101050-K (Rev 2.5.1) & later
configure more communications
parameters
1101040- & later C300 Conitel, 20Ai, ADi, AO, CP1, TDO 1101050-B & later
1101040-F & later C300 Conitel SOE selective on scan 1101050-E & later
groups
1101040-J & later C2025 Conitel Bi/Unipolar analogs, 1101050-K (Rev 2.5.1) & later
configure more communications
parameters
1101042- & later Baker, 20Ai, ADi, AO, CP1, TDO All
1101042-C & later Baker Bi/Unipolar analogs, configure 1101050-K (Rev 2.5.1) & later
more communications parameters
1101059- & Harris 5000/5500, 20Ai, ADi, AO, CP1, 1101050-E (Rev 2.0) &
1101059-A TDO 1101050-F (Rev 2.2)
1101059-B Harris 5000/5500, Harris 6000, 20Ai, ADi, 1101050-H (Rev 2.3) only
AO, CP1, TDO
1101059-C & later Harris 5000/5500, Harris 6000, 20Ai, ADi 1101050-J (Rev 2.4) & later;
with Chatter Filter, AO, CP1, TDO recommend J4 (2.4.5) or later
1101060- & later Indactic 2033, 20Ai, ADi, AO, CP1, TDO 1101050-E (Rev 2.0) & later
1101065- & later C2025 Conitel, VDEW, HLSI, 20Ai, ADi, 1101050-F (Rev 2.2) & later;
AO, CP1, OptoNet, TDO recommend J4 (2.4.5) or later
1101074-(Beta 1) C2025 Conitel, LN57, HLSI, 20Ai, ADi, 1101050-D (Rev 1.4) only
AO, CP1, OptoNet Beta 1 Only, TDO
1101074-(Beta 2) OptoNet (Beta 2) 1101050-E (Rev 2.0) only
1101074-A & -B OptoNet 1101050-E (Rev 2.0) only
1101074-C & later Nonvolatile OptoNet points, ACT 1101050-F (Rev 2.2) & later;
recommend J4 (2.4.5) or later
1101074-D & later C2025 Conitel Bi/Unipolar analogs, 1101050-K (Rev 2.5.1) & later
configure more communications
parameters (C2025 Conitel and LN57),
remove LN57 restriction on scan length
1101075-(Beta 1) C2025 Conitel, Gas Calcs, HLSI, 20Ai, 1101050-D (Rev 1.4) only
ADi, AO, CP1, OptoNet Beta 1 Only,
TDO
1101075-(Beta 2) OptoNet (Beta 2) 1101050-E (Rev 2.0) only
1101075-A OptoNet 1101050-E (Rev 2.0) only
1101075-B Nonvolatile OptoNet points, ACT 1101050-E(Rev 2.0 & later;

I/A Series Intelligent SCADA System Page 7 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

RTU Software Module Support Added RTUCFG Version

Version
recommend J4 (2.4.5) or later
1101075-C & later C2025 Conitel Bi/Unipolar analogs, 1101050-K (Rev 2.5.1) & later
configure communications parameters
1101076- & later LN57, HLSI, 20Ai, ACT, ADi, AO, CP1, 1101050-J2 (Rev 2.4.2) &
OptoNet, TDO later; recommend J4 (2.4.5) or
later
1101076-B & later Configure communications parameters, 1101050-K (Rev 2.5.1) & later
remove LN57 restriction on scan length
1101084- & later C2025 Conitel DCIU & DNP3 1101050-K5 (Rev 2.5.5) &
later
1101085_ & later C2025 Conitel DCIU 1101050-J5 (Rev 2.4.5) &
later
1101085_1 & later C2025 Conitel DCIU 1101050-J7 & later
1101085-B & later C2025 Conitel DCIU 1101050-M (Rev 2.6.1) & later
1101085-C & later C2025 Conitel DCIU 1101050-M6 (Rev 2.6.6) &
later
1101087-A & later C300 Conitel and LN57 and standard I/O 1101050-K (Rev 2.5.1) & later
cards; configure communications
parameters, remove LN57 restriction on
scan length
1101089_ & later Modbus Slave protocol and standard I/O 1101050-K (Rev 2.5.1) & later
cards
1101089A & later Modbus Slave protocol and standard I/O 1101050-M (Rev 2.6.1) & later
cards
1101101_ & later DNP3 and FoxCom Master 1101050-N1 (Rev 2.7.1) &
later
1101103_ & later ACT Sync Check 1101050-N(Rev2.7) & later
1101118A & later C2025 Conitel/Baker DCIU 1101050-M (Rev 2.6.1) & later
1101118B & later C2025 Conitel/Baker DCIU 1101050-M6 (Rev 2.6.6) &
later
1101119_ & later DNP3 1101050-K5 (Rev 2.5.5) &
later
1101125_ & later C2025 Conitel DCIU and Modbus Slave 1101050-M6 (Rev 2.6.6) &
later
1101126_ & later C2025 Conitel Slave and Modbus Slave 1101050-M6 (Rev 2.6.6) &
later
1101128_ & later Event Logger 1101050-N1 (Rev 2.7.1) &
later
1101130_ & later DNP3 and FoxCom Master 1101050-N1 (Rev 2.7.1) &
later
1101131_ & later FoxCom Master and Modbus Slave 1101050-N1 (Rev 2.7.1) &
later
1101132_ & later C2025 Conitel Master/Slave and Modbus 1101050-N1 (Rev 2.7.1) &
Slave later
1101133_ & later Modbus and DNP3 Slaves 1101050-N1 (Rev 2.7.1) &
later
1101135_ & later Harris and C2025 Conitel Slaves 1101050-N1 (Rev 2.7.1) &
later
1101038_ & later Modbus Master and C2025 Conitel 1101050-P2 (Rev 2.8) & later
1101141_ & later Communication Line Server (TCP CLS) 1101050-S (Rev 2.11) & later
1101143_ & later IEC 60870-5-103 Master, Modbus Slave 1101050-S3 (Rev 2.13) &
& C2025 Conitel later
1101145_ & later IEC 60870-5-103 Master, Modbus Master 1101050-S3 (Rev 2.13) &

I/A Series Intelligent SCADA System Page 8 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

RTU Software Module Support Added RTUCFG Version

Version
& DNP3 later
1101150_ & later WISP+ Slave & Master, IEC 60870-5-103 1101050-T (Rev 2.14) & later
Master
1101153_ & later CLS, IDF’s, TCPIP 1101050-T6 (Rev 2.46) &
later
1101154_ & later AC Transducer, standard I/O cards, IDF’s, 1101050-T6 (Rev 2.46) &
IEC 60870-5-101 slave, IEC 60870-5-103 later
Master, WISP Master & Slave
1101155_ & later AC Transducer, standard I/O cards, IDF’s, 1101050-T6 (Rev 2.46) &
C2025 Conitel Master & Slave, DNP3 later
Master & Slave, IEC 60870-5-101 Slave,
IEC 60870-5-103 Master, Modbus Master
& Slave, Serial Event Logger, FoxCom
Master
1101155B & later Modbus Master Advanced options added, 1101050-W1 (Rev 2.71) &
FoxCom Master Removed later
1101155D Multi IO card, Condensed Package IO 1101050-X4 (Rev 2.87)
card, FoxCom Master, Harris
5000/5500/6000 Slave, TCPIP, C300
Conitel Slave
1101155E WISP+ Master and Slave 1101050-X5 (Rev 2.91)
1101155F DNP3 Slave dial up 1101050-X6 (Rev 3.00)
1101155H DNP Master over serial ports and LN57 1101050-X7 (Rev 3.12) &
later
1101155K DNP3 Custom Polling 1101050-X9 (Rev 3.14) &
later
1101155L No new functionality. Maintenance issues 1101050-Y3 (Rev 3.18) &
only. later
1101165_ & later DNP3 Slave, Poletop I/O cards, Poletop 1101050-T6 (Rev 2.46) &
Power supply/Battery charger card later
1101166_ & later AC Transducer, standard I/O cards, IDF’s, 1101050-U (Rev 2.60) & later
DNP3 Master & Slave, Foxcom, Modbus
Master & Slave, TCPIP
1101170_ & later Modbus Master, DNP3 Slave 1101050-X (Rev 2.77) & later
1101177_ & later AC Transducer, standard I/O cards, IDF’s, 1101050-W1 (Rev 2.71) &
C300 Conitel, C2025 Conitel Slave, DNP3 later
Master & Slave, Harris, Modbus Master &
Slave
Table 1: Configurator Support for RTU Software Versions

The table below summarises the Configurator support for various modules.
RTUCFG Version
1101050-A (Rev 1.1) & later
1101050-B (Rev 1.2) & later
1101050-C (Rev 1.3) & later
Module Support Added
Baker Communications Protocol
C2025 Conitel Communications Protocol
Calculations
20 Channel Ai Card
ADi Card
AO Card (2 and 4 Channel)
Condensed Package (CP1) Card
TDO Card
C300 Conitel Communications Protocol
LN57 Communications Protocol

I/A Series Intelligent SCADA System Page 9 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

RTUCFG Version Module Support Added

1101050-D (Rev 1.4) OptoNet Node Card (Beta 1 only)
1101050-E (Rev 2.0) & later Indactic 2033 Communications Protocol
Harris 5000/5500 Communications Protocol
AC Transducer Card
OptoNet Node Card (Beta 2 and production release)

1101050-F (Rev 2.2) & later Nonvolatile OptoNet points

Logical RTUs in Harris 5000/5500
Harris 6000 Communications Protocol (initial)
VDEW Master Communications Protocol
1101050-H (Rev 2.3) & later Harris 6000 Communications Protocol (1101059B)
1101050-J (Rev 2.4) & later Harris 6000, ADI Chatter Filters
1101050-J2 (Rev 2.4.2) Altered AC Transducer engineering unit scaling (intended
for Beta testing with 1101076- only)
1101050-J4 (Rev 2.4.5) Correction to J2
1101050-J5 (Rev 2.4.5) Conitel DCIU addition
1101050-J7 (Rev 2.4.5) Conitel DCIU changes
1101050-K (Rev 2.5.1) Modbus Slave protocol and DNP3 protocols. Supports
Uni/Bipolar analogs for C2025 Conitel, enhanced
communications parameters for C2025 Conitel and LN57
1101050-K5 (Rev 2.5.5) DNP3 protocol updated
12-Channel Serial Card added
1101050-M (Rev 2.6.1) 12 port serial cards
CPU serial cards
Modbus Slave protocol on comm 2 and 12 port serial
cards
Calculations can use comm 2 and 12 port serial cards
Choice of version number when using “Customised” RTU
Software
Station address editing (limited) permitted for Conitel
Master logical RTUs
Extra RTU Software versions added
Can select normal/extended addressing for Indactic
1101050-M6 (Rev 2.6.6) Add P/N’s 1101085C, 1101118B, 1101125_ and
1101126_
Raise/Lowers to Calculation AI’s for 1101036J,
1101085C and 1101118B
Allow TDO (10 Amp) for all appropriate P/N’s
Allow CP Main and 7 Slot Backplanes for all P/N’s
Fix C2025 Conitel Master Win95 crash problem
Fix CPU card for CP Main and Test Rig file types
1101050-N (Rev 2.7) Add P/N 1101103_
Add AC Transducer Sync Check
Disable new LN57 config file format
1101050-N1 (Rev 2.7.1) Add P/N 1101128_
Add FoxCom Master
Add Event Logger
Add Error Log
1101050-P1 (Rev 2.8) Add P/N 1101129
Add P/N 1101097
Add P/N 1101101
Add ModBus Master
1101050-P2 (Rev 2.8) Add P/N 1101138
Update Modbus Master & DNP3

I/A Series Intelligent SCADA System Page 10 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

RTUCFG Version Module Support Added

1101050-R (Rev 2.9) Add IDF Calculations & Analog Filtering
Update DNP3 (Internal Release for testing only)
1101050-R2 (Rev 2.10) Add IDF Calculations & Analog Filtering
Update DNP3, Update Logical RTU notation
1101050-S (Rev 2.11) Add TCP CLS, extend availability of IDF Calculations
1101050-S1 (Rev 2.12) Correction to Restore procedure
1101050-S3 (Rev 2.13) Add 1101143, 1101145 to include IEC 60870-5-103
Master
1101050-T1 (Rev 2.14) Add 1101150, to include WISP+ & IEC 60870-5-103
Master
1101050-T3 (Rev 2.17) Add 1101152, 1101153 and 1101154. Add IEC 60870-5-
101 Slave.
1101050-U (Rev 2.60) Number of enhancements, refer to MODS under Utilities
menu
1101050-W1 (Rev 2.71) Modbus Master Advanced options
1101050-X (Rev 2.77) DNP Frozen counter support added, P/N 1101170 added
1101050-X2 (Rev 2.82) Multi IO Card configuration support added
1101050-X3 (Rev 2.84) New IDF’s and IRIG-B added.
1101050-X4 (Rev 2.87) Removed P/N 1101155C, added 1101155D
1101050-X5 (Rev 2.91) 1101155E and new IDF’s added
1101050-X6 (Rev 3.00) DNP3 Slave Dial up support added, P/N 1101155F
added
1101050-X7 (Rev 3.12) DNP3 Master over serial ports, P/N 1101155H added
1101050-X8 (Rev 3.13) No additional module support – just defect correction
1101050-X9 (Rev 3.14) DNP3 Custom Polling, P/N 1101155J, 1101155K added
1101050-Y3 (Rev 3.17) No additional module support – just defect correction,
P/N 1101155L added
Table 2: Configurator Support for Modules
Note: For the configuration of various module parameters, appropriate user manuals should be
consulted. These are available on the RTU / CLS Documentation CDROM (part number 2005654).

2.3 Superceded versions

The 1101050-Y3 release supercedes all earlier versions of RTU Configurator.

3. Changes Since Previous Release

3.1 New functionality

Not Applicable.

3.2 Enhanced functionality

Not Applicable.

3.3 Defect correction

SIR 43685 (CR FW#180): C50CFG (X9) does not support 4 channel AO card using software
1101155K. The support for the four channel AO card was accidentally removed if RTU was configured
using the 1101155K software. This has been rectified so the four channel AO card is now available
for configuration when using the 1101155K and later software.
SIR 43719 (CR FW#181): C50 Configurator 8 Channel serial card DNP backup Channel not
configurable. Incorrect configuration files were generated if attempting to configure DNP backup

I/A Series Intelligent SCADA System Page 11 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

channel where the primary channel was not the first Channel on the multi serial card. This has been
rectified so that if a backup channel is configured, the associated primary channel is the previous
channel on the same mutli-serial card. Additional checks were also added to the creation of backup
channels to eliminate common errors. The first of these was to check for the existence of the primary
channel that is associated with the backup channel configured. The second check was to ensure that
the channel being designated as the primary channel is not an existing backup channel in the
configuration (i.e. this eliminates the possibility of creating a backup of a backup).
CR FW#205: C50 Configurator missing firmware 1101101. The software version 1101101-J is now
selectable as the RTU software version.

3.4 Deleted functionality

Not applicable.

4. Special Advice and Known Limitations

At the time of release, there are no priority 1 defects outstanding. However, the following special
advice and behaviour of the 1101050-Y3 Configurator Software should be noted:
1) Paradox Runtime and RTUCFG have been observed to be unstable on some machines using a
Command Interpreter called “4DOS”. If problems running RTUCFG are observed when using a non-
standard DOS Command interpreter, use RTUCFG with the plain MS-DOS Command Interpreter.
2) Configuration file generation failure has been observed when running the RTUCFG on Windows
95. This has only occurred when a DNP3 Master scan point entity number is 1000 or greater. This
behaviour may also be evident on platforms other than Win NT 4.0, Win 2000 and Win XP. It is
recommended that the RTUCFG is run on Windows NT 4.0, Win 2000 or Windows XP.
3) The version compatibility information in Section 2.2 should be observed to determine those
features available in the Configurator that are not supported in some versions of the RTU/CLS
Software.
4) As mentioned in the Introduction, updating the RTU Software on a PC using InstallShield will cause
the RTUCFG to be UNINSTALLED AND REINSTALLED automatically. This means that all
RTUCFG data will be deleted even if a RTUCFG upgrade is not meant to take place. Following one
of the procedures outlined in section 5.1 to backup and restore the data avoids this problem.
5) The new 8 channel serial card does not exist in the RTU Configurator (SIR 43314). The
configuration of the 8 channel card is identical to the 12 channel serial card, therefore to configure the
8 channel serial card select the 12 channel serial card and leave the last 4 channels blank.
6) RTU Configurator should tolerate deletion of feedback points within the IEC 60870-5-101 system
(SIR 43334). The current behaviour is the termination of the application when these points are
deleted.

5. Installation/Upgrade Instructions
The RTU Configurator must be installed onto an engineer’s workstation PC from the release CDROM.
The release CDROM provides a graphical installation wizard. In accordance with Microsoft
guidelines, the RTU Configurator files will be installed under the “C:\Program Files\Foxboro”
directory, rather than in “C:\C50CFG” (as used in older releases).
If you are upgrading from an earlier version of the RTU Configurator and wish to keep the
configuration data from your previous version, you must follow the steps in the following section.
Otherwise, you may skip to Section 5.2.

I/A Series Intelligent SCADA System Page 12 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

5.1 Saving data from an existing installation.

The RTUCFG installation process installs an empty database (e.g. containing no configuration data).
If updating an existing installation of RTUCFG, any existing configuration data should be saved before
installing the new version. After the new version is installed, this data can be reloaded.
There are three methods of saving existing data before installing the new Configurator and
subsequently reloading that data into the new Configurator (listed in their recommended order of
usage):
1. Use the V2SAVE and V2LOAD batch files and paradox scripts from this new release to save all
data in the old version of RTUCFG and load this data into the new version after installation. This
is the preferred method of preserving existing data because all processing is performed in
one pass, and is therefore much faster than saving each RTU individually. The V2SAVE batch file
and script (V2SAVE.BAT and V2SAVE.SC) can be found in the V2SAVE directory on the release
CDROM. V2LOAD can be found in the RTU Configurator installation directory after installation is
completed.
NOTE: 1) If upgrading a system which contains DNP3 configuration data from a release earlier
than 2.8 this method cannot be used due to major structural changes in the protocol. In this case
method 3 below should be employed to reload data.
2) The v2save process may return error messages informing of invalid formats, but this does not
necessarily mean that the data cannot be loaded. Once (and if) the data can be loaded, it is a
good idea to compare a number of cfg files generated from the previous and current version of
the RTUCFG to identify data that could not be saved or loaded. Note that valid differences may
exist, for example bug fixes or checksum calculations may cause variances. It is recommended
that data be upgraded from the version of the RTUCFG immediately prior from the current
release.
2. Backup the data for each RTU in the database by using the “Utilities | Backup RTU”, “Utilities |
Backup Site” or “Utilities | Backup Network” menu option, and load this data into the new
installation by using the “Utilities | Restore RTU”, “Utilities | Restore Site” or “Utilities | Restore
Network” menu option. The new version of RTUCFG can reload backups produced by any earlier
version of RTUCFG after release 2.8.
3. Generate configuration files (.CFG) for each RTU in the database, and import each of these
configuration files into the new installation (using the Configurator “Utilities | Load CFG File” menu
option). The new version of RTUCFG can import configuration files produced by all earlier
versions of RTUCFG. This method does not preserve information about the RTU software
version, user identity, the RTU’s Site and the OptoNet network identity and card-file types. This is
because these details are not recorded in the configuration file, and must be re-entered manually.
NOTE: If upgrading a system which contains DNP3 configuration data from a release earlier than
2.8 this is the only method which can be used due to major structural changes in the protocol.
It is not possible to use the database tables from any previous release of RTUCFG with the new
version’s program library. Therefore it is not possible to backup all data by using DOS copy or backup
and restore. One (or more) of the three methods listed above must be used. Methods 2 and 3
(Backup RTU/ Restore RTU and Load CFG File) are used in the normal manner (refer to document
2005159 RTU50 Configuration, Programming and Diagnostic for more information).
The method for using V2SAVE and V2LOAD is described below with the sample commands given
afterwards. Type in the following commands at the Windows Command Prompt (shown in bold type
below; the ↵ symbol means press the <Enter> key). Note that if the old version of the Configurator is
installed in some location other than “C:\Program Files\Foxboro\RTU Configurator”, then
that location should be used. We assume that the release CDROM is in D: drive.
a. Change to the operating directory where the old version of the Configurator is normally
used (usually “C:\Program Files\Foxboro\RTU Configurator”).
b. Copy the V2SAVE batch file and Paradox script file from the V2SAVE directory of the
release CDROM to this operating directory.

I/A Series Intelligent SCADA System Page 13 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

c. Run the V2SAVE batch task. This will create a set of files containing the data dumped
from the existing tables (PDOXRUN should already be in the DOS path if RTUCFG has
been previously used). The dumped data files have .TXT extensions. Progress
messages are displayed during this process.
Note: Still attempt to load the data even if error messages of invalid formats are
displayed, as they are not always fatal.
d. Install the new RTUCFG in the normal manner (refer to Section 5.2).
e. Copy the dumped .TXT files to the new installation directory (usually “C:\Program
Files\Foxboro\RTU Configurator”) if not already there.
f. Run the V2LOAD batch task in the installation directory to load the table data previously
dumped with the V2SAVE script. Progress messages will be displayed during this
process.
g. After the data from the previous version has been loaded, the V2SAVE and V2LOAD
scripts and .BAT files are no longer required, and they may be deleted (when executed,
.SC files create corresponding .SC2 files, which may also be deleted)
h. Start the RTU Configurator in the usual manner.
Example of the command line prompt output
C:\> cd Program Files\Foxboro\RTU Configurator ↵
C:\Program Files\Foxboro\RTU Configurator> copy d:\v2save\*.* ↵
C:\Program Files\Foxboro\RTU Configurator> v2save ↵

Run the installation wizard from the CDROM via the “Start | Run” menu. If installation
completed without error:
C:\Program Files\Foxboro\Rtu Configurator> v2load ↵
C:\Program Files\Foxboro\Rtu Configurator> del v2*.* ↵
C:\Program Files\Foxboro\Rtu Configurator> c50cfg ↵

Note: Once this version of RTUCFG has been installed, do not use data saved by this version with
any earlier version of RTUCFG, as the data formats are incompatible. Also note that since X8 version
of the configurator the .TXT files are not deleted so must be manually deleted if they are no longer
required.
IMPORTANT NOTE: When upgrading from a version prior to Rev W and the RTU software build
version is 12.4.5 or later (the version number is displayed in TOOL), all DNP3 Master communication
port and associated logical RTU details will need to be manually updated by the user once the data
has been loaded. This is due to a number of parameters being moved from the DNP3 Master
communications port to the logical RTU’s, and the inclusion of new logical RTU parameters.

5.2 Installing RTUCFG

For most users, a short introductory menu will be displayed automatically when the release CDROM
is loaded into the engineer’s workstation. If this does not happen automatically, open the file
D:\menu.exe, where D is the drive letter of the CDROM drive.
The introductory menu contains links to the installation program for the RTU Software and Utilities,
and for several other related Foxboro products. Make sure the check box next to the RTU Software
and Utilities options is checked, then click Install to begin installation. Follow the on-screen
instructions to select the installation directory and to choose the components that you wish to install.
Accepting the default installation path is strongly recommended.
Depending on the components selected during the installation, a number of desktop shortcuts will be
created of which one will be for the RTU Configurator.

I/A Series Intelligent SCADA System Page 14 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

To ensure correct operation of the installed components, the installation program will automatically set
several environment variables. Windows 95, 98 and Millennium Edition users will need to restart
Windows for these changes to take effect.
Important Note: Users upgrading from versions before 1101155-F must manually remove the
environment variable settings they made when installing the earlier version. For Windows NT, 2000
and XP Professional users, this may be done using the Control Panel -> System -> Environment
dialog. Windows 95, 98 and Millenium Edition users will need to manually edit the C:\autoexec.bat
file. If any old settings are not removed, the RTU Configurator may not operate correctly.

5.3 Configuring the Workstation

After installation, the PATH environment variable will include the installation directories of the RTU
Configurator, Utilities and Paradox Runtime Engine, the C50_UTIL variable will contain the installation
directory of the RTU50 Utilities, and the C50_WORK variable will contain the Windows temporary
directory, e.g. C:\WINDOWS\TEMP. Users should ensure that the Windows TEMP directory
nominated in the C50_WORK environment variable exists.
If SALL applications are to be compiled the appropriate C compiler must also be included in the PATH
environment variable.
• For RTU10, the Diab Compiler Suite 4.2b is required.
• For RTU50 Real Mode Software, Turbo C++ 3.0 is required.
• For RTU50 Protected Mode Software, Watcom C++ 11.0a or OpenWatcom version 1.0 (available
for free download from http://www.openwatcom.org) is required.
Please consult your operating system’s manual for instructions on how to set environment variables.

5.4 Using the RTU Configurator with multiple RTU Software parts
After RTU50 software and the utilities have been installed run multpart. This batch program copies
sall, riaf, and idf files for the specific part number (refer to section 2.1).

6. Validation and Verification Statement

A variety of verification and validation activities have been conducted on the 1101050-Y3 Configurator
Software and Utilities prior to their release. The assurance strategy for 1101050-Y3 consisted of 3
parts:
1. Change Design and Code Reviews
The design and source code of all baseline changes were documented and reviewed by peer
developers before acceptance for system integration.
2. Enhancement / Incident Retest
For each enhancement / incident addressed in this release, testing was conducted by an
independent team to ensure that the incident was fixed satisfactorily and that there were no
unintended side-effects from the modification. Test cases are documented in Incident Resolution
Checklists.
3. Platform compatibility
Tests were performed to assure Configurator operation on Windows NT, Windows 98, Windows
2000 and Windows XP.

7. Related Documentation
For further information, please refer to the following documents. These are available on the RTU /
CLS Documentation CDROM (part number 2005654).

I/A Series Intelligent SCADA System Page 15 of 16

 RTU50/RTU10/CLS Configurator Release Note
1101050-Y3

Document no. Title Version

2005550 RTU50 Configuration User Manual 1.1
2005604 RTU50 Intrinsic Database Functions User Manual 1.1

8. Customisations

8.1 Customising C50CFG.BAT

RTUCFG is run as a Paradox Runtime application initiated by the file C50CFG.BAT. The command
line “PDOXRUN -stack 32 -extk 16000 C50Cfg” in the batch file initiates C50CFG, and
includes a stack size parameter.
The -extk 16384 limits the amount of memory used by Paradox Runtime to 16MB. This is only
necessary for computers that contain more than 16MB of memory.
On some computers the stack size may be reduced to about 20 (ie 20 kilobytes) for a small gain in
performance. If this is done it is possible that RTUCFG will halt with a resource error for insufficient
stack space. If this occurs increase the -stack parameter value.
If RTUCFG is being run on a laptop (or other computer) that has a monochrome monitor attached to a
colour video controller, some displays may be difficult to read. To force the use of a monochrome
colour set, add the switch -b&w to the command line ie: “PDOXRUN -stack 32 -extk 16000 -b&w
C50Cfg”. This may make the displays more legible on some LCD screens, or the original colour
settings may be clearer.
If snow appears when RTUCFG updates the screen (usually this only occurs on CGA cards/monitors),
this can be prevented by adding the -snow switch to the command line: “PDOXRUN -stack 32 -extk
16000 -snow C50CFG”
The NextTask command in C50CFG.BAT must not be altered.

8.2 Customising RunTOOL.BAT

RTUCFG calls the RunTOOL.BAT file to activate TOOL. This batch task may be modified as desired
to suit your installation. If you require other programs to be run before or after TOOL (for example to
exchange COM1 and COM2 so that TOOL uses the COM2 port) then these may be added to this
batch file.
Early releases of TOOL hid the cursor, and did not restore the cursor when TOOL was terminated.
The MODE co80 command in this batch file restores the cursor after TOOL is run. If this is not used
the cursor may remain invisible within RTUCFG after returning from TOOL.

I/A Series Intelligent SCADA System Page 16 of 16