Page 4
Preface A.4. DNP3 Qualifier Code ....................103 A.5. DNP3 Event Status Flags ..................105 Index ............................107 Revision History Revision Date Comment 29 May 2015 Initial document 26 June 2015 Add Scheduled mode Tag map status 14 July 2015 Add note that a maximum of 230 bytes can be transferred per mapped item when in Scheduled Tag Mode.
1.1. INTRODUCTION TO THE DNP3 ROUTER This manual describes the installation, operation, and diagnostics of the Aparian DNP3 Router. The DNP3 Router provides intelligent data routing between EtherNet/IP and DNP3 (serial, Ethernet UDP, or Ethernet TCP). The DNP3 Router allows the user to integrate DNP3 devices over a secure link into a Rockwell Logix platform (e.g.
The DNP3 Router transfers messages received from a Logix Message Logix (Msg) Instruction. (DNP3 Master) Table 1.1. – Modes of Operation Router is configured using the Aparian Slate application. This program can be DNP3 downloaded from www.aparian.com free of charge. Slate offers various configuration methods, including a controller tag browser.
Page 7
Preface Figure 1.2. - Example of a typical network setup in reactive mode By converting and redirecting serial DNP3 messages from legacy devices to EtherNet/IP, the module provides an interface for data exchange to Allen-Bradley ControlLogix and CompactLogix platforms. This enables user to replace legacy devices and systems with minimal effort and downtime.
Page 8
Preface Systems that rely on a central ControlLogix communicating to a number of remote DNP3 devices, (e.g. Eletrical Protection Units or Intelligent Relays), may find the DNP3 Router useful when operating in Scheduled Tag Mode as shown in the image above. The module will exchange data between the DNP3 device and Logix platform at a configured interval without any need for additional coding or mapping.
ADDITIONAL INFORMATION The following documents contain additional information that can assist the user with the module installation and operation. Resource Link Slate Installation http://www.aparian.com/software/slate DNP3 Router User Manual DNP3 Router Datasheet http://www.aparian.com/products/dnp3router Example Code & UDTs www.cisco.com/c/en/us/td/docs/video/cds/cde/cde205_220_420/installation/guide/ Ethernet wiring standard cde205_220_420_hig/Connectors.html...
Installation 2. INSTALLATION 2.1. MODULE LAYOUT The module has three ports at the bottom of the enclosure as shown in the figure below. The ports are used for Ethernet, RS232 serial, and power. The power port uses a three-way connector which is used for the DC power supply positive and negative (or ground) voltage as well as the earth connection.
Page 11
Installation Figure 2.2. – DNP3 Router front and top view The module provides four DIP switches at the top of the enclosure as shown in the top view figure above. DIP Switch Description DIP Switch 1 Used to force the module into “Safe Mode”. When in “Safe Mode” the module will not load the application firmware and will wait for new firmware to be downloaded.
Installation 2.2. MODULE MOUNTING The module provides a DIN rail clip to mount onto a 35mm DIN rail. Figure 2.3 - DIN rail specification The DIN rail clip is mounted on the bottom of the module at the back as shown in the figure below.
Installation 2.3. POWER A three way power connector is used to connect Power+, Power– (GND), and earth. The module requires an input voltage of 10 – 28Vdc. Refer to the technical specifications section in this document. Figure 2.5 - Power connector 2.4.
Setup 3. SETUP 3.1. INSTALL CONFIGURATION SOFTWARE All the network setup and configuration of the module is achieved by means of the Aparian Slate device configuration environment. This software can be downloaded from http://www.aparian.com/software/slate. Figure 3.1. - Aparian Slate Environment 3.2.
Page 15
Setup Once opened, the DHCP server will listen on all available network adapters for DHCP requests and display their corresponding MAC addresses. Figure 3.3. - DHCP Server NOTE: If the DHCP requests are not displayed in the DHCP Server it may be due to the local PC’s firewall.
Page 16
Setup The successful assignment of the IP address by the device is indicated by the green background of the associated row. Figure 3.5. - Successful IP address assignment It is possible to force the module back into DHCP mode by powering up the device with DIP switch 2 set to the On position.
Page 17
Setup Figure 3.7. - Selecting the Target Browser The Target Browser automatically scans the Ethernet network for EtherNet/IP devices. Figure 3.8. - Target Browser Right-clicking on a device, reveals the context menu, including the Port Configuration option. Figure 3.9. - Selecting Port Configuration Document No.
Setup All the relevant Ethernet port configuration parameters can be modified using the Port Configuration window. Figure 3.10. - Port Configuration Alternatively, these parameters can be modified using Rockwell Automation’s RSLinx software. 3.3. CREATING A NEW PROJECT Before the user can configure the module, a new Slate project must be created. Under the File menu, select New.
Page 19
Setup A Slate project will be created, showing the Project Explorer tree view. To save the project use the Save option under the File menu. A new device can now be added by selecting Add under the Device menu. Figure 3.12. - Adding a new device In the Add New Device window select the DNP3 Router, and click the Ok button.
DNP3 PARAMETERS The DNP3 parameters will be configured by Slate. Refer to the additional information section for documentation and installation links for Aparian Slate. The DNP3 parameter configuration consists of a general configuration, security configuration as well as a serial configuration.
Page 21
Setup Description This parameter is used to provide a more detail description of the application for the module. Major Revision The major revision of the module Mapping Mode The mapping mode will determine how the DNP3 messages are routed. In Reactive Tag mode the module will automatically route the DNP3 message and function to the correct Logix tag.
Page 22
Setup Figure 3.15. - General Configuration The DNP3 configuration consists of the following parameters: Parameter Description Protocol The DNP3 Router can interface to the DNP3 device(s) on either serial, Ethernet TCP, or Ethernet UDP. Retry Limit The retry limit determines how many times the module must retry the message exchange before failing it.
Page 23
Setup responses must be sent. This will allow for unsolicited communication without the need to worry about TCP socket timeouts. NOTE: Certain DNP3 Masters will not allow a DNP3 Outstation to create a TCP connection on the DNP3 Master. Table 3.2 – DNP3 configuration parameters The DNP3 configuration is shown in the figure below.
Page 24
Setup MAC Algorithm The MAC algorithm is used to encrypt the challenge data for secure authentication. DNP3 allows for various encryption standards in different formats to be used for secure authentication: HMAC SHA-1 encryption (4 octets – serial) – for legacy support HMAC SHA-1 encryption (8 octets –...
Page 25
Setup Figure 3.17 - Security configuration The Master Events configuration consists of the following parameters: Parameter Description Event Unload Mode When the DNP3 Router is set in Scheduled (Master) Mode it can unload Events from DNP3 Outstations in one of two ways: Class Mode Events will be unloaded by class (e.g.
Page 26
Setup Buffer Size The size of the Events Array defined in the Logix controller. NOTE: This value must not exceed the Logix controller tag array size. If this is the case the unloading of events to the Logix controller will not operate correctly. Unload Count This parameter is the maximum number of evens that will be uploaded per poll.
Page 27
Setup The Outstation Settings Attributes configuration consists of the following parameters: Parameter Description Enable Master Filter The DNP3 Router (in Outstation Mode) can have a DNP3 Master allowed list. This can help reducing risks of unauthorized DNP3 Masters exchanging data with the DNP3 Outstation.
Page 28
Setup Figure 3.19. – Outstation Settings Configuration The Outstation Events configuration consists of the following parameters: Parameter Description Unsolicited Event Trigger The Event triggers can be used by the DNP3 Router (in Outstation Mode) to limited the amount of individual unsolicited responses sent to the DNP3 Master. To reduce traffic the user can set limits, one of which must be reached, before an unsolicited response is sent.
Setup Figure 3.20. – Outstation Events Configuration 3.5. MESSAGE ROUTING The module can be configured to route DNP3 data in one of three modes: Reactive Tag (Outstation) mode Schedule Tag (Master) mode Unscheduled mode 3.5.1. R EACTIVE UTSTATION The Reactive Tag routing mode allows mapping of virtual Data Files to Logix tags across multiple controllers.
Page 30
Setup Figure 3.21. - Reactive Tag mode configuration The Reactive Tag mode is configured in two steps. First the user must create a Target Name (CIP path to the destination Logix controller) which will be used to link the DNP3 group, variation, and range to the destination Logix tag.
Page 31
Setup Figure 3.23. - Target Browser selection The required Logix controller can then be chosen by selecting it and clicking the Ok button, or by double-clicking on the controller module. A maximum number of 3 controller mapping entries can be added. The second part of the Reactive Tag mode is to configure the link between a DNP3 group, variation, and range combination to a Logix tag.
Page 32
Setup Figure 3.24. – Reactive Tag Mapping DNP3 allows the user to select from a range of different formats (called variations) for each group. This will allow the user to access additional information for a specific group (e.g. timestamp, status, etc.). For this reason, the user must use or match the example UDTs provided (see the additional information section) to access the all data in the Logix controller.
Page 33
Setup Figure 3.25. – Tag Browser tag selection The figure below is an example of how DNP3 messages are routed to the Logix tags using the Reactive Tag Map mode. NOTE: It is the user’s responsibility to ensure that the Logix tag datatype/UDT and size matches that of the DNP3 message requests.
Page 34
Setup Figure 3.26 - Reactive Tag mode configuration in Slate (example route 1) Figure 3.27 - Reactive Tag mode configuration in Slate (example route 2) Document No. D109-010 Page 34 of 108 Revision 1.15...
Setup When using operate commands the user will always need a tag for the operate command as well as a tag for the status. For example, when using Binary Commands (switching a binary value on or off) the Binary Control Group 12 will need to be used. This group is an operate-only group and does not contain or hold any value.
Page 36
Setup Figure 3.29. - Scheduled Tag configuration The Schedule Tag mode is configured in three steps. First the user must create a Target Name (CIP path to the destination Logix controller) which will be used to link the DNP3 group, variation, and range to the destination Logix tag.
Page 37
Setup Figure 3.31. - Target Browser selection The required Logix controller can then be chosen by selecting it and clicking the Ok button, or by double-clicking on the controller module. A maximum number of 3 controller mapping entries can be added. NOTE: A maximum of 230 bytes can be exchanged per mapped item when running in Scheduled Tag Mode.
Page 38
Setup The second part of the Scheduled Tag mode setup is to configure the scan intervals. The scan intervals allow different data items to be transferred at different rates. There are 4 scan classes, viz. A, B, C and D. The intervals for each can be adjusted by entering the scan time in milliseconds.
Page 39
Setup NOTE: The IP address is only relevant if the protocol selected is either Ethernet TCP or Ethernet UDP. The Node address is relevant for both the previous mentioned Ethernet protocols as well as serial. The DNP3 group and variation selected is that of the remote device. The user must ensure that the remote device supports both the group selected as well as the data format (variation).
Setup NOTE: It is the user’s responsibility to ensure that the Logix tag datatype/UDT and size matches that of the DNP3 message requests. Failing to do this can cause unexpected results and communication faults. A list of recommended data types for each Group – Variant combination is listed in Appendix A.
Page 41
Setup NOTE: When using DNP3 Commands (e.g. Control Relay Output Block – CROB, or Analog Outputs) events will be logged when commands are received, thus the deadband field is not applicable. Figure 3.35. – DNP3 Event selection Each mapped line item will be read every 10ms from the Logix controller. If a mapped line item is sufficiently large then the reading of all the elements in the mapped line item will be spread over multiple Logix controller reads.
Setup NOTE: In the applicable DNP3 objects, Bit 7 is unused. Although used to trigger the logging of an event, this bit is masked off before being transmitted to the DNP3 master and thus complying with the DNP3 specification. NOTE: The Logix triggered event mechanism requires the Enable Events parameter to be configured in the Slate Logix Tag Mapping (above).
Page 43
Setup update a Logix UDT array (see example Logix code) to allow the Logix application code to use NOTE: Refer to the Logix example code which provides a mechanism to extract the DNP3 Events from the Logix Master Events Tag. Once there is confirmation from the Logix controller that the event has successfully been written to an index offset of the Logix Master Event Array the DNP3 Router will then send a confirm to the DNP3 Outstation that the event has been received and it can be removed from...
Setup Polling individual Groups for each DNP3 Outstation (e.g. Group 32 – Analog Input Events). Figure 3.39 – DNP3 Master Event Unloading The unloading of buffered events into a Logix controller is explained in section 5. 3.7. MODULE DOWNLOAD Once the DNP3 configuration has been completed, it must be downloaded to the module.
Page 45
Setup The Connection path can be set by right-clicking on the module and selecting the Connection Path option. Figure 3.40. - Selecting Connection Path The new connection path can then be either entered manually or selected by means of the Target Browser.
Page 46
Setup Figure 3.42. - Selecting Download Once complete, the user will be notified that the download was successful. Figure 3.43. - Successful download During the download process the module’s time will be compared to that of the PC’s time. Should the difference be greater than 30 seconds, the user will be prompted to set the module time to that of the PC time.
Installation tool will be invoked to complete the registration. Alternatively, the EDS file can be downloaded from the product web page at http://www.aparian.com/products/dnp3router and registered manually using the EDS Hardware Installation Tool shortcut under the Tools menu in Studio 5000.
Page 48
Figure 3.47 – Adding a module The module selection dialog will open. To find the module more easily, use the Vendor filter to select only the Aparian modules as shown in the figure below. Document No. D109-010 Page 48 of 108...
Page 49
Setup Figure 3.48 – Selecting the module Locate and select the DNP3 Router module, and select the Create option. The module configuration dialog will open, where the user must specify the Name and IP address as a minimum to complete the instantiation. Figure 3.49 –...
Page 50
Setup Once the instantiation is complete the module will appear in the Logix IO tree. Figure 3.50 – Logix IO tree The Module Defined Data Types will automatically be created during the instantiation process. These data types provide meaningful structures to the module data. An excerpt of the Input Image is shown in the following figure.
Setup 3.8.2. RSL 5000 C OGIX ONFIGURATION ERSION 3.8.2.1. ADD MODULE TO I/O CONFIGURATION The module can operate in both a Logix “owned” and standalone mode. When the module operates in a Logix “owned” mode the DNP3 Router will need to be added to the RSLogix 5000 IO tree.
Page 52
Setup Figure 3.53. - RSLogix General module properties in RSLogix 5000 NOTE: The user will need to enter the exact connection parameters before the module will establish a class 1 connection with the Logix controller. Next the user needs to add the connection requested packet interval (RPI). This is the rate at which the input and output assemblies are exchanged.
Page 53
Setup Once the module has been added to the RSLogix 5000 IO tree the user must assign the User Defined Types (UDTs) to the input and output assemblies. The user can import the required UDTs by right-clicking on User-Defined sub-folder in the Data Types folder of the IO tree and selecting Import Data Type.
Page 54
Setup Figure 3.57. - Selecting partial import file The import will create the following: The required UDTs (user defined data types) Two controller tags representing the Input and Output assemblies. A routine mapping the DNP3Router module to the aforementioned tags. ...
Page 55
Setup Figure 3.58. - Imported RSLogix 5000 objects Refer to the additional information section of this document for an example RSLogix 5000 project as well as the required UDTs. Document No. D109-010 Page 55 of 108 Revision 1.15...
Logix Operation 4. LOGIX OPERATION 4.1. MESSAGE ROUTING When the module has been correctly setup the DNP3 message initiator will send a read/write to a certain DNP3 group and variation which will then be routed to a Logix tag. The messages sent by the initiator must be completed with the correct data for successful operation.
Logix Operation 4.2.1. I NPUT SSEMBLY The following parameters are used in the input assembly of the module. Parameter Datatype Description Instance STRING This parameter is the instance name of the module that was configured under the general DNP3 configuration in Slate. Status.ReactiveTagMode BOOL Set if the module is operating in Reactive Tag mode.
See Appendix A for more information on this. To simplify the configuration of the required message a number of UDTs have been preconfigured, and are available on the Aparian DNP3Router webpage (see the further information section). The message instruction should be setup as follows: Document No.
Page 59
Logix Operation Figure 4.2. - Message Instruction Figure 4.3. - Message Configuration Parameter Description Message Type CIP Generic Service Type Custom Service Code 6A (Hex) - Unscheduled DNP3 Pass-through Class 40C (Hex) Instance Attribute Source Element The request tag instance. Must follow the structure of the AparianDNP3RMsgRequest UDT.
Page 60
Logix Operation Destination Element The response tag instance. Must follow the structure of the AparianDNP3RMsgResponse UDT. Table 4.3. - Message Configuration Paramaters Figure 4.4. - Messsage Configuration - Communication The Path must be configured to that of the DNP3 Router. If the DNP3 Router has been added in the I/O tree, then the Browse option can be used to select the path.
Page 61
Logix Operation Figure 4.5. - Unscheduled Message Request Tag Parameter Description Destination Node The DNP3 node address of the destination device. Request Data Size The size of the request data being sent Port The DNP3 Router supports three ports to interface a DNP3 device: Serial, Ethernet TCP, or Ethernet UDP.
Logix Operation Bit 0 – Broadcast Bit 1 – Class 1 events Bit 2 – Class 2 events Bit 3 – Class 3 events Bit 4 – Need Time Bit 5 – Local control Bit 6 – Device trouble Bit 7 – Device restart Bit 8 –...
Page 63
Logix Operation Figure 4.7. – DNP3 Message Request Example The response to the message is shown in the next figure. The data values can them be copied (COP instruction) to the required tag destination. The DNP3 Group, Variant and Qualifier codes are shown in the Appendix. Document No.
Page 64
Logix Operation Figure 4.8. – DNP3 Message Response Example Document No. D109-010 Page 64 of 108 Revision 1.15...
DNP3 Operation 5. DNP3 OPERATION 5.1. GENERAL DNP3 supports various formats for each group of data points. The different formats can include additional data to that of the main requested variable needed (e.g. Status, Time, etc.). For this reason, the Logix controllers needs to map the data for these formats to User-Defined Data Types (UDTs).
Page 66
DNP3 Operation Figure 5.2. – Supported UDT for DNP3 Group 30 with Variation 1 A new tag or array must be created to match the DNP3 Group and Variation. Figure 5.3. – New Tag with Supported UDT for DNP3 Group 30 with Variation 1 Document No.
DNP3 Operation In Slate the Target Tag selected must be the Tag or Array with Data Type AparianDNP3Analog32Flag as shown below. Figure 5.4. – Selecting the correct tag from Slate’s Tag Browser. The same procedure can be followed for numerous other DNP3 Group and Variation combinations.
DNP3 Operation Function Description Select/Operate The select/operate function is a two-step operate where the Master first “Arms” the outputs with the select function before enabling the “Armed” output with the operate function. Direct-Operate The Direct-Operate function has a similar outcome to the Select/Operate function but is a one-step function.
DNP3 Operation The RequestPending bit in the mapped Logix Tag for the control command will be set, indicating that a new operate command was received. The Outstation Controller should copy the values Command UDT to the respective Status UDT (Binary: Group 12 to 10, Analog: Group 41 to 40).
Page 70
DNP3 Operation notified and must execute the requested command. This is done by having a Freeze Counter Control UDT which can be used by the Logix controller to take the needed action. NOTE: The Control Tag must be named identical to that of the DNP3 Counter Tag used with the addition of “Ctrl”...
DNP3 Operation 5.4. DNP3 EVENTS – UNSOLICITED RESPONSES Events are generated in the Outstation and processed by the Master. Events can be grouped during the unloading process by either their assigned class or Data Type Group (e.g. Group 23 – Analog). Unloading can be initiated by the Master via a set interval poll or initiated by the Outstation via an Unsolicited Response message.
Page 72
DNP3 Operation 5.4.1.2. SELECTING AN EVENT VARIATION The required event variation must be selected. Note that if “with Time” is selected the logging of an event will be timestamped. Figure 5.12 – Select variation 5.4.1.3. SELECTING A DEADBAND (DB) The change deadband must be selected. When the value changes by more than the deadband an event is logged.
DNP3 Operation 5.4.1.5. SELECTING THE UNSOLICITED EVENT TRIGGERS The Event triggers can be used by the DNP3 Router (in Outstation Mode) to limited the amount of individual unsolicited responses sent to the DNP3 Master. To reduce traffic the user can set limits which once reached will only send an unsolicited response. Figure 5.15 –...
Page 74
DNP3 Operation The structure of the UDT is provided below. Figure 5.16 – Master Event Logix UDT Below is an explanation of each element in the structure: Attribute Description EvtPending This bit is set when the event is written into the controller. The application code can use this bit, and subsequently clear it, when the event has been processed.
Refer to the Logix Master Example code which can be found on the website at the following link http://www.aparian.com/products/dnp3router. The Logix Master Example code provides UDTs and AOIs to process events in the Master Event Buffer and copy the values to the respective static DNP3 objects.
Page 76
DNP3 Operation Refer to the Logix Master Example (DNP3MasterExample) code which can be found on the website at the following link http://www.aparian.com/products/dnp3router. The Logix Master Example code provides UDTs and AOIs to process events in the Master Event Buffer and copy the values to the respective static DNP3 objects.
Security 6. SECURITY DNP3 offers Secure Authentication for links at risk of being attacked. There are various Key Change methods, Message Authentication Code (MAC) algorithms, and Authentication methods provided in the DNP3 protocol specification. Various keys are used in DNP3 Secure Authentication. Session keys are used most frequently as it is used for Authentication of the requests.
Page 78
Security Figure 6.1 - DNP3 Router key update method. The module supports all DNP3 MAC algorithms and Key Wrap algorithms. The module also supports Aggressive Authentication mode which reduces the amount of traffic on the network (which could be required on busy networks or serial communication). NOTE: The user needs to ensure that the other DNP3 device with which it is communicating has the same security options configured as the DNP3 Router and that the selected options are supported in the device.
Diagnostics 7. DIAGNOSTICS 7.1. LEDS The module provides three LEDs for diagnostics purposes as shown in the front view figure below. A description of each LED is given in the table below. Figure 7.1 - DNP3 Router front view Description The module’s Ok LED will provide information regarding the system-level operation of the module.
The statistics can be accessed in full by Slate or using the web server in the module. To view the module’s status in the Aparian-Slate environment, the module must be online. If the module is not already Online (following a recent configuration download), then right-click on the module and select the Go Online option.
Page 81
Diagnostics Figure 7.4. - Status monitoring - General The General tab displays the following general parameters and can also be used to set the module time to the PC time: Parameter Description Mode Indicates the current operating mode: Transparent, Reactive Tag, Scheduled Tag, or Unscheduled.
Page 82
Diagnostics Module Time Indicates the module’s internal time. The module time is stored in UTC (Universal Coordinate Time) but displayed on this page according to the local PC Time Zone settings. MAC Address Displays the module’s unique Ethernet MAC address. Temperature The internal temperature of the module.
Page 83
Diagnostics Critical Messages Tx The number of critical DNP3 packets sent by the module when security is enabled. Critical Messages Rx The number of critical DNP3 packets received by the module when security is enabled. Messages Discarded The number of DNP3 packets discarded by the module. Error Messages Tx The number of error DNP3 packets sent by the module.
Page 84
Diagnostics DNP3 Message Queue Full The DNP3 Router has received too many simultaneous messages to process. Node Mismatch The received message node number did not match the DNP3 Router configured node address. Select Size Too Large When the Select/Operate functionality is used the DNP3 Router supports a maximum of 255 bytes per transaction (or one full DNP3 message).
Diagnostics This may be caused by the External Access property of the Logix tag being set to either None or Read Only. Tag Reads The number of tag read transactions executed by the DNP3 Router module. Tag Writes The number of tag write transactions executed by the DNP3 Router module. ENIP Retries This count increases when no response was received from the Logix Controller by the time the ENIP timeout is reached.
Page 86
Diagnostics Authorization Failures Increases when a user is not authorized to perform a requested operation. Unexpected Responses The other device has responded with a message that was not expected during the authentication process. No Responses The other device has not replied during the authentication process. Aggressive Not Supported When Aggressive Mode Authentication is not supported this will increase.
Page 87
Diagnostics The following Event statistics are only relevant when the module is operating in Reactive mode: Figure 7.9. - Status monitoring – Event Statistics Statistic Description Group The specific DNP3 Group used Event Class The assigned DNP3 Event Class Event Count The number of outstanding events Load Address Memory address of event load index...
Diagnostics Figure 7.10. - Status monitoring – CIP Statistics Statistic Description Class 1 Timeout Count Number of times a Class 1 connection has timed out Class 1 Forward Open Count Number of Class 1 Connection establish attempts Class 1 Forward Close Count Number of Class 1 Connection close attempts Class 1 Connection Count Number of Class 1 Connections currently active...
Page 89
Diagnostics Figure 7.11. - Selecting DNP3 Packet Capture The DNP3 Packet Capture window will open and automatically start capturing all DNP3 packets. Figure 7.12 – DNP3 packet capture To display the captured DNP3 packets, the capture process must first be stopped, by pressing the Stop button.
Page 90
Diagnostics Figure 7.13. – DNP3 Packet Capture complete The captured DNP3 packets are tabulated as follows: Statistic Description Index The packet index, incremented for each packet sent or received. Time The elapsed time since the module powered up. Status The status of the packet. Received packets are checked for valid DNP3 constructs and valid checksums.
Diagnostics The packet capture can be saved to a file for further analysis, by selecting the Save button on the toolbar. Previously saved DNP3 Packet Capture files can be viewed by selecting the DNP3 Packet Capture Viewer option in the tools menu. Figure 7.14.
Diagnostics Figure 7.16. – Module Event Log The log can also be stored to a file for future analysis, by selecting the Save button in the tool menu. To view previously saved files, use the Event Log Viewer option under the tools menu. 7.5.
Page 93
Diagnostics Figure 7.17. - Web interface Document No. D109-010 Page 93 of 108 Revision 1.15...
Technical Specifications 8. TECHNICAL SPECIFICATIONS 8.1. DIMENSIONS Below are the enclosure dimensions as well as the required DIN rail dimensions. All dimensions are in millimetres. Figure 8.1 – DNP3 Router enclosure dimensions Figure 8.2 - Required DIN dimensions Document No. D109-010 Page 94 of 108 Revision 1.15...
Technical Specifications Maximum DNP3 request 1000 bytes size per mapped item in Reactive Tag Mode Maximum DNP3 request 230 bytes size per mapped item in Scheduled Tag Mode Maximum Logix Controller support Unsolicited Response support Maximum event buffer per 100,000 (total of 900,000) DNP3 group Number of Commands per Request...
Appendix – DNP3 reference A. APPENDIX – DNP3 REFERENCE A.1. DNP3 FUNCTIONS Code Function Confirm Read Write Select Operate Direct Operate Direct Operate - No Response Freeze Freeze - No Response Freeze Clear Freeze Clear - No Response Freeze At Time Freeze At Time - No Response Cold Restart Warm Restart...
Appendix – DNP3 reference A.3. SUPPORTED DNP3 GROUP VARIATIONS Group Supported Var. Supports Group Variation Description Recommended Data Type Description Functions Code Events Packed Format SINT Binary Read Inputs ● With Flags AparianDNP3BinaryInputWithFlag Double Bit Packed Format SINT Binary Read ●...
Page 103
Appendix – DNP3 reference A.4. DNP3 QUALIFIER CODE The qualifier code (byte) is made up of the Object Prefix nibble and the Range Field nibble as described in the table below. Bit Number --> Prefix Code Range Specifier Code Table A.5 – DNP3 Qualifier Code Prefix Code Object Prefix Objects packed without a prefix...
Page 104
Appendix – DNP3 reference Qualifier Object Prefix Range Specifier Preferred Code Objects packed without a prefix 8-bit Start-Stop index ● Objects packed without a prefix 16-bit Start-Stop index ● Objects packed without a prefix 32-bit Start-Stop index Objects packed without a prefix 8-bit Start-Stop virtual address Objects packed without a prefix 16-bit Start-Stop virtual address...
Page 105
Appendix – DNP3 reference A.5. DNP3 EVENT STATUS FLAGS Flag desciption Group Bit 0 – Online Bit 1 – Restart Bit 2 – Communication Lost Bit 3 – Remote Forced 2 – Binary Input Events Bit 4 – Local Forced Bit 5 –...
Page 106
Appendix – DNP3 reference Bit 1 – Restart Bit 2 – Communication Lost Bit 3 – Remote Forced Bit 4 – Local Forced Bit 5 – Over range Bit 6 – Reference Error Bit 7 – Reserved Bit 0 – Online Bit 1 –...
Need help?
Do you have a question about the A-DNP3R and is the answer not in the manual?
Questions and answers