SYS Feature Pack 3

Transcription

1 Issued: Version: A SYS Feature Pack Copyright 2013, ABB Oy, Substation Automation Products 1

2 The information in this document is subject to change without notice and should not be construed as a commitment by ABB Oy, Substation Automation Products. ABB Oy, Substation Automation Products assumes no responsibility for any error that may appear in this document. 2

3 Contents INTRODUCTION... 5 RECOMMENDATIONS... 6 PCM600 version... 6 SUPPORTED OPERATING SYSTEMS... 7 NEW FEATURES... 8 Modbus Slave... 8 DNP 3.0 Slave... 8 IEC MicroSCADA IET Interface / Safe Import Feature... 9 Measurement Reports configuration Copy&Paste Report Page Find&Replace text in Report Page IMPROVEMENTS AND ERROR CORRECTIONS Base system...11 Process Communication Network topology OPC Alarms & Events Server Process Displays Measurement Reports and Trends Display Measurement Display Cyber Security...12 Tools...12 Group Alarm editor Display Builder Communication...13 IEC Master IEC Slave IEC Master IEC Slave IEC Master DNP 3.0 Master DNP 3.0 Slave Modbus Master Modbus Slave ANSI X3.28 Half Duplex COM 500i Application...18 Signal Routing External OPC Data Access Client...18 External OPC DA Client

4 DOCUMENTATION Appendix MicroSCADA Pro SYS FP2 Hotfix Appendix MicroSCADA Pro SYS FP2 Hotfix Appendix MicroSCADA Pro SYS FP2 Hotfix Appendix MicroSCADA Pro SYS FP2 Hotfix INSTALLATION Installing

5 INTRODUCTION MicroSCADA Pro is a product family designed mainly for substation automation, electrical SCADA and distribution management applications. The products of the MicroSCADA Pro family are: MicroSCADA Pro Control System SYS 600 MicroSCADA Pro Compact System SYS 600C MicroSCADA Pro Distribution Management System DMS 600 This new version MicroSCADA Pro SYS Feature Pack 3 is an add-on to SYS The Feature Pack release concept means incremental add-on releases and upgrades of MicroSCADA Pro software between the main releases. This document describes the new features of 9.3 FP3, and modifications and corrections made. Note: consist of previously released SYS FP2 Hotfix 1 to Hotfix 4 and all the modifications and corrections done in these hotfixes are updated in Appendix 1 to 4. 5

6 RECOMMENDATIONS PCM600 version It is recommended to use PCM600 version 2.5 or newer if PCM600 and SYS 600 are installed in the same computer. 6

7 SUPPORTED OPERATING SYSTEMS SYS can be used on the following operating systems: Windows XP Professional Windows XP Professional + SP1 Windows XP Professional + SP2 Windows XP Professional + SP3 Windows Server 2003 Windows Server SP1 Windows Server SP2 Windows Server 2003 R2 Windows Server 2008 Standard, 32 Bit Windows Server 2008 Standard without Hyper-V, 32 Bit Windows Server 2008 Enterprise, 32 Bit Windows Server 2008 Enterprise without Hyper-V, 32 Bit Windows Server SP2 Windows 7 Professional, 32 Bit Windows 7 Ultimate, 32 Bit With SYS Feature Pack 2 support for the following operating systems has been added: Windows Server 2008 R2 Standard + SP1 Windows 7 Professional, 64 Bit Windows 7 Ultimate, 64 Bit For PCM600, check the supported operating systems from PCM600. 7

8 NEW FEATURES This chapter highlights the main new features of this release. More new features are listed in the following chapters. Modbus Slave TCP extension and serial line redundancy The Modbus TCP/IP server extension and serial line redundancy are done as extensions to the current Modbus slave. The Modbus slave can run two TCP communications and two serial port communications simultaneously. Earlier the Modbus slave only used only one serial port for communication. The TCP server extension adds new functionalities from which the most important is the possibility to use two separate TCP/IP communications. The TCP/IP extension and the serial line redundancy are added to the slave so that the serial functionality stays unchanged. DNP 3.0 Slave Support for Kepco 1.0 profile A set of features defined by DNP Kepco 1.0 profile is supported. The most important feature is the support of redundant line functionality using non-standard object group 80, variation 0. Special instructions for the system configuration for systems using this profile has been introduced. IEC Private range ASDU 150 is supported in both master and slave implementations of IEC

9 MicroSCADA IET Interface / Safe Import Feature Safe Import Feature has been developed to enable small process object changes during commissioning work. It can be found from Object Navigator, select Tools > Import and define Import File Name with the IET Safe Import Loadfile format. This feature modifies safe attributes in one or many process objects through a new file format with.sfx extension. Following attributes are defined as safe attributes: AC Alarm Class AD Alarm Delay AG Alarm Generation EE Event Enabled EH Event Handling HA History Activation HE History Enabled HF History at First Update HH History on History HL History Log Numbers LA Alarm Activation LD Listing Device OI Object Identifier OX Object Text CX Comment Text PA Printout Activation PH Printout History PU Printout at First Update 9

10 Measurement Reports configuration Copy&Paste Report Page Within the Report Page configuration it s now possible to copy and paste one ready configured page. Find&Replace text in Report Page Now it s possible to find and replace within the selected page some entered text. This feature works for the selected source columns. Both new features helps to decrease the engineering effort for the Report Page configuration in particular if bay oriented Report Pages are requested. 10

11 IMPROVEMENTS AND ERROR CORRECTIONS Base system Process Communication Proxy station malfunction When a proxy station was first forced to use either primary or secondary station (by setting STAn:BAS to 1 or 2) and then unforced by setting AS to 0, the proxy station did not switch to use the other one when the forced station was suspended. Network topology Wrong voltage level coloring Network Topology calculation now correctly sets voltage levels in situations where two powered transformers are looped by faulty or intermediate state switching devices. OPC Alarms & Events Server Crash of OPC Alarms & Events server When a client connected to OAES.exe and interface query failed or the client quickly released all interfaces, OAES occasionally crashed. Process Displays Initial double drawing of process view Opening a display containing multiple data sources may have caused double drawing of the view. If the last data source did not have any data variables, the display was initially drawn before the display data was received. At the later state the display was updated with correct data values. Measurement Reports and Trends Display Layout setting dialog Localization and corrupted confirmation message issues which is appearing after pressing Default Settings button from Layout Settings has been fixed 11

12 Legend attribute description has been localized. All attribute description uses localization text from SCIL Measurement Display Now user is able to load preconfigurations when logout and login again Column header font size in tabular view is corrected and now it is proper visible even user changes OS display size. Now user specific preconfigurations is visible in only own user level. Cyber Security Security event log filling rapidly Note! SYS 600C devices have security scripts deployed by default. The deployment can also be verified from the existence of.log files in sc\setup\security folder. If security scripts have been deployed to the server, fix should be done manually according to below instructions. There was an audit policy setting, which filled Windows security event log rapidly. Correct audit policy settings have now been set in security scripts. To manually fix this: 1. Open Command Prompt with admin privileges 2. Run following command to change subcategory Other Policy Change Events : auditpol /set /subcategory:"{0cce ae-11d9-bed }" /success:disable /failure:disable Tools Group Alarm editor Group alarm viewer could not open The toolbar for the Group alarm viewer has been removed because of missing functionality. Object State handling Object state 3 (not synchronized) will now be treated in the same way as Object State 0 Display Builder Malformed topology model generation In some situations Display Builder generated malformed topology models. The IX's for topology objects were not correctly formatted resulting TOPO_OBJECT_CN_CROSS_REFERENCE_NOT_FOUND errors. 12

13 Communication IEC Master Station attribute MS Message Application is accepted as vector Station attribute MS Message Application is accepted as vector also for IEC station object. If multiple values are given to attribute MS, system messages from the station object are sent to multiple applications. IEC Slave Station attribute MS Message Application is accepted as vector Station attribute MS Message Application is accepted as vector also for IEC station object. If multiple values are given to attribute MS, system messages from the station object are sent to multiple applications. Incorrect summer time bit handling in events The SU bit of the time stamp of the events was incorrectly initialized depending on the existence of the CTRL parameter of the EV attributes. It was possible that the event contained the summer time bit set thought it was not set by the application. The SU bit is present only in the events using the long timestamp CP56Time2a. Test bit of time synchronization command incorrectly handled In case the master sends time synchronization with 'test bit' set, system time was uselessly set according to the message. 'Test' bit of a command is not handled correctly with setting 'Exceptional command checking' In case the bit 8 (Exceptional command checking) of the station attribute RM was set, the commands containing the 'Test' bit set were handled incorrectly and a negative confirmation using COT 45=Unknown cause of transmission was uselessly returned to the master. IEC Master Station attribute MS Message Application is accepted as vector Station attribute MS Message Application is accepted as vector also for IEC station object. If multiple values are given to attribute MS, system messages from the station object are sent to multiple applications. ASDU33 and private ASDU150 supported The support for the reception of the ASDU <33> := Bitstring of 32 bit with time tag CP56Time2a and the private range ASDU <150> has been added. 13

14 IEC Slave Station attribute MS Message Application is accepted as vector Station attribute MS Message Application is accepted as vector also for IEC station object. If multiple values are given to attribute MS, system messages from the station object are sent to multiple applications. Incorrect summer time bit handling in events The SU bit of the time stamp of the events was incorrectly initialized depending on the existence of the CTRL parameter of the EV attributes. It was possible that the event contained the summer time bit set although it was not set by the application. Test bit of time synchronization command incorrectly handled In case the master sends time synchronization with 'test bit' set, system time was uselessly set according to the message. 'Test' bit of a command is not handled correctly with setting 'Exceptional command checking' In case the bit 8 (Exceptional command checking) of the station attribute RM was set, the commands containing the 'Test' bit set were handled incorrectly and a negative confirmation using COT 45=Unknown cause of transmission was uselessly returned to the master. ASDU33 and private ASDU150 supported The support for the transmission of the ASDU <33> := Bitstring of 32 bit with time tag CP56Time2a and the private range ASDU <150> has been added. IEC Master Station attribute MS Message Application is accepted as vector Station attribute MS Message Application is accepted as vector also for IEC station object. If multiple values are given to attribute MS, system messages from the station object are sent to multiple applications. DNP 3.0 Master Station attribute MS Message Application is accepted as vector Station attribute MS Message Application is accepted as vector also for DNP station object. If multiple values are given to attribute MS, system messages from the station object are sent to multiple applications. Conflict in SA value setting Values bigger than 1000 for the station attribute SA may have conflicted with the values which has been used internally in the initialization of the STA object. The problem may have appeared if the configuration has been created with a SCIL script. 14

15 DNP 3.0 Slave Station attribute MS Message Application is accepted as vector Station attribute MS Message Application is accepted as vector also for DNP station object. If multiple values are given to attribute MS, system messages from the station object are sent to multiple applications. Special port number can be used in UDP mode also Using a special notation with the station attribute IA, a non-standard port number can be used in the UDP mode also. Stand-by line functionality is possible using new station attribute QC If a new station attribute QC is defined to have non-zero values, the event queues are cleared. This configuration provides a possibility to create a redundant line solution in which certain request type from the master clears the buffered events from the stand-by line. Option to disable unsolicited responses in start-up The RM attribute of the station, bit 3, can be used to disable the transmission of unsolicited event messages in startup. If this bit is set and the event sending should occur as unsolicited, it must be enabled by the master with request 0x14 ENABLE_UNSOLICITED. RM bit 3 has an effect on all event classes 1, 2 and 3. Unsolicited event sending was not correct after enabling If an 'Enable Unsolicited' message is received and there were buffered events, the automatic transmission of these events did not start correctly. Internal indications word IIN can be controlled from the COM500i application The two-byte internal indication field which is present in each response message from can now be controlled from the MicroSCADA application using the station object attributes IN and CF. See protocol specific manual for more detailed information. Event releasing does not work correctly If the master issues an event poll containing multiple classes, events were not released correctly from the event queue although a valid confirmation was received from the master. This led to a buffer overflow. The error is in version 9.3FP2 but not in earlier versions. Modbus Master Improved TCP connection logic In case the configured IP-address for an IED has not been present in the network, the TCP connection to other IEDs may have been disturbed or delayed. IA setting fixed If the value of the station attribute IA was set by the MicroSCADA application in runtime, error 13833=PLCC_INVALID_ATTRIBUTE_VALUE was uselessly returned. The problem appeared only if the address has been entered once before. 15

16 AV and DV attribute write handling improved Handling of long data vectors for STA attribute AV and DV has been improved. Writing to these attribute will cause a request of function 16 = Write Multiple Registers. This modification has an effect both in serial and TCP modes. Writing to BV attribute caused an incorrect request If the station attribute BV was written and the amount of values given from SCIL was dividable with 8, the forming of the request was incorrect. One useless data byte was added to the message. The message was still formally correct and may have been handled normally by the slave device. Modbus Slave TCP extension and serial line redundancy The Modbus TCP/IP server extension and serial line redundancy are done as extensions to the current Modbus slave. The Modbus slave can run two TCP communications and two serial port communications simultaneously. Earlier the Modbus slave only used only one serial port for communication. The TCP server extension adds new functionalities from which the most important is the possibility to use two separate TCP/IP communications. The TCP/IP extension and the serial line redundancy are added to the slave so that the serial functionality stays unchanged. Separate debug output window In windows 7 and in windows 2008 server the Modbus slave is started in session 0 which has no visible console window. A separate output window has been introduced to allow users to see the possible error messages which are enabled with the setting debug_info in the configuration file. Incorrect response to function code 11 request If the Modbus master issued a request with function code 11 (Get Comm Event counter), the response message was formally incorrect. No Buffers available error In case the master sent too many write analog value requests to Modbus slave registers using function code 16, error no buffers available may have printed to the console. Now an exception code is returned to the master to indicate that the slave is busy, meaning that the last write message handling hasn t ended yet. This exception code is now also sent in similar situations with function codes 5, 6 and 15. Amount of analog setpoints in one message limited The maximum amount of the analog values of type word in one Modbus write message (function code 16) has been limited to 28. If the amount of the values is higher, an exception response is returned to the master. The Bit Value write message has also been limited. The maximum Bit Value message length is now 38. Modbus slave attribute functionality didn't follow the manual Some of the attributes of the Modbus slave attributes did not follow the manual in detail. Testing of write attributes may have caused errors because the checking of the arguments was not adequate in all cases. Also some manual errors were corrected. The mentioned attributes were used only by the COM500i signal routing procedures. Improved behavior when the main application goes cold In case the main application went cold, the Modbus slave tried to connect the application 3 times and then reinitialized the CPI connection. This behavior filled the debug window and was considered wasteful. Now the 16

17 Modbus slave doesn t do the re-initialization if the connection to the application is lost, but tries to reconnect after a while. AV and DI writings are done even if an error occurs Write messages from the master were handled to some extent even though an error was detected in the message attributes. Incorrect database initialization Index 0 in AV, DI, DD and PC write messages in no longer used for initialization anymore. It worked well but in some situations it caused unwanted behavior with the X-reference Tool. New AI (Analog Initialization) and II (Indication Initialization) were introduced for initialization purposes. Behavior when IU attribute is set to in_use/ not_in_use The status of the data points changed to 10 when a stations IU attribute was set to not_in_use, and to 2 when the IU attribute was set back to in_use. Now the status of data points are no longer affected by stations IU attribute. ANSI X3.28 Half Duplex The usage of Header Timeout disturbed communication with virtual serial ports In case the virtual serial ports were used for the communication line and the line attribute HT (Header Timeout) was bigger than 0, it was possible that also valid responses were not received correctly. This caused useless retransmissions and error printouts in the MicroSCADA application. New operation mode When the ANSI X3.28 half duplex line is directly connected to the IEDs, one disappeared application layer response message has caused a suspension for a STA object and this has disturbed the cyclical data reading. This suspension can now be disabled by using the line attribute OM, bit 0. See the description of the line attribute OM from the System Objects manual for more information. Disabling of the link layer retransmissions is possible In case the link layer retransmissions disturb the connected IED or the data write message contains time synchronization data, the disabling of the retransmissions from the link layer may be needed. This is now possible by using the line attribute OM, bits See the description of the line attribute OM from the System Objects manual for more information. 17

18 COM 500i Application Signal Routing Modbus slave initialization with new attributes The initialization of Modbus slave has been changed to new AI and II attributes. Scil error in command procedure COM_CPISS Log writing caused error in com_cpiss command procedure, if system message was received from Modbus slave. External OPC Data Access Client External OPC DA Client Status of measurements with range after communication break During and after recovery of communication break with IED the status of measurements with range (limit checking in IED) were not updated correctly. This was seen e.g. as incorrect color coding of the measurements in process display. Setting the station IU=0 may block communication to other IEDs If STA object is take out of use i.e. IU->0 and configuration contains grouped items for the IED in question, the data updating may be blocked from all IEC61850 IEDs configured to the same External DA Client. The behaviour is incorrect in version 9.3FP2 but not in earlier versions. 18

19 DOCUMENTATION The user documentation is available as PDF files on The documentation is also included in the product package. Notice! Adobe Acrobat Reader is not included in the delivery of this product, but can be freely downloaded from Updated Manuals SYS 600 DNP 3.0 Slave Protocol SYS 600 Modbus Master Protocol SYS 600 Modbus Slave Protocol SYS 600 Installations and Administration Manual SYS 600 System Configuration SYS 600C Product Guide SYS 600C User's Guide 19

20 Appendix 1 MicroSCADA Pro SYS FP2 Hotfix 1 The Hotfix includes corrections for the following problems: 1. Event/Alarm/Blocking List When Monitor Pro application window is started with command line arguments to login automatically and load eventlist / alarmlist / blockinglist, the colors in the displays were initially not following the selected color scheme. 2. Event/Alarm List When Monitor Pro application window is started with command line arguments to login automatically and load eventlist / alarmlist, the list content was initially not updated correctly. 3. Data Mirroring Mirroring stops working for a specific unit if the IU attribute of a process object is programmatically set to 0 and then immediately back to 1 or SS is set to MANUAL and immediately back to AUTO and the modified process object is the last mirrored process object which is connected to the unit. 4. Process Database User defined process objects generate alarms if they have alarm limits (LI and HI) defined, even if AC=0. 5. Proxy Stations When either primary or secondary station gets suspended, the OS of connected process objects goes to 2 even if the other connection is ok. 6. System Configuration Tool When creating a new configuration (Configuration/New) bad default values are given to some of the attributes of the Node object. Attributes TL, LP, MI and SE have value "#" and the attribute KS has value 1. An attempt to view the attribute KS results to the SCIL error 421 SCIL_ATTRIBUTE_NOT_FOUND. 7. Object Navigator Copy/Paste operation of Process Object or Data Object failed, if the object has a reference to a non-existing logging profile. 8. Cyber Security Settings In some computers, the DCOM settings script OPCDCOM.cmd overwrote Windows default DCOM setting. This resulted in situation where some programs or dialogs did not start or open, for example, Windows Explorer in the Taskbar. However, HSB-Workplace connection worked correctly. ANONYMOUS LOGON user account should have Local and Remote access rights for DCOMCNFG.exe > COM Security > Access > Edit Limits. This is now fixed. The script file also takes a backup of current settings before 20

21 executing new DCOM settings and it has better error handling for missing command line arguments. 9. Process Displays Mouse click events on symbols mapped to Memory or Constant Data Variables were not recognized correctly. 10. Manuals Some pictures were missing in the System Configuration Manual 11. COM500i If configuring an IEC x AO command in COM500i with functions Interlock override and Synchrocheck override, the process objects BNCC_0000x: P indexes 11, 12 and 13 are created as BI even if "Receive as Double command" are configured for that object. 12. Measurement Reports If a report contains several pages it was possible to save the curve properties for only one page into the preconfiguration. The report display crashed if the date was selected in the Day report. 13. Notify Window Cyrillic characters were not shown correctly. 14. IEC communication When an IED is disconnected, taken out of use (IU=0) or IEC61850 OPC server is killed, station statuses are not update correctly in System Self Supervision 15. Monitor Pro Launching Visual SCIL tools from menus or toolbars did not accept changes in the Tool Size option. The Hotfix includes the following new functionality: 1. Event/Alarm/Blocking List It is now possible to save the data shown in the lists to a file in CSV format. The separator between the columns is the semicolon sign. 21

22 Appendix 2 MicroSCADA Pro SYS FP2 Hotfix 2 The Hotfix includes corrections for the following issues: 1. Base system, Internal OPC DA client When a process object is created into an OPC_DA type station on-the-fly, two (identical) OPC item subscriptions are created in the OPC client (OPCC). Consequently, the process object is updated twice whenever its value changes. Excessive subscriptions are generated also when the process object is taken out of use and then back to use. Subscriptions are done correctly at application start-up. Therefore, the problem vanishes after restarting the application. 2. Communication, PC-NET When the first STA object connected to a IEC master is taken into use (IU=1) for the first time after startup of PC-NET, the APL_EVENT event channel is incorrectly activated with event 'RUNNING' with other STA objects connected to the same line. 3. Communication, IEC61850 During buffered reporting resynchronization the IEC OPC Server made checks for report entry time and invalidated requested reports due to receiving false report times. This caused requesting of all available reports from IED buffers resulting to duplicate events in event list. Functionality is now changed so that the report entry time is no longer checked. 4. Communication, IEC61850 After startup the IED Device connection status OPC item remained with bad quality until 1st connection is established. The behavior is now changed so that the item gets good quality at startup with initial timestamp ( : UTC). The item value is updated once when 1st connection attempt with IED fails with current timestamp. After this item is updated on connection status changes. 5. Communication, DuoDriver The new DuoDriver version now also accept licenses without expiration date. You need to un-install the old DuoDriver and install the new one delivered with this Hotfix. 6. Application Frame, Process Display In some situations, like hibernating the computer, the Process Display stopped from updating. 7. Application Frame, Process Display 22

23 It is now possible to open Process Display files from PICT subfolders. All other folders are prohibited when opening Process Displays from command line or using Tool Launcher. When using Open File dialog any Process Display can be still opened. 8. Application Frame, Process Display Monitor Pro instances in RDP sessions are now informed about changes in Process Displays when such file is saved in Display Builder. 9. Application Frame, Start argument When using -login or -loginonce command line arguments the login sometimes failed with error invalid username or password. 10. Application Frame, Start argument Monitor Pro command line argument -wait works now also with Windows 2008 Server operating system. 11. MicroSCADA login, Emergency login Login to classic monitor using the emergency administrator account and password has been fixed 12. Event/Alarm/Blocking Display, Color settings An unhandled exception occurred in case of using decimal number values inside the coloring condition. 13. List and Report Displays, Localization It was not possible to localize the following text items: - Title in color selection dialog used the same reference string for all settings. - Unicode character strings were not handled correctly. For example Measurement Reports comment was not saved correctly and it was not possible to use certain Unicode strings as Display filter. 14. Event Display After user logs out from Monitor Pro and then logs in using same user credential the event list was not always able to show event rows correctly. 15. Alarm Displays It was not possible to acknowledge free type Process Object alarms. 16. Blocking Display Number of Signals fields were not showing the correct total amount of blocked signals. 17. Measurement Reports, Data collection The base period calculation for Report Objects of type Calculated failed. 23

24 18. Trends Application, Navigate menu An unhandled exception occurred if Process Objects for configured Trend curves have been deleted. 19. PCM 600 project integration Launching PCM600 from the process display sometimes failed if several PCM600 versions were installed in the computer. Now always the latest (highest) PCM600 version is used. 20. Display Builder, Object browser PCM600 project data load time has been improved. 21. Display Builder, Settings The coordinate system setting (World/Screen) was not correctly saved and World coordinates were not correctly used when Display Builder was started the first time in a Monitor Pro session. 22. Network Topology Coloring, Earth switch and earth symbol Earth switch symbol coloring was not always consistent. Two earth switch symbols connected to a same busbar were sometimes colored using different colors. 23. Network Topology Coloring, Line indicator It was not possible to add several feeding points with independent voltage level definitions to the same process object group. This can be used e.g. to have one line indicator showing the power flow and another feeding the voltage level color to the feeder segment. 24. Power Process, control dialogs Some not visible control elements from other tabs could get activated by mouse click in the empty advanced view area. 25. Power Process, control dialogs When auto-reclosing function was installed and configured within a bay, only an empty reclosing tab was shown in a switch control dialog. 26. VisualSCIL Graph object An unhandled exception occurred when selecting some item from the VS_GRAPH popup menu. 27. Cyber Security scripts, Windows services Note! SYS 600C devices have security scripts deployed by default. The deployment can also be verified from the existence of log files in sc\setup\security folder. If security scripts have already been deployed to the server, these fixes should be done manually, see instructions below. The startup type of Task Scheduler service was set to Disabled. This setting was 24

25 valid in older Windows operating systems but not in newer ones (Windows 7 and later). Automatic startup type has now been set for this service in security scripts. To manually fix this: 1. Open regedt32.exe (Registry Editor) 2. Browse to the key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Schedule 3. Set value Start=2 4. Close Registry Editor and reboot the server A Windows service called Diagnostic Host Service did not have proper access rights and Windows event log was filling with events (ID: 7000). Correct access rights have now been set in security scripts. To manually fix this: 1. Run secpol.msc (Local Security Policy) 2. Browse to User Rights Assignment > Profile system performance and open Properties 3. Add user: "NT Service\WdiServiceHost" and confirm changes 4. Close Local Security Policy and reboot the server 25

26 Appendix 3 MicroSCADA Pro SYS FP2 Hotfix 3 The Hotfix includes corrections for the following issues: 1. Base system, Network topology calculation The communication between the kernel and the OPC DA Server could stop working ('OPC Server closed:0'). This could happen in large systems with big overview displays if the communication to IED s was lost or re-established while large overview displays were shown. 2. Communication, OPC DA client IEC61850 During and after recovery of communication break with IED the status of measurements with range (limit checking in IED) were not updated correctly. This was seen e.g. as incorrect color coding of the measurements in process display. 3. Monitor Pro Application Frame Alarm Notifications / Auto-logout functionalities could stop working if the computer has been in sleep or hibernation state. It was not possible to localize the header of message boxes coming from Monitor Pro application window. A new text with ID 127 ( Monitor Pro ) is located in the resource file FrameWindow_EN.dll. With operator access rights it was possible to create/delete files and folders in the File Open/Save/Select dialogs. This is now disabled and the dialogs have also been harmonized. 4. Monitor Pro, Process Display It is now possible to locate objects in Process Displays from VisualSCIL dialogs. This can be done with the LOCATE_OBJECT identifier in SendDisplayCommand function. See Application Design manual for more information about SendDisplayCommand usage and parameters. It is now possible to modify own user specific shortcuts in Process Display Visibility dialog with authorization level >= 1 in GENERAL group. To modify Application specific shortcuts requires authorization level >= 2 in GENERAL group. Other users' shortcuts can be modified with authorization level 5 in GENERAL group (no change). Control Dialog related Application Settings did not work properly if the user logs in to several applications in the same Monitor Pro session. 26

27 The symbol file name has been added to the Find results in Monitor Pro. Temporary zoom areas were sometimes not cleared correctly between user sessions. When Monitor Pro sessions were used in workstations with different screen resolutions it could happen that the Monitor Pro window was placed outside the visible area. The same could happen also for floating toolbars. 5. Event Display, Navigating between event sets did not work properly if all events in the event set had same time stamp. 6. Measurement Report, Display Week reports using base period history length of one year could hang when navigating to the first week of the year. The last saved user specific Report did not show up in the Navigate/Reports sub menu. Application and user specific report pre-configurations are separated by separator line in the Navigate/Reports menu. 7. Measurement Reports, Configuration. It was not possible to configure empty columns in the Report Page. This can be used as a kind of separator between columns. The SCIL operation check was too strict e.g. preventing the usage of variables not declared in the SCIL program itself. The menu construction was not always done in the correct alphabetical order. The Measurement Report upgrade dialog was shown each time the Measurement Reports node was selected in the Object Navigator, as long as the report were not upgraded. Now the upgrade dialog can be suppressed but it can be released again from the file list context menu. NOTE! Keeping older version prevents any modification to the existing configuration. Obsolete Report Objects types EN and GA are not supported anymore in the Measurement Reports package of 9.3 FP2. Object of these types were ignore during the upgrade but will now be converted to "Measured Period (MP)" type instead. In case the common Report data read procedures BGU_READSF and BGU_READPF from classic LIB510 Measurement Reports are used in an application they will be upgraded so that they can still be used also with the new Report Configuration database. 27

28 8. Trends Application, Trend basket Changing the trend number without saving current configuration in Trend settings dialog occasionally caused Monitor Pro to hang. 9. Measurement Reports and Trends, Legend Legend column names can be localized now. NOTE! The Reports and Trends specific attribute names can be found in Measurement or Trends resource dll - sc\prog\sa_lib\en\trendapp_texts_en.dll - sc\prog\sa_lib\en\measreport_texts_en.dll The common attributes as e.g. OI or OX in the text database: - sc\sys\active\sys_\sys_text.sdb 28

29 Appendix 4 MicroSCADA Pro SYS FP2 Hotfix 4 The Hotfix includes modifications to the IEC communication that have been made in order to be granted the Level A conformance certificate from KEMA. The modifications are the following: 1. IEC Certificate Level A SYS IEC Client (IEC OPC Server v1.6) has been conformance tested and is certified with an UCA IEC Certificate Level A issued by KEMA. The client system has not shown to be non-conforming to: IEC , 7-1, 7-2, 7-3, 7-4 and 8-1 Communication networks and systems in substations. 2. Dynamic dataset handling improvements Dynamically created datasets are now checked and need to match in configuration and IED. In case of mismatch the dataset is deleted from IED and recreated. 3. Command termination indication added An indication of command termination message from IED is now available for all control data objects using enhanced security control model. Indication for success or failure response can be seen from new cmdtermination OPC item in every data object. 4. SNTP client using SNTP v4 The SNTP client now uses SNTP v4 to request time synchronization. 5. Disturbance recording download improved The automatic disturbance recording download now supports files with whitespace in file name. 6. Functionality monitoring status changes More statuses are available for observing object status of device connection (IED.Object status) and reporting initialization (IED.LD.LN.RCB.Object status). Some object status codes have also new meanings and one is removed. 29

30 INSTALLATION Installing When installing a new system it is required to install SYS FP1a and FP2 beforehand. SYS FP3 will not install if FP2 is not detected on the system. Upgrading to is performed by installing FP3 on an existing FP2 system. The product package consists of several executable files. However, only SYS600_93_FP3.exe should be manually executed when installing the product. The documentation is in PDF format and is installed together with the product. During the installation, a computer restart might be requested before the installation is completed. In this case the installation must be manually started again after the restart. A computer restart may also be requested after the installation has been completed and it is highly recommended to perform the restart to ensure system stability. 30

31 ABB Oy Substation Automation Products P.O. Box 699 FI Vaasa FINLAND Tel Fax