MW100-S16 DNP3.
Table of Contents 1. Introduction ..................................................................................................................... 5 2. DNP communication functions ....................................................................................... 6 2.1. Required options for DNP communication ............................................................. 8 2.2. DNP master/client function .................................................................................... 9 2.2.1.
2.4.8.2. DNP master setting screen for polling action ...................................... 77 2.4.8.3. DNP master setting screen for command table ................................... 79 2.4.9. DNP client setting screens ............................................................................ 81 2.4.9.1. DNP client setting screen for polling period ........................................ 81 2.4.9.2. DNP client setting screen for polling action......................................... 83 2.4.9.3.
3.2. DNP object implementation table.......................................................................
1. Introduction DNP 3.0 (Distributed Network Protocol) is a kind of telecommunication standard and is used at electrical distribution industry in America, Africa, Australia and so on. It is designed to transmit relatively small packets of data in a reliable manner specifically for SCADA application. In MW100, DNP communication function has implemented at R3.03 special version and which supports the function of the DNP Master, Slave, Client and Server.
2. DNP communication functions MW100 main module has one ethernet port for TCP/IP communication and one serial port for RS-232, 422/485 communication (optional), and DNP communication function can be used with downloading MW100 R3.03 special firmware which implements DNP protocol. MW100 (I/O Module + Main Module) Ethernet Port (10 / 100 Mbps) Serial Port (Option , RS-232-C or RS-422-A / 485,) MW100 Main Module Figure 1.
Basic specification of serial and ethernet port in MW100, which is used as a datalink of the DNP communication, is shown in Table 1 and Table 2. Table 1. Specification of serial port Item Datalink Specification RS-232-C, RS-422-A / 485 Baud rate 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 bps Parity bits None, Odd, Even Stop bits 1, 2 bit Byte size 8 bit (fixed) Handshake Off : Off (fixed) Table 2.
2.1. Required options for DNP communication As DNP communication function is not the standard feature of MW100, user should specify required options in Table 3 as needed at ordering time. Table 3.
2.2. DNP master/client function DNP master/client functions enable to exchange data between MW100 and IEDs with DNP protocol. Accessible objects with DNP master/client functions are Binary Input, Binary Output, Analog Input, Analog Output, Double-bit, Counter objects only. I/O channel (Max. 60) I/O channel (Max. 60) Math channel (Max. 300) Math channel (Max. 300) Comm. Input channel (Max. 300) Comm. Input channel (Max.
Framework of DNP master/client functions of MW100 is shown in Figure 3. DNP master/client functions have two timers, they are called "Integrity Poll" and "Event Poll" timer, and each timer publish read command and poll class in IED periodically. Time Integrity Poll Read Class 0 + Execute Command table Time Event Poll Read Class 1, 2, 3 + MW100 (Master) Target list Command table Command / Response DNP3.0 Network IED IED (Slave) (Slave) Max. 10 Units Figure 3.
Period of integrity/event poll and publishing commands are configurable at MW100. Parameters for controlling DNP master/client behavior is shown in Table 4. Table 4. Parameters for controlling DNP master/client behavior Kind Integrity Poll Configuration Period and publishing commands for polling static data - period is configurable within 1 to 3600 [s] - class read : - selectable from “Off”, “Class 0”, “Class 0, 1, 2, 3” - publishing command : - Max.
2.2.1. DNP master/client specification Basic specification of DNP master/client functions is shown in Table 5. Table 5. Basic specification of DNP master/client functions Item Accessible objects Specification Binary Input (1) Double-bit (3) Binary Output (10) Counter (20) Analog Input (30) Analog Output (40) Class (60) Configurable destinations Max. 10 units Configurable commands Max.
2.2.2. Enabling DNP master/client functions To use DNP master/client functions of MW100, user should enable these functions at first. Required steps to enable DNP master/client functions are shown in Figure 4 and Figure 5. About the detail of the configuration, refer the explanation of Table 6 and Table 7. Screen of serial communication setting [step 1] select the function (driver) [step 2] configure the master DNP address Screen of DNP 3.0 master setting 1 [step 3] enable the master function Figure 4.
Screen of DNP 3.0 communication setting 1 [step 1] configure the client DNP address Screen of DNP 3.0 client setting 1 [step 2] enable the client function Figure 5.
Table 6. Parameters for enabling DNP master function Kind Function Configuration Choice of serial function (driver) - select ”DNP 3.0 Master” Address 2 DNP address of DNP master function - configurable within 0 to 65519 Master Function Enabling switch of DNP mater function - toggle switch to Enable or not Table 7.
2.2.3. Configuration of destination of DNP master/client To use DNP master/client functions of MW100, user should configure the destination address and behavior of the communication. Items for configuring the destination and behavior of DNP master/client functions are shown in Table 8. About the detail of the configuration, refer the explanation of the pages showed in the table. Table 8. Items for configuring destination and behavior of DNP master/client Item Configuration of destination address Page P.
2.2.3.1. Configuration of destination address Screens for configuring destination address of DNP master/client functions are shown in Figure 6 and Figure 7. When the address field is left to be blank, function of the row is disabled. About the detail of the configuration, refer the explanation of Table 9. Screen of DNP 3.0 master setting 2 Destination address Figure 6.
Screen DNP 30. client setting 2 Destination address Destination IP address and port Figure 7.
Table 9. Parameters for configuring destination address of DNP master/client Kind Address Configuration DNP address of the DNP slave/server - In case of blank, function is disabled - configurable within 0 to 65519 Server IP address of the DNP server - configurable within 0.0.0.0 to 255.255.255.255 Port Service port of the DNP server - configurable within 1 to 65535 3 3 Well-known ports for DNP 3.0 protocol are 20000/tcp and udp.
2.2.3.2. Configuration of polling period and action Screens for configuring polling period and action of DNP master/client functions are shown in Figure 8 and Figure 9. In case the integrity or event poll is not needed, turn off the polling action. About the detail of the configuration, refer the explanation of Table 10. Screen of DNP 3.0 master setting 1 Polling period Screen of DNP 3.0 master setting 2 Polling action Figure 8.
Screen of DNP 3.0 client setting 1 Polling period Screen of DNP 3.0 client setting 2 Polling action Figure 9.
Table 10. Parameters for configuring polling period and action Kind Integrity Poll Configuration Period and publishing commands for polling static data - period is configurable within 1 to 3600 [s] - class read : - selectable from “Off”, “Class 0”, “Class 0, 1, 2, 3” - command publishing : - Max.
2.2.3.3. Configuration of unsolicited message Screens for configuring unsolicited message of DNP master/client functions are shown in Figure 10 and Figure 11. When these switches are enabled, DNP master/client functions will ask DNP slave/servers to enable unsolicited message with publishing Enable/Disable Unsolicited command. About the detail of the configuration, refer the explanation of Table 11. Screen of DNP 3.0 master setting 2 Switch for unsolicited message Figure 10.
Screen of DNP 3.0 client setting 2 Switch for unsolicited message Figure 11.
Table 11.
2.2.4. Configuration of command table of DNP master/client To use DNP master/client functions of MW100, user should configure the command table which describes the mapping information between DNP objects and MW100 channels. Screens for configuring command table of DNP master/client functions are shown in Figure 12 and Figure 13. About the detail of the configuration, refer the explanation of Table 12. Screen of DNP master setting 3 Command setting table Figure 12.
Screen of DNP 3.0 client setting 3 Command setting table Figure 13.
Table 12.
2.2.4.1. Behavior of Poll function When Poll function is specified in the function field, DNP master/client functions search responses from the slave and pick up only objects which have specific group number and index. After that they store the data into the specified MW100 channels. 4 Screen of DNP 3.0 master setting 3 Destination and object Index and channel number - DNP message is not published. - Pick up and store only the data specified.
Polling objects and the setting of group number field in command table of DNP master/client functions are shown in Table 13. Table 13.
2.2.4.2. Behavior of Read function When Read function is specified in the function field, DNP master/client functions will publish Read message to the slave. Following behavior will be the same as Poll function. Screen of DNP 3.0 master setting 3 Destination and object Index and channel number ・Read message is published. ・Pick up and store only the data specified. MW100 (Master) Command Response IED IED (Slave) (Slave) Figure 15.
2.2.4.3. Behavior of Operate function When one of Select + Operate, Direct Operate, Direct Operate NA is specified in the function field, DNP master/client will publish Select, Operate messages to the slave. Screen of DNP 3.0 master setting 3 Destination and object Index and channel number ・Select, Operate messages are published. ・Store the writing data into the messages MW100 (Master) Command Response IED IED (Slave) (Slave) Figure 16.
Operating objects and the setting of group number field in command table of DNP master/client functions are shown in Table 14. Table 14.
2.3. DNP slave/server function DNP slave/server functions enable to exchange data between MW100 and SCADAs with DNP protocol. Accessible objects with DNP slave/server functions are Binary Input, Binary Output, Analog Input, Analog Output objects only. SCADA SCADA (Master) (Client) Command / Response Command / Response RS-232, 422, 485 Ethernet IED IED (Slave) (Server) MW100 (Slave) MW100 (Server) I/O channel (Max. 60) I/O channel (Max. 60) Math channel (Max. 300) Math channel (Max.
Framework of data mapping between DNP objects and MW100 channels in DNP slave/server functions is shown in Figure 24 and Table 15. In MW100, index number assigned to each channel is fixed regardless of the destination object types.
Table 15. Data mapping between DNP objects and MW100 channels Channel I/O channel (001 to 060) Index 0 to 59 Object Binary Input Analog Input Attribute Read only Binary Output Analog Output Writable Math channel (A001 to A300) 1000 to 1299 Binary Input Analog Input Read only Comm.
2.3.1. DNP slave/server specification Basic specification of DNP slave/server functions is shown in Table 16. Table 16. Basic specification of DNP slave/server functions Item Implemented objects Specification Binary Input (1) Binary Output (10) Analog Input (30) Analog Output (40) Time (50) Class (60) Device (80) Available datalink Serial (RS-232, 422/485), Ethernet (TCP/IP, UDP/IP) Accessible device Max. 10 units Permission of unsolicited msg.
2.3.2. Enabling DNP slave/server functions To use DNP slave/server functions of MW100, user should enable these functions at first. Required steps to enable DNP Slave/server functions are shown in Figure 19 and Figure 20. About the detail of the configuration, refer the explanation of Table 17 and Table 18. Screen of serial communication setting [step 1] select the function (driver) [step 2] configure the slave DNP address Figure 19.
Screen of DNP 3.0 communication setting 1 [step 1] configure the server DNP address Screen of server setting [step 2] enable server function Figure 20.
Table 17. Parameters for enabling DNP slave function Kind Function Configuration Choice of serial function (driver) - select ”DNP 3.0 Slave” Address 5 DNP address of DNP slave function - configurable within 0 to 65519 Table 18.
2.3.3. Configuration of destination of DNP slave/server To use DNP slave/server functions of MW100, user should configure the destination address and behavior of the communication. Items for configuring the destination and behavior of DNP slave/server functions are shown in Table 19. About the detail of the configuration, refer the explanation of the pages shown in the table. Table 19. Items for configuring destination and behavior of DNP slave/server Item Permission of unsolicited message Page P.
2.3.3.1. Permission of unsolicited message Screen for permitting unsolicited message to DNP slave/server functions is shown in Figure 21. When this switch is enabled, DNP slave/server functions will accept Enable/Disable Unsolicited command from DNP master/clients. About the detail of the configuration, refer the explanation of Table 20. Screen of DNP 3.0 communication setting 1 Switch for unsolicited message Figure 21.
Table 20.
2.3.3.2. Configuration of destination address Screens for configuring destination address of DNP slave/server functions are shown in Figure 22 and Figure 23. When the address field is left to be blank, function of the row is disabled. About the detail of the configuration, refer the explanation of Table 21. Screen of DNP 3.0 slave setting Destination address Figure 22.
Screen of DNP 3.0 server setting Destination address Destination IP address and port Figure 23.
Table 21. Parameters for configuring destination address of DNP slave/server Kind Address Configuration DNP address of the DNP master/client - In case of blank, function is disabled - configurable within 0 to 65519 Client IP address of the DNP client - configurable within 0.0.0.0 to 255.255.255.255 Port Service port of the DNP client - configurable within 1 to 65535 7 7 Well-known ports for DNP 3.0 protocol are 20000/tcp and udp.
2.3.4. Configuration of object table of DNP slave/server To use DNP slave/server functions of MW100, user should configure the object table which describes the mapping information between DNP objects and MW100 channels. Data mapping between DNP objects and MW100 channels are shown in Figure 24. In MW100, index number assigned to each channel is fixed regardless of the destination object types.
Screen for configuring object table of DNP slave/server functions is shown in Figure 25. About the detail of the configuration, refer the explanation of Table 22. Screen of DNP 3.0 object setting Range of mapping channel Event class and default variation Figure 25.
Table 22.
Example of the object table configuration is shown in Figure 26. Only the mapped channel data in this table become accessible from DNP master/client. Screen of DNP 3.
2.3.4.1. Configuration of data variation In MW100, variations of static / event data are configurable. Screens for configuring data variation are shown in Figure 27. About the detail of the configuration, refer the explanation of Table 23. Screen of DNP 3.0 object setting Default variation Screen of DNP 3.0 communication setting 1 Switch for timestamp Figure 27.
Table 23.
Responded variations to static polls are shown in Table 24. When static data are read with variation zero, DNP slave/server functions will respond with default variation set in the object table. Table 24.
Responded variations to event polls are shown in Table 25. When event data are read with variation zero, DNP slave/server functions will respond with the same data type to the default variation with putting timestamp information as needed. Table 25.
2.4. DNP configuration screens DNP communication functions are configurable using Web service of MW100. Web service can be used with putting address of the MW100 into URL of Web browser. Communication setting Web Service Ethernet MW100 Figure 28.
Anchor points to configuration screens for DNP communication functions are shown in Figure 29. Serial communication setting IP address setting Server setting DNP communication function settings Figure 29.
Configuration screens related with DNP master, slave, client and server function are shown in Table 26. About the detail of the configuration, refer the explanation of the pages shown in the table. Table 26. Configuration screens related with each DNP communication function DNP master DNP slave DNP server DNP client DNP master setting DNP slave setting DNP server setting DNP client setting P. 75 P. 69 P. 71 P. 81 DNP object setting P. 73 DNP communication setting P. 64 Server setting P.
2.4.1. Serial communication setting screen Serial communication setting screen is shown in Figure 30. About the detail of the configuration, refer the explanation of Table 27. Figure 30.
Table 27. Parameters for configuring serial communication Kind Function Configuration Choice of serial function (driver) - selectable from ”DNP 3.0 Master”, “DNP 3.
2.4.2. IP address setting screen IP address setting screen is shown in Figure 31. About the detail of the configuration, refer the explanation of Table 28. Figure 31.
Table 28. Parameters for configuring IP address Kind Host Name Configuration Host name of MW100 - ignored (not used at DNP client/server) Domain Name Domain name of MW100 - ignored (not used at DNP client/server) IP Address IP address of MW 100 - configurable within 0.0.0.0 to 255.255.255.255 Subnet Mask Subnet mask of MW 100 - configurable within 0.0.0.0 to 255.255.255.255 Default Gateway Default gateway of MW 100 - configurable within 0.0.0.0 to 255.255.255.
2.4.3. Server setting screen Server setting screen is shown in Figure 32. About the detail of the configuration, refer the explanation of Table 29. Figure 32.
Table 29. Parameters for configuring server function Kind TCP Keep Alive Configuration Period of TCP keep alive - ignored (not used at DNP server) Application Timeout Application service timeout - ignored (not used at DNP server) Action Enabling switch of server function - selectable from ”On”, “Off” Port Service port of the server - configurable within 1 to 65535 10 10 Well-known ports for DNP 3.0 protocol are 20000/tcp and udp.
2.4.4. DNP communication setting screens 2.4.4.1. DNP communication setting screen for application service DNP communication setting screen for application service is shown in Figure 33. About the detail of the configuration, refer the explanation of Table 30. Figure 33.
Table 30.
2.4.4.2. DNP communication setting screen for protocol stack behavior DNP communication setting screen for protocol stack behavior is shown in Figure 34. About the detail of the configuration, refer the explanation of Table 31 and Table 32. Figure 34.
Table 31.
Table 32.
2.4.5. DNP slave setting screen DNP slave setting screen is shown in Figure 35. About the detail of the configuration, refer the explanation of Table 33. Figure 35.
Table 33.
2.4.6. DNP server setting screen DNP server setting screen is shown in Figure 36. About the detail of the configuration, refer the explanation of Table 34. Figure 36.
Table 34. Parameters for configuring destination address of DNP server Kind Address Configuration DNP address of the DNP client - In case of blank, function is disabled - configurable within 0 to 65519 Client IP address of the DNP client - configurable within 0.0.0.0 to 255.255.255.255 Port Service port of the DNP client - configurable within 1 to 65535 11 11 Well-known ports for DNP 3.0 protocol are 20000/tcp and udp.
2.4.7. DNP object setting screen DNP object setting screen is shown in Figure 37. About the detail of the configuration, refer the explanation of Table 35. Figure 37.
Table 35.
2.4.8. DNP master setting screens 2.4.8.1. DNP master setting screen for polling period DNP master setting screen for polling period is shown in Figure 38. About the detail of the configuration, refer the explanation of Table 36. Figure 38.
Table 36.
2.4.8.2. DNP master setting screen for polling action DNP master setting screen for polling action is shown in Figure 39. About the detail of the configuration, refer the explanation of Table 37. Figure 39.
Table 37.
2.4.8.3. DNP master setting screen for command table DNP master setting screen for command table is shown in Figure 40. About the detail of the configuration, refer the explanation of Table 38. Figure 40.
Table 38.
2.4.9. DNP client setting screens 2.4.9.1. DNP client setting screen for polling period DNP client setting screen for polling period is shown in Figure 41. About the detail of the configuration, refer the explanation of Table 39. Figure 41.
Table 39.
2.4.9.2. DNP client setting screen for polling action DNP client setting screen for polling action is shown in Figure 42. About the detail of the configuration, refer the explanation of Table 40. Figure 42.
Table 40.
2.4.9.3. DNP client setting screen for command table DNP client setting screen for command table is shown in Figure 43. About the detail of the configuration, refer the explanation of Table 41. Figure 43.
Table 41.
2.5. DNP configuration commands Extended or added commands to the MW100 specific service (34318/tcp) is shown in Table 42. Current setting of each command can be acquired with query operation, and new settings are accepted only at setting mode and administrator level. Table 42. Extended or added commands for DNP communication functions Cmd.
2.5.1. Serial communication setting (YS) This command is used to configure serial communication function. For implementing DNP communication functions, new switches named DNP3_M and DNP3_S are added to p1 parameter for enabling DNP master/slave functions.
2.5.2. Enabling server function (WS) This command is used to enable server functions. For implementing DNP communication functions, new switch named DNP3 is added to p1 parameter for enabling DNP server functions.
2.5.3. Enabling client function (WC) This command is used to enable master/client functions, to implement DNP communication functions, new switch named DNP3_M and DNP3_C are added to p1 parameter for enabling DNP master/slave functions.
2.5.4. DNP master action setting (WM) This command is used to configure action of DNP master. For implementing DNP communication functions, this command is added. - Setting WM p1, p2, p3 16 p1 : Period of integrity poll [s] (1 to 3600) p2 : Period of event poll [s] (1 to 3600) p3 : Response timeout [s] (1 to 60) - Query WM ? 16 Unless MATH and DNP option is specified, command can't be used.
2.5.5. DNP master destination setting (WN) This command is used to configure destination of DNP master. For implementing DNP communication functions, this command is added.
2.5.6. DNP master command table setting (WO) This command is used to configure command table of DNP master. For implementing DNP communication functions, this command is added.
2.5.7. DNP client action setting (WP) This command is used to configure action of DNP client. For implementing DNP communication functions, this command is added. - Setting WP p1, p2, p3 21 p1 : Period of integrity poll [s] (1 to 3600) p2 : Period of event poll [s] (1 to 3600) p3 : Response timeout [s] (1 to 60) - Query WP ? 21 Unless MATH and DNP option is specified, command can't be used.
2.5.8. DNP client destination setting (WQ) This command is used to configure destination of DNP client. For implementing DNP communication functions, this command is added.
2.5.9. DNP client command table setting (WR) This command is used to configure command table of DNP client. For implementing DNP communication functions, this command is added.
2.5.10. DNP client/server address setting (WU) This command is used to configure DNP addresses of DNP client/server. For implementing DNP communication functions, this command is added. - Setting WU p1, p2 26 p1 : DNP address of DNP client (0 to 65519) p2 : DNP address of DNP server (0 to 65519) - Query WU ? 26 Unless DNP option is specified, command can't be used.
2.5.11. DNP slave/server object table setting (WV) This command is used to configure object table of DNP slave/server. For implementing DNP communication functions, this command is added.
p5 : Default variation (1 to 6) - 1, 2 : in case p1is xx_BI 1, 2 : in case p1 is xx_BO 1 to 6 : in case p1 is xx_AI 1 to 4 : in case p1 is xx_AO Query WV [p1] ? - 99/131 - IM MW100-S16E-1 Ed01
2.5.12. DNP slave destination setting (VV) This command is used to configure destination of DNP slave. For implementing DNP communication functions, this command is added. - Setting VV p1, p2 28 29 p1 : Destination number (01 to 10) p2 : DNP address of DNP master (0 to 65520) - Query VV [p1] ? 28 Unless DNP option is specified, command can't be used. 29 When 65520 is set to p2, entry is disabled.
2.5.13. DNP server destination setting (VW) This command is used to configure destination of DNP server. For implementing DNP communication functions, this command is added. - Setting VW p1, p2 (in case p2 is 65520) VW p1, p2, p3, p4 (in case p2 is not 65520) 30 31 p1 : Destination number (01 to 10) p2 : DNP address of DNP client (0 to 65520) p3 : IP address of DNP client (0.0.0.0 to 255.255.255.
2.5.14. DNP application service setting (WW) This command is used to configure application service of DNP slave/server. For implementing DNP communication functions, this command is added.
2.5.15. DNP application layer setting (WX) This command is used to configure behavior of application layer of DNP protocol stack. For implementing DNP communication functions, this command is added.
2.5.16. DNP datalink layer setting (WY) This command is used to configure behavior of datalink layer of DNP protocol stack. For implementing DNP communication functions, this command is added.
2.6. DNP log and summary output Added functions to the log and summary output command (FL) are shown in Table 43. Table 43.
2.6.1. Log and summary output (FL) This command is used to output log or summary. To implement DNP communication functions, new parameter named DNP3_M, DNP3_C, DNP3_S, DNP3_T and DNP3_MC, DNP3_MS, DNP3_CC, DNP3_CS are added.
MODBUS_S : Modbus slave log MODBUS_T : Modbus server log MATH : Math computation log CMD : Device operation log RECSTATUS : Recording status DNP3_M : DNP master log DNP3_C : DNP client log DNP3_S : DNP slave log DNP3_T : DNP server log p3 : Maximum number of lines to output (refer Table 44) Table 44. Maximum number of lines to output Data kind (p2) ERROR MEDIA ALARM MESSAGE COM FTPC SMTP DHCP SNTP FTPS HTTP Max.
- Setting to output summary FL p1, p2, p3, p4 (in case p1 is 1) p1 : Output type (1) 1 : Output summary p2 : Data kind (MODBUS_MC, MODBUS_MS, MODBUS_CC, MODBUS_CS, DNP3_MC, DNP3_MS, DNP3_CC, DNP3_CS) MODBUS_MC : Modbus master command status MODBUS_MS : Modbus master connection status MODBUS_CC : Modbus client command status MODBUS_CS : Modbus client connection status BALANCE : Results of initial balancing of strain inputs DNP3_MC : DNP master command status DNP3_MS : DNP master connection status DNP
2.6.2. DNP master log output (FL0, DNP3_M) Format and example of DNP master log output is shown in Table 46. Table 46. Format of DNP master log output EA CrLf yy/mo/dd hh:mm:ss xxx mmm... CrLf : EN CrLf yy year (00 to 99) mo month (01 to 12) dd day (01 to 31) hh hour (00 to 23) mm minute (00 to 59) ss second (00 to 59) xxx : number of command (001 to 100, ---) mmm... : status of command (refer Table 56) Table 47.
2.6.3. DNP client log output (FL0, DNP3_C) Format and example of DNP client log output is shown in Table 48. Table 48. Format of DNP client log output EA CrLf yy/mo/dd hh:mm:ss xxx mmm... CrLf : EN CrLf yy year (00 to 99) mo month (01 to 12) dd day (01 to 31) hh hour (00 to 23) mm minute (00 to 59) ss second (00 to 59) xxx : number of command (001 to 100, ---) mmm... : status of command (refer Table 56) Table 49.
2.6.4. DNP slave log output (FL0, DNP3_S) Format and example of DNP slave log output is shown in Table 50. Table 50. Format of DNP slave log output EA CrLf yy/mo/dd hh:mm:ss d: mmm ... CrLf : EN CrLf yy year (00 to 99) mo month (01 to 12) dd day (01 to 31) hh hour (00 to 23) mm minute (00 to 59) ss second (00 to 59) d message kind (C : command, R : response) mmm... message digest Table 51.
2.6.5. DNP server log output (FL0, DNP3_T) Format and example of DNP server log output is shown in Table 52. Table 52. Format of DNP server log output EA CrLf yy/mo/dd hh:mm:ss d: mmm ... CrLf : EN CrLf yy year (00 to 99) mo month (01 to 12) dd day (01 to 31) hh hour (00 to 23) mm minute (00 to 59) ss second (00 to 59) d message kind (C : command, R : response) mmm... message digest Table 53.
2.6.6. DNP master command status output (FL1, DNP3_MC) Format and example of DNP master command status output is shown in Table 54. Table 54. Format of DNP master command status output EA CrLf scan = x, time = y ms CrLf CrLf xxx mmm... CrLf : EN CrLf x: count of executed commands (0 to 100) y: execution time of commands [ms] (0 to .. ) xxx : number of command (001 to 100) mmm... : status of command (refer Table 56) Table 55.
Status of DNP master/client commands are shown in Table 56. Table 56.
2.6.7. DNP master connection status output (FL1, DNP3_MS) Format and example of DNP master connection status output is shown in Table 57. Table 57. Format of DNP master connection status output EA CrLf xx mmm... CrLf : EN CrLf xx : Destination number (01 to 10) mmm... : Connection status to the destination (refer Table 59) Table 58.
Status of DNP master/client connections are shown in Table 59. Table 59.
2.6.8. DNP client command status output (FL1, DNP3_CC) Format and example of DNP client command status output is shown in Table 60. Table 60. Format of DNP client command status output EA CrLf scan = x, time = y ms CrLf CrLf xxx mmm... CrLf : EN CrLf x: count of executed commands (0 to 100) y: execution time of commands [ms] (0 to .. ) xxx : number of command (001 to 100) mmm... : status of command (refer Table 56) Table 61.
2.6.9. DNP client connection status output (FL1, DNP3_CS) Format and example of DNP client connection status output is shown in Table 62. Table 62. Format of DNP client connection status output EA CrLf xx mmm... CrLf : EN CrLf xx : Destination number (01 to 10) mmm... : Connection status to the destination (refer Table 59) Table 63.
2.7. Conversion of channel data Data expression at binary and analog objects in DNP protocol is shown in Figure 44. Basically data of DNP objects is composed with flag and value.
Bit composition of Flag is shown in Table 64. When the measurement or computation of MW100 has successfully executed and valid value has produced, Online bit in flag will be asserted. Some other bits might be asserted in some condition. Table 64.
MW100 uses only the bit 0 (Online), bit 1 (Restarted) and bit 5 (Over-Range), and other bits will be kept un-asserted (i.e. zero). Behavior of flag in MW100 is shown in Table 65. Table 65. Behavior of flag in MW 100 1. When slave/server has restarted or connection has initialized, Restart bit will be asserted. 2. When the value of measurement/computation channel became +Over, -Over or Valid, Online bit will be asserted. 3.
Mapping rules of MW100 channel data to the specific variation of DNP object objects are shown in Table 66 to Table 68. Table 66.
Table 67.
Table 68.
3. Appendix 3.1. DNP device profile DNP device profile of MW100 special firmware for DNP protocol is shown in Table 69 to Table 71. Table 69. DNP device profile (1/3) DNP 3 DEVICE PROFILE DOCUMENT Vendor Name : Yokogawa Electric Corporation Device Name : MW100 R3.
Table 70. DNP device profile (2/3) DNP 3 DEVICE PROFILE DOCUMENT Timeouts while waiting for : Data Link Confirm : Complete Appl. Fragment : Application Confirm : Complete Appl.
Table 71.
3.2. DNP object implementation table DNP object implementation table of DNP slave/server function in MW100 is shown in Table 72 to Table 75. Table 72. DNP object implementation table (1/4) DNP3 OBJECT IMPLEMENTATION TABLE OBJECT Grp. Var.
Table 73. DNP object implementation table (2/4) DNP3 OBJECT IMPLEMENTATION TABLE OBJECT Grp. Var.
Table 74. DNP object implementation table (3/4) DNP3 OBJECT IMPLEMENTATION TABLE OBJECT Grp. Var.
Table 75. DNP object implementation table (4/4) DNP3 OBJECT IMPLEMENTATION TABLE OBJECT Grp. Var.
