IEDScout

Examples
IEDScout Examples

Manual Version: IEDScout.AE.7 - Year 2011

© OMICRON electronics. All rights reserved.
This manual is a publication of OMICRON electronics GmbH.
All rights including translation reserved. Reproduction of any kind, e.g., photocopying, microfilming, optical
character recognition and/or storage in electronic data processing systems, requires the explicit consent of
OMICRON electronics.
Reprinting, wholly or in part, is not permitted. The product information, specifications, and technical data
embodied in this manual represent the technical status at the time of writing and are subject to change without
prior notice.
We have done our best to ensure that the information given in this manual is useful, accurate, up-to-date and
reliable. However, OMICRON electronics does not assume responsibility for any inaccuracies which may be
present.
The user is responsible for every application that makes use of an OMICRON product.

2
 IEDScout Examples

IEDScout Examples

Contents
1 Requirements and Setup ......................................................................................................................... 4
1.1 System Requirements ......................................................................................................................... 4
1.2 Installation ........................................................................................................................................... 4
1.3 Prerequisites........................................................................................................................................ 4
Network Settings..................................................................................................................................... 4
IEDScout................................................................................................................................................. 4
Multiple Network Adapters...................................................................................................................... 4
2 Examples .................................................................................................................................................. 5
2.1 Discovering and Browsing an IED ....................................................................................................... 5
Defining the IED...................................................................................................................................... 5
Discovering the IED ................................................................................................................................ 6
Browsing the IED .................................................................................................................................... 7
2.2 Working with SCL Files ....................................................................................................................... 8
Saving an SCL File ................................................................................................................................. 8
Connecting Using an SCL File ............................................................................................................... 9
2.3 Polling Data ......................................................................................................................................... 9
2.4 Working with Reports ........................................................................................................................ 10
Enabling a Report ................................................................................................................................. 10
General Interrogation ............................................................................................................................ 10
2.5 Subscribing and Recording GOOSE ................................................................................................. 11
Subscribing using GOOSE Control Blocks ........................................................................................... 11
Accessing VLAN Information ................................................................................................................ 12
GOOSE Sniffing.................................................................................................................................... 13
Transferring GOOSE Information to Configure a CMC Test Set ......................................................... 13
Subscribing Manually ........................................................................................................................... 13
GOOSE Recording ............................................................................................................................... 14
2.6 Simulating GOOSE ........................................................................................................................... 15
Creating a GOOSE ............................................................................................................................... 15
Creating a GOOSE Sequence.............................................................................................................. 15
Running a GOOSE Sequence .............................................................................................................. 16
2.7 Analyzing Client/Server Communication ........................................................................................... 17
General ................................................................................................................................................. 17
Accessing Client/Server Traffic ............................................................................................................ 17
ACSI Sniffer .......................................................................................................................................... 17
Views and Functions ............................................................................................................................ 18
Search and Filter .................................................................................................................................. 19
Details of C/S Traffic ............................................................................................................................. 19
Drilling Down......................................................................................................................................... 20
Exporting Data and Analysis with External Protocol Software ............................................................. 21

3
 IEDScout Examples

This document provides a quick introduction to some common applications performed with IEDScout and
some tips to optimize the work with IEDScout.

1 Requirements and Setup

1.1 System Requirements

• A physical computer with x86 or x64 architecture (no virtual machine)
• Windows XP SP2 and above (32 bit only),
Windows Vista any SP level (32 bit only) or
Windows 7 any SP level (32 bit and 64 bit) operating system
• Administrator or Power User rights for the installation
• A free USB port for the USB license key
• An Ethernet adapter with TCP/IP protocol bound to it
Note: Wireless adapters typically do not work with GOOSE/GSSE
• If a firewall is present, port 102 must be opened

1.2 Installation
On executing the setup program of IEDScout, the installer will start up:
Follow the instructions provided during the installation procedure.

1.3 Prerequisites

Network Settings
Before starting work with IEDScout, the network settings on the PC have to be configured properly. It is
assumed that the user has administrator or power user rights for changing the network settings. The
network adapter must be enabled and must have a valid IP address.

IEDScout
To use the full featured IEDScout, the USB license key has to be plugged into a USB port; otherwise
IEDScout will run in evaluation mode.
In the GOOSE Tab of the IEDScout configuration, the network adapter for GOOSE must be selected in
the field Adapter; the same steps are needed for GSSE. IEDScout only displays adapters that are able to
send and receive GOOSE/GSSE messages.

Multiple Network Adapters

To avoid problems due to other programs that also use port 102 (e.g. Microsoft Outlook with Exchange
server), IEDScout must be set to use a specific adapter (a specific IP address):
In the RFC1006 tab of the IEDScout Configuration window, the Local IP must be set to the IP address of
the interface to be used for connecting to the IEDs. When the PC running IEDScout has only one network
interface, the Local IP may be left at the default value "0.0.0.0".

4
 IEDScout Examples

2 Examples

2.1 Discovering and Browsing an IED

Defining the IED

A new IED is added with the New Button in the Servers tab of the Configuration window.

A name for the new device must be specified (e.g. "Q0_S"), along with the IP address. In this example the
IED's IP address is 192.168.0.77.
If a similar device is already present, the option Use existing server definition is useful. In this case only
the parameters that differ between the two server definitions have to be changed.

Figure 1 Defining the IED (Create new Server)

The parameters needed to connect to a device should be specified in the documentation for the IED.
Usually the IP address is sufficient to connect to an IED.
If special parameters need to be set, the Advanced Button will reveal all available options.

5
 IEDScout Examples

Discovering the IED

The Discover button offers a list of servers to connect to. Pick the new server and the Server Query
Progress window will open.

IEDScout now reads the self-description of the IED. It discovers the data model of the IED and then reads
the actual values contained in the data. Depending on the size of the data model, the speed of the
connection, and the server, this may take more than a minute.
IEDScout creates a new server section for the discovered IED on the main screen. Double click on the
subsections of the IED provides access to all the services that the IED supports.
E. g. double clicking on Data opens the Data View, which will be explained later.
Additionally, Datasets and all Control Blocks (GOOSE, Reports, Logs, Sampled Values) can be accessed
from here.
Right click on the light blue colored root of the IED allows the user to Disconnect or Delete the server.

Figure 2 Connected to "Q0_S"

The status of the connection to the IED is indicated with the following icons:

– Shows whether the loaded IED is connected (green) or disconnected (gray)

– The IED has been discovered

– The IED definition has been loaded from an SCL file (will be explained below)

6
 IEDScout Examples

Browsing the IED

When one of the logical devices in the Main screen is double-clicked, the Data View will open. It is divided
into two panes.
The nesting depth in the left pane is limited to the LD level and gives an overview of the IEDs and their top
level structure. This pane is especially useful for quickly navigating between IEDs when multiple devices
are loaded.
The right pane is for inspecting the IEDs' data models in detail, down to the attribute level.

Figure 3 Data View with "Q0_S" loaded

The data tree shows the different types of objects with different icons:
• – The server (IED), the root of the data tree
• – Logical Device
• – Logical Node
• – Functional Constraint
• – Data Object
• – Data Attributes, the leafs of the tree

The Data View uses colors to signalize the status and the information source of the data.
• – Initial value, the value has not yet been updated
• – The value has been retrieved by a read command
• – Data has changed within a report
• – Data has been updated by a report General Interrogation (GI)
• – Value comes from periodic reporting
• – This value has just been written
A context menu opens when a selected data item is right-clicked with the mouse. The context menu offers
various functions to be performed with the item, such as Read, Write, Polling, etc. Depending on the
selected item (context), some functions which do not apply to that item will be disabled (grayed out).

7
 IEDScout Examples

2.2 Working with SCL Files

IEDScout provides useful features with SCL. An SCL file can be created from a discovered IED. If an SCL
file with definitions of an IED is provided, the connection and browsing process can be facilitated.

Saving an SCL File

This function is typically used to produce an ICD file for a discovered IED. There are several usages of
this SCL file: support further re-connection to the device, import of GOOSE definitions by the GOOSE
Configuration module of the OMICRON Test Universe, Simulating of the IED, etc.
The Save SCL function is accessible from the main screen via the toolbar or the File menu.

The Save SCL window opens. First, the server is selected in the "Server" list.
Specifying the IED Name is mandatory and essential to get a correct SCL file. The IED discovery process
delivers the IED Name and the LD names concatenated together without delimiters. In the SCL file, these
two names need to be stored separately. To split IED Name and LD names correctly, the IED Name has
to be known.
IEDScout tries to guess the IED Name, which succeeds when sufficiently different LD names are
contained in the server. If there is only one LD in the server or if the LD names do not differ at the first
character, IEDScout cannot make a correct guess. In this case, the user must provide the correct IED
Name. In any case, the IED Name is not arbitrary and must at least match the leading characters of the
(IED Name + LD name) string delivered by the IED.
Other information as IED Type,
Manufacturer and ConfigVersion are
optional.
As far as possible, IEDScout will correct
deviations from the standard in the
discovered data model to create a
conformant SCL file. Corrections are listed
in the "Results:" list.
When storing the SCL file, information
about the meanings of attributes of type
"Enum" is added. The default source for
this information is the file "enums.dat".
While Discover delivers only the ordinal
integer values for enumerators, the
meanings are displayed in text form when
connecting to the device using an SCL file
(see the next example).

Figure 4 Save SCL window

8
 IEDScout Examples

Connecting Using an SCL File

When connecting using an SCL file, no parameters have to be specified and the connection operation is
much faster because the data model will not be requested from the server.

Opening the SCL File

An SCL file (.icd, .scd, .cid) is opened by selecting the Open SCL function from the toolbar or the File
menu in the main screen.

It is also possible to drag-and-drop an SCL file onto the Main screen of IEDScout.
A tree view with all servers in the SCL file is displayed. The tree can be expanded to a certain level to
examine the devices offered. A selection specifies which server's data are actually loaded into IEDScout.
IEDScout creates new server sections for the selected servers on the main screen, just as if they were
found through a Discover process.

Connecting
If the addressing (for example the IP address) of the server has changed since the SCL file was created,
according modifications can be made by double-clicking on Address.
A connection is then established by simply clicking Connect in the right click popup menu of the light blue
IED root node.
Connecting to a server by using its SCL file speeds up the process considerably, since the discovery of
the data model structure is not necessary. This information is already delivered by the SCL file.
The actual data can then be read with the Read Data function in the context menu of the IED or by using
the Read function (from the context menu of a data item) in the Data View.
Additionally, the SCL file contains information about the meanings of attributes of type "Enum". This
information is then displayed in text form along with the ordinal values for enumerators.

2.3 Polling Data

Data to be polled are collected in the Polling window. All polled data can be viewed together in one place.
This is especially convenient when data from different IEDs are to be observed together, which would not
be simultaneously visible in the data view.
The Polling Window opens as soon as a data object or attribute is added for polling. Adding data items is
done in the Data View by focusing an item (DO or DA) and selecting Poll from the context menu or by
dragging & dropping items from the Data View to the Polling window.
Items can be individually removed by using the context menu in the Polling window.

Figure 5 Polling Window with data

All data are polled with the same rate. The polling interval can be selected from preset values.
The green dot on the toolbar flashes when the data are polled.
If polling is paused, the data can be refreshed manually.

9
 IEDScout Examples

2.4 Working with Reports

Enabling a Report
To enable a report from the device, a report control block (RCB) must be selected. This is done by
browsing the object model in the Data View and setting the focus on a RCB. The context menu then offers
the function Enable. The values in the RCB that are changed by IEDScout by this action are then marked
in purple.

Figure 6 Data tree with enabled report (purple)

Depending on the trigger options, the server will then send the reports to IEDScout. The updated data will
be marked red in the data tree.

General Interrogation
When the report control block is enabled (as mentioned before) and the trigger option allows a general
interrogation, the GI function triggers a report that is sent regardless of the other trigger conditions.

10
 IEDScout Examples

2.5 Subscribing and Recording GOOSE

IEDScout provides four different methods to subscribe to a GOOSE.

Subscribing using GOOSE Control Blocks

Subscribing by the Control Blocks displayed in the Main Screen

The Main screen lists all available GOOSE Control Blocks (GCBs) of the IED. When one is double-clicked,
the GCB detail window opens. The menu bar has a Subscribe button.

Figure 7 Subscribing from the GOOSE Control Block detail view

On pressing the Subscribe button, the GOOSE Subscription Window opens and the GOOSE is displayed
in detail.

Figure 8 Subscribed GOOSE

All subscription actions lead to the GOOSE Subscription Window or can be initiated from there (see
further examples).

11
 IEDScout Examples

Subscribing by the Control Blocks displayed in the Data View

With the focus on a GOOSE Control Block (GCB), the context menu (accessible via right-click) offers the
function Subscribe GCB. Selecting this function will automatically set up a GOOSE subscription.

Figure 9 Subscription using a GOOSE Control Block

Accessing VLAN Information

The GOOSE subscription also shows the VLAN information in the
"Network" branch, but IEDScout can only do so if the Ethernet
packets received actually contain such a VLAN tag.
Until a few years ago, network components were not aware of
VLANs and just passed on the entire Ethernet packets
unmodified.
Today, modern network equipment is becoming more and more
"VLAN aware" and behaves accordingly. VLANs are primarily an
issue of network management, so VLANs are primarily handled in
Ethernet switches and the VLAN tags are not intended to be
processed by the end devices. Consequently, network
components (switches, adapters, drivers) may strip the VLAN
tags from the Ethernet packets. It depends on several factors if
and where VLAN tags are stripped, but with the development of
the networking components, it becomes less likely that
applications such as IEDScout will even get the VLAN tags delivered for display and further analysis. Only
in specific cases it is possible to get the VLAN tags actually delivered. There are few helpful materials on
this, the few ones can be found by submitting an internet search for "capture vlan" or similar.
Given the situation as described above, the VLAN information is more likely to be shown as "No VLAN
tag".

12
 IEDScout Examples

GOOSE Sniffing
The GOOSE Sniffer can be started from the GOOSE Subscription window or the Action menu of the Main
window. It finds all GOOSE messages arriving at the GOOSE adapter (as specified in the Configuration
dialog).
These GOOSEs can then be subscribed with the Subscribe button. Various other functions are accessible
from the context menu of a GOOSE entry.

Transferring GOOSE Information to Configure a CMC Test Set

The GOOSE Sniffer also supports Drag & Drop or Copy & Paste to the OMICRON Test Universe GOOSE
Configuration Module to subscribe/simulate GOOSEs with the CMC test set.

Drag & Drop or Copy & Paste

Figure 10 Transferring a data from the GOOSE Sniffer to the GOOSE Configuration Module

Subscribing Manually
Additionally, a GOOSE can be subscribed "from scratch" without using the IED's data model and access
to the control blocks. All relevant GOOSE parameters must be known and specified manually. This can be
done in GOOSE Subscriptions with the Subscribe button. The GOOSE parameters have to be entered in
the opening subscription dialog.

Figure 11 Subscribing manually by specifying parameters

13
 IEDScout Examples

GOOSE Recording
IEDScout has a powerful function for recording GOOSE traffic. Complex relations between data in
multiple GOOSEs can be analyzed this way.
The data are recorded into COMTRADE files which can be analyzed in several viewer applications.
OMICRON TransView may be available for this purpose if the OMICRON Test Universe software (with
EnerLyzer) is installed.
The name template defines the location where the COMTRADE records are stored and the base file
name. Incrementing numbers are appended to the filenames for further recordings.

Figure 12 GOOSE Recording Window

The Open function will launch the application associated with the COMTARDE configuration files (CFG
file extension) to view the COMTRADE files.
When using OMICRON TransView, the maximum recording time is limited to approximately 35 minutes
with a µs resolution.
Data attributes to be included in the recording need the checkmark next to them checked. Normally, only
state changes are recorded. When the sequence number (SqNum) is included, all retransmits will be
recorded as well.
Trigger conditions can be set up with attributes selected for recording.

14
 IEDScout Examples

2.6 Simulating GOOSE

The GOOSE message to be created for the example shall have the following properties:

GOOSE Parameters
GOOSE Control Reference: IEDScout/LLN0$GO$Eval
Dataset Reference: IEDScout/LLN0$Eval_DataSet
GOOSE ID: GOOSEID
Application ID: 0x3FFF
Multicast MAC Address: 01:0C:CD:01:01:FF
Retransmission: First Interval: 1000ms, Multiplier: 2, Max Interval: 8000ms,
default strategy
Data: Boolean; Integer; BitString[4]

Creating a GOOSE
Open the GOOSE Output view by selecting GOOSE Simulations from the toolbar.

Create a new GOOSE with Add GOOSE.

In the Destination MAC address field specify the last two bytes of 01 0C CD 01 01 FF.
The initial data must be entered in the Data field.
For this example, "{False, 0, [1000]}" is the initial data. The data can also be edited with the … button
next to the Data field.
The other fields are filled out according to the parameters given above:
GoID: "GOOSEID"
GcRef: "IEDScout/LLN0$GO$Eval"
DatSet: "IEDScout/LLN0$Eval_DataSet".
Set the AppID and the VLAN parameters with the Advanced button at the Advanced Addressing Window.
The strategy can be changed through the Strategy button. For this example, the defaults are used.

Creating a GOOSE Sequence

The data shall change every second between four different states:
Step 1: {False, 0, [1000]}

Step 2: {True, 1, [0100]}

Step 3: {False, 2, [0010]}

Step 4: {True, 3, [0001]}

With the Insert Step button, four steps are inserted. The Delay field is set to 1000ms on all steps.
The corresponding data are specified in the data fields.
The GOOSE will be published as soon the setup is confirmed with OK on the Edit GOOSE/GSSE window.

15
 IEDScout Examples

Figure 13 The example GOOSE with all parameters filled in

The GOOSE and the sequence shown in Figure 13 is the one used in the evaluation version of IEDScout.

Running a GOOSE Sequence

By clicking on Run in the GOOSE Out view, the data changes every second according to the setting in the
steps.

16
 IEDScout Examples

2.7 Analyzing Client/Server Communication

General
The client/server (C/S) communication is a generic term for the "Two Party Application Association"
(TPAA), which is one of the abstract communication services (ACSI) defined in IEC 61850-7-2.
In a substation, the client is typically the station controller and the server is typically an IED such as a
protection relay and the C/S communication is mainly used for the classical SCADA data exchange.
In the context of IEC 61850, the term "MMS" is often used when C/S is actually meant. But in fact MMS
(Manufacturing Message Specification, ISO 9506) is just the specific transport protocol used to perform
the C/S communication. The specific communication service mapping (SCSM) of the abstract
communication services to the MMS protocol is described in IEC 61850-8-1, which also contains the
mapping of the GOOSE service to Ethernet. C/S communication could also be performed over alternate
transport protocols, e.g. Web-Services, which are actually considered for certain applications like wind
power generation.

Accessing Client/Server Traffic

There is a significant difference between GOOSE and C/S communication. GOOSE is an Ethernet
(network layer) multicast traffic (MCAA: Multicast Application Association). Unless dedicated filters are set
up, the Ethernet switches will replicate a received GOOSE and forward it to all connected links. So any
device can receive a GOOSE without further efforts.
With C/S communication, this is different. The C/S communication is performed over explicitly established
connections between the client and the server. The data packets are forwarded as unicast traffic, and that
means that the corresponding Ethernet packets are only forwarded on those links that actually establish
the path between the involved end points (the client and the server). Without special precautions, an
analysis tool like the IEDScout, connected to an arbitrary port on an Ethernet switch, will not receive the
packets to be analyzed.
There are two means of accessing unicast traffic: taps and mirror ports. A tap is a device that is inserted
into a network link and that replicates the traffic going over the link to additional ports, from where it can
be received for further processing. A mirror port can be typically found on managed Ethernet switches and
this port can be configured to replicate the traffic from specified other ports on the switch, similar as if a
tap was used.
So for receiving C/S communication with IEDScout, the access to the traffic of interest must be first
established as indicated above.
For capturing the C/S traffic that is caused by IEDScout itself in its role as a client, there are no special
precautions necessary as this traffic is anyway accessible for IEDScout.
IEDScout obtains the C/S traffic from the same network adapter that is selected for GOOSE.

ACSI Sniffer
The ACSI Sniffer is accessed via the toolbar from the main screen.

The function captures not only the messages related to the C/S
traffic, but also the GOOSE messages, so these two ACSI services
are covered together.
To get a better overview and for easier understanding, dedicated
views for specific kinds of traffic/messages are provided on the
ACSI level. To investigate the traffic in more detail, drilling down to
lower protocol layers (MMS and Ethernet) is also possible.
The figure on the right shows how the top level ACSI services
(defined in IEC 61850-7-2) relate with the layers below.
The mapping of the C/S services to MMS (which itself uses
TCP/IP) and the mapping of GOOSE directly to Ethernet is defined
in IEC 61850-8-1.

17
 IEDScout Examples

Views and Functions

The Client/Server + GOOSE view shows the C/S messages and the GOOSE messages together.
This view gives insight in the course of actions where C/S requests and responses and GOOSEs depend
on each other. In this regard, this is more than just an event list.
The top half of the list of events below was captured from the execution of a switch command (with SBO)
on an XCBR. When the switching happens, the course of the CB status is published via GOOSE and
when the CB has entered its new state, reports are generated.

At about half down the list, the CB is tripped via a GOOSE (e.g. published by a protection relay), the
change of the CB status is again published via GOOSE and reports are sent to the client.
By default, only GOOSE status changes are displayed. If desired, the display of GOOSE
retransmissions can be enabled by checking Retransmissions in the toolbar. This is a simple (and
thus very fast) display filter that suppresses any GOOSEs with a sequence number other than zero. Be
aware that if the first GOOSE with a new status (the one with sequence number zero) is missing for some
reason, the status change will not be visible at all when repetitions are not shown. There is no further
detection of the status changes from analyzing the status numbers.
The two kinds of communication can be separately viewed in the Client/Server and GOOSE
views.
The Report view is provided for convenience. This frequently used filtered view can be accessed in
the dedicated tab without the need to use the filter function.

18
 IEDScout Examples

Search and Filter

In any view, search and filter functions are available. A toolbar with input fields for search and filter strings
are displayed at the bottom of the list.

The Search function does not alter the amount of the displayed entries, but allows finding and stepping
through all occurrences of the search string.
The Filter function limits the amount of the displayed messages to those containing the filter string.
The string matching is case insensitive and works on all text strings (path names, time stamps, ...) that are
displayed in the different columns, even if the string is in a collapsed sub-tree that is not currently visible.
For example, filtering for "report" in the C/S view would result in a similar (not exactly the same!) display
as the Report view provides.

Details of C/S Traffic

C/S communication is mostly confirmed (only unsolicited reports are unconfirmed), so the traffic mainly
consists of request/response sequences. IEDScout detects requests and responses that belong to each
other and groups them together.
When expanding an entry in a C/S view, this grouping of the request and the associated response
becomes visible. In the figure below this is shown for the operate command.

19
 IEDScout Examples

Drilling Down
In any view, a drill down to the underlying protocol layer is possible to obtain more details.
When drilling down from a C/S view to investigate the transactions on the MMS layer, all messages
belonging to the selected C/S transaction are highlighted in the MMS view with a light yellow color.
This will reveal for instance, that a single request/response pair of the C/S layer can consist of multiple
MMS messages.
The scope of messages belonging to an ACSI transaction cannot always be determined with absolute
precision, so the highlighted range may contain some excess messages.

More details on the MMS transactions can be seen when further expanding the entries. The Expand
subtree and Collapse subtree functions are most useful with MMS, because the nesting can be rather
deep with this protocol.
The Ethernet view shows the individual Ethernet packets with only few details. To provide a focused
view, only packets belonging to IEC 61850 C/S and GOOSE communication are listed.

20
 IEDScout Examples

Exporting Data and Analysis with External Protocol Software

At any level, an ultimate drill down can be achieved by exporting all Ethernet packets belonging to a
selected scope to a PCAP file for further analysis. When choosing Dump & Analyze, a temporary file will
be created and the associated application for PCAP files will be launched to open this file. In most cases
this will be the popular Wireshark network analyzer SW. If persistent saving of the dumped packets is
required, they must be explicitly saved out of the network analyzer.
Another option is to save the data from IEDScout, using the function Save as PCAP. In this case, a path
and a name for the PCAP file have to be specified. No automatic launching of a further application takes
place in this case.
All the export functions process only the displayed entries in each view, so the filter settings apply.
For documentation purposes, the content of the view can be also exported in text format by using the
Text to Clipboard and Save as Text functions. These data can be viewed and further processed in any
text editor.

21
OMICRON is an international company serving the electrical power
industry with innovative testing and diagnostic solutions.
The application of OMICRON products allows users to assess the
condition of the primary and secondary equipment on their systems
with complete confidence. Services offered in the area of
consulting, commissioning, testing, diagnosis, and training make
the product range complete.
Customers in more than 140 countries rely on the company’s ability
to supply leading edge technology of excellent quality.
Broad application knowledge and extraordinary customer support
provided by offices in North America, Europe, South and East Asia,
Australia, and the Middle East, together with a worldwide network of
distributors and representatives, make the company a market
leader in its sector.

Contact Information / Technical Support

Americas Asia-Pacific Europe, Middle East, Africa

OMICRON electronics Corp. USA OMICRON electronics Asia Limited OMICRON electronics GmbH
12 Greenway Plaza, Suite 1510 Suite 2006, 20/F, Tower 2 Oberes Ried 1
Houston, TX 77046, USA The Gateway, Harbour City 6833 Klaus
Phone: +1 713 830-4660 Kowloon, Hong Kong S.A.R. Austria
+1 800-OMICRON Phone: +852 3767 5500 Phone: +43 5523 507-333
Fax: +1 713 830-4661 Fax: +852 3767 5400 Fax: +43 5523 507-999
info@omicronusa.com info@asia.omicron.at info@omicron.at
techsupport@omicronusa.com support@asia.omicron.at support@omicron.at

For addresses of OMICRON offices with customer service centers, regional sales offices or offices for training, consulting and
commissioning, please see the Contact section of our Web site.

www.omicron.at  www.omicronusa.com