The ASE2000 Knowledge Database is an accumulated collection of items that describe various problems and situations that have been encountered with the ASE2000 Test Set and the solutions to those problems. Click on the "Problem Description" that best fits your situation to navigate to the full problem description and resolution.
Apply the "Windows Library Update" under Service Packs.
Item:
2
Subject:
Cannot Access Help System
Date:
November 4, 1999
Problem:
Cannot access the ASE2000 Help Topics.
Resolution:
The ASE2000 help system is HTML-based and requires browser support routines. These are installed as a side effect of using Microsoft's Internet Explorer. Explorer 3.02 or later is required; 4.0 is recommended.
Item:
3
Subject:
Transmission settings: Pre-Mark, Post-Mark
Date:
December 9, 1999
Problem:
Pre-mark and Post-mark settings are not being used.
Resolution:
Pre-mark and post-mark processing is not supported with standard PC COM ports, or in "Native Async" mode on an ASE I/O card. FOR ASE cards, native async mode is enabled from Properties>Communication>Line.
Item:
4
Subject:
Transmission settings: Switched Carrier
Date:
January 6, 2000
Problem:
The ASE2000 will not operate correctly using switched carrier mode. Constant carrier works OK.
Resolution:
This is a problem with standard COM ports under Windows 95 or 98. There is no problem with COM ports under Windows NT or with an ASE I/O card under any operating system. The problem resides in the Windows I/O driver's control of RTS/CTS signals. See Microsoft error report at http://support.microsoft.com/support/kb/articles/Q140/0/30.asp
Item:
5
Subject:
DNP 3
Date:
August 7, 2000
Problem:
Class Data Scans Setup for RTU Simulation.
Resolution:
This document describes ASE2000 Communication Test Set procedures to configure "RTU Simulation Mode" Class Data Scan responses for DNP 3 protocol. Each Class Data response includes a set of one or more DNP 3 data objects appropriate to the class being requested. The complete set of DNP 3 data objects is listed in the ASE2000's Exchange List view.
In RTU Simulation mode, after receiving a request for Class 0, 1, 2, or 3 data, the ASE2000 compiles a response from all enabled and properly configured exchanges in the requested class or classes. Class 0 data includes all "Static Objects". Class 1, 2, and 3 include all "Event Objects". The ASE2000 does not differentiate between Class 1, 2, and 3 requests. There is no way to assign an event object to only class 1, 2, or 3 and exclude it from the other two classes in that set.
The complete set of applicable Class Data objects are shown in the following table. DNP 3 supports objects other than listed below, but those cannot be included in Class Data responses.
Static Class Objects
Event Class Objects
Code
Description
Code
Description
1
Binary Input
2
Binary Input Change
10
Binary Output Status
20
Binary Counter
21
Binary Counter Change
22
Frozen Counter
23
Frozen Counter Change
30
Analog Input
31
Analog Change Event
32
Frozen Analog Input
33
Frozen Analog Event
40
Analog Output Status
To include a given exchange in a class data response:
Enable the exchange
Enter a response variation
Specify point indices by entering a response qualifier code
Optionally, enter point value simulation parameters
Configuration steps are performed from each Exchange's Edit Exchange Properties menu; highlight the exchange and select EDIT and EDIT EXCHANGE PROPERTIES.
To Enable an Exchange
Set the transmit flag, located in the Exchange Flags section
To Specify a Response Variation
Select from the Variation pull-down list. If you omit this step, a default variation will be selected for you.
To Enter a Qualifier Code
Select the Qualifier Setup target and any valid qualifier except All Points. To be compliant with DNP 3 Subset Definitions, you should only select one of the qualifiers described below.
For static objects, select Range Of Points, and enter indices in the Starting Point and Ending Point fields.
For event objects, select List of Points or One Point. This allows individual point index entry for each event. For One Point, the point index is entered from the Qualifier Setup menu. For List Of Points, first select the Edit List Of Points target. Next, for each point, select Add and enter a point index. The same index may be entered more than once to generate multiple entries for the same point.
To Enter Point Simulation Parameters
Point simulation parameters instruct the ASE2000 how to change data point values just before building each scan response message. Instructions apply to all points in an exchange. If different points require different instructions, use Copy and Paste to duplicate applicable exchanges and specify separate point indices and simulation parameters for each. The ASE2000 can generate responses with multiple objects of the same type, if multiple exchanges are enabled.
For each exchange:
Select the Object Properties target
Check any applicable quality code. These codes are set in the Flags field for appropriate objects and variations
Enter Value. For Analog and Counter objects, this value is used for all points. For Binary objects, each entry specifies values for eight points. The least significant bit specifies the value of the first point, continuing to the eighth bit for the eighth point. If more than eight points are defined, the pattern starts over with the ninth point and every eight thereafter.
The nth point refers to the nth point transmitted, regardless of point index. For example, assume a Binary Input Change object returning changes for points 2, 5, and 8, in that order. The value of the first point returned (index 2) is specified in the least significant bit of the value field. Point 5 is the next bit (0x02) and point 8 the third bit (0x04). The other five bits are unused.
To cause object values to change in each response, enter point-modeling parameters.
For Binary Objects, enter a Mask. Before each transmission, a new Value is computed by an exclusive OR between the Mask and current Value.
For Analog Objects, enter an Increment. Before each transmission, a new Value is computed by adding the Increment to the current Value. After the high limit is reached, new values are computed by subtracting the Increment from the current Value. After the low limit is reached, values computation reverts to addition. Low and high limits can be found under Properties, Point Configuration, and Analog Point Info.
For Counter Objects, enter an Increment. Before each transmission, a new Value is computed by adding the Increment to the current Value. Values wrap around at the counter high limit, but continue to increase thereafter. The high limit can be found under Properties, Point Configuration, and Pulse Point Info.
Item:
6
Subject:
Required Baud Rate not on Pull-Down List
Date:
August 14, 2000
Problem:
The Baud Rate pull-down list on the Communication Properties page shows standard baud rates from 110 to 19200. How can I specify a baud rate other than one of those listed?
Resolution:
The ASE2000 supports many communication speeds. Since it is not possible to list them all, only the more common ones are shown. Other speeds can be specified by simply typing the desired value in the Baud Rate data entry field, instead of selecting an entry from the pull?down list.
There are some limitations set by the hardware, as explained below:
The ASE BCOM PCMCIA card operates at speeds up to 56KB (57,600), or any speed that divides evenly into 57,600.
The ASE BCOM2 ISA card operates at speeds up to 9,600, or any speed that divides evenly into 9,600.
For standard PC COM ports, refer to your PC documentation. Within the capabilities of your PC hardware, speeds up to 57,600 are supported.
For ASE manufactured BCOM/PCMCIA and BCOM2/ISA cards, ASE recommends that the Native Async Mode box be checked when running byte protocols at speeds of 9,600 baud or higher.
Other limitations may exist when using high speeds on slow processors.
Item:
7
Subject:
Exchange Message Filtering
Date:
August 25, 2000
Problem:
Limit messages displayed on Line Monitor View to certain RTUs or Exchanges.
Resolution:
This document describes procedures for limiting information displayed on the ASE2000's Line Monitor view. The primary use of the feature occurs when running in Monitor mode, listening to communication between a master and a set of RTUs. To diagnose problems for one RTU, it is useful to see only messages for the RTU in question, and not messages for other RTUs. A secondary use is to display only specific messages, such as analog scans, and to discard all others.
In normal mode, the Test Set displays, on the Line Monitor view, all communication line exchanges (messages) detected. Names are associated with exchanges that can be identified. Others are labeled as Unknown.
To configure the Test Set to limit the set of exchanges displayed, you must first enable the option:
Properties>Display>General>Display-enabled Exchanges Only
This instructs the Test Set to display only exchanges that are defined and enabled. The initial effect of this option is just to remove Unknown exchanges from the Line Monitor view.
Further filtering requires editing individual exchanges. By default, each exchange is address insensitive. For example, a protocol with an Analog Scan exchange can identify Analog Scan messages to and from any RTU address. To modify such an exchange, request its Edit Exchange Properties menu (Edit>Edit Exchange Properties) and set the RTU address field to the desired value, such as 1. (Some protocols may use other terminology for RTU address, such as Destination, Slave, or simply Adrs.) The exchange is now defined only for address 1. If the "Display-enabled Exchanges Only" option is set, then a message of the modified exchange type for address 2 is not displayed. If the "Display-enabled Exchanges Only" option is not set, then such a message is displayed as Unknown.
Unless edited, the RTU address value for each exchange is an asterisk (*). This specifies use of the global RTU address value, entered from:
Properties>Protocol Specific>Exchange Defaults
The initial value here is also an asterisk, which specifies that any RTU address be allowed. This provides a shortcut for globally changing the RTU address of all exchanges. Instead of editing each exchange, simply alter the global "Exchange Defaults" entry. The ASE2000 will then only recognize messages, of any type, for the entered RTU address.
To reiterate, if you:
Enable the global exchange filtering option on the Display properties page, and
Set the global RTU address value on the Protocol Specific properties page
Then the ASE2000 will only display messages for the specified RTU address.
You can further limit the Line Monitoring view to display selected exchanges only. By default, all exchanges are enabled for display, and selecting the "Display-enabled Exchanges Only" option limits display only with respect to component filtering, such as just explained for RTU address. Enabled exchanges are identified by the presence of the letter 'D' under the Flags column on the Exchange List view. To disable an exchange, proceed to the Exchange Properties menu and deselect the Display option in the Flags section. The 'D' flag will disappear from the Exchange List view, and the deselected message will not be shown in the Line Monitoring view. To show exchanges of one type only, remove the 'D" flag from all other exchanges. Alternatively, you can delete all exchanges (Edit>Clear All Exchanges) and recreate the one exchange you are interested in seeing (Edit>Create Exchange Template). 'D' flag settings are processed only when the "Display-enabled Exchanges Only" option is enabled. If this feature is not enabled, all exchanges are displayed.
Item:
8
Subject:
DNP 3 Source and Destination Address Interpretation
Date:
August 25, 2000
Problem:
Specify Source and Destination Address Information for DNP 3
Resolution:
DNP 3 protocol defines two separate address fields, a source address and a destination address. Each master and slave device has its own address. In messages from the master, the destination address is the address of the slave and the source address is the address of the master. In messages from the slave, the destination address is the address of the master and the source address is the address of the slave. ASE has adopted the convention for source and destination addresses entered into the ASE2000:
The source address always specifies the address of the master, and
The destination address always specifies the address of the slave
When transmitting messages in Simulate Master mode, source and destination values are sent as entered. When transmitting messages in Simulate RTU mode, source and destination addresses are exchanged before transmission.
Similar adjustments are made on message reception, and in Monitor mode.
Item:
9
Subject:
DNP 3 Data Link Errors for Level 1 and 2 Testing
Date:
September 27, 2000
Problem:
Send error messages per DNP 3 Level 2 and Level 2 Test Procedures.
Resolution:
This technical note describes procedures for configuring the ASE2000 to transmit errant data link messages as required by the DNP Level 1 and Level 2 Test Procedures. Control over many low level components of DNP 3 message transmission exists in two primary places: an exchange's Edit Properties menu and the Force Errors menu. An Edit Properties menu is reached by highlighting the appropriate exchange and selecting Edit>Edit Exchange Properties. The Force Errors menu is reached from Properties>Protocol Specific>Force Errors.
These two menus can be used to configure many of the "special message" tests required by the Test Procedures. Unless explicitly configured to transmit a CRC error, CRC codes are recalculated to correctly reflect all configuration changes described below.
Test Section
ASE2000 Menu
Test Requirements
How to Configure the ASE2000
6.3.2
Force Errors
Request a Link Status Frame using link control block codes 0xC9 and 0xE9
The difference between these two codes is the state of the FCB bit. Normal FCB bit states can be overridden by selecting FCB:0 or FCB:1
6.6.2.1
Force Errors
Send a message with invalid start octets
Select DL Start Error
6.6.2.2
Exchange Properties
Send message with an invalid function code
Enter a decimal value into the Function pull-down list in the Data Link Layer section.PRM and FCV bit settings are controlled by separate check boxes, located near the function pull-down list.
6.6.2.4
Force Errors
Transmit messages with incorrect CRC codes
Checking Header CRC causes the ASE2000 to transmit messages with a CRC error in the data link portion. Checking Data CRC causes the ASE2000 to transmit messages with an error in the first application block CRC code
6.6.2.5
Exchange Properties
Transmit message with incorrect FCV
Select the correct function code from the Function pull-down list in the Data Link Layer section. Change the state of the FCV box to transmit a value inconsistent with the selected code
Item:
10
Subject:
Version 1.28 Release Notes
Date:
October 24, 2000
Problem:
New features and corrections implemented in Version 1.28.
Resolution:
Item:
11
Subject:
File Transfer Capability - DNP 3, IEC 870-5-101, Etc
Date:
October 25, 2000
Problem:
Need to set up values to send to an RTU/IED with a "file transfer" exchange.
Resolution:
The ASE2000 provides templates for entry of most common data and parameters such as RTU addresses, point IDs, and point values. Other cases, such as file transfer exchanges, require entry of large, and possibly complex, data structures. In most cases, when such information cannot be directly entered on ASE2000 menus, data can be specified through external text files.
Text files are specified by entering the file name, enclosed in double quotes, into the "Value" field of the applicable exchange. Data is extracted from the text file and inserted into the message sent by the ASE2000.
For example, consider the DNP 3 protocol "File Identifier" exchange. Select EDIT>EDIT EXCHANGE PROPERTIES and the Object Properties target. In the value field, enter:
"x.txt"
Using a text editor, create file "x.txt" within the ASE2000 installation folder. Alternatively, the file name can be entered with complete path information pointing to another folder. File "x.txt" should contain a list of values to transmit, one value per word (for DNP 3 protocol each word is an octet, or byte). Values are separated by at least one blank or new-line. Values default to decimal. Hex values can be specified with an 'x' suffix. For example, if file "x.txt" contains:
64x 01x 10 11 12 15 ABx
Then the ASE2000 will transmit 7 bytes: 0x64, 0x01, 0x0A, 0x0B, 0x0C, 0x0F, 0xAB.
Resolution:
The COM version of the ASE2000 Communication Test Set includes a Rainbow Sentinel Pro(TM) security plug. This plug must be attached to your parallel port before starting online communication. Without the security plug, the ASE2000 can be run to edit configuration information and to view capture files.
If you attempt to start online communication without the security plug, you will see the message:
ASE Hardware Not Installed. Cannot Continue.
If the security plug is installed, the Test Set will continue and the above message will not be seen. While communicating, presence of the security plug is verified periodically. Communication will stop if the plug is removed.
If online communication unexpectedly stops while the security plug is still present, or if the "Not Installed" message incorrectly appears at startup, then a new Rainbow Sentinel Pro(TM) I/O driver must be installed. This driver can be obtained from www.applsyseng.com/vdownload.html.
As of December 4, 2000, this problem has only been reported under Windows NT 4.0.
Item:
13
Subject:
CDC I and CDC II Configuring SCAN 1 and SCAN 3 Exchanges
Date:
January 11, 2001
Problem:
Configuring response messges for CDC I and CDC II SCAN 1 and SCAN 3 functions.
Resolution:
This section describes ASE2000 Communication Test Set configuration for CDC Types I and II protocols. These instructions, for configuring SCAN 1 and SCAN 3 exchanges, are useful for Master Simulation, Line Monitoring, and RTU Simulation modes. Both of these messages request input point data from the RTU. SCAN 1 is used to request digital and analog points. Scan 3 is used to request digital, pulse, and analog point. In both cases, there is nothing in the RTU response that the ASE2000 can use to identify the point type of each data word. To interpret data correctly, the user must configure each exchange to identify the sequence of data points in the RTU response.
Exchange configuration is performed from the "Edit Exchange Definition" menu reached by highlighting either the SCAN 1 or SCAN 3 message and selecting EDIT>EDIT EXCHANGE DEFINITION. This menu contains the ASE2000's internal representation of the selected exchange. Before proceeding, you must know how data will be returned from the RTU for the request you are configuring. For this example, assume a response consisting of:
32 bits of MCD data (16 digital points with 16 change bits)
16 bits of simple status
2 pulse accumulators
16 analogs
Use the scroll bar to locate the final entry in the "Exchange Elements" list, identified "Point Data: Unknown Quantity of Words".
Highlight this entry and select the "Replace" target.
This provides a list of exchange elements. The four relevant to this application are "Analog", "Digital", "Digital (MCD)", and "Pulse".
In this example, the RTU response starts with 32 bits of MCD, so select the "Digital (MCD)" entry.
Since each "Digital" and "Digital (MCD)" block for CDC I and II protocols requires 16 data bits, set the "Repeat Count" field to 2. This specifies 2 blocks, or 32 bits, of data.
All other fields can remain at the default values.
Select OK.
Your list should now appear as it started, with only the "Point Data ..." entry replaced with a "Digital (MCD) ..." entry.
For each of the other points, click on the "Add Element" target, select the appropriate point type, enter the correct point count, and select OK.
In this example, create "Digital" with a count of 1, "Pulse" with a count of 2, and "Analog" with a count of 16.
Since "Analog" is the last entry in the list, the count for that element can be set to 0 (except in RTU simulation mode).
A value of 0 is used if the rest of the message contains points of the same type.
When all entries have been made, select OK and save your configuration (FILE>SAVE).
Item:
14
Subject:
Version 1.30 Release Notes
Date:
May 8, 2001
Problem:
Pre-mark and Post-mark settings are not being used.
Resolution:
The following features were added to version 1.30 of the ASE2000 Communication Test Set, released on 08-May-2001.
Category
Protocol
Description
New Features
TRW 9550
Added protocol support
TRW System 9
TRW DS-850
Modbus TCP/IP
DNP 3
Add ability to set DFC bit
All LAN/WAN Protocols
Post message if other device disconnects. Allow reconnections.
Corrections
CDC Type 2
Allow faster carrier-turn-off at end of incoming message
DNP LAN/WAN
Remove abort after transmission of Broadcast Freeze message
BOA
Correct interpretation of "Init RTU" messages with exception bytes and correct display of indication change data
IEC 870-5-104
Do not reset ACK timer on reception of TESTFR message
IEC 870-5-103
Correct parsing of "Generic Identification" message
Valmet Series 5
Correct transmission order of CRC-16 bytes
Item:
15
Subject:
Version 1.31 Release Notes
Date:
June 12 , 2001
Problem:
The following features were added to version 1.31 of the ASE2000 Communication Test Set, released on 12-Jun-2001.
Resolution:
See table below:
Category
Protocol
Description
New Features
CDC Type 1
Differentiate between different SCAN 3 requests based on RTU Addr, Start Addr, Stop Addr. Previous versions used only RTU Addr.
CDC Type 2
DNP 3
Added ability to "Not Increment" Application Sequence Number
Added ability to randomly generate communication errors
Corrections
Conitel 2025
Allow faster carrier-turn-off at end of incoming message
IEC 870-5-104
Corrected "off-by-1" error in MaxRcv(w) parameter. Previously sent acknowledgements one message too late.
Resets V (R) and V(S) sequence numbers to zero after re-connect
Modbus
Corrects detection of "Preset Multiple Register" exchange
Valmet Series 3
Corrects detection of "Reset Status Change Queue" and "Reset Analog Change Queue" status bits
Valmet Series 5
VanComm
Corrects Point Values View problem where all points were assigned to RTU ID 0
Resolution:
This problem may occur for byte protocols operating on slower computers, running at higher baud rates, and using an ASE manufactured I/O card. In most cases, this can be corrected by reconfiguring the ASE I/O card through the ASE2000. Proceed to Properties, Communication, and the Line tab. Check the Native Asynch Mode box.
Resolution:
Selecting this option moves some communication processing from software to hardware and may improve reception when operating as described above. There is a slight reduction in precision for pre-transmission mark, post-transmission mark, and receiver squelch timings. This reduction is not significant to most typical system operations.
Item:
17
Subject:
Version 1.32 Release Notes
Date:
December 12, 2001
The following features were added to version 1.32 of the ASE2000 Communiction Test Set, release on 12-December-2001.
Category
Area
Description
New Features
New Protocols
Telegyr 800
Weston Recon 1
AEP
DNP 3
Added exchange to support scan for Internal Indcations
Corrections
Capture File
Corrected problem where capture file may not have been saved if the ASE2000 was closed while capture file data collection was active
DNP 3
Corrected problem that could cause time-stamp value to be displayed incorrectly by one-second
Print
Corrected File/Print problem that printed excess blank-pages
TRW (9550 and System 9)
Corrected BCH value display
Item:
18
Subject:
Wisp+ and Wisp+ Extended RTU Simulation
Date:
January 11, 2002
Problem:
The ASE2000 supports RTU simulation of Wisp+ and Wisp+ Extended protocols in a manner similar to support provided for other protocols. Operating in RTU simulation mode, the ASE2000 transmits a valid response to any valid request received from the host. A message may either be transmitted immediately, or in response to the next Poll command, as defined by the protocol. No other action is performed related to the host request. For example, a control output request does not cause a change in the state or value of a related input point.
Simple RTU simulation as described above can be initiated without any manual configuration of the ASE2000. With the default exchange list, simply select File and Simulate RTU.
Advanced RTU simulation requires manual configuration as discussed below.
Notification Messages
Notifications are generated by a RTU to report significant occurrences such as point change events. Notification messages are sent in response to Poll commands. The ASE2000 can be configured to periodically insert notification messages into a Poll Response Queue.
The default exchange list contains several notification eligible messages, identified by the following names.
Analog Input Changes
Analog Manual Changes
Analog Control Complete
Analog Output Changes
Analog Alarm Changes
Digital Change
SOE Change
Digital Manual Changes
Digital Control Complete
Counter Input Changes
To enable a message for inclusion in the notification queue:
Highlight the corresponding exchange.
Press Enter to request the Edit Exchange Properties dialog
Select the Transmit flag
Enter a transmission period in the Frequency (Sec.) entry field
Enter a valid non-zero Segment number
Enter a valid non-zero Mask value. This value defines the number of points to be reported (one bit set per point)
Select OK
Enabled exchanges are identified on the Exchange List view by the presence of an 'M' under the Flags column. Enabled exchanges are inserted into the Poll Response Queue at the specified frequency. Exchanges are removed from the queue as poll requests are received and processed. An exchange is not inserted if already present. For example, if an exchange is enabled with a frequency of 2.0 seconds, and a poll request is not received for five seconds, the queue will only contains one occurrence of that exchange.
Point Modeling
By default, all point values are reported as zero. The ASE2000 can be configured to model point value changes. Point modeling capabilities support, within each response, for:
Analog point values to change, by a fixed amount, between upper and lower limits
Digital point states to toggle
Counter values to increase by a fixed amount, resetting to zero after exceeding their maximum
Related configuration procedures are defined in the ASE2000 User Guide section titled Simulating a Secondary Station.
Item:
19
Subject:
Simulating an RTU: IEC 870-5-101 and IEC 870-5-103 Protocols
Date:
January 24, 2002
The IEC 870-5 protocols place more intelligence at the RTU/IED than most American protocols. With these, the master station periodically issues general data polls, called Class 1 and Class 2 requests. Each poll does not ask for specific data items, such as measurand (analog) or digital data points. Instead, it requests the RTU/IED to return whatever data items it determines are most important at the time the request is received. The master has a little control over which data items are reported, by being allowed to issue separate Class 1 and Class 2 requests. Typically, higher priority event data items are included in Class 1 responses, and lower priority periodic data in Class 2.
Each RTU/IED response to a Class data request falls into one of three general types:
NACKs, indicating no data available for the current request.
Progress and acknowledgement messages, such as command confirmations
ASDU Point Information
Exchanges in the first two bullets are managed by the ASE2000. Exchanges in the third, actual data point values, must be configured and enabled by the user. For each ASDU Type message to be included in response to a Class 1 or Class 2 data request, the user must:
Locate the corresponding exchange
Assign it to either Class 1 or Class 2. In most cases, this is set correctly, although the default setting can be changed
Define the number of points, values, and other point parameter information
Enter the reporting frequency
Enable the message for transmission
In addition to normal Class 1 and Class 2 polling responses, reception of an interrogation message causes all enabled exchanges to be inserted into their corresponding response queues with an Interrogated by General Interrogation cause of transmission. Note that the ASE2000 does not support group interrogations.
The ASE2000 supports RTU simulation, as described, for all generic SCADA ASDU Type messages. This term refers to messages containing analog, digital, and counter data points. The ASE2000 may not generate responses to some of the more complicated data types.
To configure an exchange as described:
Select the exchange in the Exchange List View and choose Edit>Edit Exchange Properties. The Edit Exchange Properties dialog box appears.
Assign values to the following general properties:
Transmit. Enables the exchange for data reporting
Frequency (sec). Defines how often ASE2000 attempts to report the exchange. ASE2000 includes all applicable and enabled exchanges in Interrogation or Counter Interrogation response sequences. ASE2000 also inserts the exchange in the Class 1 or Class 2 response queue at the specified frequency, as long as the value is not zero.
Cause of transmission. Defines the cause to be used in periodic responses. ASE2000 inserts the correct cause in Interrogation responses.
Object class. Defines object as Class 1 or Class 2
Address. Data Link address. Enter desired address or an '*' to use the system default address.
Common Address. Common address of ASDU. Enter desired address or an '*' to use the system default address.
Configure number of data points and point properties by entries in the Information Object section of the exchange dialog.
Each row defines one information object (data point). Add new rows by selecting the Add Row target.
Address. Defines a single information object address. If the SQ box is checked, only the first address is entered. Sequential addresses are assumed for each subsequent row. If the SQ box is unchecked, a separate address must be entered for each row.
Value and Quality information is entered by selecting the Object Properties target.
Select OK to complete editing of each exchange. You should save the configuration file when finished.
Responses to control (single point, double point, and analog output) and similar requests do not require user configuration. More complicated sequences not related to normal point data or control output requests, such as file download operations, may not be handled correctly.
Item:
20
Subject:
Creating New DNP3 Exchanges
Date:
February 4, 2002
Problem:
This technical note explains how to create new exchanges, such as Cold Restart, that may be omitted from the default exchange list.
Resolution:
There are two basic types of exchange structures within the ASE2000. These are ones where:
A request is issued by the host, to which the Remote responds. An example is Reset Link
A request is issued by the host, with no Remote response. An example is Freeze (All)
Exchanges not included in the default exchange list, such as Cold Restart, may be manually created. The simplest way to use Copy and Paste to create a copy of an existing exchange of the same basic type. That is, if you want to create a new request/response exchange (type 1, above), make a copy of any other request/response type exchange. To create a new request-only exchange (type 2), copy another exchange of that type.
You will temporarily have two identical exchanges. Edit either one to convert it to the new exchange. All edits are performed from the Edit Exchange Properties dialog, requested via the Edit pull-down menu. The following example describes steps for creating a Cold Restart exchange. Similar procedures can be used for other exchanges.
Enter a new exchange name in the Name field, such as Cold Restart
Select the correct Data Link Layer function code. In this case, select User Data (No Confirm)
Select the correct Application Layer function code, Cold Restart
Delete all objects, if any, in the Application Layer section, by repetitively selecting the Delete Row target
At this point, you have defined an exchange with no objects. The exchange message includes, in Master Simulation mode, all octets through the Application Layer function code. In RTU simulation mode the message is similar, including all octets through the IIN.
For an exchange with objects, either in the response or request, object entry or entries must be manually configured. Do not worry if objects are included in the request only, the response only, or both. The ASE2000 handles this for you. Your responsibility is only to define the objects.
In this case, the Cold Restart response contains a Time Delay Fine or Time Delay Coarse object.
Select Add Row
Use the Object pull-down list to select 52:Time Delay
Use the Variation pull-down list to select 1:Time Delay Coarse or 2:Time Delay Fine
Select Qualifier Setup, Count of Points, and enter a value of 1
You have now defined a correct Cold Restart exchange. Save your file so you do not have to reconfigure the exchange list again.
Item:
21
Subject:
Version 1.33 Release Notes
Date:
March 1, 2002
The following features were added to version 1.33 of the ASE2000 Communiction Test Set, release on 01-March-2002.
Category
Area
Description
New Features
DNP3
Saves "List of Points" IDs associated with qualifier codes 0x17 and 0x28
Add Forced Error condition for "Send Wrong Sequence Number in Application Confirm Messages"
Indactic 33/41
Insert measurand file number in group column on Point Values view
Point Values
Displays points in Inverse Video when reported with change, and Bold when reported without change. Reverts to normal video when unreported for some period of time.
Corrections
General
File/Print now prints all pages, not just the first
Point Values
Save state of Event checkbox in Analog and Digital properties
IEC 870-5-101
Corrects transmission of messages with Data Link size of 0 or 2 octets
Displays "Time Invalid" bit, when set, for Date/Time
Item:
22
Subject:
PG&E Protocol Configuration Notes
Date:
March 6, 2002
This technical note provides guidelines for configuration of selected PG&E protocol messages.
Basic AI/DI Scan
Unlike the Basic Status and Basic Analog exchanges, the Basic AI/DI Scan exchange returns data for two point types: digital and analog. Since both are returned in a single data stream, the exchange must be configured with the counts of each type.
Highlight the Basic AI/DI Scan exchange and select Edit and Edit Exchange Definition.
The resulting menu shows ASE2000's internal exchange definition table. The final two lines are:
Digital Points: unknown quantity of blocks
Analog Points: unknown quantity of points
Highlight the Digital Points entry and select Properties
Under Repeat Count, enter the number of status blocks expected in the RTU response. Each block corresponds to one PG&E sequence number, or 16 bits.
The Analog Points entry needs to be modified only when running in RTU simulation mode. Modification in other modes is optional, but allowed. Select Properties and, under Repeat Count, enter the number of expected analog points.
Write 2
This exchange should be modified when transmitting data to a RTU (Master Simulation mode, Send Once, or Send Continuously). It does not need to be modified when operating in Monitor or RTU Simulation mode.
A Write 2 message contains the Remote and Master address, function code, command code, length, and a data section. The data section contains values to be written to RTU memory. These values must be coded in a text file, created by a standard text editor external to the ASE2000. Normally, the text file would be placed in the ASE2000 installation folder. The text file contains a list of values to transmit, one value per byte. Values are separated by at least one blank or new?line. Values default to decimal. Hex values can be specified with an 'x' suffix. For example, a text file containing:
Configuring a Write 2 exchange for transmission is a two step process:
Edit a text file with values to be transmitted in the exchange's data section, and
Edit the Write 2 exchange to reference that file.
The following procedure can be used the edit the Write 2 exchange assuming a text file named pge.txt was created in the ASE2000 default installation folder.
Highlight the Write 2 exchange and select Edit and Edit Exchange Definition
The resulting menu shows ASE2000's internal exchange definition table. The final line in the To RTU section is: Data: 0 words
Highlight this line and select Replace
Scroll down, highlight the Message Element type: File, and select OK
Enter the text file name within quotes: "pge.txt"
Select OK
Item:
23
Subject:
Saving Monitoring and Capture Data to Text
Date:
April 16, 2002
The ability to save ASE2000 capture file data or information from the monitoring view to an ASCII text file is not supported directly by the ASE2000. However, this can be done using standard Windows software.
Creating a text file from ASE2000 communication information requires use of the "Generic / Text Only" printer driver that comes with Windows 95/98/ME/NT 4.0 and 2000. If not already installed, this driver can be installed with the following procedure:
Go to "Settings>Printers" and select "Add Printer". The Add Printer Wizard will start
Install as a "Local Printer"
Select "Generic" under Manufacturer and "Generic / Text Only" under Printers
Continue through the installation process
When asked to designate a port, select FILE: This will cause a text file to be created from the print operation
With the "Generic / Text Only" printer installed, you can create Text files by specifying the Text Only printer when printing from the ASE2000. You will be asked to specify a file name, which will have the default extension "prn". These files can be opened with any text editor such as Microsoft Word, Wordpad, or Notepad.
Item:
24
Subject:
Version 1.34 Release Notes
Date:
April 30, 2002
The following features were added to version 1.34 of the ASE2000 Communication Test Set, released on 30-Apr-02.
Category
Area
Description
New Features
DNP3
IN RTU simulation mode, added option to respond with incorrect application sequence number
Added ability to set all IIN bits except for "All Stations". That IIN is managed by the ASE2000. Prior releases has support for most, but not all, IINs.
Added support for new Control-Relay-Output-Block status codes per DNP Technical Bulletin TB2001-001
Find
Increased depth of pull-down list in "Find Message By Name" dialog box
New protocols
Added support for ESCA protocol as delivered to ConEd
Corrections
AEP Protocol
Added station ID field to ABS command. Added "Security code" field to MDE and MDO commands.
Capture File
Data for a few exchanges contain a character string. One example is the "file name" field in the DNP File Open command. For prior releases, the ASE2000 would abort when reading a capture file containing such a string field.
CDC Type 1
Corrected messages sent from the Analog Control view
DNP3 LAN/WAN
Support IIN bit configuration in RTU Simulation responses
Find
Corrected processing of "Find By Time"
GETAC 7020/4-BCH
"Number of words" field was not correctly processed when transmitting the SCNI exchange.
Harris 5000/6000
Corrected transmission of setpoint commands with a value of 128 or larger.
IEC 870-5-103
Corrected display of negative values for Measurand II responses
IEC 870-5-104
Corrected timing error that, during periods of heavy utilization, could cause the same sequence number to be transmitted in two consecutive messages.
SES-92
Corrected display formatting of trip/close time duration
Wisp+ and Wisp+ Extended
Corrected interpretation of data messages with the bit set
Corrected transmission of "Report" message to RTU 38
Item:
25
Subject:
Version 1.35 Release Notes
Date:
July 10, 2002
The following features were added to version 1.35 of the ASE2000 Communication Test Set, released on 10-Jul-02.
Category
Area
Description
New Features
Generic Async
Supports full-duplex line monitoring when data is received in both directions simultaneously
Corrections
General
Corrects problem that occurred only after stopping and restarting the ASE2000 in Master Sim mode. Occasionally, one exchange that had been enabled for transmission could have been disabled after the restart.
Corrects an issue where a Communication Error Event Log could identify an incorrect RTU ID. This problem could only have occurred when monitoring communication of multiple RTUs.
AEP Sync
Corrects determination of message direction (to or from RTU) in line monitoring mode
DNP 3
Corrects display of "Freeze with Time" message
The millisecond field in transmitted messages is now set from the system time. Previous versions used '0'.
IEC 870-5-101
Corrects display of "Double Point" data in the Point Values view
Allows "txt" file data to be included in "Last Segment" messages
Telegyr 800
Excludes 'SG' bit in parsing station number
Corrects intermittent error in calculation of SFB bit state in message transmissions
Telegyr 8979
Corrects error which stopped communication after receiving a Short Header response to a Analog Change Report request
Item:
26
Subject:
Version 1.36 Release Notes
Date:
August 30, 2002
The following features were added to version 1.36 of the ASE2000 Communication Test Set, released on 30-Aug-2002.
Category
Area
Description
New Features
DNP3
Added ability to transmit object 0 for Acceptance Test Procedure section 8.6.3.2
IEC 870-5-103
RTU Simulation propagates SCN number from General Interrogation to corresponding responses
SC 1801 Version 5.2
New Protocol
Pert 26/31
New Protocol
Telegyr 8979
Added ability to set RTU simulation parameters for individual analog input points instead of limiting entry to point groups
Corrections
Capture File
Correct problems with capture file access under Windows 95/98/ME/NT4.0
DNP3
Corrects response timeout calculations on long messages
IEC 870-5-101
Uses user-entered cause of transmission in class 1 and 2 responses<
