Applied Systems Engineering ASE2000 User manual

ASE2000 Version 2 Communication Test Set
User Manual
www.kalkitech.com
Version 2.21, September 2018

ASE2000 V2 Communication Test Set User Manual 2
Copyright Notice
© 2018 Applied Systems Engineering, Inc. All Rights reserved.
This user manual is a publication of Applied Systems Engineering, Inc. and it is intended for its
customers use only. Content of this manual is copyrighted and reproduction in whole or in part, for use
other than in support of ASE products, is prohibited without the specic written permission of
Applied Systems Engineering, Inc.
Disclaimer
Information in this manual is subject to change without any notice.
Information provided in this manual is intended to be accurate and reliable. However,
Applied Systems Engineering, Inc. assumes no responsibility for its use. Applied Systems Engineering,
Inc. makes no commitment to update or keep the current information in this manual.
Contact Information
Applied Systems Engineering, Inc.
1671 Dell Avenue, Suite 200,
Campbell, California, 95008, USA
Telephone: [phone]
Fax: [phone]
Email: [email protected]
Technical Support Contact Information
Online Technical Enquiry Support: www.ase-systems.com/support
E-mail Support: [email protected]

ASE2000 V2 Communication Test Set User Manual 3
Table of Contents
1. Overview 10
2. Version 1 / Version 2 Comparison 11
2.1. Exchange Mode and Task Mode Highlights 11
2.2. Exchange Mode and Task Mode Operational Basics 12
2.3. Other Version 1 and 2 Comparisons 13
3. Software Installation 14
3.1. Windows Operating System Support 14
3.2. Hardware Requirements 14
3.3. Installation Setup 15
3.4. Installation Procedure 15
4. Quick-Start Guide 16
4.1. Physical Connection to Communication Circuit 16
4.2. Launch ASE2000 Test Set Application 16
4.3. Select Operational Mode – Task Mode or Exchange Mode 16
4.4. Selection and Conguration of Protocol 17
4.4.1. Exchange Mode Protocol Selection and Conguration 17
4.4.2. Task Mode Device Selection and Conguration 18
4.4.3. CSV Point List Import / Export 20
4.5. Protocol Specic Conguration 21
4.6. Conguration of Communication Settings 21
4.6.1. Communication Settings for Serial Data Communication 21
4.7. Select Communication Mode and Start Communicating 23
4.7.1. Exchange Mode – Master Simulation Mode 24
4.7.2. Exchange Mode – Monitor Mode 24
4.7.3. Exchange Mode – RTU Simulation Mode 24
4.7.4. Task Mode – Master Simulation Mode 24
4.7.5. Task Mode – Monitor Mode 25
4.7.6. Task Mode – RTU Simulation Mode 25
5. File Types 26
6. Communication Message Processing 27
6.1. Message Export/Import Facility 28
6.2. Message Import Wireshark Files 29
6.3. Message Import Text Files 30
6.3.1. Text Message File Structure 30
6.3.2. DNP3 Example 30
6.4. SPT Import Files 31
6.4.1. DNP3 Example 31
6.5. Message Capture Facility 31
7. Screen Layout 33
7.1. Title Line 33
7.2. Menu Bar 33
7.2.1. File Menu 33
7.2.2. Edit Menu 34
7.2.3. View Menu 34

ASE2000 V2 Communication Test Set User Manual 4
7.2.4. Tools Menu 35
7.2.5. Mode Menu 43
7.2.6. Help Menu 43
7.3. Tool Bar 44
7.3.1. Player Buttons 44
7.3.2. Time Line 45
7.3.3. Capture File Control 45
7.3.4. Communication Port Selection 45
7.4. Work Space 47
7.4.1. Drag Repositioning 47
7.4.2. Context Menu 47
7.5. Docking 47
7.5.1. Drag Repositioning 47
7.5.2. Auto Hide 47
7.5.3. Context Menu 48
7.6. Layout Persistence 48
7.7. Layout Guidelines 48
7.8. Status Line 48
7.8.1. Communication Mode 48
7.8.2. Communication Statistics 48
8. View Menu Details 50
8.1. Tasks 50
8.2. Point List View 50
8.2.1. Point List Overview 50
8.2.2. Edit Menu for Points List View 52
8.2.3. RTU Simulation and Task Mode 52
8.3. Exchange List View 53
8.3.1. Exchange View Menu 54
8.4. Line Monitor View 59
8.4.1. Edit Menu for Line Monitor View 59
8.4.2. Raw Text Export 59
8.5. Messages View 59
8.5.1. Edit Menu for Messages View 62
8.6. Event Log 62
8.6.1. Edit Menu for Event Log View 62
8.7. Line Analyzer 62
8.7.1. Edit Menu for Line Analyzer View 64
9. Exchange Mode 65
9.1. Starting Communication 65
9.1.1. RTU Simulation and Monitor Mode 65
9.1.2. Master Simulation 65
10. Task Mode 66
10.1. Task Mode Operation 66
10.2. Device Denition 67
10.2.1. Point Denition 68
10.3. Task Mode Operation, Master Simulation Mode 69
10.3.1. Task Selection and Navigation 69
10.3.2. Task Activation, General 71
10.3.3. Task Setup and Activation, Digital Control Tasks 71

ASE2000 V2 Communication Test Set User Manual 5
10.3.4. Task Setup and Activation, Analog Control Tasks 73
10.3.5. Task Setup and Activation, File Transfer Tasks 75
10.4. Task Mode Operation, Monitor Mode 77
10.5. Task Mode Operation, RTU Simulation Mode 78
11. Remote Monitoring 80
11.1. Activation 80
11.1.1. SPT Remote Monitoring Conguration 80
11.1.2. ASE2000 Remote Monitoring Conguration 81
12. Project Saving 82
13. ASE2000 Cabling 83
13.1. RS-232 Connections 83
13.2. Master Simulation Mode – RS-232 83
13.2.1. RTU/IED Simulation Mode – RS-232 84
13.2.2. Monitor Mode – RS-232 84
13.3. Modem Connections 85
13.3.1. Master Simulation Mode – Modem Connection 85
13.3.2. RTU/IED Simulation Mode – Modem Connection 86
13.3.3. Monitor Mode – Modem Connection 87
14. ASE2000 Network Protocol Use 88
14.1. Master Mode 89
14.2. RTU Mode 90
14.3. Monitor Mode 90
15. ASE2000 V2 Command Line Options 92
16. ASE BELL-202 Dual-Channel Modem Adjustment 94
16.1. Adjusting Modems with White Colored Potentiometers 94
16.2. Adjusting Modems with Orange or Yellow Colored Potentiometers 95
17. RS-232 Cable And Adapter Pin-Out 96
17.1. DB-25 Connector PIN-OUT 96
17.2. DB-9 Connector PIN-OUT 96
17.3. DB-9 to DB-25 Adaptor 97
17.4. DB-25 Null Modem Adaptor (Standard) 97
17.5. DB-9 Null Modem Adaptor (Standard) 98
17.6. ASE RS-232 Monitor Adaptor Cable 98
18. ASE2000 Kit Contents 99
18.1. Model ASE2000-USB-M 99
18.2. Model ASE2000-USB-RS 99
18.3. Model ASE2000-COM 99
19. ASE2000 Kit Components 101
19.1. ASE dual channel BCOM-USB device with two RS-232 cables, USB cable, and
BCOM-USB to ASE 2-Channel Modem power cable. 101
19.2. ASE Bell-202/CCITT V.23 Dual-Channel Modem 101
19.3. DB-25 Female-Female Gender Changer 102
19.4. DB-9 to DB-25 adapter 102

ASE2000 V2 Communication Test Set User Manual 6
19.5. RS-232 Cable with DB-9 Female and DB-25 Male 102
19.6. SafeNet USB Port and Parallel Port (LPT) dongle 103
20. BCOM-USB Device Guide 104
20.1. BCOM-USB Overview 104
20.2. BCOM-USB Device Description 104
20.3. BCOM-USB Components 105
20.4. BCOM-USB RS-233 pin-out 107
20.5. BCOM-USB I/O Driver Installation 107
20.5.1. BCOM-USB Windows 2000/XP/Vista I/O Driver Installation 108
21. BCOM-USB Windows 7 and Windows 8 I/O Driver Installation 115
21.1. BCOM-USB device Troubleshooting 125
22. ASE License/Firmware Updater 128
22.1. ASE License/Firmware Updater Overview 128
22.2. ASE License/Firmware Updater License/Firmware Updater Operation 129
22.3. ASE License/Firmware Updater New License File Installation 130
22.4. ASE License/Firmware Updater New Firmware Installation 131
22.5. ASE License/Firmware Updater Program Installation 133
23. CDCTypeI–ProtocolSpecic 134
23.1. CDC Type I – Exchange Mode 134
23.1.1. CDC Type I – Edit Exchange Denition 134
23.1.2. CDC Type I – Set RTU ID and Group 136
23.1.3. CDC Type I – Exchange Mode Line Monitor 136
23.1.4. CDC Type I – Exchange Mode Master Simulation 136
23.1.5. CDC Type I – Exchange Mode RTU Simulation 136
23.2. CDC Type I – Task Mode 137
23.2.1. CDC Type I – Task Mode Line Monitor 137
23.2.2. CDC Type I – Task Mode Master Simulation 137
23.2.3. CDC Type I – Task Mode RTU Simulation 138
24. CDCTypeII–ProtocolSpecic 139
24.1. CDC Type II – Exchange Mode 139
24.1.1. CDC Type II – Edit Exchange Denition 139
24.1.2. CDC Type II – Set RTU ID 141
24.1.3. CDC Type II – Exchange Mode Line Monitor 141
24.1.4. CDC Type II – Exchange Mode Master Simulation 141
24.1.5. CDC Type II – Exchange Mode RTU Simulation 141
24.2. CDC Type II – Task Mode 142
24.2.1. CDC Type II – Task Mode Line Monitor 142
24.2.2. CDC Type II – Task Mode Master Simulation 142
24.2.3. CDC Type II – Task Mode RTU Simulation 143
25. Conitel–ProtocolSpecic 144
25.1. Conitel – Exchange Mode 144
25.1.1. Conitel – Edit Exchange Denition 144
25.1.2. Conitel – Exchange Mode Set RTU ID and Group 146
25.1.3. Conitel – Exchange Mode Line Monitor 146
25.1.4. Conitel – Exchange Mode Master Simulation 146
25.1.5. Conitel – Exchange Mode RTU Simulation 146

ASE2000 V2 Communication Test Set User Manual 7
25.2. Conitel – Task Mode 147
25.2.1. Conitel – Task Mode Line Monitor 147
25.2.2. Conitel – Task Mode Master Simulation 147
25.2.3. Conitel – Task Mode RTU Simulation 148
25.2.4. Conitel – Mapping Output Controls to Change Input Point Values 149
26. DNP3–ProtocolSpecic 150
26.1. DNP3 – Exchange Properties Menu 150
26.1.1. DNP3 – Fields 151
26.1.2. DNP3 – Object List 152
26.1.3. DNP3 – Multiple Object Exchanges 152
26.1.4. DNP3 – Variation and Qualier Codes 153
26.1.5. DNP3 – Point Value Simulation 155
26.2. DNP3 – Properties Tabs 156
26.2.1. DNP3 – Protocol Tab (Exchange Mode - Serial and LAN/WAN) 156
26.2.2. Default Exchange Values 157
26.3. DNP3 Options Sub-Tab 158
26.3.1. DNP3 Serial – Options Sub-Tab (Exchange Mode) 159
26.3.2. DNP3 Serial – Options Sub-Tab (Task Mode) 160
26.3.3. DNP3 LAN/WAN – Options Sub-Tab (Exchange Mode) 161
26.3.4. DNP3 LAN/WAN – Options Sub-Tab (Task Mode) 162
26.3.5. DNP3 LAN/WAN – Secured Sockets Layer (SSL) 163
26.4. DNP3 Simulation Sub-Tab 164
26.4.1. DNP3 – Simulation Sub-Tab (Exchange Mode – Serial and LAN/WAN) 164
26.4.2. DNP3 – Simulation Sub-Tab (Task Mode – Serial and LAN/WAN) 165
26.4.3. DNP3 – Mapping Output Controls to Change Input Point Values 166
26.4.4. DNP3 Secure Authentication Sub-Tabs 167
26.4.5. DNP3 – Secure Auth. V2 Sub-Tab (Task Mode – Serial and LAN/WAN) 167
26.4.6. DNP3 – Secure Auth. V5 Sub-Tab (Serial and LAN/WAN) 168
26.5. DNP3 – Secure Authentication Setup 169
26.5.1. DNP3 – Enabling Secure Authentication 169
26.5.2. DNP3 – ASE2000 Protection 169
26.5.3. DNP3 – Update Keys Overview 170
26.5.4. DNP3 – Update Key Entry 170
26.5.5. DNP3 – Other Secure Authentication Properties 171
26.6. DNP3 – Exchange Mode 172
26.6.1. DNP3 – Exchange Mode Line Monitor 172
26.6.2. DNP3 – Exchange Mode Master Simulation 172
26.6.3. DNP3 – Exchange Mode RTU Simulation 173
26.7. DNP3 – Task Mode 174
26.7.1. DNP3 – Task Mode Line Monitor 174
26.7.2. DNP3 – Task Mode Master Simulation 175
26.7.3. DNP3 – Task Mode RTU Simulation 176
26.8. DNP3 – Certication Tests 178
26.9. Secure Authentication Version 5 Implementation Notes 178
26.9.1. General 178
26.9.2. Shared Update Keys 178
26.9.3. Symmetric Update Key Change 178
26.9.4. Asymmetric Update Key Change 178
26.9.5. AES-GMAC MAC Algorithm 179
27. Harris5k/6k–ProtocolSpecic 181

ASE2000 V2 Communication Test Set User Manual 8
27.1. Harris 5k/6k – Exchange Mode 181
27.1.1. Harris 5k/6k – Edit Exchange Denition for Data Dump 181
27.1.2. Harris 5k/6k – Set RTU ID and Group 185
27.1.3. Harris 5k/6k – Exchange Mode Line Monitor 185
27.1.4. Harris 5k/6k – Exchange Mode Master Simulation 185
27.1.5. Harris 5k/6k – Exchange Mode RTU Simulation 185
27.2. Harris 5k/6k – Task Mode 185
27.2.1. Harris 5k/6k – Task Mode Line Monitor 186
27.2.2. Harris 5k/6k – Task Mode Master Simulation 186
27.2.3. For Harris 5k/6k, the Task Activities are: 186
27.2.4. Harris 5k/6k – Task Mode RTU Simulation 186
28. IEC60870-5–ProtocolSpecic 187
28.1. IEC 60870-5 – Exchange Properties Menu 187
28.2. IEC 60870-5 – Fields 188
28.3. IEC 60870-5 – Information Object Properties 191
28.3.1. IEC 60870-5 – Enterable from the Edit Exchange Properties Menu 191
28.3.2. IEC 60870-5 – Enterable from the Information Object Properties Menu 191
28.4. IEC 60870-5 – Protocol Tab 194
28.4.1. IEC 60870-5-101 Protocol Tab 194
28.4.2. IEC 60870-5-104 Protocol Tab 195
28.5. IEC 60870-5-101 Tab 196
28.6. IEC 60870-5-104 Tab 199
28.7. IEC 60870-5 – All Modes and Operational Types 201
28.8. IEC 60870-5 – Exchange Mode 201
28.8.1. IEC 60870-5 – Exchange Mode Line Monitor 201
28.8.2. IEC 60870-5 – Exchange Mode Master Simulation 201
28.8.3. IEC 60870-5 – Exchange Mode RTU Simulation 201
28.9. IEC 60870-5 – Task Mode 202
28.9.1. IEC 60870-5 – Task Mode Line Monitor 203
28.9.2. IEC 60870-5-101 Task Mode Master Simulation 203
28.9.3. IEC 60870-5-104 Task Mode Master Simulation 204
28.9.4. IEC 60870-5 – Task Mode RTU Simulation 205
28.9.5. IEC 60870-5 – Task Mode File Transfer 205
29. Modbus–ProtocolSpecic 208
29.1. Modbus – Exchange Mode 208
29.1.1. Modbus – Edit Exchange Denition 208
29.1.2. Modbus – Set RTU ID and Group 210
29.1.3. Modbus – Exchange Mode Line Monitor 210
29.1.4. Modbus – Exchange Mode Master Simulation 210
29.1.5. Modbus – Exchange Mode RTU Simulation 210
29.1.6. Modbus – Task Mode 210
29.1.7. Modbus – Task Mode Line Monitor 210
29.1.8. Modbus – Task Mode Master Simulation 210
29.1.9. Modbus – Task Mode RTU Simulation 211
29.1.10. Modbus – Conguring Output Controls to Change Input Point Values 212
30. Telegyr8979–ProtocolSpecic 213
30.1. Telegyr 8979 – Exchange Mode 213
30.1.1. Telegyr 8979 – Edit Exchange Denition 213
30.1.2. Telegyr 8979 – Set RTU ID and Group 214

ASE2000 V2 Communication Test Set User Manual 9
30.1.3. Telegyr 8979 – Exchange Mode Line Monitor 214
30.1.4. Telegyr 8979 – Exchange Mode Master Simulation 214
30.1.5. Telegyr 8979 – Exchange Mode RTU Simulation 215
30.2. Telegyr 8979 – Task Mode 215
30.2.1. Telegyr 8979 – Task Mode Line Monitor 215
30.2.2. Telegyr 8979 – Task Mode Master Simulation 216
30.2.3. Telegyr 8979 – Task Mode RTU Simulation 217
30.2.4. Telegyr 8979 – Mapping Output Controls to Change Input Point Values 218

ASE2000 V2 Communication Test Set User Manual 10
1. Overview
Welcome to ASE2000 Version 2, the rst major release of the ASE2000 Communication Test Set
since it was rst introduced in 1998. ASE2000 Version 2 contains all the functionality of Version
1 plus several new features, enhancements for ease of use, and upgrades requested from our
many users over the years.
The ASE2000 is a communication protocol analyzer and communication test tool designed
for operation in the SCADA industry with emphasis on protocols used predominantly in the
electric power utility industry. The ASE2000 supports over 80 such protocols, both serial and
network based. As a full-featured SCADA communication test tool, the ASE2000 supports three
basic modes of operational testing; Line Monitor Mode, Master Simulation Mode, and RTU
Simulation Mode. These are essentially functional test modes and exist within the two ASE2000
operational modes; Exchange Mode and Task Mode.
Line Monitor Mode is one of the primary uses of the ASE2000 and is used to provide visibility into
communication occurring between a master station and remote devices (RTUs, IEDs, or PLCs).
As such, one of the main features of the ASE2000 is the capability to operate as a line monitoring
device, presenting communication message data in raw (numeric) format, and also interpreting
those messages into protocol specic English text for ease of understanding. Input point values
are extracted from the message and can be viewed in a separate tabular formatted view.
In addition to monitoring communication on a serial line or network connection, the ASE2000
can also operate as either a master or remote device to further exercise, test, and diagnose
problems.
Master Simulation Mode provides the ability to simulate a master and to issue messages to
exercise and diagnose problems in a remote device. All information and views available in
Line Monitoring mode are also available in Master Simulation mode. The main di󰀨erence is
operational in that the ASE2000 takes the place of the master in transmission of messages to
the remote device.
RTU Simulation Mode provides the ability to simulate one or more remote devices to exercise the
master and diagnose potential problems. All information and views available in Line Monitoring
mode are also available in RTU Simulation mode. The main di󰀨erence is operational in that the
ASE2000 takes the place of the remote device (or devices) in transmission of messages to the
master.
For video demonstrations of ASE2000 Communications Test Set V2, visit the Applied Systems
Engineering website: http://www.ase-systems.com/videos/trainingvideo.asp.
1

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
di󰀨erent look and feel than Version 1, there was a signicant e󰀨ort 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 signicant di󰀨erence 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 di󰀨erent 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 conguration 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 conguration 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 congured
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 specic
to the task group. Instead of conguring individual exchanges as in Exchange Mode, the user
must congure devices (RTU, IED, PLC, etc.) in terms point types and point counts and the
device conguration is used in Task Mode to automatically congure the appropriate protocol
message for the desired task. Once a device conguration 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

ASE2000 V2 Communication Test Set User Manual 12
2.2. Exchange Mode and Task Mode Operational Basics
From an operational perspective:
• Exchange Mode operates as an ASE2000 Version 1 Test Set. The user selects a protocol,
is presented with an applicable set of exchanges (messages), congures and enables one
or more of these exchanges, and starts communication. Master Simulation, RTU Simulation,
and Monitor modes appear very similar, if not identical, to those in Version 1. Some manual
editing of the default exchanges to account for specic point congurations may be necessary
prior to start of communication. The actual editing steps required are largely dependent on the
protocol selected and is very similar to Version 1 editing requirements.
• Task Mode communication is based on point conguration information for a particular device.
Before starting Task Mode operation for the rst time, the user must dene one or more devices
(RTUs, IEDs, PLCs). The properties for dening a device include a protocol, device address,
and point conguration information (point types, addresses, and counts). Device denition is
persistent (retained when the ASE2000 is stopped and restarted). The user starts Task Mode
operation by rst selecting a device from the pre entered list. The ASE2000 responds by
displaying a list of tasks applicable to the protocol of the selected device. Tasks are grouped
in functional categories such as Initialize, Acquire Data, and Time Sync. The user proceeds by
selecting a grouping and a task within the selected group.
In Master Simulation mode, communication is started by selecting one of the Transmit ICONS
(Send Once or Send Continuously). The ASE2000 automatically transmits messages required
to accomplish the selected task.
Monitor Mode contains a single task, selection of which starts the line monitoring process. Data
response interpretation uses point information entered during the device conguration step.
For some protocols, such as Harris, Conitel, and CDC, the ASE2000 can only parse point data
from a communication message if it knows, in advance, the device’s point conguration. For
these, message interpretation replies on correct user data base conguration information entry.
For other protocols such as IEC and DNP3 where point conguration can be determined from the
communication message, the ASE2000 automatically creates data base entries for undened
points. For these protocols, data base conguration information denition is desirable, but not
100% required. It su󰀩ces to enter only the correct device address or ID.
Task Mode monitoring is oriented to a single device. If you wish to monitor multiple devices on
a communications line, and have a protocol that requires advanced knowledge of the devices
conguration then you may nd the Exchange Mode better suited for this operation.
RTU Simulation mode also contains a single task. The ASE2000 builds response messages
based on point information entered during the device conguration step. Complete point
conguration information must be entered for all RTU Simulation devices being used, regardless
of protocol.
During online operation in RTU Simulation mode, values for individual points can be manually
entered in the Point Values view.
Both Exchange and Task Mode support RTU simulation of a single device. Task Mode enforces
this by only responding to messages addressed to the selected device.

ASE2000 V2 Communication Test Set User Manual 13
2.3. Other Version 1 and 2 Comparisons
• Line Monitor View. Both ASE2000 Versions 1 and 2 show master/remote communication
messages in a Line Monitor View with Interpreted Data at the right and Raw Data at the left.
The entirety of each message is always shown. For ASE2000 Version 1, this is the only way
to view communication line tra󰀩c. ASE2000 Version 2 supports this view as well as the new
Messages View.
• Messages View. This view provides an alternate format presentation of master/remote
communication messages, one message per line, with time, direction, and message name.
This compact format allows presentation of many more messages, in the same monitor space,
than the Line Monitor view, and makes it easier to locate a particular message. Clicking on
any message generates an expanded view of that message, frequently with more information
than contained in the Line Monitor View. The Messages View is useful when the user wants
to see details of selected messages only. The Line Monitor View is useful to see details on
all messages.
• Tool Bar. In response to user requests, the layout has been changed to include ICONs for
frequently selected options.

ASE2000 V2 Communication Test Set User Manual 14
3. Software Installation
The ASE2000 Version 2 Test Set is a .NET application that can operate under Windows XP,
Windows Vista, or Windows 7 and 8 and requires installation of both ASE and Microsoft
components.
ASE
• ASE2000 Version 2 software
• BCOM-USB or USB Dongle I/O driver
Microsoft
• .NET Framework 4 (Later releases of theASE2000 may require a newer version of Framework).
• SQL Server, Compact Edition Version 3.5
3.1. Windows Operating System Support
ASE2000 Version 2 operates under Window XP, Vista, Windows 7 and 8. It is not supported on
older Microsoft operating systems or in any non-Windows operating system. A single ASE2000
executable is supported on both 32-bit and 64-bit versions of the operating systems but requires
installation of the appropriate I/O driver, 32-bit or 64-bit, for the Windows system being used.
3.2. Hardware Requirements
ASE2000 Version 2 operation requires an ASE-manufactured BCOM-USB device or USB
Dongle. (An exception exists for trial mode).
The ASE2000 Version 2 will not operate with an ASE PCMCIA communication card unless
a BCOM-USB or USB Dongle is also present.
ASE’s BCOM-USB device contains two RS-232 channels both capable of bit or byte
communication. It also supports 5 VDC power and RS-232 connection to ASE’s dual channel
modem, similar to connection with ASE’s PCMCIA card.
Users with a PCMCIA-based ASE2000 Version 1 package and wishing to upgrade to Version
2 must also upgrade their PCMCIA card to a BCOM-USB device or ASE USB Dongle. Contact
ASE sales at [email protected] for details on the upgrade process.
ASE2000 Version 1 will continue to operate with the BCOM-USB device as long as release
1.47 or later is installed. That is, upgrade customers will be able to use Version 1 or Version 2
software with the BCOM-USB device. Upgrade customers are allowed to retain their PCMCIA
card until the new BCOM-USB device is delivered.
For serial operations, the ASE2000 can use both ports on the USB-BCOM board or any other
serial port as long as it is supported by a Windows compatible COM port I/O driver.
For network operation, the ASE2000 operates over any standard network device (NIC) using a
standard Windows I/O driver.
3

ASE2000 V2 Communication Test Set User Manual 15
3.3. Installation Setup
Microsoft components, .NET Framework and SQL Server, if not already present, will be
automatically installed during the ASE2000 installation process. Only the English language
versions will be automatically installed. If non-English versions are required, they should be
installed manually before the ASE2000 installation. This requires Internet connection.
3.4. Installation Procedure
To install and run the ASE2000 Version 2:
• For non-English operation, make sure the appropriate language .NET Framework and Compact
SQL components are installed before installing the ASE2000
• Install the ASE2000 Version 2 software. This will install .NET Framework and Compact SQL
components if required.
• For a fully licensed version, install the I/O driver for the ASE BCOM-USB dual channel device
or USB key. Install the driver version appropriate for your Windows version (32-bit or 64-bit).
• For a trial version, download and install a trial version setup program from www.ase-systems.
com. More details can be found on that web site

ASE2000 V2 Communication Test Set User Manual 16
4. Quick-Start Guide
The following “Quick-Start” sections contain step-by-step procedures that will enable the user to
quickly get “up-and-running” for basic test set operations. Quick-Start procedures are provided
for the Operational Modes, Task and Exchange, and for the Communication Modes, Master
Simulation, RTU Simulation, and Monitor.
The procedures consist of steps which are common for any test set operation and steps that are
protocol dependent. The set-up for any test set operation consists of the following main areas:
1. Physically connect Test Set PC to the communication circuit
2. Launch ASE2000 Test Set application
3. Select Operational Mode, Task Mode or Exchange Mode
4. Select and congure protocol
5. Congure communication settings
6. Select Communication Mode and start communicating
Additional “quick-start” information is contained in protocol specic sections. These sections can
be located by performing a search on the string “quick-start” (omit the quotes).
4.1. Physical Connection to Communication Circuit
The rst step of set-up is the physical connection of the test set PC to the communication circuit.
How the test set PC is connected to the communication circuit depends on a number of factors
but it is basically determined by the physical characteristics of the communication circuit and the
test set Communication Mode to be used. Refer to the diagrams and descriptions contained in
the section ASE2000 Cabling for the conguration that matches the test environment to be used.
Once the physical connection has been made, proceed to the next step.
4.2. Launch ASE2000 Test Set Application
From the Windows Start button, select “All Programs > ASE>ASE2000 V2 Communications Test
Set>ASE2000 V2 Comm Test Set” or, if a shortcut was previously created on the desktop, select
the ASE2000 V2 icon to launch the ASE2000 application.
4.3. Select Operational Mode – Task Mode or Exchange Mode
Once the ASE2000 application has started, the next step is to select the desired Operational
Mode. If it is the rst activation of the ASE2000 software on the PC, the ASE2000 will, by default,
start in Exchange Mode. If there have been previous executions of the ASE2000 on the PC, the
default Operational Mode will be the mode the test set was in upon exit of the previous execution.
Also, if the last Operational Mode was Exchange Mode and the test environment was saved in a
MONX le, the last used MONX le will automatically be opened on start-up. If in Task Mode at
the time of exit of the previous execution, then Task Mode will be the default start-up Operational
Mode and the default “active RTU” will be the last RTU selected. To select other than the default
Operational Mode, select Mode from the task bar then select the desired mode.
4

ASE2000 V2 Communication Test Set User Manual 17
4.4. SelectionandCongurationofProtocol
The method for selection and conguration of protocol will depend on the Operational Mode.
4.4.1. ExchangeModeProtocolSelectionandConguration
In Exchange Mode, protocol selection is performed in one of four ways:
• Default protocol on start-up – If the default Operational Mode on start-up is Exchange Mode
and there was a saved “MONX” le during the previous execution, the last used MONX le will
automatically be loaded on start-up. This will establish operational parameters based on what
was previously set in the MONX le.
• Open existing MONX le – To establish an operating environment based on a previously
saved MONX le, from the task bar select “File > Open” and browse to the folder containing
the previously saved MONX le. Select the le and then select “Open”. This will establish
operational parameters based on what is contained in the MONX le.
• Open existing MON le – A MON le is similar to a MONX le, but created by ASE2000 Version
1 software. The procedure for opening a MON le is similar to opening a MONX le. The le
type, MON or MONX, is selectable from a pull down list in the bottom right portion of the le
open menu.
• Select protocol from protocol menu – On initial execution of the test set software or if a protocol
is required for which there is no existing MONX le, the required protocol is selected from
the Available Protocols menu. From the task bar select “File > Select Protocol” then select
the required protocol from the list. The Exchange List view will be updated to contain the
set of exchanges (commands, protocol messages) specic to the selected protocol. All other
operational parameters will be set to default values and will have to be modied for the current
test environment. This may include communication settings, device specic settings (RTU ID,
point conguration, etc.), and protocol specic settings.

ASE2000 V2 Communication Test Set User Manual 18
4.4.2. TaskModeDeviceSelectionandConguration
In Task Mode, protocol selection and conguration is accomplished by selecting a device where
protocol is a property of the device selected. Device selection is performed in one of three ways:
• Default device on start-up – If the default Operational Mode on start-up is Task Mode and
there was an “active” device during the previous execution, the last active device will be the
default active device on start-up.
• Selectpreviouslydeneddevice – To select a device that is di󰀨erent than the current active
device, select from the list of displayed devices in the “Task” window. If the required device
has been previously dened but does not appear in the list of displayed devices, select “Edit
> Congure RTUs…” and check the “Display” check box for the desired device then select
“Finish”. The device should now be displayed in the devices area of the Task window and can
be selected as the active device by clicking on the line containing the device.

ASE2000 V2 Communication Test Set User Manual 19
• Denenewdevice – On initial execution of the test set software or if a new device denition is
required, use the “Congure RTUs Wizard” to dene the new device. Select “Edit > Congure
RTUs…” to bring up the Congure RTUs Wizard page. On the line containing the *, enter the
device Name, Id, and select the appropriate protocol from the Protocol drop-down list. When
the device information has been entered, select the “Next>>” button which will bring up the
point conguration display. Using the entry elds, enter “Point Type”, “First Point Id”, and “Point
Count”. When the point conguration entry is complete, select the “Finish” button to exit the
Congure RTUs Wizard.
Enter device name, select device protocol from pull-down list and enter device (RTU) Id. Note
that not all protocols are fully supported in Task Mode. If the box in the Display column is checked,
the device is Active and will appear in the Task pane. Then, select Next to enter device point
conguration.

ASE2000 V2 Communication Test Set User Manual 20
4.4.3. CSV Point List Import / Export
A new RTU and point list may also be imported from text les. The le format used is CSV (comma-
delimited values), a text-viewable format interchangeable with Excel and other applications. In
some regions, characters other than comma are used as delimiters and are also supported.
A simple example of the le format looks like this (as viewed in Notepad):
Name,Protocol,Id,PointName,PointType,PointId
Conitel,Conitel 2020,5,,AI,0
Conitel,Conitel 2020,5,,AI,1
In Excel, this same le appears as:
Name Protocol Id PointName PointType PointId
Conitel Conitel 2020 5 AI 0
Conitel Conitel 2020 5 AI 1
In the above example, the RTU name is ‘Conitel’, the Protocol is ‘Conitel 2020’, and the RTU Id is
5. Each line denes a point of type ‘AI’; the rst with a point Id of 0 and the second is 1. Note that
no point names are provided, but the delimiting commas are still required to maintain positioning
order with the header description in the rst line.
Other point elds may be provided, but the minimum requirement is for PointType and PointId to
be provided with a header line and at least one data point. The minimum data is therefore:
PointType,PointId
AI,0
During import, the user is prompted for additional information necessary to create the RTU: RTU
Name, Protocol and RTU Id.