WSOS01-DOC-102 ADVC Protocol Configuration Tool R10 WEB

Protocol Configuration Tool Technical Manual for the ADVC Controller Range

Scope of this document

This docu document ment desc describe ribes s the featu features res and an d operation of the Protocol Configuration Tool for WSOS.

Limitations This docu document ment is copyrig co pyrig ht and is provide pr ovided d solely for the use of the recipient. It is not to be copied in any way, nor its contents divulged to any third party, nor to be used as the basis of a tender or specification without the express written permission of Schneider Electric (Australia) Pty Limited. This docu document ment discl oses confi confidenti denti al inte llect llectual ual property that belongs to Schneider Electric (Australia) Pty Limited. This document does not invest any rights to Schneider Electric (Australia) Pty Limited intellectual property in the recipient. Moreover, the recipient is required not to disclose any of the intellectual property contained in this document to any other party unless authorised in writing by Schneider Electric (Australia) Pty Limited.

Disclaimer The advis a dvisory ory proce dures and inform i nformation ation contained within this document have been compiled as a guide to the safe and effective operation of products supplied by Schneider Electric. It has been prepared in conjunction with references from sub-assembly suppliers and the collective experience of the manufacturer. In-service conditions for use of the products may vary between customers and end-users. Consequently, this document is offered as a guide only. It should be used in conjunction with the customers own safety procedures, maintenance program, engineering judgment and training qualifications. No responsibility, either direct or consequential, for injury or equipment failure can be accepted by the manufacturer resulting from the use of this document.

2 | Schneider Electric

Copyright ©2012 by Schneider Electric (Australia) Pty Limited All Right Rights s Reserve Res erve d. No part of the contents of this document may be reproduced or transmitted in any form or by any means without the written permission of the manu facturer.

Document part number WSOS01-DOC-102

Revision R10

Revision history: R0 0

C re re at ated f ro ro m N00-718R01

18/06/2004

R01 R0 1

Update Upda ted d fo forr la laun unch ch features, screen shots, etc.

17/10/2004

R02 R0 2

Updatted sc Upda scre reen en shots again

23/11/2004

R03 R0 3

Minorr cor Mino corre rect ctio ions ns as as per per document review

25/11/2004

R04 R0 4

New ver New versi sion on of of Prot Protoc ocol ol Configuration Tool

22/6/2005

R0 5

Up da dated WS WSOS 5 sections to reflect new changes

07/07/2005

R06 R0 6

Protoc Prot ocol ol Confi Configu gura rati tion on Tool merged merg ed into in to WSOS with Analog Input changes

17/10/2005

R07 R0 7

Minorr ch Mino chan ange ges s to update document

30/03/2006

R08 R0 8

Clarify Clar ify An Anal alog ogue ue In Inpu puts ts Dead-bands column.

30/03/2006

R09 R0 9

Updatted co Upda comp mpan anyy name, address and phone numbers.

08/07/2009

R10

M od b us

13 / 01/ 2010

Contents

1.

Introduction

4

1.1

Scope

4

2.

Overview of Protocol Configuration 4

3.

Operation of Protocol Configuration Tool

5

3.1

Creating New Files

5

3.2

List of figures Figure 1: Overview of protocol configuration tool

4

Figure 2: Creating a new file in the File Options dialog box

5

Opening Existing Protocol Mappings 5

Figure 3: Selecting existing files

5

3.3

Deleting Existing Protocol Mappings 5

3.4

Main Interface

5

Figure 4: Delete Protocol Configuration Files Dialog Box

5

3.4.1

Menu Items

6

Figure 5: Main Screen showing a standard ACR mapping

6

3.4.2

Toolbar

7

Figure 6: Toolbar

7

3.4.3

Input/ Output and Counter Tabs

8

Figure 7: Configuration Toolbox

8

3.4.4

Configuration Tool Box

8

3.5

Upgrading Software Versions

8

Figure 8: Binary Input Tab (For DNP3, MITS & Modbus protocols respectively)

9

4.

Creating a Protocol Mapping

9

4.1

Binary Inputs

9

4.2

Analog Inputs

10

Figure 9: Analog Input Tab for DNP3, MITS and Modbus protocols

10

4.3

Counters

12

Figure 10: Counter Tab

12

4.4

Binary Outputs

13

4.5

Analog Outputs

14

Figure 11: Binary Output Tab for DNP3, MITS & Modbus protocols

13

5.

Using Protocol Mappings in WSOS 15

Figure 12: Analog Output Tab for DNP3 & Modbus protocols

14

5.1

Adding DNP3, MITS and Modbus Protocol to controller configuration

Figure 13: Add DNP3, MITS and Modbus Protocols

15

Figure 14: Reading a protocol map from a controller

16

Figure 15: Selecting a DNP3 map

17

Figure 16: Selecting a MITS map

17

Figure 17: Selecting a Modbus map

17

Figure 18: Writing a map to a controller

18

5.2

5.3

5.4

Reading Existing DNP3, MITS and Modbus Mappings from the Controller

15

16

Attaching Protocol Mappings to Switchgear Device Configurations 17 Writing New DNP3/M ITS/Mo dbus Mappings into the Controller

18

Removing Protocol Mappings from the Controller

18

6.

Technical Appendix

19

6.1

File Locations

19

6.2

DNP3 Term Glossar y

19

6.2.1

DNP3 Classes

19

6.3

DNP3 Specifications

19

7.

Index

20

5.5

Technical Manual for the WSOS Protocol Configuration Tool (WSOS01-DOC-102) | 3

1. Introduction The Protocol Configuration Tool allows WSOS users to generate custo m DNP3, MITS and Modb us I/O mappings and load them into a switchgear device controller.

1.1 Scope The Protocol Configuration Tool can o nly create mappin gs that are compatible with ADVC soft ware versions A41-03.xx or higher for DNP3 protocol maps, version A42-00.00 or higher for MITS protocol maps, versio n A44-14.00 or higher for Mod bus protocol maps. The Tool is available with WSOS version 5.1.0 or later an d will work on Microsof t Windows 2000 and XP. The MITS protocol is suppor ted in WSOS version 5.1.20 onwards. The Mod bus protocol is supported in WSOS version 5.6.23 onwards. Note: A full des cription of the manufacturer’s DNP3 implement ation is avai lable in the “DN P3 Protocol Technical Manual for Advanced Controllers”, Part Number ADC01-DOC-146. The corresponding description of the MITS protocol is available in “ADVC MITS Technical Manual”, Part Number ADC01-DOC-210. The corresponding description of the Modbus protocol is available in “MODBUS Protocol Technical Manual for ADVC Controller Range”, Part Number ADC01-DOC-357. It is important to read these documents before attempting to create protocol mappings with this tool. A copy of this manual can be viewed by selecting “Help -> Tech Manual” from the Tool menu.

2. Overview of Protocol Configuration Custom protocol maps can be created and loaded into a controller directly from WSOS. The m appings and I /O lo gic are create d using the tool and saved to a mapping file on the WSOS computer. Once a valid file has b een created, it is linked to switchgear device configuration in WSOS and written into the controller. A file is treated as a librar y file. In other words, one protocol map can be linked to multiple switchgear configurations. Refer to section 5 for a description of this process.

Figure 1: Overview of protocol configuration tool

The t ypes of actions that can be mapp ed are dependent on the software version loaded in the Switchgear Device’s controller. When the tool is started the user is asked to input the software version. This is then used to retrieve a valid set of points to use when constructing mappings within the tool. The p rotocol confi guration tool is intend ed to be used Off-Line only. Mappings are created, saved and linked to a WSOS switchgear device configuration while disconnected from the switchgear. Once these tasks have be en completed the user connects to the device and writes the new mapping into the controller along with the switchgear device configuration.

WARNING Make sure the Tool is closed after a mapping has been edited. If the Tool is left open while the Automatic Data Retrieval feature is running it may attempt to update a mapping file that is already open in the Tool. This will either cause the read operation to fail or result in a situation where the newly read file differs from the file open within the Tool. 4 | Schneider Electric

3. Operation of Protocol Configuration Tool To start the protocol configuration tool select “Customise -> Co nfigurable DNP3 -> Configure Protocol Mapping” from the WSOS menu. This launches the tool and displays the “File Options” dialog. The dialog is used to create new blank mapping files or select existing mapping files for editing by selecting the appropriate radio button.

3.1 Creating New Files When creating a new file it is necessary to input the software version running within the controller. The software version can be obtained from the Switchgear Wear/General Details screen on the controller itself. The software determines which points are available in the Configuration Toolbox. If the software version running in the controller is later than that allowed by the tool, the latest allowed version should be entered. After entering these details click the “OK” button to open the blank file.

Figure 2: Creating a new file in the File Options dialog box.

3.2 Opening Existing Protocol Mappings To select an existing protocol mapping file, sele ct the “Existi ng” radio button to display a list of files. Select a file and click “Open” to view the file in the tool. Note that files created with a version number of 42 or greater are labelled with a ‘.PTM’ file extension, whereas map versions created with a major vers ion number of 41 have a ‘.D3M’ file extension. This change has been made to facilitate the addition of t he MITS proto col. Refer to Figure 3.

3.3 Deleting Existing Protocol Mappings

Figure 3: Selecting existing files.

This deletion will remove ex isting proto col mappings f rom lo cal ha rd disk. This can be done from within WSOS by going to “Customise -> Configurable Protocol Tool -> Delete ADVC Protocol Mappin gs” on the menu to display the dialog box shown in Figure 4. Select a mapping from the drop-down box and click the “Delete” button. The delete feature will not allow a mapping to be deleted if it is being referenced by a switchgear device configuration in WSOS.

Figure 4: Delete Protocol Configuration Files Dialog Box


3.4 Main Interface Once a new file has been created or an existing file has been selected the tool’s main screen is displayed as shown in Figure 5.

Figure 5: Main Screen showing a standard ACR mapping.

3.4.1 Menu Items The Protocol Configuration Tool menu in WSOS has the following options: Protocol File New

Closes the current file and allows the creation of a new file using the File Options dial og describe d in section 3.1.

Open

Closes the current file and allows the selection of an existing mapping using the File Options dialog as described in section 3.2.

Save

Saves the current file to the hard drive. If the file is new and this is the first time it has been saved, the Save As dialog will be opened allowing the user to type in a name before saving.

Save As

Opens the Save As dialog box. This allows an existing file to be saved under a new name.

The n ew file name is limited to 40 characters. T his limitat ion is to make it compatible with the naming convention used within the switchgear controller. Note: The Tool expects files to be located in a particular directory on the hard drive. If the file is saved in an alternative location it will not be listed in the File Options dialog box when opening existing files. Refer to section 6.1 for further details.


3.4.1 Menu Items (cont.) Protocol Point Insert Point

Inserts a new row at the current cursor position on the grid so that a new point can be added to the protocol map.

Delete Point

Deletes a row at the current cursor position on the grid shifting rows in the table below the deleted point upwards. (New row added to the end of the grid).

DNP Binary Inputs Analog Inputs Counters Binary Outputs Analog Outputs

Lists the Lists the Lists the Lists the Lists the

MITS Binary Inputs Analog Inputs Binary Outputs

Lists the Binary Inputs used in the mapping. Lists the A nalog Inpu ts used in the mapping. Lists the Binary Outputs used in the mapping.

MODBUS Binary Inputs Analog Inputs Binary Outputs Analog Outputs

Lists the Lists the Lists the Lists the

Print

Binary Inputs used in the mapping. Analog Inputs used in the mapping. Counters used in the mapping. Binary Outputs used in the mapping. Analog Ou tputs used in the mapping.

Binary Inputs used in the mapping. Analog Inputs used in the mapping. Binary Outputs used in the mapping. Analog Ou tputs used in the mapping.

Prints a report listing the mappings used in the current file.

Protocol Configuration Tool Help DNP3 Technical Manual

DNP Protocol Technical Manual For Automatic Circuit Reclosers with Advanced Controllers

MITS Technical Manual

MITS Telemetry Protocol Technical Manual For Automatic Circuit Reclosers with Advan ced Controllers

MODBUS Technical Manual

MODBUS Protocol Technical Manual for ADVC Controller Range

Points List

HTML file containing list and description of configurable points

Manual

Technical Manual for WSOS Protocol Configuration Tool

Protocol View Configuration Toolbox

See section 3.4.4 for detailed description

Toolbar

Hide s and disp lays th e toolbar

3.4.2 Toolbar Below the menu is a tool bar with two buttons with icons and three or five buttons depending on which protocol map you are configuring. The buttons with the icons are used to launch the input/ output Configuration Toolbox and Upgrade Software Version dialog.

Figure 6: Toolbar


3.4.3 Input/Output and Counter Tabs There are five tabbed pages in the tool for DNP3: Binary Inputs Analog In puts Counters Binary Outputs Analog Ou tputs

Lists the Binary Inputs used in the mapping. Lists the A nalog Inpu ts used in the mapping. Lists the Counters used in the mapping. Lists the Binary Outputs used in the mapping. Lists the A nalog Outputs used i n the m apping.

There are three tabbe d pages in the tool for MITS : Binary Inputs Analog In puts Binary Outputs

Lists the Binary Inputs used in the mapping. Lists the A nalog Inpu ts used in the mapping. Lists the Binary Outputs used in the mapping.

There are four tabbed pages in the tool for MODBUS: Binary Inputs Analog In puts Binary Outputs Analog Ou tputs

Lists the Binary Inputs used in the mapping. Lists the A nalog Inpu ts used in the mapping. Lists the Binary Outputs used in the mapping. Lists the A nalog Outputs used i n the m apping.

3.4.4 Configuration Tool Box The configuration tool box panel is launched by click ing the Toolbox button or by using the [Ctrl-T] keyboard shortcut. For a selected device and given software version the tree contains every available point. The tree di splays dif ferent points depend ing on which tab is selected. For example, if the Counters tab is selected then only accumulators and protocol specific data will be displayed on the tree. When a point is selected on the tree the “Point Information” window below displays relevant details such as a short description of the point, resolutions and units. The tree can be s earched entering words into the “Search for” textbox. The to olbox uses these lette rs to limit what appears o n the t ree. For example, typing the word “phase” into the box filters the tree to show all points with the word “phase” as part of its title. Figure 7: Configuration Toolbox

Note: A full points list is available in HTML format by selecting “Help -> Points List ” from the Tool’s menu.

3.5 Upgrading Software Versions This feature allows the user to take advantage of additional features that may be available when the controller software version has been upgraded to a later version. Clicking this button will have the effect of making extra points available in the configuration toolbox for creating mappings. The U pgrad e Sof tware Version but ton will only be activated if the Tool detects that the software version actually loaded in the controller from which the mapping has been read, is greater than the software version stored within the mapping. In all other cases it will be de-activated.

WARNING If a mapping is upgraded to a newer software version it will then be incompatible with other switchgear devices running older software. Make sure the software version you are upgrading to is compatible with all other switchgear devices you wish to use the mapping in before upgrading. If the mapping software version is incompatible you will not be ab le to write it into the switchge ar.


4. Creating a Protocol Mapping The P rotocol Configuration Tool allows the us er to b uild custom mappings to suit the ir own application. Points are added by selecting a row on one of the tabbed pages then double clicking or dragging a point from the Configuration Toolbox. If a row is not selected, the point will either be entered at the top of the table or into the last selected row. If a point is already there i t will be over-written. Points are deleted by selecting a row and pressing “Delete” on the keyboard or selecting “Edit -> Delete Point” from the menu. You can choose to either shift all the rows bel ow up o ne, or leave the ent ire row b lank. A bl ank row represents a reserved or unused DNP id, MITS id or Modbus point. Its value is defaulted to zero. The p oints listed in the Configuration Toolb ox are d etermi ned by the software version number entered when the file was first created.

4.1 Binary Inputs Binary inputs are used to report the status of binary points. DNP ID

Specifies the DNP ID number of the point. Range: 0 to 255 for Binary Inputs This field is read-on ly

MITS ID

Specifies the MITS ID number of the point. Range: 0x10 to 0x1f with 16 points per MITS ID This field is read-on ly

Address

Specifies the Modbus address of the point. Range: 0 to 255 for Binary Inputs This field is read-on ly

Name

The name of the point as defined in the Configuration Toolbox. This field can b e changed in two ways: •

•

Figure 8: Binary Input Tab (For DNP3, MITS & Modbus protocols respectively)

By dragging a point from the configuration tool box into the cell. Selecting the cell then double clicking a point in the configuration toolbox.

Enabled

Gives the user the ability to deactivate a point in the protocol map without removing the configured point. If the point is disabled, data for this point is still included in the map when it is uploaded to the RTU. The point will be configured, however, the settings will have no effect on the RTU. This field is unavailable in the Modbus protocol.

Class

The DNP3 class of the point. The default class can be modified by selecting from the drop-down list. This field is unavailable in the MITS and Modbus protocols. Range: 0, 1, 2, 3. See section 6.2.1 for a description of Classe s in DNP3.still present.

Invert

Specifies whether the point will be inverted. If the point is inverted it will be transmitted when the condition is false rather than true. Range: Yes, No.

Comments

Used to add descriptive comments about the point. The comment is saved to the mapping file when saved but is not written into the controlle r.


4.2 Analog Inputs Anal og Points are used to transmit an alog data s uch as line currents, voltages and contact life. Analog inputs are created by adding points as required, then modifying the parameters from the defaults if necessary.

DNP ID

Specifies the DNP ID number of the point. Range: 0 to 127 This field is read -only

MITS ID

Specifies the MITS ID number of the point. Range: 0x20 to 0x2f with 8 points per MITS ID This field is read -onl y

Addre ss

Specifies the Modbus address of the point. Range: 0 to 127 for Analog Inputs This field is read-only

Name

The name of the point as defined in the Configuration Toolbox. This field can be chan ged in two ways: •

•

Figure 9: Analog Input Tab for DNP3, MITS and Modbus protocols.



Point Min

Represents the minimum value in engineering units that can be measured by the device. The precision of data for all items in the row in engineering units is given by the number of decimal places after the number - in most instances with some exceptions this value will be to the nearest integ er.

Enabled


Class

The DNP3 class of the point. The default class can be modified by selecting from the drop-down list. This field is unavailable for the MITS protocol. Range: 0, 1, 2, 3. See section 6.2.1 for a description of Classes in DNP3.

4.2 Analog Inputs (cont.) Protocol Min

The minimum returnable value for the analog input. For DNP3 and MITS, the default value displayed is determined by the “Return Min”, “Resolution” and Multiplier” values listed in the Configuration Toolbox. For Modbus, the default value displayed is determined by the “Point Min” and “Multiplier”. This field is read-only. Its value will change if the “Multiplier” is modified.

Protocol Max

The maximum returnable value for the analog input. For DNP3 and MITS, the default value displayed is determined by the “Return Min”, “Resolution” and Multiplier” values listed in the Configuration Toolbox. For Modbus, the default value displayed is determined by the “Point Max” and “Multiplier”. This field is read-only. Its value w ill change if the “Multiplier” is modified.

Multiplier

For DNP3 and MITS, the multiplier is used to multiply/div ide the reported analog value by the amount entered. For example, a multipler of ten will divide the protocol max, protocol min and deadband (protocol units) relative to a multiplier of 1. For example, a multip lier of 10 given an initial multiplier of 1 will divide the values by 10. A multiplier of 10 given and initial multiplier of 100 will multiply the values by 10. For Modbus, the multiplier is used to divide the reported analog value by the amount entered. For example, a multipler of ten will divide the protocol max, protocol mi n by 10.

Units

Displays the units represented by the point such as Amps, kVA and Volts. This field is read -onl y and cannot be changed.

Deadband

The c hange in value required to stimulate a points ‘cha nge of state’ s tatus. Right click the column heading to select protocol or engineering unit dead-bands. N.B. not all protocols use a dead-band.

Deadband (Eng Units)

Displays the deadband value for the point in engineering units with reference to the Point Min and Point Max values.

Conversion

Used in Modbus to convert 32 bits scaled value to 16 bits data. “NORMAL” means least-significant 16-bits from 32-bits signed conversion. “LS16” means least-significant 16-bits unsigned conversion. “MS16” means most-significant 16-bits unsigned conversion. Conversion is done after scaling.

Comment

Used to add descriptive comments about the point. The comment is saved to the mapping file when saved but is not written into the controller. The “ Multiplier” is modified.


4.3 Counters Counters are used to count data and events such as Outages and Accumulated kWH. This item is not part of the MITS protocol and is not available for MITS but these points are accessible in the MITS analog inputs.

Figure 10: Counter Tab

DNP ID

This field specifies the DNP ID number of the point. Range: 0 to 40. This field is read-only

Name

The name of the point as defined in the Confi guration Toolbox. This field can b e changed in two ways: •

•



Min

The minimum value the counte r can return. This field is read-on ly and cannot be changed.

Max

The maxi mum value th e counter can return. This field is read-on ly and cannot be changed.

Enabled

Gives the user the ability to deactivate a point in the protocol map without removing the configured point. If the point is disabled, data for this point is still included in the map when it is uploaded to the RTU. The point will be configured, however, the settings will have no effect on the RTU.

Units

Displays the units represented by the point such as seconds and kWH. This field is read-only an d cannot be chan ged.

Comment

Used to add descriptive comments about the point. The comment is saved to the mapping file when saved but is not written into the controller.

4.4 Binary Outputs Binary Outputs are used to perform operations on the switchgear device and change settings.

DNP ID

Specifies the DNP ID number of the point. Range: 0 to 95 for Binary Outputs This field is read -onl y

MITS ID

Specifies the MITS ID number of the point. Range: 0xc0 to 0xc5 with 16 points per MITS ID This field is read -onl y

Addre ss

Specifies the Modbus address of the point. Range: 0 to 95 for Binary Outputs This field is read -onl y

Name

The n ame of the point as defined in the Configuration Toolbox. This field can be chan ged in two ways: •

•

Figure 11: Binary Output Tab for DNP3, MITS & Modbus protocols


Enabled


Pulse

Sets whether the point will accept a Pulse command. Range: Yes, No. (DNP3 only)

Latch

Sets whether the point will accept a Latch command Range: Yes, No. (DNP3 only)

Trip/Close

Sets whether the point will accept a Trip/Close command. Range: Yes, No. (DNP3 only)

Invert

Specifies whether the point will be inverted. Range: Yes, No.

Comments

Used to add descriptive comments about the point. The comment is saved to the mapping file when saved but is not written into the controller.


4.5 Analog Outputs Analog Ou tputs are used to chang e anal og set tings such as Protection Groups. This item is not part of the MITS protocol and is not available for MITS.

DNP ID

This field specifies the DNP ID number of the point. Range: 0 to 255. This field is read-only

Addre ss

Specifies the Modbus address of the point. Range: 0 to 95 for Binary Outputs This field is read -onl y

Name

The name of the point as defined in the Configuration Toolbox. This field can be chan ged in two ways: •

•

Figure 12: Analog Output Tab for DNP3 & Modbus protocols



Min

The m inimum valid valu e that can be written to the analog output. This field is read -onl y.

Max

The m aximum valid va lue that can be written to the analog output. This field is read -onl y.

Units

Displays the units represented by the point such as Amps, kVA and Volts. This field is read -onl y and cannot be c hange d.

Enabled


Comment

Used to add descriptive comments about the point. The comment is saved to the mapping file when saved but is n ot written into the contro ller.

5. Using Protocol Mappings in WSOS The Protocol Configuration Tool is de signed for off-line u se. Al l on-l ine op erations such as reading existing protocol mappings or writing new mappings are performed using WSOS.

5.1 Adding DNP3, MITS and Modbus Protocol to controller configuration DNP3 and/or MITS and/or Modbus can be made unavailable in the controller. Only two protocols are selectable at the same time. The user should ensure that it is available by ticking the available option on the Feature Selection screen.

Figure 13: Add DNP3, MITS and Modbus Protocols


5.2 Reading Existing DNP3, MITS and Modbus Mappings from the Controller Existing DNP3, MITS and Modbus mappings in controllers can be read and saved into a file for editing purposes. Make sure WSOS is On-Line. Select “Options -> Read Switchgear Settings from the Switchgear” from the menu in WSOS. A message box will appear allowing the user to choose what information to read from the switchgear controller. Tick the “Protocol Mapping” (or “DNP3 Mapping” if the controller software version V41 or below) checkbox and enter a password when requested. Click the “OK” button to start the read operation. During a Switchgear Read the DNP3, MITS or Modbus mapping will be written into a file if the controller has valid mapping. The filename used will be the mapping name displayed on the “DNP3 Point Configuration” status page, on the “MITS Communications Configuration” page and on the “Modbus Communications Configuration” page. If a file of this name already exists in the WSOS DNPADVC directory it will only be overwritten if the mapping itself is different from the one in the file. Note: The comments within a mapping file are not writ ten into the contro ller. The refore overwriting an existing file by reading a mapping from a controller will have the effect of wiping the comments from the file.

Figure 14: Reading a protocol map from a controller

Afte r a read switchgear operation has b een performed the resulting mapp ing file can be opened and edited off-line using the Protocol Configuration Tool. Note: Ticking Protocol Mapping only reads the IO map. To read the controller MITS Settings, DNP3 settings or Modbus settings for transmission services, unsolicited, communications, and database configuration, then the Telecontrol tick box should also be selected.


5.3 Attaching Protocol Mappings to Switchgear Device Configurations Once a MITS/DNP3/Modbus mapping is ready, it must be attached to a WSOS switchgear device configuration in order to write the mapping into the switchgear. This can only be done with the switchgear offline and by selecting the Point Mapping drop-down list on the DNP3 Point Configuration screen for DNP3 mapping. (As shown below in Figure 15 or MITS Communications Configuration screen for MITS’s as shown in Figure 16, or Modbus Communications Configuration screen for Modbus’s as shown in Figure 17). Then save the S witchgear Device Configurations information by selecting “File -> Save or Save All” from WSOS main menu.

Figure 15: Selecting a DNP3 map

The “ DNP3 Standard ACR” m ap is the default IO m ap. It reflects po ints that are available with default settings in the controller. If a feature is made available via configuration then the user is required to manually add any related points to the IO list as required.

Figure 16: Selecting a MITS map

A “DN P3 Legacy 27-17 ACR” map is also available with the tool. It contains an IO map th at emulates PTCC V27-17 or newer DNP3 IO points list.

Figure 17: Selecting a Modbus map


5.4 Writing New DNP3/MITS/Modbus Mappings into the Controller New DNP3/MITS/Modbus mappings are attached to the switchgear device configuration as described in section 5.3 and then written to the controller using the normal switchgear write procedure. Make sure WSOS is On-Line. Select “Options -> Write Switchgear Settings to Switchgear” from the WSOS menu. A message box will appear allowing the user to choose what information is written to the controller. Tick the “Protocol Mapping” checkbox and enter a password when requested. Click the “Next” button to start the write operation.

Figure 18: Writing a map to a controller

If the DNP3/MITS/Modbus mapping is incompatible with the version of software currently loaded into the controller, or if it is in so me way invalid, a warning messag e will appear. If the operator chooses to continue with the write procedure, a message will appear to advise the user that the DNP3/Protocol data will not be included in the write operation. Note: Ticking Protocol mapping only writes the IO map. To write to the controller (MITS/ DNP3/Modbus) settings for transmission services, unsolicited, communications, and database configuration, then the Telecontrol tick box should also be selected.

5.5 Removing Protocol Mappings from the Controller Map assigned to a Protocol can be removed from the Controller if it is no longer needed. That can be done with the controller offline with WSOS and by selecting from the Point Mapping drop down list on the DNP3 Point Configuration screen for DNP3 mapping (as shown in Figure 15 or MITS Communications Configuration screen for MITS’s as shown in Figure 16 or Modbus Communications Configuration screen for Modbus’s as shown in Figure 17). Then save the Switchgear Device Configurations information by selecting “File -> Save or Save All” from WSOS main menu. Lastly, perform a Switchgear Write as described in section 0 by selecting “Options -> Write Switchgear Settings To Switchgear” while the controller is On-Line with WSOS.


6. Technical Appendix 6.1 File Locations Protocol mapping filenames are also the map identification shown on the controller panel. Filenames must therefore not be longer than 40 characters to conform to the filename length restrictions within the controller. Note: .D3M/.PTM/.MBM files cannot be edited outside of the Tool. The tool retains a checksum of the filename and contents. If it detects a difference then it rejects the map as corrupt.

6.2 DNP3 Term Glossary 6.2.1 DNP3 Classes There are fo ur classes in DNP3. These are defined as fol lows: 0

Class 0 is not an event class. It is used when reporting current (static) data values and not change of state events. Note: Setting a point to Class 0 will prevent the controlle r’s protocol handler from reporting change of state events for that point to the master station. The point still remains accessible through static data polls.

1 2 3

Class 1 is used to report high priority events. Events in this class take precedence. Class 2 is used to report medium priority events. Class 3 is used to report low priority events.

6.3 DNP3 Specifications The D NP3 implementation used by the manufacturer is described in t he following documents. Basic Four Documentation Set •

“DNP3 Application Layer”, DNP3 User Group, dnpal.doc Rev 0.03

•

“DNP3 Transport Functions”, DNP3 User Grou p, dnptf.doc Rev 0.01

•

“DNP3 Data Lin k Layer”, DNP3 User Group, dnpdl.doc Rev 0.02

•

“DNP3 Data Object Library”, DNP3 User Group, dnpol.doc Rev 0.02

•

Subset Definitions Document

•

“DNP3 Subset Definitions”, DNP3 User Group, subset.wp6 rev 2.00


Index

A

I

Add D NP3 Mapping Ca pability 15 Anal og Input Class 10 11 Anal og Input Deadb and Anal og Input Return Max 7 Anal og Input Return Min 11 7 Anal og Input Scale Factor Anal og Input Units 11 Anal og Inputs 7, 8, 11 14 Anal og Output Max Anal og Output Min 14 Anal og Output Units 14 7, 8, 14 Anal og Outputs Attaching DNP3 Mapp ings to Switchgear Device Configurations 7

Input Example Introduction Invert Binary Input Invert Binary Output

B Binary Input Class Binary Inputs Binary Output Latch Binary Output Pulse Binary Output Trip/Close Binary Outputs

9 7, 8, 9 13 13 13 7, 8, 13 14

C Classes Comment Comments Configuration Tool Box Counter Max Counter Min Counter Units Counters Creating New Files

6 6, 7

Main Interface Menu Items

N 5, 6

New File

O Open Opening Existing DNP3 Mappings Overview of DNP3 Configuration

6 5 4

P Point Name Print

9, 10, 12, 13, 14 7

R Reading DNP3 Mappings from the Controller

16

Save Save As

6, 17, 18 6

T Toolbar

7

U Upgrading Software Versions Using DNP3 Mappings in WSOS

8 15

W

Deleting Existing DNP3 Mappings ? DNP ID 9, 10, 12, 13, 14 DNP3 Term Glossary 19

F


M

S 9, 19 9, 11, 12, 13 14 9, 11, 12, 13 14 8, 9, 10, 12, 13, 14 12 12 18 8, 12 3, 5

D

File Locations

? 4 9 13

19

Writing New DNP3 Mappings into the Controller

18

Notes


Notes


Notes


Make the most of your energy

Schneider Electric (Australia) Pty Ltd

Head Office 78 Waterloo Road Macquarie Park NSW 2113

Australia Wide Tel: 1300 369 233 Fax: 1300 369 288 www.schneider-el ectric.c om.au [email protected]

© 2012 Schneider Electric. All Rights Reserved.

SM

As standards, specifications and designs change from time to time, always ask for confirmation of the information given in this publication. This document has been printed using FSC Mix Certified paper. ISO 14001 environmental management system in use at mill. Information given in this publication was accurate at the time of printing.

3 0 2 4 2 M O C P I L C

WSOS01-DOC-102 ADVC Protocol Configuration Tool R10 WEB

Recommend Documents