RTU-2

SCD5200/RTU50 Software Release Note 1101155-L

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 2000 ACN 000 522 26

RTU50/SCD5200 Software Release Note 1101155-L

DOCUMENT REVISION HISTORY: Rev:

Date:

Comments:

Prep:

Check:

App:

_

29 Mar 1999

Initial Release

C. Weaver

P. Ellis

P. Holloway

A

23 Jun 1999

Release 12.2.1 1101155-A

C. Weaver

P. Johns

C. Sloane

B

06 Mar 2000

Release 12.4.2 1101155-B

C. Weaver

P. Johns

P. Ellis

C

D

27 Jul 2001

Release 12.5.0 1101155-D

J. McDonald

P. Holloway C. Sloane B. Atchison

O. Traynor

E

20 Dec 2001

Release 12.6.2 1101155-E

J. McDonald


O. Traynor

F

26 Mar 2002

Release 12.6.4 1101155-F

J. McDonald


O. Traynor

H

07 Nov 2002

Release 12.6.6 1101155-H

J. McDonald


O. Traynor

J

20 Dec 2002

Release 12.6.7 1101155-J

J. McDonald

A. West C. Sloane B. Atchison

O. Traynor

K

28 Mar 2003

Release 13.0.0 1101155-K

J. McDonald

A. West C. Sloane B. Atchison

P. Holloway

L

15 Sep 2003

Release 13.2.2 1101155-L

J McDonald

C. Weaver A. Hanlon

P. Holloway

I/A Series Intelligent SCADA System

Page 3 of 19


Table of Contents 1.

INTRODUCTION...............................................................................................................................5

2.

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

2.1 2.2 2.3 2.4 2.5 2.6

RTU SOFTWARE .................................................................................................................................6 UTILITIES ............................................................................................................................................8 SALL SUPPORT FILES .........................................................................................................................9 RTU CONFIGURATOR AND P ARADOX RUNTIME ENGINE ........................................................................9 I/O CARD AND DCB FIRMWARE............................................................................................................9 SUPERCEDED VERSIONS....................................................................................................................11

3.

CHANGES SINCE PREVIOUS RELEASE ....................................................................................11

3.1 3.2 3.3 3.4

NEW FUNCTIONALITY .........................................................................................................................11 ENHANCED FUNCTIONALITY ...............................................................................................................11 DEFECT CORRECTION........................................................................................................................12 DELETED FUNCTIONALITY ..................................................................................................................13

4.

KNOWN PROBLEMS AND LIMITATIONS....................................................................................13

5.

INSTALLATION/UPGRADE INSTRUCTIONS...............................................................................14

5.1 INSTALLING FROM CDROM ...............................................................................................................14 5.2 LOADING THE SOFTWARE ONTO AN RTU ............................................................................................15 5.2.1 Loading software using RTV ................................................................................................15 5.2.2 Loading software using TOOL32..........................................................................................16 6.

VALIDATION AND VERIFICATION STATEMENT........................................................................17

7.

RELATED DOCUMENTATION ......................................................................................................18


Page 4 of 19


1. Introduction This release note describes a major release of the SCD5200 and RTU50 Protected Mode Software and Utilities identified as part number 1101155, revision L (built from internal baseline 13.2.2). In particular, this note describes: 





The functionality provided in this part number, Associated I/O card and DCB firmware required for the use of each RTU Software subsystem, Changes since the last release of this part number (both defect fixes and additional functionality),



Outstanding problems and known risks,



Installation and upgrade procedure,



The assurance activities that have been conducted to demonstrate that the product is fit for release,



Related documentation, and



The contents of the release media.

Note: Users are encouraged to read this entire release note before attempting to install or use the subject RTU Software and Utilities. In particular, the RTU Software is now comprised of two binary files 1101155L.Z and 1101155L.DLL, both of which must be loaded into the RTU flash memory in order to boot the RTU successfully.

This release note covers the changes made since the previous release, 1101155-K. If upgrading from an earlier release, the reader should also read the release notes for the intervening releases. These release notes are included with this release note on the 1101155-L release media. 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 L 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 1101155-L for their specific projects should contact the SCADA Product Support Manager (email: [email protected]).

2. Functionality and Compatibility The RTU Software and Utilities are installed using a graphical Windows installation program. The installer covers the 1101155-L release and also the RTU Configurator (1101050-Y2) and Paradox Runtime Engine (1101035-B). Depending on the package you have purchased, the release media may also include installation programs and release notes for the corresponding System Configurator 1 (1101191-_) , Remote Terminal Viewer (1101192-A) and RTU50/SCD5200 ISaGRAF Workbench Extensions (1101193-A) products. Both the installation program and the RTU Utilities support Windows 95, Windows 98, Windows ME, Windows NT 4.0 (SP6), Windows 2000 and Windows XP. In accordance with Microsoft guidelines, the default installation directories of various components have been changed from those used in pre-1101155-F releases. Table 1 lists the components provided in this release and their default installation directories. The names appearing in the table are also the names that appear in the Custom Installation page of the installation program. Each of these components is described in the following sections.

1

The 1101191-_ System Configurator release does not show 1101155-L in the part number list. 1101155-K should be selected instead for equivalent functionality.


Page 5 of 19


Component Name:

Description:

Installation Directory:

RTU Software

RTU Software executable files

C:\

RTU Utilities

RTU Utility programs. These are described in Section 2.2.

C:\Program Files\Foxboro\RTU Utilities

RTU Configurator

RTU configuration file editor software

C:\Program Files\Foxboro\RTU Configurator

Paradox Runtime Engine

Borland Paradox runtime support files (required by RTU Configurator)

C:\Program Files\Foxboro\Paradox Runtime Engine

SALL Support Files

Files needed to compile SALL applications (required by RTU Configurator)

C:\Program Files\Foxboro\RTU Configurator\BuildSal

Embedded Firmware

The latest versions of the embedded firmware for RTU I/O and DCB cards

C:\Program Files\Foxboro\Embedded Firmware

Release Notes

Release Notes for the RTU Software and Utilities, Embedded I/O and DCB card firmware, RTU Configurator and the Paradox Runtime Engine

C:\Program Files\Foxboro\Release Notes

Table 1: Components provided in this release

2.1 RTU Software The 1101155-L RTU Software may be used on an 80386SL RTU50 CPU board (0301040), an 80486 RTU50 CPU board (0301049/0301057), a P3E RTU50 CPU board (0301061), or an SCD5200 CPU board (0301060). The RTU Software operates in 32-bit protected mode and is able to access the full memory capacity of each type of CPU board. In the case of the 80386SL board, memory capacity is 2MB. For 80486, P3E and SCD5200 CPU boards, the memory capacity is 16MB. This release (and all previous releases since 1101155-B) uses the Microsoft “Flash File System 2” in which files are held in a DOS-compatible format. Loading of this software requires the CPU board to be fitted with a Flash File System 2 compatible bootstrap PROM: 1037461-D for 80386SL RTU50 CPU boards, 1037532-_ for 80486 RTU50 CPU boards, or 1037586-_ for P3E and SCD5200 CPU boards. This software is not compatible with the 1037377-D bootstrap for 80386SL CPU boards. The 1101155-L software is designed for use with the RTU Configurator (part 1101050) version Y2 or later and the System Configurator (part 1101191) version _ or later. Earlier versions of the RTU Configurator will function adequately, but may not support all subsystems and features provided in this release. Table 2 lists the subsystems present in the 1101155-L RTU Software. For each subsystem, the table indicates whether the RTU Configurator and/or the System Configurator support the subsystem. The table also lists the versions of I/O card firmware or DCB firmware needed to correctly support all features of each subsystem in the 1101155-L RTU Software. Customers with enquiries about whether they need to upgrade I/O card or DCB firmware should contact the SCADA Product Support Manager (email: [email protected]). The latest released versions of the I/O card and DCB firmware are provided in the “Embedded Firmware” component of the installer (see Section 2.5 for more information).


Page 6 of 19


Subsystem:

RTUCFG support:

SysCFG support

Minimum firmware versions:

Current firmware versions:

AC Transducer Card

Yes

Yes

1037419 Rev. _

1037419 Rev. E

Analog Output Card

Yes

Yes

1037348 Rev. _

1037348 Rev. C

Condensed Package I/O Card

Yes

No

1037357 Rev. B

1037357 Rev. C

32DI/4AI Card (ADI) – Type 1

Yes

Yes

1037275 Rev. _

1037275 Rev. E

32DI/4AI Card (ADI) – Type 2

Yes

Yes

1037553 Rev. _

1037553 Rev. _

12 Digital Output Card (TDO)

Yes

Yes

1037404 Rev. _

1037404 Rev. C

20 Analog Input Card (20AI) – Type 1

Yes

Yes

1037378 Rev. _

1037378 Rev. B

20 Analog Input Card (20AI) – Type 2

Yes

Yes

1037554 Rev. _

1037554 Rev. _

Multi I/O Card

Yes

Yes

1037562 Rev. D

1037562 Rev. D

Yes

N/A

N/A N/A

Input/Output:

Communications: 2

8 Channel Serial Card

No

12 Channel Serial Card

Yes

No

N/A

C2025 Conitel Master

Yes

No

V.23 1037276 Rev. K3 3 V.28 1037381 Rev. B

C2025 Conitel Slave

Yes

No

V.23 1037276 Rev. K3 3 V.28 1037381 Rev. B

C300 Conitel Slave

Yes

No

DNP3 Master

Yes

DNP3 Slave

3

V.23 1037276 Rev. P V.28 1037381 Rev. D

3

V.23 1037276 Rev. P V.28 1037381 Rev. D

V.23 1037276 Rev. K3 3 V.28 1037381 Rev. B

3

V.23 1037276 Rev. P V.28 1037381 Rev. D

Yes

V.11 1037584 Rev. _ V.23 1037498 Rev. H V.28 1037462 Rev. L Optical 1037497 Rev. J

V.11 1037584 Rev. _ V.23 1037498 Rev. K V.28 1037462 Rev. L Optical 1037497 Rev. K

Yes

Yes

V.11 1037584 Rev. _ V.23 1037498 Rev. H V.28 1037462 Rev. L Optical 1037497 Rev. J

V.11 1037584 Rev. _ V.23 1037498 Rev. K V.28 1037462 Rev. L Optical 1037497 Rev. K

FoxCom Master

Yes

No

N/A

N/A

Harris 5000/5500/6000 Slave

Yes

No

V.23 1037406 Rev. _ V.28 1037405 Rev. _

V.23 1037406 Rev. C V.28 1037405 Rev. E

IEC 60870-5-103 Master

Yes

No

Optical 1037414 Rev. _

Optical 1037414 Rev. A

IEC 60870-5-101 Slave

Yes

No

V.28 1037521 Rev. _

V.28 1037521 Rev. C

2

In the RTU Configurator, an 8 channel serial card can be successfully configured as 12 channel serial card where no protocols are configured on the last four channels.

3

For multi channel operation of C2025 and C300 Conitel, upgrading to t he current DCB firmware version is recommended.


Page 7 of 19


LN57-3

4

Yes

No

V.11 1037421 Rev. B V.23 1037427 Rev. B V.28 1037423 Rev. B V.28 Dialup 1037425 Rev. B

V.11 1037421 Rev. B V.23 1037427 Rev. B V.28 1037423 Rev. B V.28 Dialup 1037425 Rev. C

Modbus Master

Yes

Yes

N/A

N/A

Modbus Slave

Yes

Yes

N/A

N/A

Optonet

Yes

Yes

N/A

N/A

TCP/IP

Yes

Yes

N/A

N/A

WISP+ Master

Yes

No

V.28 1037522 Rev B

V.28 1037522 Rev B

WISP+ Slave

Yes

No

V.28 1037522 Rev B

V.28 1037522 Rev B

Intrinsic Database Functions

Yes

Yes

N/A

N/A

SALL calculations (including floating point and gas calcs)

Yes

Yes

N/A

N/A

IEC 61131-3 (ISaGRAF)

No

Yes

N/A

N/A

Serial Event Logger

Yes

No

N/A

N/A

IRIG-B Serial Time Code 5 Generator

Yes

No

V.28 1037577 Rev A

V.28 1037577 Rev A

Calculations:

Mis cellaneous :

Table 2: Features supported in 1101155-L

The installed RTU Software files have the following characteristics: File name:

File Size:

1101155L.Z

230,462 bytes

1101155L.DLL

469,900 bytes

2.2 Utilities Table 3 lists the utility programs that are provided for use with the 1101155-L RTU Software. For more information on these programs please consult the appropriate user documents (refer to Section 7). Installation of the RTU Utilities is required for correct operation of the RTU Configurator. The utilities may also be used separately.

4

The LN57-3 binaries for the LN2068 VME DCB (parts 1037422-B, 1037424-B, 1037426-C and 1037428-B) are identical to the corresponding RTU50 DCB binaries and are also included in the installation package.

5

The IRIG-B subsystem has been introduced to satisfy a particular customer’s needs and is not directly supported by the RTU Configurator for the 1101155 part number. This subsystem may be accessed via the “Customised” RTU Software option. Please consult the SCADA Product Support Manager before using this subsystem.


Page 8 of 19


Utility:

Description:

SALL.EXE

SALL calculation compiler (requires Watcom C/C++ 11.0a)

SALLHLSI.EXE

SALL serial interface protocol definition editor

RIAF.EXE

Configuration file checking and reporting utility

CFG_CRC.EXE

Configuration file CRC generator

IDFC.EXE

Intrinsic Database Function Compiler (for use with RTU Configurator, part number 1101050)

FLT2INT.EXE

Convert IEEE 754 floating point numbers to 32-bit integer representation (for use with RTU Configurator)

TOOL32.EXE

RTU diagnostic utility.

Table 3: RTU50 utility programs

2.3 SALL support files The SALL support files are needed in order to correctly generate SALL application binary files for execution on an RTU. The SALL support files consist of a batch file, buildsal.bat, that drives the SALL compilation process and several other files that are used during the compilation process. Existing SALL applications compiled with SALL versions prior to 1101155-L must be recompiled using the buildsal.bat program provided with this release in order to function correctly with the 1101155-L RTU Software. The RTU software will detect any old calculation binaries and refuse to load them. Note that Watcom C/C++ version 11.0a (Foxboro part 1101168 or 1102057) or OpenWatcom version 1.0 (available for free download from http://www.openwatcom.org) is required for the compilation of SALL calculations. For instructions on compiling SALL applications consult the appropriate user documents listed in Section 7. The SALL related functions of the RTU Configurator require installation of the SALL Support Files component. The SALL Support Files may also be used separately.

Important note: Version 11.0b of the Watcom C/C++ compiler is known to contain a number of optimisation faults, not present in version 11.0a. Foxboro does not recommend the use of version 11.0b in place of version 11.0a for compilation of SALL applications. Watcom C/C++ version 11.0a and OpenWatcom C/C++ version 1.0 are the only versions presently supported by Foxboro.

Impor tant note: In some cases, upgrading a workstation from Windows NT or Windows 2000 to later versions of Windows may corrupt the Windows registry entries for Watcom or OpenWatcom C/C++ installations. Users are advised to reinstall the compiler after upgrading the Windows version on a workstation.

2.4 RTU Configurator and Paradox Runtime Engine Information on the RTU Configurator (Foxboro part 1101050) and the Paradox Runtime Engine (Foxboro part 1101035) is covered in separate release notes. These are included in the Release Notes component of the installer.

2.5 I/O card and DCB firmware The “Embedded Firmware” component of the installation provides the most recent version of the embedded EPROM firmware for each I/O card and Dual Communications Board (DCB) supported by the 1101155-L RTU Software. The embedded firmware is listed, by part number, in Table 4.


Page 9 of 19


Each embedded firmware part has its own requirements for installation. Please consult the appropriate release note for installation instructions. These release notes are supplied in the “Release Notes” installation component, in PDF format. If you choose to install the release notes, a desktop shortcut to them will be created.

File name:

Size:

Checksum:

Description:

1037275E.BIN

11474 bytes

$C72A

32DI/4AI (ADI) Card (type 1)

1037276P.BIN

28720 bytes

$6254

V.23 Conitel DCB

1037348C.BIN

8839 bytes

$C12C

Analog Output Card

1037357C.BIN

20016 bytes

$E8DE

Condensed Package (CP1) Card

1037378B.BIN

6532 bytes

$78EE

20 Analog Input Card (type 1)

1037381D.BIN

28208 bytes

$4A83

V.28 Conitel DCB

1037404C.BIN

10922 bytes

$C6A0

12 Digital Output (TDO) Card

1037405E.BIN

28208 bytes

$2C56

V.28 Harris 5000/5500/6000 DCB

1037406C.BIN

28208 bytes

$273C

V.23 Harris 5000/5500/6000 DCB

1037414A.BIN

28208 bytes

$F374

Optical IEC 60870-5-103 DCB

39933 bytes

-

AC Transducer Card

1037421B.BIN

32768 bytes

$88A2

V.11 LN57-3 DCB

1037423B.BIN

32768 bytes

$3267

V.28 LN57-3 DCB

1037425C.BIN

32768 bytes

$5D27

V.28 LN57-3 via dialup DCB

1037427B.BIN

32768 bytes

$D933

V.23 LN57-3 DCB

1037462L.BIN

32768 bytes

$7B24

V.28 DNP3 DCB

1037497K.BIN

32768 bytes

$85C4

Optical DNP3 DCB

1037498K.BIN

32768 bytes

$6842

V.23 DNP3 DCB

1037521C.BIN

32768 bytes

$2CBA

V.28 IEC 60870-5-101 DCB

1037522B.BIN

32768 bytes

$D518

V.28 WISP+ DCB

1037553_.BIN

17015 bytes

$462E

32DI/4AI (ADI) Card (type 2)

1037554_.BIN

11369 bytes

$F92C

20 Analog Input Card (type 2)

1037562D.BIN

17975 bytes

$EC66

Multi I/O Card

1037577A.BIN

32768 bytes

$792E

V.28 IRIG-B Serial Time Generator

1037584_.BIN

32768 bytes

$97B2

V.11 DNP3 DCB

1037419E.EXE

6

Table 4: Supported I/O card and DCB firmware

6

The AC Transducer Card Firmware is comprised of two binary files that are programmed into a pair of EPROMs. These files are distributed in a self-extracting executable file. Please consult the AC Transducer Card Firmware Release Note for more information.


Page 10 of 19


2.6 Superceded versions The 1101155-L release supercedes the following versions of the RTU Protected Mode Software and Utilities: 

1101154 (all versions),



1101155 (all versions up to revision K, including all maintenance releases thereof),






1101170 (all versions)






9101001 (all versions)















9101152 (all versions).

3. Changes Since Previous Release This release incorporates a range of enhanced functionality, along with a number of defect corrections.

3.1 New functionality No major new functionality has been introduced in this release.

3.2 Enhanced functionality This release provides several functional enhancements over the previous 1101155-K release. 











All slave protocols have been reworked to improve event reporting at startup and communications restoration. This change addresses a number of customer issues regarding spurious or duplicate events being reported by slave protocols, particularly on points sourced from I/O cards (CR FW#22, SIR 43434). Other fault reports addressed by this change are included in Section 3.3. Modbus Master was enhanced to allow analog controls to be configured to accept either signed or unsigned values (CR FW#41, SIR 42524). Previously, all analog controls were assumed to be unsigned. SALL was enhanced to allow arrays to hold references to RTU database points. This allows code to loop over a set of points rather than repeating the same code fragment for each point (CR FW#47, SIR 43520). In this release, assigning values to referenced points is supported but reading values from referenced points is not supported. Support for floating point arithmetic was improved, allowing multiple ISaGRAF calculations to perform floating point calculations (CR FW#49, SIRs 25624 and 43385). SALL was enhanced to allow integer variables to be used to specify serial port numbers in addition to the existing “COM(2)” and “CHN(x)” formats (CR FW#80). SALL was enhanced to allow floating-point analog points to be updated using the new setFPAiValue function (CR FW#146).


Page 11 of 19


Support for DNP3 32-bit integer and floating point analog outputs (Object 40 variation 1, Object 40 variation 3, Object 41 variation 1 and Object 41 variation 3) has been added to DNP3 Slave (CR FW#178, SIR 43699).



Support for DNP3 32-bit floating-point analog inputs (Object 30 variation 5, Object 32 variation 5 and Object 32 variation 7), 32-bit integer analog outputs (Object 40 variation 1 and Object 42 variation 1) and 32-bit floating point analog outputs (Object 40 variation 3 and Object 41 variation 3), and mappings to corresponding point types, have been added to DNP3 Master (CR FW#178, SIR 43699).



IEC 61131-3 (ISaGRAF) was enhanced to allow access to the SALL gas calculations AGA3, AGA7 and NX19 as ISaGRAF function blocks (CR FW#202).



Both the old (RTU50) and new (SCD5200) TCP/IP configuration formats are now accepted on both types of RTU (CR FW#220).



3.3 Defect correction A number of Change Requests, raised both externally by customers and internally due to ongoing Verification and Validation processes, have been resolved in this release. Table 5 shows a list of the Change Requests that were addressed since the 1101155-K release, sorted by subsystem. Change

Incident # Description

Request # Calculations (SALL):

FW#10 43544

Changed SetDiValue function to accept local boolean variables

FW#28 43268

Calculation overruns were reported when Multiserial card was configured but not fitted.

FW#169 -

Permit fast turnaround from send to receive on RS485 two-wire channels of 8 channel Multiserial card.

Core:

FW#25 39708

Clarified numerous warning and error messages.

FW#35, 29932 FW#223

The flash file write indicator LED (fourth from the top) was not functioning on SCD5200 CPU cards. A flash file read indication has also been added using the fifth LED from the top of the status LED group.

FW#141 -

The .DLL file is now provided in compressed form to reduce flash memory usage.

FW#225 -

Slots 9, 10 and 11 of an SCD5200 file were treated as slots 1, 2 and 3 of file 2. This is still the case for internal Electrobus addressing purposes (for compatibility with RTU50 hardware), but the correct physical slot numbers are now used for configuration and diagnostics.

FW#258 -

Prevent lockup of 8-channel serial card caused by electrical interference.

DNP3 Master:

FW#11 43540

Some point flags are cleared incorrectly for non-digital objects. This occurs when the objects reported in a message have different flags. This fault is present in releases from 1101155-E to 1101155-K.

FW#13 43555

DNP3 Master and Slave freeze if DCB is configured but Multiserial card is fitted.

FW#18 43517

Statistics points were marked as reset until changed. For example, the BAD SCANS point would not have its reset flag cleared until a bad scan was recorded. Statistics points should always be valid.

FW#27 39638

Prevent a normal or custom poll request being sent while awaiting the response to a control request. Allowing this caused the control response to be discarded and an “Unexpected sequence number” error to be reported.

FW#118 28649

Use Raise/Lower pulse widths supplied by SALL calculations in preference to configured values.

FW#218 -

Configurations containing backup channels with station addresses of 10 or greater failed to start due to the hexadecimal station address being parsed as a decimal value.

FW#254 43900 FW#267

Delay measurement timing was incorrect on COM2 and Multiserial cards.

FW#255 -

Improve handling of RS485 two-wire connections to IEDs with fast turnaround time.

DNP3 Slave:

FW#13 43555

DNP3 Master and Slave freeze if DCB is configured but Multiserial card is fitted.

FW#14 43573

Application confirms with incorrect sequence number sent occasionally due to code re-entrancy fault.

FW#26 38731

Diagnostics for Analog Inputs always assumed integer values. This meant that floating-point values were not displayed correctly.


Page 12 of 19


Change

Incident # Description

Request #

FW#67 40321

Removed hard-coded limit of 512 events per scan reply.

FW#69 40588

Correct fault where the events present indication (requesting a further scan) was set in responses containing all available events.

Harris 5000/5500/6000 Slave:

FW#101 43081

Spurious COS events were reported when a database point transition count passed beyond 16-bits resolution.

IEC 60870-5-101 Slave:

FW#45 43534

Correct failure of setpoint commands to enforce the select-execute timeout.

FW#53 42633

Correct failure to reject reselection of select-execute commands.

FW$54 42632

Correct failure to reject select-execute commands with unmatched qualifiers.

FW#212 43808

Duplicate events with incorrect timestamps sometimes generated for points sourced from ADI cards.

Modbus Master:

FW#90 41247

Modified prioritisation of messages so that controls are scheduled before reads when communications are restored after an outage.

Optonet:

FW#152 43081

Correct handling of 16-bit rollover of Optonet digital point transition counters.

TOOL:

FW#20 43486

Download of zero-byte files fails for non-system files. (System files have extensions .Z, .DLL, .ELF, .ISA, .CFG, .C50, .BN1, .BN2 and .BN3.)

FW#24 43331

Correct faults in paging of DNP3 Master logical RTU data.

FW#218 -

Various TOOL screens displayed (hexadecimal) DNP3 station addresses as decimal values.

WISP+ Master:

FW#117 43635

Archive date was ignored when DIG_SOE messages were processed. This has been changed so that the archive date is combined with the DIG_SOE time stamp to create the event time stamp.

FW#237 42590

If all bits in a byte were not being scanned, SOE timestamps could be reported to the wrong index.

WISP+ Slave:

FW#151 43636 FW#224 43689

After RTU startup, initial events were sometimes reported incorrectly or lost.

FW#235 42657

SGL events were not reported to archive until first scan after RTU startup.

Table 5: Change Requests resolved in 1101155-L

3.4 Deleted functionality Installation from floppy disk media is no longer supported as of version 1101155-F.

4. Known Problems and Limitations At the time of release, there are no priority 1 defects outstanding. However, the following problems and limitations are known to exist with the 1101155-L RTU Software. 

Unsolicited messages will never be sent on DNP3 Slave backup channels.



Corruption of the flash memory may occur if the flash memory is completely filled.







In DNP Master, class 0 scans that transmit flag changes may cause spurious events in Harris Slave. SALLHLSI fails when the same fixed tokens terminate multiple packet formats, e.g. ASCII text lines terminated CR/LF. Conitel Master TOOL and RTV screens do not show communications traffic when operating in eavesdrop mode.


Page 13 of 19


















In the IEC 60870-5-101 Slave, each feedback object should only be associated with a single control object. If the same feedback object is configured for multiple controls, the behaviour will be unpredictable. Abnormal conditions at the RTU such as device reset will result in reporting of anomalous accumulator values; these are however flagged with appropriate error indications as permitted by protocols, for correct processing by a Master Station. If an RTU50 has TCP/IP configured, but no Dual Ethernet Board (DEB) is installed, the RTU will fail to boot. For correct operation of the 12 Channel Serial card with 486-based CPU boards, 1037452-B or higher must be programmed into the Altera device fitted to socket U14 on the 12 Channel Serial card. This corresponds to ECO 0303415/2. The RTU Software may not load configuration files that have additional whitespace (spaces, tabs or CR/LF characters) after the normal content of each line. If editing configuration files by hand, you must ensure that a single CR/LF pair, placed directly after the last non-whitespace character on the line, terminates each line. Under some circumstances, DNP3 Slave fails to correctly report event buffer overflows. It is recommended that the user configure the event buffer size to be sufficiently large to prevent the occurrence of buffer overflows (SIR 41432) The RTU Modbus Master implementation supports a maximum of 160 scan groups (SIR 41161). The C2025 Conitel Slave now handles calculation of the Remote Status Word’s Accumulator Bad bits internally. It is recommended that no RTU database points be mapped to these bits by configuration (SIR 40873).

5. Installation/Upgrade Instructions The RTU Software and Utilities must be installed onto an engineer’s workstation PC from the release CDROM. The release CDROM provides a graphical installation wizard. If you have an installation of an RTU Software version prior to 1101155-F, you should manually backup and remove it before installing 1101155-L. The 1101155-L installer will automatically detect and upgrade versions from 1101155-F onwards. In accordance with Microsoft guidelines, most files are installed under the C:\Program Files directory by default. Before installing, please read the RTU Configurator release note for instructions on how to carry an existing configuration database forward to the new version of the Configurator. After installing the RTU Software and Utilities onto the engineer’s workstation, one of the RTU diagnostic utilities, TOOL32 or RTV (Remote Terminal Viewer), can be used to download the RTU Software to the RTU flash memory.

Important Note: If upgrading from an earlier RTU Software version that provided the graphical installer, you must follow the procedures outlined in the RTU Configurator Release Note to preserve your existing configuration database. R unning the ins taller without firs t following that procedure will res ult in all config uration data being lost. The RTU Configurator Release Note is supplied in the documents directory of the release disk.

5.1 Installing from CDROM 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


Page 14 of 19


instructions to select the installation directory and to choose the components that you wish to install. Accepting the default installation path is strongly recomm ended. Depending on the components selected, a number of desktop shortcuts will be created. These include sample shortcuts for running the RTU diagnostic utilities, TOOL32 and RTV. The user will need to modify the shortcuts to TOOL32 in order to select an appropriate serial port or IP address. RTV permits these selections to be made interactively. 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. 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.

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 users, this may be done using the Control Panel -> System -> Environment dialog. Windows 95, 98 and Millennium Edition users will need to manually edit the C:\autoexec.bat file. If any old settings are not removed, TOOL32 and the RTU Configurator may not operate correctly.

5.2 Loading the software onto an RTU The RTU Software is comprised of two files: 1101155L.Z, the base software file providing the core RTU Software functionality, and 1101155L.DLL, a library of loadable modules providing various communications protocols. The use of loadable modules allows the RTU Software to conserve valuable memory capacity by only loading those protocols that are actually used in a particular configuration. Both of these files must be present in the RTU flash memory (with the same filename except for filename extension) in order to boot the RTU successfully. At boot time the RTU Software performs a series of checks in order to guarantee that the .Z and .DLL files are a correctly matched pair and will refuse to load if they are not.

Important note: The .DLL files from the previous releases are not compatible with the current release. If upgrading from a previous release, both the .Z and .DLL files must be replaced with the new versions.

To load the RTU Software into the flash memory of an RTU, it is necessary to use one of the RTU diagnostic programs, RTV (Remote Terminal Viewer) or TOOL32, as described in the following sections. For further information on RTU configuration and operation, refer to the documents listed in Section 7. 5.2.1 Loading software using RTV

RTV is the new, graphical RTU diagnostic program, first shipped with the 1101155-K release. RTV provides similar functionality to the old diagnostic program, TOOL32, with a modern, mouse-driven user interface. RTV can be launched using either the desktop icon or the Start Menu entry created by the installation program. Once RTV has started, the user will be presented with the “New Connection” dialog box. From here the user can select the communications medium (TCP/IP, serial, or DNP3 File Transfer Agent) and can enter the appropriate settings for the selected communications medium. If desired, the user can enter a name with which to save the settings for future use. Clicking on the “OK” button connects RTV to the RTU using the user’s settings. Once RTV has connected to the RTU, click on “File System” in the left-hand pane and then click on the “Download” button at the bottom of the “File System” window in the right-hand pane. This will open a file selection dialog box from which the RTU Software files can be selected. By default, these files are installed in the “C:\” directory. Click the “Open” button in the file selection dialog box to


Page 15 of 19


complete the selection. RTV will ask the user to enter the name under which each file is to be stored in the RTU’s flash memory. To use the current names for all files, check the “Keep source file names” box, before clicking “OK” to begin the download. To make the new RTU Software files active when the download has finished, select the 1101155L.Z file from either the “Software 1” or “Software 2” drop down list at the top of the File System window and click on the radio-button next to the drop down list. Save the selection by clicking on the “Commit” button and then restart the RTU by using the “File | Reset” menu item. 5.2.2 Loading software using TOOL32

TOOL32 is the original console mode RTU diagnostic program, as shipped with all previous releases of the RTU Software and Utilities. TOOL32 can be started using one of the desktop shortcuts created by the installation program or by opening a Command Prompt window and entering one of the following commands: (for serial communication)

tool32 –s

(for TCP/IP communication)

tool32 –t Tool32 –d

(for DNP3 File Transfer Agent)

In the first version of the command, is the number of the PC serial port to be used for the connection (1 to 8 inclusive) and is the bit rate to be used for the connection (usually 19200). In the second version of the command, is a TCP/IP hostname (e.g. rtu1.foxboro.com.au) or address (e.g. 192.168.1.1) and is the TCP/IP port configured on the RTU for TOOL communications (usually 20476). Note that TCP/IP communications will only be available if the RTU is already running with a valid TCP/IP configuration and software. The third version of the command communicates with an RTU via the DNP3 File Transfer Agent (FTA) of a Foxboro Master Station. The parameter is the TCP/IP hostname or address of the Master Station, is the TCP/IP port of the Master Station FTA (usually 45454) and is the string configured on the Master Station to identify the target RTU. If TOOL32 is not found, check that your PATH environment variable includes the “Utilities” subdirectory of the installation path by running the “echo %PATH%” command at the Command Prompt. If TOOL32 is found but fails to connect to the RTU, check your connection to the RTU. If using TCP/IP you can do this by using the “ping” command with the name or IP address of the RTU at the Command Prompt. For example: ping rtu1.foxboro.com.au

or

ping 192.168.1.1

Important note for W indows NT/2000 us ers : Windows NT and Windows 2000 provide two different Command Prompts: command.com and cmd.exe. You should ensure that you are using TOOL32 may not function correctly with the command.com Command Prompt.

cmd.exe.

After TOOL32 connects to the RTU, press function key F4 (File Services). This will display a list of the files that are presently stored in the RTU flash memory. Now press function key F2 (Download). Enter the full path of the 1101155L.Z file (e.g. C:\1101155L.Z), press tab, enter the name under which the file is to be stored in the RTU flash memory (usually 1101155L.Z), and press function key F7 to begin downloading the file to the RTU. Repeat this process to download the 1101155L.DLL file to the RTU, ensuring that it is stored on the RTU with the same base filename that you gave to the 1101155L.Z file. If you do not download the 1101155L.DLL file the RTU will not boot. When both files have finished downloading, press function key F1 to return to the main menu and then press function key F5 (File Services) to enter the file selection screen. Use the down arrow key to highlight either “F/Ware 1” or “F/Ware 2” and press function key F5 (Show Files) to list the available


Page 16 of 19


files. Use the up and down arrow keys to highlight 1101155L.Z and press function key F2 (Select File) to select it and then press function key F6 (Make Active). Repeat this process to select a suitable configuration file for either “Config 1” or “Config 2” then press function F7 (Save Next) to commit the changes to the flash memory. After re-checking your selections press function key F3 (Restart RTU) to reboot the RTU with the 1101155-L RTU Software.

6. Validation and Verification Statement A variety of verification and validation activities have been conducted on the 1101155-L RTU Software and Utilities prior to their release. The assurance strategy for this release consisted of five parts: 1. Change Design and Code Reviews The design and source code of all baseline changes was documented and reviewed before acceptance into system integration. Reviews were performed by peer developers and by independent Software Verification Engineers. 2. Incident Retest For each incident addressed in this release, test cases were prepared and documented by an independent team to ensure that the incident was fixed satisfactorily and that there were no unintended side-effects of the modification. 3. Manual Subsystem Tests Rigorous test specifications were prepared for new or substantially changed subsystems based on software requirements, software design and (where applicable) official protocol specifications. This does not include subsystems that are unchanged since release in other RTU50 Protected Mode part numbers. The subsystems tested were: 

DNP3 Master



DNP3 Slave



TCP/IP

4. Automated Subsystem Regression Test Previously developed automated subsystem tests were repeated, where available. These included test suites for: 

Intrinsic Database Functions



Calculations (SALL)



OptoNet

The automatic nature of this testing provides a high degree of accuracy and repeatability, which in turn provides a significant degree of confidence in the parts of these subsystems for which automated tests have been produced to date. 5. System Integration Test Tests were performed to ensure correct subsystem operation in an integrated system configuration. All integration testing was conducted on frozen release candidate builds prepared th st on 14 August 2003 and 31 August 2003. Two types of integration test were performed as follows: The RTU Software was tested in a variety of configurations. 

An RTU containing I/O cards, IDF calculations and SALL calculations receiving controls and sending point values and events across a communications link to a Master RTU or simulated


Page 17 of 19


Master device. Protocols tested in this scenario were C2025 Conitel, C300 Conitel, DNP3, IEC 60870-5-101, Modbus and WISP+. 

An RTU containing I/O cards, IDF calculations and SALL calculations sharing points across Optonet with a second RTU that receives controls and sends events across a communications link to a Master RTU or simulated Master Device. Protocols tested in this scenario were C2025 Conitel, C300 Conitel, DNP3, IEC 60870-5-101, and Modbus.

The RTU Software was also exercised in a configuration where point values, events and controls were passed along a chain of Master/Slave protocol communication links. This testing demonstrated correct interaction between the different protocols. This release has used a risk-based approach to direct assurance effort where it is needed most. In particular, detailed tests were not performed for subsystems with minimal or no changes and/or substantial field confidence. Some outstanding problems identified by the testing performed are detailed in Section 4 of this release note. However, there may be defects that arise in project usage patterns that have not been detected.

7. Related Documentation For further information on RTU50 and SCD5200 installation, configuration, programming and diagnostics, please refer to the following documents. These documents are available on the RTU50 / RTU10 / CLS / SCD5200 Documentation CDROM (part number: 2005654). Part no.

Title

Version

2005064

RTU50 Conitel Communication Protocol

1.4

2005141

RTU50 Hardware Specification

1.8

2005143

RTU50 Hardware and Programming Information

1.7

2005154

RTU50 C2025 Remote Station Conitel Protocol

1.1

2005157

Conitel (C300 emulation) Communications Protocol Technical Manual

1.2

2005167

RTU50 SALL Serial Communications Interface (HLSI)

1.4

2005176

Harris 5000/5500/6000 Communications Protocol Specification

1.3

2005201

V.28 Dual Communications Board User Manual

1.1

2005543

RTU50 Conitel Master Communications Protocol User Manual

1.2

2005550

RTU50 Configuration User Manual

1.1

2005551

RTU50 Programming User Manual: State and Logic Language Reference (SALL)

1.5

2005552

RTU50 Diagnostic User Manual

1.2

2005554

RTU50 DNP3 Slave User Manual

2.0

2005555

RTU50 DNP3 Master User Manual

2.0

2005567

RTU50 Modbus Slave Protocol User Manual

1.1

2005573

RTU50 DNP3 Slave Device Profile

1.5

2005574

RTU50 DNP3 Master Device Profile

1.6

2005596

RTU50 Event Logger User Manual

1.1

2005601

RTU50 AC Transducer Card User Manual

1.1

2005602

RTU50 Modbus Master User Manual

2.0


Page 18 of 19


Part no.

Title

Version

2005604

RTU50 Intrinsic Database Functions User Manual

2.0

2005606

RTU50 IEC 60870-5-103 Master Protocol User Document

1.1

2005608

RTU50 IEC 60870-5-101 Slave User Document

1.7

2005609

RTU50 WISP+ Protocol User Document

1.1

2005653

RTU50 TCP/IP Software User Manual

2.0

2005660

RTU50 OptoNet Software User Manual

2.0

2005662

SCD5200 Hardware User Manual

1.1

2005663

System Configurator User Manual

1.0

2005671

IEC 61131-3 Programming and Runtime Environment User Manual

1.1

1101168

Watcom C/C++ Compiler Release Note

1.1

35808-114-03

SALL Floating Point User Manual

1.1


Page 19 of 19

RTU-2

Recommend Documents