1MRS235928, A, May 02, 2013 MicroSCADA Pro SYS FP2 Hotfix 2 Release Note. MicroSCADA Pro SYS FP2

Transcription

1 Products Description MicroSCADA Pro SYS FP2 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. Copyright 2013,, The information in this document is subject to change without notice and should not be construed as a commitment by,.,

2 6. Application Frame, Process Display In some situations, like hibernating the computer, the Process Display stopped from updating. 7. Application Frame, Process Display 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. Copyright 2013,, The information in this document is subject to change without notice and should not be construed as a commitment by,.,

3 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. 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. Copyright 2013,, The information in this document is subject to change without notice and should not be construed as a commitment by,.,

4 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 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\s ervices\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 Dependencies This Hotfix should only be used with SYS FP2. SYS FP2 Hotfix 1 should be installed first. Copyright 2013,, The information in this document is subject to change without notice and should not be construed as a commitment by,.,

5 Recommendation Installation It is recommended to install this Hotfix in all SYS FP2 systems. To install the Hotfix: 1. Stop the SYS 600 system 2. Run the installation program SYS600_93_2_HF2.exe Note! In Windows Server 2003 the installation must be started by using the Windows Add or Remove Programs utility. The Hotfix will install the following new files or file versions: sc\sa_lib\base\bbone\use\bgu_common.txt sc\sa_lib\base\bbone\use\bgu_eab_main.txt sc\sa_lib\base\bbone\use\bgu_sa_lib_rev.txt sc\sa_lib\base\bbone\use\bgu_utoola.vso sc\sa_lib\base\reports\use\bmu_bp_cal2.cin sc\sa_lib\base\reports\use\bmu_init.bin sc\sa_lib\base\reports\use\bmu_updt.txt sc\stool\aplbuild\objmr_lib.vso sc\prog\sa_lib\eablistcomm.dll sc\prog\sa_lib\alarmctl.dll sc\prog\sa_lib\en\alarmctl_en.dll sc\prog\sa_lib\blockingctl.dll sc\prog\sa_lib\en\blockingctl_en.dll sc\prog\sa_lib\eventctl.dll sc\prog\sa_lib\en\eventctl_en.dll sc\prog\sa_lib\framewindow.exe sc\prog\sa_lib\instancehandler.exe sc\prog\sa_lib\en\controldialog2_en.dll sc\prog\sa_lib\controldlgcommon.ocx sc\prog\sa_lib\controldlglaunch.exe sc\prog\sa_lib\controldlglr.dll sc\prog\sa_lib\controldlgmeasurement.dll sc\prog\sa_lib\controldlgswitch.dll sc\prog\sa_lib\controldlgtransformer.dll sc\prog\sa_lib\ctrldlgalarmindicator.dll sc\prog\graphicsengine\system\dvdraw.exe sc\prog\graphicsengine\system\opcconnection.dll sc\prog\pcm_client\pcmclientsetup.exe sc\setup\duodriver\duodrivernotifyobj-5a aef3-457f-8a66-adf64ec52a8d.dll sc\setup\duodriver\duodrivernotifyobj-5a aef3-457f-8a66-adf64ec52a8d_x64.dll sc\setup\duodriver\duodrv_mp.cat sc\setup\duodriver\duodrv_mp.inf sc\setup\duodriver\duodrv_prot.cat sc\setup\duodriver\duodrv_prot.inf sc\setup\duodriver\duodrvng.sys sc\setup\duodriver\duodrvng_x64.sys sc\setup\duodriver\setup.exe sc\setup\duodriver\setup.ini sc\setup\security\sys600server.inf sc\setup\security\sys600workplace.inf sc\prog\pc_net\pc_nets.exe sc\prog\61850_opc_server\iec61850 OPC Server\bin\opcs_iec61850.exe sc\prog\exec\ddex.exe sc\prog\exec\file.exe sc\prog\exec\hclxaw.dll sc\prog\exec\hclxm.dll sc\prog\exec\hclxt.dll sc\prog\exec\inet.exe sc\prog\exec\mtfl.exe sc\prog\exec\netc.exe sc\prog\exec\neti.exe sc\prog\exec\oaec.exe sc\prog\exec\oaes.exe sc\prog\exec\opcc.exe sc\prog\exec\opcc.pdb sc\prog\exec\opcs.exe sc\prog\exec\oseh.exe sc\prog\exec\pica.exe sc\prog\exec\picg.exe sc\prog\exec\picl.exe sc\prog\exec\picn.exe sc\prog\exec\pico.exe sc\prog\exec\picv.exe sc\prog\exec\picx.exe sc\prog\exec\prin.exe sc\prog\exec\prnc.exe sc\prog\exec\proc.exe sc\prog\exec\prof.exe sc\prog\exec\pros.exe sc\prog\exec\repf.exe sc\prog\exec\repl.exe sc\prog\exec\repr.exe sc\prog\exec\scil.exe sc\prog\exec\scs.exe sc\prog\exec\scspica.dll sc\prog\exec\scspico.dll sc\prog\exec\scsshr.dll sc\prog\exec\sysm.exe sc\prog\exec\shad.exe sc\prog\exec\vgal7.dll sc\prog\exec\vidc.exe sc\prog\exec\xlib.dll To uninstall the Hotfix: 1. Stop the SYS 600 system 2. Run the installation program SYS600_93_2_HF2.exe /r 3. Re-install the main product SYS FP2. Copyright 2013,, The information in this document is subject to change without notice and should not be construed as a commitment by,.,