Mico MC 212 User Guide

MiCOM C212
ioBrick Digital I/O Controller

User Manual
AVAILABLE DOCUMENTATION
C212UG004
MiCOM C212 User Manual
INSTALLATION AND MAINTENANCE

AREVA T&D products are designed for ease of installation and maintenance. As with any product
of this nature, installation and maintenance can present electrical hazards and should be
performed only by properly trained and qualified personnel. If the equipment is used in a manner
not specified by AREVA T&D, the protection provided by the equipment may be impaired.
WARRANTY AND ASSISTANCE

This product is warranted against defects in materials and workmanship for a period of thirty-six
(36) months from the date of their original shipment from the factory. Products repaired at the
factory are likewise warranted for eighteen (18) months from the date the repaired product is
shipped, or for the remainder of the product's original warranty, whichever is greater. Obligation
under this warranty is limited to repairing or replacing, at our designated facility, any part or parts
that our examination shows to be defective. Warranties only apply to products subject to normal
use and service. There are no warranties, obligations, liabilities for consequential damages, or
other liabilities on the part of AREVA T&D except this warranty covering the repair of defective
materials. The warranties of merchantability and fitness for a particular purpose are expressly
excluded.
For assistance, contact AREVA T&D at:
Telephone:
(610) 997-5100
Fax:
(610) 865-0340
Email:
info.bitronics@areva-td.com
Website:
www.areva-td.com
Shipping Address:
AREVA T&D
261 Brodhead Road
Bethlehem, PA 18017-8698
USA
COPYRIGHT NOTICE
This manual is copyrighted and all rights are reserved. The distribution and sale of this
manual is intended for the use of the original purchaser or his agents. This document
may not, in whole or part, be copied, photocopied, reproduced, translated or reduced to
any electronic medium or machine-readable form without prior consent of AREVA T&D,
except for use by the original purchaser.
The product described by this manual contains hardware and software that is protected
by copyrights owned by one or more of the following entities:
AREVA T&D Inc., 261 Brodhead Road, Bethlehem, PA 18017;
Triangle MicroWorks, Inc., 2213 Middlefield Court, Raleigh, NC 27615
TRADEMARKS
The following are trademarks or registered trademarks of AREVA T&D Inc.
AREVA T&D the AREVA logo
BiTRONICS
MiCOM
The following are trademarks or registered trademarks of the DNP User's Group:
DNP
DNP3
ii
SAFETY SECTION
This Safety Section should be read before commencing any work on the equipment.
Health and safety
The information in the Safety Section of the product documentation is intended to ensure that
products are properly installed and handled in order to maintain them in a safe condition. It is
assumed that everyone who will be associated with the equipment will be familiar with the
contents of the Safety Section.
Explanation of symbols and labels
The meaning of symbols and labels that may be used on the equipment or in the product
documentation is given below.
Installing, Commissioning and Servicing

Equipment connections
Personnel undertaking installation, commissioning or servicing work on this equipment should be
aware of the correct working procedures to ensure safety. The product documentation should be
consulted before installing, commissioning or servicing the equipment.
Terminals exposed during installation, commissioning and maintenance may present a hazardous
voltage unless the equipment is electrically isolated.
If there is unlocked access to the equipment, care should be taken by all personnel to avoid
electric shock or energy hazards.
iii
Before energizing the equipment, it must be grounded (earthed) using the protective ground
(earth) terminal, or the appropriate termination of the supply plug in the case of plug connected
equipment. Omitting or disconnecting the equipment ground (earth) may cause a safety hazard.
The recommended minimum ground (earth) wire size is 2.5 mm2 (#12 AWG), unless otherwise
stated in the technical data section of the product documentation.
Before energizing the equipment, the following should be checked:
Voltage rating and polarity
Integrity of connections
Protective fuse rating
Integrity of ground (earth) connection (where applicable)
Equipment operating conditions

The equipment should be operated within the specified electrical and environmental
limits.
Insulation and dielectric strength testing

Insulation testing may leave capacitors charged up to a hazardous voltage. At the end of each
part of the test, the voltage should be gradually reduced to zero, to discharge capacitors, before
the test leads are disconnected.
Installation and Removal
All Hazardous Voltages MUST be removed from the C212 before removing or installing.
Do not attempt to install or remove with signals connected.
Fiber optic communication
Where fiber optic communication devices are equipped, the light output of the transmitters or the
fiber cables must never be viewed directly. Optical power meters should be used to determine
the operation or signal level of the device.
Decommissioning and Disposal
1.
Decommissioning
The power supply circuit in the equipment may include capacitors across the supply or to
ground (earth). To avoid electric shock or energy hazards, after completely isolating the
supplies to the relay (both poles of any dc supply), the capacitors should be safely
discharged via the external terminals before decommissioning.
2.
Disposal
It is recommended that incineration or disposal to watercourses is avoided. Please
dispose of all electronic products in a safe manner.
iv
Manual Update History
Date
Author
Version
Description
Nov
2004
DEA
1.0
Original from Plymouth Systems material
Nov
2004
DEA
C212UG001
Added Hyper terminal instructions, safety

information
Nov
2004
DEA
C212UG002
Specifications modified per RSC
Feb
2005
DEA
C212UG003
Comments from RW Fisher added
Apr
2005
DEA
C212UG004
Production release: DNP over IP, TCP configuration,

ability to set DNP classes for data points (with
defaults), ability to disable unsolicited DNP
commands, DNP counters and freeze counters
Table of Contents
AVAILABLE DOCUMENTATION ....................................................................................... i
INSTALLATION AND MAINTENANCE.............................................................................. i
WARRANTY AND ASSISTANCE ...................................................................................... i
COPYRIGHT NOTICE ...................................................................................................... ii
TRADEMARKS ................................................................................................................. ii
SAFETY SECTION ...........................................................................................................iii
1.
Introduction.............................................................................................................. 1
1.1
Scope ................................................................................................................ 1
1.2
Overview ........................................................................................................... 1
1.3
Applications ....................................................................................................... 1
1.4
Features ............................................................................................................ 1
1.5
Definitions.......................................................................................................... 2
2.
Specifications .......................................................................................................... 3
2.1
Photo ................................................................................................................. 6
3.
Technical Overview ................................................................................................. 7
3.1
CPU and Memory.............................................................................................. 8
3.2
Contact Input Subsystem .................................................................................. 8
3.3
Output Subsystem............................................................................................. 8
3.4
Communications Subsystem............................................................................. 9
3.5
Universal Power Supply .................................................................................... 9
3.6
Packaging and Environmental........................................................................... 9
3.7
Standards ........................................................................................................ 10
3.8
Software .......................................................................................................... 10
4.
Installation ............................................................................................................. 11
4.1
Features to consider when installing the MiCOM C212 .................................. 11
4.2
Power & Digital I/O Connections ..................................................................... 12
4.2.1 Grounding.................................................................................................... 13
4.2.2 Power Connections ..................................................................................... 13
4.2.3 Contact Input Connections .......................................................................... 14
4.2.4 Relay Output Connections........................................................................... 14
4.3
Communications Connections......................................................................... 15
4.3.1 Ethernet Connections .................................................................................. 15
4.3.2 Serial Port RS-232 Connections.................................................................. 16
4.3.3 Serial Port RS-485 Connections.................................................................. 18
4.3.4 IRIG-B Input Port ......................................................................................... 19
5.
Software Configuration.......................................................................................... 20
5.1
Full Configuration via the Serial Port............................................................... 20
5.1.1 Connection: ................................................................................................. 20
5.1.2 Prompts: ...................................................................................................... 23
5.1.3 Commands: ................................................................................................. 24
5.1.4 HELP Command.......................................................................................... 26
5.1.5 LOGIN Command........................................................................................ 26
5.1.6 LOGOUT Command.................................................................................... 28
5.1.7 SAVE Command ......................................................................................... 29
5.1.8 QUIT Command .......................................................................................... 30
5.1.9 DNP Command ........................................................................................... 30
5.1.10
COM1 Command..................................................................................... 33
5.1.11
COM1 RS-485 Prompts........................................................................... 34
vi
5.1.12
COM1 RS-232 Prompts........................................................................... 37
5.1.13
IPADDRESS Command .......................................................................... 39
5.1.14
TCP Configuration ................................................................................... 40
5.1.15
UDP Command ....................................................................................... 41
5.1.16
DEFAULTS Command ............................................................................ 42
5.1.17
PASSWORD Command .......................................................................... 43
5.1.18
DATE Command ..................................................................................... 43
5.1.19
TIME Command ...................................................................................... 44
5.1.20
AUTOLOGOFF Command ...................................................................... 44
5.1.21
DEVICENAME Command ....................................................................... 44
5.1.22
SUBSTATION Command ........................................................................ 44
5.1.23
INPUT Command .................................................................................... 45
5.1.24
OUTPUT Command ................................................................................ 46
5.1.25
VERSION Report..................................................................................... 48
5.2
Limited Configuration via the Diagnostic Switch ............................................. 50
5.2.1 LED test....................................................................................................... 50
5.2.2 Enter Programming mode ........................................................................... 51
5.2.3 LED patterns during programming using the diagnostic switch................... 51
6.
DNP3.0 Protocol.................................................................................................... 55
7.
Maintenance.......................................................................................................... 56
7.1
Troubleshooting............................................................................................... 56
7.2
Field Repair ..................................................................................................... 56
7.3
Firmware program upgrade............................................................................. 56
8.
MiCOM C212 ioBrick Photos................................................................................. 58
8.1
CPU/MEMORY/COMM BOARD ..................................................................... 58
8.2
POWER/IO BOARD ........................................................................................ 59
9.
Appendix ............................................................................................................... 60
9.1
Firmware Version History ................................................................................ 60
Figure 1 - ioBrick Functional Block Diagram ..................................................................... 7

Figure 2 Board Interconnection Diagram ....................................................................... 8
Figure 3 - Switched-Positive Connections, Bussed Contacts ......................................... 12
Figure 4 - Switched-Positive Connections, Isolated Contacts......................................... 12
Figure 5 - Switched-Negative Connections, Bussed Contacts........................................ 13
Figure 6 - Switched-Negative Connections, Isolated Contacts ....................................... 13
Figure 7 - Communications Overview ............................................................................. 15
Figure 8 - RS-232 Connection to a Modem or Radio (DCE)........................................... 16
Figure 9 - RS-232 Connection to Another IED (DTE) ..................................................... 17
Figure 10 RS-485 Connection to Other IEDs............................................................... 18
Figure 11 - IRIG Daisy Chain Wiring............................................................................... 19
vii
1.Introduction
1.1 Scope
This document provides the basic product information necessary to install, commission,
and maintain the MiCOM C212 ioBrick Controller.
1.2 Overview
MiCOM C212 ioBrick is a compact Intelligent Electronic Device (IED), providing 16
digital inputs and 4 relay outputs. It is suitable for distributing digital I/O throughout a
substation, and expanding existing Remote Terminal Units (RTU) or Distributed Control
Systems (DCS). The design emphasizes rugged construction, reliable operation, and
low installed cost. Its simple configuration, universal power supply, Ethernet
communications, and small size make it ideal for a wide range of utility applications.
1.3 Applications
The ioBrick is designed to mount in, and to monitor and control indoor or outdoor electric
power apparatus such as:
Circuit breakers
Control switches
Reclosers
Pole-top switches
Transformers
Capacitor banks
1.4 Features
Minimal package footprint facilitates application in limited space. If rack mounting, two
will fit across a 19 rack space.
Low power consumption, wide temperature range, and surge suppression accommodate
application environments.
Wide input ranges for power supply and digital inputs eliminate ordering and sparing
different models for different voltages and polarities.
Form C output relays provide both normally open and normally closed contacts, and are
suitable for driving breaker coils directly.
Plug-in terminal blocks, accepting up to 12AWG wiring, facilitate installation and
replacement. Field wiring may be terminated and dressed in advance.
Entire unit is a low-cost, replaceable module, simplifying maintenance. Numerous LEDs
and diagnostics simplify verification and troubleshooting.
Simplified user configuration via serial or Ethernet ports. No physical jumpers or
adjustments.
Serial port is optically isolated, for reliability, and user-configurable for either RS-232 or
RS-485 operation. Standard protocol is DNP 3.0.
Ethernet options support DNP over TCP/IP or UDP. Either twisted-pair (10/100BaseTX) or fiber optic (100Base-FX or 10Base-FL) Ethernet may be used.
C212UG004 April 2005
-1-
Copyright 2005 AREVA T&D Inc.
Optically isolated synchronization port accepts demodulated IRIG-B time code

information from third-party clock receivers.
32-bit ARM7 processor and over 10Mbytes of memory assure power and flexibility to
accommodate complex application requirements, and guard against obsolescence.
1.5 Definitions
The following definitions apply to the Specification table in Section 2:
Installation Category (Overvoltage Category) III: Distribution Level, fixed installation,
with smaller transient overvoltages than those at the primary supply level, overhead
lines, cable systems, etc.
Pollution: Any degree of foreign matter, solid, liquid or gaseous that can result in a
reduction of electric strength or surface resistivity of the insulation.
Pollution Degree 2: Only non-conductive pollution occurs except that occasionally a
temporary conductivity caused by condensation is to be expected.
-2-
2. Specifications
Parameter
Value
Input Power
Input Power rating
12W (max), 12VA (max)
Nominal
24-250Vdc, 69-240Vac (50-60Hz)
Input Range
20-300Vdc, 55-275Vac (45-65Hz)
Contact Inputs
Configuration
Contact Input Range
16, individually isolated (ANSI/IEEE C37.90.1: 1989)

20 to 150Vdc (Input Resistance 32K, Threshold Voltage
16V)
Relay Outputs
Configuration
Output Contact Rating
4 relays, single dry form C output per relay

10A @ 30Vdc, 1/2A @ 125Vdc, resistive (see Note1)
Serial Comm. Port

Configuration
Interface Compatibility
Data Compatibility
Data Rate
Single port, optically isolated

RS-232 or RS-485, Software Selectable
Standard UART
1200 to 115.2kbps, NRZ
IRIG Port
Configuration
Data Compatibility
Single port, optically isolated

Demodulated (TTL) IRIG-B
Ethernet Port
Configuration
Optional Compatibilities
Single logical port, three physical interface options

100Base-TX (Category 5 UTP, RJ-45 Conn.)
100Base-FX (Multimode Fiber, ST Conn.)
10Base-FL (Multimode Fiber, ST Conn.)
-3-
Physical
Case including mounting
tabs
Aluminum, 9.0 W x 7.0 D x 2.75
Field Wire Terminations
Plug-in, wire-clamping terminal block, #12AWG max.
Field Wire Terminations

Torque Ratings
0.5 - 0.6 Nm
-4-
Parameter
Value
Environment
Operating Temperature
Relative Humidity
Surge Withstand
Capability
Altitude
Intended Use
-40C to 85C
0-95% non-condensing
ANSI/IEEE C37.90.1: 1989
Up to and including 2000m above sea level.

Indoor use; Indoor/Outdoor use when mounted in an
appropriately rated protective enclosure to NEMA or IP
protection classifications, as required for the installation.
Installation Category
IC III (Distribution Level) Refer to definitions (Section 1.5)
Pollution Degree
Pollution Degree 2. Refer to definitions (Section 1.5)
Enclosure Protection
Case IP20 to IEC60529:1989
Note 1: A separate source of wetting voltage is recommended for applications requiring

total relay current in excess of 1/2A
-5-
2.1 Photo
-6-
3. Technical Overview
The ioBrick is comprised of two PC boards, with its circuitry partitioned as shown in
Figure 1, and described in the subsequent subsections. The main connection between
the two boards is a 34-wire ribbon cable, carrying 5 Volt power and the digital I/O
signals, which are connected to I/O port pins on the LH79520 Microcontroller. There is
also a 2-wire cable carrying isolated 15 Volt power to the serial port.
Figure 1 - ioBrick Functional Block Diagram
Iso +15Vdc
Serial
Port
TB
XTAL
Power
Monitor
JTAG
LEDs
TB
LEDs
Address Bus
Serial Ports
OptoIsolators
IRIG
Port
XTAL
RS-232/
485 XCVR
OptoIsolator
LED
LH79520
SOC
FLASH
Memory
Ethernet
Controller
SDRAM
Data Bus
I/O Ports
LEDs
LEDs
Regulator
Regulator
+3.3Vdc
Ethernet
XFMRs
RJ45
Media
Adapter
LEDs
Fiber
XCVR
ST
Conn.
Copper
Ethernet
Fiber
Ethernet
+1.8Vdc
CPU/Mem/Comm Board
Power & Digital I/O Board

Relay Drivers
+5.0Vdc
Relays
Opto-Isolators
DC/DC
Converter
Surge
Suppression
Surge
Suppression
Surge
Suppression
TB
TB
TB
4 Form C
Outputs
16 Contact
Inputs
Wide Range
AC/DC Power Input
-7-
Iso +15Vdc
MiCOM C212 ioBrick
Figure 2 Board Interconnection Diagram
727 CPU & Comm Board

S4
34-wire
Ribbon
Cable
2-
w
ire
Po
w
er
C
ab
l
S1
S7
S10
728 Power & I/O Board
3.1 CPU and Memory

The CPU is a 32-bit Sharp microcontroller, with an ARM7 core and a watchdog circuit
that allows monitoring of each software process. Diagnostic LEDs and a header for
board checkout are provided. Program and configuration are downloadable, and stored
in a 2Mbyte, non-volatile, flash memory. 8M bytes of random access memory are also
included for dynamic data storage by the program.
3.2 Contact Input Subsystem

The contact input subsystem consists of 16 optically isolated inputs, operating from an
externally supplied wetting voltage of 24Vdc to 125Vdc, +/-15%. The equipped
redundant power input terminal block may be used to distribute input power to use as
the wetting voltage. Multiple change detect (MCD) and 1 millisecond resolution SOE is
supported, with a sampling rate of 2 kHz to ensure time-tag accuracy. Each input has an
associated LED to indicate contact status.
3.3 Output Subsystem

The output subsystem consists of 4 relay outputs. Each output relay is rated to trip
breakers without interposing relays. The four relays are provided with Form C contacts
-8-
so that they can be wired to default to either the normally open or normally closed
position when the system powers up. All relays are de-energized on system power-up or
reset. Each output relay has an associated LED to indicate when its coil is energized.
Both latch and timed pulse control commands can be issued to the output relays from
DNP3.0.
3.4 Communications Subsystem

Ethernet Options:
Ethernet 10/100Base-TX with an RJ-45 connector.
Ethernet 10Base-FL with ST fiber connectors
Ethernet 100BaseFX with ST fiber connectors
All Ethernet options support DNP 3.0 slave protocol over TCP/IP or UDP. The IP
address is configurable. Factory default is 192.168.0.254
Serial Port:
A serial port, with terminal block connections, is provided for DNP communications. It is
software configurable for RS-232 or RS-485 (default), isolated for 2500V transients, and
equipped with receive/transmit LEDs.
A second, isolated serial port (input only) is provided for demodulated IRIG-B input, with
terminal block connections. An LED indicates signal presence and synchronism status.
Protocols:
The primary protocol for both Ethernet and the serial port is DNP 3.0 level 2 (default
DNP slave address is 254) The serial port may be used for configuration using a
terminal emulator protocol and downloading files using DNP object 70. The Ethernet
port can be used to download loading files using DNP object 70. All input and control
point addresses are fixed, for easy configuration.
3.5 Universal Power Supply

Operates from 20 Vdc to 300 Vdc, or 55 to 275 Vac, 50Hz or 60 Hz. The MiCOM C212
consumes less than 500mA at 24 Vdc.
3.6 Packaging and Environmental

Packaging options include a NEMA 4X-rated sealed metal enclosure suitable for outdoor
mounting and a form-fitting aluminum case suitable for panel mounting. There are no
fans or any other moving parts and no ventilation is required within the operating
temperature range.
Case Dimensions:
Option 1 - NEMA 4X enclosure: 16Hx12Wx6D. Includes hinged door and can be
locked. Hoffman part number A16H12ALP or equivalent.
Option 2 (default) Aluminum case: 9.0 W x 7.0 D x 2.75 H. Two units can be
mounted across a standard 19-inch rack space. See mounting drawing below.
-9-
Terminations: All terminal blocks are plug-in European-style design (Phoenix or

equivalent). Each termination accepts up to #12 AWG wire. Spacing and position allows
easy access to termination screws.
Operating temperature range: -40 to +85 degrees C.
Operating humidity: 0 to 95% non-condensing.
Aluminum Case mounting drawing:
3.7 Standards
Power and digital I/O connections comply with IEEE C37.90.1 surge withstand capability
(including 5000V fast-transient). Communications ports comply with IEEE C37.90.1
surge withstand capability.
3.8 Software
Configuration program:
Factory defaults are chosen so that many applications will require no or minimal
configuration. No special program is required to configure the MiCOM C212. Any thirdparty terminal program, such as HyperTerminal is the only software tool required.
Minimal configuration can be performed without any connected terminal or computer.
See Section 5.2 for details.
Operating System:
The operating system is optimized for speed with an execution time of 100
microseconds. This performance level guarantees true 1-millisecond time stamping and
- 10 -
200 microsecond control throughput time. In addition to speed, the operating system
employs fault-tolerant design techniques to ensure maximum reliability.
4. Installation
4.1 Features to consider when installing the MiCOM C212
The ioBrick, as a unit, is the field-replaceable module. There is no need to
troubleshoot below this level, or to open the case.
Plug-in wire clamping terminal blocks accept up to 12AWG wire for all connections
except Ethernet, and facilitate field replacement.
All external connections to the ioBrick are fully isolated and surge protected.
Low power consumption and wide temperature range components allow application
in almost any environment.
Wide input ranges on primary power and digital inputs eliminate ordering and
stocking multiple models.
There are no jumpers to set, or adjustments to make.
Output relays are rated sufficiently to trip and close circuit breakers without the need
for interposing relays.
Each output relay presents a form C contact, allowing either normally open or
normally closed operation.
The serial port optically isolated, for reliability, and is software configurable for either
RS-232 or RS-485 compatibility.
10/100 Base-TX Ethernet port is transformer isolated, using standard, Category 5,
copper UTP cable.
Either 100Base-FX or 10Base-FL fiber optic Ethernet is available as an option if
extreme isolation or noise-immunity is required.
The default DNP3.0 address for the serial port is 254.
The default IP address for the Ethernet port is 192.168.0.254.
- 11 -
4.2 Power & Digital I/O Connections

The dirty connections are all routed to the same side of the ioBrick. These are the
primary power input, contact inputs, and relay outputs. Figure 3 - Figure 6 illustrate
some of the possible variations in connecting the digital I/O when either the positive or
negative side of the battery is to be switched, and when the input contacts are bussed
together at the ioBrick or elsewhere in the field equipment.
These diagrams are somewhat simplified, in that they do not show likely external
application circuitry such as on/off switching and fusing for the power input, separate
fusing for the contact inputs, and local/remote disconnect switching for the relay outputs.
They also cannot include all possibilities for the digital I/O connections. Neither the
inputs nor outputs need be powered from the station battery, but may be connected to
any power source within their rated voltage range. Each input and output is isolated
from the others, so it is not necessary to connect them all the same, as shown. Different
polarities, voltages, and bussing arrangements may be mixed.
Figure 3 - Switched-Positive Connections, Bussed Contacts
PCB
Traces
Contact Inputs
MiCOM C212 ioBrick

External Field Connections
Power & Digital I/O
Internal
Power Supply
Relay Outputs
S8
4
S6
S5
S2
-
Single
Wire
S4
-
Jumper
Links
16
S9
S1
+
1
S3
+
Single
Wire per
Contact
Load
Load
BATT+
Load
Load
Single
Wires
BATT-
Switched-Positive Connections
Contacts Bussed in Field Equipment
Figure 4 - Switched-Positive Connections, Isolated Contacts
Relay Outputs
S8
4
S6
S5
16
S9
Load
Load
Load
S1
+
Single
Wires
BATT+
BATT-
S2
-
Single
Wire
S4
-
Jumper
Links
1
S3
+
PanelMounted
TB(s)
Jumper
Links
Load
PCB
Traces
Contact Inputs
MiCOM C212 ioBrick

External Field Connections
Power & Digital I/O
Internal
Power Supply
Two Wires
per Contact
Switched-Positive Connections
Contacts Isolated in Field Equipment
- 12 -
Figure 5 - Switched-Negative Connections, Bussed Contacts
Figure 6 - Switched-Negative Connections, Isolated Contacts
4.2.1 Grounding
The Protective Earth Ground terminal of the Primary Power Input terminal block must
be tied to a solid earth ground using #12AWG wire. The mounting of the case should
also provide a low impedance path to earth ground. AREVA T&D recommends that all
grounding be performed in accordance with ANSI/IEEE C57.13.3-183.
4.2.2 Power Connections

The C212 power supply is not polarity sensitive, but an arbitrary polarity is indicated on
the label, to encourage consistency in installation wiring.
4.2.2.1 Power Inputs

The universal-input power supply accepts 20Vdc to 300Vdc or 55Vac to 275Vac 45Hz or
65Hz. An external Supply/Mains disconnect and external fusing shall be required on
the power connections to the C212.
- 13 -
4.2.2.2 Supply/Mains Disconnect

Equipment shall be provided with a Supply/Mains Disconnect that can be actuated by
the operator and simultaneously open both sides of the mains input line. The disconnect
should be UL recognized. The Disconnect should be acceptable for the application and
adequately rated for the equipment.
4.2.2.3 Overcurrent Protection/Fusing

To maintain the safety features of this product, a 2 Ampere time delay (T) fuse, with a
minimum interrupting rating of 1500 Amperes, must be connected in series with the
ungrounded/non-earthed (hot) side of the supply input prior to installation. The fuse
must carry a voltage rating appropriate for the power system on which it is to be used. A
UL Recognized fuse in an appropriate fuse holder should be used.
4.2.2.4 Contact Wetting Voltage

A second terminal block (S8) is provided for convenience in picking off the primary input
voltage for use in contact wetting.
The contact wetting voltage must be 24Vdc to 125Vdc + 15%. WARNING: DO NOT USE
TERMINAL BLOCK S8 FOR WETTING VOLTAGE IF THE POWER SOURCE TO THE
C212 IS AC, OR IS OUTSIDE OF THE DC VOLTAGE RANGE. When using the
auxiliary power terminal block S8 to provide wetting voltage for the relay contacts, the
total load current of the output relays should not exceed the primary power input fuse
rating minus the max input current to the power supply. Total relay current < 2 Amp
(max rated power input in watts / Vdc)
4.2.3 Contact Input Connections

Each of the 16 contact input circuits is individually, optically isolated. The users field
wiring or field devices may maintain the isolation between inputs, or may bus one side of
all or a subset of inputs to either the positive or negative side of a dc wetting source, as
shown in Figure 3 - Figure 6. The terminal block arrangement facilitates doing this
easily, using standard bussing combs. If two wires are brought in from each contact, an
external terminal block(s) will need to be added to handle some of the bussing, as
shown in Figure 4 and Figure 6. If desired, the primary power input voltage may be
picked off the auxiliary power terminal block to feed the wetting bus.
4.2.4 Relay Output Connections

The output of each of the four relays is a dry, form C contact pair. The user may wire to
use either the normally-open or normally-closed terminals, according to the power-up
condition required. #12AWG wire is recommended.
Since the relays do not employ magnetic blow-out, it does not matter which side of each
contact is connected to the source or the load. It is desirable to consistently use a
convention, however, so it is recommended that the source is always connected to the
common (C) terminal, and the load is always to connected to the NO (A) or NC (B)
- 14 -
terminal. There may even be applications, such as driving a red and green lamp, where
a load will be connected to each of the NO and NC terminals.
It is not necessary to use the same voltage or polarity source for each relay. The relays
may also be used to switch ac.
4.3 Communications Connections

Connections to the communications options on the ioBrick are all isolated from ground
and are made along the opposite side of the case from the power and I/O wiring, to
maximize noise immunity. These consist of a serial port, an IRIG-B port, and an
Ethernet port, which are depicted in Figure 7, and covered in more detail in the
subsequent subsections.
The serial port is software configurable between RS-232 and RS-485 compatibility, and
the Ethernet port may be assembled for 100Base-TX (twisted-pair), or 100Base-FX or
10Base-FL (fiber optic) compatibility.
Figure 7 - Communications Overview
4.3.1 Ethernet Connections

The ioBrick may be equipped with twisted-pair Ethernet, fiber-optic Ethernet, or both. If
both media are supported, only one may be actually used.
Copper Ethernet compatibility is 100Base-TX, requiring category 5 UTP cabling,
terminated in an RJ-45 plug with standard pin-out. If there are EMI/RFI concerns either
use of the fiber-option option or use of STP cabling may need to be considered. A
straightthrough cable is used to connect to a hub or switch, which is required for
networking multiple devices, but a crossover cable would be required for direct
connection to a single PC or IED.
- 15 -
Fiber Ethernet compatibility may be either 10Base-FL or 100Base-FX, according to the

model purchased, but the appropriate cable in either case is multimode fiber, terminated
in ST type connectors.
4.3.2 Serial Port RS-232 Connections

The ioBrick serial port may be software configured for either RS-232 or RS-485
compatibility. RS-232 connections are for short distance, low-speed, point-to-point
connections between two devices. The standard was developed for connecting a single
port on Data Terminal Equipment (DTE), such as a computer or printer, to a single port
on Data Communications Equipment (DCE), such as a modem. Connections may be
made between ports of like category, by cross-connecting selected signals.
Note that the pin assignments are the same on DTE and DCE equipment, but the
directions of the signals are defined as opposites. This allows a straight through cable to
be used for the original application of connecting one DTE port to one DCE port. Since
the ioBrick uses a plug-in terminal block, primarily for convenience in wiring the RS-485
daisy chain option, use of standard pin numbers is not a consideration.
Although the original standard filled a 25-pin connector (DB25), the 7 signals (plus
ground) listed in the following diagrams are the ones that are commonly used for
connection to basic, leased-line modems, and thus became the core of the RS-232
interface as is most common today. Use of the smaller DB9 and RJ45 connectors has
also become prevalent.
Historically the functions of the handshaking signals were hardwired into the hardware,
so it was necessary either to include all of the signals or to work around any absences
by judicious jumpering in the cable. Since much of the handshaking has become a
software function, a number of these core signals have fallen into disuse on many
devices. The documentation for connected devices will need to be consulted, if you wish
to minimize the number of wires in the cabling.
Figure 8 - RS-232 Connection to a Modem or Radio (DCE)
- 16 -
ioBrick Pin 6 is Signal Ground, not Chassis Ground. The serial port is optically isolated.
Four signals are the most important. The essential signals are Transmitted Data (TXD)
and Received Data (RXD), which are self-evident. When transmitting over a modem or
radio, the Request-To-Send (RTS) signal is also required to warn the modem that the
data stream is about to start, and that it must key up its carrier tone. The Clear-To-Send
(CTS) signal historically provides a modem-dependent time delay that notifies the DTE
that the carrier has had a chance to stabilize, and that it is ok to start the transmit data
stream. This delay may be configured in software, so the CTS wire is optional for the
ioBrick (see section 5.1.12). It may be necessary for interfacing to some device where
the handshaking requirement is other than a simple delay (e.g. buffered flow control).
The remaining signals are neither required nor supported by the ioBrick. Data Carrier
Detect (DCD) is provided by the modem to notify the DTE that it is detecting carrier, and
that received data is being passed. Data Terminal Ready (DTR) and Data Set Ready
(DSR) are often not used, but may be provided by the DTE and DCE, respectively, to
notify one another that they are powered up and ready to function. Some devices may
provide actively switched signals, but often these are just pulled up passively to the
positive supply. In any case, if a device requires either DTR or DSR, it probably supplies
the other, so they can simply be tied together in the cable connector at that device.
Figure 9 - RS-232 Connection to Another IED (DTE)
ioBrick Pin 6 is Signal Ground, not Chassis Ground. The serial port is optically isolated.
When connecting two DTE devices, such as the ioBrick, the TXD and RXD pins must be
cross-connected, as shown in Figure 9, because what is transmitted from one must be
received to the other.
A typical null modem cable may also cross-connect RTS and CTS, but that would not
provide a useful connection unless they are programmed for some sort of special
handshaking. If a DTE device needs to receive CTS, it should be wired to its own RTS.
This does not provide a delay, but at least it provides a relevant signal.
- 17 -
If the device needs to receive DCD, the best connection is from RTS of the other device.
Alternatively, DCD could be wired to DTR of the same device, assuming that it is
provided, which would constantly assert it. If DSR is required, it can be wired to DTR of
the same device.
4.3.3 Serial Port RS-485 Connections

The ioBrick serial port may be software configured for either RS-232 or RS-485
compatibility. RS-485 connections are for longer distance, higher-speed, multi-drop
connections among multiple devices. Figure 10 shows a four-wire connection among
several IEDs. A two-wire connection is also possible, as long as all connected devices
support tri-stating their drivers when not transmitting. In that case the corresponding
transmit and receive terminals would simply be jumpered together at each device. If any
of the devices supports only a two-wire connection, then all must follow suit.
Figure 10 RS-485 Connection to Other IEDs
A four-wire connection requires that one device act as a master, since each device must
listen to one wire pair and transmit on the other. One device must use the opposite pairs
from the rest. In Figure 10 a master IED polls data from the other IEDs. Note that its
connections to the two wire pairs are opposite from the slave devices.
The connections should be daisy chained from one IED to the next, in a linear fashion,
avoiding the creation of stubs. Each physical end of the daisy chain should be
terminated in a pair of 120 resistors, as shown. These belong at the physical extremes,
regardless of which device resides there.
The shield should be tied to the shield terminal at each device, which in the case of the
ioBrick is not earth or chassis ground since the serial port is isolated. The shield should
also be tied to earth ground at a single point in the daisy chain. If this is done at an
ioBrick, the chassis ground terminal on the adjacent IRIG port terminal block is
convenient.
- 18 -
4.3.4 IRIG-B Input Port

The C212 accepts a demodulated (TTL-compatible) IRIG-B signal from any compatible
time source. It is possible to drive multiple C212 units and other IEDs with a single time
source signal. The number of units depends on the source output.
Figure 11 - IRIG Daisy Chain Wiring
The IRIG port of the ioBrick is optically isolated, to avoid ground potential problems
between the devices on the IRIG daisy chain.
The IRIG-B port has a corresponding LED (LD21). This LEDs flash pattern indicates the
state of the synchronize signal.
Rapid steady flashing indicates no IRIG signal found.
Two flashes, pause, two flashes indicates signal found, but synchronization to
time source lost or not complete.
Repeated long flashes indicate that the ioBricks internal clock is currently
synchronized with a valid IRIG time signal.
- 19 -
5. Software Configuration
Most operating parameters of the MiCOM C212 are pre-configured and do not
need changing. The following default settings are changeable:
Setting Description
Default
Options
Serial port type:
RS-485
RS-232-C
Serial port baud rate:
9600
1200 to 115.2kbps
Serial port settings:
N, 8, 1
N, 8, 1 or 2 stop bits
Serial port DNP address:
254
1 to 65,535
Ethernet IP address:
192.168.0.254
any
TCP port for DNP
20000
1024-65535
UDP port for DNP
20000
1024-65535
DNP data class - inputs
Class 1
0-3
All configuration parameters are accessible using a terminal emulation over the
serial or Ethernet ports, but a limited subset may be modified without any
external equipment, using the diagnostic pushbutton as described in Section 5.2.
5.1 Full Configuration via the Serial Port

Only a few items such as the DNP address must be set in the ioBrick. For most
users, the factory settings will be appropriate. However, the ioBrick provides
configuration options to meet special applications as well. This section describes
the complete configuration options available.
5.1.1 Connection:
The ioBrick can be configured directly using a terminal or computer via the serial
port. Configuration is stored in non-volatile flash memory in the ioBrick. If a
computer is used, a terminal emulation program such as Hyperlink is suitable for
communicating to the ioBrick. If the serial port is already in use for DNP
communications, the user should:
1. Physically disconnect the DNP link. (This may be either an RS-232 or RS-485
connection). It is recommended that removable terminal block be unplugged so
that the permanent wiring is not disturbed.
2. Use the diagnostic switch to disable DNP processing and to set the serial port
temporarily to the standard used by the terminal or computer. This is usually RS232 but can be set to either RS-232 or RS-485. To set the link to RS-232, press
- 20 -
the diagnostic switch three short times followed by a push and hold for two
seconds. To set the link to RS-485, press the diagnostic switch four short times
followed by a push and hold for two seconds.
- 21 -
3. Once the RS-232 or RS-485 programming session is started, the digital input
LEDs will continue to display the "bouncing" indication that the unit is in
programming mode. The ioBrick will remain in this mode for at least ten minutes
or longer if the user is active on the terminal. To force an exit from this mode
manually, press the diagnostic switch one more time and the programming
pattern will revert to the normal display after about 20 seconds.See Section 5.2
in this manual for further details on the diagnostic switch operation.
4. Connect the terminal or computer to the ioBrick. The terminal should be set to
9600 baud, 8 data bits, no parity, and 1 stop bit, regardless of what baud and
settings are used for the DNP link. The cable assembly used to attach the
terminal or computer to the ioBrick can be built with a plug-in terminal block
connector so that the permanent wiring is not disturbed. See section 4.3 for pinouts and wiring diagrams.
Note that even though the user may be changing the configuration, the digital
input scanning continues to occur and any point status changes are recorded in
local memory. When the DNP connection is re-established, the point changes
will be reported to the DNP master.
When the ioBrick receives a carriage return character (sent by the Enter key
which is displayed as in this document), a copyright message and a program
version message are displayed followed by a prompt >. The message appears
similar to the following text:
MiCOM C212 ioBrick Copyright (C) 2004-2005 AREVA T&D Inc.

td.com
Version 01.00
www.Areva-
Type 'HELP' for command list.

>
The ioBrick is now ready to accept commands.
- 22 -
5.1.2 Prompts:
The ioBrick displays one of three basic prompts:
Prompt
Description
>
Indicates that the ioBrick is ready for any command

to display configuration or report data.
>>
Indicates that the user has logged in and that the

configuration can be modified. The ioBrick is ready
to accept any command to change the
configuration.
Note: the configuration is not actually modified
until the operator types the SAVE command.
This gives the operator the opportunity to discard
changes in case a mistake is made.
description <current value>:
When a configurable item is to be changed, the

ioBrick displays a description of the item along with
the current value in angle brackets <value>
followed by a colon :. The operator can do any of
the following:
Accept the current value by typing nothing
but the Enter key.
Type a new value (followed by the Enter
key).
Type a ? followed by the Enter key for
more information including the legal range
of the responses.
Type the Esc key to return immediately to
the > or >> prompt with no further
changes. To indicate that an escape (or
other control character) has been typed, ^
is echoed.
- 23 -
5.1.3 Commands:
The following commands are available from the command line. The commands
may behave differently depending upon whether or not the user has logged in.
Generally, if the user has not logged in (single prompt > displayed), then each
command simply reports the current configuration settings applicable to that
command. If the operator has logged in (double prompt >> displayed), then the
operator is shown each setting and given the opportunity to change the values.
The full command name does not need to be typed. Only the number of letters
required to make the command unique are required (but never less than two
letters). However, if additional letters are typed, they must match the command
name.
Command names are not case sensitive.
At any time a typing error is made, the error can be corrected by typing the
backspace key (Control-H, ASCII value 0x08).
If a space character and question mark are typed after the command name,
further information about that command is displayed along with the current
settings when appropriate.
If an unknown command is typed, the following message is displayed:
>GARBAGE
Invalid Command
Type 'HELP' for command list.
>
When changing a configuration setting, the ioBrick displays a series of

configuration questions. Each prompt consists of a description of the setting
along with the current value. For example, when configuring the DNP settings, if
the current DNP address is 254, the ioBrick displays:
DNP Address <254>:
If the operator types a question mark or an invalid response, a help message is

displayed usually describing the valid range for the item. The prompt is then repeated.
DNP Address <254>: ?
(ioBrick) Slave address range 1 to 65535.
DNP Address <254>:
Once an appropriate response is given, the ioBrick moves on to the next

question. If any changes have been made, the settings are reviewed at the end
of the section (right before returning to the >> prompt).
- 24 -
Command:
Description:
HELP or "?"
Display list of commands
LOGIN
Allow configuration editing
LOGOUT
Disallow configuration editing

If changes have been made, user is asked if the changes should be
saved first.
SAVE
Write changes to non-volatile (flash) memory.
QUIT
Exit terminal mode and restore DNP port.

If changes have been made, user is asked if the changes should be
saved first.
DNP
Configure DNP settings
COM1
Configure serial port settings
IPADDRESS
Change IP address Default is 192.168.0.254
TCP/IP
DNP using TCP over IP
UDP/IP
DNP using UDP over IP
DEFAULTS
Restore factory default configuration settings.
PASSWORD
Change password (3-16 char)
DATE
Display / change date <mm-dd-yyyy>
TIME
Display / change time <hh:mm:ss>
AUTOLOGOFF
Change autologoff time (minutes)
DEVICENAME
Optional ioBrick identifier
SUBSTATION
Optional Substation name
INPUT n
Digital Input configuration
OUTPUT n
Digital Output configuration
VERSION
Display a Version Report
- 25 -
5.1.4 HELP Command

Typing HELP, HE, or ? at the command prompt (followed by the Enter key)
displays the following message. Any parameters (on the same line) following the
HELP command are ignored.
>HELP
LOGIN
LOGOUT
SAVE
QUIT
DNP
COM1
IPADDRESS
TCP/IP
UDP/IP
DEFAULTS
PASSWORD
DATE
TIME
AUTOLOGOFF
DEVICENAME
SUBSTATION
INPUT n
OUTPUT n
VERSION
HELP
command ?
<escape>
Allow configuration editing

Disallow configuration editing
Save changes
Exit terminal mode
Configure DNP details
Configure serial port
IP address
DNP using TCP over IP
DNP using UDP over IP
Restore default configuration
Change password
Set date
Set time
Autologoff time
ioBrick name
Substation name
Input configuration
Output configuration
Display program version
Display this list
Display parameter range
Cancel category or command
>
5.1.5 LOGIN Command

Typing LOGIN or LOGI at the command prompt (followed by the Enter key)
allows an operator to log in. Once the operator has successfully logged in to the
system, the configuration can be changed (and saved to non-volatile flash
memory). If the user just wants to view the configuration or reports, it is not
necessary to log in. LOGON is also accepted. The user may also just type
LOG or LO and the ioBrick will assume LOGIN if the user is currently logged
out and LOGOUT if the user is currently logged in. If any parameters (on the
same line) following the LOGIN command are typed (such as ?), a help
message for the LOGIN command is displayed.
- 26 -
>LOGIN ?
LOGIN allows for configuration editing.
Operator name (2-16 characters) is saved in file.
Double prompt (>>) indicates logged in.
>
Once the LOGIN command has been accepted, the user is prompted for an
operator name. This name is not matched to any database, but a copy of the
name is saved in the configuration to indicate the identity of the last person
modifying the setup. If a connection is via TCP/IP, the IP address of the operator
is also automatically saved in the configuration. The operator name is a
minimum of two characters and a maximum of 16 characters. The user should
type an operator name followed by the Enter key. Pressing the Escape key
exits the LOGIN prompt without logging in. Typing a ? or name that is too short
or too long displays the help message shown above.
Once the operator name has been entered, the ioBrick will prompt for the three to
sixteen character password. Passwords are not case-sensitive. The password
is echoed back as * characters. If an invalid password is entered, an error
message will be displayed (for up to three tries). To abort the LOGIN process,
the operator can type the Escape key. Once the user is logged in, the double
prompt will appear.
The factory default password is ATC. This can be changed using the
PASSWORD command described later in this document. If the password is lost
or forgotten, the unit can be returned to the factory defaults (including the factory
default password) using the diagnostic switch (see Section 5.2). Note that the
operator must have physical access to the device to use this diagnostic switch
method of resetting the password.
Example:
>LOGIN
Operator: John Smith
Password: *******
Invalid Password
Password: ***
>>
- 27 -
5.1.6 LOGOUT Command

Typing LOGOUT or LOGO at the command prompt (followed by the Enter
key) disallows further changes to the configuration. The operator can still view
the configuration and reports, however. The prompt will return to a single angle
bracket >. LOGOFF is also accepted. The user may also just type LOG or
LO and the ioBrick will assume LOGIN if the user is currently logged out and
LOGOUT if the user is currently logged in. If any parameters (on the same line)
following the HELP command are typed (such as ?), a help message for the
LOGOUT command is displayed.
>>LOGOUT ?
LOGOUT disallows configuration editing.
Prompt will return to a single arrow ('>').
Reports may still be viewed.
>>
If there are no changes to the configuration when the user types LOGOUT, the
prompt will change back to the single (>) prompt and the user will be logged out.
If the operator has changed any configuration items without saving them, a
prompt appears when the LOGOUT command is entered asking if the changes
should be saved. The user can respond to this prompt with YES, NO, or
CANCEL: These responses can be abbreviated with fewer letters if desired.
YES
The configuration changes will be saved to non-volatile flash memory and

the user will be logged out.
NO
The configuration changes will be discarded and the user will be logged
out.
CANCEL or
<escape> key
The configuration changes will be left intact but will not be saved yet.
The LOGOUT command will be exited and the user will be returned to the
double (>>) prompt. That is, the user will be still logged in.
Example:
>>LOGOUT
Do you wish to save the changes you made <Yes>? ?
Type 'YES', 'NO', or 'CANCEL'
Do you wish to save the changes you made <Yes>? N
Configuration changes discarded.
>
- 28 -
5.1.7 SAVE Command

Typing SAVE or SA at the command prompt (followed by the Enter key)
writes any changes to the configuration to the on-board non-volatile flash
memory. If any parameters (on the same line) following the SAVE command are
typed (such as ?), a help message for the SAVE command is displayed.
>>SAVE ?
SAVE writes the modified configuration to flash memory.
>>
A configuration version number is also saved in the configuration information.

Every time the configuration is saved, the version number is increased by one.
This configuration version number can be used to verify that the configuration
has not been changed from the authorized configuration. The configuration
version number can be viewed using the VERSION command. The version
number is not reset to zero when the operator requests that the ioBrick be reset
to factory defaults. The version number is also increased by one when a
configuration file is reset to factory defaults or downloaded from a master. That
is, the version number always represents the number of times that the
configuration has been saved in this particular ioBrick unit. The flash memory
hardware can be written at least 1,000,000 times so that there is no practical
hardware limit on the number of times that the configuration may be saved.
Example:
>>SAVE
Saving Configuration version 0037...
Complete.
>>SAV
Configuration has not been modified.
No save performed.
>>
There will be a several second pause between the Saving Configuration

message and the Complete message while the data is actually being written to
flash memory. If for any reason the configuration could not be saved, the
Saving Configuration line would display FAILED. Such a message indicates
that the saved data did not read back as identical to the data written. If this
occurs, the defective unit should be taken out of service. Also if this does occur,
the configuration will normally either remain unchanged or be returned to the
factory default configuration as the internal configuration checksum will fail.
- 29 -
>>SAVE
FAILED.
5.1.8 QUIT Command

The QUIT command exits programming mode and restores the serial port to its
configured functionality. If the user has modified the configuration settings
without saving, the user will be prompted to save the configuration in a manner
similar to the LOGOUT command. Approximately eight seconds after exiting, the
port will be restored. If the port was being used for DNP communication, a
reminder is displayed that the DNP physical connection should be replaced.
As an alternative, the diagnostic switch (Section 5.2) can also be used to
terminate the session. If the diagnostic switch is used to terminate the session, it
is recommended that the LOGOUT command first be issued to ensure that all
desired changes have actually been saved.
Example:
>QUIT ?
Quit exits the programming session and
and restores the serial port as required.
>QUIT
Exiting programming mode.
Please reconnect serial DNP connection.
5.1.9 DNP Command

The DNP command (or just DN) allows the user to set up the specific
configuration for the DNP communications channel. Typing DNP ? describes
the DNP command in further detail followed by a listing of the current DNP
configuration.
- 30 -
Example (with configuration set to factory defaults):

>>DNP ?
DNP addresses are in the range 1 to 65535.
The default (slave) address for the ioBrick is 254.
Communication link can be RS-485 (default), RS-232, or Ethernet.
The default master address for unsolicited responses is 3.
The ioBrick can be set to respond only to the master.
Unsolicited commands can be enabled or disabled.
The Select Before Operate time (SBO) defaults to 45 seconds.
DNP ioBrick address is 254 on RS-485 link.
DNP Master address is 3.
ioBrick responds to any address.
Unsolicited responses from the ioBrick are always disabled.
Select Before Operate (SBO) time is 45 seconds.
>>
If the user is not logged in and DNP is typed, just the summary information is
displayed:
>DNP
ioBrick responds to any address.
>
If the user is logged in and DNP is typed, the ioBrick prompts the user for each
item in the DNP configuration list. To accept the current value (which is
displayed in <angle brackets>), the user may just type the enter key. To obtain a
list of the possible options, the user may type ?. To change the value, the first
few letters of the desired option may be typed. The ioBrick also recognizes
several shortcuts. For example, instead of typing RS-485, simply 4 could be
typed.
At the conclusion of the prompts, if the user has modified any values, the
summary information is displayed. If any values are incorrect, the user should
type the DNP command again and enter the correct information. At any time the
user may type the escape key and the remaining prompts will be skipped. The
summary information will still be displayed if any changes were made.
The ioBrick is capable of initiating unsolicited messages to the master. In order
to do this, the master address must be known and the feature must be enabled.
- 31 -
The master address defaults to 3 but can be set to any legal address. DNP
Masters have the ability to turn on and off this unsolicited reporting automatically.
Enable unsolicited reporting if you want to allow it. Default is not allowed.
Note: The ioBrick address (slave address) cannot match the master address.
The ioBrick will check for this condition and change the master address to the
default (3) or one less than the default (2) if necessary.
The user can also restrict the ioBrick from communicating with any other device
on the DNP channel. By default, the ioBrick will respond to any request that is
directed to it regardless of what address initiates the request.
The DNP Select Before Operate time is also programmable. This time defaults
to 45 seconds.
DNP Example accepting all current values:
>>DNP
DNP Address <254>:
DNP Link <RS-485>:
DNP Master Address <3>:
Only respond to master address <No>:
Allow unsolicited responses <No>:
Select Before Operate time <45> seconds:
>>
- 32 -
DNP Example requesting help and changing values:

>>DNP
DNP Address <254>: ?
(ioBrick) Slave address range 1 to 65535.
DNP Address <254>: 8
DNP Link <RS-485>: ?
Options: 'RS-485' (default), 'RS-232', or 'Ethernet'.
DNP Link <RS-485>: 232
DNP Master Address <3>: 8
The Master address must be different from the slave address.
DNP Master Address <3>: ?
Address range 1 to 65535, default is 3.
DNP Master Address <3>: 4
Only respond to master address <No>: Y
Allow unsolicited responses <No>:
Select Before Operate time <45> seconds: 55
ioBrick responds only to master address.
>>
Whenever the communications link is changed to RS-485 or RS-232, the serial

port is reset to its default stop bit and line turn-around characteristics for that
standard. These settings can be reviewed and set using the COM1 command.
The ioBrick can be polled simultaneously by multiple DNP Masters when using
Ethernet. Make sure all DNP masters talking to an ioBrick have unique DNP
addresses.
5.1.10 COM1 Command

The COM1 command (or just CO) allows the user to set up the specific
configuration for the COM1 serial communications channel for connection to a
DNP master. The serial port can be set either as an RS-485 link (the default) or
an RS-232 link. This selection can also be made using the DNP command,
however the COM1 command allows further specification of the serial port
parameters such as baud rate, number of stop bits, line turnaround times, and
(for RS-232) handshaking signals.
The parameters vary depending upon which standard, RS-485 or RS-232 is
chosen. Note that the same physical connector is used for either standard.
However the pin assignments on the connector change depending of which
- 33 -
standard is in use. All of the settings are performed with this software selection.
There are no hardware jumpers to set on the ioBrick itself.
Typing COM1 ? will display general help on the COM1 command followed by a
summary of the current settings.
Example (with configuration set to factory defaults):
>>COM1 ?
COM1 can be set up as RS-232 or RS-485 for DNP communications.
The port is always 8 data bits with no parity.
The baud rate and the number of stop bits can be set.
For RS-485, the delay before and after transmission can be set
as well as full duplex (4 wire) or half duplex (2 or 4 wire).
For RS-232, the RTS and CTS characteristics can be set which
may be used for radio keying.
COM1 is set to the RS-485 standard (for DNP communications) at a
baud rate of 9600 with 8 data bits, no parity, and 1 stop bit.
When transmitting, the line will be enabled 500 us before the
the first character is sent and will remain enabled 500 us
after the last character is sent.
The line is set for Half duplex.
>>
Note: Radio keying indicates handshake for radio modem in the previous example and
as further described in Section 5.1.12.
If the user is not logged in and COM1 is typed, just the summary information is
displayed. The following example shows the display of the default settings when
RS-232 is selected as the communications standard for the DNP port.
>COM1
baud rate of 9600 with 8 data bits, no parity, and 1 stop bit.
The Request To Send (RTS) line is set to always Off.
The Clear To Send (CTS) line is ignored.
>
5.1.11 COM1 RS-485 Prompts

Since RS-485 allows multiple devices on the same multi-dropped lines, all of the
devices must agree to release the lines when the units are not actively
transmitting. A typical RS-485 transmission consists of the following steps.
- 34 -
1. The ioBrick readies a packet for transmission, usually as a result of a

request from the master.
2. The ioBrick enables the RS-485 lines for transmission. Only a single
multi-dropped device can be active at a given time. If more than one
device is active, the communications will be corrupted.
3. The ioBrick waits for any transients to settle on the lines. This wait time is
the Tx Delay and defaults to 500 microseconds. This time can be set
anywhere from 50 us to 100,000 us (100ms).
4. The ioBrick transmits the packet in one continuous burst.
5. After the last bit of the last byte of the packet is transmitted, the ioBrick
waits for any transients to settle on the lines. This wait time is the Tx End
Delay and also defaults to 500 us. This time can be set anywhere from
50 us to 100,000 us as well.
The user can also specify either Half or Full duplex on the RS-485 lines.
If Half Duplex is specified, the user can physically wire the RS-485 link as a twowire RS-485 link or as a four wire RS-485 link. A two-wire link uses the same
two physical wires for both transmitting and receiving. This also means that
every slave will listen to not only the commands from the master but the
responses from all of the other slaves as well. Of course the DNP
communication layers specify the sending and receiving addresses so that these
packets will be ignored if they are not addressed to the listener. Since the same
two wires are used for both transmitting and receiving, potentially every
transmitted message is echoed back to the receiver. When Half Duplex is
specified, the receiver is turned off when a message is being transmitted.
If Full Duplex is specified, then the ioBrick can receive messages at the same
time it is transmitting. Normally this is only specified for a 4-wire link. In a 4-wire
link, one pair of wires is attached to the masters transmitter and all of the slave
receivers. The second pair of wires is attached to the masters receiver and all of
the slave transmitters.
RS-485 Example accepting all current values:
- 35 -
>>COM1
Com1 Standard <RS-485>:
Com1 Baud Rate <9600>:
Com1 Number of Stop Bits <1>:
Com1 RS-485 Tx Delay <500> us:
Com1 RS-485 End Delay <500> us:
Com1 RS-485 <Half> Duplex:
>>
RS-485 Example requesting help and changing values:

>>COM1
Com1 Standard <RS-485>: ?
Options are RS-232 or RS-485.
This setting affects DNP communications only.
Com1 Baud Rate <9600>: ?
[110, 300, 1200, 2400, 4800, 9600 (default), 14400, 19200,
38400, 57600, or 115200]
Com1 Baud Rate <9600>: 19200
Com1 Number of Stop Bits <1>: ?
1 (default) or 2 stop bits (and always 8 data bits, no parity).
Com1 Number of Stop Bits <1>: 2
Com1 RS-485 Tx Delay <500> us: ?
Delay between Tx enable and first character transmission.
(50 to 100000 microseconds, default 500 us)
Com1 RS-485 Tx Delay <500> us: 1000
Com1 RS-485 End Delay <500> us: ?
Delay between last character sent and line disable.
Com1 RS-485 End Delay <500> us: 600
Com1 RS-485 <Half> Duplex: ?
Half duplex (default) is used with 2 or 4 wire RS-485.
Reception is disabled during transmission in half duplex.
Full duplex requires 4 wire RS-485.
Com1 RS-485 <Half> Duplex: Full
baud rate of 19200 with 8 data bits, no parity, and 2 stop bits.
When transmitting, the line will be enabled 1000 us before the
the first character is sent and will remain enabled 600 us
The line is set for Full duplex.
>>
- 36 -
5.1.12 COM1 RS-232 Prompts

If the RS-232 standard is selected for a wired connection, only two units (for
example, the master and the slave) can share the link at the same time.
However, if the ioBrick is attached to a radio modem, multiple units may be on
the same DNP channel (radio frequency) while only two physical devices (the
ioBrick and the modem) share the wired connection. The ioBrick also supports
two handshaking lines, RTS and CTS, which can be used to communicate with
the radio modem.
RTS (Request To Send) is an output from the ioBrick and it can be set up as
always Off (the default), always On, or Active. When it is programmed as Active,
the line is asserted before a transmission and is deasserted after transmission.
Both the start delay and end delay are programmable so that the RTS signal can
be used to Key the modem.
CTS (Clear To Send) is an input to the ioBrick. The CTS signal can either be
ignored or programmed to regulate traffic from the ioBrick. When the CTS line is
deasserted, the ioBrick is blocked from transmitting. When the CTS line is
asserted, the ioBrick is blocked. If the CTS line is deasserted in the middle of a
packet transmission, several (buffered) bytes may be transmitted before
transmission will stop. The CTS line may be controlled from a modem which
blocks the transmission until the modem has opened a clear transmission path to
the master.
The typical operation with both RTS Active and CTS enabled is:
1. The ioBrick readies a packet for transmission.
2. The ioBrick turns on the RTS line and waits the specified Tx Delay time.
This is typically the radio keying delay time.
3. At the expiration of the starting delay, the ioBrick checks the status of the
CTS line. If the line is deasserted, the ioBrick waits until it is asserted.
The modem generally waits to assert the CTS line until it is ready to
accept the transmission.
4. Once the CTS line is asserted, the ioBrick transmits the packet. If the
CTS line is deasserted during the transmission, the remaining bytes of the
packet are delayed until CTS is once again asserted. This feature is
usually only used if the modem has limited buffering space.
5. After the last bit of the last byte is transmitted, the ioBrick starts the end
delay timer. When the end delay has expired, the ioBrick turns off the
- 37 -
RTS line. The packet sequence is now complete and the radio modem
may release the channel.
RS-232 Example accepting all current values with RTS Active:
Note: the user is not prompted for the delay times if RTS is not Active.
>>COM1
Com1 Baud Rate <9600>:
Com1 Number of Stop Bits <1>:
Com1 RS-232 Request To Send (RTS) setup <Active>:
Com1 RS-232 Tx Delay <500> us:
Com1 RS-232 End Delay <500> us:
Com1 RS-232 Clear To Send (CTS) enabled <No>:
>>
RS-232 Example requesting help and changing values:
- 38 -
>>COM1
Com1 Baud Rate <9600>: ?
[110, 300, 1200, 2400, 4800, 9600 (default), 14400, 19200,
38400, 57600, or 115200]
Com1 Baud Rate <9600>: 1200
Com1 Number of Stop Bits <1>: ?
1 (default) or 2 stop bits (and always 8 data bits, no parity).
Com1 Number of Stop Bits <1>: 2
Com1 RS-232 Request To Send (RTS) setup <Off>: ?
RTS options: Always 'Off' (default), Always 'On',
or 'Active' (On while transmitter is active).
Com1 RS-232 Request To Send (RTS) setup <Off>: Act
Com1 RS-232 Tx Delay <500> us: ?
Delay between RTS On and first character transmission.
Com1 RS-232 Tx Delay <500> us: 2000
Com1 RS-232 End Delay <500> us: ?
Delay between last character sent and RTS off.
Com1 RS-232 End Delay <500> us: 300
Com1 RS-232 Clear To Send (CTS) enabled <No>: ?
CTS: If 'Yes', transmission is blocked until the external
signal is asserted. If 'No' (default), CTS is ignored.
Com1 RS-232 Clear To Send (CTS) enabled <No>: YES
baud rate of 1200 with 8 data bits, no parity, and 2 stop bits.
The Request To Send (RTS) line will be asserted 2000 us before
the first character is sent and will remain asserted 300 us
The Clear To Send (CTS) line must be asserted before
transmission from the ioBrick will occur.
>>
5.1.13 IPADDRESS Command

The IPADRESS command (or just IP) allows the user to specify the Internet
Protocol (IP) address of the ioBrick. Every device on the network should have a
unique address. The address consists for four decimal number separated by
periods. Each number can range from 0 to 255. The default address is
192.168.0.254. If the user is not logged in, the command just reports the current
setting. If a question mark is typed after the command, a short explanation is
displayed followed by the current setting.
Example requesting IP Address help
- 39 -
>IPADDRESS ?
The IP Address uniquely identifies the ioBrick on a network.
The ioBrick IP Address is 192.168.0.254
>
Example requesting help and changing the IP Address:

>>IP
IP Address for the ioBrick <192.168.0.254>: ?
The IP Address consists of four numbers (0 to 255) separated
by decimal points. The default address is 192.168.0.254
IP Address for the ioBrick <192.168.0.254>: 192.168.0.35
The ioBrick IP Address is 192.168.0.35
>>
5.1.14 TCP Configuration

TCP configuration allows the TCP port and IP Addresses to be set when using
TCP/IP for DNP communications. For security, the addresses of the masters
that communicate to the device must be set explicitly using this command.
The TCP port is defaulted to 20000. The TCP port must match port set in the
DNP Master. The range for this variable is 1024 to 65535.
Each of the DNP masters allowed to communicate to this ioBrick is entered, with
up to three device addresses entered. Note that the ioBrick should be on the
same subnet as the Masters for communication to take place this means the
first three sets of digits in the IP Address should be the same.
If the user is not logged in, the command just reports the current setting. If a
question mark is typed after the command, a short explanation is displayed
followed by the current setting.
Example of TCP settings (default)
>TCP
The TCP port
Commands may
Commands may
Commands may
for DNP
be sent
be sent
be sent
is 20000.
from Master 1 IP address 0.0.0.0
>
- 40 -
When logged on, the port and/or Master IP addresses can be changed as shown
below.
Example of entering DNP Masters IP Address:
>> TCP
TCP port for DNP commands to the ioBrick <20000>:
DNP Master IP Address 1 for TCP <0.0.0.0>: 192.168.0.200
DNP Master IP Address 2 for TCP <0.0.0.0>:
DNP Master IP Address 3 for TCP <0.0.0.0>: ?
IP Addresses consists of four numbers (0 to 255) separated
by decimal points. 0.0.0.0 indicates not in use.
DNP Master IP Address 3 for TCP <0.0.0.0>:
The TCP port for DNP is 20000.
Commands may be sent from Master 1 IP address 192.168.0.200
>>
5.1.15 UDP Command

UDP configuration allows the UDP port and IP Addresses to be set when using
UDP/IP for DNP communications. For security, the addresses of the masters
that communicate to the device must be set explicitly using this command.
The UDP port is defaulted to 20000. The port must match port set in the DNP
Master. The range for this variable is 1024 to 65535.
Each of the DNP masters allowed to communicate to this ioBrick is entered, with
up to three device addresses entered. Note that the ioBrick should be on the
same subnet as the Masters for communication to take place this means the
first three sets of digits in the IP Address should be the same.
If the user is not logged in, the command just reports the current setting. If a
question mark is typed after the command, a short explanation is displayed
followed by the current setting.
- 41 -
Example of UDP settings (default)

>UDP
The UDP port
Commands may
Commands may
Commands may
for DNP
be sent
be sent
be sent
is 20000.
>
Example of adding a UPD master IP Address:

>>UDP
UDP port for DNP commands to the ioBrick <20000>: ?
The standard UDP port number for DNP is 20000.
Range 1024 to 65535.
UDP port for DNP commands to the ioBrick <20000>:
DNP Master IP Address 1 for UDP <0.0.0.0>: ?
IP Addresses consists of four numbers (0 to 255) separated
by decimal points. 0.0.0.0 indicates not in use.
DNP Master IP Address 1 for UDP <0.0.0.0>: 192.168.0.100
DNP Master IP Address 2 for UDP <0.0.0.0>:
DNP Master IP Address 3 for UDP <0.0.0.0>:
The UDP port for DNP is 20000.
>>
5.1.16 DEFAULTS Command

The DEFAULTS command (or DEF) resets the ioBrick to its factory default
configuration. A confirmation is obtained from the user before the configuration
is actually reset. As always, no configuration information is actually modified until
the changes are written using the SAVE command. Typing the command with a
question mark or typing the command when not logged in results in the following
message:
>DEFAULT ?
This command restores all configuration settings to their
factory defaults, including DNP on RS-232 and DNP address 254.
>
- 42 -
DEFAULTS and SAVE Example when the operator is logged in:

>>DEF
Do you wish to restore the ioBrick to its factory defaults <No>? Y
The ioBrick configuration has been reset to factory defaults.
>>SAVE
Complete.
>>
5.1.17 PASSWORD Command

The PASSWORD command (or PA) allows the user to change the stored
password in the ioBrick. Passwords are from three to sixteen characters and are
not case-sensitive. In order to change the password, the user must be logged in
so that the user may subsequently save the configuration with the new password.
When changing the password, the user is prompted for the old password and
asked to type the new password twice to guard against typing errors. Typing
PASSWORD with a question mark or when not logged in brings up the following
message:
>PASSWORD ?
This command allows a logged in user to change the password.
Passwords are 3 to 16 characters and are not case sensitive.
>
Example of a logged in user changing the password:

>>PASS
Old Password: ***
New Password (3 to 16 characters): *******
Repeat New Password: *******
Password will be changed when configuration is saved.
>>
5.1.18 DATE Command

The DATE command allows the user to display or change the current date. Note
that normally there is no need to set the date as the date and time are updated
via the DNP link or the IRIG-B signal. Note also that the date and time
- 43 -
oftentimes will be specified in UTC or Universal Coordinated Time rather than

local time so that Daylight Savings Time is never an issue. The Date is specified
in month-day-year format as mm-dd-yyyy.
Even though the date is not stored in the configuration, the user must be logged
in to change the date. No SAVE is required.
5.1.19 TIME Command

The TIME command allows the user to display or change the current time. Note
that normally there is no need to set the time as the date and time are updated
via the DNP link or the IRIG-B signal. Note also that the date and time
oftentimes will be specified in UTC or Universal Coordinated Time rather than
local time so that Daylight Savings Time is never an issue. The Time is specified
in 24 hour military time format as hour:minute:second.millisecond
(hh:mm:ss.mmm). If the user wishes to set the time, the millisecond field should
not be included.
Even though the time is not stored in the configuration, the user must be logged
in to change the time. No SAVE is required.
5.1.20 AUTOLOGOFF Command

The AUTOLOGOFF command (or AU) allows the user to set the maximum time
that a programming session can stay active with no user interaction. The default
time is 60 minutes. If there is no activity within this period, the user is logged off
and the link will be restored as required.
5.1.21 DEVICENAME Command

The DEVICENAME command (or DEV) allows the user to specify a name for
this ioBrick or the equipment it controls. This name can be used to verify that the
correct unit is being accessed when the user is programming over a remote link.
The name can be from zero to 32 characters long.
5.1.22 SUBSTATION Command

The SUBSTATION command (or SUB) allows the user to specify a name for
the substation at which this ioBrick is located. This name can be used to verify
that the correct unit is being accessed when the user is programming over a
remote link. The name can be from zero to 32 characters long.
- 44 -
5.1.23 INPUT Command

The INPUT command (or IN) allows the user to configure each of the sixteen
digital inputs. The factory default configuration will usually be sufficient for most
applications and no input configuration is normally required. An optional
parameter with the INPUT command is the actual input number (0 to 15) or a
question mark for general help. If the optional number is not used, the software
starts with point 0 and increments each time the INPUT command is issued.
Normally, every input is included as three DNP points: a digital input point, a
counter, and a freeze counter. The configuration allows any input to be disabled
for any of these uses. However, to prevent renumbering of the remaining points,
the unused slot is still left in the DNP memory map.
Each input can be configured into DNP classes based on the point type.
When reported as a binary input it is defaulted to DNP Class 1.
When reported as a normal counter it is defaulted to DNP Class 3.
When reported as a freeze counter it is defaulted to DNP Class 3.
The chatter characteristics of each digital input can also be specified individually.
A digital input is considered to be in the Chatter state if it has transitioned ten
times or more in the last ten seconds. Both this chatter limit and chatter period
can be changed as required. A point in the Chatter state does not generate
unnecessary network traffic. Once the point is stable for the chatter period, it
automatically returns to the non-chatter state.
In addition, a 0 to 32 character name can be specified for the digital input point
for documentation purposes.
- 45 -
Example of Input setting for point

>IN
Digital Input
Reported as a
Reported as a
Reported as a
Chatter limit
0:
binary input:
Yes
normal counter: Yes
freeze counter: Yes
is 10 transitions in
DNP Class: 1
DNP Class: 3
DNP Class: 3
10 seconds.
>
Example with requests for help:

>>IN 3
Input Name <>: ?
Length 0 to 32 characters. To erase, type a space.
Input Name <>:
Report as a binary input: <Yes>: ?
DNP Object 1: YES or NO.
Report as a binary input: <Yes>:
DNP assigned class for binary input: <1>: ?
0=none, DNP class 1, 2, or 3 (default is 1).
DNP assigned class for binary input: <1>:
Report as a normal counter: <Yes>: ?
Report as a normal counter: <Yes>:
DNP assigned class for normal counter: <3>:
Report as a freeze counter: <Yes>: ?
Report as a freeze counter: <Yes>:
DNP assigned class for freeze counter: <3>:
Chatter Limit: <10> transitions: ?
Maximum transitions for chatter period (0=disabled) 0 to 1000.
Chatter Limit: <10> transitions:
>>
5.1.24 OUTPUT Command

The OUTPUT command (or OU) allows the user to configure each of the four
digital outputs. The factory default configuration will usually be sufficient for most
applications and no output configuration is normally required. An optional
parameter with the OUTPUT command is the actual output number (0 to 3) or a
question mark for general help. If the optional command is not used, the system
starts with output 0 and increments each time the OUTPUT command is issued.
- 46 -
The OUTPUT configuration allows the user to specify which DNP control
commands may be set to the point. By default, all commands are accepted.
These include:
Pulse ON
Pulse OFF
Latch ON
Latch OFF
Paired CLOSE (programmable on even addresses only actual
output is the odd point following).
Paired Close refers to the Close output point, which is activated in a
trip and close pair.
Paired TRIP (programmable on even addresses only actual
output is the even point).
Paired Trip refers to the Trip output point, which is activated in a trip
and close pair.
In addition, a 0 to 32 character name can be specified for the digital output point
for documentation purposes.
See Section 6 for DNP point mapping.
Example:
>OUT
Digital Output 0:
Pulse Commands: Allow ON & OFF
Latch Commands: Allow ON & OFF
Paired Trip & Close commands allowed.
>
- 47 -
Example of using the OUTPUT command to configure point 2.

>>OUT 2
Output Name <>: ?
Length 0 to 32 characters. To erase, type a space.
Output Name <>:
Allow Pulse ON command: <Yes>: ?
YES or NO. After the command, the output is left OFF.
Allow Pulse ON command: <Yes>:
Allow Pulse OFF command: <Yes>: ?
YES or NO. After the command, the output is left ON.
Allow Pulse OFF command: <Yes>:
Allow Latch ON command: <Yes>: ?
YES or NO. After the command, the output is left ON.
Allow Latch ON command: <Yes>:
Allow Latch OFF command: <Yes>: ?
YES or NO. After the command, the output is left OFF.
Allow Latch OFF command: <Yes>:
Allow Paired Trip command: <Yes>: ?
YES or NO. A Trip pulses this point ON. Next point is OFF.
Allow Paired Trip command: <Yes>:
Allow Paired Close command: <Yes>: ?
YES or NO. A Close pulses the next point ON. This point is OFF.
Allow Paired Close command: <Yes>:
>>
5.1.25 VERSION Report

The VERSION report (or VE) allows the operator to display the version number
of the ioBrick main program, the ioBrick boot program, and the User
Configuration version, operator, operator IP Address, and date/time of last
modification. This command does not affect the configuration so the user does
not need to be logged in. Typing a question mark or any additional parameters
has no effect on the command.
- 48 -
Example:
>VERSION
MiCOM C212 ioBrick Copyright (C) 2004 AREVA T&D Inc. www.Areva-td.com
ioBrick program version 01.00
'Version 01.00'
Boot program version 01.00
'Version 01.00'
Configuration version 0039 last modified Fri 12-Nov-2004 16:21:49.919
by operator [John Smith] at IP Address 0.0.0.0
>
Note: The version strings enclosed in single quotation marks may contain
additional information about the program release.
Note: The IP Address will be 0.0.0.0 if the user logged in locally or used the
diagnostic switches to program the unit.
Note: If the diagnostic switches are used to change the configuration, the
operator name will be DIAG_SWITCH.
- 49 -
5.2 Limited Configuration via the Diagnostic Switch

The diagnostic switch allows the user to control the function of the serial port (either
DNP or configuration programming). Note that if the user has configured DNP to run
over the Ethernet port, then the serial port is automatically available for user interaction.
However, if DNP is to share the serial port, then this mechanism allows the port to be
switched between the normal DNP operation and the user interface operation. The
Ethernet port can also be used as an alternate method of programming.
The diagnostic switch allows limited programming of the following settings without the
use of any attached devices. These settings are:
DNP connection:
RS-485 (default)
RS-232
Ethernet
DNP address:
Addresses 4 to 19 programmable without tools.
The following sections give instructions for limited programming through the
diagnostic switch. The diagnostic switch interface also allows a user to return the ioBrick
to its factory default settings, as well as verify the current configuration.
5.2.1 LED test

Pressing the diagnostic switch once will result in the following sequence:
(a) all Digital input LEDs ON for one second
(b) all Digital input LEDs OFF for one second
(c) resume normal operation (LEDs display the current input status)
- 50 -
5.2.2 Enter Programming mode

Pressing the diagnostic switch twice (in a two-second period) causes the unit to enter
the programming mode. Four main options are allowed:
(a) Selection of the serial port for temporary programming operation (either RS232 or RS-485). Entering this mode will suspend serial DNP communications so
that the DNP connection can be disconnected and a PC can be attached to the
serial port.
(b) DNP setup: Ethernet, RS-232 serial, or RS-485 serial
(c) DNP address: selection of addresses 4-19 is allowed using this method. If an
address outside of this range is needed, it can be programmed using a computer
or terminal.
(d) Reset ioBrick configuration to factory defaults (DNP address 254, DNP over
RS-485)
Note: The diagnostic switch is the switch furthest from the Ethernet connector. The
switch closest to the Ethernet connector is the reset switch.
5.2.3 LED patterns during programming using the diagnostic switch

Once the user presses the diagnostic switch twice, the LEDs switch to a distinctive
pattern to indicate that the LEDs are no longer reflecting the status of the 16 digital
inputs but are instead displaying the status of the programming or programming
connection. LED15, LED14, LED13, LED12, & LED11 are in a continuous rotating
flashing loop to alert the user that the LEDs are not in their normal mode. The LEDs
bounce back and forth from LED15 to LED11 and back to LED15. The remaining LED
patterns have the specific meanings described within the tables found on the following
pages.
To advance to the next selection, the user briefly presses the diagnostic switch. Each
time the switch is pressed and released, the state will advance to the next pattern. If no
action is taken within a time-out period, all of the LEDs will be blanked for one second
and the display will then revert to the normal operation. Timeout values for each step
are explained following the tables below.
If the user wants to select the option specified by the currently displayed pattern, the
user must press and hold the diagnostic switch for approximately 2 seconds. Once the
selection has been accepted, the selected pattern will begin to flash indicating that the
action has been taken and the user can release the switch.
In addition, any time that the currently displayed pattern matches the actual current
configuration, LED16 will be lit. This allows the operator to confirm the settings without
having to reprogram the unit.
- 51 -
The general usage of the LEDs is as follows:

LED1:
RS-232 mode selected
LED2:
RS-485 mode selected
LED3:
DNP connection definition (used with

LED1 and LED2 as described below)
LED4-10 on singly:
DNP Addresses 4 though 10
LED10 on plus one

of LED1-9 on:
DNP Addresses 11 to 19
LED4 to 10 all on:
Return to factory default settings
LED11-15:
rotating pattern to indicate diagnostic

and programming mode
LED16:
on indicates that the currently

displayed selection matches the
current programmed or selected
value.
The selection steps and corresponding LED patterns are shown below.

indicates that the LED is on

indicates that the LED is off
indicates that the LED is part of a rotating flashing pattern
"P"
indicates that the LED is on if the selection matches the current

programming and off if it does not.
"S"
indicates that the LED is on if the selection matches the current

temporary serial port selection.
When lit during Step 1 in the next table, the LED 16 indicates that the
user has changed the configuration using the diagnostic switches
and that the changes will be programmed into flash memory in
approximately 20 seconds. To cancel these changes, hold the
diagnostic switch for approximately 2 seconds and the LED will go
out (and programming mode will be exited).
M:
- 52 -
C212 ioBrick
LED Setup
Step
1:
Step
2:
Step
3:
Step
4:
Step
5:
Step
6:
Step
7:
Step
8:
Step
9:
Step
10:
Step
11:
Step
12:
Step
13:
Step
14:
Step
15:
Step
16:
Step
17:
Step
18:
Step
19:
Step
20:
ioBrick is in
Programming
Mode.
Selecting this
step will force
exit.
Select RS-232 for
temporary
connection
Select RS-485 for
temporary
connection
Ethernet selected
for DNP normal
communication
RS-232 selected
for DNP normal
communication
RS-485 selected
for DNP normal
communication
(factory default)
DNP Address 4
DNP Address 5
DNP Address 6
DNP Address 7
DNP Address 8
DNP Address 9
DNP Address 10
DNP Address 11
DNP Address 12
DNP Address 13
DNP Address 14
DNP Address 15
DNP Address 16
DNP Address 17
16
15
14
13
12
11
10
P
P
P
P
P
P
P
P
P
P
P
P
P
P
- 53 -
C212 ioBrick
LED Setup
Step
21:
Step
22:
Step
23:
16
DNP Address 18
14
13
12
11
10
15
14
13
12
11
10
DNP Address 19
Return ioBrick to
factory defaults
Press the switch
again to return
to Step 1.
15
P
P
16
If no action is taken for the timeout (defined below) period, the display automatically will
revert to normal operation.
o The timeout period for Steps 2 and 3 (programming via a terminal) is ten minutes
after the last user interaction if the user has actually selected this option. To
cancel, pressing the diagnostic switch again will immediately cause the system to
revert to normal operation. The use of the LOGOUT command is recommended
to ensure any data entered is saved if the switch is used to revert to normal
operation.
o
The timeout period for all other steps (or Steps 2 & 3 if no action is selected) is
about 20 seconds.
Rotating (Flashing) Pattern for LED15 to LED11

This distinctive pattern indicates that the 16 LEDs are displaying the programming mode
status and not the status of the 16 digital inputs.
16
15
14
13
12
11
10
- 54 -
6. DNP3.0 Protocol
The MiCOM C212 supports DNP3.0 Level 2 protocol (slave) over the serial or Ethernet
port. The ioBrick will automatically respond correctly to the DNP objects listed below.
DNP 3.0 point addresses are fixed, as follows:
16 digital inputs: 0 to 15
4 digital outputs: 0 to 3
DNP address for the ioBrick defaults to 254, and the master address defaults to 3. The
ioBrick supports unsolicited DNP reporting, which must be enabled (see Section 5.1.9
for these changes).
Binary inputs are defaulted to DNP Class 1, Counters to DNP Class 3, and may be
changed using the INPUT commands (see Section 5.1.23).
The TCP and UPD ports are defaulted to a value of 20000. The port may be changed
(see Sections 5.1.14 and 5.1.15) to match the DNP master. IP Addresses for the DNP
masters are also entered in these sections.
Up to 4 simultaneous TCP/IP connections are supported along with simultaneous DNP
over UDP communication.
DNP Object
Number
Description
Variation
Supported
Binary input
All
Binary input Change
All
10
Control Relay Output
All
12
Pattern Output Control
All
20
Counter, Binary and Delta
All
21
Counter, Frozen and Frozen Delta
All
22
Counter, Change and Delta Change
All
23
Counter, Frozen event and Frozen Delta Event
All
50
Time and Date, Absolute and Interval
All
51
Common time of Occurrence (COT)
All
52
Time Delay
All
60
Data
70
File Identifier
All
80
Internal Indications
All
Class 0 and 1
- 55 -
7. Maintenance
7.1 Troubleshooting
The C212 does not require any routine maintenance. There are no adjustments to make
or batteries to change. The C212 runs self diagnostic routines when the system is reset
(on power up or when the reset button is pressed) as well as continuous self-diagnostic
routines using background processing during normal operation. The 16 LEDs normally
used to indicate digital input status are temporarily used to display diagnostic information
on power-up or reset, as follows:
Pattern- normal boot sequence:
Meaning:
All LEDs on for 1s
Initial boot and SDRAM test
LEDs rotate from LED1 to LED16 for 5s SDRAM read back test and zeroing
All LEDs off
Program loaded
Note: After a normal program load is completed the digital input LEDs indicate actual
input status.
Pattern- error detected during test:
Meaning
LED8 to LED 1 rotating
Boot error (watchdog resets to clear error)
LED9 on:
Unknown error
LED 10 on:
SDRAM failure
LED11 on:
No program in flash memory
LED12 on:
Primary program in flash corrupted
LED13 on:
Primary and secondary programs corrupted
7.2 Field Repair

There are no field repairable parts on the C212.
7.3 Firmware program upgrade

The C212 firmware program is upgradeable through the serial port or the Ethernet port.
The program is stored in nonvolatile flash memory. To upgrade the firmware program,
load the new file using DNP object 70 (file transfer). Step-by-step instructions are
included with the firmware upgrade file. Firmware releases may be obtained using the
contact information provided at the beginning of this document.
- 56 -
The ioBrick can hold two programs in its non-volatile flash memory: a primary program
and a secondary (backup) program. Whenever a new program is downloaded, the
existing secondary program is discarded. After the new program is downloaded and the
ioBrick is reset, the existing primary program becomes the secondary program, and the
newly downloaded program becomes the new primary program. If the primary program
becomes corrupted, the ioBrick will automatically failover to the secondary program.
To force the secondary program to run in place of the primary program, press and
release the reset button and then press and hold the diagnostic switch on until after the
boot sequence is complete.
A program which is currently executing in memory cannot be replaced until after the
ioBrick is reset. That is, the currently executing program is always marked as a "readonly" file.
- 57 -
8. MiCOM C212 ioBrick Photos

8.1 CPU/MEMORY/COMM BOARD
ETHERNET
PORT
10FL OR 100FX
ETHERNET
PORT
10/100TX
FIBER OPTIC
TRANSCEIVER
AND LEDs
RESET SELFTEST CPU PROGRAM

CPU
PORT
BUTTON BUTTON
(FACTORY USE)
IRIG-B PORT
(DEMODULATED)
SERIAL PORT
RS-232/RS-485
SOFTWARE
SELECTABLE
POWER LED
OPTICAL
ISOLATION
ARM CPU
SERIAL PORT SERIAL PORT

TRANSMIT LED RECEIVE LED
IRIG B SYNC LED
ETHERNET TRANSMIT AND

RECIEVE LEDs
BUS PORT TO
I/O BOARD
4 LEDs
INDICATE
OUTPUT RELAY
STATE
- 58 -
16 LEDs
INDICATE INPUT
STATUS OR
DIAGNOSTIC
RESULTS
8.2 POWER/IO BOARD

BUS PORT TO
CPU BOARD
UNIVERSAL POWER
SUPPLY
POWER LED
OPTICAL ISOLATION
OUTPUT RELAYS
POWER
OUTPUT
POWER INPUT
(69-240VAC 50/60HZ,
24-240VDC)
16 DIGITAL INPUTS
(24-125VDC EXTERNAL
WETTING VOLTAGE)
4 RELAY
OUTPUTS
(FORM C)
- 59 -
9. Appendix
9.1 Firmware Version History
Description
File Name
Release Date
C212 Initial Release
ioBrickVer00_11.elf
Nov 2004
C212 Production Release
ioBrickVer01_00.elf
Apr 2005
ioBrickBoot_01_00.elf
Apr 2005
C212 Bootloader
- 60 -

Mico MC 212 User Guide

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Mico MC 212 User Guide

Transféré par

Droits d'auteur :

Formats disponibles

MiCOM C212

ioBrick Digital I/O Controller

MiCOM C212 User Manual

INSTALLATION AND MAINTENANCE

WARRANTY AND ASSISTANCE

Installing, Commissioning and Servicing

Protective fuse rating

Integrity of ground (earth) connection (where applicable)

Equipment operating conditions

Insulation and dielectric strength testing

Manual Update History

Original from Plymouth Systems material

Added Hyper terminal instructions, safety

Specifications modified per RSC

Comments from RW Fisher added

Production release: DNP over IP, TCP configuration,

Figure 1 - ioBrick Functional Block Diagram ..................................................................... 7

C212UG004 April 2005

Copyright 2005 AREVA T&D Inc.

Optically isolated synchronization port accepts demodulated IRIG-B time code

C212UG004 April 2005

Copyright 2005 AREVA T&D Inc.

12W (max), 12VA (max)

24-250Vdc, 69-240Vac (50-60Hz)

20-300Vdc, 55-275Vac (45-65Hz)

16, individually isolated (ANSI/IEEE C37.90.1: 1989)

4 relays, single dry form C output per relay

Serial Comm. Port

Single port, optically isolated

Single port, optically isolated

Single logical port, three physical interface options

C212UG004 April 2005

Copyright 2005 AREVA T&D Inc.

Aluminum, 9.0 W x 7.0 D x 2.75

Field Wire Terminations

Plug-in, wire-clamping terminal block, #12AWG max.

Field Wire Terminations

C212UG004 April 2005

Copyright 2005 AREVA T&D Inc.

Up to and including 2000m above sea level.

IC III (Distribution Level) Refer to definitions (Section 1.5)

Pollution Degree 2. Refer to definitions (Section 1.5)

Case IP20 to IEC60529:1989

Note 1: A separate source of wetting voltage is recommended for applications requiring

C212UG004 April 2005

Copyright 2005 AREVA T&D Inc.

C212UG004 April 2005

Copyright 2005 AREVA T&D Inc.

Power & Digital I/O Board

C212UG004 April 2005

MiCOM C212 ioBrick

Copyright 2005 AREVA T&D Inc.

Figure 2 Board Interconnection Diagram

727 CPU & Comm Board

3.1 CPU and Memory

3.2 Contact Input Subsystem

3.3 Output Subsystem

C212UG004 April 2005

Copyright 2005 AREVA T&D Inc.

3.4 Communications Subsystem

3.5 Universal Power Supply

3.6 Packaging and Environmental