ASE2000 V2 Communication Test Set User Manual 11
2. Version 1 / Version 2 Comparison
Version 1 of the ASE2000 Communication Test Set was rst released in 1998 with thousands of
copies currently in use worldwide. And, while some areas of ASE2000 Version 2 have a slightly
dierent look and feel than Version 1, there was a signicant eort made to provide a familiar
operating interface for users already familiar with Version 1 to minimize the learning requirement
in making the transition from Version 1 to Version 2.
2.1. Exchange Mode and Task Mode Highlights
The most signicant dierence between ASE2000 Version 1 and Version 2 is the addition of Task
Mode operational mode. ASE2000 Version 1 has a single, unnamed, operational mode but, with
the addition of Task Mode in Version 2, it became necessary to distinguish between the two
Version 2 operational modes. In Version 2, the test set features provided in Version 1 as well as
a Version 1 “look and feel” is available in Version 2 Exchange Mode and, to a certain extent, can
be thought of as Version 1 “compatibility mode”. The main conceptual dierent between the two
modes is in the way communication is organized. For the most part, the same capabilities exist
in both Exchange and Task Modes. In addition, Task Mode supports some complex operations
such as le transfers and embedded DNP3 security messages. These capabilities are only
partially available in Exchange Mode. Exchange Mode can support multiple operations, such
as scanning a device for data while also periodically issuing control output requests. Task Mode
currently supports single operations only.
Exchange Mode operations are based on the selection and conguration of one or more
protocol messages or exchanges. The terms message, protocol message, and exchange will
be used interchangeably in this document. The user selects one or more messages, edits them
as necessary for the point conguration of the target device, and enables communication for
the appropriate functional mode; Monitor, Master, or RTU. Some detailed knowledge of the
protocol may be required for message preparation. Content of all messages must be congured
in advance and message content cannot be edited once communication starts.
Task Mode is a new mode of operation introduced in Version 2 and is intended to provide a
simple, easy to use interface to commonly used test set functions that do not require a detailed
knowledge of the protocol. As the name implies, it presents a “task” oriented interface for selecting
test set functionality. For example, instead of a list of individual exchanges, the user is presented
with a set of functional “tasks” such as “Initialization”, “Acquire Data”, ”Controls”, etc. Within each
task group is a set of exchanges that, for the selected protocol, provide the functions specic
to the task group. Instead of conguring individual exchanges as in Exchange Mode, the user
must congure devices (RTU, IED, PLC, etc.) in terms point types and point counts and the
device conguration is used in Task Mode to automatically congure the appropriate protocol
message for the desired task. Once a device conguration is entered, it is saved permanently
is a device database where it can be re-selected for future test sessions. When operating in
Task Mode, Master Simulation and RTU Simulation actions are performed on a single, selected
device. Monitor Mode supports monitoring of one or more selected devices.
2
To Next Page
Loading...
Need help?
General
