WSOS01-DOC-102 ADVC Protocol Configuration Tool R10 WEB

8/12/2019 WSOS01-DOC-102 ADVC Protocol Configuration Tool R10 WEB

1/24

Protocol Configuration ToolTechnical Manual for theADVC Controller Range


2/242 | Schneider Electric

Scope of this document

This document describes the features andoperation of the Protocol Conguration Toolfor WSOS.

Limitations This document is copyright and is providedsolely for the use of the recipient. It is not tobe copied in any way, nor its contents divulgedto any third party, nor to be used as the basisof a tender or specication without the expresswritten permission of Schneider Electric(Australia) Pty Limited.

This document discloses condential inte llectualproperty that belongs to Schneider Electric

(Australia) Pty Limited. This document doesnot invest any rights to Schneider Electric(Australia) Pty Limited intellectual property inthe recipient. Moreover, the recipient is requirednot to disclose any of the intellectual propertycontained in this document to any other partyunless authorised in writing by SchneiderElectric (Australia) Pty Limited.

Disclaimer The advisory procedures and informationcontained within this document have been

compiled as a guide to the safe andeffective operation of products supplied bySchneider Electric.

It has been prepared in conjunction withreferences from sub-assembly suppliers and thecollective experience of the manufacturer.

In-service conditions for use of the productsmay vary between customers and end-users.Consequently, this document is offered as aguide only. It should be used in conjunctionwith the customers own safety procedures,maintenance program, engineering judgmentand training qualications.

No responsibility, either direct or consequential,for injury or equipment failure can be acceptedby the manufacturer resulting from the use ofthis document.

Copyright2012 bySchneider Electric (Australia) Pty Limited

All Rights Reserved.

No part of the contents of this document maybe reproduced or transmitted in any form orby any means without the written permissionof the manufacturer.

Document part numberWSOS01-DOC-102

RevisionR10

Revision history:

R00 Created f romN00-718R01

18/06/2004

R01 Updated for launchfeatures, screenshots, etc.

17/10/2004

R02 Updated screenshots again

23/11/2004

R03 Minor corrections as perdocument review

25/11/2004

R04 New version of ProtocolConguration Tool

22/6/2005

R05 Updated WSOS 5sections to reectnew changes

07/07/2005

R06 Protocol Conguration Tool merged intoWSOS with AnalogInput changes

17/10/2005

R07 Minor changes toupdate document

30/03/2006

R08 Clarify Analogue Inputs

Dead-bands column.

30/03/2006

R09 Updated companyname, address andphone numbers.

08/07/2009

R10 Modbus 13/01/2010


3/24Technical Manual for the WSOS Protocol Conguration Tool (WSOS01-DOC-102) | 3

Contents

1. Introduction 41.1 Scope 4

2. Overview of Protocol Configuration 4

3. Operation of ProtocolConfiguration Tool 5

3.1 Creating New Files 5

3.2 Opening Existing Protocol Mappings 5

3.3 Deleting Existing Protocol Mappings 5

3.4 Main Interface 5

3.4.1 Menu Items 6

3.4.2 Toolbar 7

3.4.3 Input/Output and Counter Tabs 8

3.4.4 Conguration Tool Box 8

3.5 Upgrading Software Versions 8

4. Creating a Protocol Mapping 94.1 Binary Inputs 9

4.2 Analog Inputs 10

4.3 Counters 12

4.4 Binary Outputs 13

4.5 Analog Outputs 14

5. Using Protocol Mappings in WSOS 15

5.1 Adding DNP3, MITS and ModbusProtocol to controller conguration 15

5.2 Reading Existing DNP3, MITSand Modbus Mappings fromthe Controller 16

5.3 Attaching Protocol Mappingsto Switchgear Device Congurations 17

5.4 Writing New DNP3/MITS/ModbusMappings into the Controller 18

5.5 Removing Protocol Mappings fromthe Controller 18

6. Technical Appendix 19

6.1 File Locations 19

6.2 DNP3 Term Glossary 19

6.2.1 DNP3 Classes 19

6.3 DNP3 Specications 19

7. Index 20

List of figures

Figure 1: Overview of protocolconguration tool 4

Figure 2: Creating a new le in theFile Options dialog box 5

Figure 3: Selecting existing les 5

Figure 4: Delete Protocol CongurationFiles Dialog Box 5

Figure 5: Main Screen showing astandard ACR mapping 6

Figure 6: Toolbar 7

Figure 7: Conguration Toolbox 8

Figure 8: Binary Input Tab(For DNP3, MITS & Modbusprotocols respectively) 9

Figure 9: Analog Input Tab forDNP3, MITS and Modbusprotocols 10

Figure 10: Counter Tab 12

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

Figure 12: Analog Output Tab for DNP3& Modbus protocols 14

Figure 13: Add DNP3, MITS andModbus Protocols 15

Figure 14: Reading a protocol mapfrom 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



Figure 1: Overview of protocol conguration tool

1. Introduction The Protocol Conguration Tool allows WSOS users to generate custom DNP3, MITS and ModbusI/O mappings and load them into a switchgear device controller.

1.1 Scope The Protocol Conguration Tool can only create mappings that are compatible with ADVC software

versions A41-03.xx or higher for DNP3 protocol maps, version A42-00.00 or higher for MITSprotocol maps, version A44-14.00 or higher for Modbus protocol maps.

The Tool is available with WSOS version 5.1.0 or later and wil l work on Microsof t Windows 2000and XP. The MITS protocol is suppor ted in WSOS version 5.1.20 onwards. The Modbus protocol issupported in WSOS version 5.6.23 onwards.

Note: A full descript ion of the manufacturers DNP3 implementation is avai lable in the DNP3Protocol Technical Manual for Advanced Controllers, Part Number ADC01-DOC-146. Thecorresponding description of the MITS protocol is available in ADVC MITS Technical Manual, PartNumber ADC01-DOC-210. The corresponding description of the Modbus protocol is available inMODBUS 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 thistool. A copy of this manual can be viewed by selecting Help -> Tech Manual from the Tool menu.

WARNING

Make sure the Tool is closed after amapping has been edited.If the Tool is left open while the Automatic

Data Retrieval feature is running it mayattempt to update a mapping le that isalready open in the Tool. This will eithercause the read operation to fail or resultin a situation where the newly read lediffers from the le open within the Tool.

2. Overview of ProtocolConfigurationCustom protocol maps can be created andloaded into a controller directly from WSOS.

The mappings and I /O logic are created usingthe tool and saved to a mapping le on theWSOS computer. Once a valid le has beencreated, it is linked to switchgear deviceconguration in WSOS and written into thecontroller. A le is treated as a library le. Inother words, one protocol map can be linkedto multiple switchgear congurations. Refer tosection 5 for a description of this process.

The t ypes of act ions that can be mapped aredependent on the software version loaded in theSwitchgear Devices controller. When the tool isstarted the user is asked to input the softwareversion. This is then used to retrieve a valid setof points to use when constructing mappingswithin the tool.

The protocol conguration tool is intended tobe used Off-Line only. Mappings are created,

saved and linked to a WSOS switchgeardevice conguration while disconnected fromthe switchgear. Once these tasks have beencompleted the user connects to the device andwrites the new mapping into the controller alongwith the switchgear device conguration.



3. Operation of ProtocolConfiguration Tool

To start the protocol conguration tool select Customise -> CongurableDNP3 -> Congure Protocol Mapping from the WSOS menu. Thislaunches the tool and displays the File Options dialog. The dialog isused to create new blank mapping les or select existing mapping les forediting by selecting the appropriate radio button.

3.1 Creating New FilesWhen creating a new le it is necessary to input the software versionrunning within the controller. The software version can be obtainedfrom the Switchgear Wear/General Details screen on the controlleritself. The software determines which points are available in theConguration Toolbox.

If the software version running in the controller is later than that allowed bythe tool, the latest allowed version should be entered. After entering thesedetails click the OK button to open the blank le.

3.2 Opening Existing Protocol Mappings To select an existing protocol mapping le, select the Existing radiobutton to display a list of les. Select a le and click Open to view thele in the tool. Note that les created with a version number of 42 orgreater are labelled with a .PTM le extension, whereas map versions

created with a major vers ion number of 41 have a .D3M le extension. This change has been made to facil itate the addition of the MITS protocol.Refer to Figure 3.

3.3 Deleting Existing Protocol Mappings

This deletion will remove existing protocol mappings f rom local harddisk. This can be done from within WSOS by going to Customise ->Congurable Protocol Tool -> Delete ADVC Protocol Mappings on themenu to display the dialog box shown in Figure 4. Select a mapping fromthe drop-down box and click the Delete button. The delete feature willnot allow a mapping to be deleted if it is being referenced by a switchgeardevice conguration in WSOS.

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

Figure 3: Selecting existing les.

Figure 4: Delete Protocol Conguration Files Dialog Box



3.4.1 Menu ItemsThe Protocol Conguration Tool menu in WSOS has the following options:

Protocol File

New Closes the current le and allows the creation of a new le using theFile Options dialog described in section 3.1.

Open Closes the current le and allows the selection of an existingmapping using the File Options dialog as described in section 3.2.

Save Saves the current le to the hard drive. If the le is new and this isthe rst time it has been saved, the Save As dialog will be openedallowing the user to type in a name before saving.

Save As Opens the Save As dialog box. This allows an existing le to besaved under a new name.

The new lename is limited to 40 characters. This limitat ion is to make it compatible with thenaming convention used within the switchgear controller.

Note: The Tool expects les to be located in a particular directory on the hard drive. If the le issaved in an alternative location it will not be listed in the File Options dialog box when openingexisting les. Refer to section 6.1 for further details.

3.4 Main InterfaceOnce a new le has been created or an existing le has been selected the toolsmain screen is displayed as shown in Figure 5.

Figure 5: Main Screen showing a standard ACR mapping.



Protocol Point

Insert Point Inserts a new row at the current cursor positionon the grid so that a new point can be added tothe protocol map.

Delete Point Deletes a row at the current cursor position onthe grid shifting rows in the table below the

deleted point upwards. (New row added to theend of the grid).

DNP Binary Inputs Lists the Binary Inputs used in the mapping.

Analog Inputs Lists the Analog Inputs used in the mapping.Counters Lists the Counters used in the mapping.Binary Outputs Lists the Binary Outputs used in the mapping.

Analog Outputs Lists the Analog Outputs used in the mapping.

MITS Binary Inputs Lists the Binary Inputs used in the mapping.

Analog Inputs Lists the Analog Inputs used in the mapping.Binary Outputs Lists the Binary Outputs used in the mapping.

MODBUS Binary Inputs Lists the Binary Inputs used in the mapping.

Analog Inputs Lists the Analog Inputs used in the mapping.Binary Outputs Lists the Binary Outputs used in the mapping.


Print Prints a report listing the mappings used inthe current le.

Protocol Conguration Tool Help

DNP3 Technical Manual DNP Protocol Technical Manual For AutomaticCircuit Reclosers with Advanced Controllers

MITS Technical Manual MITS Telemetry Protocol Technical ManualFor Automatic Circuit Reclosers with

Advanced Controllers

MODBUS Technical Manual MODBUS Protocol Technical Manual for ADVCController Range

Points List HTML le containing list and description ofcongurable points

Manual Technical Manual for WSOS ProtocolConguration Tool

Protocol View

Conguration Toolbox See section 3.4.4 for detailed description

Toolbar Hides and disp lays the toolbar

3.4.2 ToolbarBelow the menu is a tool bar with two buttons with icons and three or ve buttons depending onwhich protocol map you are conguring. The buttons with the icons are used to launch the input/ output Conguration Toolbox and Upgrade Software Version dialog.

Figure 6: Toolbar

3.4.1 Menu Items (cont.)



WARNING

If a mapping is upgraded to a newer software version it willthen be incompatible with other switchgear devices runningolder software.

Make sure the software version you are upgrading to is compatiblewith all other switchgear devices you wish to use the mapping inbefore upgrading. If the mapping software version is incompatibleyou will not be ab le to write it into the switchgear.

There are ve tabbed pages in the tool for DNP3:

Binary Inputs Lists the Binary Inputs used in the mapping. Analog Inputs Lists the Analog Inputs used in the mapping.Counters Lists the Counters used in the mapping.Binary Outputs Lists the Binary Outputs used in the mapping.


There are three tabbed pages in the tool for MITS :

Binary Inputs Lists the Binary Inputs used in the mapping. Analog Inputs Lists the Analog Inputs used in the mapping.Binary Outputs Lists the Binary Outputs used in the mapping.

There are four tabbed pages in the tool for MODBUS:

Binary Inputs Lists the Binary Inputs used in the mapping. Analog Inputs Lists the Analog Inputs used in the mapping.Binary Outputs Lists the Binary Outputs used in the mapping.


3.4.3 Input/Output and Counter Tabs

Figure 7: Conguration Toolbox

3.4.4 Configuration Tool Box The conguration tool box panel is launched by click ingthe Toolbox button or by using the [Ctrl-T] keyboard shortcut.

For a selected device and given software version the tree contains everyavailable point.

The tree displays dif ferent points depending on which tab is selected.For example, if the Counters tab is selected then only accumulators andprotocol specic data will be displayed on the tree.

When a point is selected on the tree the Point Information windowbelow displays relevant details such as a short description of the point,resolutions and units.

The tree can be searched entering words into the Search for textbox. The toolbox uses these lette rs to l imit what appears on the t ree. Forexample, typing the word phase into the box lters the tree to show allpoints with the word phase as part of its title.

Note: A full points list is available in HTML format by selectingHelp -> Points List from the Tools menu.

3.5 Upgrading Software Versions This feature allows the user to take advantage of additional features that maybe available when the controller software version has been upgraded to alater version. Clicking this button will have the effect of making extra pointsavailable in the conguration toolbox for creating mappings.

The Upgrade Sof tware Version but ton will only be activated if the Tooldetects that the software version actually loaded in the controller from whichthe mapping has been read, is greater than the software version storedwithin the mapping. In all other cases it will be de-activated.



4. Creating a Protocol Mapping The Protocol Conguration Tool allows the user to build 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 theConguration Toolbox. If a row is not selected, the point will either be entered at the top of the table or into the last selectedrow. 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 shif t all the rows below up one, or leave the ent ire row blank. A blank row represents a reserved orunused DNP id, MITS id or Modbus point. Its value is defaulted to zero.

The points listed in the Conguration Toolbox are determined by the software version number entered when the le wasrst created.

4.1 Binary InputsBinary inputs are used to report the status of binary points.

DNP ID Species the DNP ID number of the point.Range: 0 to 255 for Binary Inputs

This eld is read-only

MITS ID Species the MITS ID number of the point.Range: 0x10 to 0x1f with 16 points per MITS ID


Address Species the Modbus address of the point.Range: 0 to 255 for Binary Inputs


Name The name of the point as dened in theConguration Toolbox.

This eld can be changed in two ways: By dragging a point from the conguration

tool box into the cell.

Selecting the cell then double clicking a pointin the conguration toolbox.

Enabled Gives the user the ability to deactivate a pointin the protocol map without removing thecongured point. If the point is disabled, datafor this point is still included in the map whenit is uploaded to the RTU. The point will becongured, however, the settings will have noeffect on the RTU. This eld is unavailable inthe Modbus protocol.

Class The DNP3 class of the point. The defaultclass can be modied by selecting fromthe drop-down list. This eld is unavailable in

the MITS and Modbus protocols.Range: 0, 1, 2, 3.See section 6.2.1 for a description of Classesin DNP3.still present.

Invert Species whether the point will be inverted.If the point is inverted it will be transmittedwhen the condition is false rather than true.Range: Yes, No.

Comments Used to add descriptive comments aboutthe point. The comment is saved to themapping le when saved but is not writteninto the controlle r.

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



4.2 Analog Inputs Analog Points are used to transmit analog data such as line currents,voltages and contact life. Analog inputs are created by adding points asrequired, then modifying the parameters from the defaults if necessary.

DNP ID Species the DNP ID number of the point.Range: 0 to 127


MITS ID Species the MITS ID number of the point.Range: 0x20 to 0x2f with 8 points per MITS ID


Address Species the Modbus address of the point.Range: 0 to 127 for Analog Inputs




tool box into the cell. Selecting the cell then double clicking a point

in the conguration toolbox.

Point Min Represents the minimum value in engineeringunits that can be measured by the device. Theprecision of data for all items in the row inengineering units is given by the number ofdecimal places after the number - in mostinstances with some exceptions this value will

be to the nearest integer.

Enabled Gives the user the ability to deactivate a pointin the protocol map without removing thecongured point. If the point is disabled, datafor this point is still included in the map when itis uploaded to the RTU. The point will becongured, however, the settings will have noeffect on the RTU. This eld is unavailable inthe Modbus protocol.

Class The DNP3 class of the point. The default classcan be modied by selecting from thedrop-down list. This eld is unavailable for theMITS protocol.Range: 0, 1, 2, 3.See section 6.2.1 for a description ofClasses in DNP3.

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



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 Conguration Toolbox.

For Modbus, the default value displayed is determined by the Point Minand Multiplier. This eld is read-only. Its value will change if theMultiplier is modied.

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 Conguration Toolbox.For Modbus, the default value displayed is determined by the Point Maxand Multiplier.

This eld is read-only. Its value will change if the Multiplier is modied.

Multiplier For DNP3 and MITS, the multiplier is used to multiply/div ide the reportedanalog value by the amount entered. For example, a multipler of ten willdivide the protocol max, protocol min and deadband (protocol units)relative to a multiplier of 1. For example, a multip lier of 10 given an initialmultiplier of 1 will divide the values by 10. A multiplier of 10 given andinitial multiplier of 100 will multiply the values by 10.

For Modbus, the multiplier is used to divide the reported analog value bythe amount entered. For example, a multipler of ten will divide the protocolmax, protocol min by 10.

Units Displays the units represented by the point such as Amps, kVA and Volts. This eld is read-only and cannot be changed.

Deadband The change in value required to stimulate a points change of state s tatus.Right click the column heading to select protocol or engineering unitdead-bands. N.B. not all protocols use a dead-band.

Deadband (Eng Units) Displays the deadband value for the point in engineering units withreference 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-signicant 16-bits from 32-bits signed conversion.LS16 means least-signicant 16-bits unsigned conversion.MS16 means most-signicant 16-bits unsigned conversion.Conversion is done after scaling.

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

The Multiplier is modied.



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

Figure 10: Counter Tab

DNP ID This eld species the DNP ID number of the point.Range: 0 to 40.


Name The name of the point as dened in the Conguration Toolbox.

This eld can be changed in two ways:

By dragging a point from the conguration tool box into the cell.

Selecting the cell then double clicking a point in theconguration toolbox.

Min The minimum value the counter can return. This eld is read-only and cannot be changed.

Max The maximum value the counter can return. This eld is read-only and cannot be changed.

Enabled Gives the user the ability to deactivate a point in the protocol map withoutremoving the congured point. If the point is disabled, data for this pointis still included in the map when it is uploaded to the RTU. The point willbe congured, however, the settings will have no effect on the RTU.

Units Displays the units represented by the point such as seconds and kWH. This eld is read-only and cannot be changed.

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



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

4.4 Binary OutputsBinary Outputs are used to perform operations on the switchgear deviceand change settings.

DNP ID Species the DNP ID number of the point.Range: 0 to 95 for Binary Outputs


MITS ID Species the MITS ID number of the point.Range: 0xc0 to 0xc5 with 16 points perMITS ID


Address Species the Modbus address of the point.Range: 0 to 95 for Binary Outputs




tool box into the cell.


Enabled Gives the user the ability to deactivate a pointin the protocol map without removing thecongured point. If the point is disabled, datafor this point is still included in the map when itis uploaded to the RTU. The point will becongured, however, the settings will have noeffect on the RTU. This eld is unavailable in

the Modbus protocol.

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

Latch Sets whether the point will accept aLatch commandRange: Yes, No. (DNP3 only)

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

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

Comments Used to add descriptive comments aboutthe point. The comment is saved to themapping le when saved but is not writteninto the controller.



Figure 12: Analog Output Tab for DNP3 &

Modbus protocols

4.5 Analog Outputs Analog Outputs are used to change analog set tings such as ProtectionGroups. This item is not part of the MITS protocol and is not availablefor MITS.

DNP ID This eld species the DNP ID number ofthe point.

Range: 0 to 255. This eld is read-only

Address Species the Modbus address of the point.Range: 0 to 95 for Binary Outputs



This eld can be changed in two ways:

By dragging a point from the congurationtool box into the cell.


Min The minimum valid value that can be written tothe analog output.

This eld is read-only.

Max The maximum valid va lue that can be writ ten tothe analog output.

This eld is read-only.

Units Displays the units represented by the point suchas Amps, kVA and Volts.

This eld is read-only and cannot be changed.

Enabled Gives the user the ability to deactivate a pointin the protocol map without removing thecongured point. If the point is disabled, data forthis point is still included in the map when it isuploaded to the RTU. The point will becongured, however, the settings will have noeffect on the RTU. This eld is unavailable in theModbus protocol.

Comment Used to add descriptive comments about thepoint. The comment is saved to the mapping lewhen saved but is not written into the contro ller.



5. Using Protocol Mappings in WSOS The Protocol Conguration Tool is designed for off- line use. Al l on-l ine operations such as readingexisting protocol mappings or writing new mappings are performed using WSOS.

5.1 Adding DNP3, MITS and Modbus Protocol to

controller configurationDNP3 and/or MITS and/or Modbus can be made unavailable in the controller. Only two protocols areselectable at the same time. The user should ensure that it is available by ticking the available optionon the Feature Selection screen.

Figure 13: Add DNP3, MITS and Modbus Protocols



5.2 Reading Existing DNP3, MITS and Modbus Mappingsfrom the ControllerExisting DNP3, MITS and Modbus mappings in controllers can be read and saved into a le forediting purposes.

Make sure WSOS is On-Line. Select Options -> Read Switchgear Settings from the Switchgearfrom the menu in WSOS. A message box will appear allowing the user to choose what informationto 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. Clickthe OK button to start the read operation.

During a Switchgear Read the DNP3, MITS or Modbus mapping will be written into a le if thecontroller has valid mapping. The lename used will be the mapping name displayed on the DNP3Point Conguration status page, on the MITS Communications Conguration page and on theModbus Communications Conguration page. If a le of this name already exists in the WSOSDNPADVC directory it will only be overwritten if the mapping itself is different from the one in the le.

Note: The comments within a mapping le are not writ ten into the contro ller. Therefore overwritingan existing le by reading a mapping from a controller will have the effect of wiping the commentsfrom the le.

After a read switchgear operation has been performed the resulting mapping le can be openedand edited off-line using the Protocol Conguration Tool.

Note: Ticking Protocol Mapping only reads the IO map. To read the controller MITS Settings, DNP3settings or Modbus settings for transmission services, unsolicited, communications, and databaseconguration, then the Telecontrol tick box should also be selected.

Figure 14: Reading a protocol map from a controller



5.3 Attaching Protocol Mappings to SwitchgearDevice Configurations

Once a MITS/DNP3/Modbus mapping is ready, it must be attached toa WSOS switchgear device conguration in order to write the mappinginto the switchgear. This can only be done with the switchgear ofineand by selecting the Point Mapping drop-down list on the DNP3 PointConguration screen for DNP3 mapping. (As shown below in Figure 15or MITS Communications Conguration screen for MITSs as shownin Figure 16, or Modbus Communications Conguration screen forModbuss as shown in Figure 17). Then save the Switchgear DeviceCongurations information by selecting File -> Save or Save All fromWSOS main menu.

The DNP3 Standard ACR map is the default IO map. It reects pointsthat are available with default settings in the controller. If a feature is madeavailable via conguration then the user is required to manually add anyrelated points to the IO list as required.

A DNP3 Legacy 27-17 ACR map is also available with the tool. I tcontains an IO map that emulates PTCC V27-17 or newer DNP3 IOpoints list.

Figure 15: Selecting a DNP3 map

Figure 16: Selecting a MITS map

Figure 17: Selecting a Modbus map



5.4 Writing New DNP3/MITS/Modbus Mappings into the ControllerNew DNP3/MITS/Modbus mappings are attached to the switchgear device congurationas described in section 5.3 and then written to the controller using the normal switchgearwrite procedure.

Make sure WSOS is On-Line. Select Options -> Write Switchgear Settings to Switchgear from theWSOS menu. A message box will appear allowing the user to choose what information is written tothe controller. Tick the Protocol Mapping checkbox and enter a password when requested. Clickthe Next button to start the write operation.

If the DNP3/MITS/Modbus mapping is incompatible with the version of software currently loadedinto the controller, or if it is in some way invalid, a warning message will appear. If the operatorchooses to continue with the write procedure, a message will appear to advise the user that theDNP3/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 databaseconguration, then the Telecontrol tick box should also be selected.

5.5 Removing Protocol Mappings from the ControllerMap assigned to a Protocol can be removed from the Controller if it is no longer needed. That canbe done with the controller ofine with WSOS and by selecting from the Point Mappingdrop down list on the DNP3 Point Conguration screen for DNP3 mapping (as shown in Figure15 or MITS Communications Conguration screen for MITSs as shown in Figure 16 or ModbusCommunications Conguration screen for Modbuss as shown in Figure 17). Then save theSwitchgear Device Congurations information by selecting File -> Save or Save All from WSOSmain 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.

Figure 18: Writing a map to a controller



6. Technical Appendix

6.1 File LocationsProtocol mapping lenames are also the map identication shown on the controller panel.Filenames must therefore not be longer than 40 characters to conform to the lename lengthrestrictions within the controller.

Note: .D3M/.PTM/.MBM les cannot be edited outside of the Tool. The tool retains a checksum ofthe lename 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 four classes in DNP3. These are dened 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 rs protocol

handler from reporting change of state events for that point to the masterstation. The point still remains accessible through static data polls.

1 Class 1 is used to report high priority events. Events in this classtake precedence.

2 Class 2 is used to report medium priority events.3 Class 3 is used to report low priority events.

6.3 DNP3 Specifications The DNP3 implementation used by the manufacturer is described in the following documents.

Basic Four Documentation Set DNP3 Application Layer, DNP3 User Group, dnpal.doc Rev 0.03 DNP3 Transport Functions, DNP3 User Group, dnptf.doc Rev 0.01 DNP3 Data Link Layer, DNP3 User Group, dnpdl.doc Rev 0.02 DNP3 Data Object Library, DNP3 User Group, dnpol.doc Rev 0.02 Subset Denitions Document DNP3 Subset Denitions, DNP3 User Group, subset.wp6 rev 2.00



Index

A Add DNP3 Mapping Capability 15 Analog Input Class 10 Analog Input Deadband 11 Analog Input Return Max 7 Analog Input Return Min 11 Analog Input Scale Factor 7 Analog Input Units 11 Analog Inputs 7, 8, 11 Analog Output Max 14 Analog Output Min 14 Analog Output Units 14 Analog Outputs 7, 8, 14 Attaching DNP3 Mappings to SwitchgearDevice Congurations 7

BBinary Input Class 9 Binary Inputs 7, 8, 9 Binary Output Latch 13 Binary Output Pulse 13 Binary Output Trip/Close 13 Binary Outputs 7, 8, 13 14

CClasses 9, 19 Comment 9, 11, 12, 13 14 Comments 9, 11, 12, 13 14 Conguration Tool Box 8, 9, 10, 12, 13, 14 Counter Max 12 Counter Min 12 Counter Units 18 Counters 8, 12 Creating New Files 3, 5

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

FFile Locations 19

IInput Example ? Introduction 4 Invert Binary Input 9 Invert Binary Output 13

MMain Interface 6 Menu Items 6, 7

NNew File 5, 6

OOpen 6 Opening Existing DNP3 Mappings 5 Overview of DNP3 Conguration 4

PPoint Name 9, 10, 12, 13, 14Print 7

RReading DNP3 Mappings from theController 16

SSave 6, 17, 18 Save As 6

T

Toolbar 7UUpgrading Software Versions 8 Using DNP3 Mappings in WSOS 15

WWriting New DNP3 Mappings intothe Controller 18



Notes


24/24

Schneider Electric (Australia) Pty LtdHead Ofce Australia Wide78 Waterloo Road Tel: 1300 369 233Macquarie Park Fax: 1300 369 288NSW 2113 www.schneider-electric.com.au

h l @ h id l i

As standards, specications and designs change from time to time, always ask for conrmationof the information given in this publication.

This document has been printed using FSC Mix Certied paper. ISO 14001 environmentalmanagement system in use at mill.

M 2

4 2 0 3

Make the most of your energy SM

WSOS01-DOC-102 ADVC Protocol Configuration Tool R10 WEB

Documents

Transcript of WSOS01-DOC-102 ADVC Protocol Configuration Tool R10 WEB