CIMPLICITY 9.5 Important Product Information SIM 17

Transcription

1 CIMPLICITY 9.5 Important Product Information SIM 17 August 7, 2018

2 Contents Purpose of this Document Installation New Features and Enhancements Alarms CIMPLICITY v9.5 SIM 5: Alarm Sound Manager Options CIMPLICITY v9.5 SIM 1: Alarm Messages Message Processing Limits CimEdit/CimView CIMPLICITY v9.5 SIM 15: Support for removing screens and obtaining screen count independently from screen cache CIMPLICITY v9.5 SIM 15: Support for determining usage of string space CIMPLICITY v9.5 SIM 1: Debounce Configuration Attributes CIMPLICITY Options CIMPLICITY v9.5 SIM 1: DEP Support Expression Editor Enhancements OPC Server CIMPLICITY v9.5 SIM 17: Multiple Setpoint Support for Asynchronous Write Items Scripting and Open Interface CIMPLICITY v9.5 SIM 10: Disable Delete and Export Records options from Script CIMPLICITY v9.5 SIM 7: Parameters for reloading.net Assemblies CIMPLICITY v9.5 SIM 3: Enhancements to Historian Tag Timestamp CIMPLICITY v9.5 SIM 3: DB Deadband Functions CIMPLICITY v9.5 SIM 2: Enhancements to Point Management Script Functions Tracker CIMPLICITY v9.5 SIM 15: Security enhancements for Tracker SQL Database Trends and DGR CIMPLICITY v9.5 SIM 10: Timezone Support for Trend Control User/Windows Authentication Workbench CIMPLICITY v9.5 SIM 4: Project Upgrade Progress Dialog CIMPLICITY v9.5 SIM 1: Firewall Configuration Settings GE Digital 2

3 CIMPLICITY v9.5 SIM 1: Save Point Values Fixed Defects Issues Resolved: Alarms CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: CimEdit/CimView CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Classes and Class Objects CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM GE Digital 3

4 3.3.4 CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Device communications CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Logging CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Login CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Networking CIMPLICITY v9.5 SIM GE Digital 4

5 3.7.2 CIMPLICITY v9.5 SIM Issues Resolved: Points and Scripting CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Proficy Integration CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Proficy Process Systems CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Project and System Management CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM GE Digital 5

6 CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Recipes CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Server Redundancy CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Statistical Process Control (SPC) CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Tracker/Order Execution Management CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM GE Digital 6

7 CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Issues Resolved: Trends and DGR CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM CIMPLICITY v9.5 SIM Known Issues General Information McAfee Anti-virus Details WebSpace Special Instructions Contact GE Digital GE Digital 7

8 PURPOSE OF THIS DOCUMENT The purpose of this document is to provide information to facilitate installing and using this SIM. Do not install this Service upgrade unless your system has a build number equal or greater than: CIMPLICITY v.9.5 Build 36749r. 1 INSTALLATION To install this update: 1. Go the GE Digital Web site: 2. Select Software > HMI SCADA > CIMPLICITY. 3. Under Filter Content by, select Downloads. The SIM patch labeled CIMPLICITY_95SIM17_36749r.exe appears in the list of download files; the list is sorted by date by default. 4. Select the SIM and download the file locally. 5. Extract the SIM executable files into a temporary/working directory. 6. Stop all CIMPLICITY applications on the host computer. 7. Open Windows Explorer. 8. Open the temporary/working directory where you placed the downloaded file. 9. Double-click patch.exe to initiate the installation program. GE Digital 8

9 2 NEW FEATURES AND ENHANCEMENTS 2.1 ALARMS CIMPLICITY v9.5 SIM 5: Alarm Sound Manager Options DE18927 SF Alarm Sound Manager now has the following configuration option added: Attribute Name AMV_SOUND_LOOP Purpose/Meaning Provide additional support for continuous playback of alarm sound audio files Attribute Value N or n [Default] Purpose Current Application behavior will not be affected. Y or y When the attribute value is set to Y or y: Alarm sound will be repeated in loop till the specified stop criteria is satisfied Sound will stop immediately if stop criteria is satisfied The alarm audio file will continue to play in loop, even if the replay option is not selected Alarm Sound file will pause immediately if muted and will resume playing when cleared CIMPLICITY v9.5 SIM 1: Alarm Messages Message Processing Limits DE16460 SF Alarm Properties dialog now has the following fields added: GE Digital 9

10 Property Name Purpose Permitted Limits Default Value Auto processing interval Number of Auto Alarms processed at a time The time interval (in minutes) for processing the auto alarms. The number of auto alarms that will be processed at a time. 1 to to GE Digital 10

11 2.2 CIMEDIT/CIMVIEW CIMPLICITY v9.5 SIM 15: Support for removing screens and obtaining screen count independently from screen cache US US Four new methods have been added to enable you to do the following actions in CimView or CimEdit: Remove the display screens and library screens independently from the screen cache. Obtain the number of screens in the display screen cache and the library screen cache independently. Method Description Example GefApplication.Fl ushdisplayscreen Cache GefApplication.Fl ushlibraryscreen Cache GefApplication.Di splayscreencache Count GefApplication.Li braryscreencach ecount This method removes all the screens that can be displayed from the screen cache. This method removes all the library screens from the screen cache. This method obtains the number of screens in the display cache. This method obtains the number of screens in the library cache. Sub Application_FlushDisplayScreenCache() CimGetScreen.Application.FlushDisplayScreenCache End Sub Sub Application_FlushLibraryScreenCache() CimGetScreen.Application.FlushLibraryScreenCache End Sub Sub Application_FlushDisplayScreenCache() MsgBox "Screens in display cache = " + CimGetScreen.Application.DisplayScreenCacheCount End Sub Sub Application_FlushLibraryScreenCache() MsgBox "Screens in library cache = " + CimGetScreen.Application.LibraryScreenCacheCount End Sub CIMPLICITY v9.5 SIM 15: Support for determining usage of string space US Four new methods have been added in CimView to enable you to determine how the string space is managed and how much of it is remaining. GetMemoryInfoStringSpace This method obtains information on the memory usage for string space. It has the following parameters: used: The number of used bytes in the string space. free: The number of free bytes in the string space. total: The number of total bytes in the string space. outflags: The internal information about the string space. This parameter is unused. Note: The sum of the used and free parameter values will not be equal to the value of the total parameter. This is because of the overhead that is used to manage the allocated blocks. GE Digital 11

12 GetMemoryInfoStringSpaceHandles This method obtains information on the handle usage for string space. It has the following parameters: used: The number of handles that have been used. free: The number of handles that are free. total: The total number of handles (32736). The code in the following example uses the GetMemoryInfoStringSpace and GetMemoryInfoStringSpaceHandles methods to obtain memory information and display it in a dialog box. Option Explicit Sub OnMouseUp(x As Long, y As Long, flags As Long) Dim mymsg As String Dim used As Long, free As Long, total As Long, outflags As Long Dim charcount Dim i Dim myarray(100) As String mymsg = "" mymsg = mymsg & Chr$(13) & "---- BEFORE ----" GetMemoryInfoStringSpace used, free, total, outflags mymsg = mymsg & Chr$(13) & "SPACE used:" & used & ", free:" & free & ", total:" & total mymsg = mymsg & ", outflags:" & outflags GetMemoryInfoStringSpaceHandles used, free, total mymsg = mymsg & Chr$(13) & "HANDLES used:" & used & ", free:" & free & ", total:" & total ' Use up some string space and handles charcount = 0 For i = LBound(myarray) To UBound(myarray) Step 1 myarray(i) = "ABCDEFGHIJKLMNOPQRSTUVWXYZ " & i & " ABCDEFGHIJKLMNOPQRSTUVWXYZ " charcount = charcount + Len(myarray(i)) Next i mymsg = mymsg & Chr$(13) mymsg = mymsg & Chr$(13) & "---- AFTER populating, elements:" & (UBound(myarray) - LBound(myarray)) _ & " char count:" & charcount & " ----" GetMemoryInfoStringSpace used, free, total, outflags mymsg = mymsg & Chr$(13) & "SPACE used:" & used & ", free:" & free & ", total:" & total mymsg = mymsg & ", outflags:" & outflags GE Digital 12

13 GetMemoryInfoStringSpaceHandles used, free, total mymsg = mymsg & Chr$(13) & "HANDLES used:" & used & ", free:" & free & ", total:" & total End Sub MsgBox mymsg, ebokonly+ebinformation, "Memory Info" GetMemoryInfoPublicSpace This method obtains information on the memory usage for storing the values for public variables used in scripts at the module level. It has the following parameters: used: The amount of memory in bytes that has been used for public variable space storage. free: The amount of free space to hold new variables. total: The amount of memory available for public variables. GetMemoryInfoSymbolSpace This method obtains information on the memory usage for storing the names of the symbols for public variables used in scripts at the module level. It has the following parameters: used: The amount of memory in bytes that has been used for public variable name storage. free: The amount of free space to hold new variable names. total: The amount of available memory for public variables names. The code in the following example uses the GetMemoryInfoPublicSpace and GetMemoryInfoSymbolSpace methods. Public testpubliclong As Long Public testpublicstring As String Private pv_test As Long Private pv_teststring As String Type ExampleRect left As Integer top As Integer right As Integer bottom As Integer End Type Public dd As ExampleRect Sub OnMouseUp(x As Long, y As Long, flags As Long) Dim ssused As Long GE Digital 13

14 Dim ssfree As Long Dim ssmax As Long Dim psused As Long Dim psfree As Long Dim psmax As Long Dim SymUsed As Long Dim SymFree As Long Dim SymMax As Long Dim handlesused As Long Dim handlesfree As Long Dim handlesmax As Long Dim memflags As Long testpubliclong = 1200 pv_teststring = 1200 testpublicstring = "constant string to show usage of string space by constants" pv_teststring = "More data, more data" GetMemoryInfoStringSpaceHandles handlesused, handlesfree, handlesmax GetMemoryInfoStringSpace ssused, ssfree, ssmax, memflags GetMemoryInfoPublicSpace psused, psfree, psmax GetMemoryInfoSymbolSpace SymUsed, SymFree, SymMax MsgBox "The current memory information: " + Chr$(13)_ + "Handles Used = " + Format$(handlesUsed) + Chr$(13)_ + "Handles Free = " + Format$(handlesFree) + Chr$(13)_ + "Handles Max = " + Format$(handlesMax) + Chr$(13)_ + "String Space Used = " + Format$(ssUsed) + Chr$(13)_ + "String Space Free = " + Format$(ssFree) + Chr$(13)_ + "String Space Max = " + Format$(ssMax) + Chr$(13)_ + "Public Space Used = " + Format$(psUsed) + Chr$(13)_ + "Public Space Free = " + Format$(psFree) + Chr$(13)_ + "Public Space Max = " + Format$(psMax) + Chr$(13)_ + "Symbol Space Used = " + Format$(SymUsed) + Chr$(13)_ + "Symbol Space Free = " + Format$(SymFree) + Chr$(13)_ + "Symbol Space Max = " + Format$(SymMax) End Sub GE Digital 14

15 2.2.3 CIMPLICITY v9.5 SIM 1: Debounce Configuration Attributes DE17197 SF Starting in CIMPLICITY 9.5 SIM 1, a new command line parameter "/StripDebounce" has been added for CimEdit. Usage: CimEdit.exe /StripDebounce <ScreenPath.cim> Purpose: When CimEdit is launched with this command line parameter to open the screen path indicated by ScreenPath.cim, all the Debounce configuration from every event will be removed and the screen will be saved before exiting. This will result in events of the screen getting queued up while the previous event handler is still executing. GE Digital 15

16 2.3 CIMPLICITY OPTIONS CIMPLICITY v9.5 SIM 1: DEP Support US25570 Starting in CIMPLICITY 9.5 SIM 2, Users can choose to use either the DEP or the NoDEP version of CimEdit/CimView executable as per their requirements. 1. Enabling/Disabling DEP Version of CimEdit/CimView executable from CIMPLICITY Options: Under the "Security" Tab of CIMPLICITY Options, a new option has been added for enabling/disabling the use of DEP Version of CimEdit/CimView executable. GE Digital 16

17 Property Name Enable DEP Purpose Checked/Unchecked Comments Enable/Disable the use of DEP Version executable Checked [Default Option] Unchecked The DEP Enabled version of CimEdit/CimView will be copied to the exe sub-folder under CIMPLICITY Installation Folder. Note: When DEP is enabled, functional behavior (such as ActiveX controls that do not support DEP) will not work in CimEdit/CimView. The DEP Disabled version of CimEdit/CimView will be copied to the exe sub-folder under CIMPLICITY Installation Folder. Note:When DEP is disabled then functional behavior that does not support DEP (ActiveX controls that do not support DEP) will workd properly in CimEdit/CimView. 2. Enabling/Disabling DEP Version of CimEdit/CimView executable from Command Prompt: The "Enable DEP" option can be enabled from command line by using the options specified below: a. Use Startup.exe /EnableDEP command to Check the "Enable DEP" option. b. Use Startup.exe /DisableDEP command to Uncheck the "Enable DEP" option. GE Digital 17

18 2.4 EXPRESSION EDITOR ENHANCEMENTS DE18314 SF Starting in CIMPLICITY 9.5 SIM 3, the ability to allow projects to wait for proper shutdown of scripts has been added. As part of this enhancement, the following functionality has been included: Wait Time Configuration: Users can now configure a wait duration for which the forced termination of running scripts will be paused when the project is being shut down. EM_SCRIPT_TIMEOUT parameter can be set to the number of milliseconds to wait before the scripts that are running at the time of project shutdown, are terminated. Note: If the EM_SCRIPT_TIMEOUT value is not defined, the default time limit of 1000 milliseconds is used. Pre-Terminate Scripting Support: Users can now configure a pre-termination script and run it at the time of project shutdown. To do this: 1. Users must set RUN_PRE_TERM_SCRIPT global parameter to 'Y' or 'y'. 2. Create a new script "em_pre_term.bcl" for the project. When the above mentioned global parameter and script has been configured for the project, then at the time of project shutdown, the event manager will: a. Execute contents of "em_pre_term.bcl" script b. Wait for the time duration of 1000 milliseconds or the one specified in EM_SCRIPT_TIMEOUT parameter. c. Terminates any scripts that are still running at the end of wait duration. d. Executes contents of "em_term.bcl" script. GE Digital 18

19 2.5 OPC SERVER CIMPLICITY v9.5 SIM 17: Multiple Setpoint Support for Asynchronous Write Items US SF The CIMPLICITY OPC Server now provides multiple setpoint support to the Point Manager with a single request for all OPC client Asynchronous 2.0 Write Item operations. This improves performance and optimizes OPC client Asynchronous 2.0 group Write Item requests. The OPC client Asynchronous Write Item operation will fail if the duration of the response of the setpoint operation is more than the specified time-out value. The default time-out value is 2 seconds and is controlled by the WriteItemTimeout parameter in the CimOPCServer.xml file. This ensures that the OPC client and server function as expected when the response is delayed from the Point Manager. You can update the time-out value by modifying the following parameter: <serverparameters> <writeitemtimeout>enter time-out value in ms here</writeitemtimeout> </serverparameters> GE Digital 19

20 2.6 SCRIPTING AND OPEN INTERFACE CIMPLICITY v9.5 SIM 10: Disable Delete and Export Records options from Script DE39768 SF Starting SIM 10 for 9.5 Version, the ability to disable, via scripts, the option to export or delete database records. The details are as mentioned below: Users can now, from scripts, disable the option to delete database records. This can be done by calling the function DisableDeleteRecordsAction. Function Name Usage Syntax Description DisableDeleteRecordsActi on mytable.disabledeleterecordsacti on The call to CimTable.DisableDeleteRecordsActi on function from a script will provide the ability to disable delete records option configured as part of maintenance action. Users can now, from scripts, disable the option to export database records. This can be done by calling the function DisableExportRecordsAction. Function Name Usage Syntax Description DisableExportRecordsAction mytable.disableexportrecordsaction The call to CimTable.DisableExportRecord saction function from a script will provide the ability to disable export records option configured as part of maintenance action. Users can now, from scripts, access the current settings for Delete Record option by calling the GetDeleteRecordOptions function, which return a value of CimTableDeleteRecordEnum enumeration data type. Function/ Enumeration Name GetDeleteRecordOptions Description The call to GetDeleteRecordOptions function will return an enumerated value of CimTableDeleteRecordEnum type. CimTableDeleteRecordEnum Enumeration Value Description cimtableretainrecordnone cimtableretainrecordcount cimtableretainrecordtime The delete record option has been disabled. The delete record option retains records based on count. The delete record option retains records based on time. GE Digital 20

21 Users can now, from scripts, access the current settings for Export Record option by calling the GetExportRecordOptions function, which return a value of CimTableExportRecordEnum enumeration data type. Function/ Description Enumeration Name GetExportRecordOptions The call to GetExportRecordOptions function will return an enumerated value of CimTableExportRecordEnum type. CimTableExportRecordEnum Enumeration Value Description cimtableexportrecordnone cimtableexportrecordcount cimtableexportrecordtime cimtableexportrecordall The export record option has been disabled. The export record option has been set to be based on count. The export record option has been set to be based on time. The export record option has been set to export all records CIMPLICITY v9.5 SIM 7: Parameters for reloading.net Assemblies DE29003 SF EMRP.NET Scripts can call methods from external.net assemblies. When a script gets compiled, a DLL gets generated and is stored in Windows Temp Folder with a GUID Name and in the cache. Each time the project is executed, the DLL is loaded from the cache. If the DLL is not available in cache, then it is regenerated and is ensured to be available to EMRP Process when started. There were problems observed when the version of generated DLL that is available in cache is not matching the latest generated DLL. In order to resolve this issue, starting CIMPLICITY 9.5 SIM 7, the below mentioned global parameters have been added: Parameter Value Meaning Values/ Ranges EM_SCRIPT_RECOMPILE_ALWAYS EM_SCRIPT_COMPILE_WAIT Specifies if the script has to be forcefully recompiled on every project start Specifies the time to wait before proceeding to use the generated DLL. Y or y N or n.net Assemblies will be recompiled on every project start.net Assemblies will not be recompiled on every project start Default time to wait before loading scripts asynchronously Wait time Limits before loading scripts asynchronously GE Digital 21

22 2.6.3 CIMPLICITY v9.5 SIM 3: Enhancements to Historian Tag Timestamp DE18661 SF Starting CIMPLICITY 9.5 SIM 3, a new parameter "HIST_TIME_STAMP_TYPE" has been added to configure how Historian Tag Timestamp is processed from CIMPLICITY project. Parameter Value HIST_TIME_STAMP_TYPE Parameter not defined or expected value not specified for the parameter X Y Z Meaning CIMPLICITY Timestamp will be logged to Historian for every configured tag CIMPLICITY Timestamp is logged to Historian for every configured tag. Collector Timestamp is logged to Historian for every configured tag. Collector configurable default Timestamp is logged to Historian for every configured tag CIMPLICITY v9.5 SIM 3: DB Deadband Functions Deadband Functions Starting in CIMPLICITY 9.5 SIM 3, the following API calls have been added to the Configuration Object Model to enable assignment of deadband for data logging point conditions. DE18634; SF-NA DE18693; SF New methods and properties added to CIMBasic scripting are listed below: API Function Parameters Purpose EnableDataLogPtDeadBand Parameter Name Default Value Purpose <Point Name> Valid Point Name SetDataLogPtDeadBand <TRUE/FALSE> Parameter Name <Point Name> <Deadband Value> Default Value Valid Point Name The point for which the deadband value has to be enabled/ disabled Enables/ Disables deadband usage for specified point. Purpose The point for which deadband value has to be set The deadband value to be set for specified point Enable/ Disable Deadband option for the specified point. Set/ Get Deadband value for the specified point. GE Digital 22

23 API Function Parameters Purpose SetDataLogPtDeadBandType Parameter Name Default Value Purpose <Point Name> Valid The point for Point which deadband Name type has to be set <Deadband Type> The type of deadband to be set for the specified point Set/ Get Deadband type for the specified point. GE Digital 23

24 Sample Script Sample script for newly added APIs Example Sub Main() Dim project as CimProject set project = CreateObject("CimProject") project.openlocalproject "C:\Program Files (x86)\proficy\proficy CIMPLICITY\projects\mydemo\MYDEMO.GEF" Dim database as CimDatabase Set database = project.database Set datatable = database.gettable("data_log") datatable.addloggedpoint "POINT1" 'Enable/Disable databand datatable.enabledatalogptdeadband "POINT1", True x = datatable.isdatalogptdeadbandenabled("point1") 'Set/Get Deadband Value datatable.setdatalogptdeadband "POINT1", 10 x = datatable.getdatalogptdeadband("point1") 'Set/Get Deadband type datatable.setdatalogptdeadbandtype "POINT1", cimdbdatalogdeadbandabsolute x = datatable.getdatalogptdeadbandtype("point1") End Sub CIMPLICITY v9.5 SIM 2: Enhancements to Point Management Script Functions String Functions Starting in CIMPLICITY 9.5 SIM 2, a new function has been added to allow the timestamp of a Derived Point to be set at runtime via scripting. This function will add the ability to update timestamps of derived points with the timestamp of the result of an expression evaluation. New methods and properties added to CIMBasic scripting are listed below: Properties: Point.TimeStampUTC Methods: Point.SetTimeStampHR GetTimeComponentsHR_UTC SetTimeFromComponentsHR_UTC PointUpdateMultiple New methods and properties added to.net scripting are listed below: Methods: CIMPLICITY.PointUpdateMultiple Point.TimeStampUTC GE Digital 24

25 Point.TimeStampUTC is a read/write property. This property can be used to retrieve/store the timestamp into a Basic Date Object. The timestamp (in UTC format) indicates the time at which the point's value was read from the PLC. Note: The Date value stored in this variable is the based on UTC Value. Syntax Point.TimeStampUTC Example Sub Main() Dim x as new Point a$ = InputBox$("Enter a point id") x.id = a$ x.onchange top : x.getnext Trace str$(x.timestamputc) & " " & x.value goto top End Sub Point.SetTimeStampHR Point.SetTimeStampHR method can be used to set the High Resolution Time Stamp value for the point. Syntax: Point.SetTimeStampHR dbltimehigh, dbltimelow Parameter Description dbltimehigh Double, High Value of the Time Stamp dbltimelow Double, Low Value of the Time Stamp Example Sub Main() Dim pt1 As New point Dim pt2 As New point Dim pt3 As New point pt1.id = "gg" pt2.id = "test" pt3.id = "timeval" Dim result As Boolean Dim yy As Integer Dim mm As Integer Dim dd As Integer Dim hh As Integer Dim min As Integer Dim sec As Integer Dim nano As Long Dim qlow As Double Dim qhigh As Double Dim qlowo As Double Dim qhigho As Double 'Initialize Objects yy = 2016 mm = 9 dd = 15 hh = 23 GE Digital 25

26 min = 59 sec = 59 nano = SetTimeFromComponentsHR qlow, qhigh,yy,mm,dd,hh,min,sec,nano pt1.value = 60 pt1.settimestamphr qhigh, qlow result = pt1.gettimestamphr(qhigho, qlowo) pt3.settimestamphr qhigho, qlowo result = pt3.setquadintvalue(qhigh, qlow) pt2.value = "Fred" Dim timestamp As Date timestamp = DateSerial(yy, mm, dd) + TimeSerial(hh, min, sec) pt2.timestamputc = timestamp Dim points(3) As Point Set points(0) = pt1 Set points(1) = pt2 Set points(2) = pt3 result = PointUpdateMultiple(points) 'The PointUpdateMultiple failed probably because its an application process. 'Do a setpoint instead If result = FALSE Then result = PointSetMultiple(points) End If End Sub GetTimeComponentsHR_UTC GetTimeComponentsHR_UTC method can be used to get the Time Stamp of the point from High Resolution components in UTC Format. Syntax: GetTimeComponentsHR_UTC dbltimehigh,dbltimelow,yyyy,mm, dd, hh, mm, sec,nano Parameter Description dbltimehigh Double, High Value of the Time Stamp dbltimelow Double, Low Value of the Time Stamp yyyy The year, in the range mm The month, in the range dd The day of the month hh The hour, specified as a 24-hour clock. mm Minutes past the hour, in the range sec Seconds, in the range nano Fractional seconds, specified in Nano seconds. SetTimeFromComponentsHR_UTC SetTimeFromComponentsHR_UTC method can be used to set the Time Stamp for the point from High Resolution components in UTC Format. GE Digital 26

27 Syntax: SetTimeFromComponentsHR_UTC dbltimehigh,dbltimelow,yy,mm, dd, hh, min, sec,nano Parameter Description dbltimehigh Double, High Value of the Time Stamp dbltimelow Double, Low Value of the Time Stamp yyyy The year, in the range mm The month, in the range dd The day of the month hh The hour, specified as a 24-hour clock. mm The hour, specified as a 24-hour clock. sec Seconds, in the range nano Fractional seconds, specified in Nano seconds. Example Sub Main() Dim pt1 As New point Dim pt2 As New point Dim pt3 As New point pt1.id = "gg" pt2.id = "test" pt3.id = "timeval" Dim result As Boolean Dim yy As Integer Dim mm As Integer Dim dd As Integer Dim hh As Integer Dim min As Integer Dim sec As Integer Dim nano As Long Dim qlow As Double Dim qhigh As Double Dim qlowo As Double Dim qhigho As Double 'Initialize Objects yy = 2016 mm = 9 dd = 15 hh = 23 min = 59 sec = 59 nano = SetTimeFromComponentsHR_UTC qlow, qhigh, yy,mm, dd, hh, min, sec, nano pt1.value = 60 pt1.settimestamphr qhigh, qlow result = pt1.gettimestamphr(qhigho, qlowo) pt3.settimestamphr qhigho, qlowo result = pt3.setquadintvalue(qhigh, qlow) pt2.value = "Fred" GE Digital 27

28 Dim timestamp As Date timestamp = DateSerial(yy, mm, dd) + TimeSerial(hh, min, sec) pt2.timestamputc = timestamp Dim points(3) As Point Set points(0) = pt1 Set points(1) = pt2 Set points(2) = pt3 result = PointUpdateMultiple(points) 'The PointUpdateMultiple failed probably because its an application process. 'Do a setpoint instead If result = FALSE Then result = PointSetMultiple(points) End If End Sub PointUpdateMultiple PointUpdateMultiple method can be used to perform Point Update operation on multiple points that are passed in the Array of Point Objects. Note: 1. A point update will also update the time stamp of the point using the TimeStampUTC set on the point object. A normal SetPoint operation uses the current time for the timestamp. 2. The PointUpdateMultiple function: a. Is only callable from EMRP. If it is called from another application it will return false, and log an error message. b. Can be used only for Global Points. c. Will not work with Safety Point. Syntax: PointUpdateMultiple arrayofpointobjects Example 1 Sub Main Dim opointobj As Point Dim opointarray(6) As Point Dim bresult As Boolean Set opointobj = New Point opointobj.id = "A1" opointobj.value = 22 opointobj.timestamputc = CDate( ) Set opointarray(0) = opointobj Set opointobj = New Point opointobj.id = "A2" opointobj.value = 33 opointobj.timestamputc = CDate( ) Set opointarray(1) = opointobj Set opointobj = New Point opointobj.id = "A3" GE Digital 28

29 opointobj.value = 44 opointobj.timestamputc = CDate( ) Set opointarray(2) = opointobj Set opointobj = New Point opointobj.id = "A4" opointobj.value = 55 opointobj.timestamputc = CDate( ) Set opointarray(3) = opointobj Set opointobj = New Point opointobj.id = "A5" opointobj.value = 66 opointobj.timestamputc = CDate( ) Set opointarray(4) = opointobj bresult = PointUpdateMultiple(oPointArray) End Sub Example 2 Sub Main() Dim pt1 As New point Dim pt2 As New point Dim pt3 As New point pt1.id = "gg" pt2.id = "test" pt3.id = "timeval" Dim result As Boolean Dim yy As Integer Dim mm As Integer Dim dd As Integer Dim hh As Integer Dim min As Integer Dim sec As Integer Dim nano As Long Dim qlow As Double Dim qhigh As Double Dim qlowo As Double Dim qhigho As Double 'Initialize Objects yy = 2016 mm = 9 dd = 15 hh = 23 min = 59 sec = 59 nano = SetTimeFromComponentsHR qlow, qhigh,yy,mm,dd,hh,min,sec,nano pt1.value = 60 pt1.settimestamphr qhigh, qlow result = pt1.gettimestamphr(qhigho, qlowo) pt3.settimestamphr qhigho, qlowo GE Digital 29

30 result = pt3.setquadintvalue(qhigh, qlow) pt2.value = "Fred" Dim timestamp As Date timestamp = DateSerial(yy, mm, dd) + TimeSerial(hh, min, sec) pt2.timestamputc = timestamp Dim points(3) As Point Set points(0) = pt1 Set points(1) = pt2 Set points(2) = pt3 result = PointUpdateMultiple(points) 'The PointUpdateMultiple failed probably because its an application process. 'Do a setpoint instead If result = FALSE Then result = PointSetMultiple(points) End If End Sub CIMPLICITY.PointUpdateMultiple CIMPLICITY.PointUpdateMultiple method can be used to perform Point Update operation on multiple points that are passed in the Array of Point Objects. Note: 3. A point update will also update the time stamp of the point using the TimeStampUTC set on the point object. A normal SetPoint operation uses the current time for the timestamp. 4. The CIMPLICITY.PointUpdateMultiple function: a. Is only callable from EMRP. If it is called from another application it will return false, and log an error message. b. Can be used only for Global Points. c. Will not work with Safety Point. Syntax: CIMPLICITY.PointUpdateMultiple arrayofpointobjects Example using System; using System.Collections.Generic; using Proficy.CIMPLICITY; public class PointUpdateMultiple { public void Main() { int status; Point[] array = new Point[2]; DateTime date1 = new DateTime(2014, 9, 15, 7, 30, 12, 123, DateTimeKind.Local); date1 = date1.addticks(4560); using (Point sp1 = new Point(),sp2 = new Point()) { sp1.id = "gg"; sp2.id = "test"; GE Digital 30

31 array[0] = sp1; array[1] = sp2; sp1.value = 60; sp2.value = "Fred.Net"; sp1.timestamp = date1; sp2.timestamp = date1; } } } status = Cimplicity.PointUpdateMultiple(array); GE Digital 31

32 2.7 TRACKER CIMPLICITY v9.5 SIM 15: Security enhancements for Tracker SQL Database US DE73513 DE73512; SF When installing Tracker and updating the database, the SQL Scripts now disable the Show Advanced options and Ad-Hoc Distributed Queries options that they enabled. This eliminates any security risk that could have been caused if the options remained enabled. GE Digital 32

33 2.8 TRENDS AND DGR CIMPLICITY v9.5 SIM 10: Timezone Support for Trend Control US Starting SIM 10 for 9.5 Version, the ability to use Timezone support in the trend control has been added to CIMPLICITY. The Timezone setting can be done for a trend control by using the SetTimeZone function. The SetTimeZone is a method for a Trend Invoke method action. Purpose Sets the time zone to the trend control and displays the data based on the selected time zone. Input TimeZone Index enumeration published as part of Trend.ocx type library. Return Value Boolean: True or False Index Published Enumeration List Trend Type Library - TREND_TIME_ZONE_INFO 0 TREND_TZ_SYSTEM_DEFAULT 1 TREND_TZ_AFGHANISTAN_STANDARD_TIME 2 TREND_TZ_ALASKAN_STANDARD_TIME 3 TREND_TZ_ALEUTIAN_STANDARD_TIME 4 TREND_TZ_ALTAI_STANDARD_TIME 5 TREND_TZ_ARAB_STANDARD_TIME 6 TREND_TZ_ARABIAN_STANDARD_TIME 7 TREND_TZ_ARABIC_STANDARD_TIME 8 TREND_TZ_ARGENTINA_STANDARD_TIME 9 TREND_TZ_ASTRAKHAN_STANDARD_TIME 10 TREND_TZ_ATLANTIC_STANDARD_TIME 11 TREND_TZ_AUS_CENTRAL_STANDARD_TIME 12 TREND_TZ_AUS_CENTRAL_W_STANDARD_TIME 13 TREND_TZ_AUS_EASTERN_STANDARD_TIME 14 TREND_TZ_AZERBAIJAN_STANDARD_TIME 15 TREND_TZ_AZORES_STANDARD_TIME 16 TREND_TZ_BAHIA_STANDARD_TIME 17 TREND_TZ_BANGLADESH_STANDARD_TIME 18 TREND_TZ_BELARUS_STANDARD_TIME 19 TREND_TZ_BOUGAINVILLE_STANDARD_TIME 20 TREND_TZ_CANADA_CENTRAL_STANDARD_TIME 21 TREND_TZ_CAPE_VERDE_STANDARD_TIME 22 TREND_TZ_CAUCASUS_STANDARD_TIME 23 TREND_TZ_CEN_AUSTRALIA_STANDARD_TIME 24 TREND_TZ_CENTRAL_AMERICA_STANDARD_TIME 25 TREND_TZ_CENTRAL_ASIA_STANDARD_TIME 26 TREND_TZ_CENTRAL_BRAZILIAN_STANDARD_TIME 27 TREND_TZ_CENTRAL_EUROPE_STANDARD_TIME 28 TREND_TZ_CENTRAL_EUROPEAN_STANDARD_TIME 29 TREND_TZ_CENTRAL_PACIFIC_STANDARD_TIME 30 TREND_TZ_CENTRAL_STANDARD_TIME 31 TREND_TZ_CENTRAL_STANDARD_TIME_MEXICO GE Digital 33

34 Index Published Enumeration List Trend Type Library - TREND_TIME_ZONE_INFO 32 TREND_TZ_CHATHAM_ISLANDS_STANDARD_TIME 33 TREND_TZ_CHINA_STANDARD_TIME 34 TREND_TZ_CUBA_STANDARD_TIME 35 TREND_TZ_DATELINE_STANDARD_TIME 36 TREND_TZ_E_AFRICA_STANDARD_TIME 37 TREND_TZ_E_AUSTRALIA_STANDARD_TIME 38 TREND_TZ_E_EUROPE_STANDARD_TIME 39 TREND_TZ_E_SOUTH_AMERICA_STANDARD_TIME 40 TREND_TZ_EASTER_ISLAND_STANDARD_TIME 41 TREND_TZ_EASTERN_STANDARD_TIME 42 TREND_TZ_EASTERN_STANDARD_TIME_MEXICO 43 TREND_TZ_EGYPT_STANDARD_TIME 44 TREND_TZ_EKATERINBURG_STANDARD_TIME 45 TREND_TZ_FIJI_STANDARD_TIME 46 TREND_TZ_FLE_STANDARD_TIME 47 TREND_TZ_GEORGIAN_STANDARD_TIME 48 TREND_TZ_GMT_STANDARD_TIME 49 TREND_TZ_GREENLAND_STANDARD_TIME 50 TREND_TZ_GREENWICH_STANDARD_TIME 51 TREND_TZ_GTB_STANDARD_TIME 52 TREND_TZ_HAITI_STANDARD_TIME 53 TREND_TZ_HAWAIIAN_STANDARD_TIME 54 TREND_TZ_INDIA_STANDARD_TIME 55 TREND_TZ_IRAN_STANDARD_TIME 56 TREND_TZ_ISRAEL_STANDARD_TIME 57 TREND_TZ_JORDAN_STANDARD_TIME 58 TREND_TZ_KALININGRAD_STANDARD_TIME 59 TREND_TZ_KAMCHATKA_STANDARD_TIME 60 TREND_TZ_KOREA_STANDARD_TIME 61 TREND_TZ_LIBYA_STANDARD_TIME 62 TREND_TZ_LINE_ISLANDS_STANDARD_TIME 63 TREND_TZ_LORD_HOWE_STANDARD_TIME 64 TREND_TZ_MAGADAN_STANDARD_TIME 65 TREND_TZ_MAGALLANES_STANDARD_TIME 66 TREND_TZ_MARQUESAS_STANDARD_TIME 67 TREND_TZ_MAURITIUS_STANDARD_TIME 68 TREND_TZ_MID_ATLANTIC_STANDARD_TIME 69 TREND_TZ_MIDDLE_EAST_STANDARD_TIME 70 TREND_TZ_MONTEVIDEO_STANDARD_TIME 71 TREND_TZ_MOROCCO_STANDARD_TIME 72 TREND_TZ_MOUNTAIN_STANDARD_TIME 73 TREND_TZ_MOUNTAIN_STANDARD_TIME_MEXICO 74 TREND_TZ_MYANMAR_STANDARD_TIME 75 TREND_TZ_N_CENTRAL_ASIA_STANDARD_TIME 76 TREND_TZ_NAMIBIA_STANDARD_TIME 77 TREND_TZ_NEPAL_STANDARD_TIME 78 TREND_TZ_NEW_ZEALAND_STANDARD_TIME 79 TREND_TZ_NEWFOUNDLAND_STANDARD_TIME 80 TREND_TZ_NORFOLK_STANDARD_TIME 81 TREND_TZ_NORTH_ASIA_EAST_STANDARD_TIME 82 TREND_TZ_NORTH_ASIA_STANDARD_TIME GE Digital 34

35 Index Published Enumeration List Trend Type Library - TREND_TIME_ZONE_INFO 83 TREND_TZ_NORTH_KOREA_STANDARD_TIME 84 TREND_TZ_OMSK_STANDARD_TIME 85 TREND_TZ_PACIFIC_SA_STANDARD_TIME 86 TREND_TZ_PACIFIC_STANDARD_TIME 87 TREND_TZ_PACIFIC_STANDARD_TIME_MEXICO 88 TREND_TZ_PAKISTAN_STANDARD_TIME 89 TREND_TZ_PARAGUAY_STANDARD_TIME 90 TREND_TZ_ROMANCE_STANDARD_TIME 91 TREND_TZ_RUSSIA_TIME_ZONE_10 92 TREND_TZ_RUSSIA_TIME_ZONE_11 93 TREND_TZ_RUSSIA_TIME_ZONE_3 94 TREND_TZ_RUSSIAN_STANDARD_TIME 95 TREND_TZ_SA_EASTERN_STANDARD_TIME 96 TREND_TZ_SA_PACIFIC_STANDARD_TIME 97 TREND_TZ_SA_WESTERN_STANDARD_TIME 98 TREND_TZ_SAINT_PIERRE_STANDARD_TIME 99 TREND_TZ_SAKHALIN_STANDARD_TIME 100 TREND_TZ_SAMOA_STANDARD_TIME 101 TREND_TZ_SARATOV_STANDARD_TIME 102 TREND_TZ_SE_ASIA_STANDARD_TIME 103 TREND_TZ_SINGAPORE_STANDARD_TIME 104 TREND_TZ_SOUTH_AFRICA_STANDARD_TIME 105 TREND_TZ_SRI_LANKA_STANDARD_TIME 106 TREND_TZ_SYRIA_STANDARD_TIME 107 TREND_TZ_TAIPEI_STANDARD_TIME 108 TREND_TZ_TASMANIA_STANDARD_TIME 109 TREND_TZ_TOCANTINS_STANDARD_TIME 110 TREND_TZ_TOKYO_STANDARD_TIME 111 TREND_TZ_TOMSK_STANDARD_TIME 112 TREND_TZ_TONGA_STANDARD_TIME 113 TREND_TZ_TRANSBAIKAL_STANDARD_TIME 114 TREND_TZ_TURKEY_STANDARD_TIME 115 TREND_TZ_TURKS_AND_CAICOS_STANDARD_TIME 116 TREND_TZ_ULAANBAATAR_STANDARD_TIME 117 TREND_TZ_US_EASTERN_STANDARD_TIME 118 TREND_TZ_US_MOUNTAIN_STANDARD_TIME 119 TREND_TZ_UTC 120 TREND_TZ_UTC_PLUS_ TREND_TZ_UTC_PLUS_ TREND_TZ_UTC_MINUS_ TREND_TZ_UTC_MINUS_ TREND_TZ_UTC_MINUS_ TREND_TZ_UTC_MINUS_ TREND_TZ_VENEZUELA_STANDARD_TIME 127 TREND_TZ_VLADIVOSTOK_STANDARD_TIME 128 TREND_TZ_W_AUSTRALIA_STANDARD_TIME 129 TREND_TZ_W_CENTRAL_AFRICA_STANDARD_TIME 130 TREND_TZ_W_EUROPE_STANDARD_TIME 131 TREND_TZ_W_MONGOLIA_STANDARD_TIME 132 TREND_TZ_WEST_ASIA_STANDARD_TIME 133 TREND_TZ_WEST_BANK_STANDARD_TIME GE Digital 35

36 Index Published Enumeration List Trend Type Library - TREND_TIME_ZONE_INFO 134 TREND_TZ_WEST_PACIFIC_STANDARD_TIME 135 TREND_TZ_YAKUTSK_STANDARD_TIME Sample Code Dim otrend As TrendLib.ITrend Dim bret As Boolean Set otrend = CimGetScreen.Object.Objects.Item("Trend1").OLEObject bret = otrend.settimezone(trend_tz_india_standard_time) Or bret = otrend.settimezone(54) Basic Script Methods 1. SetTimeComponentsHR_Ex (param1, param2 10) Purpose: Given components of the time based on Time zone. Current time divided into time components of year, month, day, hour, min, sec and nanoseconds. Param1 Double Low value of input time Param2 Double High value of input time Param3 Integer Timecomponent Param4 Integer Timecomponent Param5 Integer Timecomponent Param6 Integer Timecomponent Param7 Integer Timecomponent Param8 Integer Timecomponent Param9 Long Nanosecond time component Param10 Integer TimeZoneIndex Where Time Zone Index can be either Trend Lib TREND_TIME_ZONE_INFO (If there is a CimView screen reference to the trend.ocx file) or an index number in the list below: Index Enumeration 0 COR_CIMP_SYSTEM_DEFAULT 1 COR_CIMP_AFGHANISTAN_STANDARD_TIME 2 COR_CIMP_ALASKAN_STANDARD_TIME 3 COR_CIMP_ALEUTIAN_STANDARD_TIME 4 COR_CIMP_ALTAI_STANDARD_TIME 5 COR_CIMP_ARAB_STANDARD_TIME 6 COR_CIMP_ARABIAN_STANDARD_TIME 7 COR_CIMP_ARABIC_STANDARD_TIME 8 COR_CIMP_ARGENTINA_STANDARD_TIME 9 COR_CIMP_ASTRAKHAN_STANDARD_TIME 10 COR_CIMP_ATLANTIC_STANDARD_TIME 11 COR_CIMP_AUS_CENTRAL_STANDARD_TIME 12 COR_CIMP_AUS_CENTRAL_W_STANDARD_TIME 13 COR_CIMP_AUS_EASTERN_STANDARD_TIME 14 COR_CIMP_AZERBAIJAN_STANDARD_TIME 15 COR_CIMP_AZORES_STANDARD_TIME GE Digital 36

37 Index Enumeration 16 COR_CIMP_BAHIA_STANDARD_TIME 17 COR_CIMP_BANGLADESH_STANDARD_TIME 18 COR_CIMP_BELARUS_STANDARD_TIME 19 COR_CIMP_BOUGAINVILLE_STANDARD_TIME 20 COR_CIMP_CANADA_CENTRAL_STANDARD_TIME 21 COR_CIMP_CAPE_VERDE_STANDARD_TIME 22 COR_CIMP_CAUCASUS_STANDARD_TIME 23 COR_CIMP_CEN_AUSTRALIA_STANDARD_TIME 24 COR_CIMP_CENTRAL_AMERICA_STANDARD_TIME 25 COR_CIMP_CENTRAL_ASIA_STANDARD_TIME 26 COR_CIMP_CENTRAL_BRAZILIAN_STANDARD_TIME 27 COR_CIMP_CENTRAL_EUROPE_STANDARD_TIME 28 COR_CIMP_CENTRAL_EUROPEAN_STANDARD_TIME 29 COR_CIMP_CENTRAL_PACIFIC_STANDARD_TIME 30 COR_CIMP_CENTRAL_STANDARD_TIME 31 COR_CIMP_CENTRAL_STANDARD_TIME_MEXICO 32 COR_CIMP_CHATHAM_ISLANDS_STANDARD_TIME 33 COR_CIMP_CHINA_STANDARD_TIME 34 COR_CIMP_CUBA_STANDARD_TIME 35 COR_CIMP_DATELINE_STANDARD_TIME 36 COR_CIMP_E_AFRICA_STANDARD_TIME 37 COR_CIMP_E_AUSTRALIA_STANDARD_TIME 38 COR_CIMP_E_EUROPE_STANDARD_TIME 39 COR_CIMP_E_SOUTH_AMERICA_STANDARD_TIME 40 COR_CIMP_EASTER_ISLAND_STANDARD_TIME 41 COR_CIMP_EASTERN_STANDARD_TIME 42 COR_CIMP_EASTERN_STANDARD_TIME_MEXICO 43 COR_CIMP_EGYPT_STANDARD_TIME 44 COR_CIMP_EKATERINBURG_STANDARD_TIME 45 COR_CIMP_FIJI_STANDARD_TIME 46 COR_CIMP_FLE_STANDARD_TIME 47 COR_CIMP_GEORGIAN_STANDARD_TIME 48 COR_CIMP_GMT_STANDARD_TIME 49 COR_CIMP_GREENLAND_STANDARD_TIME 50 COR_CIMP_GREENWICH_STANDARD_TIME 51 COR_CIMP_GTB_STANDARD_TIME 52 COR_CIMP_HAITI_STANDARD_TIME 53 COR_CIMP_HAWAIIAN_STANDARD_TIME 54 COR_CIMP_INDIA_STANDARD_TIME 55 COR_CIMP_IRAN_STANDARD_TIME 56 COR_CIMP_ISRAEL_STANDARD_TIME 57 COR_CIMP_JORDAN_STANDARD_TIME 58 COR_CIMP_KALININGRAD_STANDARD_TIME 59 COR_CIMP_KAMCHATKA_STANDARD_TIME 60 COR_CIMP_KOREA_STANDARD_TIME 61 COR_CIMP_LIBYA_STANDARD_TIME 62 COR_CIMP_LINE_ISLANDS_STANDARD_TIME 63 COR_CIMP_LORD_HOWE_STANDARD_TIME 64 COR_CIMP_MAGADAN_STANDARD_TIME 65 COR_CIMP_MAGALLANES_STANDARD_TIME 66 COR_CIMP_MARQUESAS_STANDARD_TIME 67 COR_CIMP_MAURITIUS_STANDARD_TIME GE Digital 37

38 Index Enumeration 68 COR_CIMP_MID_ATLANTIC_STANDARD_TIME 69 COR_CIMP_MIDDLE_EAST_STANDARD_TIME 70 COR_CIMP_MONTEVIDEO_STANDARD_TIME 71 COR_CIMP_MOROCCO_STANDARD_TIME 72 COR_CIMP_MOUNTAIN_STANDARD_TIME 73 COR_CIMP_MOUNTAIN_STANDARD_TIME_MEXICO 74 COR_CIMP_MYANMAR_STANDARD_TIME 75 COR_CIMP_N_CENTRAL_ASIA_STANDARD_TIME 76 COR_CIMP_NAMIBIA_STANDARD_TIME 77 COR_CIMP_NEPAL_STANDARD_TIME 78 COR_CIMP_NEW_ZEALAND_STANDARD_TIME 79 COR_CIMP_NEWFOUNDLAND_STANDARD_TIME 80 COR_CIMP_NORFOLK_STANDARD_TIME 81 COR_CIMP_NORTH_ASIA_EAST_STANDARD_TIME 82 COR_CIMP_NORTH_ASIA_STANDARD_TIME 83 COR_CIMP_NORTH_KOREA_STANDARD_TIME 84 COR_CIMP_OMSK_STANDARD_TIME 85 COR_CIMP_PACIFIC_SA_STANDARD_TIME 86 COR_CIMP_PACIFIC_STANDARD_TIME 87 COR_CIMP_PACIFIC_STANDARD_TIME_MEXICO 88 COR_CIMP_PAKISTAN_STANDARD_TIME 89 COR_CIMP_PARAGUAY_STANDARD_TIME 90 COR_CIMP_ROMANCE_STANDARD_TIME 91 COR_CIMP_RUSSIA_TIME_ZONE_10 92 COR_CIMP_RUSSIA_TIME_ZONE_11 93 COR_CIMP_RUSSIA_TIME_ZONE_3 94 COR_CIMP_RUSSIAN_STANDARD_TIME 95 COR_CIMP_SA_EASTERN_STANDARD_TIME 96 COR_CIMP_SA_PACIFIC_STANDARD_TIME 97 COR_CIMP_SA_WESTERN_STANDARD_TIME 98 COR_CIMP_SAINT_PIERRE_STANDARD_TIME 99 COR_CIMP_SAKHALIN_STANDARD_TIME 100 COR_CIMP_SAMOA_STANDARD_TIME 101 COR_CIMP_SARATOV_STANDARD_TIME 102 COR_CIMP_SE_ASIA_STANDARD_TIME 103 COR_CIMP_SINGAPORE_STANDARD_TIME 104 COR_CIMP_SOUTH_AFRICA_STANDARD_TIME 105 COR_CIMP_SRI_LANKA_STANDARD_TIME 106 COR_CIMP_SYRIA_STANDARD_TIME 107 COR_CIMP_TAIPEI_STANDARD_TIME 108 COR_CIMP_TASMANIA_STANDARD_TIME 109 COR_CIMP_TOCANTINS_STANDARD_TIME 110 COR_CIMP_TOKYO_STANDARD_TIME 111 COR_CIMP_TOMSK_STANDARD_TIME 112 COR_CIMP_TONGA_STANDARD_TIME 113 COR_CIMP_TRANSBAIKAL_STANDARD_TIME 114 COR_CIMP_TURKEY_STANDARD_TIME 115 COR_CIMP_TURKS_AND_CAICOS_STANDARD_TIME 116 COR_CIMP_ULAANBAATAR_STANDARD_TIME 117 COR_CIMP_US_EASTERN_STANDARD_TIME 118 COR_CIMP_US_MOUNTAIN_STANDARD_TIME 119 COR_CIMP_UTC GE Digital 38

39 Index Enumeration 120 COR_CIMP_UTC_PLUS_ COR_CIMP_UTC_PLUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_VENEZUELA_STANDARD_TIME 127 COR_CIMP_VLADIVOSTOK_STANDARD_TIME 128 COR_CIMP_W_AUSTRALIA_STANDARD_TIME 129 COR_CIMP_W_CENTRAL_AFRICA_STANDARD_TIME 130 COR_CIMP_W_EUROPE_STANDARD_TIME 131 COR_CIMP_W_MONGOLIA_STANDARD_TIME 132 COR_CIMP_WEST_ASIA_STANDARD_TIME 133 COR_CIMP_WEST_BANK_STANDARD_TIME 134 COR_CIMP_WEST_PACIFIC_STANDARD_TIME 135 COR_CIMP_YAKUTSK_STANDARD_TIME Sample Code Dim yy As Integer Dim mon As Integer Dim dd As Integer Dim hh As Integer Dim min As Integer Dim sec As Integer Dim nano As Long Dim qlow As Double Dim qhigh As Double Legend: yy = 2017 mon = 10 dd = 13 hh = 15 min = 00 sec = 0 nano = 0 SetTimeFromComponentsHR_Ex qlow,qhigh,yy,mon,dd,hh,min,sec,nano,trend_tz_korea_standard_time Or SetTimeFromComponentsHR_Ex qlow,qhigh,yy,mon,dd,hh,min,sec,nano,60 GE Digital 39

40 2. SetTimecomponentHR() (param1, param2 10) Param1 Param2 Param3 Param4 Param5 Param6 Param7 Param8 Double Low value of input time Double High value of input time Integer Timecomponent Integer Timecomponent Integer Timecomponent Integer Timecomponent Integer Timecomponent Integer Timecomponent Param9 Long Nanosecond time component Param10 Integer TimeZoneIndex Sub OnMouseUp (x As Long, y As Logn, flags As Long) Declare variables: Dim yy As Integer Dim mm As Integer Dim dd As Integer Dim hh As Integer Dim min As Integer Dim sec As Integer Dim nano As Long Dim qlow As Double Dim qhigh As Double Legend: yy = 2017 mon = 7 dd = 13 hh = 21 min = 43 sec = 10 nano = 0 SetTimeFromComponentsHR qlow,qhigh,yy,mm,dd,hh,min,sec,nano MsgBox qhigh MsgBox qlow GE Digital 40

41 3. GetLocalDateAdjustedToTimeZone Purpose: Convert the local time to specified time zone. Inputs Year Month Day Hour Minutes Seconds Milliseconds TimeZoneIndex Data Type Integer Integer Integer Integer Integer Integer Long Integer Returns Adjusted Time Date Data Type Date Where Time Zone Index can be either Trend Lib TREND_TIME_ZONE_INFO (If there is a CimView screen reference to the trend.ocx file) or an index number in the list below: Index Enumeration 0 COR_CIMP_SYSTEM_DEFAULT 1 COR_CIMP_AFGHANISTAN_STANDARD_TIME 2 COR_CIMP_ALASKAN_STANDARD_TIME 3 COR_CIMP_ALEUTIAN_STANDARD_TIME 4 COR_CIMP_ALTAI_STANDARD_TIME 5 COR_CIMP_ARAB_STANDARD_TIME 6 COR_CIMP_ARABIAN_STANDARD_TIME 7 COR_CIMP_ARABIC_STANDARD_TIME 8 COR_CIMP_ARGENTINA_STANDARD_TIME 9 COR_CIMP_ASTRAKHAN_STANDARD_TIME 10 COR_CIMP_ATLANTIC_STANDARD_TIME 11 COR_CIMP_AUS_CENTRAL_STANDARD_TIME 12 COR_CIMP_AUS_CENTRAL_W_STANDARD_TIME 13 COR_CIMP_AUS_EASTERN_STANDARD_TIME 14 COR_CIMP_AZERBAIJAN_STANDARD_TIME 15 COR_CIMP_AZORES_STANDARD_TIME 16 COR_CIMP_BAHIA_STANDARD_TIME 17 COR_CIMP_BANGLADESH_STANDARD_TIME 18 COR_CIMP_BELARUS_STANDARD_TIME 19 COR_CIMP_BOUGAINVILLE_STANDARD_TIME 20 COR_CIMP_CANADA_CENTRAL_STANDARD_TIME 21 COR_CIMP_CAPE_VERDE_STANDARD_TIME 22 COR_CIMP_CAUCASUS_STANDARD_TIME 23 COR_CIMP_CEN_AUSTRALIA_STANDARD_TIME 24 COR_CIMP_CENTRAL_AMERICA_STANDARD_TIME 25 COR_CIMP_CENTRAL_ASIA_STANDARD_TIME 26 COR_CIMP_CENTRAL_BRAZILIAN_STANDARD_TIME 27 COR_CIMP_CENTRAL_EUROPE_STANDARD_TIME 28 COR_CIMP_CENTRAL_EUROPEAN_STANDARD_TIME 29 COR_CIMP_CENTRAL_PACIFIC_STANDARD_TIME 30 COR_CIMP_CENTRAL_STANDARD_TIME GE Digital 41

42 Index Enumeration 31 COR_CIMP_CENTRAL_STANDARD_TIME_MEXICO 32 COR_CIMP_CHATHAM_ISLANDS_STANDARD_TIME 33 COR_CIMP_CHINA_STANDARD_TIME 34 COR_CIMP_CUBA_STANDARD_TIME 35 COR_CIMP_DATELINE_STANDARD_TIME 36 COR_CIMP_E_AFRICA_STANDARD_TIME 37 COR_CIMP_E_AUSTRALIA_STANDARD_TIME 38 COR_CIMP_E_EUROPE_STANDARD_TIME 39 COR_CIMP_E_SOUTH_AMERICA_STANDARD_TIME 40 COR_CIMP_EASTER_ISLAND_STANDARD_TIME 41 COR_CIMP_EASTERN_STANDARD_TIME 42 COR_CIMP_EASTERN_STANDARD_TIME_MEXICO 43 COR_CIMP_EGYPT_STANDARD_TIME 44 COR_CIMP_EKATERINBURG_STANDARD_TIME 45 COR_CIMP_FIJI_STANDARD_TIME 46 COR_CIMP_FLE_STANDARD_TIME 47 COR_CIMP_GEORGIAN_STANDARD_TIME 48 COR_CIMP_GMT_STANDARD_TIME 49 COR_CIMP_GREENLAND_STANDARD_TIME 50 COR_CIMP_GREENWICH_STANDARD_TIME 51 COR_CIMP_GTB_STANDARD_TIME 52 COR_CIMP_HAITI_STANDARD_TIME 53 COR_CIMP_HAWAIIAN_STANDARD_TIME 54 COR_CIMP_INDIA_STANDARD_TIME 55 COR_CIMP_IRAN_STANDARD_TIME 56 COR_CIMP_ISRAEL_STANDARD_TIME 57 COR_CIMP_JORDAN_STANDARD_TIME 58 COR_CIMP_KALININGRAD_STANDARD_TIME 59 COR_CIMP_KAMCHATKA_STANDARD_TIME 60 COR_CIMP_KOREA_STANDARD_TIME 61 COR_CIMP_LIBYA_STANDARD_TIME 62 COR_CIMP_LINE_ISLANDS_STANDARD_TIME 63 COR_CIMP_LORD_HOWE_STANDARD_TIME 64 COR_CIMP_MAGADAN_STANDARD_TIME 65 COR_CIMP_MAGALLANES_STANDARD_TIME 66 COR_CIMP_MARQUESAS_STANDARD_TIME 67 COR_CIMP_MAURITIUS_STANDARD_TIME 68 COR_CIMP_MID_ATLANTIC_STANDARD_TIME 69 COR_CIMP_MIDDLE_EAST_STANDARD_TIME 70 COR_CIMP_MONTEVIDEO_STANDARD_TIME 71 COR_CIMP_MOROCCO_STANDARD_TIME 72 COR_CIMP_MOUNTAIN_STANDARD_TIME 73 COR_CIMP_MOUNTAIN_STANDARD_TIME_MEXICO 74 COR_CIMP_MYANMAR_STANDARD_TIME 75 COR_CIMP_N_CENTRAL_ASIA_STANDARD_TIME 76 COR_CIMP_NAMIBIA_STANDARD_TIME 77 COR_CIMP_NEPAL_STANDARD_TIME 78 COR_CIMP_NEW_ZEALAND_STANDARD_TIME 79 COR_CIMP_NEWFOUNDLAND_STANDARD_TIME 80 COR_CIMP_NORFOLK_STANDARD_TIME 81 COR_CIMP_NORTH_ASIA_EAST_STANDARD_TIME 82 COR_CIMP_NORTH_ASIA_STANDARD_TIME GE Digital 42

43 Index Enumeration 83 COR_CIMP_NORTH_KOREA_STANDARD_TIME 84 COR_CIMP_OMSK_STANDARD_TIME 85 COR_CIMP_PACIFIC_SA_STANDARD_TIME 86 COR_CIMP_PACIFIC_STANDARD_TIME 87 COR_CIMP_PACIFIC_STANDARD_TIME_MEXICO 88 COR_CIMP_PAKISTAN_STANDARD_TIME 89 COR_CIMP_PARAGUAY_STANDARD_TIME 90 COR_CIMP_ROMANCE_STANDARD_TIME 91 COR_CIMP_RUSSIA_TIME_ZONE_10 92 COR_CIMP_RUSSIA_TIME_ZONE_11 93 COR_CIMP_RUSSIA_TIME_ZONE_3 94 COR_CIMP_RUSSIAN_STANDARD_TIME 95 COR_CIMP_SA_EASTERN_STANDARD_TIME 96 COR_CIMP_SA_PACIFIC_STANDARD_TIME 97 COR_CIMP_SA_WESTERN_STANDARD_TIME 98 COR_CIMP_SAINT_PIERRE_STANDARD_TIME 99 COR_CIMP_SAKHALIN_STANDARD_TIME 100 COR_CIMP_SAMOA_STANDARD_TIME 101 COR_CIMP_SARATOV_STANDARD_TIME 102 COR_CIMP_SE_ASIA_STANDARD_TIME 103 COR_CIMP_SINGAPORE_STANDARD_TIME 104 COR_CIMP_SOUTH_AFRICA_STANDARD_TIME 105 COR_CIMP_SRI_LANKA_STANDARD_TIME 106 COR_CIMP_SYRIA_STANDARD_TIME 107 COR_CIMP_TAIPEI_STANDARD_TIME 108 COR_CIMP_TASMANIA_STANDARD_TIME 109 COR_CIMP_TOCANTINS_STANDARD_TIME 110 COR_CIMP_TOKYO_STANDARD_TIME 111 COR_CIMP_TOMSK_STANDARD_TIME 112 COR_CIMP_TONGA_STANDARD_TIME 113 COR_CIMP_TRANSBAIKAL_STANDARD_TIME 114 COR_CIMP_TURKEY_STANDARD_TIME 115 COR_CIMP_TURKS_AND_CAICOS_STANDARD_TIME 116 COR_CIMP_ULAANBAATAR_STANDARD_TIME 117 COR_CIMP_US_EASTERN_STANDARD_TIME 118 COR_CIMP_US_MOUNTAIN_STANDARD_TIME 119 COR_CIMP_UTC 120 COR_CIMP_UTC_PLUS_ COR_CIMP_UTC_PLUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_UTC_MINUS_ COR_CIMP_VENEZUELA_STANDARD_TIME 127 COR_CIMP_VLADIVOSTOK_STANDARD_TIME 128 COR_CIMP_W_AUSTRALIA_STANDARD_TIME 129 COR_CIMP_W_CENTRAL_AFRICA_STANDARD_TIME 130 COR_CIMP_W_EUROPE_STANDARD_TIME 131 COR_CIMP_W_MONGOLIA_STANDARD_TIME 132 COR_CIMP_WEST_ASIA_STANDARD_TIME 133 COR_CIMP_WEST_BANK_STANDARD_TIME 134 COR_CIMP_WEST_PACIFIC_STANDARD_TIME GE Digital 43

44 Index Enumeration 135 COR_CIMP_YAKUTSK_STANDARD_TIME Sample Code Dim yy As Integer Dim mon As Integer Dim dd As Integer Dim hh As Integer Dim min As Integer Dim sec As Integer Dim nano As Long Dim adjdate As Date local time 2017 Oct 13 3 PM Legend: yy = 2017 mon = 10 dd = 13 hh = 15 min = 0 sec = 0 nano = 0 Convert the time to Korean time: adjdate = GetLocalDateAdjustedToTimeZone(yy,mon,dd,hh,min,sec, nano,trend_tz_korea_standard_time) Or adjdate = GetLocalDateAdjustedToTimeZone(yy,mon,dd,hh,min,sec, nano,60) MsgBox format$(adjdate, "m/d/yyyy:hh:n:ss") Returns 2017 Oct 14 4 AM GE Digital 44

45 2.9 USER/WINDOWS AUTHENTICATION The following new Windows Authentication features/enhancements have been added to the CIMPLICITY v9.5 SIMs. CIMPLICITY v9.5 SIM8 DE32737; SF DE32738; SF US Starting CIMPLICITY 9.5 SIM 8, support has been provided to authenticate Domain Users in CIMPLICITY after explicit Logout action. In order to enable this functionality, the following global parameter has to be defined in CIMPLICITY Configuration: Attribute Name For Purpose Value DOMAIN_USER_AUTOLOGIN Domain User Authentication To support authentication of domain users in CIMPLICITY after explicit logout Enter one of the following. Y or y Allows domain user to log in automatically after explicit logout N or n User will have to provide login credentials after explicit logout Default Allows domain user to log in automatically after explicit logout Note: To use the above-mentioned settings for the default "ADMINISTRATOR" User, the "Authentication Type" must be set to "Windows Domain with Group Mapping" in the User Properties Dialog. GE Digital 45

46 2.10 WORKBENCH CIMPLICITY v9.5 SIM 4: Project Upgrade Progress Dialog US64408 Starting in CIMPLICITY 9.5 SIM 4, when upgrading a project to CIMPLICITY 9.5 Version, users will be presented with a "Project Upgrade Progress Dialog". Purpose: When upgrading a CIMPLICITY Project to be opened in CIMPLICITY 9.5 Version, users will be provided with better information about the status of the project upgrade operation. The images below show the different states of the Project Upgrade Progress Dialog: Image: After successful "Project Upgrade" Operation Image: "Project Upgrade" Operation in progress Image: "Project Upgrade" - Operation failure notification GE Digital 46

47 CIMPLICITY v9.5 SIM 1: Firewall Configuration Settings US79712 Starting in CIMPLICITY 9.5 SIM 8, the Firewall Configuration Settings for CIMPLICITY can be configured to have a specific set of configuration options used when integrating with Windows Firewall. Allow the type of Firewall Configuration Settings to be used when integrating CIMPLICITY with Windows Firewall. GE Digital 47

48 Option Enabled/Disabled Changes done to Windows Firewall Settings 1. Private Profile 2. Domain Profile Enabled [Default] Disabled Enabled [Default] Under the Private Profile section: 1. CIMPLICITY will be enabled in "Allowed apps and features" Options. 2. CIMPLICITY Executables set will be added to "Inbound Rules" list. Under the Private Profile section: 1. CIMPLICITY will be disabled in "Allowed apps and features" Options. 2. CIMPLICITY Executables set will be removed from "Inbound Rules" list. Non-Domain System: 1. CIMPLICITY will not be shown in "Allowed apps and features" Options. 2. CIMPLICITY Executables set will be added to "Inbound Rules" list for Domain Profile Section. 3. Public Profile Disabled Enabled Disabled [Default] Domain System: Under the Domain Profile section: 1. CIMPLICITY will be enabled in "Allowed apps and features" Options. 2. CIMPLICITY Executables set will be added to "Inbound Rules" list. Non-Domain System: CIMPLICITY Executables set will be removed from "Inbound Rules" list for Domain Profile Section. Domain System: Under the Domain Profile section: 1. CIMPLICITY will be disabled in "Allowed apps and features" Options. 2. CIMPLICITY Executables set will be removed from "Inbound Rules" list. Under the Public Profile section: 1. CIMPLICITY will be enabled in "Allowed apps and features" Options. 2. CIMPLICITY Executables set will be added to "Inbound Rules" list. Under the Public Profile section: 1. CIMPLICITY will be disabled in "Allowed apps and features" Options. 2. CIMPLICITY Executables set will be removed from "Inbound Rules" list CIMPLICITY v9.5 SIM 1: Save Point Values US98267 Starting in CIMPLICITY 9.5 SIM 9, Users can configure the option to save Point Values based on timers as well. GE Digital 48

49 Purpose: Save Point Values of a project based on timers as well. To access this option, users can access the dialog by clicking the Settings button for points from Settings tab in Project Properties. In the dialog, the user can now select the "On Timer" option and specify the time interval as shown below: Option Enabled/Disabled Changes done to Windows Firewall Settings 1. On Timer 2. Save Interval Unselected [Default] Selected Disabled [If Timer option is not selected]. Enabled [If Timer option is selected]. The Point Values will not be saved based on timer. also, the Save interval field will be disabled. The Point Values will be saved at regular intervals, based on the time interval specified in the Save interval field. The value of Save interval field will not be used for Point Value Save operations. Defaults to 10 minutes. The value of Save interval field will be used to determine the interval for Saving Point Values. GE Digital 49

50 3 FIXED DEFECTS The following issues have been resolved in HMI/SCADA CIMPLICITY v ISSUES RESOLVED: ALARMS CIMPLICITY v9.5 SIM 15 Alarm Script API/ Database Logger Alarms API Script/ Point name limitation DE63284 SF Previously, when no reference item was passed using the AlarmGenerate and AlarmUpdate Script APIs, the Database Logger inserted nonsensical data into the Reference field of the ALARM_LOG table. DE61310 SF Previously, when you updated the state of an alarm, the alarm API script did not accept point names that were longer than 32 characters. This issue has been resolved. When no reference item is passed using the AlarmGenerate and AlarmUpdate Script APIs, the Database Logger inserts no data into the Reference field of the ALARM_LOG table. This issue has been resolved. When you update the state of an alarm, the alarm API script now accepts point names that are longer than 32 characters CIMPLICITY v9.5 SIM 12 Alarms/ ANA Expressions DE55827 SF When running a CIMPLICITY Project configured with DNP Driver, incorrect timestamp value gets assigned for Alarm Reset Operation. When running a CIMPLICITY Project configured with DNP Driver, timestamp value for Alarm Reset Operation is now set properly CIMPLICITY v9.5 SIM 9 Historical Alarm Viewer/ Alarm Filtering DE32362 SF When filters are applied to Historical Alarm Viewer control in CimView, the specified filters are not applied properly. When filters are applied to Historical Alarm Viewer control in CimView, the specified filters are now applied properly. GE Digital 50

51 3.1.4 CIMPLICITY v9.5 SIM 7 Alarm Viewer/ Alarm Message String Alarms/ Alarm Generation DE25790 SF When resources are dynamically added to remote project at runtime, the alarms for points are not visible in Alarm Viewer on Enterprise Project DE27532 SF When an expression having multiple AL( ) functions is used in an OR statement, and the points are configured with delayed alarm generation then the alarms are not generated properly for all combinations. Also, the help information for using PTMRP_ALARM_DELAY_STATE Global Parameter appears to be incorrect. Setting the parameter value to Y changes alarm state immediately to Point Management Clients. When resources are dynamically added to remote project at runtime, the alarms for points are now displayed properly in Alarm Viewer on Enterprise Project When an expression having multiple AL( ) functions is used in an OR statement, and the points are configured with delayed alarm generation then the alarms are now generated properly for all combinations. The information mentioned below should be referenced while using PTMRP_ALARM_DELAY_STATE Global Parameter: 1. When the parameter value is set to Y, the alarm state changes immediately and alarm delay is not applicable. 2. When the parameter value is set to N, the Alarm State Delay is enabled CIMPLICITY v9.5 SIM 5 Alarms/ Historical Alarm Viewer Alarms/ Alarm Manager DE16906 SF When a Historical Alarm Viewer used in CimScreen is viewed at runtime, the text in the control does not get displayed using the configured font information. DE16436 SF When screen containing Trend Object is opened in viewer node, "Unknown alarm manager - AMRP " error message gets logged into system log. When a Historical Alarm Viewer used in CimScreen is viewed at runtime, the text in the control now gets displayed using the configured font information. When screen containing Trend Object is opened in viewer node, the "Unknown alarm manager - AMRP " error message no longer gets logged into system log CIMPLICITY v9.5 SIM 3 DE18704 SF GE Digital 51

52 Alarms/ ANA Expressions When ANA() function is used to refer an alarm on device point, the ANA() function does not reflect the correct state when communication with device gets reset. When ANA() function is used to refer an alarm on device point, the ANA() function now reflects the correct state when communication with device gets reset CIMPLICITY v9.5 SIM 2 Alarms/ Alarm Field Errors Alarms/ Alarm Message DE17934 SF With SetPoint audit trail enabled on a CIMPLICITY project, performing a SetPoint operation from a viewer that is running an older version of CIMPLICITY will cause Alarm field related error on the CIMPLICITY node running the project. DE18050 SF When $DOWNLOAD Alarm is used in alarm messages, "BAD FIELD" gets populated into the alarm message for the $DOWNLOAD Alarm. With SetPoint audit trail enabled on a CIMPLICITY project, performing a SetPoint operation from a viewer that is running an older version of CIMPLICITY will no longer result in Alarm field related errors on the CIMPLICITY node running the project. When $DOWNLOAD Alarm is used in alarm messages, the alarm message for the $DOWNLOAD Alarm now gets generated properly CIMPLICITY v9.5 SIM 1 Alarms/ ANA Expressions Alarms/ Application Crashes Alarms/ Dynamic Changes Alarms/ Auto Timed Acknowledges DE17370 SF When ANA() expressions are used for device points in screens, the expression returns TRUE even if alarm is not present on point. DE17268 SF Intermittent AMRP.exe process crashes occur during runtime. DE16727 SF When changes are made to Alarms dynamically, A&E OPC Server crashes are observed. DE16460 SF When a point configured with an alarm having timed auto acknowledge, is When ANA() expressions are used for device points in screens, the expression now returns TRUE only if alarm is present on point. Intermittent AMRP.exe process crashes no longer occur during runtime. When changes are made to Alarms dynamically, A&E OPC Server crashes no longer occur. When a point configured with an alarm having timed auto acknowledge, is used in a GE Digital 52

53 Alarms/ Alarm Process Crash Alarm Viewer/ Alarm Message String Alarms/ Delayed alarms and Dead Bands used in a CIMPLICITY project, the alarms are not generated properly. DE16187 SF When executing CIMPLICITY Project, Alarm Management Resident Process crashes are observed intermittently. DE16117 SF When viewing an alarm that is using the %STATE property as part of the message, it was possible that the %STATE field would not properly reflect the device availability. DE16371 SF When a point configured with an alarm having Deadband and a Delay, is used in a CIMPLICITY project, the alarms are not generated properly. CIMPLICITY project, the alarm is now generated properly. When executing CIMPLICITY Project, Alarm Management Resident Process crashes are no longer occur. When viewing alarms in Alarm Viewer, the device point state being displayed now shows the device availability status properly. When a point configured with an alarm having Deadband and a Delay, is used in a CIMPLICITY project, the alarm is now generated properly. GE Digital 53

54 3.2 ISSUES RESOLVED: CIMEDIT/CIMVIEW CIMPLICITY v9.5 SIM 17 CimLayout configuration file/ Read error DE79785 SF Previously, in CIMPLICITY 9.5, if you tried to open a CimLayout configuration file that was created in CIMPLICITY 8.2, an error occurred. This issue has been resolved. In CIMPLICITY 9.5, you can now open a CimLayout configuration file that was created in CIMPLICITY CIMPLICITY v9.5 SIM 16 CimView/ Script Iteration issues CimView/ Crash issues DE79214 Internal Previously, when a script was run on a collection of closed or overlaying screens, CimView stopped responding. DE76983 Internal Previously, CimView stopped responding due to several issues related to string space, COM server, duplicate child objects, and scripts with multiple arguments. This issue has been resolved. CimView now functions as expected when a script is run on a collection of closed or overlaying screens. This issue has been resolved. CimView now functions as expected as the issues related to string space, COM server, duplicate child objects, and scripts with multiple arguments have been resolved CIMPLICITY v9.5 SIM 13 CimEdit/ Scripting Issues DE59347 SF When modifying contents of a graphics screen using smart objects and scripts in CimEdit, changes made to screens via script are not persisted when the CimEdit application is closed. When modifying contents of a graphics screen using smart objects and scripts in CimEdit, changes made to screens via script are now persisted properly when the CimEdit application is closed. GE Digital 54

55 3.2.4 CIMPLICITY v9.5 SIM 12 CimView/ Viewer Connectivity CimView/ Expression Evaluation CimView/ Expression Evaluation CimView/ Application Crash DE55363 SF When the project is restarted on the server, the screens on viewer configured with On Demand Points do not recover their values properly. DE55847 SF When viewing CIMPLICITY Screens configured with expression update events on screen startup, in CimView, the expression updates occur prematurely. DE55648 SF When copying a button object from one screen to another, the procedures configured in the original button get deleted/modified during copy/paste operation. DE51950 SF When a CIMPLICITY Project configured with Server Redundancy is recovering from fail-over in runtime, performing screen overlay operations causes CimView application to crash occasionally. When the project is restarted on the server, the screens on viewer configured with On Demand Points now recover their values properly. When viewing CIMPLICITY Screens configured with expression update events on screen startup, in CimView, the expression updates now occur properly after screen initialization. When copying a button object from one screen to another, the procedures no longer get deleted/modified during copy/paste operation. When a CIMPLICITY Project configured with Server Redundancy is recovering from fail-over in runtime, performing screen overlay operations no longer causes CimView application to crash CIMPLICITY v9.5 SIM 11 CimView/ Color Animation DE51054 SF When CimView is used to view graphic screens created in older version of CIMPLICITY, the color animation expressions do not evaluate properly when multiple bits of Point Attribute Set are used in animation expressions. When CimView is used to view graphic screens created in older version of CIMPLICITY, the color animation expressions now evaluate properly when multiple bits of Point Attribute Set are used in animation expressions. GE Digital 55

56 3.2.6 CIMPLICITY v9.5 SIM 10 CimLayout/ CimView Application Crash CimView/.CLM Files and CimView Application Crash CimLayout/ CimView Application Crash CimView/ /LoadPassword Parameter DE51055 SF Previously, when a script thread closed a window (close or overlay) and another script thread accessed it through the object model, CimView stopped responding. DE44121 SF When using CimView to navigate between graphic screens of a project configured with.clm files, occasional CimView application crashes are observed. DE51611; SF DE51612; SF When closing a CimLayout that has multiple screens configured in Runtime, CimView application crashes are observed. DE42392 SF When launching CimView application with /LoadPassword commandline parameter, the auto-login functionality does not work as expected. Also, the login dialog is not shown when launching CimView screens via CimLayout application. This issue has been resolved. When a script thread closes a window (close or overlay) and another script thread accesses it through the object model, the issue of CimView not responding no longer occurs. When using CimView to navigate between graphic screens of a project configured with.clm files, CimView application crashes are no longer seen. When closing a CimLayout that has multiple screens configured in Runtime, CimView application crashes are no longer seen. When launching CimView application with /LoadPassword commandline parameter, the functionality works as expected. Points to consider: Please ensure that: 1. <FileName>.cfg file is populated with the right UserName and Password information. The login credentials must be same as that configured for the user in workbench for the project. 2. Global parameter UR_PWD_CASE is set to Y if password is case sensitive. 3. <FileName>.cfg file is placed in the data subdirectory of the CIMPLICITY installation directory (e.g. C:\Program Files\Proficy\Proficy CIMPLICITY\data). 4. /LoadPassword commandline option is invoked as mentioned below: CimView.exe /LoadPassword <FileName>.cfg 5. When using CimLayout, the /LoadPassword commandline option cannot be used. However, the login dialog will now be displayed at the top when launching CimLayout. GE Digital 56

57 Advanced Viewer/ CimView Application Crash CimEdit/.NET Controls DE41572 SF When using CimView application in Advanced Viewer mode, periodic application crashes are observed with CimView application. DE37835 SF When working on CimEdit Screens, adding and removing a.net Control from the CimEdit Screen causes the control to be deleted from system as well. When using CimView application in Advanced Viewer mode, periodic application crashes no longer happen with CimView application. When working on CimEdit Screens, adding and removing a.net Control from the CimEdit Screen will no longer delete the control from system as well CIMPLICITY v9.5 SIM 9 CimView/ RichEdit Control CimView/ Menu Items DE40420 SF When working with RichEdit Control, copying the contents of the control does not work if the focus is not set on the control. DE19911 SF When a menu item containing multiple menu items is configured in a screen, the display order for the menu items is reversed at runtime in CimView. Copying the contents of RichEdit Control now works properly. When a menu item containing multiple menu items is configured in a screen, the menu items are now displayed as configured in CimView CIMPLICITY v9.5 SIM 8 CimView/ Memory Leak Issues CimView/ Application Crash DE30694 SF When CimView application is run with /NoScreenExit Command Line Argument, memory leaks are observed at runtime. DE31439; SF DE31444; SF When running CimView application, occasional crashes and hangs are observed. When CimView application is run with /NoScreenExit Command Line Argument, memory leaks are no longer observed at runtime. When running CimView application, occasional crashes and hangs are no longer seen. GE Digital 57

58 3.2.9 CIMPLICITY v9.5 SIM 7 CimView/ Faceplates on Viewers CimView/ Linked Objects CimView/ Linked Objects DE28095 SF When viewing CimView screens on Viewer machine, the faceplates configured for Class objects are not shown to user. DE19764; SF DE22688; SF DE25995; SF When a screen containing a linked object that is configured with locally defined event is viewed in runtime, the linked object does not get highlighted properly. DE27248 SF When a screen containing a linked object, configured with screen overlay/screen open action is triggered in runtime, the configured actions do not get executed. When viewing CimView screens on Viewer machine, the faceplates configured for Class objects are now shown properly to user. When a screen containing a linked object that is configured with locally defined event is viewed in runtime, the linked object now highlighted properly. When a screen containing a linked object, configured with screen overlay/screen open action is triggered in runtime, the configured actions now get executed properly CIMPLICITY v9.5 SIM 6 CimView/ Application Crash CimView/ Memory Leaks CimEdit/ Expression Parser CimEdit/.NET Components DE19278 SF When overlaying screens containing linked objects in CimView, application crash occurs. DE18729 SF When CimView opens a screen containing a trend object, and the /noscreenexit command line argument is used, then the CimView process may experience a memory growth. DE19774 SF When an event that is configured for an object in a screen using OnExpressionUpdate() function is triggered, the specified value is not set to the associated device point properly. DE18815 SF When a CimEdit screen having a frame container configured with.net components and expressions is opened When overlaying screens containing linked objects in CimView, application crashes no longer occur. When CimView opens a screen containing a trend object, and the /noscreenexit command line argument is used, then the CimView process memory growth no longer occurs. When an event that is configured for an object in a screen using OnExpressionUpdate() function is triggered, the specified value is now properly set to the associated device point. When a CimEdit screen having a frame container configured with.net components and expressions is opened in CimView, the GE Digital 58

59 CimView/ Linked Objects in CimView, the configured expressions are not evaluated properly when opening the screen. DE19764; SF DE22688; SF When a screen containing a linked object that is configured with locally defined event is viewed in runtime, the linked object does not get highlighted properly. configured expressions now evaluated properly on start. When a screen containing a linked object that is configured with locally defined event is viewed in runtime, the linked object now highlighted properly CIMPLICITY v9.5 SIM 5 CimLayout/ File Browsing CimView/ Terminal Server Sessions CimView/ Alarm Viewer CimView/ "Always On Top" Option DE18947 SF With the option to browse files being disabled in CIMPLICITY options, user is still allowed to access option to open files from CimLayout application in Webspace Session. DE18937 SF When large number of Terminal Services sessions are open and CimView application is opened from one of the sessions, occasional application hangs occur. DE17244 SF When a CimView screen is configured with an Alarm Viewer control that is configured to display an alarm having long tag name, attempting to open the screen from Alarm viewer at runtime does not open the target screen. DE16982 SF When multiple screens are configured with "Always On Top" option in a project, opening more than one screen at runtime can cause inactive screens to lose the "Always On Top" option setting. With the option to browse files being disabled in CIMPLICITY options, user will no longer be allowed to access option to open files from CimLayout application in Webspace Session. When large number of Terminal Services sessions are open and CimView application is opened from one of the sessions, occasional application hangs no longer occur. When a CimView screen is configured with an Alarm Viewer control that is configured to display an alarm having long tag name, the screen can now be successfully opened from Alarm viewer at runtime. When multiple screens are configured with "Always On Top" option in a project, opening more than one screen at runtime no longer causes inactive screens to lose the "Always On Top" option setting. GE Digital 59

60 CIMPLICITY v9.5 SIM 4 CimView/ Global Scripts CimView/ Blink Animation CimView/ Touch Enabled Screens CimView/ OLE Objects DE18743 SF When "Edit Global Script" option is used to modify a global script, the edit window does not bring up the selected script in script editor at times. DE18695 SF When a graphics screen, containing a push button object configured with color animation, is opened in CimView application, the button styles do not get displayed properly when clicking the button object. DE18833 SF On touch enabled screens, Mouse down events are not handled properly by CimView application. Triggering of Mouse Down events occur in incorrect sequence. DE18862 SF When a screen that has multiple OLE Objects is opened in CimView application for editing, attempting to delete text from an OLE Object results in text being deleted in a different OLE Object When "Edit Global Script" option is used to modify a global script, the edit window now brings up the selected script properly. When a graphics screen, containing a push button object configured with color animation, is opened in CimView application, the button styles now get displayed properly when clicking the button object. On touch enabled screens, Mouse down events now get handled properly by CimView application. Triggering of Mouse Down events also now occur in correct sequence. When a screen that has multiple OLE Objects is opened in CimView application for editing, deletion of text from an OLE Object now works properly CIMPLICITY v9.5 SIM 3 CimView/.NET Control Properties CimView/.NET Controls DE18696 SF When properties of.net Controls added in a screen are being edited, scrolling to the property to be modified does not happen properly. DE18574 SF When a.net control configured with properties that can be set is added to a screen, is the edited properties are not saved properly. DE18512 SF When properties of.net Controls added in a screen are being edited, property to be modified can now be scrolled to properly. When a.net control configured with properties that can be set is added to a screen, is the edited properties are now saved properly. GE Digital 60

61 CimView/ CimLayout Crash XY Plot/ Resize Issue When CimLayout application for a project is open, any attempt to logout currently logged-in user from the system results in CimLayout application crash. DE16253 SF When a XY Plot control object (ActiveX control) is used to display data with multiple series, re-sizing of the control does not happen properly. When CimLayout application for a project is open, currently logged-in user can successfully log out from the system without any crash issues. When a XY Plot control object (ActiveX control) is used to display data with multiple series, resizing of the control now happens properly CIMPLICITY v9.5 SIM 2 CimView/ Screen Open Events CimView/ ANA Expressions CimEdit/ Group Containers CimView/ CimLayout Configuration CimView/ Screen Navigation DE18205 SF When a CimView screen is being launched OnScreen Open Events get triggered and executed even before the login credentials have been provided by user. DE18167; SF DE18277; SF When CimView is used to view CimScreens, the linked objects with color animation expressions that use AL() and ANA() functions are falsely activated on start of project. DE17655 SF With the group container for a group object of screen in open state, if a second screen is opened for editing in CimEdit, the opened group container can no longer be closed. DE17507 SF When a CimLayout is configured to refer to a non-existing screen, crashes are observed when CimLayout is launched. DE17475 SF When navigating between CimView screens using the navigation toolbar, memory leaks and intermittent When a CimView screen is being launched, any Screen Open events that require user credentials will now wait before getting executed. Note: Events that do not require user intervention would still get triggered and executed without waiting for User Credentials. When CimView is used to view CimScreens, the linked objects with color animation expressions that use AL() and ANA() functions now work properly on start of project. With the group container for a group object of screen in open state, if a second screen is opened for editing in CimEdit, the opened group container can now be closed properly. When a CimLayout is configured to refer to a non-existing screen, crashes are no longer observed when CimLayout is launched. Navigating between CimView screens using the navigation toolbar now works properly and issues related to memory leaks and intermittent GE Digital 61

62 CimView/ Point View Dialog CimEdit/ Script Execution Objects with Shadow crashes/hangs of CimView application are observed. DE17427 SF When Point View is used in CimView, copying of all displayed points does not happen properly to the clipboard. DE16752 SF When logging into a CimView screen after switching users, the scripts configured for the screen get executed before successful login, resulting in script execution failures. DE7740 SF When objects with shadows are grouped or placed closely together and one or more objects in the group are made invisible at runtime using variables, the shadow remains while actual object(s)/group is invisible. crashes/hangs of CimView application are no longer seen. When Point View is used in CimView, all displayed points now get copied properly to the clipboard. When logging into a CimView screen after switching users, the scripts configured for the screen now get executed after successful login. Now, when objects with shadows are grouped or placed closely together and one or more objects in the group are made invisible at runtime using variables, the shadow and the object(s)/group becomes invisible CIMPLICITY v9.5 SIM 1 CimEdit/ Upgraded Screens CimEdit/.NET Controls CimEdit/ Runtime File Extensions CimEdit/ CTX File Format DE16991 SF When opening a screen that is upgraded to 9.5 Version, CimEdit crashes are observed. DE17362 SF NET Controls created in CimEdit Screens under an account with elevated privileges are not accessible to other users. DE16725 SF When browsing for CimView Runtime screens, the supported file extensions are shown as *.CMRT instead of *.CIMRT file types. DE17894 SF When graphic screens configured with Forms.ComboBox objects are stored in.ctx file format, the screens can no longer be opened for editing. When opening a screen that is upgraded to 9.5 Version, CimEdit crashes are no longer seen..net Controls created in CimEdit Screens under an account with elevated privileges are now accessible to other users. When browsing for CimView Runtime screens, the supported file extensions are now shown properly as *.CIMRT file types. Graphic screens having Forms.ComboBox objects configured that stored in.ctx file format can now be opened for editing. GE Digital 62

63 CimView/ Application Hang CimView/ CimLayout Crashes CimView/ Shadow Locations CimView/ Objects with Shadow CimView/ Expression Updates DE16070 SF When a condition expression in CimView contains the "GT" (greater than) function, CimView hang could occur. DE16335; SF DE16332; SF When navigating between CimView screens that are part of a CimLayout configuration, CimView application crashes were observed: 1. When the Alt Key was pressed during screen Navigation. 2. When the CimLayout instance was closed. DE17551; SF DE17889; SF When graphic screens are opened in CimView at runtime, the shadows for objects appear at incorrect location. DE10669; SF DE10661; SF When objects with shadows are grouped or placed closely together and one or more objects in the group are made invisible at runtime using variables, the shadow remains while actual object(s)/ group is invisible. DE16442; SF DE16368; SF When navigating between CimView screens, variable expression updates get triggered during screen open operation. When the "GT" (greater than) expression is used in a CimView expression, it will no longer potentially hang. CimView application crashes are no longer observed when CimView Screens are used in CimLayout configuration. When graphic screens are opened in CimView at runtime, the shadows for objects now appear at proper location. Now, when objects with shadows are grouped or placed closely together and one or more objects in the group are made invisible at runtime using variables, the shadow and the object(s)/ group becomes invisible. When navigating between CimView screens, variable expression updates no longer get triggered during screen open operation. 3.3 ISSUES RESOLVED: CLASSES AND CLASS OBJECTS CIMPLICITY v9.5 SIM 15 Classes/ Data items DE73843 SF Previously, data items that used the $DATAITEM_EXISTS expression and did not exist in the project were shown as invalid points in Point Control Panel. This issue has been resolved. Data items that use the $DATAITEM_EXISTS expression and do not exist in the project are no longer shown as invalid points in Point Control Panel. GE Digital 63

64 3.3.2 CIMPLICITY v9.5 SIM 12 Class Objects/ CimServer Application Crash DE46653 SF When modifying class objects in runtime when dynamic mode is enabled, occasional CimServer application crashes are observed. When modifying class objects in runtime when dynamic mode is enabled, CimServer application crashes no longer occur CIMPLICITY v9.5 SIM 11 Composite Classes/ PreCreate Scripts DE38592 SF When objects of composite class are created, the PreCreate scripts of the subclass do not execute properly and attributes configured for modification do not get updated properly. When objects of composite class are created, the PreCreate scripts of the subclass now execute properly and attributes configured for modification get updated properly. Note: The PreCreate scripts can modify attributes of a subclass object in static state only. Dynamic mode is currently not supported CIMPLICITY v9.5 SIM 10 Classes/ Properties and Methods DE40250 SF When creating contents of a CimEdit Screen in a project, adding a.net control does not display all methods and properties supported for the control. When creating contents of a CimEdit Screen in a project, adding a.net control now displays all methods and properties supported for the control CIMPLICITY v9.5 SIM 9 Class Object/ Copying Class Objects or Dynamic Object Creation DE37246; SF DE37788; SF When copying an object of a class between projects or creating an object dynamically in a project at runtime using scripting, no warnings are When copying an object of a class between projects or creating an object dynamically in a project at runtime using scripting, the object GE Digital 64

65 provided if the required class has not been defined in destination project. Also, the invalid object can no longer be deleted in destination project. creation operation fails if the required class is not found in destination project CIMPLICITY v9.5 SIM 8 Class/ Pre/Post Create Scripts DE29516 SF When configuring a Class,.NET scripts can be selected for configuring the Pre- Create and Post Create scripts. When configuring a Class,.NET scripts can no longer be selected for configuring the Pre-Create and Post Create scripts. Only *.bcl scripts are now allowed CIMPLICITY v9.5 SIM 7 Class Configuration/ Graphics File Reference Class Object/ Object Creation via scripting Class Object/ Object Creation DE27382 SF When an imported class configuration is opened for modification, deleting the Graphics file reference will cause "Failed to create File" error message to be displayed when Apply button is clicked. DE22045 SF When class objects are being created via scripting support, CimServer.exe application crashes occur randomly. DE24371 SF When the configured class object is being created via the Class Object Creation dialog, if the OK Button is pressed more than once, then created object might get corrupted. When an imported class configuration is opened for modification, deleting the Graphics file reference will no longer cause "Failed to create File" error message to be displayed when Apply button is clicked. When class objects are being created via scripting support, CimServer.exe application crashes no longer occur. When the configured class object is being created via the Class Object Creation dialog, the OK Button is now disabled during object creation process so that created object does not corrupted CIMPLICITY v9.5 SIM 5 Class Objects/ DE19083 SF GE Digital 65

66 Object Properties Class Objects/ script execution Class/ Actions and scripts When the attributes of a class object are being modified, some of the configured object attributes are deleted randomly. DE17019 SF When a script, configured to access the child objects of a composite class object, is run, runtime failure occurs and script execution gets halted. DE17027 SF When a class is configured with an action referring to a script, the Class Properties dialog does not display the name of associated script in the display grid, even though a script is assigned. When the attributes of a class object are being modified, the configured object attributes no longer get altered or deleted. The "CompositeObjects" property is not valid for class objects that are composite in nature or contains child objects. A new function IsCompositeObject() is now available that can be used in scripts to determine if a class object is composite in nature or not before accessing its attributes/properties. When a class is configured with an action referring to a script, the Class Properties dialog now properly displays the name of associated script in the display grid CIMPLICITY v9.5 SIM 4 Class Objects/ Just-in-time points DE18514 SF When messages are being logged for class objects, the ALARM_ID information does not get logged into database for Just-In-Time points. When messages are being logged for class objects, the ALARM_ID information does now gets logged properly into database for Just-In- Time points CIMPLICITY v9.5 SIM 3 Class Objects/ Faceplates Class Objects/ Alarm Routing DE18163; SF DE18216; SF When a screen that has a class/object using a face plate configured is opened at runtime, errors are repeatedly logged in the project status logs. DE18329 SF When a class object created with an Alarm Attribute enabled is "edited, to add and enable another alarm, the Alarm Routing properties for that A screen that has a class/object using a face plate configured can now be opened successfully at runtime. No errors are now logged in the project status logs. When a class object created with an Alarm Attribute enabled is edited, to add and enable another alarm, the Alarm Routing properties for that Alarm Data Item now gets configured GE Digital 66

67 Alarm Data Item does not get configured with the default Alarm Routing properties of the Object as expected. properly with the default Alarm Routing properties of the Object as expected CIMPLICITY v9.5 SIM 2 Classes and Objects/ Faceplate Functionality DE16994; SF DE18217; SF When a Class Object, configured with Faceplate, is set to perform a Setpoint Operation, the Faceplate does not get drawn properly on the CimView Screen. When a Class Object, configured with Faceplate, is set to perform a Setpoint Operation, the Faceplate now gets drawn properly on the CimView Screen CIMPLICITY v9.5 SIM 1 Classes and Objects/ Object Explorer Class Objects/ Class Object Properties Class Objects/ Faceplates DE16726 SF When browsing the "Enhanced Design Library" folder in the Object Explorer in CimEdit, "Unexpected File Format" errors occur. DE16516 SF Unicode characters used in the description field for a Class Object properties are not properly. When new objects are created for the class, the description field content appears distorted cannot be edited. DE16938; SF DE16939; SF When the screen associated with the faceplate defined for a class having existing objects is updated to point to a different screen, the objects of the class do not updated properly to reflect the new changes. When browsing the "Enhanced Design Library" folder in the Object Explorer in CimEdit, "Unexpected File Format" errors are no longer occur. Unicode characters used in the description field for a Class Object properties are now shown properly. Also, the contents of description field having Unicode characters can be edited properly. When the screen associated with the faceplate defined for a class having existing objects is updated to point to a different screen, the objects of the class now get updated to reflect the new changes. To start using the objects with changes, the user can do either of the following: a. Close and reopen CimView Screen. b. Wait for a duration of 8 minutes so that the changes are updated correctly. GE Digital 67

68 3.4 ISSUES RESOLVED: DEVICE COMMUNICATIONS CIMPLICITY v9.5 SIM 17 OPC Client/ Duplicate Asynchronous Write DE84082 SF Previously, when an OPC Client Asynchronous Write operation was performed twice with the same value, the client processes did not respond. This issue has been resolved. Client processes now respond as expected when an OPC Client Asynchronous Write operation is performed twice with the same value CIMPLICITY v9.5 SIM 16 S90 Triplex/ Device Point Dynamic Duplication DE73645 SF Previously, when you dynamically duplicated a point, the S90 Triplex process stopped responding. This issue has been resolved. When you dynamically duplicate a point, the S90 Triplex process functions as expected CIMPLICITY v9.5 SIM 15 OPC UA Server/ Security Configuration DE70611 SF Previously, while setting up the OPC UA Server Security Configuration, if you selected either the Basic 256 or the Basic256Sha256 option, the security configuration was corrupted. This issue has been resolved. While setting up the OPC UA Server Security Configuration, if you select either the Basic 256 or the Basic256Sha256 option, the security configuration is not corrupted CIMPLICITY v9.5 SIM 10 Modbus/ Device Connectivity DE40586 SF When a project having multiple Modbus devices configured, is put into run mode with one or more devices in offline state, then when the devices come back online, When a project having multiple Modbus devices configured, is put into run mode with one or more devices in offline state, then when the devices come back online, they are now GE Digital 68

69 they are not recognized by CIMPLICITY Project. A project restart is required to have the devices identified at runtime. recognized by CIMPLICITY Project. A project restart is no longer required to have the devices identified at runtime CIMPLICITY v9.5 SIM 7 OPC UA Client/ Point Updates DE22048 SF When a project configured with OPC UA Devices/ ports is started, the points are marked as unavailable and values are not shown in Point Control Panel. Also, process crashes are observed when project is being stopped. When a project configured with OPC UA Devices/ ports is started, the points are now available and values are shown properly in Point Control Panel. Also, process crashes no longer occur CIMPLICITY v9.5 SIM 6 OPC Client/ Point Updates Modbus/ TCP Ports OPC Client/ OPC Groups DE17309 SF When a project is configured with OPC points, some of the configured points get incorrect value updates if ALL_UNSO option has been enabled. DE20294 SF When a project configured with more than 10 Modbus TCP Ports is put into Run mode, Ports higher than 10 are shown as Halted in the Process Control Dialog. DE15801; SF DE22049; SF DE24373; SF When configuring OPC Groups for an OPC client, new OPC groups do not get created. When a project is configured with OPC points, the configured points no longer get incorrect value updates if ALL_UNSO option has been enabled. When a project configured with more than 10 Modbus TCP Ports is put into Run mode, all configured Modbus Ports run properly and no longer get halted when viewed from Process Control Dialog. When configuring OPC Groups for an OPC client, new OPC groups now get created properly CIMPLICITY v9.5 SIM 4 DE18809 SF GE Digital 69

70 Modbus/ Server Redundancy When Modbus TCP/IP driver is used in a project and Model type is set to STAT_PLC or GENERIC_PLC type, the driver communications do not work properly in a server redundancy setup. When Modbus TCP/IP driver is used in a project and Model type is set to STAT_PLC or GENERIC_PLC type, the driver communications will now work properly in a server redundancy setup CIMPLICITY v9.5 SIM 3 OPC UA Client/ Communication Issues S90 Triplex/ OEM Protection DE16958; SF DE18637; SF DE18719; SF When a project configured with OPC UA Client is run, point updates are not received occasionally at times. DE18580; SF DE18504; SF When OEM Protection option is enabled for a project, communication issues between the project and configured PLCs are observed. When a project configured with OPC UA Client is run, point updates are now received properly. When OEM Protection option is enabled for a project, communication between the project and configured PLCs now occur properly CIMPLICITY v9.5 SIM 2 OPC Client/ Incorrect timestamps DE18530 SF When viewing the points associated with an OPC Server, CIMPLICITY displays incorrect number of milliseconds in the last field of Point timestamp. When viewing the points associated with an OPC Server, CIMPLICITY now displays correct number of milliseconds in the last field of Point timestamp CIMPLICITY v9.5 SIM 1 Marquee Driver/ Import/Export Support DE17717 SF When the Marquee Message Import tool is used for importing data into CIMPLICITY Project, the data is not imported properly. DE16881 SF The Marquee Message Import tool can now be used for importing data into CIMPLICITY Project successfully. GE Digital 70

71 S90 Triplex/ Stale Data Issue Proficy Driver Server/ Device Points OPC Server/ Partner Dead Messages Modbus/ Crash Issue When the network is restored after a brief disconnect, incorrect data is retrieved from PLC devices. DE16604 SF When PDS Device Point is created in a CIMPLICITY Project, "Poll After Set" option is set by default. DE16392 SF When CIMPLICITY HMI OPC Server is shutdown gracefully, "Partner Dead" error messages get logged into the status log DE16855 SF The Modbus TCP/IP device communication interface could terminate as a result of receiving malformed packets for unsolicited data. When the network is restored after a brief disconnect, data is now retrieved properly from PLC devices. "Poll After Set" option is no longer set by default for newly created PDS Device Points in a CIMPLICITY Project. When CIMPLICITY HMI OPC Server is shutdown gracefully, "Partner Dead" error messages are no longer logged into the status log. Malformed unsolicited data will no longer cause the Modbus TCP/IP device communication interface to fail. GE Digital 71

72 3.5 ISSUES RESOLVED: LOGGING CIMPLICITY v9.5 SIM 17 Database Logging/ Dynamic change of data points DE80372 SF Previously, if you dynamically added or removed data points to or from a database logging table, the database logging failed. This issue has been resolved. Database logging no longer fails when you dynamically add or remove data points to or from a database logging table CIMPLICITY v9.5 SIM 15 Database Logging/ Run-time system points DE70610 SF Previously, run-time system points that you added to the DATA_LOG table did not appear after the table was closed. This issue has been resolved. You can no longer add run-time system points to the DATA_LOG table CIMPLICITY v9.5 SIM 9 SQL Database/ Reconcile Table Historian/ Data Logging DE39060 SF When using the "Reconcile Table" utility in Database logger tool, the "sequence number" column is not updated properly. DE36540; SF DE36541; SF When a project is configured to use Historian for logging information, the connection to database does not get established and data logging does not happen. When using the "Reconcile Table" utility in Database logger tool, the "sequence number" column now gets updated properly. When a project is configured to use Historian for logging information, the connection to database now gets established properly and data logging happens successfully. Note: User Login Credentials also should be specified while configuring the Historian Data Server. The user login credentials should now be specified in the following fields for successful configuration of Historian Data Server: Login Name: It must be selected from the OPC User drop-down field. Login Password: This must be specified in the OPC Password field. GE Digital 72

73 Also, user will now be notified if invalid credentials are mentioned CIMPLICITY v9.5 SIM 2 Data Logger/ Process Crash Historian Tags/ Bad Values DE18477 SF When using Data Logging Functionality on a project configured with redundancy support, DL_RP Process crashes are observed. DE17785 SF When Points are logged to Historian, if the values of the points do not change, then bad quality data is logged to Historian. When using Data Logging Functionality on a project configured with redundancy support, DL_RP Process crashes are no longer seen. When Points are logged to Historian, even if the values do not change, valid data is logged to Historian CIMPLICITY v9.5 SIM 1 Data Logging/ PPS Alarms Information PTDL/DL Process Crash Historian/ Data Logging DE17466; SF DE17470; SF When information about acknowledged PPS Alarms is logged into database, the timestamp information is not logged properly. DE17357 SF PTDL_RP Process crashes are observed intermittently when using the data logging functionality. DE16067; SF DE16069; SF When Historian A&E OPC Collector is used to log information in a Redundant CIMPLICITY Project, Errors are logged into system logs when the project is stopped on secondary/primary node. When information about acknowledged PPS Alarms is logged into database, the timestamp information is now logged properly. PTDL_RP Process crashes are no longer seen when using the data logging functionality. When Historian A&E OPC Collector is used to log information in a Redundant CIMPLICITY Project, Errors are no logged system logs when the project is stopped on secondary/primary node. GE Digital 73

74 3.6 ISSUES RESOLVED: LOGIN CIMPLICITY v9.5 SIM 17 Domain Controller/ Workbench login DE75662 SF Previously, if you were disconnected from the Domain Controller, you could not log in to the Workbench application. This issue has been resolved. If you are disconnected from the Domain Controller, you can log in to the Workbench application CIMPLICITY v9.5 SIM 15 CIMPLICITY Login/ Runtime data DE70395 Internal Previously, in Windows Server 2016 and Windows 10, when you ran a web client with a user profile that was not configured in CIMPLICITY, you were not asked to log in to CIMPLICITY and the run-time data did not appear. This issue has been resolved. In Windows Server 2016 and Windows 10, when you run a web client with a user profile that is not configured in CIMPLICITY, you are asked to log in to CIMPLICITY and the run-time data appears. GE Digital 74

75 3.7 ISSUES RESOLVED: NETWORKING CIMPLICITY v9.5 SIM 8 Networking/ Viewing points from Viewer DE36850 SF When browsing points on a viewer node using Point Control Panel, the points configured on a server are not shown properly. When browsing points on a viewer node using Point Control Panel, the points configured on a server are now shown properly. Also, to resolve the issue, minor enhancements were done to Firewall Configuration Settings. Please refer to Changes to Firewall Configuration Settings section for more information CIMPLICITY v9.5 SIM 1 Server Redundancy/ Broadcasting Document Delivery/ UNC Path Issue DE17258 SF In a Server Redundant setup, restarting the primary node when the secondary is set as master causes broadcast error messages to be logged into system log. DE16463 SF When Mapped Network Drive path is used, the Document Delivery feature does not work properly. In a Server Redundant setup, restarting the primary node when the secondary is set as master, broadcast error messages are no longer logged into system log. The Document Delivery feature now supports UNC Paths in place of the Mapped Network Drive path. GE Digital 75

76 3.8 ISSUES RESOLVED: POINTS AND SCRIPTING CIMPLICITY v9.5 SIM 17 Basic Control Engine Scripting/ GetGroupLogArrayPtElem DE83006 SF Previously, if you made a call to a group log table using the object model GetGroupLogArrayPtElem (pointid), an error occurred. This issue has been resolved. No error occurs if you make a call to a group log table using the object model GetGroupLogArrayPtElem (pointid) CIMPLICITY v9.5 SIM 16 Points/ Cross Reference utility DE78060 SF Previously, several points whose screens were cross-referenced in a project were reported missing from the Cross Reference utility. This issue has been resolved. The points whose screens are cross-referenced in a project can now be found as the Cross Reference utility now also searches the subfolders of the screens CIMPLICITY v9.5 SIM 14 Basic Control Script/Mapping Drives DE51063 SF When a project on a remote server is opened, CIMPLICITY creates a mapped drive. When the remote connection to the project ended, the connection was not unmapped completely. When the remote connection to the project ends, the connection is now unmapped completely CIMPLICITY v9.5 SIM 13 Event Manager/ Hang Issues DE62459 SF When executing lot of C# Scripts, the Event Manager occasionally pauses and takes a long time to recover. When executing lot of C# Scripts, the occasional long duration pauses no longer occur and the Event Manager works properly. GE Digital 76

77 Event Manager/ Dynamic Script Updates Virtual Point/ Dynamic Value Updates DE66014 SF When modifying.net Scripts by setting the project to dynamic mode at runtime, if the script changes are done after point operations, then the script editor hangs and script updates are not persisted. DE66942 SF When making changes to a Virtual Point at Runtime by turning on the Dynamic Mode, the updated values are not saved properly. When modifying.net Scripts by setting the project to dynamic mode at runtime, if the script changes are done after point operations, then the script editor no longer hangs. The dynamic script updates are now persisted properly. When Virtual Point is updated at Runtime by turning on the Dynamic Mode, the changed value is now saved properly CIMPLICITY v9.5 SIM 12 Event Manager/ Long Point Names PTMDP/ Memory Leaks Points/ EMRP Crash Points/ Enumerations DE49532 SF When PointEvent.ID attribute of EMEvent is accessed at runtime, the name of tags configured with long names is not returned properly. DE58023 SF When a CIMPLICITY Project configured to read values from device points is put into Run Mode, Memory Leak issues are observed with the PTMDP module. DE57722 SF When starting a CIMPLICITY Project in Run Mode, EMRP Process crashes are observed if the EMRP Process is paused or restarted during project startup. DE55358 SF When new values are added to an enumeration point in dynamic mode at runtime, the newly added enumeration values are not accessible for dependent points in Point Control Panel. When PointEvent.ID attribute of EMEvent is accessed at runtime, the name of tags configured with long names now gets returned properly. When a CIMPLICITY Project configured to read values from device points is put into Run Mode, Memory Leak issues are no longer observed with the PTMDP module. When starting a CIMPLICITY Project in Run Mode, EMRP Process crashes are no longer seen if the EMRP Process is paused or restarted during project startup. When new values are added to an enumeration point in dynamic mode at runtime, the newly added enumeration values are now properly accessible for dependent points in Point Control Panel. GE Digital 77

78 3.8.6 CIMPLICITY v9.5 SIM 10 CLIE/ Importing Boolean Point Alarm Limits Points/ Accessing Array Elements Points/ Point Change Events Points/ Change Approval PTMRP/ Application Crash PTX_RP/ Memory Leaks DE47318 SF When importing Alarm Limits information for Boolean points using CLIE, the alarm limits are not imported properly into the project. DE43261 SF When accessing the elements of a point array at runtime in Point Control Panel for a CIMPLICITY Project, the value of the 0th element is shown as unavailable and value is not shown properly. DE35156 SF When a Point Change Event associated with Transition Set Action is configured for a project in Event Manager, disabling the event causes invalid error messages to be logged into status log. DE42781 SF When a Project configured with Change Approval settings is put into Run mode, performing set point operations processes Change Approval actions, but fails to log the information into database. DE41404 SF When executing a CIMPLICITY Project, occasional process crashes occur in PTMRP Process. DE44178 SF When reading points via script in a project, reading unavailable points information causes memory leaks in PTX_RP Process. When importing Alarm Limits information for Boolean points using CLIE, the alarm limits are now imported properly into the project. In case of failures, the associated errors/failures now get logged into the Project Log Folder. When accessing the elements of a point array at runtime in Point Control Panel for a CIMPLICITY Project, the value of the 0th element is now shown as available and value is shown properly. When a Point Change Event associated with Transition Set Action is configured for a project in Event Manager, disabling the event no longer causes invalid error messages to be logged into status log. When a Project configured with Change Approval settings is put into Run mode, performing set point operations now results in successful Change Approval actions and subsequent logging of information into database. When executing a CIMPLICITY Project, occasional process crashes no longer occur in PTMRP Process. When reading points via script in a project, reading unavailable points information no longer causes memory leaks in PTX_RP Process CIMPLICITY v9.5 SIM 9 Scripting/ Navigation DE40238 SF GE Digital 78

79 Toolbar Scripting Attempting to hide Child Bar of Navigation Bar via scripting by setting up the "NavLoadNoChildBar" to True does not work properly. "NavLoadNoChildBar" call is now obsolete. Use NavBarVisible flag Instead as shown in the script below: Sub NavLoadNoChildBar (cfgfile As String, startpath As String) Dim ocimscr As GefScreen Set ocimscr = CimGetScreen Points/ Point Object Scripting/ GefObject.Name Function Point Control Panel/ Timestamp Values Scripting/ Events Quick Watch/ Point Value Evaluation Scripting/ Saved Points DE41877 SF When modifying the point attribute information of a project via script, invoking the modify command using the keyword "MODIFIED" does not change the point attributes properly. DE40232 SF When a name with invalid characters are passed to GefObject.Name to set object name, no errors are shown to user. DE38736 SF When evaluating calculated points in Point Control Panel, the evaluation timestamps are not updated properly. DE38465 SF When debugging a script during runtime, the changes made to Event Information is not applied properly. DE38464 SF When debugging a script during runtime, Invalid characters are shown in Quick Watch Window while viewing point values. DE34439 SF When starting a project, the saved point information does not get loaded properly and causes calculated points to become unavailable in Point Control Panel. DE29518 SF ocimscr.navload cfgfile, startpath ocimscr.navbarvisible = False ' Disable navigation bar End Sub When modifying the point attribute information of a project via script, invoking the modify command using the keyword "MODIFIED" now updates the point attributes properly. When a name with invalid characters are passed to GefObject.Name to set object name, error message is shown in CimEdit, while errors are logged into application logs in CimView. When evaluating calculated points in Point Control Panel, the evaluation timestamps are now updated properly. When debugging a script during runtime, the changes made to Event Information is now applied properly. When debugging a script during runtime, point values are now shown properly in Quick Watch Window. When starting a project, the saved point information now gets loaded properly and calculated point information is shown properly in Point Control Panel. GE Digital 79

80 Scripting/ Point addition and Point deletion Events Editor/ Point ID Name When adding or deleting points in a project using scripting, the time taken to perform the operation is much more than that in previous versions. DE35653 SF When viewing points configured for events in Event Editor, invalid characters are shown in Point ID Field. When adding or deleting points in a project using scripting, the time taken to perform the operation is now similar to that in previous versions. When viewing points configured for events in Event Editor, invalid characters no longer appear in Point ID Field CIMPLICITY v9.5 SIM 8 EMRP/ Memory Leaks DE35668 SF When executing C# Scripts, Memory leaks are observed in EMRP Process, resulting in subsequent process crashes. When executing C# Scripts, Memory leaks are no longer observed in EMRP Process and process crashes do not occur CIMPLICITY v9.5 SIM 7 EMRP/ Application Crash DE29003 SF When EMRP Process is triggered at the start of project, Application crashes are logged when loading the dependent.net assemblies into memory. When EMRP Process is triggered at the start of project, Application crashes no longer occur when loading the dependent.net assemblies into memory. As part of the resolution, two new global parameters have now been added. Please refer to parameters for reloading.net Assemblies for more information CIMPLICITY v9.5 SIM 6 Point Translation/ Memory Growth Issues DE23049 SF When CimView opens a screen containing a trend object, and the /noscreenexit command line argument When CimView opens a screen containing a trend object, and the /noscreenexit command GE Digital 80

81 Points/ Points Browse Tool is used, then the PTX_RP process may experience a memory growth. DE19115; SF DE19118; SF When browsing points of a project from a Viewer, the point browser dialog crashes randomly. line argument is used, then the PTX_RP process memory growth no longer occurs. When browsing points of a project from a Viewer, the point browser dialog no longer crashes CIMPLICITY v9.5 SIM 5 PTMRP/ Application Crash Scripting/ Script Debugging Points/ PTQ_SNAP application Points/ Points Browse Tool DE18557 SF When a CIMPLICITY Project is put into run mode, PTMRP Process crash occurs and project does not run properly. DE18207 SF When debugging a script via script editor, the event information configured in editor cannot be retrieved using CimEmEvent.ObjectID method. DE18684 SF When ptq_snap application is run, the values for fully qualified local points are not read properly during first read. DE16921 SF When browsing points of a project in the Browse Tool, the enterprise points are not filtered properly when the filter is set to view points for a specific device. When a CIMPLICITY Project is put into run mode, PTMRP Process no longer crashes and project runs properly. When debugging a script via script editor, the event information configured in editor can now be retrieved using CimEmEvent.ObjectID method and script debugging can be done successfully. When ptq_snap application is run, the values for fully qualified local points are now read properly. When browsing points of a project in the Browse Tool, the enterprise points are not shown in the Browse Tool when the filter is set to view points for a specific device CIMPLICITY v9.5 SIM 3.NET Scripting/ Updating Array Elements DE18679 SF When array elements are modified using SetRawArray and SetArray from.net Scripts, the array elements values do not updated properly. When array elements are modified using SetRawArray and SetArray from.net Scripts, the array elements values now get updated properly. GE Digital 81

82 Basic Scripting/ Scripting User Interface Point Management/ Process Crash.NET Scripting/ Intellisense Support Delta Accumulator Point Values DE18558 SF Events created in dynamic mode at runtime do not get listed in Basic Scripting User Interface. DE18272; SF DE18479; SF When opening a CimView screen, configured with expressions, in runtime, PTMRP Process crashes are observed intermittently. DE17679 SF When large.net Scripts are being edited, the built-in intellisense support responds very slowly and causes unnecessary delays. DE18550 SF When a delta accumulator point value is updated by configured expression point or by reset point, the updated value is not saved properly. Events created in dynamic mode at runtime now get listed in Basic Scripting User Interface. When opening a CimView screen, configured with expressions, in runtime, PTMRP Process crashes are no longer seen. An option has now been added in the "Tools" menu to enable/disable the intellisense support. The editing of scripts will now be faster when intellisense is disabled. When a delta accumulator point value is updated by configured expression point or by reset point, the updated value is now saved properly. Points/ Point Creation Timestamp On restarting the project, the delta accumulator point value is not updated properly. DE18661 SF When a point created in CIMPLICITY project is configured to be logged into Historian configured with "Time Assigned by" set to "Collector", the timestamp information is stored based on source instead. On restarting the project, the delta accumulator point value now gets updated properly. When a point created in CIMPLICITY project is configured to be logged into Historian configured with "Time Assigned by" set to "Collector", the timestamp information is now stored based on collector. Please refer to New Features/Enhancements section for more information about HIST_TIME_STAMP_TYPE parameter that has now been provided to control the way timestamp information is processed CIMPLICITY v9.5 SIM 2 EMRP/ Random Crashes DE18563 SF When custom scripts configured using.net scripting languages are being When custom scripts configured using.net scripting languages are being executed at GE Digital 82

83 Point Control Panel/ Set Empty String EMRP/ Crash Issue.NET Scripting/ Invalid ActionIDs executed at runtime, EMRP Process crashes at random. DE18204 SF When Point Control Panel is used to set empty string value to a String Point, the empty string does not get assigned to the point. DE14513 SF When using Event Manager functionality, process crashes were observed. DE18346 SF When Cimplicity.CimGetEMEvent().ActionID is used in a Script, incorrect action ID is returned. runtime, EMRP Process crashes no longer occur. When Point Control Panel is used to set empty string value to a String Point, the empty string now gets assigned to the point as expected. Application crashes no longer occur when using Event Manager functionality. When Cimplicity.CimGetEMEvent().ActionID is used in a Script, valid action ID is now returned CIMPLICITY v9.5 SIM 1 CIMPLICITY Points/ Reset Point Timestamps CimProject/ Project Archiving.NET Scripting/ Persistence of data Configuration Object Model/ Memory Leaks EMRP/ Column Sorting DE17032 SF When a CIMPLICITY point configured with reset point configured updated, the time stamp information is not updated properly. DE17439 SF Archiving of information using CimProject.ArchiveProject() function does not work properly DE17273 SF When a.net control object with event configured is used on a screen, the script entry point information configured for the object does not get persisted. DE17265 SF When objects are created using the Configuration Object model, memory leaks are observed. DE16682 SF When a CIMPLICITY point configured with reset point configured updated, the time stamp information is now updated properly. Archiving of information using CimProject.ArchiveProject() function now works as expected. When a.net control object with event configured is used on a screen, the script entry point information configured for the object now gets persisted properly. When objects are created using the Configuration Object model, memory leaks are no longer seen. GE Digital 83

84 EMRP/ Script Execution EMRP/ Exception Handling EMRP/ Object names EMRP/ Performance Issue Script Editor/ Intellisense Support EMRP/ Alarm Events Virtual Points/ Dynamic mode Point Duplication EMRP/ Application Crash While the list of event/actions are being loaded, operations to add a column and/or performing sort operation on the Events or actions in the Event Editor causes event editor to crash. DE17254 SF When an event s Action in a script is configured to run C# Script that has the same name as script s Class name, Script do not execute properly. DE16751 SF When the Try/Catch Exception blocks are used in scripting, information about the point causing the exception is not available. DE15590 SF When Event ID/Action ID is fetched from scripts, incorrect object names are returned. DE16258 SF When scripts containing events are used in CIMPLICITY Project, memory growth and performance degradation are observed. DE16254 SF When editing.net scripts, the intellisense functionality does not work as expected. DE16065 SF While editing events using the Event Editor, wildcard characters are not working properly. DE16565 SF When a virtual point is duplicated in dynamic mode, the duplicated points do not get updated properly. DE17263 SF When multiple scripts are accessing the same script or point simultaneously, the Event Manager process can crash randomly. Event editor crashes no longer occur when adding a column and/or sorting on the Events or actions in the Event Editor while the list is loading. Execution of scripts now happen properly for cases where an event s Action configured to run C# Script that has the same name as script s Class name. When the Try/Catch Exception blocks are used in scripting, information about the point causing the exception is now made available. When Event ID/Action ID is fetched from scripts, object names are now returned correctly. When scripts containing events are used in CIMPLICITY Project, memory growth and performance degradation are no longer seen. When editing.net scripts, the intellisense functionality now works as expected. While editing events using the Event Editor, wildcard characters now work properly. Duplicate points that are created dynamically will now update properly. When multiple scripts are accessing the same script or point simultaneously, the Event Manager process no longer crashes. GE Digital 84

85 3.9 ISSUES RESOLVED: PROFICY INTEGRATION CIMPLICITY v9.5 SIM 13 ipower/ Buffered Reports DE60551 SF When processing multiple updates for a device point from an IEC buffered report through PDS, the derived point does not process all the available updates. When processing multiple updates for a device point from an IEC buffered report through PDS, the derived point now processes all the available updates as expected CIMPLICITY v9.5 SIM 3 ipower/ Copying Class Objects DE18560 SF When running ipower, attempting to copy a class object from one project to another, it results in operation failure error messages and objects in source project get deleted. When running ipower, attempting to copy a class object from one project to another no longer results in operation failure error messages and objects in source project do not deleted during the copy operation CIMPLICITY v9.5 SIM 1 ipower/ Copying Class Objects DE16072 SF When running ipower, attempting to copy a class object from one project to another causes workbench to hang during the copy operation. When running ipower, copying a class object from one project to another happens successfully and workbench no longer hangs during the copy operation. GE Digital 85

86 3.10 ISSUES RESOLVED: PROFICY PROCESS SYSTEMS CIMPLICITY v9.5 SIM 16 Object Builder/ Object path DE78065 SF Previously, when building CIMPLICITY PPS objects, if the EGD configuration server resided on a remote node, the path to building PPS objects was not found and an error occurred. This issue has been resolved. For PPS version 3.5 and above, CIMPLICITY PPS objects can be built without errors even when the EGD configuration server resides on a remote node CIMPLICITY v9.5 SIM 11 Object Builder/ Class Generation DE42038 SF When creating classes using the Object Builder, certain types of classes and objects of those classes are not created properly. When creating classes using the Object Builder, the classes and objects of those classes are now created properly CIMPLICITY v9.5 SIM 7 Proficy Process Systems/ Rate of Change Alarms Suppression DE19544; SF DE19548; SF DE19552; SF When Rate of Change (ROC) alarms are suppressed, from PPS Project, the suppressed alarms are still displayed in CIMPLICITY's Alarm Viewer. The suppressed Rate of Change (ROC) alarms from PPS Project, are no longer displayed in CIMPLICITY's Alarm Viewer. Note: 1. For existing projects, the ALARM_A class has to be imported manually from the installation folder. [<installation path>\proficy CIMPLICITY\classes\pps\ALARM_A.soc] 2. New project will not require any additional actions as the updated ALARM_A file will be available for use. GE Digital 86

87 CIMPLICITY v9.5 SIM 1 Object Builder/ Events and Actions DE16654; SF DE16658; SF When creating classes using the Object Builder, Event/ Action definitions do not get added to PPS Classes properly. Event/ Action definitions now get added to PPS Classes properly and objects are created properly by the Object Builder. GE Digital 87

88 3.11 ISSUES RESOLVED: PROJECT AND SYSTEM MANAGEMENT CIMPLICITY v9.5 SIM 17 Workbench/ Broadcasting Sessions DE78075 SF Previously, if you specified invalid credentials when starting broadcasting sessions, both the project log and systems logs displayed error messages. This issue has been resolved. Now, when you specify invalid credentials when starting broadcasting sessions, only the project log displays an error message CIMPLICITY v9.5 SIM 13 Workbench/ Performance Issues DE66289 SF When deleting large number of points from the Workbench, the time taken to complete the point delete operation is very long, and leads to drop in application performance. When deleting large number of points from the Workbench, the time taken to complete the point delete operation is similar that in previous versions of CIMPLICITY. Also, there is appreciable improvement in application performance CIMPLICITY v9.5 SIM 12 Workbench/ Object Browsing DE57942 SF When using the Object Browser tool to browse Class Objects, the usage of Wild Cards at start or within the search string does not browse the class objects in the project properly. When using the Object Browser tool to browse Class Objects, the usage of Wild Cards at start or within the search string now browses the class objects in the project properly CIMPLICITY v9.5 SIM 11 Workbench/ Application Crash DE52644 SF When Class Objects are being deleted from Workbench, random application crashes are observed. Workbench application crashes no longer occur when Class Objects are being deleted from Workbench. GE Digital 88

89 CIMPLICITY v9.5 SIM 10 Navigation/ Navigation Configuration Utility DE52604 SF-NA When using Navigation Configuration Utility to configure Screen Navigation, Screen Layout or Screen Deployment, the Navigation Configuration tool is displayed in Read-Only mode on some Operating Systems. When using Navigation Configuration Utility to configure Screen Navigation, Screen Layout or Screen Deployment, the Navigation Configuration tool is now displayed in Edit Mode CIMPLICITY v9.5 SIM 9 Workbench/ Application Crash DE39982 SF When configuring OPC Client Device, workbench crashes are observed. When configuring OPC Client Device, workbench crashes are no longer seen. Workbench/ Filtering Points Workbench/ Project Start Stop Time DE38593 SF When viewing points in Workbench, filter settings are not applied when displaying points. DE18673 SF When starting/stopping an upgraded project or a new project, the time taken to complete the operation is much higher than that in older versions. When viewing points in Workbench, filter settings are now applied properly and points are displayed properly based on the configured filter options. When starting/stopping an upgraded project or a new project, the time taken to complete the operation is now similar to that in older versions CIMPLICITY v9.5 SIM 8 Workbench/ Project Properties DE28671 SF When making modifications to Project Properties, Configuration changes made to project do not get saved properly and errors get reported. When making modifications to Project Properties, Configuration changes made to project now get saved properly and errors are no longer reported. GE Digital 89

90 CIMPLICITY v9.5 SIM 7 Workbench/ Master Data Folder Comparison DE25497; SF DE25499; SF When comparing master and data folders, folder comparison failures are reported due to unavailable Server Configuration file. When comparing master and data folders, the folder comparison utility should omit comparison of specific files, including the Server Configuration file. Now, invalid folder comparison errors no longer occur CIMPLICITY v9.5 SIM 6 Workbench/ WebView Broadcast Sessions DE20164 SF When referencing a screen on a remote UNC path in a broadcast session, User Interface to configure white-listing for the broadcast session is not accessible. When referencing a screen on a remote UNC path in a broadcast session, the whitelisting for the broadcast session can now be configured CIMPLICITY v9.5 SIM 5 Workbench/ SIM Installation Workbench/ AMV Sound Manager Workbench/ Project DE17066 SF When installing a SIM for 9.5 Version on a machine, installation issues occur and SIM installation process gets halted. DE18927 SF When a CIMPLICITY Project is configured using Alarm Sound Manager application to play audio files while an alarm is active, the alarm audio files are not played as expected and following behaviors are observed: 1. Alarm Sound Files are not played in succession while alarm is active 2. Alarm Sound Files are restarted each time the associated point value changes. 3. The interval between each looping is not consistent. DE16132 SF Installation a SIM for 9.5 Version now happens successfully on a machine without any issues. The behaviors reported below can now be managed by setting up a new "Project Level" Configuration Parameter: 1. Alarm Sound Files are not played in succession while alarm is active 2. Alarm Sound Files are restarted each time the associated point value changes. 3. The interval between each looping is not consistent. AMV_SOUND_LOOP Configuration Parameter now can be used to ensure that the alarm sound audio files are played properly. GE Digital 90

91 Upgrade Crash When a project created in newer version is opened in an older version of CIMPLICITY, workbench crash occurs and users are not provided appropriate notification about the error. When a project created in newer version is opened in an older version of CIMPLICITY, workbench no longer crashes. Also, users are notified about the inability to open a project created in newer version CIMPLICITY v9.5 SIM 4 Workbench/ Project Login Workbench/ Log Viewer DE15454 SF When login operation is preformed using script functions, user is prompted for login credentials even when necessary credentials are provided through script. DE18776 SF When viewing log entries in Log Viewer, not all logged entries are displayed. User will now be able to successfully login using script functions by providing required credentials through script. When viewing log entries in Log Viewer, all logged entries are now displayed. Workbench/ Project Configuration Update Workbench/ Application Process Crash Workbench/ Domain Integration DE18872 SF When starting an upgraded project, the user is requested to perform configuration update for each project start operation, even when no modifications are done. DE18868; SF DE18870; SF When running a CIMPLICITY Project, occasional PTX_RP Process crashes occur. DE18404 SF When Domain Integration is enabled for a project and a user logs into the project at runtime, then the user is not allowed to stop the project. Any attempt to stop the project results in multiple requests for user to login and user is not allowed to stop the project. When starting an upgraded project, the user is now requested to perform configuration update at project start only when modifications are done. When running a CIMPLICITY Project, occasional PTX_RP Process crashes no longer occur. When Domain Integration is enabled for a project and a user logs into the project at runtime, the user will now able to stop a project without any errors CIMPLICITY v9.5 SIM 3 Workbench/ UR DE18095 SF GE Digital 91

92 Resource Leaks When a project with domain integration enabled, is run for a long time, resource leaks are observed with the User Registration process leading to subsequent crash. When a project with domain integration enabled, is run for a long time, resource leaks are no longer seen and process crashes do not occur anymore CIMPLICITY v9.5 SIM 2 Workbench/ Log Viewer Workbench/ Domain Authentication DE18015 SF When a log file generated on a node has more than the standard limit of 1000 records is opened on a different node, the log file fails to get opened. No warning messages are shown to user. DE17773 SF When Domain Authentication component is used in a project, ill-formatted error message is logged into system log if a role is not identified with a user. When a log file generated on a node has more than the standard limit of 1000 records is opened on a different node the log file now gets opened. Also, the number of records shown is determined by the following conditions" 1. The first 1000 records are shown at maximum, if the LOG_MAXRECORDS entry is not available. 2. if LOG_MAXRECORDS entry.is available, then it will display the records based on the limit specified. When Domain Authentication component is used in a project, the error message logged into system log, if a role is not identified with a user, will now contain details of the user for which it failed to find a role CIMPLICITY v9.5 SIM 1 Workbench/ Project Performance Issues Workbench/ Project Upgrade DE16728 SF When an enterprise project is upgraded to 9.5 Version, performance degradation issues are seen and the project s workbench becomes eventually becomes unresponsive and hangs. DE17648 SF When a project configured with S90 Triplex driver is upgraded to 9.5 version, CIMPLICITY Workbench request for project upgrade When an enterprise project is upgraded to 9.5 Version, performance degradation issues are no longer seen and the project s workbench does not go unresponsive or hangs anymore. Once upgraded to 9.5 Version, a project configured with S90 Triplex driver can now be put into Run Mode successfully. GE Digital 92

93 continually and does not allow to put the project into Run Mode. Workbench/ Device Points Workbench/ Time Zone and DST Changes DE16437 SF When listing the points of a project, the device points would take a significant time to load/display. DE16115 SF When a project is running and time zone changes occur, some of the system variables do not update properly until the project is restarted. Loading and displaying of device point data no longer takes a significant period of time. When the project is running and time zone changes occur, system variables now update properly. GE Digital 93

94 3.12 ISSUES RESOLVED: RECIPES CIMPLICITY v9.5 SIM 12 Recipes/ Text Data Type Variables DE51060 SF When a CIMPLICITY Project, configured with Recipes having virtual points of Text Data Type, is put into run mode, the values of variables are not properly updated in the recipe control. When a CIMPLICITY Project, configured with Recipes having virtual points of Text Data Type, is put into run mode, the values of variables now get properly updated in the recipe control CIMPLICITY v9.5 SIM 10 Recipes/ Import Recipes DE40375 SF When importing recipes into a CIMPLICITY Project that already has recipes configured, the import operation fails randomly. When importing recipes into a CIMPLICITY Project that already has recipes configured, the import operation now completes successfully without any failures CIMPLICITY v9.5 SIM 4 Recipes/ Recipe Upload - Corruption Issue DE15475 SF When uploading a recipe into a CIMPLICITY project, the string values are not uploaded properly. When uploading a recipe into a CIMPLICITY project, the string values are now uploaded properly. GE Digital 94

95 3.13 ISSUES RESOLVED: SERVER REDUNDANCY CIMPLICITY v9.5 SIM 17 Server Redundancy/ IP address DE81457 SF Previously, in the Project Properties window, if you selected the Server Redundancy option, and then selected the Use this IP address option, the server redundancy function stopped working. This issue has been resolved. In the Project Properties window, if you select the Server Redundancy option, the Use this IP address option is now disabled CIMPLICITY v9.5 SIM 13 Server Redundancy/ Primary Server Failover DE61236 SF When a fail-over occurs due to network failure, the Secondary Server switches over to Master Mode. On restoration of network, when the Primary Server is made the master, the values of $ROLE and $USER become unavailable at times. When a fail-over occurs due to network failure, the Secondary Server switches over to Master Mode. On restoration of network, when the Primary Server is made the master, the values of $ROLE and $USER will now be available without any issues ISSUES RESOLVED: STATISTICAL PROCESS CONTROL (SPC) CIMPLICITY v9.5 SIM 8 SPC/ Duplicate Data Records DE31620 SF When using SPC functionality that has data tables configured, the SPCVARX Table gets updated with duplicate records from SPC Table. When using SPC functionality that has data tables configured, the SPCVARX Table no longer gets updated with duplicate records from SPC Table CIMPLICITY v9.5 SIM 5 DE17891 GE Digital 95

96 SPC/ Data Import/Export SF When SPC data exported from a project using SPC tool is imported into another project, the import process fails to import the exported data successfully. The SPC data exported from a project using SPC tool can now be successfully imported into another project CIMPLICITY v9.5 SIM 1 SPC/ Moving Range Charts DE16755 SF SPC Moving Range chart does not display values for the selected range. SPC Moving Range chart now displays values for the selected range. GE Digital 96

97 3.15 ISSUES RESOLVED: TRACKER/ORDER EXECUTION MANAGEMENT CIMPLICITY v9.5 SIM 17 TADBH Maintenance/ Deadlock RCO Site/ Ready Point RCO Site/ Tracker Configuration UI Tracker/ Duplicate Item ID DE72386 SF Previously, the Historical TADB Maintenance job entered a deadlock state during execution and stopped multiple times. DE80371 SF Previously, if an RCO site was triggered, it caused errors to occur every 10 seconds. This issue occurred only when a Ready Point was configured, but not set to the Ready value. DE80369 SF Previously, if you edited an RCO site using an RCO Solve block, the Tracker Configuration UI stopped responding. DE80067 SF Previously, when items with the same ID from different Tracker projects were moved through the PRT_UI utility, the item in the targeted project was deleted without notifying you. This issue has been resolved. The Historical TADB Maintenance job now runs on schedule without entering a deadlock. This issue has been resolved. If an RCO site is triggered with a Ready Point configured, but not set to the Ready value, no errors occur. This issue has been resolved. If you edit an RCO site using an RCO Solve block, the Tracker Configuration UI functions as expected. This issue has been resolved. Now, when items with the same ID from different Tracker projects are moved through the PRT_UI utility, a message appears, asking you to choose if the item in the targeted project should be deleted CIMPLICITY v9.5 SIM 15 PRT_ITEM_STATUS/ Graphic Display point Tracker/ Range Maintenance Error DE72386 SF Previously, the Graphic Display point did not display the value of the PRT_ITEM_STATUS attribute in Point Control Panel. DE56555 SF Previously, in a Tracker application that did not use TADB, when you used the Tracker Configuration utility to This issue has been resolved. The Graphic Display point now displays the value of the PRT_ITEM_STATUS attribute in Point Control Panel. This issue has been resolved. In a Tracker application that does not use TADB, when you use the Tracker GE Digital 97

98 access Range Maintenance and create a range, a blank error message appeared. Configuration utility to access Range Maintenance and create a range, a meaningful error message appears CIMPLICITY v9.5 SIM 14 Tracker/ PRTV Tracker/PRT_IMPORT.EXE Performance DE62622 SF When the PRTV command is run for a file in a Tracker project, duplicate records are created. DE66720 SF The performance of the process of running the prt_import.exe file degrades during import. When the PRTV command is run for a file in a Tracker project, duplicate records are not created. The performance of the process of running the prt_import.exe file during import has improved by approximately 96% CIMPLICITY v9.5 SIM 13 Item Agent/ Where Clause TRK_DC/ Process Crash and Memory Leak DE63565 SF When the Tracker Item Agent is used to restrict the item collection returned by making use of Where clause, no items are returned. DE58041 SF When running a tracker project for a long time, memory leaks and occasional process crashes were observed on TRK_DC module When the Tracker Item Agent is used to restrict the item collection returned by making use of Where clause, the restricted set of items are now returned properly. When running a tracker project for a long time, memory leak issues no longer occur now and the occasional process crash issues are no longer observed on TRK_DC module CIMPLICITY v9.5 SIM 11 TADB/ PRT_TADB_DIFF Errors DE41719 SF When items are being moved between regions, PRT_TADB_DIFF.exe does not When items are being moved between regions, PRT_TADB_DIFF.exe now reports GE Digital 98

99 report mismatch in item attribute values between PRT and TADB properly. mismatch in item attribute values between PRT and TADB properly CIMPLICITY v9.5 SIM 10 TADBH/ Database Trustworthy Settings DE53601 SF When upgrading a Tracker project configured TADBH, the Trustworthy Flag gets enabled automatically. This could lead to security concerns. When upgrading a Tracker project or creating a new Tracker project that has TADBH configured, the Trustworthy Flag no longer gets enabled by default CIMPLICITY v9.5 SIM 9 TADB/ Database Trustworthy Settings TADB/ Database Access DE18307 SF When TADB Database is configured for a project, the Trustworthy Flag gets enabled automatically. This could lead to security concerns. DE33541 SF When accessing TADB Database, connectivity issues are observed along with occasional application crashes. When TADB Database is configured for a project, the Trustworthy Flag no longer gets enabled automatically. The functionality works as intended even with this flag turned off. When accessing TADB Database, valid error messages are now shown for connectivity issues. Also, application does not crash during normal operations CIMPLICITY v9.5 SIM 8 PRT_EXPORT.EXE/ Memory Leaks DE33245 SF When using prt_export.exe to export data, memory leaks occur and application crash/hangs are seen. When using prt_export.exe to export data, memory leaks no longer occur and application crash/hangs are not observed CIMPLICITY v9.5 SIM 6 DE18951 GE Digital 99

100 PRT_UI/Serialized Items Reordering Tracker Configuration UI/ Historical TADB SF When PRT_UI application is used to reorder the regions that contain nonserialized items, for a Tracker project that has TADB enabled, the reordering does not occur properly. DE18698 SF When using Tracker Configuration UI to enable/disable TADB replication in Historical TADB, SQL Stored Procedures do not get executed properly and failures occur. When PRT_UI application is used to reorder the regions that contain non-serialized items, for a Tracker project that has TADB enabled, the reordering now happens properly. When using Tracker Configuration UI to enable/disable TADB replication in Historical TADB, SQL Stored Procedures now get executed properly and failures no longer occur CIMPLICITY v9.5 SIM 5 Tracker/ PRT_EXPORT.exe process crash Trkcollector.exe/ Application Crash Tracker/ PRT_UI process crash DE18843 SF When using prt_export.exe to export data, application crash occurs if NO_TRKPRO extension is used in the command line. DE18932 SF When an application configured with Tracker is run, TrkCollector application crash occurs occasionally. DE16331 SF When a tracker project is run with PRT_UI /L command line argument, PRT_UI crash occurs when attempting to advance an item in the PRT_UI When using prt_export.exe to export data, application crash no longer occurs if NO_TRKPRO extension is used in the command line. When an application configured with Tracker is run, TrkCollector application occasional crashes no longer occur. When a tracker project is run with PRT_UI /L command line argument, PRT_UI crash no longer occurs when attempting to advance an item in the PRT_UI CIMPLICITY v9.5 SIM 3 Tracker/ PRT_DC process crash Tracker/ PRT_DC process crash DE13855 SF When a tracker route is configured with only a destination region or only a source region, triggering route transfer will cause PRT_DC process to crash. DE18672 SF When a tracker project is run, PRT_DC process crashes intermittently. When a tracker route is configured with only a destination region or only a source region, triggering route transfer will no longer cause PRT_DC process to crash. When a tracker project is run, PRT_DC process crashes no longer occur. GE Digital 100

101 CIMPLICITY v9.5 SIM 2 BCO Objects/ ASCII Broadcast Forms DE17993 SF When broadcasting ASCII Broadcast forms containing BCO objects that refer to STRING_80 points containing a string longer than 63 characters, script crashes are observed. When broadcasting ASCII Broadcast forms containing BCO objects that refer to STRING_80 points containing a string longer than 63 characters, script crashes no longer occur. GE Digital 101

102 3.16 ISSUES RESOLVED: TRENDS AND DGR CIMPLICITY v9.5 SIM 16 ptmap COM message filter/ CimView crash DE76974 Internal Previously, Trend disabled the ptmap COM message filter, because of which CimView stopped responding. This issue has been resolved. CimView now functions as expected as Trend no longer disables the ptmap COM message filter CIMPLICITY v9.5 SIM 14 Trend/ Timestamp Display Format Trend/ Timestamp Display Format DE69851 SF When trend line data is saved from trend control, any data associated with the time zone displays a time stamp in the local server s time zone. DE69852 SF When you increment the tick count in trend view, the tick label displays a time stamp in the local server s time zone. When trend line data is saved from trend control, any data associated with the time zone displays a time stamp converted to the trend control s time zone. When you increment the tick count in trend view, the tick label displays a time stamp converted to the trend view s time zone CIMPLICITY v9.5 SIM 13 Trend/ Reference Line Exports DE44669; SF DE46920; SF When exporting Reference Line Information from Trend object, filenames more than 8 characters cannot be specified. When exporting Reference Line Information from Trend object, filenames with more than 8 characters can now be used CIMPLICITY v9.5 SIM 8 DE33414 SF GE Digital 102

103 Trend/ Line Types On a redundancy enabled project, a trend object that is configured to display point data from an SQL Database, fails to read point information from SQL Database at runtime On a redundancy enabled project, a trend object that is configured to display point data from an SQL Database, now successfully read point information from SQL Database and plots trend at runtime CIMPLICITY v9.5 SIM 6 Trend/ AddLoggedLine Method Trend/ Historian Line Types DE12535 SF When a project configured with a popup screen having a Trend Object on it, is launched at runtime, the trendline is not drawn properly at times if a script is configured to add a DynPointLine to the trend object. DE19282 SF When a screen containing a trend object that is configured with Historian and Historian Expression line types is viewed in runtime, the configured lines are not drawn properly. When a project configured with a popup screen having a Trend Object on it, is launched at runtime, the trendline is now drawn properly if a script is configured to add a DynPointLine to the trend object. When a screen containing a trend object that is configured with Historian and Historian Expression line types is viewed in runtime, the configured lines are now drawn properly CIMPLICITY v9.5 SIM 4 Quick Trend/ User DSNs DE7637; SF DE7653; SF If a large number of lines were supposed to display on a QuickTrend chart while Server Redundancy was enabled, the trend chart would often not display the lines or correct database values. QuickTrends will now successfully display multiple lines when Server Redundancy is enabled. Quick Trend/ User DSNs Note: it was indeterminate as to which lines would display values. At times QuickTrends would recover from an incorrect display; other times it did not. DE12537; SF DE18156; SF When QuickTrend tool is used to view trending of values, User DSNs created during the trending operations do not When QuickTrend tool is used to view trending of values, User DSNs created during the trending operations get deleted properly and there is no effect on machine's performance. GE Digital 103

104 DGR/ Replay Freeze Issue get deleted, resulting in reduced machine performance levels. DE18779 SF When transition is made from normal mode to DGR mode at runtime for a screen that references multiple projects, and one of the referenced projects does not log data to any database (SQL or Historian), DGR will freeze at the start of replay. When transition is made from normal mode to DGR mode at runtime for a screen that references multiple projects, and one of the referenced projects does not log data to any database (SQL or Historian), DGR will no longer freeze at the start of replay CIMPLICITY v9.5 SIM 3 Trend/ User Login Trend/ Historian Line Types Trend/ AddLoggedLine Method DE18710 SF When a Trend control used on a screen has historian logged points configured, multiple login requests are shown to user. DE18688 SF When a line referring to Historian point, configured with Engineering Units (EU), is added to the trend object, and is set to display the EU value for the slider, the EU value is not displayed. DE18656 SF When lines from SQL database table are added to trend object with a call to "AddLoggedLine", rapidly switching screens causes "Table name could not be validated. xxx(table name)" error to occur randomly. Also, on acknowledging this error, the trend line does not get successfully added in the trend chart. When a Trend control used on a screen has historian logged points configured, multiple login requests are no longer shown to user. When a line referring to Historian point, configured with Engineering Units (EU), is added to the trend object, and is set to display the EU value for the slider, the EU value is now displayed properly. The Table name validation error no longer occur when rapidly switching between screens and the trend line now gets successfully added in the trend chart. GE Digital 104

105 CIMPLICITY v9.5 SIM 2 Trend/ DeleteTrendLine Method DE17697 SF When "DeleteTrendLine" method of the trend object is used to delete a trend line from the runtime configuration, the trend line does not get deleted from the trend object. When "DeleteTrendLine" method of the trend object is used to delete a trend line from the runtime configuration, the trend line now gets deleted properly from the trend object CIMPLICITY v9.5 SIM 1 Trend/ Timestamp Display Format Trend/ Historian Line Types DE16957 SF When displaying trending information, the ActiveX Trend object displays date in invalid format DE7860 SF When plotting trend for Interpolated lines, the samples do not get plotted properly for time durations that are greater than an hour. When displaying trending information, the ActiveX Trend object now displays date in the configured format Trend for Interpolated lines with sample intervals beyond an hour now get plotted properly. GE Digital 105

106 4 KNOWN ISSUES Known issues in the CIMPLICITY V9.5 release are as follows. Known Issues: 1. When a screen containing multiple OLE Objects is opened in CimView application for editing, attempting to delete text from an OLE Object results in text being deleted in a different OLE Object. 2. Starting SIM 10 for 9.5 Version, the fixes for value accumulator related issues have been reverted for couple of scenarios. The fixes will be added back once the additional scenarios are validated. Useful Information: 1. The point values are treated as 8-Byte REALs and the values will get converted to 8-Byte REALs internally by CIMPLICITY. GE Digital 106

107 5 GENERAL INFORMATION 5.1 MCAFEE ANTI-VIRUS DETAILS This SIM has been verified against the following version of McAfee Anti-Virus Application: Parameter Version Additional Information Number McAfee Agent Last security update check: 8/6/2018 4:26:17 PM Last agent-to-server communication: 8/6/2018 4:03:32 PM McAfee GTI Proxy Agent Language: English (United States) McAfee Host Intrusion Prevention McAfee VirusScan Enterprise + AntiSpyware Enterprise Scan engine version (32- bit) Scan engine version (64- bit) 8.0 Build date: Tuesday, April 18, ( ) Build Number: Security Content Version: Security Content Created On: Wednesday, July 4, 2018 Patch: 9 Build date: 3/30/2017 DAT version DAT Created on: 8/5/2018 Buffer Overflow and Access Protection DAT version 750 GE Digital 107

108 5.2 WEBSPACE WebSpace Error: The publisher is not allowed per license agreement. Symptom When attempting to connect a WebSpace client to a system running CIMPLICITY 9.0/9.5 an error occurs: "The publisher is not allowed per license agreement.". Upon the error, the client session is terminated and it is not possible to connect. Environment Primary Product Module: WebSpace Primary Product Version: 8.2/9.0/9.5 Primary Product OS: All Operating Systems Cause This problem was introduced by the release of CIMPLICITY 8.2 SIM 47 (or newer), CIMPLICITY 9.0 SIM 19 (or newer), CIMPLICITY 9.5 SIM 4 (or newer). A change was made in these SIM's that changed the way Digital Signatures for installed files was handled. After the introduction of these SIM's then a fix is also required on the WebSpace systems in order to allow for proper functionality. Resolution To resolve the problem, two updates must be applied (in order): 1. Proficy WebSpace (if it has not already been applied). Note that this update must be applied first before it is possible to install/use WebSpace Compatibility Update Proficy WebSpace Compatibility Update 4: Proficy WebSpace Compatibility Update 4 (64 bit): PWS48_CompatibilityUpdate_004_x64. The recommendation is to install WebSpace , reboot, then install Compatibility Update 4, and then reboot. When complete, this should resolve the issue and allow client sessions to connect again to the WebSpace Server. GE Digital 108