Micom C264/C264C: Bay Computer

MiCOM C264/C264C
Bay Computer
C264/EN AD/C41
Addendum
Addendum C264/EN AD/C41
MiCOM C264/C264C Page 1/74
CONTENT
1. SCOPE OF THE DOCUMENT 3
2. CHAPTER C264_ENIN_C40 4
3. CHAPTER C264_ENAP_C40 33
4. CHAPTER C264_ENST_C40 38
5. CHAPTER C264_ENCT_C40 53
6. CHAPTER C264_ENTD_C41 66
7. CHAPTER C264_ENMF_C40 67
8. CHAPTER C264_ENFT_C40 69
9. CHAPTER C264_ENHI_C40 72
C264/EN AD/C41 Addendum
Page 2/74 MiCOM C264/C264C
BLANK PAGE
1. SCOPE OF THE DOCUMENT

The present document is an addendum to the MiCOM C264 Operator and technical
documentation - MiCOM C264 issue C40. It describes the additional features and evolution
between the PACiS V4.5.0 and the PACiS V4.5.5 with references to the specific chapters.
2. CHAPTER C264_ENIN_C40
[Cancel and Replace]
7. MiCOM C264 SOFTWARE INSTALLATION

While you have inserted the PACiS CD-ROM System installation into your CD-drive you will
find the install software of the computer into the following directory:
\System\Delivery\PACiS Va.b.c\C264 VX.YZ (Va.b.c is the PACiS system version, X.YZ is
the computer version).
Install the Computer_X.YZ.exe on your PC.
It is recommended to use default installation parameters. This will install CMT (Computer
Maintenance Tool), FTP server and set the C264 application in a directory accessible by the
MiCOM C264.
Connect the MiCOM C264 and the PC on the same Ethernet switch or directly with a
crossed Ethernet wire.C264 installation is procedure is same for CPU2 (CPU260) and CPU3
(CPU270).
7.6 C264 Software upgrade
7.6.1 C264 - CPU260 Software Upgrade
To use C264 release B5.14 and above it’s mandatory to update the C264 computer
"bootrom”. A new flash memory partition is done to create a specific zone for waveforms.
This guide details the installation procedure.
NOTE: There is no backward compatibility, so it’s mandatory to re-install
bootrom version for a C264 CPU2 (CPU260) when using oldest C264
BY.xx version of computer software.
This procedure is also useable to re-install the oldest version.
(Bootrom and Bootprom are two names for the same thing).
Compatibility matrix
C264 release label Bootrom version label

B5.xx: lower than or equal to 13 A0.18 and below
B5.xx: upper than or equal to 14 B0.14
7.6.1.1 How to find the Bootrom version of the C264 - CPU260 board
7.6.1.1.1 Using the serial interface in front panel
The bootrom version is indicated on the first text sent to the terminal.
It is indicated on the line beginning by “BSP version”.
FIGURE 1: CPU2 (CPU260) - BOOTROM VERSION AT HYPERTERMINAL
7.6.1.1.2 Using the CMT

Start the CMT software and select the Ethernet from the Selected Link. Search the computer
and select the computer in “computer list” menu.
Stop calculator in "bootprom" mode.
1. Select the computer in "computer's list" menu
2. Click on "Parameters" menu button
3. Select "Bootprom boot" and click on "Set boot parameter"
FIGURE 2: CPU2 (CPU260) - BOOT PARAMETERS AT CMT TOOL
4. Click menu button "Reboot computer"
FIGURE 3: CPU2 - CONFIRM REBOOT
5. Click "YES" and wait for computer reboot ends

6. Select the computer in "computer's list" menu when this one is again available
7. Click on "Computer version" menu button
The bootrom version is indicated on the line beginning by “BSP version” as shown below.
NOTE: Once the “boot prom boot” mode has been selected, every time the
computer is rebooted or powered-up it will be stopped in this mode.
The mode must be manually set to “Flash boot” to get back a
normal mode.
FIGURE 4: CPU2 (CPU260) - BOOTROM VERSION AT CMT TOOL
7.6.1.1.3 Label on the CPU Board

Each CPU board as a label on its solder side, indicating the version of the bootrom installed
on it by the production team as shown below.
FIGURE 5: CPU260 - BOOTROM VERSION ON CPU BOARD

NOTE: Once the bootrom version has been updated to a new version it’s
mandatory to update also manually the label.
7.6.1.2 Procedure to Upgrade Software

7.6.1.2.1 Run CMT
Use the version of CMT that includes the right version of the bootrom.
For a B0.14 bootrom update uses at least a B5.14 version of CMT.
For an A0.18 bootrom update uses at the most a B5.13 version of CMT.
7.6.1.2.2 Stop calculator in "bootrom" mode
• Select the computer in “computer’s list” menu
• Click on “Parameters” button
• Select “Bootprom boot” and validate by clicking on “Set boot parameter”
FIGURE 6: CPU260 - BOOT PARAMETERS AT CMT TOOL
• Click on “Reboot computer” button
• Click “YES” and wait for computer reboot ends

7.6.1.2.3 Update "bootrom"
• Select computer and in "BootInstall" menu select the directory where the C264
computer software is installed.
Normally for a default installation: "C:\Program Files\PACiS
• Then select the sub directory specific of you board type:

For a default installation: "C:\Program Files\PACiS\Computer\C264_cpu2"
• Finally select the file bootrom.flh.

The directory may be "C:\Program Files\PACiS\Computer\C264_cpu2"
C:/Program Files/PACiS/Computer/C264_cpu2/bootrom.fih
FIGURE 7: CPU2 (CPU260) - UPDATE BOOTROM
• Click on "Update bootrom"
FIGURE 8: STOP COMPUTER
• Bypass this warning Click on "OK"

FIGURE 9: CPU2 (CPU260) - UPDATE BOOTROM CONFIRM
• Click on "YES"
Messages:
Update bootrom progress

/RAMDEV/bootrom.flh: resent frames x/yyy
Writing in Flash
Writing Bootrom
Update bootrom: OK
C:/Program Files/PACiS/Computer/C264_cpu2
FIGURE 10: CPU2 (CPU260) - UPDATE BOOTROM: OK
Wait until the end of the update = Update bootrom: OK
• Reboot computer (Click menu button "Reboot computer")

• Click on "YES"
7.6.1.2.4 Erase and Format FLASH
• After reboot complete, select the computer.
• In "File explorer" menu click on button "Flash format"
C:/Program Files/PACiS/Computer/
FIGURE 11: CPU2 (CPU260) - ERASE AND FORMAT FLASH
• Bypass this security message: Click on "OK"

FIGURE 12: CONFIRM ERASE AND FORMAT FLASH
• Click "YES"
Messages:
Flash formatting progress:

00x% done
Wait few minutes before format flash ending.
• Click "OK"
• Click "YES"
7.6.1.2.5 BootInstall
Once the reboot finished the computer stays in “STOPPED” mode.
• Using the CMT, select the computer and in "BootInstall" menu choose the installation
directory of the C264 CPU type.
For a default installation the directory is:
"C:\Program Files\PACIS\Computer\C264_cpu2"
C:/Program Files/PACiS/Computer/C264_cpu2/
FIGURE 13: CPU2 (CPU260) - BOOT INSTALL
• Click on "Start: bootInstall"
• Bypass the security if necessary: Click "NO"

FIGURE 14: CPU2 (CPU260)- BOOT INSTALL CONFIRM
• Click "YES"
Messages:
/flash/bin/filename: Resent frames x/yyy

Total installation progress
• Wait message "BootInstall finished !"
7.6.1.2.6 Set parameters and restart computer
• Click on "Parameters" menu button
FIGURE 15: CPU2 (CPU260) - SET BOOT PARAMETERS
• Select "Flash Boot" and validate clicking on "Set boot parameter"

• Reboot the computer (Click menu button "Reboot computer")
7.6.2 C264 - CPU270 Software Upgrade

To use C264 release B5.14 and above it’s mandatory to update the C264 computer
"bootrom”. A new flash memory partition is done to create a specific zone for waveforms.
This guide details the installation procedure.
NOTE: There is no backward compatibility, so it’s mandatory to re-install
bootrom version for a C264 CPU3 (=CPU270) when using oldest
C264 BY.xx version of computer software.
This procedure is also useable to re-install the oldest version.
(Bootrom and Bootprom are tow names for the same thing).
Compatibility matrix
C264 release label Bootrom version label

B5.xx: lower than or equal to 13 B0.12 and below
B5.xx: upper than or equal to 14 B0.14 or B0.15 and above
B6.xx: ( any xx ) B0.14 / B0.15 / B0.17 and above
Note for old bootrom:

It’s preferred to update the first delivered cpu3 boards using B0.7 bootrom version to B0.12
to avoid the loss of “boot parameters” after a keyboarding error.
Note on B0.14/B0.15 bootrom version differences:
The version B0.14 modifies the new flash memory partition, version B0.17 adds the
possibility to manage serial number bigger than 32665. This version, B0.17, will be used by
production when they will pass this limit.
As the serial number of a CPU board is unique and linked to the board (for all is life!) an
update from B0.14 to B0.17 it’s not necessary.
7.6.2.1 Find the Bootrom version of the C264 CPU270 board

7.6.2.1.1 Using the serial interface in front panel
For bootrom versions lower than B015
The bootrom version is not indicated on the first text sent to the terminal on versions until
B0.14.
It can be indicated after typing the command “v” at the line beginning by “BSP version”.

For bootrom versions upper or equal to B015

The bootrom version is indicated on the first text sent to the terminal.
It is indicated on the line beginning by “BSP version”.

7.6.2.1.2 Using the CMT
• Stop calculator in "bootprom" mode
• Select the computer in "computer's list" menu
• Select "Bootprom boot" and click on "Set boot parameter"
FIGURE 18: CPU3 (CPU270) – BOOTPROM BOOT
• Click menu button "Reboot computer"
• Click "YES" and wait for computer reboot ends
• Click on "Computer version" menu button

The bootrom version is indicated on the line beginning by “BSP version”.
FIGURE 19: CPU3 (CPU270) – BOOTROM VERSION AT CMT TOOL
NOTE: Once the “Bootprom boot” mode has been selected every time the
computer is rebooted or powered-up it will be stopped in this mode.
The mode must be manually set to “Flash boot” to get back a
normal mode.
7.6.2.1.3 Label on the CPU

Each CPU board as a label on its solder side, indicating the version of the bootrom installed
on it by the production team:
FIGURE 20: CPU3 (CPU270) – BOOTROM VERSION ON CPU BOARD
NOTE: Once the bootrom version has been updated to a new version it’s
mandatory to update also manually the label (think to next user …).
7.6.2.2 Procedure to upgrade software

7.6.2.2.1 CPU boards coming directly from production
The board stop it-self after the first count-down, it is in bootrom mode.
For bootrom version lower than B0.15 bootrom update it is not possible in this mode. It is
mandatory to boot the board in network boot mode.
The C264 in this mode download its application software using File Transfert Protocol (FTP),
so the FTP server must run on the PC server.
A) Run CMT
Use the version of CMT which includes the right version of the bootrom.
For a B0.14 bootrom update uses at least a B5.14 version (or any B6.xx) of CMT.
For a B0.12 bootrom update uses at the most a B5.13 version of CMT.
B) Configure Network boot
• Select the computer in "Computer's list" menu
• Select "Network boot"
• Fill with the right values: IP on Ethernet and IP 2 on Ethernet
• Fill with the right value: host IP (the address of your PC)
• Validate clicking on "Set boot parameter"
FIGURE 21: CPU3 (CPU270) – SET PARAMETERS

NOTE: With version lower than B0.13 this setting lasts about one minute and
sends an error message.
But the memorisation of new parameters is done.
• Click button "Reboot computer"

WARNING: FOR VERSIONS B6.00 TO B6.08 THE COMMAND REBOOT CAN ONLY
BE ISSUED USING THE SHELL INTERFACE (REBOOT SHELL
COMMAND) OR POWERING DOWN AND UP THE COMPUTER WHEN
THE C264 IS IN STOPPED MODE.
• Click "YES" and wait for computer reboot ends.

As the computer it is normally in maintenance mode you directly pass to step 7.6.2.2.3.
7.6.2.2.2 Run CMT
Use the version of CMT that includes the right version of the bootrom.
For a B0.14 bootrom update uses at least a B5.14 version (or any B6.xx) of CMT.
For a B0.12 bootrom update uses at the most a B5.13 version of CMT.
7.6.2.2.3 Stop C264 Application
Set the computer mode to “Stopped”:
• Select the computer in "Computer's list" menu
• Click on "Stop computer” menu button

The computer mode can be red using “Computer version” menu button.
7.6.2.2.4 Update Bootrom
• Select computer and in "BootInstall" menu select the directory where the C264
computer software is installed
• Normally for a default installation: "C:\Program Files\PACiS
• Then select the sub directory specific of you board type:
• For a default installation: "C:\Program Files\PACiS\Computer\C264_cpu3"
• Finally select the file bootrom.flh

The directory may be "C:\Program Files\PACiS\Computer\C264_cpu3".
FIGURE 22: CPU3 (CPU270) – UPDATE BOOTROM
• Click on "Update bootrom"
• Bypass this warning Click "OK", if it appears

FIGURE 23: CPU3 (CPU270) – UPDATE BOOTROM CONFIRM
• Click "YES" on Begin update bootrom

Messages:
Update bootrom progress

/RAMDEV/bootrom.flh: resent frames x/yyy
Writing in Flash
Writing Bootrom
Update bootrom: OK
Wait until the end of the update = Update bootrom: OK

FIGURE 24: CPU3 (CPU270) – UPDATE BOOTROM IN PROGRESS

For versions B5.xx and B6.09 and above, it is possible to restart the C264 using the
"Reboot computer" menu button.
COMMAND) OR POWERING DOWN AND UP THE COMPUTER.
• Click "YES"
7.6.2.2.5 Stop C264 Application

Set the computer mode to “Stopped”:
• Click on "Stop computer” menu button

The computer mode can be red using “Computer version” menu button.
7.6.2.2.6 Erase and Format FLASH

After reboot complete, select the computer.
In "File explorer" menu click on button "Flash format".
FIGURE 25: CPU3 (CPU270) – ERASE AND FORMAT FLASH
• Bypass this security message: Click "OK”, if it is necessary
• Click "OK"
FIGURE 26: CPU3 (CPU270) – ERASE AND FORMAT FLASH CONFIRM
• Click "YES"
Messages:
Flash formatting progress:

00x% done
Wait few minutes before format flash ending.

FIGURE 27: CPU3 (CPU270) – ERASE AND FORMAT FLASH OK
• Click "OK"

• Click "YES"
7.6.2.2.7 BootInstall
• Select computer and in "BootInstall" go to the installation directory of the calculator

For a default installation the directory may be:
"C:\Program Files\PACiS\Computer\C264_cpu3"
FIGURE 28: CPU3 (CPU270) – BOOT INSTALL
• Click on "Start: bootInstall"
• Bypass the security if necessary: Click "NO"

FIGURE 29: CPU3 (CPU270) – BOOT INSTALL CONFIRM
• Click "YES"
Messages:
/flash/bin/filename: Resent frames x/yyy

Total installation progress
FIGURE 30: CPU3 (CPU270) – BOOT INSTALL IN PROGRESS
FIGURE 31: CPU3 (CPU270) – BOOT INSTALL IN PROGRESS

Wait message "BootInstall finished!”
7.6.2.2.8 Set computer parameters
FIGURE 32: CPU3 (CPU270) – SET BOOT PARAMETERS
• Select "Flash Boot" and click on "Set boot parameter"

In case of error, fill out the field IP 2 on Ethernet with a fake value.
7.6.2.2.8 Restart computer

Reboot the computer (Click menu button "Reboot computer").
3. CHAPTER C264_ENAP_C40
4.7.1.5 Setting acquisition attributes of Modbus legacy network

When adding a Modbus legacy network, the following attributes, available for all its IEDs,
must be updated:
1. number of retries (range [1, 10], step 1): corresponds to the number of tries of the
same frame without IED response, the computer will send it before setting it
disconnected.
2. acknowledgement time-out (range [100 ms, 30 s], step 100 ms): maximum delay an
IED answer is awaited when the computer asks it an information.
3. synchronisation (none / Schneider Electric / SEPAM / Flexgate) ): refer to section
4.3.5.2 of chapter C264/EN CT for details and to the reference document of the
connected IED.
4. synchronisation cycle (range [10 s, 655350 s], step 10 s): time synchronisation
period of the IED by the computer. Only significant if attribute (3) is set to ‘Schneider
Electric’, 'Flexgate' or to 'SEPAM'.
5. downgraded cycle (range [1s, 10 s], step 100 ms): if an IED is set disconnected by
the computer, it tries to re-connect it regularly at this cycle.
6. inter frame duration (range [1, 50], step 1): this attribute represents the minimum
time, expressed in number of characters, that must exist between two frames.
(1)
(2)
(3)
(4)
(5)
(6)
FIGURE 38: SETTING ‘ACQUISITION’ ATTRIBUTES OF A MODBUS LEGACY NETWORK
4.7.1.11 Setting attributes of a MODBUS acquisition type

When adding a Modbus acquisition type, the following attributes, available for all its linked
IEDs, must be updated:
1. IED type (Modicon / M300 / MICOM S20 / M230 / WAGO / ABB Flexgate / SEPAM):
by default use ‘Modicon’.
2. MODBUS function (1 / 2 / 3 / 4 / 7 / 8 ): function number used for polling frame: To
test the IED connection, this attribute gives which Modbus function is used. For
Schneider Electric IED product, the function 7 is generally used.
3. mapping address (range [0, 232-1]): associated to attribute (2), it gives which start
address is used to test the IED connection:
− if MODBUS function is set to 1 or 2 this attributes defines a bit address
− if MODBUS function is set to 3 or 4 this attributes defines a word address
− if MODBUS function is set to 5 this attributes is not significant
− if MODBUS function is set to 8 this attributes defines a sub-code
− if MODBUS function is set to 7 this attributes is not significant

4. size to read (range [0, 2048]: associated to attribute (3), it gives which length is used
to test the IED connection:
− if MODBUS function is set to 1 or 2 this attributes defines a number of bits
− if MODBUS function is set to 3 or 4 this attributes defines a number of words
− if MODBUS function is set to 7 or 8 this attributes is not significant

5. data frame length (range [2 bytes, 256 bytes]): if an IED cannot manage frames
longer than 256 bytes, this attribute must be set to the available length for the IED.
(1)
(2)
(3)
(4)
(5)
FIGURE 45: SETTING ATTRIBUTES OF A MODBUS ACQUISITION TYPE
4.7.2.3 Defining an IED address for a MV datapoint

The addition of an IED address for a MV datapoint is done via the “Objects entry” window at
IED MV mapping level by clicking on mouse’s right button.
Once added, IED MV address attributes must be set at SCE level:
1. short name of the address: used for internal SCE identification.
For Modbus protocol:
2. mapping address (range [0, 65535],step 1): Word address.
3. fonction (range [0, 65535],step 1): Modbus function to use to read the MV:
- 3, 4: read word,
- 7 : read status.
4. data format: see following paragraph (Measurement formats that can be used with
the MODBUS protocol).
For T101 protocol:
5. information object address (range [0, 16777215],step 1).
6. common address of ASDU (range [-1, 65535],step 1): by default (–1) is equal to IED
address.
For T103 protocol:
7. ASDU number (range [0, 65535],step 1):
- 3, 4, 9 (for all IED)
- 10 (for acquisition of measurement with "generic Services"
- 77 (Only for Px2x)
- 73 (Only for Px3x).
8. fonction type (range [0, 65535],step 1).
9. information number (range [0, 65535],step 1).
10. index in the ASDU (range [0, 65535],step 1).

11. common address of ASDU (range [-1, 65535],step 1): by default (–1) is equal to IED
address.
12. unit of the MEAS (Voltage / Current / Power / Frequency / No Unit).
13. substituted if unknown (No / Yes).
For this protocol it is possible to perform acquisition of measurements only using the Generic
Services of IEC 60870-5-103 protocol by polling. This can be done by setting some
parameters as follows:
− ASDU number: 10
− function type 254
− information number: 244
− index in the ASDU: Generic Identification Number given by the mapping of the IED
For DNP3 protocol:
14. address (range [0, 65535],step 1).
Modbus
(1)
(2)
(3)
(4)
T101
(5)
(6)
T103
(7)
(8)
(9)
(10
(11 )
) (12
(13 )
)
DNP3
(14
)
FIGURE 52: DEFINING AN IED ADDRESS FOR A MV DATAPOINT

Measurement formats that can be used with the MODBUS protocol

Because the Modbus norm only describes the transmission of 16 bits values (transmission of
the high order byte first), new formats must be defined to describe the different ways to
transmit 32 bits values (what ever their type: signed or unsigned integers, real values) or
8 bits values.
So the format to apply to an analog input depends on the way it is transmitted and
consequently on the representation of the value in the memory of the device.
In the following table, the “transmission order” column (4) indicates the way a value is
transmitted, i.e. the order in which the bytes of the value are transmitted. The bytes are
numbered from 1 (lowest order byte) to 4 (highest order byte).
Transmission
Format Description
order
INT8_LB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the low order byte of the word.
INT8_HB Transmission of an 8 bit signed integer in a 16 bit value. /
The significant byte is the high order byte of the word.
UINT8_LB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the low order byte of the word.
UINT8_HB Transmission of an 8 bit unsigned integer in a 16 bit value. /
The significant byte is the high order byte of the word.
INT16 Transmission of a 16 bit signed integer. The high order 2-1
byte is transmitted first (see Modbus norm)
UINT16 Transmission of a 16 bit unsigned integer. The high order 2-1
byte is transmitted first (see Modbus norm)
INT32_LW_LB Transmission of a 32 bit signed integer. The low order 1-2-3-4
word of the long value is transmitted first. The low order
byte of each word is transmitted first.
INT32_LW_HB Transmission of a 32 bit signed integer. The low order 2-1-4-3
word of the long value is transmitted first. The high order
INT32_HW_LB Transmission of a 32 bit signed integer. The high word of 3-4-1-2
the long value is transmitted first. The low byte of each
word is transmitted first.
INT32_HW_HB Transmission of a 32 bit signed integer. The high order 4-3-2-1
UINT32_LW_LB Transmission of a 32 bit unsigned integer. The low order 1-2-3-4
UINT32_LW_HB Transmission of a 32 bit unsigned integer. The low order 2-1-4-3
UINT32_HW_LB Transmission of a 32 bit unsigned integer. The high order 3-4-1-2
UINT32_HW_HB Transmission of a 32 bit unsigned integer. The high order 4-3-2-1
REAL32_LW_LB Transmission of a 32 bit real value. The low order word is 1-2-3-4
transmitted first. The low order byte of each word is
transmitted first.
Transmission
Format Description
order
REAL32_LW_HB Transmission of a 32 bit real value. The low order word is 2-1-4-3
transmitted first. The high order byte of each word is
transmitted first.
REAL32_HW_LB Transmission of a 32 bit real value. The high order word is 3-4-1-2
transmitted first. The low order byte of each word is
transmitted first.
REAL32_HW_HB Transmission of a 32 bit real value. The high order word is 4-3-2-1
transmitted first. The high order byte of each word is
transmitted first.
M230_T5_TYPE Transmission of a 32 bit: Unsigned Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary unsigned value 24 bytes
M230_T6_TYPE Transmission of a 32 bit: Signed Measure 4-3-2-1
Bit 31to 24 decimal exposant (signed 8 bytes)
Bit 23…00 binary signed value 24 bytes
M230_T7_TYPE Transmission of a 32 bit: power factor 4-3-2-1
Bit 31to 24 Signed:Import / Export (00/FF)
Bit 23…16 Signed:Inductive / capacitive (00/FF)
Bit 15…00 Unsigned value (16 bytes)
ION_MODULUS Transmission of a 32 bit: ION Energy values 4-3-2-1
_10000_unsigned
Bit 31to 16 reg Hight: RH= unsigned value/10000
Bit 15…00 reg Low: RL = unsigned value modulus 10000
Value = RH*10000+RL
ION_MODULUS Transmission of a 32 bit: ION Energy values 4-3-2-1
_10000_signed
Bit 31to 16 reg Hight: RH= signed value/10000
Bit 15…00 reg Low: RL = signed value modulus 10000
Value = RH*10000+RL
Both reg high and low are signed
4. CHAPTER C264_ENST_C40
[New Chapter]
1.3 MiCOM S1 PACiS

It describes the Settings -or on-line- parameters, which can be modified in runtime on
MiCOM C264. MiCOM S1 PACiS application provides the facility to view and edit the
parameters/settings of C264.
The setting for the C264 parameters will be performed using a file transfer mechanism. The
setting is allowed only if the C264 is in Operational mode. In case of C264 redundancy, the
setting can be performed only on the Active computer (an internal mechanism between
Active and Standby allows to avoid discrepancy between both computers parameters).
1.3.1 Presentation of parameters in MiCOM S1 PACiS.
The structure of parameters in MiCOM S1 PACiS is:
• OP.PARAMETERS: global C264 parameters in read-only mode (database version, IP

address, computer name, …)
• CONFIGURATION: general parameters for protective functions
• PROTECTION GROUP 1: parameters for each protective function
• PROTECTION GROUP 2: parameters for each protective function
• AUTOMAT.CONTROL
• AVR
• Synchrocheck
• Auto-recloser bay 1
• ….
• Auto-recloser bay N
• ISAGRAF Automatism 1
• …
• ISAGRAF Automatism N
• PSL Automatism 1
• …
• PSL Automatism M
The description of each parameter can be seen in below figure.
FIGURE 1: EXAMPLE OF MiCOM S1 PACiS
Built in function like Isagraf, PSL automatism and Auto-Recloser are configured in SCE. Only
parameters of configured functions are visible and editable in MiCOM S1 PACiS.
It is possible to set the following functions:
• Automation ' built-in’: as autorecloser, synchrocheck, AVR
• Protective function implemented for PACiS
• Automation: ISaGRAF: (float or integer threshold & Boolean)
• Automation PSL (=FBD): Two kinds of parameters in FBD: The timeout used for
(TON/ TOFF) and the parameter (Boolean) validation
1.3.2 Upload a setting file to C264
FIGURE 2: MiCOM S1 PACiS SETTING SOFTWARE

The MiCOM S1 PACiS application indicates that a file .VAL is available. The “VAL” file is
transferred via FTP. C264 is the FTP client. A FTP server is mandatory on the MiCOM S1
PACiS host PC. MiCOM S1 PACiS application transfers “VAL” file to a computer defined by
its IP address. Computer checks the coherency of this file and acknowledges it positively or
negatively.
MiCOM S1 PACiS upload values to c264 using the function “Set Settings”
1.3.2.1 Editing the Online Parameters
Install the CMT software.
Start the “MiCOM S1 PACIS” Application:
Under the Windows/Start/Programs,
Select …/PACiS/Computer/MICOM S1 PACIS application.
Start the “PACiS FTPD” Application (for communication with C264):
Under Windows/Start/Programs,
Select …/PACiS/Computer/PACiS FTPD application.
FIGURE 3: MiCOM S1 PACiS EDITING ON LINE PARAMETERS
FIGURE 4: MiCOM S1 PACiS EDITING ON LINE PARAMETERS
Figures 38 & 39 show the global C264 parameters in Read Only mode. Editing of the
function can be done by cick edit on the parameters, as shown in below figures.
1.3.2.2 How to send ‘setting files’ to C264
FIGURE 5: MiCOM S1 PACiS - SET SETTINGS
FIGURE 6: MiCOM S1 PACiS - SET SETTINGS: GENERATION TYPE CHOICE
FIGURE 7: MiCOM S1 PACiS - SET SETTINGS: TRANSFERRING VALUES

1.3.2.3 How to navigate into MICOM S1 PACIS.
FIGURE 8: MiCOM S1 PACiS – HOW TO NAVIGATE - 1

1.3.2.4 How to edit online C264 values
FIGURE 12: MiCOM S1 PACiS – HOW TO EDIT VALUES – AR-PCCN
1.3.2.5 Edit AR-PCCN parameters

List of parameters can be modified:
Parameter Min Max Step

Numbers of fast cycle for earth fault 0 1 1
Numbers of slow cycle for earth fault 0 2 1
Numbers of fast cycle for phase fault 0 1 1
Numbers of slow cycle for phase fault 0 2 1
Reclaim time fast cycle (ms) 10000 15000 1000
Reclaim time slow cycle (ms) 3000 10000 1000
Reclaim time manual close (ms) 10000 20000 1000
Timer cycle fast earth (ms) 100 500 1
Timer cycle slow1 earth (ms) 10000 30000 1000
Timer cycle slow2 earth (ms) 10000 30000 1000
Timer cycle fast phase (ms) 100 500 1
Timer cycle slow1 phase (ms) 10000 30000 1000
Timer cycle slow2 phase (ms) 10000 30000 1000
FIGURE 13: MiCOM S1 PACiS – HOW TO EDIT VALUES – AR-PCCN
1.3.2.6 Edit AUTORECLOSER (TYPE 1) parameters


1st period triphased time (ms) 100 60000 10
2nd period triphased time (ms) 1000 3600000 10
3rd period triphased time (ms) 1000 3600000 1000
Reclaim delay time (ms) 1000 600000 1000
Inhibition delay (ms) 1000 3600000 1000
Unlock delay (ms) 1000 600000 1000
Manual close delay (ms) 1000 600000 1000
Parameter Value
Functioning mode (1 ph trip) 1P / 1P-3P / 1P-3P-3P / 1P-3P-3P-3P
Functioning mode (3 ph trip) 3P / 3P-3P / 3P-3P-3P / 3P-3P-3P-3P
FIGURE 14: MiCOM S1 PACiS – HOW TO EDIT VALUES – AR TYPE 1

1.3.2.7 Edit INTERNAL SYNCHROCHECK (TYPE 1) parameters

Schemes:
Parameter Value
Close with synchro: Coupling and locking YES / NO
Close with synchro: locking YES / NO
Close with synchro: Line Dead and Bus Live YES / NO
Close with synchro: Line live and Bus Dead YES / NO
Close with synchro: Line Dead and Bus Dead YES / NO
Close : Locking YES / NO
Close: Line Dead and Bus Live YES / NO
Close: Line live and Bus Dead YES / NO
Close : Line Dead and Bus Dead YES / NO
Autorecloser Locking YES / NO
Autorecloser Line Dead and Bus Live YES / NO
Autorecloser Line live and Bus Dead YES / NO
Autorecloser Line Dead and Bus Dead YES / NO
FIGURE 15: MiCOM S1 PACiS – HOW TO EDIT VALUES – SYNCHROCHECK (TYPE 1) SCHEMES
Timings:

Parameters T1: 200 10000 20
Presence deltas test duration (ms)
Presence test duration (ms)
absence deltas test duration (ms)
Parameters Ta: 0 1000 10
close time of circuit breaker (ms)
Close with synchro scheme delay (ms) 1 3600 1
FIGURE 16: MiCOM S1 PACiS – HOW TO EDIT VALUES – SYNCHROCHECK (TYPE 1) TIMINGS
Thesholds:

Line voltage over threshold 0 100 1
Line voltage under threshold 0 100 1
Bus voltage overthreshold 0 100 1
Bus voltage underthreshold 0 100 1
Voltage delta threshold for locking 0 100 1
Minimum frequency for locking 45.5 59.5 0.1
Maximum frequency for locking 50.5 66.0 0.1
Frequency delta threshold for locking 0.02 0.1 0.01
Phase delta threshold for locking 0 90.0 1
FIGURE 17: MiCOM S1 PACiS – HOW TO EDIT VALUES – SYNCHROCHECK (TYPE 1) THRESHOLDS
1.3.2.8 Edit FBD Timer parameters

Editable parameters of FBD Timer:

FBD timer (Standard timer) (ms) 50 5000 5
FIGURE 18: MiCOM S1 PACiS – HOW TO EDIT VALUES – FBD TIMER
1.3.2.9 Edit FBD Boolean parameters
Editable parameters of Boolean:
Parameter Value
FBD Boolean True / Flase
FIGURE 19: MiCOM S1 PACiS – HOW TO EDIT VALUES – FBD BOOLEAN

1.3.2.10 Edit AVR parameters

AVR management:

AVR_state 0 1 1
AVR_mode 0 1 1
TAP management:

First tap delay (s) 10 70 5
Next tap delay (s) 2 30 2
First_tap_delay_bypass_delay (s) 20 120 10
Preset_tap_value 1 64 1
Preset_tap_delay (s) 0 10 1
Tcip_delay (s) 5 180 5
Tcip_end_delay (s) 1 120 1
Tap_changer_fault_delay (s) 60 600 10
Nb_tap_before_high 1 10 1
Nb_tap_before_low 1 10 1
Slipping_period (days) 1 120 1
Intermediate_position_active 0 1 1
Intermediate_tap_delay (s) 0 60 1
Intermediate_tap_value 1 64 1
Runaway_tap_delay (s) 0 60 1
Voltage:

voltage_presence (in Volts: % of Vn) 20 80 10
regulation_deadband (% of Vc) 0 4 0.25
abnormal_voltage (% of Vc) 2 11 1
abnormal_volt_pres_delay (s) 0 120 1
abnormal_voltage_delay_present (s) 20 600 10
abnormal_voltage_delay_missing (s) 0 600 1
Voltage_present_delay (s) 0 120 1
Voltage_missing_delay (s) 30 180 1
Compounding_activation 0 1 1
Compounding_method 0 1 1
Compound_A1 (in % of Vn/In) 0 60 0.5
Compound_B1 (in % of Vn/In) 0 60 0.5
Compound_A2 (in % of Vn/In) 0 60 0.5
Compound_B2 (in % of Vn/In) 0 60 0.5

Double_wound_voltage_diff (in % of Vn) 0 10 1
Voltage_correction (in % of Vn) -10 10 0.01
Voltage Target:

Remote_target_min_value (in % of Vn) 90 105 0.25
Remote_target_max_value (in % of Vn) 95 110 0.25
Remote_target_max_difference (Volts) 50 500 10
End_remote_target_delay (mn) 0 480 10
End_local_target_delay (mn) 3 10 1
Local_target_voltage (Volts) 90 110 0.25
Target_voltage1 (% of Vn) 88 112 0.1
Automatism:

Tap_changer_position_active 0 1 1
Tap_changer_fast_move_active 0 1 1
Overcurrent_detection_active 0 1 1
Overcurrent_threshold (in % of In) 50 500 10
Overcurrent_delay (s) 0 30 0.1
overvoltage_detection_active 0 1 1
overvoltage_threshold (in % of Vn) 100 130 1
Overvoltage_delay (s) 0 30 0.1
Undervoltage_detection_active 0 1 1
Undervoltage_threshold (in % of Vn) 50 100 1
Undervoltage_delay (s) 0 30 0.1
Tap_changer_blocking_allowed 0 1 1
Tap_changer_blocking_ delay (s) 0 300 0.1
1.3.3 Download a setting file from C264
FIGURE 14: MiCOM S1 PACiS – DOWNLOAD A SETTING FILE
The MiCOM S1 PACiS application needs to have a .VAL file located in the computer’s flash.
The “VAL” file is transferred via FTP.When data transmission is finished; the C264 sends an
acknowledgement message. This message give permission to read the .VAL received.
MiCOM S1 uses the .VAL file in order to get back and update the .SET values. (Only values
are used by MICOM S1).
MiCOM S1 PACiS downloads values from C264 using the function “Get Settings”.
NOTE: A register key is used for the settings. The name of the key is
“VERSION”.
It is located under HKEY_LOCAL_MACHINE\Software\PACIS\MICOM S1\Settings\
The value of this key can be 0 or 1. The default value is 1.
Following figures shows the how to get .VAL file from C264.
FIGURE 15: MiCOM S1 PACiS – GET SETTINGS - 1

FIGURE 16: MiCOM S1 PACiS – GET SETTINGS - 2
1.3.4 MiCOM S1 PACiS with different operating modes of the C264

Active mode
In this mode, the MiCOM S1 PACiS facilities are active.
Standby mode
In this mode, C264 is not operational.
The C264 is to deny the transfer of the setting file via MiCOM S1 PACiS application when it
is in standby mode.
NOTE: In redundancy mode (when C264 is redunded), Protection functions
are not allowed (-> No Settings).
Test mode
In this mode, the MiCOM S1 PACiS facilities are active.
Other mode
No possible operation.
1.3.5 MiCOM S1 PACiS acknowledge
Receipt value MiCOM S1 PACiS message

0 Setting done
1 Incorrect C264 DB Version revision
2 Number of protections incoherent with DB
3 No setting file in the C264
4 FTP server problem - Verify that the FTP client is launched and try
again
5 C264 internal error
6 C264 incorrect number
7 Setting impossible, command running
8 Error IED address
9 Incompatible data structure
10 IED setting failed
Receipt value MiCOM S1 PACiS message

11 Compatibility error between C264 and SCE
12 Number of columns of the .VAL file incorrect
13 Error: label too long
14 Error PROTECTIONS C264: Value not between MIN and MAX
15 Error ELECTRE d: Value not between MIN and MAX
16 Error FBD: Value not between MIN and MAX
17 Error ISAGRAF: Value not between MIN and MAX
18 Error AUTO RECLOSER: Value not between MIN and MAX
19 Error AUTO RECLOSER PCCN: Value not between MIN and MAX
20 Error SYNCHROCHECK: Value not between MIN and MAX
21 Error AVR: Value not between MIN and MAX
22 Error PROTECTIONS C264: Verification phase incorrect
23 Error ELECTRE d: Verification phase incorrect
24 Error FBD: Verification phase incorrect
25 Error ISAGRAF: Verification phase incorrect
26 Error AUTO RECLOSER: Verification phase incorrect
27 Error AUTO RECLOSER PCCN: Verification phase incorrect
28 Error SYNCHROCHECK: Verification phase incorrect
29 Error AVR: Verification phase incorrect
30 Error: File OK but a problem occured during file copy
31 Error: Setting file for CPU3 sent to a CPU2
32 Error in file checksum
33 Error: MiCOM S1 task not present
34 Error: Trip in progress
5. CHAPTER C264_ENCT_C40
3.4 Slave IEC 60870-5-101 profile

3.4.5 Application layer
Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used
exclusively in this companion standard.
Common address of ASDU
(system-specific parameter, all configurations that are used are to be marked ‘X’)
⌧ One octet ⌧ Two octets
Information object address

⌧ One octet ⌧ Structured
⌧ Two octets ⌧ Unstructured
⌧ Three octets
Cause of transmission
⌧ One octet ⌧ Two octets (with originator address)
Selection of standard ASDUs

Process information in monitor direction
(station-specific parameter, mark each type ID ‘X’ if it is only used in the standard direction,
‘R’ if only used in the reverse direction, and ‘B’ is used in both directions)
⌧ <1> := Single-point information M_SP_NA_1
⌧ <2> := Single-point information with time tag M_SP_TA_1
⌧ <3> := Double-point information M_DP_NA_1
⌧ <4> := Double-point information with time tag M_DP_TA_1
⌧ <5> := Step-position information M_ST_NA_1
⌧ <6> := Step-position information with time tag M_ST_TA_1
<7> := BitString of 32 bit M_BO_NA_1
<8> := BitString of 32 bit with time tag M_BO_TA_1
⌧ <9> := Measured value, normalized value M_ME_NA_1
⌧ <10> := Measured value, normalized value with time tag M_ME_TA_1
⌧ <11> := Measured value, scaled value M_ME_NB_1
⌧ <12> := Measured value, scaled value with time tag M_ME_TB_1

⌧ <13> := Measured value, short floating point value M_ME_NC_1
⌧ <14> := Measured value, short floating point value with time tag M_ME_TC_1
⌧ <15> := Integrated totals M_IT_NA_1
⌧ <16> := Integrated totals with time tag M_IT_TA_1
<17> := Event of protection equipment with time tag M_EP_TA_1
⌧ <18> := Packed start events of protection equipment with time tag M_EP_TB_1
⌧ <19> := Packed output circuit transmission of protection equipment with time tag M_EP_TC_1
<20> := Packed single-point information with status change detection M_PS_NA_1
<21> := Measured value, normalized value without quality descriptor M_ME_ND_1
⌧ <30> := Single-point information with time tag CP56Time2a M_SP_TB_1
⌧ <31> := Double-point information with time tag CP56Time2a M_DP_TB_1
⌧ <32> := Step-position information with time tag CP56Time2a M_ST_TB_1
<33> := Bistring of 32 bits with with time tag CP56Time2a M_BO_TB_1
⌧ <34> := Measured value, normalized with time tag CP56Time2a M_ME_TD_1
⌧ <35> := Measured value, scaled with time tag CP56Time2a M_ME_TE_1
⌧ <36> := Measured value, short floating point number with time tag CP56Time2a M_ME_TF_1
⌧ <37> := Integrated totals with time tag CP56Time2a M_IT_TB_1
<38> := Event of protection equipment with time tag CP56Time2a M_EP_TD_1
⌧ <39> := Packed start events of protection equipment with time tag CP56Time2a M_EP_TE_1
⌧ <40> := Packed output circuit information of protection equipment with time tag CP56Time2a M_EP_TF_1
Process information in control direction

⌧ <45> := Single command C_SC_NA_1
⌧ <46> := Double command C_DC_NA_1
⌧ <47> := Regulating step command C_RC_NA_1
⌧ <48> := Set point command, normalized value C_SE_NA_1
⌧ <49> := Set point command, scaled value C_SE_NB_1
⌧ <50> := Set point command, short floating point value C_SE_NC_1
<51> := BitString of 32 bits C_BO_NA_1

System information in monitor direction

⌧ <70> := End of initialisation M_EI_NA_1
System information in control direction

⌧ <100> := Interrogation command C_IC_NA_1
⌧ <101> := Counter Interrogation Command C_CI_NA_1
<102> := Read command C_RD_NA_1
⌧ <103> := Clock synchronisation command C_CS_NA_1
⌧ <104> := Test command C_TS_NB_1
<105> := Reset process command C_RP_NC_1
⌧ <106> := Delay acquisition command C_CD_NA_1
Parameter in control direction

<110> := Parameter of measured value, normalized value P_ME_NA_1
<111> := Parameter of measured value, scaled value P_ME_NB_1
<112> := Parameter of measured value, short floating point value P_ME_NC_1
<113> := Parameter activation P_AC_NA_1
File transfer
⌧ <120> := File ready F_FR_NA_1
⌧ <121> := Section ready F_SR_NA_1
⌧ <122> := Call directory, select file, call file, call section F_SC_NA_1
⌧ <123> := Last section, last segment F_LS_NA_1
⌧ <124> := Ack file, ack section F_AF_NA_1
⌧ <125> := Segment F_SG_NA_1
⌧ <126> := Directory F_DR_TA_1
Special use (private range)

⌧ <136> := Database version M_DB_NA_1
⌧ <137> := Regulating delay command C_RC_NB_1

Type identifier and cause of transmission assignments

(station-specific parameters)
Shaded boxes are not required.
Blank = function or ASDU is not used
Mark type identification/cause of transmission combinations:
‘X’ if used only in the standard direction
‘R’ if used only in the reverse direction
‘B’ if used in both directions
Type ID Cause of transmission

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X X
<2> M_SP_TA_1 X X X
<3> M_DP_NA_1 X X X X X
<4> M_DP_TA_1 X X X
<5> M_ST_NA_1 X X X X X
<6> M_ST_TA_1 X X X
<7> M_BO_NA_1
<8> M_BO_TA_1
<9> M_ME_NA_1 X X X X
<10> M_ME_TA_1 X
<11> M_ME_NB_1 X X X X
<12> M_ME_TB_1 X
<13> M_ME_NC_1 X X X X
<14> M_ME_TC_1 X
<15> M_IT_NA_1 X X
<16> M_IT_TA_1 X X
<17> M_EP_TA_1
<18> M_EP_TB_1 X
<19> M_EP_TC_1 X
<20> M_PS_NA_1
<21> M_ME_ND_1
<30> M_SP_TB_1 X X X
<31> M_DP_TB_1 X X X
<32> M_ST_TB_1 X X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1
<39> M_EP_TE_1 X
<40> M_EP_TF_1 X
<45> C_SC_NA_1 X X X X X X X X

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<46> C_DC_NA_1 X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X
<51> C_BO_NA_1 X
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1 X
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1 X X X X X
<105> C_RP_NA_1 X
<106> C_CD_NA_1 X X X
<110> P_ME_NA_1 X
<111> P_ME_NB_1 X
<112> P_ME_NC_1 X
<113> P_AC_NA_1 X
<120> F_FR_NA_1 X X X X
<121> F_SR_NA_1 X X X X
<122> F_SC_NA_1 X X X X
<123> F_LS_NA_1 X X X X
<124> F_AF_NA_1 X X X X
<125> F_SG_NA_1 X X X X
<126> F_DR_TA_1 X X
<136> M_DB_NA_1 X
<137> C_RC_NB_1 X X X X X X X X
3.5 Slave IEC 60870-5-104 profile

3.5.6 Application layer
Transmission mode for application data
Mode 1 (Least significant octet first), as defined in clause 4.10 of IEC 870-5-4, is used
exclusively in this companion standard.
Common address of ASDU

(System specific parameter)
The address field of the link and the common address of ASDU could have a different
number of bytes.
a One octet ` Two octets
Information object address

(System specific parameter)
a One octet ` Structured

a Two octets ` Unstructured
` Three octets
Cause of transmission
(System-specific parameter)
a One octet ` Two octets (with originator address)
Length of APDU
(System-specific parameter)
The maximum length of APDU is 253 (default). The maximum length may be reduced by the
system.
Configurable Maximum length of APDU per system
Selection of standard ASDUs

Process information in monitor direction
(Station-specific parameter)
` <1>: = Single-point information M-SP-NA-1

a <2>: = Single-point information with time tag M-SP-TA-1
` <3>: = Double-point information M-DP-NA-1
a <4>: = Double-point information with time tag M-DP-TA-1
` <5>: = Step position information M-ST-NA-1
a <6>: = Step position information with time tag M-ST-TA-1
a <7>: = Bit-string of 32 bit M-BO-NA-1
a <8>: = Bit-string of 32 bit with time tag M-BO-TA-1
` <9>: = Measured value, normalised value M-ME-NA-1
a <10>: = Measured value, normalised value with time tag M-ME-TA-1
` <11>: = Measured value, scaled value M-ME-NB-1
a <12>: = Measured value, scaled value with time tag M-ME-TB-1
` <13>: = Measured value, short floating point value M-ME-NC-1
a <14>: = Measured value, short floating point value with time tag M-ME-TC-1
` <15>: = Integrated totals M-IT-NA-1

a <16>: = Integrated totals with time tag M-IT-TA-1
a <17>: = Event of protection equipment with time tag M-EP-TA-1
a <18>: = Packed starts events of protection equipment with time tag M-EP-TB-1
a <19>: = Packed output circuit information of protection equipment M-EP-TC-1
with time tag
a <20>: = Packed single-point information with status change detection M-PS-NA-1
a <21>: = Measured value, normalised value without quality M-ME-ND-1
descriptor
Process information in monitor direction with the Extension of time tag

(Station-specific parameter)
` <30>: = Single-point information with time tag CP56Time2a M-SP-TB-1

` <31>: = Double-point information with time tag CP56Time2a M-DP-TB-1
` <32>: = Step position information with time tag CP56Time2a M-ST-TB-1
a <33>: = Bit-string of 32 bit with time tag CP56Time2a M-BO-TB-1
` <34>: = Measured value, normalised value with time tag M-ME-TD-1
CP56Time2a
` <35>: = Measured value, scaled value with time tag CP56Time2a M-ME-TE-1
` <36>: = Measured value, short floating point value, time tag CP56Time2a M-ME-TF-1
` <37>: = Integrated totals with time tag CP56Time2a M-IT-TB-1
a <38>: = Event of protection equipment with time tag CP56Time2a M-EP-TD-1
` <39>: = Packed start event of protection equipment, time tag M-EP-TE-1
CP56Time2a
` <40>: = Packed output circuit information of protection equipment M-EP-TF-1
with time tag CP56Time2a
Process information in control direction

(station specific parameter)
` <45>: = Single command C-SC-NA-1

` <46>: = Double command C-DC-NA-1
` <47>: = Regulating step command C-RC-NA-1
` <48>: = Set point command normalised value C-SE-NA-1
` <49>: = Set point command scaled value C-SE-NB-1
` <50>: = Set point command, short floating point value C-SE-NC-1
a <51>: = Bit-string of 32 bit C-BO-NA-1
` <58>: = Single command with time tag CP56Time2a C_SC_TA_1
` <59>: = Double command with time tag CP56Time2a C_DC_TA_1
` <60>: = Regulating step command with time tag CP56Time2a C_RC_TA_1
` <61>: = Set point command normalized value with time tag CP56Time2a C_SE_TA_1
` <62>: = Set point command scaled value with time tag C_SE_TB_1
CP56Time2a
` <63>: = Set point command short floating point value with time tag C_SE_TC_1
CP56Time2a
a <64>: = Bitstring of 32 bits with time tag CP56Time2a C_BO_TA_1
NOTE: Time tag command (ASDU 58 to 63) are managed as standard

command (ASDU 45 to 50), i.e. the time tag is not used.
System information in monitor direction
` <70>: = End of initialisation M-EI-NA-1
System information in control direction

(station-specific parameter)
` <100>: = Interrogation commands C-IC-NA-1

` <101>: = Counter interrogation command C-CI-NA-1
a <102>: = Read command C-RD-NA-1
` <103>: = Clock synchronisation command C-CS-NA-1
a <104>: = Test command C-TS-NA-1
a <105>: = Reset process command C-RP-NA-1
a <106>: = Delay acquisition command C-CD-NA-1
` <107>: = Test command with time tag CP56time2a C-TS-TA-1
Parameter in control direction

a <110>: = Parameter of measured value, normalised value P-ME-NA-1

a <111>: = Parameter of measured value, scaled value P-ME-NB-1
a <112>: = Parameter of measured value, short floating point value P-ME-NC-1
a <113>: = Parameter activation P-AC-NA-1
File transfer
` <120>: = File ready F-FR-NA-1

` <121>: = Section ready F-SR-NA-1
` <122>: = Call directory, select file, call file, call section F-SC-NA-1
` <123>: = Last section, last segment F-LS-NA-1
` <124>: = Ack file, ack section F-AF-NA-1
` <125>: = Segment F-SG-NA-1
` <126>: = Directory F-DR-TA-1
File transfer is only implemented in computer gateway.
Special use
(private range)
` <136>: = Data base version M-DB-NA-1

` <137>: = Regulating delay command C-RC-NB-1
` <138>: = Regulating delay command with time tag CP56Time2a C-RC-TB-1
Type identifier and cause of transmission assignments

(station specific parameters)
X Mark type identification/cause of transmission combinations: ‘X’ if used

Shaded boxes are not required
Blank = function or ASDU is not used
. Required in 1995 standard, suppressed in 2000.

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<1> M_SP_NA_1 X X X X X
<2> M_SP_TA_1
<3> M_DP_NA_1 X X X X X
<4> M_DP_TA_1 .
<5> M_ST_NA_1 X X X X X
<6> M_ST_TA_1 .
<7> M_BO_NA_1
<8> M_BO_TA_1
<9> M_ME_NA_1 X X X X
<10> M_ME_TA_1
<11> M_ME_NB_1 X X X X
<12> M_ME_TB_1
<13> M_ME_NC_1 X X X X
<14> M_ME_TC_1
<15> M_IT_NA_1 X X
<16> M_IT_TA_1
<17> M_EP_TA_1
<18> M_EP_TB_1
<19> M_EP_TC_1
<20> M_PS_NA_1
<21> M_ME_ND_1
<30> M_SP_TB_1 X X X
<31> M_DP_TB_1 X X X
<32> M_ST_TB_1 X X X
<33> M_BO_TB_1
<34> M_ME_TD_1 X
<35> M_ME_TE_1 X
<36> M_ME_TF_1 X
<37> M_IT_TB_1 X X
<38> M_EP_TD_1
<39> M_EP_TE_1 X
<40> M_EP_TF_1 X
<45> C_SC_NA_1 X X X X X X X X
<46> C_DC_NA_1 X X X X X X X X
<47> C_RC_NA_1 X X X X X X X X
<48> C_SE_NA_1 X X X X X X X X
<49> C_SE_NB_1 X X X X X X X X
<50> C_SE_NC_1 X X X X X X X X

20 37
1 2 3 4 5 6 7 8 9 10 11 12 13 to to 44 45 46 47
36 41
<51> C_BO_NA_1
<58> C_SC_TA_1 X X X X X X X X
<59> C_DC_TA_1 X X X X X X X X
<60> C_RC_TA_1 X X X X X X X X
<61> C_SE_TA_1 X X X X X X X X
<62> C_SE_TB_1 X X X X X X X X
<63> C_SE_TC_1 X X X X X X X X
<64> C_BO_TA_1
<70> M_EI_NA_1 X
<100> C_IC_NA_1 X X X X X X X X
<101> C_CI_NA_1 X X X X X X
<102> C_RD_NA_1
<103> C_CS_NA_1 X X X X X
<104> C_TS_NA_1
<105> C_RP_NA_1
<106> C_CD_NA_1
<107> C_TS_TA_1 X X X
<110> P_ME_NA_1
<111> P_ME_NB_1
<112> P_ME_NC_1
<113> P_AC_NA_1
<120> F_FR_NA_1 X X
<121> F_SR_NA_1 X X
<122> F_SC_NA_1 X X X
<123> F_LS_NA_1 X X
<124> F_AF_NA_1 X X
<125> F_SG_NA_1 X X
<126> F_DR_TA_1 X X
<136> M_DB_NA_1
<137> C_RC_NB_1 X X X X X X X X
<138> C_RC_TB_1 X X X X X X X X
• COT <45>:= Unknown Cause of Transmission

4.3 MODBUS communication

4.3.5.2 Time synchronisation

Preliminary remark: All the devices connected to a given network must have the same
synchronisation procedure (address and time and date format)
because the synchronisation is performed through a broadcast frame.
There are will be four types of synchronisation depending on a configuration parameter:
• No synchronisation
• Schneider Electric synchronisation: date and time conform to the inverted IEC 870-5-4
CP56Time2a format and is set at address 800h
• SEPAM synchronisation: date and time conform to the SEPAM (Merlin Gerin)
documentation (SEPAM1000+S20, SEPAM1000+S40, PM500, PM650, SEPAM2000)
• Flexgate synchronisation: date and time conform to the Flexgate (ABB) documentation
No calculation of the transmission delay is performed.
4.5.2.1 Input
ASDU Data Note

1 Dated Digital input (absolute dating)Control Treated
acknowledgement
2 Dated Digital input (relative dating) Treated
3 Measurement Treated
4 Measurement: Default position Treated
5 Identification Not treated
6 Time synchronisation acknowledgement Treated
8 End of GI Treated
9 Measurement Treated
10 General Data Treated (some
measurements only)
11 General Identification Not treated
17 Measurement Reg D only
23 … 31 Disturbance file management Treated
45 Ack of Single Command MiCOM Px3x only
46 Ack of Double Command MiCOM Px3x only
49 Analog protection signalOnly adress 0 which is MiCOM Px3x only
DVICE: Device type
65 Single Point MiCOM Px3x only
66 Single Point with Time Tag MiCOM Px3x only
67 Double Point MiCOM Px3x only
68 Double Point with Time Tag MiCOM Px3x only
71 BitString 32 Bit without time tag –couple FUN/TYP MiCOM Px3x only
computed:
F8h / 70h: State of the IEDF8h / 74h: Request
Station Interlock
ASDU Data Note

72 BitString 32 Bit with time tag – see ASDU 71 MiCOM Px3x only
73 Measurement, Normalised value MiCOM Px3x only
77 Measurement MiCOM Px3x only
79 Energy Counter MiCOM Px3x only
4.5.2.2 Output
ASDU Data Note

6 Time synchronisation Treated
7 Request a GI Treated
20 Command Treated
21 General Data Treated (some
measurements only)
23 … 31 Disturbance file management Treated
45 Single Command MiCOM Px3x only
46 Double Command MiCOM Px3x only
140 Read protection parameter MiCOM Px3x only
Only adress 0 which is DVICE: Device type
144 Setpoint Reg D only
6. CHAPTER C264_ENTD_C41
4.3.3 AIU211
The AIU211 board provides 8 isolated and insulated analogue inputs. It means there is no
common point between two analogues. All 8 analogue inputs are separated from each other.
Each AI can be configured in voltage or current range individually as specified in the table
below:
Type Ranges
Current input range ±1mA
±5 mA
±10 mA
±20 mA
4-20 mA
Sampling period 100 ms
Accuracy 0,1% full scale at 25°C
AD conversion 16 bits (15bits+sign)
Common mode rejection ratio (CMMR) > 100dB
Serial mode rejection ratio (SMMR) > 40dB
Input impedance for current inputs 75 Ω
Temperature drift: up to 30ppm/°C.

The ranges are defined during the configuration phase.
The current/voltage selection is done by choosing the input number of the connector.
A maximum of 6 AIU boards (including AIU201, AIU210 and AIU211) can be installed inside
a C264 rack.
5.2 Power supply
The BIU241 board burden on the internal 5V bus is 1,25W. This takes into account
watchdog, redundancy relays and communication ports.
The efficiency of the power supply is 78%.
NOTE: There is a peak current during the C264 start: the peak current can
reach 6,2 A during the first 50 milliseconds (measured on the BIU241-
A03 board with source in 125 VDC).
7. CHAPTER C264_ENMF_C40
3. THE EMBEDDED MAINTENANCE WEB-SERVER

The Maintenance Web server is only embedded in a CPU270 (also named CPU3) board.
This server can be accessed via the Internet Network with a standard web browser (Internet
Explorer 5.0 minimum or Mozilla Firefox 1.5 minimum).
An URL is defined to access this web browser: http://ip_address/fs/index.htm. Operator has
to know the IP address of the c264 webserver to establish the link.
Two level of access rights are defined depending on User name and associated password
according to the following table:
User name password Access rights

level1 level1 Maintenance data
level2 level2 Maintenance data and upload files
When operator connects to the webserver the following dialog box is displayed.
FIGURE 6: THE LOGIN DIALOG BOX

After correct name and password are entered the home page is displayed. The user can
choose the language (English / French / Deutch / Spanish) then select the information to be
displayed.
FIGURE 7: WEBSERVER HOME PAGE

8. CHAPTER C264_ENFT_C40
7.1.4.8 Homing
Homing is a facility which taps transformers such that their open circuit terminal volts follows
the volts on the busbars that they are selected to within 3% of the busbar voltage when the
mode of this busbar is In automatic control.
Homing is only able if there is at least one transformer connected on the corresponding
busbar and if transformer busbar disconnector is closed and LV circuit breaker open.
Homing is disabled while the busbar voltage is less than Umin (80% of nominal voltage).
If a transformer is under Homing Mode, a manual control is not accepted.
If (and only) a fault on the Tap Changer remains active, the transformer remains OUT of
automatic control. As a consequence, homing ceases as lons as the Tap Changer is faulty
and until the operator selects "Clear AVR faults".
Time out T3 is used for the first tap in the homing mode.
Time out T4 is used between successive taps.

9.1.2.1 Fast Waveform Recording
The inputs for the fast waveform records are up to 4 CT samples and 4 VT samples, and the
values of the selected digital inputs and outputs. Up to 128 digital channels may be captured.
The choice of selected inputs/outputs is defined in configuration.
The waveform recorder provides up to 8 analogue measurements and up to 128 digital
channels for extraction by a remote device.
A maximum of 480 cycles ( 9,6 seconds at 50 Hz) of measurements samples, with
32 samples per cycle, can be stored, divided in 1, 2, 4 or 8 files saved in flash disk.
A timer channel is also required to provide accurate timing information for each sample. The
delay between each sample is assumed constant over a single cycle.
Number of Files Number of cycles

8 60
4 120
2 240
1 480
The waveform recorder can be triggered by the following events, each of which is user
configurable:
• Changes in state of binary inputs (SP, DP, MP, SI or Groups
• Changes in state of digital outputs
• Measurement threshold violations
• Operator request
Only one re-trig is allowed: it means that a new trigger can only be accepted after the end of
recording of the current waveform.
Waveform records are available in COMTRADE 2001 format.
NOTE: The trigerring is available only from a state/value with VALID quality
(ex: SET/REST; OPEN/CLOSE) to a state/value with VALID quality.
9.1.2.2 Slow Waveform Recording

The inputs for the slow waveform records are:
• analogue values coming from CT VT calculation (RMS values)
• analogue values coming from AIU boards
• Digital inputs
• Digital outputs
The slow waveform manages up to 24 analogue and 48 digital values.
Data from CT/VT can be chosen among:
• RMS Values of phase voltage
• RMS values of busbar voltage
• RMS values of phase current
• RMS values of residual voltage and current
• Fundamental sequence components
• Active Power
• Reactive Power
• Apparent Power
• Frequency
• Harmonics levels
MiCOM C264/C264C stores at maximum 5000 integrated values as follow:
Number of Files Number of integrated values

1 5000
2 2500
5 1000
10 500
20 250
50 100
The integrated value has duration up to one hour. It is defined in configuration.

For analogue, the stored value is the average value during integrated period.
For digital, the stored value depends also on the average.
If average value > x then the stored value is 1 else it is 0, x is defined in configuration and it
is a value between 0.1 and 0.9. The slow waveform recorder can be triggered by the
following events, each of which is user configurable:
• Changes in state of binary inputs (SP, DP, MP, SI or Groups)
• Changes in state of digital outputs
• Measurement threshold violations
• Operator request
• Periodically (i.e. every day at 00h00)

NOTE: The trigerring is available only from a state/value with VALID quality
(ex: SET/REST; OPEN/CLOSE) to a state/value with VALID quality.
9. CHAPTER C264_ENHI_C40
2.3 Configuration Data

The behaviour of the free LEDs is defined in the computer DataBase.
When using a Simple DHMI, the 12 free LEDs give the status of the associated BI. Each BI
state is displayed using the ON / OFF / BLINKING led state (defined in the DS).
When using a Full DHMI (with LCD), the 13 free LEDs can be configured to have 2 different
behaviours:
1. give the status of the associated BI. Each BI state is displayed using the ON / OFF /
BLINKING led state (same way as with a Simple DHMI),
2. provide a way to manage BIs as alarms.
This behaviour B is detailed hereafter:
• if the BI is “transient”:
− if the BI is SET, the associated LED is ON or Blinking Slow (depends of the DB),
− after pressing the ‘C’ button, the LED’s state becomes OFF (without any
password).
• if the BI is “permanent”:
− if the BI is SET, the associated LED is Blinking Slow,
− after pressing the ‘C’ button, the LED’s state becomes ON (without any
password),
− if the BI is RESET, the associated LED remains Blinking if the ‘C’ button has not
been pressed or is OFF if it has.
Remarks:
− The “C” button is used for the navigation in the menu tree. This feature remains and
so alarm acknowledgement will be not allowed from the menu tree.
− The alarm acknowledgement function is not available with the simple panel (no “C”
button available).
Phenomenon LED status Possible reason Way to solve

Functions as All LEDs are OFF The cable between Verify the connection
communication, CPU and GHU2xx, or between CPU or
automation, printing are GHU2xx itself is not GHU2xx.
well operating and the operational
If connection is OK
watch dog on BIU is
and the problem is
SET.
not already solved
then change the
GHU2xx board.
The supply is ON and All LEDs are OFF Problem with BIU Replace BIU board or
the watch dog on BIU board or CPU board CPU board.
is RESET.
Phenomenon LED status Possible reason Way to solve

C264 is not running or LED1 ON Incoherent database Download a coherent
not fully operational database
Hardware fault Go in Fault panel and
Board panel to
determine the faulty
board and change it.
C264 is not fully LED1 is blinking A IED is disconnected Go into IED panel to
operational determine the
disconnected IED and
verify the cable, the
BIU configuration, the
communication
parameters inside the
PACiS configurator,
the communication
parameters inside the
relay.
The printer is Go into Fault panel
disconnected and verify that paper
is available, the
printer is switch ON,
the printer cable.
A problem about clock Go into Fault panel
synchronisation and verify that the
external clock is
switch ON, the
external clock is
connected to the
antenna, the external
clock is connected to
the C264.
A problem about PLC Go into Fault panel
(ISaGRAF) and connect the
ISaGRAF workbench
to the C264. Verify
the behaviour of the
PLC.
The 12 other LED’s are freely configurable: they can be attached to a datapoint.
Furthermore, the datapoint state is displayed through a led state: on, off, slow blinking, fast
blinking.
For a Single Point, the Set / Reset / Invalid (i.e. all other states) can be attached to a led. For
a Double Point, the Open / Close / Invalid (i.e. all other states) can be attached to a led.
BLANK PAGE
Customer Care Centre
http://www.schneider-electric.com/CCC
© 2011 Schneider Electric. All rights reserved.
Schneider Electric
35 rue Joseph Monier
92506 Rueil-Malmaison
FRANCE
Phone: +33 (0) 1 41 29 70 00
Fax: +33 (0) 1 41 29 71 00
www.schneider-electric.com Publishing: Schneider Electric
Publication: C264/EN AD/C41 03/2011

Micom C264/C264C: Bay Computer

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Micom C264/C264C: Bay Computer

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Micom C264/C264C: Bay Computer

Uploaded by

Copyright:

Available Formats

MiCOM C264/C264C

MiCOM C264/C264C Page 1/74

1. SCOPE OF THE DOCUMENT 3

Page 2/74 MiCOM C264/C264C

MiCOM C264/C264C Page 3/74

1. SCOPE OF THE DOCUMENT

Page 4/74 MiCOM C264/C264C

7. MiCOM C264 SOFTWARE INSTALLATION

C264 release label Bootrom version label

MiCOM C264/C264C Page 5/74

FIGURE 1: CPU2 (CPU260) - BOOTROM VERSION AT HYPERTERMINAL

7.6.1.1.2 Using the CMT

Page 6/74 MiCOM C264/C264C

FIGURE 2: CPU2 (CPU260) - BOOT PARAMETERS AT CMT TOOL

4. Click menu button "Reboot computer"

FIGURE 3: CPU2 - CONFIRM REBOOT

5. Click "YES" and wait for computer reboot ends

MiCOM C264/C264C Page 7/74

FIGURE 4: CPU2 (CPU260) - BOOTROM VERSION AT CMT TOOL

7.6.1.1.3 Label on the CPU Board

FIGURE 5: CPU260 - BOOTROM VERSION ON CPU BOARD

Page 8/74 MiCOM C264/C264C

7.6.1.2 Procedure to Upgrade Software

• Select the computer in “computer’s list” menu

• Click on “Parameters” button

• Select “Bootprom boot” and validate by clicking on “Set boot parameter”

FIGURE 6: CPU260 - BOOT PARAMETERS AT CMT TOOL

• Click on “Reboot computer” button

• Click “YES” and wait for computer reboot ends

MiCOM C264/C264C Page 9/74

7.6.1.2.3 Update "bootrom"

• Then select the sub directory specific of you board type:

• Finally select the file bootrom.flh.

FIGURE 7: CPU2 (CPU260) - UPDATE BOOTROM

• Click on "Update bootrom"

FIGURE 8: STOP COMPUTER

• Bypass this warning Click on "OK"

Page 10/74 MiCOM C264/C264C

FIGURE 9: CPU2 (CPU260) - UPDATE BOOTROM CONFIRM

Update bootrom progress

FIGURE 10: CPU2 (CPU260) - UPDATE BOOTROM: OK

Wait until the end of the update = Update bootrom: OK

• Reboot computer (Click menu button "Reboot computer")

MiCOM C264/C264C Page 11/74

7.6.1.2.4 Erase and Format FLASH

• After reboot complete, select the computer.

• In "File explorer" menu click on button "Flash format"

FIGURE 11: CPU2 (CPU260) - ERASE AND FORMAT FLASH

• Bypass this security message: Click on "OK"

Page 12/74 MiCOM C264/C264C

FIGURE 12: CONFIRM ERASE AND FORMAT FLASH

Flash formatting progress:

• Reboot computer (Click menu button "Reboot computer")

MiCOM C264/C264C Page 13/74

FIGURE 13: CPU2 (CPU260) - BOOT INSTALL

• Click on "Start: bootInstall"

• Bypass the security if necessary: Click "NO"