cfgpro08.pdf

7/25/2019 cfgpro08.pdf

1/64

Config Pro Configuration System User's Guide Appendix C: Memory Models and Parts Information C-1

Appendix C: Memory Models andParts Information

Overview

This appendix contains information about D20M, D20M+ and D20M++ processor

boards, including PROM types and sizes, part numbers, and other differentiating

features.


2/64

C-2 Appendix C: Memory Models and Parts Information Config Pro Configuration System User's Guide

D20 M and D20 M+ Memory Devices

The following table lists the Harris part numbers for the memory devices that can be

used in D20 M and D20 M+ RTUs.

Memory

Bank Size

Memory IC

Size EPROM NVRAM RAM

32K (8K x 8) N/A Harris Part

#160-0025

N/A

128K (32K x 8) Harris Part

#160-0022

Harris Part

#160-0028

Harris Part

#160-0023


#160-0029

N/A Harris Part

#160-0023


#160-0032

Harris Part

#160-0035

Harris Part

#160-0030

1 M (256K x 8) Harris Part

#160-0033

N/A N/A

2 M (512K x 8) N/A N/A Harris Part#160-0034

NOTES:

28-pin: 160-0022, 160-0025, 160-0028, 160-0029

32-pin: 160-0030, 160-0032, 160-0033, 160-0034, 160-0035


3/64


Harris D20M Processor Board Types

The following table lists the part numbers for the D20M style processor boards.

Note that D20M processor boards are no longer produced, and this information is for

reference only. Do not quote D20M part numbers for new orders.

Part

Number

EPROM

(Bank B)

NVRAM

(Bank C)

RAM

(Bank D)

D20 M

Type

Comments

526-0001 128K 32K 128K 1 N/A

526-0001S 512K 32K 128K S1 N/A

526-0002 128K 32K 128K 2 N/A

526-0003 128K 128K 128K 3 N/A

526-0006 256K 32K 128K 4 N/A

526-0006A 256K 32K 128K 4A N/A

526-0007 256K 128K 128K 5 N/A

526-0008 256K 32K 512K 6 N/A

526-0010 256K 128K 128K 8 N/A

526-0011 256K 128K 512K 9 TCXO, PG&E only

526-0011A 256K 128K 512K 9A N/A

526-0012 256K 32K 128K 10 VME

526-0012A 256K 32K 128K 10A VME

526-0013 256K 128K 512K 11 PG&E only

526-0014 256K 128K 512K 12 N/A

526-0014A 256K 128K 512K 12A N/A

526-0014B 512K 128K 512K 12B N/A

526-0014C 1M 128K 512K 12C N/A

526-0015 512K 128K 512K 13 VME

526-0015A 512K 128K 512K 13A VME

526-0015B 1M 128K 512K 13B VME

526-0016 256K 128K 512K 14 TCXO

526-0017 512K 128K 512K 15 N/A

526-0018 256K 32K 128K 16 TCXO

526-0019 512K 128K 512K 17 TCXO

526-0020 512K 128K 128K 18 N/A

526-0021 512K 32K 128K 19 N/A

XXX-0001 512K 64K 512K N/A BOW Software


4/64


Harris D20M+ Processor Board Types

The following table lists the part numbers for the D20M+ style processor boards.

Part

Number

EPROM

(Bank B)

NVRAM

(Bank C)

RAM

(Bank D)

Jumpers

24,25

Pal-Type

U20, U38 Comments

526-0101 512K 128K 128K 1-2, 1-2 A, A N/A

526-0102 512K 128K 128K 1-2, 1-2 A, A TCXO

526-0103 512K 128K 128K 1-2, 1-2 A, A VME

526-0104 512K 128K 128K 1-2, 1-2 A, A VME TCXO

526-0105 512K 128K 512K 1-2, 1-2 A, B N/A

526-0106 512K 128K 512K 1-2, 1-2 A, B TCXO

526-0107 512K 128K 512K 1-2, 1-2 A, B VME MATH

526-0108 512K 128K 512K 1-2, 1-2 A, B MATH

526-0109 512K 128K 512K 1-2, 1-2 A, B VME

526-0110 512K 128K 512K 1-2, 1-2 A, B VME TCXO

526-0111 512K 128K 32K 2-3, 1-2 A, C N/A

526-0112 512K 128K 32K 2-3, 1-2 A, C VME TCXO

526-0113 512K 128K 32K 2-3, 1-2 A, C TCXO

526-0114 512K 128K 32K 2-3, 1-2 A, C MATH

526-0115 512K 128K 32K 2-3, 1-2 A, C VME

526-0116 512K 128K 32K 2-3, 1-2 A, C VME MATH


5/64


Harris D20M++ Processor Board Types

The following table lists the part numbers for the D20M++ style processor boards.

Part

Number

EPROM

(Bank B)

NVRAM

(Bank C)

RAM

(Bank D)

Jumpers

Z4, Z5 Comments

526-1000 512K 128K 512K 1-2, 1-2 VME TXCO

526-1000A 512K 128K 512K 1-2, 1-2 VME TXCO

526-1001 512K 128K 512K 1-2, 1-2 N/A

526-1001A 512K 128K 512K 1-2, 1-2 N/A

526-1002 512K 512K 512K 1-2, 1-2 N/A

526-1002A 512K 512K 512K 1-2, 1-2 N/A

526-1003 512K 512K 512K 1-2, 1-2 VME TXCO

526-1003A 512K 512K 512K 1-2, 1-2 VME TXCO

526-1004 512K 128K 512K 1-2, 1-2 TCXO

526-1004A 512K 128K 512K 1-2, 1-2 TCXO

526-1005 512K 512K 512K 1-2, 1-2 TCXO

526-1005A 512K 512K 512K 1-2, 1-2 TCXO

526-1006 1M 512K 512K 1-2, 1-2 N/A

526-1006A 1M 512K 512K 1-2, 1-2 N/A

526-1008 1M 128K 512K 1-2, 1-2 N/A

526-1008A 1M 128K 512K 1-2, 1-2 N/A

526-1009 512K 128K 1M 1-2,1-2 N/A

526-1009A 512K 128K 1M 1-2,1-2 N/A

526-1010 1M 512K 512K 1-2,1-2 TCXO

526-1010A 1M 512K 512K 1-2,1-2 TCXO

526-1011 1M 128K 512K 1-2,1-2 TCXO

526-1011A 1M 128K 512K 1-2,1-2 TCXO


6/64


Harris D10M++ Processor Board Types

The D10M++ processor boards are for use with compact, low point count RTUs. The

following table lists the part numbers for the D10M++ style processor boards.

Part

Number

EPROM

(Bank B)

NVRAM

(Bank C)

RAM

(Bank D)

Jumpers

Z4, Z5 Comments

526-1012 512K 128K 512K 1-2, 1-2

526-1012A 512K 128K 512K 1-2, 1-2

Harris CPM Board Types

The following table lists the part numbers for the Communication Processor Module

(CPM) boards.

Part

Number

EPROM

(Bank B)

NVRAM

(Bank C)

RAM

(Bank D) Comments

514-0001 128K 8K 32K Bell 202 Modem

514-0002 256K 32K 128K Bell 202 Modem

514-0003 128K 8K 32K CCITT V.23 Modem

514-0004 256K 32K 128K CCITT V.23 Modem

514-0005 512K 32K 128K Bell 202 Modem

514-0006 512K 32K 128K CCITT V.23 Modem

514-0101 256K 32K 128K CPM2

514-1000 512K 32K 128K CPM3

514-1001 512K 128K 128K CPM3


7/64

Config Pro Configuration System User's Guide Appendix D: Error and Warning Messages D-1

Appendix D: Error and WarningMessages

Overview

This appendix contains lists of error and warning messages that you may encounter

during the following operations:

Creating a new device

Generating a downloadable configuration file

Converting an existing configuration file

Upgrading a device

Exporting application configuration tables

The messages are arranged in alphabetical order , and take the following format:

Message (what you see on the screen)

Message type (error or warning)

Error messages

Warning messages

Cause of error or warning (an explanation of the most probable cause of the error)

Action to take (steps that you can take to rectify the error or warning)


8/64

D-2 Appendix D: Error and Warning Messages Config Pro Configuration System User's Guide

Error and Warning Messages

For any error in this section that refers you to this page as the Action to Take,

follow these steps:

1. Exit out of Config Pro, and out of the Windows environment.

2. Restart Windows and Config Pro.

3. Try the function or step that caused the error again.

4. If the same error message appears, please contact the Harris Controls Customer

Service Department at (403) 243-3335.

file not found.

Cause of Error: The specified file could not be found. This error is normally generated

if a user-provided file is missing.

For the ImportAppl icat ion function this is only a warning message. It

can be disregarded if there is no need to import the file.

Action to Take: If the specified file is missing, create it or place it in the appropriate

place.

bytes left over from table conversion.

Cause of Error: The record size in the configuration file is different than the record sizein Config Pro's table structure definitions. This normally means that

you have specified the wrong version of the associated application in

the device's firmware.%s.CSV file not found.

Action to Take: Select a device with an appropriate firmware type for the conversion

operation, or change the firmware of the device to include the

appropriate application version.

Application (Processor ) not found in

device configuration (has been disabled).

Cause of Warning: Although the specified application is defined in the current device's

firmware, it was not found in the configuration file being converted.

Config Prohas disabled the application.

Action to Take: None.


9/64


Application (processor ) not present

in upgraded device; data has been lost.

Cause of Warning: An application that was present in the original device was not found in

the upgraded device. Config Prohas deleted the information

associated with that application.


Application of processor in the

enabled application list database has been removed.

Cause of Warning: An application that was present in the original device was not found in

the upgraded device. Config Prohas removed the information

associated with that application.


Application Ver (processor ) was added to the upgraded device.

Cause of Warning: An application that is present in the upgraded device was not present in

the original device. The data for that application has been set to the

appropriate default values.

Action to Take: Edit the tables associated with the application appropriately.

Could not access file.

Cause of Error: Config Prowas unable to access the specified file.

Action to Take: See page D-2.

Could not access function in file.

Cause of Error: Config Prowas unable to find the specified function in the specifiedfile.



10/64


Could not access the board# record from the processor

list database.

Cause of Error: Config Prowas unable to access the processor database file associated

with the specified processor record.


Could not access the device in the device list database.

Cause of Error: Config Prowas unable to access the device's database file associated

with the specified device.


Could not add Ver (processor ) record to the enabled application list database.

Cause of Error: Config Prowas unable to add a specified application with its version

record to the application database file.

Action to Take: Free up some hard disk space and try the operation again. If the same

error message appears, see page D-2.

Could not add record to the enabled table list database.

Cause of Error: Config Prowas unable to add a specified table record to the table list

database file.



Could not add default raw data record(s) to the table.

Cause of Error: Config Prowas unable to add a default binary data record or records to

the specified table.




11/64


Could not add raw data record to the raw data table.

Cause of Error: Config Prowas unable to add a binary data record to the specified

binary data table.

Action to Take: Free up some hard disk space and try the operation again. If the sameerror message appears, see page D-2.

Could not add record to file.

Cause of Error: Config Prowas unable to add a record to the specified file.



Could not add record to table.

Cause of Error: Config Prowas unable to add a record to the specified table.



Could not add record to the peripheral list database.

Cause of Error: Config Prowas unable to add a record to the peripheral database file.



Could not add the appropriate number of records to the binary data file.

Cause of Error: Config Prowas unable to add records to the binary data file.



Could not add the appropriate number of records to the embedded table.

Cause of Error: Config Prowas unable to add records to the database file.




12/64


Could not add the board# record to the processor list

database.

Cause of Error: Config Prowas unable to add the specified processor record to the

processor database file.



Could not add the new raw data file to the enabled table list database.

Cause of Error: Config Procould not add a reference to the new data table to the table

list database.



Could not add the VME board record to the VME board database.

Cause of Error: Config Prowas unable to add a VME board record to the VME

database file.



Could not allocate memory.

Cause of Error: Config Prowas unable to assign enough system memory to complete

the requested operation.

Action to Take: Try closing a currently running application (other than Config Pro) and

then try the operation again. If the same error message appears, see

page D-2.

Could not change the name of the D20 Board configuaration file.

Cause of Error: Config Prowas unable to rename the D.20 board configuration file.



13/64


Could not change the processor number from to

in the database.

Cause of Error: Config Prowas unable to change the processor number in the specified

database file.


Could not close file.

Cause of Error: Config Prowas unable to close the specified file.


Could not copy record to the peripheral list database.

Cause of Error: Config Prowas unable to copy a record to the peripheral database file.



Could not copy temporary copy of version of table .

Cause of Error: Config Prowas unable to copy a table to the specified table file.



Could not copy the application to the application

.

Cause of Error: Config Prowas unable to copy an internal application database file.




14/64


Could not copy the VME board record to the VME board database.

Cause of Error: Config Prowas unable to copy a record to the VME database file.



Could not create file.

Cause of Error: Config Prowas unable to create the specified database or binary data

file.



Could not create list database.

Cause of Error: Config Prowas unable to create the specified database file.



Could not create raw data table.

Cause of Error: Config Prowas unable to create the specified data table file.



Could not create table file.




Could not create database file(s).

Cause of Error: Config Prowas unable to create an internal database file or files.




15/64


Could not create default records in the file.

Cause of Error: Config Prowas unable to create a default record for the specified file.



Could not create path to database file.

Cause of Error: Config Prowas unable to create the sub-directory to hold the specified

database file.

Action to Take: Ensure that you have sufficient user rights to create directories under

the WESDATA directory. If the problem persists, see page D-2.

Could not create path to temporary copy of version of table.

Cause of Error: Config Prowas unable to create the sub-directory to hold the specified

table.

Action to Take: Ensure that you have sufficient user rights to create directories under

the WESDATA directory. If the problem persists, see page D-2.

Could not create temporary copy of version of the table .




Could not create the table and add the default number of

records.

Cause of Error: Config Prowas unable to create an internal specified table databasefile, and/or add default records to that table.




16/64


Could not delete application (processor ) in the enabled application list database.

Cause of Error: Config Prowas unable to delete the specified application record from

the application database file.


Could not delete record from table.

Cause of Error: Config Prowas unable to delete a record from the specified table.


Could not delete record(s) from file.

Cause of Error: Config Prowas unable to delete a record or records from the specified

database file.


Could not delete the old raw data file from the enabled table list database.

Cause of Error: Config Prowas unable to delete a binary data record from the table list

database file.


Could not delete the processor list database.

Cause of Error: Config Prowas unable to delete the current processor database file.


Could not determine length of file.

Cause of Error: Config Prowas unable to access the specified binary data file size

information.


Could not determine number of applications in device.


17/64


Cause of Error: Config Prowas unable to access the device's table list database file.


Could not determine number of matching records in virtual point map table.

Cause of Error: Config Prowas unable to access the virtual point mapping table

database file.


Could not determine number of records in file.

Cause of Error: Config Prowas unable to access the specified database file information.


Could not determine number of records in file (DPA instance

table).

Cause of Error: Config Prowas unable to access the system point database's DPA list

database table.


Could not determine number of tables in device .

Cause of Error: Config Prowas unable to access the device's table list database file.


Could not determine the size of the binary data records.

Cause of Error: Config Prowas unable to access the binary data file information.



18/64


Could not disable application .

Cause of Error: Config Prowas unable to access the device's application list database

file.


Could not disable table .

Cause of Error: Config Prowas unable to access the application's table list database

file.


Could not disable the processor in the processor list

database.

Cause of Error: Config Prowas unable to disable the specified processor in the

currently selected device.


Could not enable the processor in the processor list

database.

Cause of Error: Config Prowas unable to enable the specified processor in thecurrently selected device.


Could not find version of table ; no action taken.

Cause of Warning: A table that is present in the upgraded device was not found in the

original device. Config Prohas ignored the information associated

with that table.



19/64


Could not generate file.

Cause of Error: Config Prowas unable to open or create the specified device

configuration file.

Action to Take: Free up some hard disk space and try the operation again. If the sameerror message appears, see page D-2.

Could not get board configuration information.

Cause of Error: Config Prowas unable to access the specified peripheral information.


Could not get table structure information.

Cause of Error: Config Prowas unable to access the structure definition file for the

specified table.


Could not get application list information.

Cause of Error: Config Prowas unable to access the device's application list database

file.


Could not get board information.

Cause of Error: Config Prowas unable to access the peripheral list database file.


Could not get default raw data record for the table structure.

Cause of Error: Config Prowas unable to get a default record for the specified table.


Could not get info on DCA from the system point

database files.


20/64


Cause of Error: Config Prowas unable to access the system point database file

information.


Could not get info on version of application .

Cause of Error: Config Prowas unable to access the DCA instance information.


Could not get information on table of version of

application .

Cause of Error: Config Prowas unable to access the specified application database fileinformation.


Could not get number of records in table.

Cause of Error: Config Prowas unable to access the currently selected table data file.


Could not get number of records in table .

Cause of Error: Config Prowas unable to access the specified table data file.


Could not get peripheral configuration table structure ( D20_CNFG ).


D20_CNFG table.


Could not get raw data record from the raw data table.

Cause of Error: Config Prowas unable to access the specified table data file.


21/64



Could not get table info for embedded table of table

.

Cause of Error: Config Prowas unable to access the structure definition data

associated with the embedded table.


Could not get table info for table .

Cause of Error: Config Prowas unable to access the structure definition associated

with the specified table.


Could not get table list for version of application .


file.


Could not get table structure for table of version

of application .


specified table.



22/64


Could not get table structure for version of table .


specified table.


Could not get table structure info.


currently selected table.


Could not get the table structure.


specified table.


Could not get the DCA position of the D.20 application.

Cause of Error: Config Prowas unable to access the WIN DCA list database file.


Could not get the DCA position in the WIN DCA list.

Cause of Error: Config Prowas unable to access the WIN DCA list database file.


Could not get the default raw data record.

Cause of Error: Config Prowas unable to get a default record for the currently selected

table.


Could not get the device's firmware information.


23/64


Cause of Error: Config Prowas unable to access the device's firmware definition files..


Could not get the device information.

Cause of Error: Config Prowas unable to access the device's database files.


Could not get the device serial ports.

Cause of Error: Config Prowas unable to access the device's database files.


Could not get the device subtype information.

Cause of Error: Config Prowas unable to access the part number information database

file.


Could not get the information of the application

(processor ).


specified application.


Could not get the information of the application version

(processor ).


specified application application version.


Could not get the number of records in the VME board database file.

Cause of Error: Config Prowas unable to access the VME database file.


24/64



Could not get the peripheral type.

Cause of Error: Config Prowas unable to access the peripheral list database file.


Could not get the pointer to the table structure.

Cause of Error: Config Prowas unable to access the specified table's data structure

information.


Could not get the source raw data record.

Cause of Error: Config Prowas unable to access the currently selected table data file.


Could not get the table list from the application definition subsystem.

Cause of Error: Config Prowas unable to get the list of tables associated with the

selected application..Action to Take: See page D-2.

Could not get the total records.

Cause of Error: Config Prowas unable to access the specified virtual point map

database file.



25/64


Could not load file.

Cause of Error: Config Prowas unable to load the specified DLL file.

Action to Take: All .DLL files are located in the \WESSYS\BIN directory. If you are

on a network, make sure that you have adequate access rights to thatdirectory, and then retry the operation. If the same error message

appears, see page D-2.

Could not load file, and could not complete application

upgrade; do not use device.

Cause of Error: Config Prowas unable to load the specified DLL file, and was unable

to upgrade the currently selected device.

Action to Take: All .DLL files are located in the \WESSYS\BIN directory. If you are

on a network, make sure that you have adequate access rights to that

directory, and then retry the operation. If the same error message

appears, see page D-2.

Could not obtain new virtual point number from file.

Cause of Error: Config Prowas unable to access the specified virtual point map

database file.


Could not obtain virtual system point number.

Cause of Error: Config Prowas unable to access a virtual point map database file..


Could not open file.

Cause of Error: Config Prowas unable to open the specified file.



26/64


Could not open file (version ).

Cause of Error: Config Prowas unable to specified file.


Could not open point map table (secondary index).

Cause of Error: Config Prowas unable to open the specified system point mapp

database file.


Could not open point map table (primary index).

Cause of Error: Config Prowas unable to open the specified system point map database

file.


Could not open file (DPA instance table).

Cause of Error: Config Prowas unable to open the specified DPA list database file.


Could not open database file(s).

Cause of Error: Config Prowas unable to open a database file or files.


Could not open peripheral configuration table ( D20_CNFG ).

Cause of Error: Config Prowas unable to open the peripheral configuration file.



27/64


Could not open system point database files.

Cause of Error: Config Prowas unable to access the system point database files.


Could not open table list for version of application

.

Cause of Error: Config Prowas unable to open the application's table list database file.


Could not open temporary copy of version of table .

Cause of Error: Config Prowas unable to open the specified data table file..



Could not open the configuration table.

Cause of Error: Config Prowas unable to open the specified data table file.


Could not open the raw data table.

Cause of Error: Config Prowas unable to open the specified data table file.


Could not open the application list database.

Cause of Error: Config Prowas unable to open the device's application list database

file.



28/64


Could not open the board configuration binary file.

Cause of Error: Config Prowas unable to open a peripheral board configuration file.


Could not open the DCA list database.

Cause of Error: Config Prowas unable to open the system point database's DCA list

database file.


Could not open the device list database.

Cause of Error: Config Prowas unable to open the project's device list database file.


Could not open the device note file.

Cause of Error: Config Prowas unable to open the device notes file.


Could not open the device virtual point mapping table.

Cause of Error: Config Prowas unable to open a virtual point map database file.


Could not open the firmware application cross reference database.

Cause of Error: Config Prowas unable to open the specified database file.



29/64


Could not open the peripheral list database.

Cause of Error: Config Prowas unable to open a peripheral list database file.


Could not open the processor list database file.

Cause of Error: Config Prowas unable to open the processor list database file.


Could not open the table list database.

Cause of Error: Config Prowas unable to open the table list database file associated

with the selected application.


Could not open the system VME board database file.

Cause of Error: Config Prowas unable to open the specified database file.


Could not open the VME list database file.

Cause of Error: Config Prowas unable to open a currently selected VME board

database file.


Could not open virtual point map table(s).

Cause of Error: Config Prowas unable to open one or more virtual point map database

files.



30/64


Could not read file.

Cause of Error: Config Prowas unable to access or read the specified file.


Could not read from file.

Cause of Error: Config Prowas unable to access or read from the specified file.


Could not read information from board configuration file.

Cause of Error: Config Prowas unable to access or read from the specified file.


Could not read table record.

Cause of Error: Config Prowas unable to access or read from the specified data table

file.


Could not retrieve table information.


file.


Could not retrieve table information.


file.



31/64


Could not save the description of the processor in the

processor list database.

Cause of Error: Config Prowas unable to access or write to the processor list database

file.


Could not set the pointer to the network configuration file.

Cause of Error: Config Prowas unable to access the D.20 application's network

configuration file information.


Could not set the enabled state of all the applications in the device .

Cause of Error: Config Prowas unable to enable all the applications in the specified

device.


Could not update record in file.

Cause of Error: Config Prowas unable to access or update a record in a specifieddatabase file.


Could not update system point field(s).

Cause of Error: Config Prowas unable to access or update the table's system point field

or fields.



32/64


Could not update the board configuration to the intermediate

binary file.

Cause of Error: Config Prowas unable to copy the D.20 peripheral board information

to the intermediate binary file maintained by the D.20 editor..



Could not update the database file.

Cause of Error: Config Prowas unable to access or write to the specified database file.


Could not update the board type information.



Could not update the enabled table list database.



Could not update the extended point type information to the DO virtual point

mapping table.



Could not update the number of counter inputs to the CT virtual point

mapping table.



Could not update the peripheral list database.


33/64




Could not update the record in the enabled application list.

Cause of Error: Config Prowas unable to access or write to a record in the specified

database file.


Could not update the redundant flag in the device list database.



Could not upgrade D.20 Application from version to

version .

Cause of Error: Config Prowas unable to upgrade the D.20 application to the new

version.


error message appears, see page D-2. Note that it is not currently

possible to upgrade from a newer version of the D.20 application to an

older version (i.e., you cannot upgrade from version 7.xx to 6.xx).

Could not write information to board configuration file.





34/64


Could not write table record.

Cause of Error: Config Prowas unable to write a table record to the table data file.



Could not write the flag to B003.INI file.

Cause of Error: Config Prowas unable to write the specified flag to the B003.INI data

file.



Could not write to file.

Cause of Error: Config Prowas unable to write to the specified file.



Extra records found in sub-table of upgraded table; these

records have been set to defaults.

Cause of Warning: Sub-table in the upgraded table has more recordsthan the original sub-table had. The extra records have been set to

default values.

Action to Take: Edit the upgraded table appropriately.

Field do(es) not have the same data or entry type; data has been

set to defaults.

Cause of Warning: The specified field is defined differently in the upgraded table than it is

in the original table. Config Prowas unable to copy the data from theoriginal to the upgraded version, and has set the data in the specified

field to the default value.



35/64


Field was added to sub-table ; data has been

set to defaults.

Cause of Warning: The specified field was not present in the original sub-table. The new

field has been set to the appropriate default data.


Field was added to the upgraded table; data has been set to

defaults.

Cause of Warning: The specified field was not present in the original table. The new field

has been set to the appropriate default data.


Field was not found in the upgraded table; data has been lost.

Cause of Warning: The specified field, which was present in the original table, was not

found in the upgraded table. Config Prowas unable to copy the data

from the original to the upgraded version.


Internal database error in , at line .

Cause of Error: Config Prowas unable to access a database file at the specified line in

the specified source file.


Memory allocation error.

Cause of Error: Config Prowas unable to assign enough system memory to complete

the requested operation.

Action to Take: Try closing a currently running application (other than Config Pro) and

then try the operation again. If the same error message appears, see

page D-2.

NVRAM space required ( Bytes) is larger than available

NVRAM area ( Bytes).


36/64


Cause of Error: The downloadable configuration file is larger than the NVRAM

available to the current processor board.

Action to Take: Upgrade the firmware used by the current device to include a processor

board that has more NVRAM space.

New database file () created.

Cause of Warning: The database file containing the table information was not present and

had to be created. This normally means that you haven't edited the

table.

Action to Take: Go to the appropriate table window to verify that the table's contents

are correct before proceeding.

Not enough records found in sub-table of upgraded table;data has been lost.

Cause of Warning: Sub-table in the upgraded table has fewer records

than the original sub-table had. Any records following those that have

been copied are lost.


Processor in the processor list database has been

disabled.

Cause of Warning: Thespecified processor board that was present in the original device

was not found in the upgraded device. Config Prohas disabled the

information associated with that processor board.



37/64


Processor not found in device configuration.

Cause of Error: Although the specified processor board is defined in the current device,

it was not found in the configuration file being converted.

Action to Take: Disable the processor board of the selecteddevice, and try the operation again. If the same error message appears,

see page D-2.

Record: , Field: , bytes left over from table

conversion.

Cause of Error: The table's record size in the configuration file is different than the

record size in the Config Protable structure definitions. This normally

means that you have specified the wrong version of the application in

the device's firmware.

Action to Take: Select a device with an appropriate firmware type for the conversion

operation, or change the firmware of the device to include the

appropriate application version.

Record: , Field: , Computed value of is above

upper limit of .

Cause of Error: The value in the specified field is greater than the maximum allowable

value for the field.Action to Take: Go back to the appropriate table window and type in a value that is

lower than or equal to the .

Record: , Field: , Computed value of is above

the upper limit of ; value now set to .

Cause of Warning: The conversion process determined that the value for the specified field

is outside of the allowable range. Config Prohas changed the value to

.

Action to Take: Go to the associated table window to verify that the field was set to an

appropriate value.


38/64


Record: , Field: , Computed value of is below

lower limit of .

Cause of Error: The value in the specified field is less than the minimum allowable value

for the field.

Action to Take: Go back to the appropriate table window and type in a value that is

greater than or equal to the .

Record: , Field: , Computed value of is below

the lower limit of ; value now set to .



.


appropriate value.

Record: , Field: , Computed value of is not a

multiple of .

Cause of Error: The value in the specified field is not a divisible by .


divisible by .

Record: , Field: , Computed value of is not a

multiple of ; value is now set to .

Cause of Warning: The conversion process determined that the value for specified field is

not a multiple of . Config Prohas changed the value

to .


appropriate value.


39/64


Record: , Field: , Could not determine end of system

point range.

Cause of Error: Config Prowas unable to access the currently selected device's virtual

map database file(s).


Record: , Field: , Could not get application

information.

Cause of Error: Config Prowas unable to access the device's database file information.


Record: , Field: , Could not get application versioninformation.

Cause of Error: Config Prowas unable to access the device's database file information.


Record: , Field: , Could not get size of

table.

Cause of Error: Config Prowas unable to access the table referenced by the table

position field.


Record: , Field: , Could not read embedded binary

data file.

Cause of Error: Config Prowas unable to read the binary data file associated with the

specified table.



40/64


Record: , Field: , Could not read embedded database

file.

Cause of Error: Config Prowas unable to read the embedded data file associated with



Record: , Field: , Could not update DCA list database.

Cause of Error: Config Prowas unable to write to the specified file.



Record: , Field: , Could not write to embedded binarydata file.

Cause of Error: Config Prowas unable to write to the binary data file associated with



Record: , Field: , Could not write to embedded

database file.

Cause of Error: Config Prowas unable to write to the embedded data file associated

with the specified table.


Record: , Field: , DCA/DTA application not found in

system point database.

Cause of Error: Config Procannot find the specified DCA or DTA application in the

system point database's DCA list file.



41/64


Record: , Field: , End of file encountered while

reading record.

Cause of Error: Config Proencountered the end of the file before it had finished

reading a record from the import file.

Action to Take: Make sure that the import file is structured appropriately for the table

being imported.

Record: , Field: , Invalid characters encountered in

value () will be ignored.

Cause of Error: Config Proencountered one or more invalid characters while parsing

the specified field in the import file.

Action to Take: Make sure that the import file does not contain invalid characters.

Record: , Field: , Invalid system point value.

Cause of Error: The system point you have referenced does not exist. This error may

occur if you have deleted or modified a peripheral board, or if you have

modified the point number assignment in the system point database.

Action to Take: Go back to the appropriate table window and select a valid system

point number.

Record: , Field: , No field is associated with the

multiple entry group.

Cause of Error: Config Procannot determine the "type" of the specified field.


DEVELOPERS: This error will occur if you have not defined a field in the multiple entry group for

each item in the associated list field. Refer to Create a Multiple Entry Fieldin the

Config Pro Table Bui lder User' s Guidefor further information about multiple

entry groups.


42/64


Record: , Field: , No list field is associated with the

multiple entry group.

Cause of Error: Config Procannot determine the "type" of the specified field.


DEVELOPERS: This error will occur if you have not associated a list field with the multiple entry

group. Refer to Create a Multiple Entry Fieldin the Confi g Pro Table Buil der

User' s Guidefor further information about multiple entry groups.

Record: , Field: , Range of points selected goes past

available system points.

Cause of Error: The number of points selected in the specified table is too large and

goes past the available system points.

Action to Take: Go back to the appropriate table window and do one of the following:

change the table position value so that the selected range of

points will fit into the associated system point table

change the number of points selected so that they don't go past

the end of the associated system point table

add points to the end of the associated system point table to

accommodate the range you have selected.

Record: , Field: , Range of records selected goes

past end of table.

Cause of Error: The number of records selected in the specified table is too large and

goes past the end of the table.

Action to Take: Go back to the appropriate table window and do one of the following:

change the table position value so that the selected range of

records will fit into the table

change the number of records selected so that they don't go past

the end of the table

add records to the end of the specified table to accommodate

the range you have selected.


43/64


Record: , Field: , System point () does not

exist; value set to default.

Cause of Warning: The system point specified in the import file does not exist in the

device.


appropriate value.

Record: , Field: , Unknown list item.

Cause of Error: The value specified in the "list" field is not valid.

Action to Take: Go back to the appropriate table window and ensure that you have

selected a valid item in the "list" field. If the error reoccurs, see page

D-2.

Record: , Field: , Unknown list item.

Cause of Warning: The value found in the list field is not valid.


appropriate value.

Record: , Field: , Unknown list item (); value

set to default ().

Cause of Warning: Config Proencountered a list item name which does not exist while

parsing the specified field in the import file.

Action to Take: Make sure that the import file does not contain invalid list item names.

Record: , Field: , Value of is above upper

limit of .

Cause of Error: The value you have specified is greater than the maximum allowablevalue of .

Action to Take: Go back to the appropriate table window and type in a value that is less

than or equal to the .


44/64


Record: , Field: , Value of is above upper

limit of ; value now set to .



.


appropriate value.

Record: , Field: , Value of is below lower

limit of .

Cause of Error: The value you have specified is less than the minimum allowable value

of .


greater than or equal to the .

Record: , Field: , Value of is below lower

limit of ; value now set to .



.

Action to Take: Go to the associated table window to verify that the field was set to anappropriate value.

Table was added in version of application

; data has been set to defaults.

Cause of Warning: A table has been found in the upgraded firmware that was not in the

original device's firmware. The table has been created with a default

number of records.

Action to Take: Edit the table appropriately.


45/64


Table was added to version of application

.

Cause of Warning: A table that is present in the upgraded application was not present in

the original application. The data for that table has been set to the

appropriate default values.

Action to Take: Edit the table appropriately.

Table was not found in version of application

; data has been lost.

Cause of Warning: A table that existed in the original device's firmware was not found in

the upgraded device firmware. All information associated with this

table has been deleted.


Table not found in device configuration (has been disabled).

Cause of Warning: Although the specified table is defined in the current device's firmware,

it was not found in the configuration file being converted. Config Pro

has disabled the table.


Table structure not defined for table of version

of application .

Cause of Error: Config Prowas unable to access the table structure definition for the

specified table.


There is NO Board Information.

Cause of Warning: The D.20 board configuration file was not created in the original

device's firmware. Config Prohas created the default D.20 board

configuration file.



46/64


Trying to read past end of file.

Cause of Error: Config Prowas read past the end of the specified file.


The D.20 peripheral termination board and digital output termination

information do not exist and must be manually updated.

Cause of Message: The configuration file did not contain any information about the

termination boards used with the D20 peripheral. No digital output

termination information was found either.

Action to Take: Set the termination board type information for each peripheral in the

Peripheral Informationdialog box. Then set the termination and

relay types for each digital output point on the K- and C-boards.

User cancelled out of process.

Cause of Error: You pressed before the specified process was completed.

Action to Take: Start the specified process again and let it run to completion, or carry

out whatever other task you need to perform.

VME board type is not valid.

Cause of Error: Config Prowas unable to access the specified database file.



47/64

Config Pro Configuration System User's Guide Appendix E: Borland Database Engine Configuration E-1

Appendix E: Borland DatabaseEngine Configuration

Database Engine Configuration Utility

The IDAPI configuration utility is an application that sets up and manages the

Borland Database Engine's configuration. The configuration parameters are stored in

a binary file with the extension .CFG (for example, IDAPI.CFG) that the database

engine reads at start-up. The main screen of the utility is shown below.

The IDAPI configuration utility is set up in notebook format, with tabbed "pages" that

govern different configuration tasks. These tasks include the following:

Setting the default parameters for any database driver your Borland Database

Engine application will access (Driverspage).


48/64

E-2 Appendix E: Borland Database Engine Configuration Config Pro Configuration System User's Guide

Creating a connection between your Borland Database Engine application and an

ODBC database (Driverspage).

Adding, deleting, or modifying database aliases (Aliasespage).

Setting your Borland Database Engine initialization parameters (Systempage).

Setting the format for displaying date, time, and numeric data (Date, Time, and

Numberspage).

NOTE: Before using this utility to change your IDAPI configuration file, be sure to close

any open IDAPI applications (such as Config Pro). Your changes will take effect the next

time you start your IDAPI application.

Paradox Driver Settings

The only settings you need to be concerned with are the Paradox driver settings.These settings determine the way that Paradox tables are created, sorted, and handled.

To modi fy the Paradox dr iver sett ings:

1. Select Paradox Driverfrom the list of Driver Nameson the drivers

page.

2. Update NET DIRif required. Leave all other settings as defaults.

NET DIR is the directory containing the network control file

(PDOXUSRS.NET). If the NET DIR directory is not set up properly, you

will not be able to access device configurations on a network drive.

If your projects reside on a network drive, NET DIR should be set to a

directory on the network drive to which you have full rights. All other

Config Prousers must configure the Paradox driver setting on their local

computers with the same NET DIR directory.

If your projects reside on a local hard drive, NET DIR can be set to any

directory on the hard drive.


49/64

Config Pro Configuration System User's Guide Appendix F: Interpreting Old Configuration Guides F-1

Appendix F: Interpreting OldConfiguration Guides

What Are "Old" Configuration Guides?

Before Config Prowas released, Harris RTU configurations were managed using a

tool called the WESDAC Configuration System (more commonly known as

Configuration System I). With this tool, you used a text editor to enter data into a

text file to define how applications were configured.

Config Pro, on the other hand, allows you to edit configuration data using a

graphically oriented table editor. This editor represents the configuration information

in a visually understandable format, and prevents you from entering invalid values.

The Config Proformat is very different from the Configuration System I text file

format.

All of the currently existing Harris application configuration guides have been written

for use with Configuration System I. While Harris is striving to upgrade these guides

to be usable with Config Pro as quickly as possible, you will likely have to refer to the

Configuration System I style guides for information in the interim.

This appendix describes how to use the Configuration System I configuration guides

with Config Pro.


50/64

F-2 Appendix F: Interpreting Old Configuration Guides Config Pro Configuration System User's Guide

Old Text Files vs. Conf ig ProTables

In Configuration System I, a single text file was used to define all of the tables

associated with a particular application. The name of the configuration file associated

with a given application was based on the application's identification number.

For example, the Harris HR6000/XA-21 application (which is identified as application

A003) has a text file called A003_CFG.TXT associated with it. The accompanying

configuration guide explains how to fill in the various parts of the A003_CFG.TXT

file.

With Config Pro, there is no A003_CFG.TXT file associated with application A003.

Instead, all configuration data is stored in separate database files that are managed by

the Config Protable editor. The tables that make up application A003 (or Harris

HR6000/XA-21) are represented by icons and grouped together in the application

window, as shown in the diagram below.

The Harris HR6000/XA-21 application configuration guide describes how to

configure each of the tables shown in the HR6000/XA-21 application window.


51/64


Old and New: An Example

The following figure shows part of a typical configuration text file: the table and data

definitions for the Harris HR6000/XA-21 Digital Input Map Table (A003MT01).

The DEFINE_TABLE section (shown below) defines the structure and number ofrecords in the table. This data controls how Configuration System I interprets the data

in the DATA_TABLE section.

DEFINE_TABLE = 5 NAME = A003MT01 MAXRECS = 6 /* No. of Inputs */ CONTROL_WORD = 0x92 DEFINE_RECORD:

SIZE = * {5}

DEFINE_DATA: li*4 /* 1. System point number */ c /* 2. COS ownership */ c /* 3. SOE ownership */

c /* 4. Freeze ownership */ b /* filler */

The DEFINE_DATA part of the DEFINE_TABLE section (shown above) provides

information about how each element of data must be formatted. The DEFINE_DATA

information is generally in the following format:

t[n]*w where: t= type, n= quantity, w= width

The nand wfields are optional. If they are not specified, the default for both is one.

Thetfield can contain the following values:

i = signed integer li = long signed integer

u = unsigned integer lu = long unsigned integer

f = floating point number lf = long floating point integer

o = octal integer lo = long octal integer

d = decimal integer ld = long decimal integer

b = byte filler h = hexadecimal integer

s = character string x = hexadecimal integer

c = single character lx = long hexadecimal integer

r = read in data from external file


52/64


The DATA_TABLE section contains the actual configuration data.

DATA TABLE = 5 /* SYSTEM COS SOE FREEZE */ /* POINT OWN OWN OWN */ 2 Y Y Y 3 Y N Y 4 Y Y Y 5 Y Y Y 6 Y Y Y -1 Y Y Y

The descriptions of the Harris Digital Input Map Table fields (as named in the

DEFINE_TABLE section of the table) are shown below. This is the type of

information that is typically contained in the old Configuration System I configuration

guides.

System Point Number Field

This numeric field specifies the system point that is associated with the logical point.

The first entry in the table for the port is the first logical point. Use negative one (-1)

to define spares.

COS Ownership Field

This single-character field specifies whether COS is to be generated for the logical

point. Specify Y if COS is to be generated, or N if COS is not to be generated.

SOE Ownership Field

This single-character field specifies whether SOE is to be generated for the logical

point. Specify Y if SOE is to be generated, or N if SOE is not to be generated.

Freeze Ownership Field

This single-character field specifies whether the logical point, when indexed by a

frozen accumulator port, is to affected by a freeze operation (broadcast, timed, orimmediate). Specify Y to enable freezing for the point, or N to disable freezing for the

point. When the same system point is mapped by two or more logical points within the

same LRU, specifying Y for any one point will affect all the points.


53/64


In Config Pro, the configuration data for the table is presented in spreadsheet format.

The following diagram presents the same information as the DATA_TABLE section

shown above, but in the more friendly Config Proformat.


54/64


Detailed Comparison of the Two Formats

In Config Pro, the structure of the data tables is hidden from you: Config Prohas no

counterpart for the Configuration System I DEFINE_TABLE section.

The Config Protable editor only allows you to enter actual configuration table data.

This is equivalent to editing the DATA_TABLE information in Configuration System

I.

Configuration Table Names

In Configuration System I, the configuration tables had short, vague identification

numbers. The Harris Digital Input Map Table identification, for example, is

A003MT01.

Config Prouses both the old table ID number, plus a descriptive name to identify the

table. The diagram below shows the icon that represents the Digital Input Map Table.

Note that the new table name is shown first, followed by the table ID number.

Column Titles

The column titles in the Config Protables are loosely based on the names given to the

fields in the old configuration guides. These titles/field names should be used as your

main points of reference when you use the Configuration System I configuration

guides with Config Pro. In the example on page F-3, the field identified as System

Point Fieldis identified asDigital Input Pointin the Config Protable editor.


55/64


Data Fields

Certain table fields that exist in Configuration System I files are shown differently in

Config Pro, or are not shown at all, depending on the nature of the configuration data.

In the example on page F-3, the filler field that was defined in the ConfigurationSystem I DEFINE_TABLE section is not present in the Config Protable. As well, in

the Config Protable, you do not edit the remaining fields by manually entering

numbers and characters, but rather by selecting from constrained lists of options.

A explanation of the various types of fields supported by Config Procan be found in

the Representati on of Di ff erent F ield Typessection of this appendix.

Order of Data Fields

The general order of the fields is the same in Config Proas it is in Configuration

System I. For the most part, you should be able to match up the fields in the old

configuration guide with those shown in the Config Protable. There may be

occasional exceptions, for example theFillerfield mentioned in the previous section.

Status Bar

Whenever a field in a Config Protable is highlighted, a short description of the field is

shown in the status bar. This description expands upon the column title, and furtherexplains what kind of data you are editing.

If the column title and status bar do not provide enough information for you, then you

will have to resort to using the associated Configuration System I configuration guide.


56/64


Representation of Different Field Types

This section describes the types of fields you can find in a configuration table, and

compares how Configuration System I and Config Prorepresent those fields.

Scal ing, Time Per iod, and Other Num eric Fields

Any fields that allow you to select from a continuous range of values are displayed as

numbers, and are modified by typing in a numeric value. The example below shows a

numeric field containing theRTS On Delayparameter.

Configuration System I Representation:

DEFINE_TABLE = 1 ... DEFINE_DATA ... I*2 /* 6. RTS on delay */ ...

DATA_TABLE = 1 ... 40 /* 6. RTS on delay */ ...

Config ProRepresentation:


57/64


Descript io ns and Other Text Entry Fields

Any fields that require a description or other user-defined string are displayed as text,

and are modified by typing in a sequence of alphanumeric characters. The example

below shows a text entry field containing a single line of the WESMAINT II Welcome

Message.


DEFINE_TABLE = 3 /* Login System Credit Message */ ... DEFINE_DATA: ... s[1]*80 /* Text to display */ ...

DATA_TABLE = 3 /* Login System Credit Messages */ ...

"Harris Distribution Automation Products" ...



58/64


DCA Index Fields

In Configuration System I, it was important to specify the position of the system point

database record associated with a DCA or DTA application. This record was found in

the CFG_DCA table of the B008_CFG.TXT configuration file. The following

example shows how a DCA index field is defined in Configuration System I.


DEFINE_TABLE = 1 /* DCA-specific parameters. */ ... DEFINE_DATA: ... I[1]*2 /* This DCA's index into WIN CFG_DCA configuration table. */ ...

DATA_TABLE = 1

... 1 /* This DCA's index into WIN CFG_DCA configuration table. */ ...


Config Proautomatically handles all DCA index fields. Although they are displayed,

they are not editable.


59/64


Filler Fields

Filler fields are used to reserve space in a configuration table record. The following

example shows how a filler field is defined in Configuration System I.

DEFINE_TABLE = 5 ... DEFINE_DATA: ... b /* filler. */ ...

DATA_TABLE = 5 ... 0 /* filler. */ ...

Config Proautomatically handles all filler fields, and therefore does not display them

in the table editor.


60/64


Communicat ion Port and Other List Fields

A list field allows you to select from or enter one of a small, fixed set of values. The

example below shows a communications port field that is set to COM1. You could

enter the name of any one of the available communication ports for this device,

assuming you know their names.


DEFINE_TABLE = 1 ... DEFINE_DATA: ... s*4 /* 1. COM port */ ...

DATA_TABLE = 1 ...

COM1 /* 1. COM port */ ...


In Config Pro, a field that lets you to select from a list of items is identified by a down-

arrow preceding the value, as shown here.

To change the value, you select the field, and then either double-click on it or press

on the keyboard. This brings up a list box, from which you can make your

selection.


61/64


Sub-tables

Some tables contain groups of fields that are repeated many times. The following shows sub-

table information for user rights settings in WESMAINT II.


DEFINE_TABLE = 2 /* Users who may log in record */ ... DEFINE_DATA: ... lu*4, lx*4, lx*4, /* 1st application control */ lu*4, lx*4, lx*4, /* 2nd application control */ lu*4, lx*4, lx*4, /* 2nd application control */ ...

DATA_TABLE = 2 /* Users who may log in definitions */ ... 14, ffffffff, ffffffff, /* May use all WESMAINT functions */ 3, ffffffff, ffffffff, /* May use all Harris functions */ 00, 00, 00, /* May not use any functions */ ...


Groups of repeated fields are represented in Config Proby a field containing an embedded

table, as shown below.

To edit the contents of a sub-table, you select the field, and then either double-click on it or

press on the keyboard. This brings up a secondary table editor that allows you to

edit the sub-table.


62/64


System Point Fields

All fields that reference a system point are shown with both the physical system point

number and the point descriptor. The following example shows the first digital input

point selected.


DEFINE_TABLE = 5 ... DEFINE_DATA: ... li*4 /* 1. System point number */ ...

DATA_TABLE = 5 ... 0 /* 1. System point number */ ...


Note that in Config Pro, the system point number is always 1-based (i.e. the firstsystem point is always point 1). Most Configuration System I configuration guides

show the system point number as a 0-based value. Be careful when comparing the

two.

To change the system point value in Config Pro, you must select the field, and then

either double-click on it or press on the keyboard. This brings up a list of

all points defined in the RTU. You can then make your selection.


63/64


Table Offset Fields

In Configuration System I, table offset fields contain values that define a record

position within another table. The following example shows the first record in the

associated table having been selected.


DEFINE_TABLE = 1 ... DEFINE_DATA: ... I*2 /* 17. LRU x-ref table offset */ ...

DATA_TABLE = 1 ... 00 /* 17. LRU x-ref table offset */ ...


Note that in Config Pro, table offsets are almost always shown as 1-based values (i.e.the first record in the associated table is always record 1). Most Configuration system

I configuration guides show table offsets as 0-based values. Be careful when

comparing the two.

To change the table offset value in Config Pro, you select the field, and then either

double-click on it or press on the keyboard. This brings up a copy of the

associated table, from which you can select a new offset.


64/64

On-line Help Support

Config Procurrently does not have on-line help available for configuration table

information. Please refer the appropriate Configuration System I configuration guide

for help, or contact the Harris DAP Customer Service Department, shown in the

About This Guidechapter.

Date post:	01-Mar-2018
Category:	Documents
Upload:	salvator-fayssal
View:	216 times
Download:	1 times

cfgpro08.pdf

Documents