cimplicity 9.0 important product information

CIMPLICITY 9.0 Important Product Information

SIM 28

April 25, 2018

GE Digital 2

Contents

Purpose of this Document ...................................................................................................................................... 12

1 Installation ............................................................................................................................................................ 12

2 New Features and Enhancements ............................................................................................................. 13

2.1 Alarms ................................................................................................................................................................ 13

2.1.1 CIMPLICITY v9.0 SIM 7: Alarm Message – Truncation Limits .............................................. 13

2.1.2 CIMPLICITY v9.0 SIM 15: Alarm Properties .......................................................................... 13

2.1.3 CIMPLICITY v9.0 SIM 20: Alarm Sound Manager Options .................................................... 14

2.2 Change Management .................................................................................................................................. 15

2.2.1 CIMPLICITY v9.0 SIM 1: Auto Login to Change Management Projects ................................ 15

2.2.2 CIMPLICITY v9.0 SIM 1: Enhanced Audit Trail ...................................................................... 15

2.3 CimEdit/CimView .......................................................................................................................................... 16

2.3.1 CIMPLICITY v9.0 SIM 12: “NoScreenExit” Commandline Parameter................................... 16

2.3.2 CIMPLICITY v9.0 SIM 16: “StripDebounce” Commandline Parameter ................................ 16

2.4 Configuration of Auto Login for Trusted Users ................................................................................ 17

2.4.1 CIMPLICITY v9.0 SIM 4: Configuring Auto Login for Trusted Users ..................................... 17

2.4.2 CIMPLICITY v9.0 SIM 7: Auto Login Support for Trusted Users - Configuration Settings ... 18

2.5 Database Logging/Historian..................................................................................................................... 22

2.5.1 CIMPLICITY v9.0 SIM 1: Individual Point Logging ................................................................. 22

2.5.2 CIMPLICITY v9.0 SIM 2: Historian/Enumerated Points ........................................................ 23

2.5.3 CIMPLICITY v9.0 SIM 2: Point Logging/Same Timestamp .................................................... 24

2.5.4 CIMPLICITY v9.0 SIM 8: Sequence Numbering ..................................................................... 26

2.6 Expression Editor Enhancements .......................................................................................................... 27

2.6.1 CIMPLICITY v9.0 SIM 7: Expressions Editor – Quality Operations ....................................... 27

2.6.2 CIMPLICITY v9.0 SIM 17: Wait Time Configuration .............................................................. 27

2.6.3 CIMPLICITY v9.0 SIM 17: Pre-Terminate Scripting Support ................................................. 27

2.7 Network Global Discovery ......................................................................................................................... 28

2.7.1 CIMPLICITY v9.0 SIM 1: Proficy Global Discovery Server ..................................................... 28

2.7.2 CIMPLICITY v9.0 SIM 1: Proficy Global Discovery Server Agent .......................................... 28

2.7.3 CIMPLICITY v9.0 SIM 1: OPC UA Security Setup Tool ........................................................... 29

2.7.4 CIMPLICITY v9.0 SIM 1: Enhanced Discovery Server Browser ............................................. 29

GE Digital 3

2.8 Points and Scripting ..................................................................................................................................... 30

2.8.1 CIMPLICITY v9.0 SIM 19: HIST_TIME_STAMP_TYPE parameter ........................................... 30

2.9 Project and System Management ......................................................................................................... 31

2.9.1 CIMPLICITY v9.0 SIM 22: US98670 – Password Masking ..................................................... 31

2.10 Scripting and Open Interface ................................................................................................................... 32

2.10.1 CIMPLICITY v9.0 SIM 1: Scripting Methods............................................................................ 32

2.10.2 CIMPLICITY v9.0 SIM 1: Open Interface ................................................................................ 32

2.10.3 CIMPLICITY v9.0 SIM 1: XY Plot Object Model Property: AreaFill ........................................ 32

2.10.4 CIMPLICITY v9.0 SIM 6: Enhancements to Maintenance Scripting Functions .................... 33

2.10.5 CIMPLICITY v9.0 SIM 17: Enhancements to Point Management Script Functions ............. 37

2.10.6 CIMPLICITY v9.0 SIM 23: Parameters for reloading .NET Assemblies ................................. 49

2.11 Tracker/Order Execution Management .............................................................................................. 50

2.11.1 CIMPLICITY v9.0 SIM 1: Tracker Order/Execution Management Enhancements ............... 50

2.11.2 CIMPLICITY v9.0 SIM 6: Enhancements to support usage of PRTCNT from TADB ............. 52

2.11.3 CIMPLICITY v9.0 SIM 8: Tracker Devcom Enhancements .................................................... 52

2.11.4 CIMPLICITY v9.0 SIM 10: Tracker Collector Enhancements ................................................ 55

2.12 Users/Windows Authentication ............................................................................................................. 56

2.12.1 CIMPLICITY v9.0 SIM 1: Windows Authentication: Allow Configuration Auto Login .......... 56

2.12.2 CIMPLICITY v9.0 SIM 1: Windows Authentication: And Quick Trends ................................ 56

2.12.3 CIMPLICITY v9.0 SIM 24: Users/Windows Authentication .................................................. 57

3 Fixed Defects ....................................................................................................................................................... 58

3.1 Issues Resolved: Alarms. ............................................................................................................................ 58

3.1.1 CIMPLICITY v9.0 SIM 1 ........................................................................................................... 58

3.1.2 CIMPLICITY v9.0 SIM 2 ........................................................................................................... 59

3.1.3 CIMPLICITY v9.0 SIM 3 ........................................................................................................... 59

3.1.4 CIMPLICITY v9.0 SIM 6 ........................................................................................................... 59

3.1.5 CIMPLICITY v9.0 SIM 9 ........................................................................................................... 60

3.1.6 CIMPLICITY v9.0 SIM 10 ........................................................................................................ 60

3.1.7 CIMPLICITY v9.0 SIM 11 ........................................................................................................ 60

3.1.8 CIMPLICITY v9.0 SIM 12 ........................................................................................................ 60

3.1.9 CIMPLICITY v9.0 SIM 15 ........................................................................................................ 61

GE Digital 4

3.1.10 CIMPLICITY v9.0 SIM 16 ........................................................................................................ 61

3.1.11 CIMPLICITY v9.0 SIM 17 ........................................................................................................ 62

3.1.12 CIMPLICITY v9.0 SIM 18 ........................................................................................................ 62

3.1.13 CIMPLICITY v9.0 SIM 19 ........................................................................................................ 62

3.1.14 CIMPLICITY v9.0 SIM 20 ........................................................................................................ 63

3.1.15 CIMPLICITY v9.0 SIM 22 ........................................................................................................ 63

3.1.16 CIMPLICITY v9.0 SIM 26 ........................................................................................................ 64

3.2 Issues Resolved: CimEdit/CimView. ...................................................................................................... 65

3.2.1 CIMPLICITY v9.0 SIM 1 ........................................................................................................... 65

3.2.2 CIMPLICITY v9.0 SIM 2 ........................................................................................................... 69

3.2.3 CIMPLICITY v9.0 SIM 3 ........................................................................................................... 70

3.2.4 CIMPLICITY v9.0 SIM 4 ........................................................................................................... 71

3.2.5 CIMPLICITY v9.0 SIM 5 ........................................................................................................... 71

3.2.6 CIMPLICITY v9.0 SIM 6 ........................................................................................................... 72

3.2.7 CIMPLICITY v9.0 SIM 7 ........................................................................................................... 73

3.2.8 CIMPLICITY v9.0 SIM 8 ........................................................................................................... 74

3.2.9 CIMPLICITY v9.0 SIM 9 ........................................................................................................... 75

3.2.10 CIMPLICITY v9.0 SIM 10 ........................................................................................................ 75

3.2.11 CIMPLICITY v9.0 SIM 11 ........................................................................................................ 76

3.2.12 CIMPLICITY v9.0 SIM 12 ........................................................................................................ 77

3.2.13 CIMPLICITY v9.0 SIM 13 ........................................................................................................ 77

3.2.14 CIMPLICITY v9.0 SIM 14 ........................................................................................................ 78

3.2.15 CIMPLICITY v9.0 SIM 15 ........................................................................................................ 78

3.2.16 CIMPLICITY v9.0 SIM 16 ........................................................................................................ 79

3.2.17 CIMPLICITY v9.0 SIM 18 ........................................................................................................ 80

3.2.18 CIMPLICITY v9.0 SIM 19 ........................................................................................................ 81

3.2.19 CIMPLICITY v9.0 SIM 20 ........................................................................................................ 82

3.2.20 CIMPLICITY v9.0 SIM 21 ........................................................................................................ 83

3.2.21 CIMPLICITY v9.0 SIM 22 ........................................................................................................ 83

3.2.22 CIMPLICITY v9.0 SIM 23 ........................................................................................................ 84

3.2.23 CIMPLICITY v9.0 SIM 25 ........................................................................................................ 84

GE Digital 5

3.2.24 CIMPLICITY v9.0 SIM 26 ........................................................................................................ 85

3.2.25 CIMPLICITY v9.0 SIM 27 ........................................................................................................ 86

3.2.26 CIMPLICITY v9.0 SIM 28 ........................................................................................................ 87

3.3 Issues Resolved: Classes and Class Objects ..................................................................................... 88

3.3.1 CIMPLICITY v9.0 SIM 1 ........................................................................................................... 88

3.3.2 CIMPLICITY v9.0 SIM 2 ........................................................................................................... 89

3.3.3 CIMPLICITY v9.0 SIM 3 ........................................................................................................... 91

3.3.4 CIMPLICITY v9.0 SIM 5 ........................................................................................................... 92

3.3.5 CIMPLICITY v9.0 SIM 7 ........................................................................................................... 93

3.3.6 CIMPLICITY v9.0 SIM 8 ........................................................................................................... 93

3.3.7 CIMPLICITY v9.0 SIM 9 ........................................................................................................... 94

3.3.8 CIMPLICITY v9.0 SIM 10 ........................................................................................................ 94

3.3.9 CIMPLICITY v9.0 SIM 11 ........................................................................................................ 95

3.3.10 CIMPLICITY v9.0 SIM 14 ........................................................................................................ 95

3.3.11 CIMPLICITY v9.0 SIM 18 ........................................................................................................ 96

3.3.12 CIMPLICITY v9.0 SIM 19 ........................................................................................................ 96

3.3.13 CIMPLICITY v9.0 SIM 20 ........................................................................................................ 96

3.3.14 CIMPLICITY v9.0 SIM 21 ........................................................................................................ 97

3.3.15 CIMPLICITY v9.0 SIM 22 ........................................................................................................ 97

3.3.16 CIMPLICITY v9.0 SIM 23 ........................................................................................................ 98

3.3.17 CIMPLICITY v9.0 SIM 24 ........................................................................................................ 98

3.3.18 CIMPLICITY v9.0 SIM 25 ........................................................................................................ 98

3.3.19 CIMPLICITY v9.0 SIM 26 ........................................................................................................ 99

3.3.20 CIMPLICITY v9.0 SIM 28 ........................................................................................................ 99

3.4 Issues Resolved: Device communications ...................................................................................... 100

3.4.1 CIMPLICITY v9.0 SIM 1 ......................................................................................................... 100

3.4.2 CIMPLICITY v9.0 SIM 2 ......................................................................................................... 100

3.4.3 CIMPLICITY v9.0 SIM 3 ......................................................................................................... 101

3.4.4 CIMPLICITY v9.0 SIM 5 ......................................................................................................... 103

3.4.5 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 103

3.4.6 CIMPLICITY v9.0 SIM 10 ...................................................................................................... 103

GE Digital 6

3.4.7 CIMPLICITY v9.0 SIM 15 ...................................................................................................... 104

3.4.8 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 104

3.4.9 CIMPLICITY v9.0 SIM 17 ...................................................................................................... 104

3.4.10 CIMPLICITY v9.0 SIM 18 ...................................................................................................... 105

3.4.11 CIMPLICITY v9.0 SIM 19 ...................................................................................................... 105

3.4.12 CIMPLICITY v9.0 SIM 20 ...................................................................................................... 105

3.4.13 CIMPLICITY v9.0 SIM 21 ...................................................................................................... 105

3.4.14 CIMPLICITY v9.0 SIM 22 ...................................................................................................... 106

3.4.15 CIMPLICITY v9.0 SIM 27 ...................................................................................................... 106

3.5 Issues Resolved: Logging. ....................................................................................................................... 107

3.5.1 CIMPLICITY v9.0 SIM 1 ......................................................................................................... 107

3.5.2 CIMPLICITY v9.0 SIM 2 ......................................................................................................... 110

3.5.3 CIMPLICITY v9.0 SIM 4 ......................................................................................................... 110

3.5.4 CIMPLICITY v9.0 SIM 5 ......................................................................................................... 111

3.5.5 CIMPLICITY v9.0 SIM 10 ...................................................................................................... 111

3.5.6 CIMPLICITY v9.0 SIM 11 ...................................................................................................... 111

3.5.7 CIMPLICITY v9.0 SIM 13 ...................................................................................................... 111

3.5.8 CIMPLICITY v9.0 SIM 15 ...................................................................................................... 112

3.5.9 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 112

3.5.10 CIMPLICITY v9.0 SIM 17 ...................................................................................................... 113

3.6 Issues Resolved: Networking ................................................................................................................ 114

3.6.1 CIMPLICITY v9.0 SIM 1 ......................................................................................................... 114

3.6.2 CIMPLICITY v9.0 SIM 3 ......................................................................................................... 115

3.6.3 CIMPLICITY v9.0 SIM 5 ......................................................................................................... 115

3.6.4 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 115

3.6.5 CIMPLICITY v9.0 SIM 7 ......................................................................................................... 116

3.6.6 CIMPLICITY v9.0 SIM 9 ......................................................................................................... 116

3.6.7 CIMPLICITY v9.0 SIM 15 ...................................................................................................... 116

3.6.8 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 117

3.7 Issues Resolved: Points and scripting ............................................................................................... 118

3.7.1 CIMPLICITY v9.0 SIM 1 ......................................................................................................... 118

GE Digital 7

3.7.2 CIMPLICITY v9.0 SIM 2 ......................................................................................................... 121

3.7.3 CIMPLICITY v9.0 SIM 3 ......................................................................................................... 122

3.7.4 CIMPLICITY v9.0 SIM 5 ......................................................................................................... 123

3.7.5 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 124

3.7.6 CIMPLICITY v9.0 SIM 7 ......................................................................................................... 125

3.7.7 CIMPLICITY v9.0 SIM 8 ......................................................................................................... 126

3.7.8 CIMPLICITY v9.0 SIM 9 ......................................................................................................... 126

3.7.9 CIMPLICITY v9.0 SIM 10 ...................................................................................................... 127

3.7.10 CIMPLICITY v9.0 SIM 11 ...................................................................................................... 128

3.7.11 CIMPLICITY v9.0 SIM 12 ...................................................................................................... 129

3.7.12 CIMPLICITY v9.0 SIM 13 ...................................................................................................... 129

3.7.13 CIMPLICITY v9.0 SIM 14 ...................................................................................................... 130

3.7.14 CIMPLICITY v9.0 SIM 15 ...................................................................................................... 131

3.7.15 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 131

3.7.16 CIMPLICITY v9.0 SIM 17 ...................................................................................................... 133

3.7.17 CIMPLICITY v9.0 SIM 18 ...................................................................................................... 133

3.7.18 CIMPLICITY v9.0 SIM 19 ...................................................................................................... 134

3.7.19 CIMPLICITY v9.0 SIM 20 ...................................................................................................... 134

3.7.20 CIMPLICITY v9.0 SIM 21 ...................................................................................................... 135

3.7.21 CIMPLICITY v9.0 SIM 22 ...................................................................................................... 135

3.7.22 CIMPLICITY v9.0 SIM 23 ...................................................................................................... 135

3.7.23 CIMPLICITY v9.0 SIM 24 ...................................................................................................... 136

3.7.24 CIMPLICITY v9.0 SIM 25 ...................................................................................................... 136

3.7.25 CIMPLICITY v9.0 SIM 26 ...................................................................................................... 137

3.7.26 CIMPLICITY v9.0 SIM 27 ...................................................................................................... 137

3.7.27 CIMPLICITY v9.0 SIM 28 ...................................................................................................... 138

3.8 Issues Resolved: Proficy Integration. ................................................................................................. 139

3.8.1 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 139

3.8.2 CIMPLICITY v9.0 SIM 7 ......................................................................................................... 139

3.8.3 CIMPLICITY v9.0 SIM 8 ......................................................................................................... 140

3.8.4 CIMPLICITY v9.0 SIM 9 ......................................................................................................... 140

GE Digital 8

3.8.5 CIMPLICITY v9.0 SIM 15 ...................................................................................................... 141

3.8.6 CIMPLICITY v9.0 SIM 19 ...................................................................................................... 141

3.8.7 CIMPLICITY v9.0 SIM 24 ...................................................................................................... 141

3.8.8 CIMPLICITY v9.0 SIM 27 ...................................................................................................... 142

3.9 Issues Resolved: Proficy Process Systems. ..................................................................................... 143

3.9.1 CIMPLICITY v9.0 SIM 1 ......................................................................................................... 143

3.9.2 CIMPLICITY v9.0 SIM 10 ...................................................................................................... 143

3.9.3 CIMPLICITY v9.0 SIM 11 ...................................................................................................... 143

3.9.4 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 143

3.9.5 CIMPLICITY v9.0 SIM 23 ...................................................................................................... 144

3.10 Issues Resolved: Project and System Management. .................................................................. 145

3.10.1 CIMPLICITY v9.0 SIM 1 ......................................................................................................... 145

3.10.2 CIMPLICITY v9.0 SIM 2 ......................................................................................................... 146

3.10.3 CIMPLICITY v9.0 SIM 3 ......................................................................................................... 147

3.10.4 CIMPLICITY v9.0 SIM 5 ......................................................................................................... 147

3.10.5 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 147

3.10.6 CIMPLICITY v9.0 SIM 7 ......................................................................................................... 148

3.10.7 CIMPLICITY v9.0 SIM 8 ......................................................................................................... 148

3.10.8 CIMPLICITY v9.0 SIM 10 ...................................................................................................... 148

3.10.9 CIMPLICITY v9.0 SIM 11 ...................................................................................................... 149

3.10.10 CIMPLICITY v9.0 SIM 13 ...................................................................................................... 149

3.10.11 CIMPLICITY v9.0 SIM 15 ...................................................................................................... 150

3.10.12 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 150

3.10.13 CIMPLICITY v9.0 SIM 17 ...................................................................................................... 151

3.10.14 CIMPLICITY v9.0 SIM 18 ...................................................................................................... 151

3.10.15 CIMPLICITY v9.0 SIM 19 ...................................................................................................... 151

3.10.16 CIMPLICITY v9.0 SIM 20 ...................................................................................................... 152

3.10.17 CIMPLICITY v9.0 SIM 23 ...................................................................................................... 152

3.10.18 CIMPLICITY v9.0 SIM 24 ...................................................................................................... 153

3.10.19 CIMPLICITY v9.0 SIM 25 ...................................................................................................... 153

3.11 Issues Resolved: Recipes ........................................................................................................................ 154

GE Digital 9

3.11.1 CIMPLICITY v9.0 SIM 5 ......................................................................................................... 154

3.11.2 CIMPLICITY v9.0 SIM 19 ...................................................................................................... 154

3.11.3 CIMPLICITY v9.0 SIM 28 ...................................................................................................... 154

3.12 Issues Resolved: Server Redundancy. ............................................................................................... 155

3.12.1 CIMPLICITY v9.0 SIM 2 ......................................................................................................... 155

3.12.2 CIMPLICITY v9.0 SIM 3 ......................................................................................................... 155

3.12.3 CIMPLICITY v9.0 SIM 4 ......................................................................................................... 155

3.12.4 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 156

3.12.5 CIMPLICITY v9.0 SIM 11 ...................................................................................................... 156

3.12.6 CIMPLICITY v9.0 SIM 13 ...................................................................................................... 156

3.12.7 CIMPLICITY v9.0 SIM 14 ...................................................................................................... 157

3.12.8 CIMPLICITY v9.0 SIM 27 ...................................................................................................... 157

3.13 Issues Resolved: Statistical Process Control (SPC). .................................................................... 158

3.13.1 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 158

3.13.2 CIMPLICITY v9.0 SIM 20 ...................................................................................................... 158

3.13.3 CIMPLICITY v9.0 SIM 21 ...................................................................................................... 158

3.13.4 CIMPLICITY v9.0 SIM 23 ...................................................................................................... 158

3.14 Issues Resolved: Tracker/Order Execution Management ........................................................ 159

3.14.1 CIMPLICITY v9.0 SIM 2 ......................................................................................................... 159

3.14.2 CIMPLICITY v9.0 SIM 4 ......................................................................................................... 159

3.14.3 CIMPLICITY v9.0 SIM 5 ......................................................................................................... 160

3.14.4 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 161

3.14.5 CIMPLICITY v9.0 SIM 8 ......................................................................................................... 161

3.14.6 CIMPLICITY v9.0 SIM 9 ......................................................................................................... 162

3.14.7 CIMPLICITY v9.0 SIM 10 ...................................................................................................... 163

3.14.8 CIMPLICITY v9.0 SIM 11 ...................................................................................................... 165

3.14.9 CIMPLICITY v9.0 SIM 13 ...................................................................................................... 166

3.14.10 CIMPLICITY v9.0 SIM 14 ...................................................................................................... 167

3.14.11 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 167

3.14.12 CIMPLICITY v9.0 SIM 17 ...................................................................................................... 167

3.14.13 CIMPLICITY v9.0 SIM 20 ...................................................................................................... 168

GE Digital 10

3.14.14 CIMPLICITY v9.0 SIM 21 ...................................................................................................... 168

3.14.15 CIMPLICITY v9.0 SIM 28 ...................................................................................................... 169

3.15 Issues Resolved: Trends and DGR ....................................................................................................... 170

3.15.1 CIMPLICITY v9.0 SIM 1 ......................................................................................................... 170

3.15.2 CIMPLICITY v9.0 SIM 3 ......................................................................................................... 171

3.15.3 CIMPLICITY v9.0 SIM 6 ......................................................................................................... 171

3.15.4 CIMPLICITY v9.0 SIM 7 ......................................................................................................... 172

3.15.5 CIMPLICITY v9.0 SIM 9 ......................................................................................................... 172

3.15.6 CIMPLICITY v9.0 SIM 13 ...................................................................................................... 172

3.15.7 CIMPLICITY v9.0 SIM 14 ...................................................................................................... 173

3.15.8 CIMPLICITY v9.0 SIM 16 ...................................................................................................... 173

3.15.9 CIMPLICITY v9.0 SIM 18 ...................................................................................................... 174

3.15.10 CIMPLICITY v9.0 SIM 19 ...................................................................................................... 174

3.15.11 CIMPLICITY v9.0 SIM 20 ...................................................................................................... 175

3.15.12 CIMPLICITY v9.0 SIM 21 ...................................................................................................... 176

3.15.13 CIMPLICITY v9.0 SIM 23 ...................................................................................................... 176

3.15.14 CIMPLICITY v9.0 SIM 26 ...................................................................................................... 176

4 Known Issues .................................................................................................................................................... 177

4.1 Administrator Privileges Required ..................................................................................................... 177

4.2 SQL Server ..................................................................................................................................................... 179

4.3 Tracker Project Upgrade and TADB Replication ........................................................................... 180

5 General Information ...................................................................................................................................... 183

5.1 McAfee Anti-virus Details ....................................................................................................................... 183

5.2 CimEdit/CimView ....................................................................................................................................... 183

5.3 Device Communications ......................................................................................................................... 184

5.4 Logging ............................................................................................................................................................ 185

5.5 Networking ................................................................................................................................................... 185

5.6 Points and Scripting .................................................................................................................................. 185

5.7 WEBSPACE .................................................................................................................................................... 189

6 Special Instructions ....................................................................................................................................... 190

7 Contact GE Digital .......................................................................................................................................... 191

GE Digital 11

GE Digital 12

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.0 Build 24465r.

1 INSTALLATION

To install this update:

1. Go the GE Digital Web site: http://digitalsupport.ge.com 2. Select Software > HMI SCADA > CIMPLICITY. 3. Under Filter Content by, select Downloads. The SIM patch labeled “HMI-

9.0.24465r.000028.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.

Go to: Table of Contents

http://digitalsupport.ge.com/

GE Digital 13

2 NEW FEATURES AND ENHANCEMENTS

2.1 ALARMS

2.1.1 CIMPLICITY v9.0 SIM 7: Alarm Message – Truncation Limits

DE8337; SF-00291058 When Alarm Messages are generated, the values of points embedded in Alarm Message are truncated to the limits given below:

Point Data Type Allowed Characters Count

STRING 72

QUAD 21

All Other Types 16


2.1.2 CIMPLICITY v9.0 SIM 15: Alarm Properties

DE14947; SF-00364472 Alarm Properties dialog now has the following fields added:

Property Name Purpose Permitted Limits Default Value

Auto processing interval The time interval (in minutes) for processing the auto alarms.

1 to 32767 5

Number of Auto Alarms processed at a time

The number of auto alarms that will be processed at a time.

1 to 32767 25


GE Digital 14

2.1.3 CIMPLICITY v9.0 SIM 20: Alarm Sound Manager Options

DE18616; SF-00391433 Alarm Sound Manager now has the following configuration option added:

Attribute Name Purpose/Meaning

AMV_SOUND_LOOP Provide additional support for continuous playback of alarm sound audio files

Attribute Value Purpose

N or n [Default] Current Application behavior will not be affected.

Y or y When the attribute value is set to Y or y: 1. Alarm sound will be repeated in loop till the specified stop criteria is satisfied. 2. Sound will stop immediately if stop criteria is satisfied. 3. The alarm audio file will continue to play in loop, even if the replay option is not

selected. 4. Alarm Sound file will pause immediately if muted and will resume playing when

cleared.


GE Digital 15

2.2 CHANGE MANAGEMENT

2.2.1 CIMPLICITY v9.0 SIM 1: Auto Login to Change Management Projects

The Windows Authentication new Allow Configuration Auto Login feature also enables valid users who have logged into CIMPLICITY to be automatically logged into Change Management.


2.2.2 CIMPLICITY v9.0 SIM 1: Enhanced Audit Trail

Change Management now offers an enhanced audit trail. The audit entries include the:

• Point.

• Action.

• User who performed the action.

See the "Enable project Management" topic in the CIMPLICITY documentation for details on the above enhancements.


GE Digital 16

2.3 CIMEDIT/CIMVIEW

2.3.1 CIMPLICITY v9.0 SIM 12: “NoScreenExit” Commandline Parameter

DE13813; SF-00347207 DE13859; SF-00334970 Starting from CIMPLICITY 9.0 SIM 12, a new command line parameter "NoScreenExit" has been added. Use this command line parameter to enable a behavior similar to that offered by NoExit command for Popup Dialogs when Multiple Monitors are being used to run CimView screens.


2.3.2 CIMPLICITY v9.0 SIM 16: “StripDebounce” Commandline Parameter

DE17196; SF-00371956 Starting from CIMPLICITY 9.0 SIM 16, 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 17

2.4 CONFIGURATION OF AUTO LOGIN FOR TRUSTED USERS

2.4.1 CIMPLICITY v9.0 SIM 4: Configuring Auto Login for Trusted Users

Trusted Users can now use Configuration Auto Login feature to automatically log into CIMPLICITY and also allow automatic log into Change Management. For more information on auto login access capability for trusted users, refer to the Configure Client Properties topic in the CIMPLICITY Help. Trusted Users can now use Configuration Auto Login feature:

• Select Configuration Security to enable Allow configuration auto login for trusted client users.

• Select Allow configuration auto login for trusted client users.


GE Digital 18

2.4.2 CIMPLICITY v9.0 SIM 7: Auto Login Support for Trusted Users - Configuration Settings

Pre-requisites: Please refer to below listed help topics for more information on Configuration Settings requirements for Trusted Users' Auto Login Support feature:

Operation Dialog Name Help Topic Help Section

Help Source

Configure Trusted Clients for Auto Login Support

Client Properties Configuring Client Properties

Client Configuration

CIMPLICITY Help

Add Trusted Users in CIMPLICITY Projects

User Properties; General Properties Tab

User Configuration

User Configuration

CIMPLICITY Help

Enable PCM Server Auto Login for Trusted Users

Project Properties; Change Management Tab

Enable Project Management

Proficy Change Management

CIMPLICITY Help

Enable CIMPLICITY configuration auto login for trusted users

Project Properties; Options Tab

Set Project Options

Project Properties

CIMPLICITY Help Configuring Auto Login for Trusted Users topic in IPI.

Below listed options, provided in the dialog boxes listed in the table above, need to be configured to get the desired Auto Login Support for Trusted Users:

Option Name Option Type

Purpose Dialog Name

Default User ID Edit Box These parameters specify configuration settings for defining Trusted Users to provide Auto Login Support for CIMPLICITY Server and/or PCM Server. Note: Refer to tables below for more information.

Client Properties

Trusted Check box

Authentication Type Dropdown List

User Properties; General Properties Tab

Enable Change Management Check box Selected Note: Applicable only If PCM Server Auto Login for Trusted Users is needed.

Project Properties; Change Management Tab

Logon at Workbench Startup Check box

Configuration Security Check box Selected Note: Applicable if CIMPLICITY Server Auto Login and/or PCM Server Auto Login for Trusted Users is needed.

Project Properties; Options Tab

Allow configuration auto login for trusted client users

Check box

GE Digital 19

Configuration Setting options: The table below lists impact of above listed options on the Configuration Settings of Auto Login support for Trusted Users: Pre-Condition: Trusted Check Box is cleared while configuring Client Properties

In the Default User ID field

Trusted CIMPLICITY User Authentication Type Field is set to

CIMPLICITY Server Auto Login Criteria for Trusted User

PCM Server Auto Login Criteria for Trusted User

Select a User ID from the list of available users for the project as default "Trusted" User ID

Any of the following options: 1. None 2. CIMPLICITY

Users from CIMPLICITY project with Default Trusted User ID are treated as Trusted CIMPLICITY Users and are automatically logged in. For all other cases [1], users need to enter a valid User ID and Password (if required) in the CIMPLICITY login dialog box. Note: CIMPLICITY Server Windows Login is either local or domain user.

Users are automatically logged into PCM Server only when Trusted PCM User Security Provider Type is set to "Default" [2] For all other cases, users need to enter a valid User ID and Password (if required) in the PCM Login dialog box.

Any of the following options: 1. Windows Domain 2. Windows Domain Group Mapping

Users from the CIMPLICITY project with Default Trusted User ID are automatically logged in only when: 1. Windows Authentication is enabled. 2. CIMPLICITY Server Windows Login User Domain matches the CIMPLICITY project trusted user.

Users are automatically logged into PCM Server only when: 1. Trusted PCM User Security Provider Type is "NT Authentication" 2. Auto Login is enabled 3. Domain name is matches with CIMPLICITY Trusted User. For All other cases, users need to enter a valid User ID and Password (if required) in the PCM Login dialog box.

Leave Default User ID Field blank

Any of the following options: 1. None 2. CIMPLICITY 3. Windows Domain 4. Windows Domain Group Mapping

For all other cases [1], users need to enter a valid User ID and Password (if required) in the CIMPLICITY login dialog box.

For All cases, users need to enter a valid User ID and Password (if required) in the PCM Login dialog box.

GE Digital 20

Pre-Condition: Trusted Check Box is cleared while configuring Client Properties

In the Default User ID field

CIMPLICITY Server Windows Login User Type

Trusted CIMPLICITY User Authentication Type Field is set to

CIMPLICITY Server Auto Login Criteria for Trusted User

PCM Server Auto Login Criteria for Trusted User

Select a User ID from the list of available users for the project as default "Trusted" User ID or Leave Default User ID Field blank

Domain Any of the following options: 1. None 2. CIMPLICITY

Users are automatically logged in if Windows Logon User Name matches the CIMPLICITY User ID [3] For all other cases [1], users need to enter a valid User ID and Password (if required) in the CIMPLICITY login dialog box.

Users are automatically logged into PCM Server only when: 1. Trusted PCM User Security Provider Type is "NT Authentication" 2. Auto Login is enabled 3. Domain name is matches with CIMPLICITY Trusted User. For All other cases, users need to enter a valid User ID and Password (if required) in the PCM Login dialog box.

Any of the following options: 1. Windows Domain 2. Windows Domain Group Mapping

Users are automatically logged in when below mentioned conditions are met: 1. Windows Logon User Name matches the CIMPLICITY User ID [3] 2. Windows Authentication is enabled 3. CIMPLICITY Server Windows Login User Domain matches the CIMPLICITY project trusted user. For all other cases [1], users need to enter a valid User ID and Password (if required) in the CIMPLICITY login dialog box.

Local Any of the following options: 1. None 2. CIMPLICITY

Users are automatically logged in if Windows Logon User Name matches theCIMPLICITY User ID [3] For all other cases [1], users need to enter a valid User ID and Password (if required) in the CIMPLICITY login dialog box.

Users are automatically logged into PCM Server only when Trusted PCM User Security Provider Type is set to "Default" [2] For all other cases, users need to enter a valid User ID and Password (if required) in the PCM Login dialog box.

GE Digital 21

Additional Information:

1. If the defined user is not a valid CIMPLICITY Trusted User, then user will have to provide valid User ID and Password in CIMPLICITY Login Dialog Box. If these credentials satisfy the PCM Auto Login Criteria, then user is automatically logged into PCM Server.

2. If Trusted CIMPLICITY User exists in PCM Server with same authentication credentials, then current user will be automatically logged into PCM server when PCM Server Security Provider Type is set to "Default".

3. CIMPLICITY User ID can be any of the following:

1. Specified Default User ID

2. Any valid CIMPLICITY User ID, when Default User ID Field is empty.


GE Digital 22

2.5 DATABASE LOGGING/HISTORIAN

2.5.1 CIMPLICITY v9.0 SIM 1: Individual Point Logging

Individual points can now be selected to be logged to Microsoft SQL Server and/or Proficy Historian. Example:

See either the "Step 2.2. Enter Device Point Advanced General Properties" or "Step 2.2. Enter Virtual Point Advanced General Properties" topics in the CIMPLICITY documentation for details.


GE Digital 23

2.5.2 CIMPLICITY v9.0 SIM 2: Historian/Enumerated Points

Feature IDs: US5642; US5641 Issue: In previous CIMPLICITY versions, if CIMPLICITY points with enumerations were logged to Historian, they were logged as string points. This prevented the Historian tags from being saved correctly. New Feature A new check box, “Save enumerations as integers” option, which enables existing enumerated points to be successfully saved to Historian, is now available on the Project Properties dialog box > Historian tab. Selecting/clearing the Save enumerations as integers check box does the following.

Check box Status

Details

Selected ✓ Saves enumerated points that already exist in Historian as integers. ✓ Creates enumerations in Historian that match the enumerations in CIMPLICITY. ✓ Enables enumerated points to be updated correctly in Historian. ✓ Enables actions that include:

o Add points with enumerations (new and existing) dynamically. o Play back with DGR. o Trend the enumeration points (by removing the numeration set on the

Historian side).

Clear ✓ Saves enumerated points as strings. ✓ Does not create enumerations in Historian to match the enumerations in CIMPLICITY. ✓ Does not update enumerated points in Historian correctly.

Important: Currently Historian tags with enumerations cannot be used in Historian tag expressions.


GE Digital 24

2.5.3 CIMPLICITY v9.0 SIM 2: Point Logging/Same Timestamp

DE7276, SF-00178624 DE7275; SF-00177471 DE7277; SF-00178110 DE7274; SF-00177554 DE7278; SF-00179554 Issue The same point was changing values more rapidly than the resolution of the clock so many different point values were being logged for the same point with the same timestamp. This generated errors that were sent to the CIMPLICITY Status Log. Resolution Beginning with CIMPLICITY v8.2 SIM 30, the uniqueness constraint has been dropped on existing key columns; CIMPLICITY can now log data to the same point with the same timestamp without generating errors.

➢ New GROUP_LOG or DATA_LOG Tables When a new GROUP_LOG or DATA_LOG table is added to a project the uniqueness constraint no longer is applied.

➢ Existing GROUP_LOG or DATA_LOG Tables A new tool, ToolIndexUpgClust.exe, is now available to remove the existing Unique constraint.

Do the following to implement the tool:

1. Open a Command window. 2. Set the directory to the ..\<CIMPLICITY Installation>/exe directory..

The default entry is: cd C:\Program Files (x86)\Proficy\Proficy CIMPLICITY\exe

3. Prepare a string with quotes and fields as follows: Note: Use a text editor (e.g. Notepad) to prepare part of the string that is included in the command; you can then paste the prepared part into the Command window (within the command syntax) when it is ready. The syntax for the prepared string is as follows. "<dsn name>;UID=<user name>;PWD=<user password>;APP=<database name>;"

Example "CIMPLICITY Logging - POINTS;UID=sa;PWD=Admin#1;APP=CIMPLICITY;"

Tip: You can:

➢ Use the connect_string field in the dbms_def.idt file record to find the string values.

➢ IDTPOP the file in the Command Window ..\<CIMPLICITY Installation>/exe directory to

open the dbms_def.idt file.

a. Open the Command window. b. Change the directory to the ..\<CIMPLICITY Installation>/exe directory.

c. Type IDTPOP dbms_def

d. Press Enter. e. Type Notepad dbms_def.idt

f. Press Enter. Result: Notepad opens the dbms_def.idt file where you can find the necessary values.

GE Digital 25

Example:

4. Do the following to pass the command when the string is ready. a. Pass the prepared string as a command line argument to the ToolIndexUpgClust.exe tool.

b. Provide the table ID as a second argument for which uniqueness needs to be dropped.

The syntax for the complete command is: C:\Program Files (x86)\Proficy\Proficy

CIMPLICITY\exe>ToolIndexUpgClust.exe "<dsn name>;UID=<user

name>;PWD=<user password>;APP=<database name>;" <table ID>

Example C:\Program Files (x86)\Proficy\Proficy

CIMPLICITY\exe>ToolIndexUpgClust.exe "CIMPLICITY Logging -

POINTS;UID=sa;PWD=Admin#1;APP=CIMPLICITY;" DATA_LOG


GE Digital 26

2.5.4 CIMPLICITY v9.0 SIM 8: Sequence Numbering

US11483; SF-NA

Issue In previous CIMPLICITY versions, Duplicate Records/timestamps were getting logged during high speed logging. New Feature A new ”sequence_number” column has been added to DATA_LOG & GROUP_LOG tables and has been made the primary key. This ”sequence_number” column gets incremented for every new record. Note: The tables will not have duplicate records till 2^63 (2 power 63) values of Identity. Beginning with CIMPLICITY v9.0 SIM 8, the behavior will be as mentioned below:

Table Name Changed Behavior

New DATA_LOG or GROUP_LOG Tables

When a new DATA_LOG or GROUP_LOG table is added to a project, a new primary key comprising only "sequence_number" of Identity Column type is added to the table. The "sequence_number" is an auto-increment column updated by Database Server.

Existing DATA_LOG or GROUP_LOG Tables

No change in behavior


GE Digital 27

2.6 EXPRESSION EDITOR ENHANCEMENTS

2.6.1 CIMPLICITY v9.0 SIM 7: Expressions Editor – Quality Operations

Flag Name Return Value

Additional comments

IsConfigured Returns TRUE if the point is configured

FALSE for the following conditions: 1. If the point is not found in the configuration. 2. If the project is not reachable.

Format IsConfigured(PointID)

Comments Using the IsConfigured() function in an expression allows the expression to reference points that may or may not be configured, and still have the expression evaluate to a good quality value. Normally, if an unconfigured point is referenced by an expression, it will always evaluate to bad quality to indicate a problem with the configuration. The use of IsConfigured() function in the expression for a point signals the expression engine that this condition is being handled by the expression logic and will make an attempt to evaluate the expression even if the point being referenced is not configured.


2.6.2 CIMPLICITY v9.0 SIM 17: 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.


2.6.3 CIMPLICITY v9.0 SIM 17: 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 28

2.7 NETWORK GLOBAL DISCOVERY

2.7.1 CIMPLICITY v9.0 SIM 1: Proficy Global Discovery Server

A new Proficy Global Discovery Server, which is distributed on a separate DVD, will be shipped to you when the GDS option is selected on your CIMPLICITY license. The Proficy GE Global Discovery Server (GDS): ✓ Can be used manage application certificates for all OPC UA applications at a site. ✓ Is a database of applications? ✓ Enables all applications in the Proficy GDS to communicate with each other securely. ✓ Performs like a search engine. Can find all the applications that are running in your factory/environment. Example

1. A factory has 100 different applications that are running on different machines; 2. An administrator enters the applications into the Proficy GDS 3. Valid users can use the Proficy GDS to find any of the 100 applications.

Note: The Proficy GDS can be used out of the box; it can also be customized if your system has unique requirements. See Proficy Global Discovery Server documentation for details about the application.


2.7.2 CIMPLICITY v9.0 SIM 1: Proficy Global Discovery Server Agent

A new Proficy Global Discovery Server Agent is installed when CIMPLICITY is installed. The Proficy Global Discovery Server Agent (GDS Agent) is the primary tool to:

✓ Set up your OPC UA Application (Client or Server) ✓ Work with the Proficy GDS ✓ Easily and securely trust and communicate with other GDS Registered Applications.

Double-click a Proficy Global Discovery Agent icon on the desktop or Start Menu to open the application. See Proficy Global Discovery Agent documentation for details about the application.


GE Digital 29

2.7.3 CIMPLICITY v9.0 SIM 1: OPC UA Security Setup Tool

A major feature of OPC UA communications is the ability to apply security to the communications, to ensure that the environment and system are safe and secure. To allow clients to securely communicate with servers, it is necessary for both the:

1. Client application to accept the Server as a legitimate Server 2. Server to accept the Client as a legitimate Client.

The OPC UA Security tool is now available to enable you to quickly set up a secure communication between the OPC UA Client and the GDS Server registered applications. See the "OPC UA Security Tool" section in the documentation for details.


2.7.4 CIMPLICITY v9.0 SIM 1: Enhanced Discovery Server Browser

The OPC UA DA configuration connection offers extensive Discovery Server browsing capability in both Direct Address and Global Directory discovery modes. See the "2.1. OPC UA DA configuration: Connection topic>B. Browse Button/UA Server Discovery section" for details.


GE Digital 30

2.8 POINTS AND SCRIPTING

2.8.1 CIMPLICITY v9.0 SIM 19: HIST_TIME_STAMP_TYPE parameter

DE8252; SF-00283462 Starting CIMPLICITY 9.0 SIM 18, a new parameter "HIST_TIME_STAMP_TYPE" has been added to configure how Historian Tag Timestamp is processed from CIMPLICITY project.

Parameter Value Meaning

HIST_TIME_STAMP_TYPE Parameter not defined or expected value not specified for the parameter

CIMPLICITY Timestamp will be logged to Historian for every configured tag

X CIMPLICITY Timestamp is logged to Historian for every configured tag.

Y Collector Timestamp is logged to Historian for every configured tag.

Z Collector configurable default Timestamp is logged to Historian for every configured tag.


GE Digital 31

2.9 PROJECT AND SYSTEM MANAGEMENT

2.9.1 CIMPLICITY v9.0 SIM 22: US98670 – Password Masking

Starting CIMPLICITY 9.0 SIM 22, enhancements have been made to mask the actual password and hide the number of characters in a password string that is entered by users in various login/configuration dialogs.


GE Digital 32

2.10 SCRIPTING AND OPEN INTERFACE

2.10.1 CIMPLICITY v9.0 SIM 1: Scripting Methods

The following alarm methods are now available for scripting.

AlarmGenerateEx AlarmGenerateEx, which is based on the AlarmGenerate method, in addition, enables CIMPLICITY to

provide:

• Internal or external timestamps. Note: A timestamp can be passed from another system or device to a CIMPLICITY alarm database.

• Time reported down to microseconds.

• Timestamps in UTC or local time to the CIMPLICITY alarm database.

AlarmUpdateEx AlarmUpdateEx, which is based on the AlarmUpdate method, in addition, enables CIMPLICITY to provide:

• Internal or external timestamps. Note: A timestamp can be passed from another system or device to a CIMPLICITY alarm database.

• Time reported down to microseconds.

• Timestamps in UTC or local time to the CIMPLICITY alarm database.


2.10.2 CIMPLICITY v9.0 SIM 1: Open Interface

Long Point ID Fields The CIMPLICITY APIs have been enhanced to accommodate long point IDs.

Example: The AlarmInfo Structure in the Alarm Viewer API now includes an additional field: long_name.

Where long_name is a full alarm ID.

The following line has been inserted at the end of the structure. TCHAR long_name[LONG_NAME_LEN+1];

Device Communications Toolkit – Maximum number of Domains The Device Communications toolkit was enhanced to optionally support a larger maximum number of domains. The following subroutine has been added to the toolkit. user_device_set_max_device_domain_count()


2.10.3 CIMPLICITY v9.0 SIM 1: XY Plot Object Model Property: AreaFill

An AreaFill property has been added to the XY Plot Object Model to enable scripting the new XY plot

AreaFill feature that enables plotted areas for item values to display in color and to indicate areas where

values from two or more items overlap.


GE Digital 33

2.10.4 CIMPLICITY v9.0 SIM 6: Enhancements to Maintenance Scripting Functions

DE8513 The following new scripting features/enhancements have been added to the CIMPLICITY v9.0 SIMs

Method Name Usage Example(s)

PeriodicMaintenance 'This example displays the usage of PeriodicMaintenance method. Sub Main()

Dim project As CimProject

Dim Val

Dim BVal

Set project = CreateObject("CimProject")

project.OpenLocalProject

"C:\d\g_ws\#00257668_LineAng\TestData\TestData.gef"

Set myDatabase = project.database

Set myTable = myDatabase.GetTable("DATA_LOG")

myTable.PeriodicMaintenanceRate = 12

myTable.PeriodicMaintenanceRateUnits = cimHour

myTable.PeriodicMaintenance = FALSE

Val = myTable.PeriodicMaintenanceRate

BVal = myTable.PeriodicMaintenance

End Sub

SyncMaintenance 'This example displays the usage of SyncMaintenance method. Sub Main()


Dim Val

Dim BVal






myTable.SyncMaintenance = FALSE

BVal = myTable.SyncMaintenance

myTable.SyncMaintenance = TRUE

myTable.SyncMaintenanceTime = 990

End Sub

GE Digital 34


DigitalMaintenance 'This example displays the usage of DigitalMaintenance method. Sub Main()


Dim Val

Dim BVal






myTable.DigitalMaintenance = FALSE

BVal = myTable.DigitalMaintenance

myTable.DigitalMaintenance = TRUE

myTable.DigitalMaintenancePointID = "SWITCH"

End Sub

LowSpaceTrigger 'This example displays the usage of LowSpaceTrigger method. Sub Main()


Dim Val

Dim BVal






myTable.LowSpaceTrigger = FALSE

BVal = myTable.LowSpaceTrigger

myTable.LowSpaceTrigger = TRUE

myTable.LowSpaceTriggerAmount = 100

myTable.LowSpaceTriggerDrive = "C:"

End Sub

GE Digital 35


LogCountMaintenance 'This example displays the usage of LogCountMaintenance method. Sub Main()


Dim Val

Dim BVal






myTable.LogCountMaintenance = FALSE

BVal = myTable.LogCountMaintenance

myTable.LogCountMaintenance = TRUE

myTable.LoggingCount = 25000

End Sub

GE Digital 36


Example that makes use of all the new included methods

'This example displays the usage of all the newly added methods. Sub Main()


Dim Val

Dim BVal






myTable.PeriodicMaintenance = FALSE

myTable.SyncMaintenance = FALSE

myTable.DigitalMaintenance = FALSE

myTable.LowSpaceTrigger = FALSE

myTable.LogCountMaintenance = FALSE

BVal = myTable.PeriodicMaintenance

BVal = myTable.SyncMaintenance

BVal = myTable.DigitalMaintenance

BVal = myTable.LowSpaceTrigger

BVal = myTable.LogCountMaintenance

myTable.PeriodicMaintenance = TRUE

myTable.PeriodicMaintenanceRate = 12

myTable.PeriodicMaintenanceRateUnits = cimHour

myTable.SyncMaintenance = TRUE

myTable.SyncMaintenanceTime = 990

myTable.DigitalMaintenance = TRUE

myTable.DigitalMaintenancePointID = "SWITCH"

myTable.LowSpaceTrigger = TRUE

myTable.LowSpaceTriggerAmount = 100

myTable.LowSpaceTriggerDrive = "C:"

myTable.LogCountMaintenance = TRUE

myTable.LoggingCount = 25000

End Sub


GE Digital 37

2.10.5 CIMPLICITY v9.0 SIM 17: Enhancements to Point Management Script Functions

New methods and properties added to CIMBasic scripting are listed below:

Properties

o Point.ErrCode

o Point.ErrMsg

o Point.TimeStamp

o Point.TimeStampUTC

Methods

o Point.SetTimeStampHR

o GetTimeComponentsHR_UTC

o SetTimeFromComponentsHR_UTC

o PointSetMultiple

o PointSetMultipleEx

o PointUpdateMultiple

New methods and properties added to .NET scripting are listed below:

Methods

o CIMPLICITY.PointSetMultiple

o CIMPLICITY.PointSetMultipleEx

o CIMPLICITY.PointUpdateMultiple

Properties Point.ErrCode Point.ErrCode is a read-only property. Integer value containing the error code for a failed call or zero for a successful operation. Point.ErrMsg Point.ErrMsg is a read-only property. This property stores string value containing the error message for a failed call or empty string for a successful operation Point.TimeStamp Point.TimeStamp is a read/write property. This property can be used to retrieve/store the timestamp into a Basic Date Object. The timestamp 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 the local settings.

Syntax Point.TimeStamp

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.TimeStamp) & " " & x.Value

goto top

End Sub

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#CIMPLICITY.PointSetMultiple

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#CIMPLICITY.PointSetMultipleEx

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#CIMPLICITY.PointUpdateMultiple


mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#Point.SetTimeStampHR

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#GetTimeComponentsHR_UTC

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#SetTimeFromComponentsHR_UTC

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#PointSetMultiple

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#PointSetMultipleEx

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#PointUpdateMultiple

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#CIMPLICITY.PointSetMultiple

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000017__EnhancementsToPointManagementScriptFunctions.htm#CIMPLICITY.PointSetMultipleEx


GE Digital 38

Point.TimeStampUTC 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 based on the 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

min = 59

sec = 59

nano = 9999999

GE Digital 39

Syntax Point.SetTimeStampHR dblTimeHigh, dblTimeLow 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




yyyy The year, in the range 1970..9999

mm The month, in the range 1..12

dd The day of the month

hh The hour, specified as a 24-hour clock.

mm Minutes past the hour, in the range 0..59

sec Seconds, in the range 0..59

nano Fractional seconds, specified in Nano seconds.

GE Digital 40

SetTimeFromComponentsHR_UTC SetTimeFromComponentsHR_UTC method can be used to set the Time Stamp for the point from High Resolution components in UTC Format.

Syntax SetTimeFromComponentsHR_UTC dblTimeHigh ,dblTimeLow ,yy ,mm, dd, hh, min, sec ,nano




yyyy The year, in the range 1970..9999

mm The month, in the range 1..12

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 0..59

nano Fractional seconds, specified in Nano seconds.

Example Sub Main() Dim pt1 As New point Dim pt2 As New point


pt1.ID = "gg"

pt2.ID = "test"

pt3.ID = "timeVal"


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


'Initialize Objects

yy = 2016

mm = 9

dd = 15

hh = 23

min = 59

sec = 59

nano = 9999999

SetTimeFromComponentsHR_UTC qlow, qhigh, yy ,mm, dd, hh, min,

sec, nano

pt1.Value = 60




GE Digital 41

Syntax SetTimeFromComponentsHR_UTC dblTimeHigh ,dblTimeLow ,yy ,mm, dd, hh, min, sec ,nano result = pt3.SetQuadIntValue(qHigh, qlow)

pt2.Value = "Fred"





Set points(0) = pt1

Set points(1) = pt2

Set points(2) = pt3







End If

End Sub

PointSetMultiple PointSetMultiple method can be used to do SetPoint operation on multiple points that are passed in the Array of Point Objects.

Syntax PointSetMultiple(point1[,point2[,point3...]])

Description Performs setpoints for up to 30 points in a single setpoint request. If a failure occurs the function returns false, otherwise true is returned.

Comments If you need to set the value of multiple points, use this function rather than issuing multiple single setpoint requests for faster script execution. The point ErrCode property will be set to a non-zero value for a setpoint that failed. The point ErrMsg property will contain the associated error message. There are two variants of PointSetMultiple. The first variant takes all the points declared in the argument list. The second variant takes an array.

Example Sub Main()

Dim status As Boolean

Dim sp1 As New Point: sp1.Id = "SP1"




sp1.Value = 1

sp2.Value = 2

sp3.Value = 3

sp4.Value = 4

status = PointSetMultiple(sp1,sp2,sp3,sp4)

If status = False Then

If sp1.ErrCode <> 0 Then

MsgBox sp1.ErrMsg

GE Digital 42

Syntax PointSetMultiple(point1[,point2[,point3...]]) End If

End If

’Using an array

Dim points(1 To 4) As Point

Set points(1) = sp1

Set points(2) = sp2

Set points(3) = sp3

Set points(4) = sp4

status = PointSetMultiple(points)

End Sub

Error Message

Point.ErrCode Integer value containing the error code for a failed call to PointSetMulitple or PointSetMultipleEx, or zero for a successful operation. Point.ErrMsg String value containing the error message for a failed call to PointSetMulitple or PointSetMultipleEx, or empty string for a successful operation

PointSetMultipleEx PointSetMultipleEx method can be used to do SetPoint operation on multiple points that are passed in the Array of Point Objects.

Syntax PointSetMultipleEx (password,point1[,point2[,point3...]])

Description Performs setpoints for up to 30 points in a single setpoint request, using the provided setpoint password. If a failure occurs the function returns false, otherwise true is returned.


Example Sub Main()

Dim status As Boolean

Dim pwd As String

pwd = "mypassword"





sp1.Value = 1

sp2.Value = 2

sp3.Value = 3

sp4.Value = 4

status = PointSetMultipleEx(pwd, sp1, sp2, sp3, sp4)

If status = False Then

If sp1.ErrCode <> 0 Then

MsgBox sp1.ErrMsg

GE Digital 43

Syntax PointSetMultipleEx (password,point1[,point2[,point3...]]) End If

End If

’Using an array

Dim points(1 To 4) As Point

Set points(1) = sp1

Set points(2) = sp2

Set points(3) = sp3

Set points(4) = sp4

status = PointSetMultipleEx(pwd, points)

End Sub

Error Message


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(42633.0630673264)

Set oPointArray(0) = oPointObj


oPointObj.Id = "A2"





oPointObj.Id = "A3"

GE Digital 44

Syntax PointUpdateMultiple arrayOfPointObjects oPointObj.Value = 44




oPointObj.Id = "A4"





oPointObj.Id = "A5"




bResult = PointUpdateMultiple(oPointArray)

End Sub

Example 2

Sub Main()




pt1.ID = "gg"

pt2.ID = "test"

pt3.ID = "timeVal"


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


'Initialize Objects

yy = 2016

mm = 9

dd = 15

hh = 23

min = 59

sec = 59

nano = 9999999

SetTimeFromComponentsHR qlow, qhigh,yy,mm,dd,hh,min,sec,nano

pt1.Value = 60




GE Digital 45

Syntax PointUpdateMultiple arrayOfPointObjects

result = pt3.SetQuadIntValue(qHigh, qlow)

pt2.Value = "Fred"





Set points(0) = pt1

Set points(1) = pt2

Set points(2) = pt3







End If

End Sub

CIMPLICITY.PointSetMultiple CIMPLICITY.PointSetMultiple method can be used to do SetPoint operation on multiple points that are passed in the Array of Point Objects.

Syntax CIMPLICITY.PointSetMultiple(point1[,point2[,point3...]])

Description Performs setpoints for up to 30 points in a single setpoint request. If a failure occurs the function returns false, otherwise true is returned.


Example using System;

using System.Collections.Generic;

using Proficy.CIMPLICITY;

public class GetSetNET

{

public void Main()

{

int status;

Point[] array = new Point[4];

using (Point sp1 = new Point(),sp2 = new Point(),sp3 =

new Point(),sp4 = new Point())

{

sp1.Id = "SP1";

sp2.Id = "SP2";

sp3.Id = "SP3";

sp4.Id = "SP4";

GE Digital 46

Syntax CIMPLICITY.PointSetMultiple(point1[,point2[,point3...]])

array[0] = sp1;

array[1] = sp2;

array[2] = sp3;

array[3] = sp4;

sp1.Value = 1;

sp2.Value = 2;

sp3.Value = 3;

sp4.Value = 4;

status = Cimplicity.PointSetMultiple(array);

}

}

}

Error Message


CIMPLICITY.PointSetMultipleEx CIMPLICITY.PointSetMultipleEx method can be used to perform SetPoint operation on multiple points that are passed in the Array of Point Objects.

Syntax CIMPLICITY.PointSetMultipleEx (password,point1[,point2[,point3...]])

Description Performs setpoints for up to 30 points in a single setpoint request, using the provided setpoint password. If a failure occurs the function returns false, otherwise true is returned.





public class GetSetNET

{

public void Main()

{

int status;


using (Point sp1 = new Point(),sp2 = new Point(),sp3 =

new Point(),sp4 = new Point())

{

sp1.Id = "SP1";

sp2.Id = "SP2";

sp3.Id = "SP3";

sp4.Id = "SP4";

GE Digital 47

Syntax CIMPLICITY.PointSetMultipleEx (password,point1[,point2[,point3...]])

array[0] = sp1;

array[1] = sp2;

array[2] = sp3;

array[3] = sp4;

sp1.Value = 1;

sp2.Value = 2;

sp3.Value = 3;

sp4.Value = 4;

status =

Cimplicity.PointSetMultipleEx("MyPassword",array);

}

}

}

Error Message


GE Digital 48

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:

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 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




public class PointUpdateMultiple

{

public void Main()

{

int status;


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";

array[0] = sp1;

array[1] = sp2;

sp1.Value = 60;

sp2.Value = "Fred.Net";Ye

sp1.TimeStamp = date1;

sp2.TimeStamp = date1;

status = Cimplicity.PointUpdateMultiple(array);

}

}

}


GE Digital 49

2.10.6 CIMPLICITY v9.0 SIM 23: Parameters for reloading .NET Assemblies

DE18203 SF-00428119 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. To resolve this issue, starting from CIMPLICITY 9.0 SIM 23, the below mentioned global parameters have been added:

Parameter Value Meaning Values/ Ranges

EM_SCRIPT_RECOMPILE_ALWAYS Specifies if the script must be forcefully recompiled on every project start

Y or y .NET Assemblies will be recompiled on every project start

N or n .NET Assemblies will not be recompiled on every project start

EM_SCRIPT_COMPILE_WAIT Specifies the time to wait before proceeding to use the generated DLL.

10000 Default time to wait before loading scripts asynchronously

0 - 30000 Wait time Limits before loading scripts asynchronously


GE Digital 50

2.11 TRACKER/ORDER EXECUTION MANAGEMENT

2.11.1 CIMPLICITY v9.0 SIM 1: Tracker Order/Execution Management Enhancements

The following new Enhancements have been added to CIMPLICITY v9.0 SIM 1:

o New Support

o PRT and TADB Differences

o TADB/Historical TADB Maintenance:

o New Global Parameters

New Support Tracker and Order Execution Management now support:

➢ Long point names. ➢ Long event names. ➢ Long status messages. ➢ Microsoft SQL Server 2014.

PRT and TADB Differences The following new features and enhancements have been added to more precisely detect and report discrepancies that exist between PRT and TADB data.

➢ Detect logical discrepancies between Tracker and TADB ➢ Differential Report Timestamps ➢ Selective Differential Reports ➢ Locationless Item Report

See the "4. TADB/PRT Backing File Synchronization and Recovery" section in the CIMPLICITY documentation for details. TADB/Historical TADB Maintenance PRT no longer deletes items from the TADB except when the archive disposition is used. All items are archived to the Historical TADB to prevent accidental deletion of item data. The archive disposition only indicates when they are archived, not if they are archived. Archiving misplaced or deleted items in TADB and archived items in Historical TADB is handled with rule based SQL Agent jobs that are configured and started by the normal CIMPLICITY project upgrade processes. PRT no longer deletes items from the TADB except when the archive disposition is used. PRT archiving functions as it always has; it:

✓ Deletes the item from PRT. ✓ Sets the Active column for the item in TADB to 0. ✓ Deletes the item from TADB.

The 0 value for the item's Active column is sent to the Historical TADB; the item, which is then ignored, remains archived.

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000001__Tracker_Order_Execution_Management_Enhancements.htm#Support

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000001__Tracker_Order_Execution_Management_Enhancements.htm#Differences

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000001__Tracker_Order_Execution_Management_Enhancements.htm#Maintenance

mk:@MSITStore:C:/CIMPLICITY_SIMs/CIMPLICITYSIMIPIs/CIMPLICITYSimIPISources/V9.0/Readme900027/readme.chm::/NewFeaturesEnhancements/CIMPLICITY_v9.0-000001__Tracker_Order_Execution_Management_Enhancements.htm#Parameters

GE Digital 51

Notes ➢ All items are archived to the Historical TADB to prevent accidental deletion of item data. The archive

disposition only indicates when they are archived, not if they are archived. ➢ Archiving misplaced or deleted items in TADB and archived items in Historical TADB is handled with

rule based SQL Agent jobs that are configured and started by the normal CIMPLICITY project upgrade processes.

➢ Following are definitions for terms that help to indicate how data is maintained in PRT, TADB and Historical TADB.

Term Definition

Remove Generically explains when data, in the context of Archive, Delete and Purge, is no longer there, without reusing the other terms and creating circular definitions.

Archive Delete from PRT and TADB, but not from Historical TADB. Note: Scripts, for example, can archive an item at anytime

Delete The definition for delete is revised slightly after the Historical TADB/TADB Maintenance enhancements have been implemented.

Before enhancement

Deleted data from PRT, TADB, and Historical TADB. Note: Deleting is valuable for temporary items that do not need to be kept for a long time.

After enhancement

Delete from PRT and remove the region from the TADB item. Note: This mimics behavior when there is a region overflow.

Purge Delete old previously archived items in Historical TADB.

A TADB Maintenance dialog box enables a user to change the settings for the TADB maintenance job.

A Historical TADB Maintenance dialog box enables a user to change the settings for the Historical TADB maintenance job.

See the "Step 6.4. Perform TADB/Historical TADB Maintenance" section in the CIMPLICITY documentation for details. New Global Parameters New global parameters have been added:

GE Digital 52

Parameter Name Comments

TRKCOLLECTOR_COMM_TOUT To specify the number of seconds before TrkCollector gives up on a SQL command.

TRKCOLLECTOR_CONN_TOUT To specify the number of seconds TrkCollector can take to get a SQL connection.

See topics with the same name in the CIMPLICITY documentation for more details.


2.11.2 CIMPLICITY v9.0 SIM 6: Enhancements to support usage of PRTCNT from TADB

Background ➢ PRTCNT would experience command timeouts during startup while using TADB. ➢ Evaluation of values by PRTCNT would take longer time. ➢ PRTCNT was not able to treat a project as not having TADB enabled.

US8127: Changes have been made to improve the usage of PRTCNT from TADB. These changes will ensure that:

➢ PRTCNT does not experience command timeouts at startup while using TADB. ➢ The values are evaluated much faster.

Tracker Global Parameter The following global parameter allows PRTCNT to ignore TADB when the TADB product option is enabled.

PRTCNT_USE_TADB

For Project

Purpose To enable PRTCNT to ignore the TADB option even if it is enabled.

Value Values are as follows

Y PRTCNT will use TADB if the project has TADB Option enabled.

N PRTCNT will assume that the project does not have TADB Option enabled.


2.11.3 CIMPLICITY v9.0 SIM 8: Tracker Devcom Enhancements

US11447: Overview: Starting CIMPLICITY v9.0 SIM 8, on initial project configuration or project upgrade, the tracker projects will be automatically configured with a port: TRK0, and a device using that port called TRACKER. Additional ports and devices may be configured as needed. Notes

➢ When multiple ports and devices are configured, it’s best to try to divide large sequential areas of the tracking model among the ports, and further divide the model among the devices for best performance.

The Devcom process makes use of the device concept to represent worker threads within a Devcom process. Each thread can have its own behavioral settings. The below shown settings can be edited for modifying the behavior.

GE Digital 53

Property Details

Use TADB Purpose To indicate whether queries should go directly to the TADB, or be passed to the TrkCollector process for resolution.

Checked Queries will be directed to TADB

Unchecked Queries will be passed to TrkCollector process for resolution.

Default Value

Checked

Notes Since items are cached, changing the setting is most likely to affect initial cache loading time and item refresh time when items are modified

Sleep between data fetches

Purpose To specify refresh rate (in hundredths of a second) for refreshing point values.

Notes Larger values mean longer delays between a change and the update of relevant points. Smaller values put a greater demand on system resources.

After the devices are configured as desired, points can be configured to use those devices to subscribe to data in the tracking model. Notes

➢ All Tracker Devcom points are read only. ➢ On the device tab of a Tracker Devcom point, as shown below, the tracker runtime addressing can be

entered, as well as point update criteria selection.

GE Digital 54

➢ The recommended update criteria in most circumstances is On-Demand, Unsolicited, On Change to

cause the least amount of overhead when point values are changing slowly or when point values aren’t being viewed.

The addressing is aided by an address builder dialog, as shown below:

1. The region and location specify the part of the tracking model to display. Negative locations count from

the tail of the region. Therefore, ”-1” means the last location, ”-2” means the second from last location, and so on.

2. Item class and type are a mechanism to filter for specific items in regions where multiple items can share a location.

3. If a region has multiple items per location and class or type filtering isn't used, the item chosen is indeterminate.

4. If more than one item exists in a location with the same filtered class or type, the results are indeterminate.

5. ”Attribute” is the desired attribute to use to populate the point. See the TrkAttributes.Item method in the Tracker Agent Object Model for a list of valid system attributes.

6. All system, standard, and extended attributes are available. When manually entering addresses, the following address patterns are valid: /"REGION".location..."ATTRIBUTE" /"REGION".location."".""."ATTRIBUTE" /"REGION".location."ITEMCLASS"."ITEMTYPE"."ATTRIBUTE" /"REGION".location."ITEMCLASS".."ATTRIBUTE" /"REGION".location."ITEMCLASS".""."ATTRIBUTE" /"REGION".location.."ITEMTYPE"."ATTRIBUTE" /"REGION".location.""."ITEMTYPE"."ATTRIBUTE" When using array points, the location in the address specifies the location used to populate the first element. Successive locations will be used to populate successive elements. In the case of a negative location, successive elements are populated with counter-successive locations. Locations will be represented in the elements in the reverse order that they are stored in the tracking model.

GE Digital 55


2.11.4 CIMPLICITY v9.0 SIM 10: Tracker Collector Enhancements

US11450: Overview: Starting CIMPLICITY v9.0 SIM 10, extended attributes are being supported by TrkCollector.

Tracker Global Parameter The following global parameter allows PRTCNT to ignore TADB when the TADB product option is enabled.

TRKCOLLECTOR_ITEM_CACHE

For Computer

Purpose To Enable/Disable support for caching extended attributes in TrkCollector


Y Extended attributes will be cached by TrkCollector

N Caching of extended attributes by TrkCollector will be disabled.


GE Digital 56

2.12 USERS/WINDOWS AUTHENTICATION

2.12.1 CIMPLICITY v9.0 SIM 1: Windows Authentication: Allow Configuration Auto Login

In CIMPLICITY v9.0 R2+ Windows authentication can automatically login valid Windows users to: ➢ Perform CIMPLICITY configuration, even if CIMPLICITY Configuration Security is enabled. ➢ Access Proficy Change Management project features.


2.12.2 CIMPLICITY v9.0 SIM 1: Windows Authentication: And Quick Trends

In CIMPLICITY v9.0+ a user who is logged into CIMPLICITY through Windows Authentication can now view Quick Trends for any selected point. To incorporate this feature into your project.

1. Create a new global parameter named: QT_ENABLE_SQL_WINAUTHEN

For Windows Authentication Project

Purpose To support Windows Authentication with Quick Trends.

Value Enter one of the following.

1 or Y Supports Windows Authentication with Quick Trends.

N or NA

Does not support Windows Authentication with Quick Trends.

Default Value

NA

2. Select a point. 3. Select Log data on the point's Point Properties dialog box>General tab. 4. Do a configuration update. 5. Start the project. 6. Open a Quick Trend for the selected point.

GE Digital 57

Result: Quick Trends will retrieve point data from the SQL database using Windows Authentication irrespective of whether the user has logged into CIMPLICITY using Windows Authentication. See the "Windows Authentication Configuration" section in the CIMPLICITY documentation for details.


2.12.3 CIMPLICITY v9.0 SIM 24: Users/Windows Authentication

DE25927; SF-00443063 DE25928; SF-00444528 Starting CIMPLICITY 9.0 SIM 23, support has been provided to authenticate Domain Users in CIMPLICITY after explicit Logout action. To enable this functionality, the following global parameter has to be defined in CIMPLICITY Configuration:

Attribute Name

DOMAIN_USER_AUTOLOGIN

For Domain User Authentication

Purpose To support authentication of domain users in CIMPLICITY after explicit logout

Value Enter one of the following.

Y or y Allows domain user to log in automatically after explicit logout

N or n User must provide login credentials after explicit logout

Default Allows domain user to log in automatically after explicit logout

Note:

1. 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.

2. CIMPLICITY currently does not support Multiple Domains. Please ensure that Domain Name is not part of user name when calling from Scripts.

Supported UserName Format: cimpsetprojectuserpassword "UserName", "password", ProjectName

Unsupported UserName Format: cimpsetprojectuserpassword "DomainName\UserName", "password", ProjectName

GE Digital 58

3 FIXED DEFECTS

3.1 ISSUES RESOLVED: ALARMS.

3.1.1 CIMPLICITY v9.0 SIM 1

Feature Issue Resolved

HAV/Column Rename

DE6407 Case- 1-2462587106 SF-0077091

When an action was taken in the Historical Alarm Viewer (HAV) column names that had been changed reverted to the original name. Example If a button was clicked or the HAV was double-clicked to display as a full screen a column name that was changed from Column1 to Caption 1 reverted to Column1

Now when an HAV column is renamed it retains its new name.

Enterprise Projects/Language Translation Memory Leaks

DE6837 Case-1-3063964408 SF-00177315

When Language Translations were configured for an Enterprise source project, they were sent to the remote Enterprise project along with alarms. However, this data was not released in the Enterprise project's Alarm Management Resident Process (AMRP) memory causing it to accumulate as a memory leak.

Alarm translation data is now released and no longer accumulates as a memory leak.

New Script/*.bcl extension

DE6873 Case-NA SF-00233816

If *.bcl script was duplicated in a class

using the CIMPLICITY Workbench>Class Properties dialog box>Scripts tab>Duplicate button it would create a new script but the new script did not have any extension at all.

When a *.bcl script is duplicated in a

class using the CIMPLICITY Workbench>Class Properties dialog box>Scripts tab->Duplicate button it now adds a *.bcl extension to the

new script.

Alarm Printer/Too Many Rows

DE6990 Case-NA SF-00238287

The Alarm Printer would always print two or more rows even when only one row was necessary.

The Alarm Printer now only prints the number of rows required to print the complete report.


GE Digital 59



alarm.idt/Corrupted Record Entry

DE7268 SF-00243238

If a project contained a corrupted record entry (e.g. Alarm ID as NULL) in the alarm.idt file, the alarm

functionality did not work correctly.

If a corrupted record entry is detected in the alarm.idt file

1. The corrupted entry is skipped. 2. The following error is sent to the Status

Log. "Unexpected Error: found invalid alarm id in alarm definition"




HAV/Column Rename

DE7404 SF-00177389

When an action was taken in the Historical Alarm Viewer (HAV) column names that had been changed reverted to the original name. Example If a button was clicked or the HAV was double-clicked to display as a full screen a column name that was changed from Column1 to Caption 1 reverted to Column1.

Now when an HAV column is renamed it retains its new name.




Alarm Viewers/Alarm Message

DE8328 SF-00289568

When using the %% symbol in an alarm message to display a percent (%) sign, the alarm message would not evaluate/display properly.

Alarm Messages now display properly the percent symbol when %% is used in the message.


GE Digital 60



HAV/ QUERY_UTC_ONLY Flag

DE10756 SF-00254845

When QUERY_UTC_ONLY flag is set to X for HAV control does not filter of alarms based on timestamp field as expected.

When QUERY_UTC_ONLY flag to X for HAV control, the alarms are now filtered based on timestamp field as expected.




Alarm Manager Crash

DE11149 SF-00283586

When running an Enterprise source project configured with Alarms, the Alarm Management Process crashes randomly.

When running an Enterprise source project configured with Alarms, the Alarm Management Process no longer crashes.




Alarm Data/ Alarm Message Logging Settings

DE11164; SF-00320189 DE10662; SF-00315405

When upgrading a project with logging attributes enabled for alarm log table, alarm message does not occur as expected.

When upgrading a project with logging attributes enabled for alarm log table, alarm message now gets logged properly.




Alarm Manager Crash Issue

DE6927 SF-00177372

When setpoint ranges specified for alarm limits are out of the converted value range, the alarms do not work properly.

The alarms work as expected when setpoint ranges specified for alarm limits are out of converted value range.


GE Digital 61



Alarms/ Application Crashes

DE15930 SF-00374453

Intermittent AMRP.exe process crashes occur during runtime.

Intermittent AMRP.exe process crashes no longer occur during runtime.

Alarms/ Alarm Process Crash

DE16186 SF-00379017

When executing CIMPLICITY Project, Alarm Management Resident Process crashes are observed intermittently.

When executing CIMPLICITY Project, Alarm Management Resident Process crashes are no longer occur.

Alarms/ Delayed alarms and Dead Bands

DE16370 SF-00178157

When a point configured with an alarm having Deadband and a Delay, is used in a CIMPLICITY project, the alarms are not generated 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.

Alarms/ Auto Timed Acknowledges

DE14947 SF-00364472

When a point configured with an alarm having timed auto acknowledge, is used in a CIMPLICITY project, the alarms are not generated properly.

When a point configured with an alarm having timed auto acknowledge, is used in a CIMPLICITY project, the alarm is now generated properly.

Alarm Viewer/ Alarm Message String

DE16116 SF-00311065

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.

When viewing alarms in Alarm Viewer, the device point state being displayed now shows the device availability status properly.




Alarms/ Alarm Message

DE17607 SF-00391178

When $DOWNLOAD Alarm is used in alarm messages, "BAD FIELD" gets populated into the alarm message for the $DOWNLOAD Alarm.

When $DOWNLOAD Alarm is used in alarm messages, the alarm message for the $DOWNLOAD Alarm now gets generated properly.

Alarms/ ANA Expressions

DE17369 SF-00387489

When ANA() expressions are used for device points in screens, the expression returns TRUE even if alarm is not present on point.

When ANA() expressions are used for device points in screens, the expression now returns TRUE only if alarm is present on point.


GE Digital 62



Alarms/ Class Object Alarm Routing

DE17929 SF-00393568

When Alarm Data Item is enabled for an edited class object, Alarm Routing Properties are not set properly for the Alarm Data Item.

When Alarm Data Item is enabled for an edited class object, Alarm Routing Properties are now set properly for the Alarm Data Item.




Alarms/ Alarm Field Errors

DE17933 SF-00177288

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.

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.





DE18703 SF-00350770

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.


GE Digital 63



Alarms/ Historical Alarm Viewer

DE16732 SF-00427622

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.

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.

Alarms/ Alarm Manager

DE14680 SF-00413057

When screen containing Trend Object is opened in viewer node, "Unknown alarm manager - AMRP " error message gets logged into system log.

When screen containing Trend Object is opened in viewer node, the error message no longer gets logged into system log.




Alarms/ Alarm Generation

DE19765 SF-00437231

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

Alarm Viewer/ Alarm Message String

DE25789 SF-00422053

When resources are dynamically added to remote project at runtime, the alarms for points are not visible in Alarm Viewer on Enterprise Project

When resources are dynamically added to remote project at runtime, the alarms for points are now displayed properly in Alarm Viewer on Enterprise Project


GE Digital 64




DE55824 SF-00460152

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.


GE Digital 65

3.2 ISSUES RESOLVED: CIMEDIT/CIMVIEW.



.cimrt Screens/Linked Objects

DE6069 Case-NA SF-00207874

When an attempt was made to insert a linked object (via the Object Explorer) on a target screen and the source screen was a *.cimrt

(runtime-only) screen, the target screen would hang.

Objects linked to a *.cimrt screen can

now be successfully inserted into target screens.

Blinking Linked Objects/Alarm Acknowledged

DE6075 Case-1-3956647848 SF-00179060

When Multiple blinking linked objects on multiple screens that were:

• Upgraded from CIMPLICITY v6.0.

• In alarm state.

• Included ANA in the blink expression.

Were acknowledged Then Only the object on the active linked object screen stopped blinking.

When multiple blinking linked objects on multiple screens are in alarm state and then acknowledged, all the objects stop blinking.

Polyline Objects with Round Edges

DE7086 Case-1-3402885641 SF-00179164

CimEdit polyline objects that were designed with round edges in CIMPLICITY v7.0 SIM 27 had sharp edges when the screen was opened in CIMPLICITY v8.2.

CimEdit polyline objects that were designed with round edges in CIMPLICITY v7.0 SIM 27 continue to have round edges when the screen is opened in CIMPLICITY v8.2 SIM 29 or higher.

CimView Screens/Thin Lines around Edges

DE6096; Case-1-3463606171; SF-00178020 DE6095; Case-1-3201370088; SF-00177598

Thin lines that were not configured to display, incorrectly displayed around one or more edges of large CimView screens.

CimView screens that are not configured to have borders now do not display lines around one or more edges.

GE Digital 66


Smart Objects/Elements in an Array

DE6253 Case-1-3500942060 SF-00177524

CIMPLICITY v8.2 Smart Objects that used an element from an array as a data source did not report (display) the correct value. Example A button continued to display 0 when it was clicked. It did not change to 1 when it was configured to: 1. Use an element in an array as the value. 2. Display a toggled BOOLEAN value each time it was clicked (0 to 1; 1 to 0). 3. Initiate with a 0 value.

CIMPLICITY v8.2 Smart Objects now display the correct value when the value comes from an element in an array point.

CimLayout/Borders around Frames

DE6097 Case-1-2520789631 SF-00179513

CimLayout would insert a 1-pixel wide border around each frame whether or not it was split.

CimLayout no longer inserts a border around frames that are not split.

Global Script Open Messages

DE6101 Case-1-3499916325 SF-00180149

(Began in CIMPLICITY v8.2) When inserting a class object onto a CimEdit screen, which already had a global script running, also caused the global script to run, an error message displayed reporting the following. The script is currently running, you will need to load the script when it is not running. The message would close and the script would continue to run when an OK button was clicked.

In this situation, a message will continue to open; however, it will now display the name of the script that is running.

Deployment/*.navbar DE6087 Case-1-2854744722 SF-00177513

When deployment updates included the navigation file (*.navbar), the

Navigation bar buttons would become blocked. CimView would have to be closed and re-opened to enable the buttons.

Navigation bar buttons now perform properly after a deployment update of the *.navbar file.

GE Digital 67


Navigation Bar/Standard w/Children

RALLLY-DE6088 Case-1-3236440920 SF-00180346

When a Standard Navigation bar was configured with children the navigation banner would display siblings rather than children.

A new option added to the Navigation Configuration Tool (BarStyle) enables a screen designer to configure whether siblings or children display on the Child menu bar

Style Name Description

Old Bar

Standard w/ Child

Maps to Standard w/ Child (Siblings) Note: This is the existing behavior that will show siblings in the submenu

New Bar

Standard w/ Child (Children)

Can be configured to show the selected node's children in the submenu.

Navigation Tree/Nodes at Bottom

DE6115; Case-1-3377201911: SF-00177437 DE6106; Case-1-3971212742; SF-00179215

When the navigation bar was in Tree View, it was difficult, at times impossible, to select nodes that required scrolling down the tree to be reached. This included an issue that occurred after a node was selected. Nodes that were closer to the bottom of the tree view could not be selected until the tree was scrolled, at least slightly.

Nodes, even at the bottom of a Navigation tree that require scrolling to be reached can be easily selected without interruptions.

Text Objects/Edit DE6110 Case-1-3862074681 SF-00178162

If a user scrolled to the top line of a multi-line text or text button object and attempted to edit it, CimEdit would crash.

Users can successfully scroll to the top line of a multi-line text or text button object and edit it.

CimLayout/ OnOpenScreen

DE6119 Case-1-2657929791 SF-00183999

When a CimView screen that was opened through CimLayout called code that accessed the CimLayout Object Model from an OnOpenScreen script, it would fail during the first startup. Note: CimLayout was not fully initialized; objects and variables would not be populated.

When CimLayout starts if the CimView screen is not ready read, CimLayout will pause until the screen is fully initialized before opening it.

GE Digital 68


WebBrowser ActiveX Control Shrinking

DE6433; Case-1-2551307002; SF-00177344 DE6831; Case-1-3816998441; SF-00178667 DE6826; Case-1-3679558316; SF- 00178098 DE6830; Case-1-3899965061; SF-00178715

A Microsoft WebBrowser ActiveX control embedded in a CimView screen would become smaller each time the CimView screen was overlaid by another screen or closed and then reopened.

Microsoft WebBrowser ActiveX controls embedded in CimView screens retain their original size after the screen has been overlaid or closed and then reopened.

Popup Screens DE6756 Case-1-1415473001 SF-177245

After a CimView screen opened a Popup screen and the: 1. Original screen was doing a Point.Get or Point.Set while

it was not in focus. 2. Popup screen had an AMV

OCX control

3. Network was disconnected and reconnected while the Popup screen was open. 4. Popup screen was closed. The original CimView screen hung while the script processed a thread indefinitely.

Now, when a CimView screen opens a Popup screen, it continues to run correctly, even when scripts are run and the network is disconnected and reconnected.

Navigation Bar/Button Text Alignment

DE6828 Case-1-3847888401 SF-00178714

When a project was upgraded from CIMPLICITY v8.1 to v8.2, text that was left-aligned on the Navigation toolbar changed to be center-aligned. Note: The change was made based on a client request; however, it did not work with other configurations.

A new BOOLEAN flag (Left Aligned Text) has been added as part of node's Button configuration; the flag will enable the CimEdit screen designer to force the text alignment on the button to the left. Important

• CimEdit screens that have been upgraded from a CIMPLICITY version that is less than v8.2 have this flag set to False by default; the text is center aligned.

• The flag must be set to True for each node that requires the text to be left-aligned.

Two Screens/Message Generated by a Script

DE7029 Case-NA SF-00226932

When two screens simultaneously tried to open a message generated by a script from within a screen script CimView would hang.

Two screens can now successfully open a message generated by a script from within a screen script.

GE Digital 69


.NET Controls/Memory Leak

DE7031; Case-NA; SF-00180226 DE7030; Case-NA; SF-00224466

.Net controls that implemented

IDisposible would not have the

Dispose method called when the

screen that contained the control was closed. This could cause a memory leak.

For controls that implement an IDisposable interface, the Dispose

method is now called when the screen is closed.

CimView/Opening a Dialog Box (Additional Issue)

DE6121 Case-1-2721634611 SF-00177350

(On multi-monitor systems) Note: This issue was fixed almost entirely in SIM 26. However, an additional instance of CimView performing a call to open a dialog box caused CimView to crash.

The reported instance of CimView crashing when performing a call to open a dialog box has been fixed.




Variable Name Length

DE7384 SF-00255333

(Beginning in CIMPLICITY v9.0) An attempt to enter a screen variable name with more than 32 characters was prevented; instead a message would display reporting that: Variable Name should not be more than 32 characters.

Variable names can again be more than 32 characters in length.

Overlay Action/ Expression Evaluation

DE7250 SF-00240669

When a screen performed an Overlay action to

itself, expressions would not evaluate correctly on the screen.

When a screen performs an Overlay action to itself,

expressions will now evaluate correctly.

ActiveX Objects/Focus

DE7315 SF-00178037

The focus did not shift properly when many ActiveX objects (e.g. Microsoft Text Box, List Box, Combo Box) were included on a CimView screen and a user attempted to change the selection from one to another.

The focus now shifts properly among ActiveX objects on a CimView screen. When a user selects an object, that object becomes the active object.

GE Digital 70


Linked Objects/Unavailable or Blank

DE7357; SF-00177281 DE7358; SF-00177454 DE6248; SF-00177553 DE7356; SF-00205180 DE7355; SF-00208540

In some situations, linked objects and/or associated variable values became unavailable or blank.

Graphic objects are now refreshed with their latest expression evaluation results and/or associated variable values. Linked objects display properly; they are no longer unavailable or blank.




CIMPLICITY v9.0 Process/CIMPLICITY v8.0 Screens

DE7385 SF-00255128

When a CIMPLICITYv9.0 Viewer received point updates that indicated a point was unavailable from a CIMPLICITY v8.0 Server, it would crash.

A CIMPLICITY v9.0 Viewer no longer crashes when it receives point updates that indicate a point from a CIMPLICITY v8.0 Server is unavailable; it indicates the correct point state.

Line's Angle DE7434 SF-00257668

If a line object was drawn on a screen (e.g. horizontally) and an angle was applied (e.g. 90 degrees) that changed how it displayed (e.g. to vertical), the following occurred when the screen was: 1. Saved, closed, re-opened. The line returned to its original position (e.g. horizontal). 2. Saved, closed, re-opened again. The line displayed in the configured angle (e.g. 90 degrees vertical).

If an angle is applied to a line object that is drawn on a CimEdit screen, the line displays in the configured angle whenever the screen is saved, closed and re-opened.

CimView Crash/Hovering over Objects

DE7477 SF-NA

In some cases, CimView would crash while hovering over objects on the CimView screen.

In the cases where CimView would crash while hovering over objects on the CimView screen, it now continues to run.

CimEdit/HAV/Windows Explorer

DE7413 SF-NA

GE Digital 71


If a CimEdit screen that had an HAV on it was opened through Windows Explorer and then closed, CimEdit would crash.

A CimEdit screen that includes an HAV can now be successfully opened through Windows Explorer and closed.




CimView/Multiple Monitors/Language Translations

DE7718 SF-00221235

CimView would crash when the same CimView screen displayed on multiple monitors and used language translations.

CimView continues to run if a screen displays on multiple monitors and uses language translations.




CimView/ /Convert command

DE7116 SF-00242031

Converting .CTX files using the /convert command line argument takes a long time to complete.

Conversion of .CTX files using the /convert command will no longer take a prolonged period of time.

CimView/ /Keypad Option

DE7352 SF-00252967

When CimView is initiated using the /Keypad command line argument and a ”variable setpoint” action with an enumerated point is performed, the virtual keypad is displayed rather than a choice of allowed enumeration values.

When CimView is initiated using the /Keypad command line argument and a variable setpoint action is executed the user is presented with a choice of allowed enumeration values.

CimView/Object Rotation

DE8006 SF-NA

After an object is rotated by setting the rotation angle, the value in the rotation field is unchanged.

After an object is rotated by setting the rotation angle value, the value in the rotation field is reset to zero.

CimView/ Print Support and CPU Consumption

DE8178 SF-00272666

Printing a CimView screen containing shadows results in high CPU consumption.

Printing a CimView screen containing shadows no longer results in high CPU consumption.


GE Digital 72



CimView/Cimview Crash on Script Execution

DE8462; SF-00274180

Executing GefAction.SetToAbsoluteSetPoint method causes CimView application to crash.

Executing GefAction.SetToAbsoluteSetPoint method no longer causes CimView application to crash.

Linked Objects/Unavailable or Blank

DE8483; SF-00267794 DE8485; SF-00273723 DE8846; SF-00296660

In some situations, linked objects and/or associated variable values became unavailable or blank.

Graphic objects are now refreshed with their latest expression evaluation results and/or associated variable values. Linked objects display properly; they are no longer unavailable or blank.

CimView/Distorted Menu Text

DE9039 SF-00295899

When generating text on an object in CimView via script, in some instances the text would appear upside down.

When generating objects via script, the displayed text now appears with the correct orientation.

GefLineFormat (object)/Text Objects

DE6081 SF-00178687

The GefLineFormat (object), which can be used to define the border attributes portion of an object did not produce correct results for text objects in CimEdit/CimView.

The GefLineFormat (object), which can be used to define the border attributes portion of an object now performs correctly for text objects in CimEdit/CimView.

Navigation Toolbar/CaptivePopups

DE8458 SF-00291705

When popup windows are opened, and the navigation toolbar is enabled in CimView, then the popup window would also have the navigation toolbar visible.

Now when popups are opened from a screen that has the navigation toolbar visible, the toolbar will not appear on the popup itself.


GE Digital 73



.NET Control/ListBox control

DE9709 SF-00295518

When multiple selections are done in a .NET ListBox control, there is no means to get the selected items count and selected items as needed.

Count and GetAt methods are now exposed from .NET Orion Control's IListBox interface. These functions can be used to obtain the selected items count and also to obtain an item at given index. Example 1: ListBox1.Items.Count // Returns the number of items

selected.

ListBox1.Items.GetAt(Index) // Returns the item at

specified index.

Example 2: Sub GetData()

Dim cimOleObj As

Occ_System_Windows_Forms.IOccListBox

Dim oObj As Object

Dim var1 As Variant

Dim iCount As Integer

Set oObj =

cimGetScreen.Object.Objects.Item("MyListBox").OleObje

ct

Set cimOleObj = oObj

Set xItems = cimOleObj.Items

iCount = xItems.Count 'give the items count

MsgBox iCount

var1 = xItems.GetAt(0) 'Give the value at index: 0

MsgBox "Index: 0, Value = " & var1

End Sub

.NET Object/Data Corruption

DE9735 SF-00273507

When Undo/Redo operations are performed on .NET Controls that are placed in a CimEdit Screen, object corruption occurs.

Performing Undo/Redo operations on .NET Controls that are placed in a CimEdit Screen, no longer results in object corruption.

GE Digital 74




Cimview Crash/ ZoomToRectangle Method

DE9847 SF-00297742

When GefScreen.ZoomToRectangle method is used in scripting to perform zooming operation on CimView Screen, CimView application would occasionally crash. Also, the GefScreen.ZoomToRectangle method did not work as expected.

Performing zooming operation through scripting by making use of GefScreen.ZoomToRectangle method no longer causes CimView application to crash. Additional Information: ZoomToRectangle method is designed to allow users to specify a rectangle area on the screen in document coordinates (TWIPS) and fill the screen with that rectangle. Example: Sub GefScreen_ZoomToRectangle()

Dim oCimScr As GefScreen

Set oCimScr = CimGetScreen

'Specify

Top/Bottom/Left/Right in TWIPS.

oCimScr.ZoomToRectangle

(390 * 20), (365 * 20), (80 *

20), (777 * 20)

End Sub

Cimview Crash/ Visibility Animation Expression

DE9154 SF-00299391

A crash would occur, when a screen that contained a text object is configured with a Visibility Animation Expression, is opened in CimView

A screen, that contains a text object configured with Visibility Animation Expression, can now be opened in CimView successfully.

CimView/Hidden Objects

DE6143 SF-00043167

Objects that were hidden behind other objects (on a CimView screen) were selectable.

Now when there is a grouped object with action objects on the top level of a CimView screen, objects that are at the back of the grouped object (and cannot be seen) cannot be selected.

Notes

• This behavior is similar to CIMPLICITY v8.1.

• If objects at the back of grouped objects should be selected, this can be achieved through visibility animations or frames with visibility expressions.

GE Digital 75




CimView/ /noexit command

DE10232 SF-00310745

When multiple CimView screens are launched with "/noexit" command line parameter, the exit option gets disabled only for the first CimView screen.

Now, all CimView screens launched with "/noexit" command line parameter, will have the exit option disabled as expected.

CimView/ Horizontal Scrollbar

DE9842 SF-00307096

When navigating between screens, the horizontal scroll bar disappears at times and prevents users from using the scrolling functionality

Users can now navigate between screens, without any scroll bar disappearance issues.

Objects with Shadow

DE7739; SF-00217928 DE10660; SF-00238425 DE10668; SF-00203258

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.

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.




CimView/ Strings with White-space

DE9153 SF-00298360

When evaluating expressions with strings having white-space, the concatenation of strings results in incorrect trimming of white-space.

When evaluating expressions with strings having white-space, the white-space now gets properly trimmed during string concatenation.

CimView/ Non-Array point expressions

DE11397 SF-00322556

When non-array points are represented as array points with zero index in expression, incorrect results are given by the expression parser.

When non-array points are represented as array points with zero index in expression, the expression parser evaluates them properly and returns correct results.

CimView/Expression Parser

DE11380 SF-00288604

GE Digital 76


Parsing of expressions for invalid / unavailable points in CimView causes invalid outcomes.

Parsing of expressions for invalid / unavailable points in CimView no longer causes invalid outcomes.




CimView/ Application Hang

DE12293 SF-00329891

When executing SQL query commands through script from CimView screens, CimView application hangs are observed at times with steady growth in memory consumption.

When executing SQL query commands through script from CimView screens, application hangs and increase in memory consumed are no longer observed.

CimView/ Performance Issues

DE13237; SF-00338726 DE13239; SF-00335744 DE13241; SF-00327562 DE13243; SF-00330754

When CimView application is run, increased CPU Usage durations are observed during normal operations. This results in delayed responses from CimView application to user actions.

When CimView application is run, increased CPU Usage durations are no longer observed during normal operations. Also, there are no delayed responses from CimView application to user actions.

CimView/ SetVariable Operation

DE12074 SF-00329554

When trying to set value to a screen level variable, CimView application crash can occur if the screen contains group objects with frame containers.

CimView application no longer crashes when value is being set to a screen level variable on screens that contain group objects with frame containers.


GE Digital 77



CimView/ Animation Issues

DE8260; SF-00289187 DE8810; SF-00295447 DE11709; SF-00290139 DE12608; SF-00335062 DE12685; SF-00307497 DE12779; SF-00336336 DE13086; SF-00338798 DE13267; SF-00297212 DE13952; SF-00315058 DE14001; SF-00350614 DE14065; SF-00316990 DE14100; SF-00327847 DE14102; SF-00343649

When viewing CIMPLICITY Screens: 1. The objects on CimView Screens periodically go unavailable. 2. Expression evaluation does not happen properly at random. 3. Screens being brought from cache do not redraw properly.

CIMPLICITY Screens now display graphics without any issues. The animations and expression evaluations now happen as expected without any display issues.

CimView Crash Issue

DE8888 SF-00294493

CimView application would crash at times when executing a Script

CimView application crashes no longer occur during script executions.




CimView/ Advanced Viewer Crashes

DE14776; SF-NA DE14945; SF-NA

When using Advanced Viewer, intermittent crashes are observed during screen overlay and script execution.

When using Advanced Viewer, screen overlay and script execution occur properly without any crash issues.

CimView/ Screen Upgrade

DE13540 SF-00338211

Upgrading a CimView screen that has buttons using scripts may not upgrade properly into CIMPLICITY 9.0.

Upgrading of a CimView screen that has buttons referencing scripts now upgrade properly to CIMPLICITY 9.0


GE Digital 78




DE14104 SF-00277428

When viewing CIMPLICITY Screens: 1. The objects on CimView Screens periodically go unavailable. 2. Expression evaluation does not happen properly at random. 3. Screens being brought from cache do not redraw properly.

CIMPLICITY Screens now display graphics without any issues. The animations and expression evaluations now happen as expected without any display issues.

CimView/ ARC Objects

DE14514 SF-00357238

When Arc, Chord or Pie objects with start angle set to <= 1 are used in CimView Screens, they do not get rendered properly.

When Arc, Chord, or Pie objects with start angle set to <= 1 are used in CimView Screens, they now get rendered properly.




XY Plot/ Re-size Issue

DE15583 SF-00357019

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 a XY Plot control object (ActiveX control) is used to display data with multiple series, re-sizing of the control now happens properly.

CimView/ Application Hang

DE15178 SF-00363624

When a condition expression in CimView contains the "GT" (greater than) function, CimView hang could occur.

When the "GT" (greater than) expression is used in a CimView expression, it will no longer potentially hang.

CimView/ Objects with Shadow

DE10660; SF-00238425 DE10668; SF-00203258

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.

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.

CimView/ Expression Updates

DE16441; SF-00382378 DE16367; SF-00372068

When navigating between CimView screens, variable expression updates get triggered during screen open operation.

When navigating between CimView screens, variable expression updates no longer get triggered during screen open operation.

DE16331; SF-00359661 DE16334; SF-00379473

GE Digital 79



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.

CimView application crashes are no longer observed when CimView Screens are used in CimLayout configuration.




CimEdit/ Script Execution

DE17825 SF-00383299

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.

When logging into a CimView screen after switching users, the scripts configured for the screen now get executed after successful login.

CimEdit/ Group Containers

DE17654 SF-00393389

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.

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.

CimView/ CimLayout Configuration

DE17506 SF-00391732

When a CimLayout is configured to refer to a non-existing screen, crashes are observed when CimLayout is launched.

When a CimLayout is configured to refer to a non-existing screen, crashes are no longer observed when CimLayout is launched.

CimView/ Screen Navigation

DE17474 SF-00385221

When navigating between CimView screens using the navigation toolbar, memory leaks and intermittent crashes/hangs of CimView application are observed.

Navigating between CimView screens using the navigation toolbar now works properly and issues related to memory leaks and intermittent crashes/hangs of CimView application are no longer seen.

CimView/ Point View Dialog

DE17426 SF-00386571

When Point View is used in CimView, copying of all displayed points does not happen properly to the clipboard.

When Point View is used in CimView, all displayed points now get copied properly to the clipboard.

CimView/ ANA Expressions

DE18166; SF-00395793 DE18274; SF-00401761

When CimView is used to view CimScreens, the linked objects with color animation expressions that use

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.

GE Digital 80


AL() and ANA() functions are falsely activated on start of project.

CimEdit/ CTX File Format

DE17893 SF-00356113

When graphic screens configured with Forms.ComboBox objects are stored in .ctx file format, the screens can no longer be opened for editing.

Graphic screens having Forms.ComboBox objects configured that stored in .ctx file format can now be opened for editing.

CimEdit/ .NET Controls

DE16681 SF-00383990

.NET Controls created in CimEdit Screens under an account with elevated privileges are not accessible to other users.

.NET Controls created in CimEdit Screens under an account with elevated privileges are now accessible to other users.

CimEdit/ Upgraded Screens

DE10898 SF-00259630

When opening a screen that is upgraded to 9.0 Version, CimEdit crashes are observed.

When opening a screen that is upgraded to 9.0 Version, CimEdit crashes are no longer seen.

CimView/ Objects with Shadow

DE10660; SF-00238425 DE10668; SF-00203258

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.

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.

CimView/ Shadow Locations

DE17407; SF-00390874 DE17874; SF-00397614 DE18053; SF-00399566

When graphic screens are opened in CimView at runtime, the shadows for objects appear at incorrect location.

When graphic screens are opened in CimView at runtime, the shadows for objects now appear at proper location.




CimView/ Color Animation

DE18365 SF-00403111

When color animation is configured is configured for a group that has a text object without any animation configured, then at runtime the text object is not displayed properly.

When color animation is configured is configured for a group that has a text object without any animation configured, the text object is now shown properly at runtime.

CimView/ CimLayout Crash

DE18511 SF-00398103

When CimLayout application for a project is open, any attempt to logout currently

When CimLayout application for a project is open, currently logged-in user can successfully

GE Digital 81


logged-in user from the system results in CimLayout application crash.

log out from the system without any crash issues.




CimView/ Blink Animation

DE18727 SF-00415025

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.

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.

CimView/ Touch Enabled Screens

DE18746 SF-00412550

On touch enabled screens, Mouse down events do not handle properly by CimView application. Triggering of Mouse Down events occur in incorrect sequence.

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.

CimView/ OLE Objects

DE18861 SF-00387654

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 a screen that has multiple OLE Objects is opened in CimView application for editing, deletion of text from an OLE Object now works properly.

CimView/ .NET Control Properties

DE18698 SF-00415570

When properties of .NET Controls added in a screen are being edited, scrolling to the property to be modified does not happen properly.

When properties of .NET Controls added in a screen are being edited, property to be modified can now be scrolled to properly.


GE Digital 82



CimView/ Alarm Viewer

DE17227 SF-00429465

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.

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.

CimLayout/ File Browsing

DE18747 SF-00416485

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.

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.

CimView/ Terminal Server Sessions

DE10988 SF-00318176

When large number of Terminal Services sessions are open and CimView application is opened from one of the sessions, occasional application hangs occur.

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.

CimView/ "Always On Top" Option

DE16333 SF-00425480

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.

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 83



CimView/ Memory Leaks

DE18618 SF-00408888

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.

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.

CimEdit/ .NET Components

DE19098 SF-00419567

When a CimEdit screen having a frame container configured with .NET components and expressions is opened in CimView, the configured expressions are not evaluated properly when opening the screen.

When a CimEdit screen having a frame container configured with .NET components and expressions is opened in CimView, the configured expressions now evaluated properly on start.

CimEdit/ Expression Parser

DE16410 SF-00424954

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.

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.




CimView/ Linked Objects

DE19048; SF-00435114 DE22682; SF-00436901 DE25778; SF-00445980

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.

When a screen containing a linked object that is configured with locally defined event is viewed in runtime, the linked object now highlighted properly.

CimView/ Linked Objects

DE27370 SF-00447845

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 a screen containing a linked object, configured with screen overlay/screen open action is triggered in runtime, the configured actions now get executed properly.


GE Digital 84



CimView/ Application Crash

DE19746; SF-00394554 DE31438; SF-00429861 DE31442; SF-00429616

When running CimView application, occasional crashes and hangs are observed.

When running CimView application, occasional crashes and hangs are no longer seen.

CimView/ Memory Leak Issues

DE28675 SF-00452127

When CimView application is run with /NoScreenExit Command Line Argument, memory leaks are observed at runtime.

When CimView application is run with /NoScreenExit Command Line Argument, memory leaks are no longer observed at runtime.




CimEdit/ .NET Controls

DE37427 SF-00468341

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 working on CimEdit Screens, adding and removing a .NET Control from the CimEdit Screen will no longer delete the control from system as well.

CimView/ RichEdit Control

DE40565 SF-00473139

When working with RichEdit Control, copying the contents of the control does not work if the focus is not set on the control.

Copying the contents of RichEdit Control now works properly.


GE Digital 85



CimView/ /LoadPassword Parameter

DE49691 SF-00476196

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.

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.

CimView/ Color Animation

DE53972 SF-00485521

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.

CimView/ Application Crash

DE51948 SF-00464899

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

GE Digital 86


CimView/ Expression Evaluation

DE51067 SF-00486846

When viewing CIMPLICITY Screens configured with expression update events on screen startup, in CimView, the expression updates occur prematurely.

When viewing CIMPLICITY Screens configured with expression update events on screen startup, in CimView, the expression updates now occur properly after screen initialization.

CimView/ Expression Evaluation

DE39770 SF-00470620

When copying a button object from one screen to another, the procedures configured in the original button get deleted/modified during copy/paste operation.

When copying a button object from one screen to another, the procedures no longer get deleted/modified during copy/paste operation.




Advanced Viewer/ CimView Application Crash

DE58328 SF-00474634

When using CimView application in Advanced Viewer mode, periodic application crashes are observed with CimView application.

When using CimView application in Advanced Viewer mode, periodic application crashes no longer happen with CimView application.

CimView/ RichEdit Control

DE40565 SF-00473139

When working with RichEdit Control, copying the contents of the control does not work if the focus is not set on the control.

Copying the contents of RichEdit Control now works properly.


GE Digital 87



Advanced Viewer/ Point OPC Server

DE70825 SF-00554819

Updates made to Advanced Viewer in CIMPLICITY versions 8.2 and 9.5 are not ported to CIMPLICITY version 9.0.

Updates made to Advanced Viewer in CIMPLICITY versions 8.2 and 9.5 have been ported to CIMPLICITY version 9.0.

CimEdit/ Scripting Issues

DE67008 SF-00510966

When the content of a graphics screen is modified in CimEdit, changes made to screens through a script are not reflected even after CimEdit is closed.

The changes made to the screen will reflect only when the script is stopped. Note: In CimEdit, changes to a screen are not reflected when a script is running on that screen.


GE Digital 88

3.3 ISSUES RESOLVED: CLASSES AND CLASS OBJECTS



Role Deleted/Class Object Update

DE6394 Case-1-2776154652 SF-00067666

When a role was deleted, the role definition for class objects (Object dialog box>Alarm Routing tab) was not updated; the role was not deleted.

Note: The role was deleted on the Alarm Definition dialog box>Alarm Routing tab and on the Point Properties dialog box>Alarm Routing tab.

When a role is deleted, the role definition for class objects is updated.

Class C# Scripts/Script Editor

DE6993 Case-NA SF-00238766

On the CIMPLICITY Cass dialog box>Scripts tab, when an existing C#

script was either:

• Double-clicked.

• Selected and then the Properties button was clicked

Program Editor for .bcl scripts would

open instead of the CimScriptIDE Editor for C# scripts.

Now, on the CIMPLICITY Cass dialog box>Scripts tab, when a C# script is selected

to be opened in a script editor, the CimScriptIDE Editor opens.

Class Object Event/Action Orphans

DE7088 Case-NA SF-00240311

Actions could become orphaned from CIMPLICITY Class Object instances when using the CIMPLICITY Workbench and required manual IDTPOP / SCPOP

editing to delete them.

When event/action definitions are deleted or modified when configuring the class, the changes are reflected immediately for the objects; there is no need to modify the SC

files.


GE Digital 89



Point Cross Reference/Database Logger NULL Point ID

DE7115 SF-00235708

If a CIMPLICITY class data item had database logging enabled, at times, the: 1. Data did not log correctly. 2. Point Cross Reference displayed a NULL point ID.

1. CIMPLICITY Class data item that have database logging enabled, correctly log data. 2. Point Cross Reference reports the correct data.

Browse Buttons/Object Dialog Box Custom Tabs

DE7256 SF-00241994

In a CIMPLICITY class, if a custom tab was configured for that class object's dialog box, Browse buttons (e.g. for Points, Roles, Alarms) did not display for attributes that were located on those tabs.

Browse buttons now display for attributes located on a Class Object dialog box>Custom tab.

%VAL1({$OBJECT}.POINT})/ Class Data Item

DE7093; SF-00248185 DE7267; SF-00249533

Attempting to use %VALn functions in alarm

messages would generate errors and fail. Note: Functions included:

• %VAL1({$OBJECT}.COMMENT

• %VAL1({$OBJECT}.POINT})

%VALn functions

now work correctly when {$OBJECT}

is specified in point alarm messages.

Data Items/Device ID or Address Field values

DE7239 SF-00248775

(Beginning in CIMPLICITY v9.0) Class data items required values in the Device ID or Address fields. This prevented some sub-expressions (e.g. $ADDRESS_ADJ) from working properly.

Class data items no longer require values in the Device ID or Address fields.

Events/Attributes DE7433 SF-NA

(Beginning with CIMPLICITY v9.0) In some instances, particularly when using classes and class objects, the following did not perform correctly.

• Events that were configured with point attributes.

• Events and actions that were configured with user defined attributes.

• Change events on {$OBJECT}.SomeItem.$RAW_VALUE

attributes.

The events and actions in these instances now perform correctly. Important: The combination of the point ID and the attribute must be less than 53 characters. Point IDs with more than 32 characters are replaced with a GUID that is 32

GE Digital 90


characters. In this case, if the attribute ID has 23 characters or more, it cannot be used with the 32-character point ID.

Data Items/Logging Selections

DE7438 SF-00257944

(CIMPLICITY v9.0 SIM 1) Each Data Item dialog box>General tab had one Log data check box replaced with a Log to database and/or a Log to Historian check box. As a result {$OBJECT}.points that had both

Database Logger and Historian selected before the enhancement, had only Database Logger selected after the enhancement. Notes

• The availability of the Log to database and/or Log to Historian check boxes was based on whether Database Logger (SQL Server) and/or Historian were installed and enabled in the project)

• (CIMPLICITY v9.0 SIM 1) Log to database was checked on the Data Item dialog box>General tab; Log to Historian was not selected.

• The $LOG expression was

split into $LOG and

$LOG_HISTORIAN.

o $LOG remained set,

indicating Database Logger.

o $LOG_HISTORIA

N was not set.

Now, {$OBJECT}.points that had

logged to both Database Logger and Historian in CIMPLICITY v9.0 and lower, again have both Database Logger and Historian selected, if both continue to be installed and enabled. Note: $LOG and

$LOG_HISTORIAN are now both

set.


GE Digital 91



Classes/Objects Repeated Editing

DE7481 SF-00260711

Repeated editing of CIMPLICITY Class definitions and Object instances would eventually corrupt the event, action, and

event_action associations in the

Event Manager Resident Process (EMRP).

CIMPLICITY Class definitions and Object instances can now be edited repeatedly without affecting the associations in the EMRP.

Class re-import/Renamed Scripts

DE7536 SF- 00253614

One or more existing class objects could be deleted when the following occurred. 1. A class was imported. 2. A class script was renamed. Note: If the script was looked for using the original name, it did not exist. 3. The class was imported again. Result: Because the re-imported class could not recover the original script it could possibly delete one or more class objects.

Class objects are not deleted if classes are re-imported after a script is renamed.

Long Name in Warning Message

DE7451 SF-NA

When an attempt was made to delete a class/object event/action with a long name from the Event Editor, a warning message would report that the object: Event Name as GUID" cannot be deleted. Note: The warning message was expected; however, it should not have displayed the long event name as GUID.

When an attempt was made to delete a class/object event/action with a long name from the Event Editor, a warning message includes the actual class/object event/action name (instead of GUID).

Proc_or_srcpt

Field/Long Point Name

DE7462 SF-NA

In the Event Editor>Proc_or_srcpt field the entry GUID would display for a long point name instead of the actual point name.

The actual long point name now displays in the Event Editor>Proc_or_srcpt field.

DATA_ITEM_EXIST/Point

Configuration Validation

DE7543 SF-NA

When a class used the DATA_ITEM_EXIST expression,

object instances would validate the configuration of points that did not exist for an object instance.

Point configuration validation was not executed if the point will not be created for the object instance.

GE Digital 92




Classes/Non-class point reference

DE8067 SF-00283221

A point not derived from a class object cannot be used in point expression that are defined as a data item in a class object.

A point not derived from a class object can now be used in point expression that are defined as a data item in a class object.

Classes/Event/Action duplication

DE8068 SF- 00283584

Mixed case Event and Actions in a class definition cannot be duplicated.

Mixed case Event and Actions in a class definition can now be duplicated.

Classes/Dynamic class creation

DE8069 SF-00284127

Trying to dynamically create a CIMPLICITY class object results in an error.

CIMPLICITY class objects can now be dynamically created.

Class/Object Point Creation

DE8141 SF-00285666

Using a Point Browse object as defined on a Class Attribute results in an error when selecting a point ID that is not exclusively uppercase.

Mixed and lowercase point IDs may now be selected from a Point Browse object as defined by a Class Attribute.

Class Alarm Deletion DE8182 SF-00285824

When Alarm(s) derived from a class data were deleted from the Alarm List, the class object could not be modified or saved until the Alarm(s) were recreated.

Deletion of alarms associated with class data items is no longer allowed.

(Classes/Objects)/Change Approval

DE7935 SF-00255636

When modifying the Change Approval settings on a Class Data Item, the changes are not propagated in the definition of the points derived from the associated object.

Change Approval settings on a Class Data Item, are now propagated to the points derived from the associated object.


GE Digital 93



Classes/Object Creation

DE9150 SF-00298021

Creation of objects from a class fails if one or more data items of the class refer to long point name(s)

Objects can now be successfully created from a class that has one or more data items referring to long point name(s).

Classes/Non-class point reference

DE9151 SF-00298398

A dynamically created class/object that has either a long point name or references a non-class/object point, will not display the point value at runtime.

A dynamically created class/object that has either a long point name or references a non-class/object point, will now display the point value at runtime as expected.




Classes/ Warning Messages

DE9622 SF-00304402

When objects of a class that are configured with data item containing valid expression are created, warning messages would be logged to the status Log.

Warning messages are no longer logged in the status log when an object of a class, configured with data item containing valid expression, is created.

Class Import/Export/ .NET Script Compilation

DE10153 SF-00312256

When a class containing a .NET Script is exported and imported back, the compilation of the imported .NET script fails.

The compilation of a .NET Script contained in a class, that is exported and imported back, now succeeds without any failures.

Server/Viewer DE9834 SF-00219769

When using CIMPLICITY 8.1, if the screens were viewed in CimView on a CIMPLICITY 8.2 GlobalView/WebSpace server, the animations for Class Object graphics would not work.

When using CIMPLICITY 8.1, if the screens were viewed in CimView on a CIMPLICITY 8.2 GlobalView/WebSpace server, the animations for Class Object graphics will now work properly.


GE Digital 94



Class Objects/ Point Properties Dialog

DE10594 SF-NA

When objects are dynamically created at Runtime, the object's events and actions that are configured for basic events, do not work as expected.

When objects are dynamically created at Runtime, the object's events and actions that are configured for basic events, now work as expected.

Class Objects/ Point Properties Dialog

DE10504; SF-00312279 DE10505; SF-00312277

Large expressions defined for data items of a class object, when viewed in the Point Properties dialog, are not visible properly.

Large expressions defined for data items of a class object, when viewed in the Point Properties dialog, are now properly visible.




Class/ Events and Actions

DE8845 SF-00296750

When the configuration for an event of a class is changed from normal data item to non-class points, the new configuration fails to get updated properly on applying the changes.

When the configuration for an event of a class is changed from normal data item to non-class points, the new configuration now gets updated properly on applying the changes.

Class Objects/ JIT Points

DE10326 SF-00312384

When upgrading projects containing classes and class objects, configured with Just In Time (JIT) Points, upgrade operation does not complete successfully. After upgrade, the JIT points are not accessible from client applications.

The upgrade operation for projects containing classes and class objects, configured with Just In Time (JIT) Points now gets completed successfully. After upgrade, the JIT points are now properly accessible from client applications.


GE Digital 95



Class Configuration/ Data Corruption

DE7904 SF-00276983

When a CIMPLICITY Class that is referenced by a large number of objects is modified, then the class may become corrupted.

When a CIMPLICITY Class that is referenced by a large number of objects is modified, it no longer corrupts.

Class Objects/ Objects Deletion Issues

DE11226 SF-00322711

When objects are deleted from the project, the project is not properly updated, leading to corruption of project data.

When objects are deleted from the project, the project now get properly updated and no corruption of project data occurs.

Class Configuration/ Data Item Configuration

DE11315; SF-00324323 DE10987; SF-00317100

When CIMPLICITY Class data item is configured with $DATAITEM_EXISTS expression, the data gets updated incorrectly at times, leading to corruption of project data.

When CIMPLICITY Class data item is configured with $DATAITEM_EXISTS expression, the data now gets updated correctly and project data corruption no longer occurs.




Class Objects/ Trigger Points

DE15048 SF-00364855

When trigger point configured in data item of a class is removed, the existing class objects are not properly updated.

When trigger point configured in data item of a class is removed, the existing class objects are now updated properly.

Class Objects/ PTDP Crashes

DE15504 SF-00353267

When class objects are created dynamically through scripts, PTDP crashes at times.

Class objects can now be created dynamically through scripts without any crashes in PTDP module.


GE Digital 96



Class Objects/ Just-in-time points

DE18439 SF-00396199

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.

Class Objects/ Alarm Routing

DE17929 SF-00393568

When a class object created with an Alarm Attribute enabled is ”r;edited”, to add and enable another alarm, the Alarm Routing properties for that Alarm Data Item does not get configured with the default Alarm Routing properties of the Object as expected.

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 properly with the default Alarm Routing properties of the Object as expected.




Class Objects/ Duplicate Object ID

DE18007; SF-00391810 DE18748; SF-00393480 DE18731; SF-00417785

When updating Class Objects information of a project that contains large number of Classes and Class Objects configured, errors are shown about duplication of objects. Also, the configuration information of some objects gets modified and object corruption occurs

When updating Class Objects information of a project that contains large number of Classes and the class objects now get configured properly. Also, the configuration information objects no longer get corrupted during update process.




Class/ Actions and scripts

DE16653 SF-00427206

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


GE Digital 97



Class Objects/ Object Properties

DE18643 SF-00411938

When the attributes of a class object are being modified, some of the configured object attributes are deleted randomly.

When the attributes of a class object are being modified, the configured object attributes no longer get altered or deleted.




Class Configuration/ Graphics File Reference

DE27136 SF-00449340

When a 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.

When a 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.

Class Object/ Object Creation via scripting

DE25784 SF-00438808

When class objects are being created via scripting support, CimServer.exe application crashes occur randomly.

When class objects are being created via scripting support, CimServer.exe application crashes no longer occur.

Class Object/ Object Creation

DE25136 SF-00427719

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


GE Digital 98



Class Object/ View Object points at Runtime

DE27948 SF-00450967

When object of a class containing JIT Point definitions mapping to OPC Server is copied, any modifications done to the copied object causes its JIT Points to be shown as invalid in Point Control Panel at runtime.

When object of a class containing JIT Point definitions mapping to OPC Server is copied, any modifications done to the copied object no longer causes its JIT Points to be shown as invalid in Point Control Panel at runtime.

Class/ Pre/Post Create Scripts

DE31047 SF-00453853

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.




Class Object/ Copying Class Objects or Dynamic Object Creation

DE35131; SF-00451588 DE35380; SF-00461481

When copying an object of a class between projects or creating an object dynamically in a project at runtime using scripting, no warnings are provided if the required class has not been defined in destination project. Also, the invalid object can no longer be deleted in destination project.

When copying an object of a class between projects or creating an object dynamically in a project at runtime using scripting, the object creation operation fails if the required class is not found in destination project.




Classes/ Properties and Methods

DE37315 SF-00449159

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.


GE Digital 99



Class Objects/ CimServer Application Crash

DE55828 SF-00479616

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.




Data Item/ Alarm generation

DE18213 Internal

When a Class data item is duplicated, the alarm is not generated for the duplicate Class data item.

When a Class data item is duplicated, the alarm is also generated for the duplicate Class data item.


GE Digital 100

3.4 ISSUES RESOLVED: DEVICE COMMUNICATIONS



OPC Server/Timestamps

DE6181 Case-1-1637642166 SF-00180631

(In a redundant setup) if an OPC Client performed many synchronous read operations against the CIMPLICITY OPC Server, timestamps could be bad or one node timestamp could be different from the other for the same point update.

(In a redundant setup) Timestamps are now correct when an OPC Client performs many synchronous read operations against the CIMPLICITY OPC Server.

Advanced Viewer/Point.Get()

DE6414 Case- 1-2456023517 SF-00080696

When using a script with the Advanced Viewer, repeated Point.Get()

commands for an OPC point value would eventually cause the Advanced Viewer to report errors.

Point.Get() can now be

successfully used repeatedly for an Advanced Viewer OPC point.

STAT_PLC/Setpoint to Coils

DE5804 Case-1-2844137922 SF- 00177456

Setpoint operations to coils would fail when writing to devices configured with STAT_PLC that required only single coil

writes.

The device communication interface has been enhanced to allow configuration of single coil writes with the STAT_PLC

model.




Alarm Events

DE5802 SF-00180057

Alarm Events names did not display correctly in Enterprise Client applications.

Alarm Events names now display correctly in Enterprise Client applications.


GE Digital 101



Series 90 to S90 Triplex Conversion/MASTER or SLAVE Omission

DE7090 SF-00242442

In scripts used by the Process Manager, the designation of MASTER or SLAVE was omitted when a project was converted from Series90 Ethernet to S90 Triplex.

Now, either MASTER or SLAVE is inserted correctly at the top of the MASTER.MCP or SLAVE.MCP file for

any new conversion from S90 Ethernet to S90 Triplex.

If you converted the S90 Ethernet device previously do the following.

Directory Action

...\<project>\MASTER 1. Open the MASTER.MCP file

(e.g.. using Notepad). 2. Confirm that the MASTER entry is on the top line in the file. 3. If MASTER is missing: 1. Add a new line at the top of the file. 2. Enter MASTER. 3. Save the file..

...\<project>\SLAVE 1. Open the SLAVE.MCP file (e.g..

using Notepad). 2. Confirm that SLAVE is on the top line in the file. 3. If SLAVE is missing:

a. Add a new line at the top of the file.

b. Enter SLAVE.

c. Save the file.

Note: Call support if you continue to have issues.

Duplicate PDS Devices/ master_pos_0.ini

DE7546 SF-00257120

If a Proficy Driver Server (PDS) device was duplicated in a CIMPLICITY project, the appropriate entries for the new device were not inserted in the master_pos_0.ini

Appropriate entries for PDS devices that are duplicated in a CIMPLICITY project are now inserted in the ..\<project>\data folder.

GE Digital 102


file in the ...\<project>\data

folder.


GE Digital 103



OPC Server/Data Reads

DE8241 SF-00281793

The read method would intermittently return an incorrect NULL value.

The read method no longer incorrectly returns a NULL value.




OPC UA/OpenSSL Support

US9577 SF-NA

Security Vulnerabilities have been identified in v1.0.1j version of OpenSSL

OpenSSL has now been upgraded to v1.0.1m version and the security vulnerabilities have been addressed. For more information on the Security Vulnerabilities addressed with the version upgrade, please refer to: https://www.openssl.org/news/openssl-1.0.1-notes.html




S90 Triplex/ Process Crash

DE11590 SF-00305834

During initialization, if I/O errors occurred during the transactions where the device communication interface queried the PLC for device information, the device communication interface could terminate unexpectedly.

The device communication interface no longer terminates and records the correct values for PLC memory sizes when reading the information from the device.


https://www.openssl.org/news/openssl-1.0.1-notes.html

https://www.openssl.org/news/openssl-1.0.1-notes.html

GE Digital 104



Proficy Driver Server/ Device Points

DE11817 SF-00328999

When PDS Device Point is created in a CIMPLICITY Project, "Poll After Set" option is set by default.

"Poll After Set" option is not longer set by default for newly created PDS Device Points in a CIMPLICITY Project.

S90 Triples/ Stale Data Issue

DE16398 SF-00319024

When the network is restored after a brief disconnect, incorrect data is retrieved from PLC devices.

When the network is restored after a brief disconnect, data is now retrieved properly from PLC devices.

Modbus/ Crash Issue

DE16853 SF-00344471

The Modbus TCP/IP device communication interface could terminate as a result of receiving malformed packets for unsolicited data.

Malformed unsolicited data will no longer cause the Modbus TCP/IP device communication interface to fail.

OPC Server/ Partner Dead Messages

DE16391 SF-00247450

When CIMPLICITY HMI OPC Server is shutdown gracefully, "Partner Dead" error messages get logged into the status log

When CIMPLICITY HMI OPC Server is shutdown gracefully, "Partner Dead" error messages are no longer logged into the status log.




Marquee Driver/ Import/Export Support

DE17605 SF-00393849

When the Marquee Message Import tool is used for importing data into CIMPLICITY Project, the data is not imported properly.

The Marquee Message Import tool can now be used for importing data into CIMPLICITY Project successfully.




OPC Client/ Incorrect timestamps

DE18391 SF-00404320

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.


GE Digital 105



S90 Triplex/ OEM Protection

DE17912; SF-00397334 DE18581; SF-00403151

When OEM Protection option is enabled for a project, communication issues between the project and configured PLCs are observed.

When OEM Protection option is enabled for a project, communication between the project and configured PLCs now occur properly.




Modbus/ Server Redundancy

DE18808 SF-00411258

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.




OPC UA Client/ Communication Issues

DE14879 SF-00350191

When a project is configured to use OPC UA Client with Unsigned Byte Array points from IGS, the point values are not properly read into CIMPLICITY via the OPC UA Client.

When a project is configured to use OPC UA Client with Unsigned Byte Array points from IGS, the point values are now properly read into CIMPLICITY via the OPC UA Client.




OPC Client/ Point Updates

DE20065 SF-00414428

When a project is configured with OPC points, some of the configured points get incorrect value updates if ALL_UNSO option has been enabled.

When a project is configured with OPC points, the configured points no longer get incorrect value updates if ALL_UNSO option has been enabled.


GE Digital 106



OPC Client/ OPC Groups

DE23845; SF-00438584 DE23846; SF-00424397 DE25133; SF-00443458

When configuring OPC Groups for an OPC client, new OPC groups do not get created.

When configuring OPC Groups for an OPC client, new OPC groups now get created properly.




Modbus/ Device Connectivity

DE61741 SF-00472209

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 not recognized by CIMPLICITY Project. A project restart is required to have the devices identified at runtime.

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 recognized by CIMPLICITY Project. A project restart is no longer required to have the devices identified at runtime.


GE Digital 107

3.5 ISSUES RESOLVED: LOGGING.



Enumerated Point/Logging Raw Value

DE6085 Case-1-3766566845 SF-00178095

If, for an enumerated point, Raw value was selected to be logged on the DATA_LOG/GROUP_LOG Table Properties dialog box>Logging Attributes tab, the enumerated value would be logged, not the raw value.

When Raw value is selected to be logged as an enumerated point's logging attribute, the raw value is now logged.

CIMPLICITY/Historian String Connection

DE6076 Case-1-2474809791 SF-00177317

The Historian connection was lost after CIMPLICITY with the Historian connection ran for many weeks (e.g. three to four weeks). Note: The connection string on the CIMPLICITY® Options dialog box>Historian Connections tab would disappear.

CIMPLICITY can run as long as necessary with a Historian string connection remaining connected.

Historian OPC Interface/Device Data Timestamps

DE6103 Case-1-3899587431 SF-00178784

When device data was logged to Historian via the Historian OPC Interface the first point update contained an invalid timestamp.

When device data is logged to Historian via the Historian OPC Interface all point updates now contain valid timestamps.

Historian/Username Length

DE6104 Case-1-4012885678 SF-00178075

A username that was entered in the Add/Edit Historian Connection dialog box could not be longer than 14 characters. If an attempt was made to enter a longer name a message would open reporting that Text must not exceed 14 characters.

The Historian connection username length can now be 85 characters, as follows. Domain length (64) + Slash

(1)+ Username length(20)

GE Digital 108


PTDL/DL Process Crash

DE6816 Case-1-2752984845 SF-00067187

The Table Properties dialog box>Advanced tab has a Write Queue size field that enables users to enter a queue size that applies to that table. However, the queue size did not have a maximum limit. The following issues could occur.

• It was possible to configure many Database logging tables with many fields and a queue size for each table that could cause the Database Logger to go beyond the maximum 2 GB process memory space. This would cause the Point Logging (PTDL_RP) process and Data

Logging (DL_RP) to crash.

• There was no error message to report what happened.

Note: The Logging Properties dialog box>Parameters tab includes a Default table write queue size field that applies to any table that is not assigned its own queue size. The maximum size is 32,727 Bytes.

• An individual table queue size has a maximum size of 32,727 Bytes.

• If a memory exception still occurs, the Database Logger does the following for: Tables

o Stops initializing additional tables; instead it drops them.

o Logs an error message for each dropped table to the Status log.

Individual records. o Drops an individual

record if the error exception happens when the record is being initialized.

o Logs an error message for each individual dropped record to the Status log.

Historian/EU conversion

DE6833 Case-1-1697426321 SF-00072370

When a project started an engineering units (EU) Conversion was not performed in a synchronous read from the Historian Collector. As a result, CIMPLICITY logged the $RAW_VALUE of a scaled point to

Historian and would eventually begin to log $VALUE.

This caused trends to have spikes and invalid values logged to Historian.

EU Conversion is now performed in a synchronous read from Historian Collector when EU is configured for points. This eliminates trend spikes and invalid logged values that occurred then the EU conversion was not performed.

GE Digital 109


Database Logger/Enterprise Point

DE6836 Case-1-2895722511 SF-00186373

An Enterprise point located in one project could be added to a Database Logger table (e.g. GROUP_LOG table) that was attached to a different project. This caused an error when: 1. The point that was incorrectly in the table was selected. 2. An attempt was made to edit the point properties. Note: The Enterprise point should not have been allowed to be added to another project's log table.

Database Logger does not support Enterprise points in Enterprise projects. Now an error message will open when a user attempts to add an Enterprise point to a log table (e.g. clicking the AddItem button in the GROUP_LOG table). The error message reports the following. Point information unavailable. Point cannot be logged or modified.

Historian OPC A&E Collector Shutdown

DE6423 Case-1-2645992477 SF-65514

The Historian OPC A&E Collector would crash when a CIMPLICITY project that had the Historian OPC A&E Interface configured was stopped.

The Historian OPC A&E Collector now shuts down correctly when a CIMPLICITY project is stopped.

Historian Servers/Different Data

DE6073 Case-1-3963250259 SF-00180203

Historian servers that should have received identical data that was initialized at the CIMPLICITY OPC Server and sent to the Historian servers, instead could receive different data. The difference was caused by some itemID columns remaining

blank.

itemID columns are now be filled

properly with appropriate point names for all the involved Historian servers. The data they receive is identical.


GE Digital 110



On digital point state (HIGH)/First Occurrence

DE6970 SF-00236679

The first time an On digital

point state (HIGH) event was

triggered for a point that was in a DATA_LOG or Group Log table, no data was logged. Each time the point's event was triggered after the first time, the data was logged as expected.

Data is now logged every time an On

digital point state (HIGH) event is

triggered for a point that is in a DATA_LOG or Group Log table.

Database Logger/Incorrect Error Messages

DE7410 SF-00241009

When a project that used the Database Logger to log data to SQL Server was started, an error message would be logged to the project Status log for each item on the table that was to be logged. The error message was: End of data returned from query

The error message, End of data returned from query, is no longer logged to the project Status log when a project that uses the Database Logger is started.




Database Logger/Group Table

DE7692 SF-00272152

When a Logged Expression line is added to a trend object and expressions are modified, Setup Dialog box does not accept the database logger table as a group table.

Expressions can now be given for line type logged expressions and Setup Dialog Box will accept database logger table as group table.

Database Logger/Startup Crash

DE7640 SF-00177601

While starting CIMPLICITY project, Data Logger module crashes occasionally.

Changes were made to correct the string data manipulation and Data Logger module no longer crashes while starting CIMPLICITY project.


GE Digital 111



Database Logger/Maintenance Action

DE8070 SF-00281456

If a Database Logger Maintenance Action is set to delete records by time, and a count of 24855 days is set, then the entire database content will be erased.

Database Maintenance Actions now functions without any improper deletions.




Database Logger/ Alarm Logging

DE10662 SF-00315405

When a project, with logging attributes for alarm log table enabled, is upgraded and run, it does not log alarm messages properly.

When a project, with logging attributes for alarm log table enabled, is upgraded and run, it now logs alarm messages properly.




Database Logger/ Data Log Settings

DE12530 SF-00334250

When data log settings are modified for a class. The changes get applied to new objects, but do not get reflected for existing objects.

When data log settings are modified for a class. The changes get applied properly to both existing and new objects.




Historian/ Bad Data on startup


When Points are logged to Historian, if the values of the points do not change, then bad quality data is logged to Historian.

When Points are logged to Historian, even if the values do not change, bad quality data is not logged to Historian.


GE Digital 112



Historian/ Data Logging

DE16066; SF-00180065 DE16068; SF-00304393

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




Data Logging/ Sequence Objects

DE18287 SF-N/A

When logging data to Oracle Database, data does not get logged into database and "sequence does not exist" errors get logged into Project Log.

When logging data to Oracle Databases, data now gets logged into the database properly and no errors are logged into Project Log. Additional Information: Any existing tables will have to be dropped so that new tables get created on project Start up.

Historian Tags/ Bad Values

DE16075 SF-00374752

When Points are logged to Historian, if the values of the points do not change, then bad quality data is logged to Historian.

When Points are logged to Historian, even if the values do not change, valid data is logged to Historian.

PTDL/DL Process Crash

DE17356 SF-00361690

PTDL_RP Process crashes are observed intermittently when using the data logging functionality.

PTDL_RP Process crashes are no longer seen when using the data logging functionality.

Data Logging/ PPS Alarms Information

DE13852; SF-00338159 DE17469; SF-00229625

When information about acknowledged PPS Alarms is logged into database, the timestamp information is not logged properly.

When information about acknowledged PPS Alarms is logged into database, the timestamp information is now logged properly.


GE Digital 113



Data Logger/ Process Crash

DE18476 SF-00391829

When using Data Logging Functionality on a project configured with redundancy support, DL_RP Process crashes are observed.

When using Data Logging Functionality on a project configured with redundancy support, DL_RP Process crashes are no longer seen.


GE Digital 114

3.6 ISSUES RESOLVED: NETWORKING



GlobalView/WebView/Open Screen in New Tab

DE6074 Case-1-3279791754 SF-00181046

When working with both GlobalView and WebView on different nodes and using WebView to repeatedly open the same GlobalView screen in a new tab, an error message would report The session's resolution is invalid.

This issue is resolved in Proficy WebSpace v4.7. Proficy WebSpace v4.7 supersedes GlobalView; if you have a GlobalView license you can replace GlobalView with Proficy WebSpace v4.7.

Digital Certificate Update

DE6822 Case-1-3524865981 SF-00179022

Because a digital certificate validity had expired, when a user attempted to access a WebView page an Application blocked by security settings error message would open, requiring the user to accept the risk.

The new digital certificate for signing the WebView module has been added. This eliminates validity error messages when attempting to access a WebView page.

WebView/Invalid Messages

DE6437 Case-1-2588569517 SF-00074531

The CIMPLICITY Web server would crash when any field in a message (e.g. password, user name, options, etc.) being passed in was larger than allowed lengths.

CIMPLICITY now checks the parameters of any message sent to the WebView port. If the parameters are larger than allowed lengths, the message fails. Notes

o In many cases the failure will be reported in the Status log.

o This resolution corrected vulnerability issue, GEIP13-03, which is described in the KB15602 document on the GE Intelligent Platforms Industrial Software and Automation Support Web site.

WebSpace DE6759 Case-1-1481397483 SF-00083153

When connecting to a WebSpace server, CimView would crash on startup if the user who was authenticated on the server had a user defined system PATH

CimView starts up successfully if the user who is authenticated on the server has a user defined system PATH environment

http://support.ge-ip.com/support/index?page=kbchannel&id=S:KB15602&actp=search

GE Digital 115


environment variable and it did not have all of the Windows paths.

variable, even it does not have all of the Windows paths.




Viewer on Remote Server/Router Failure

DE6805; SF-00177521 DE6804; SF- 00177353 DE6806; SF-00177599 DE7625; SF- 00177519 DE7617; SF-00233930

When a user worked with a CIMPLICITY Viewer by logging into a remote server connection, the router would fail periodically.

Users can now successfully work with a CIMPLICITY Viewer by logging onto a remote server. The router continues to run in this configuration.




Document Delivery Processes

DE7638 SF-00206189

The Document Delivery process is periodically terminated unexpectedly when multiple devices were configured with the same destination address.

The Document Delivery process no longer terminates unexpectedly when multiple devices were configured with the same destination address.




WebView/Out of Memory Error

DE8076 SF-00229218

When CimView screens are opened from remote client via WebView, a Java Runtime error may appear on the client session.

When WebView sessions are opened on a client node, they will no longer generate a Java Runtime error.


GE Digital 116



WebView Service/RTIP Node

DE6070 SF-00208544

The WebView Service crashed periodically on the RTIP node primarily because of the way the path was being handled.

The path handling has been substantially stabilized




WebSpace/ Template Issue

DE11119 SF-NA

When creating pages from Proficy Webspace, "proficy webspaceTemplate not found" error is shown and web page creation fails.

Creating pages from Proficy Webspace, now succeeds without any failures or error messages.

WebView/ Scaling

DE11073 SF-NA

When the "Full Screen" display icon is clicked in Proficy Vision the CimView Screen does not scale according to the new screen client area.

When the "Full Screen" display icon is clicked in Proficy Vision the CimView Screen now scales according to the new screen client area.




Document Delivery/ UNC Path Issue

DE16462 SF-00362123

When Mapped Network Drive path is used, the Document Delivery feature does not work properly.

The Document Delivery feature now supports UNC Paths in place of the Mapped Network Drive path.


GE Digital 117



Server Redundancy/ Broadcasting

DE17257 SF-00386523

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.

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.


GE Digital 118

3.7 ISSUES RESOLVED: POINTS AND SCRIPTING



Point Cross Reference/Nonexistent Points

DE6093 Case-1-3726497631 SF-00178948

When points were deleted (e.g. from CimEdit/CimView screens or from the project), Point Cross Reference continued to report the points and associate them with the applications they had been deleted from, even after the Point Cross References databases were updated.

Point Cross Reference reports only existing points.

Derived Point/Timestamp


When a derived point that has an equation based off of a device point was used, the derived point used the local server timestamp to identify when the calculation was last done. However, the timestamp for the derived calculated point should be the timestamp of the device point in the equation.

The timestamp for the derived calculated point is now the timestamp of the device point in the equation.

Error Message/ Setpoint Limits

DE6926 Case-1-1511385444 SF-00177366

An invalid error message would display under the following conditions. 1. A device point used a linear conversion and setpoint limits. 2. A user attempted to set a point value outside of the specified limits. Result: The error message reported an invalid limit range specified for the point.

When a user attempts to set a value (for a device point using linear conversion), which is outside of specified setpoint limits, an error message reports the correct limits in which a valid value can be set.

Point Import Failure DE6108 Case-1-3916888851 SF-00180680

Attempting to import a point into a project (using a .csv file) would fail and an error

would be generated in the following conditions. 1. The same point already existed in the project. 2. The import point had an On-

Update alarm type

3. The project point had an Absolute

alarm type.

The point now imports successfully; the updated point has an On-Update alarm

type.

GE Digital 119


String Space DE6408 Case-1-1364073518 SF-00057998

An Out of String Space could occur, when a string

variable or string variant was assigned to a fixed variant (Long or any other type).

A string variable or string variant can now be assigned to a fixed variant without running out of string space.

CIMPLICITY Script Editor/Multiple Scripts Open

DE6817 Case-1-3165017736 SF- 00177536

When self-built and third party custom .NET assembly

lists were added to the in-Event Editor Setup dialog box>.Net Assembly References list, concurrent reads and writes of a saved (from the list) reference assemblies file caused the CIMPLICITY Script Editor to crash.

The CIMPLICITY Script Editor remains open and performs correctly when self-built and third party custom .NET assembly

lists are added to the in-Event Editor Setup dialog box>.Net Assembly References list

VB .NET Scripts/EMRP Crashes

DE6823 Case-1-3616121723 SF-00179537

A Visual Basic (VB) .NET script would crash after running

for a brief time in the CIMPLICITY Script Editor; this caused the Event Manager Resident Process (EMRP) to crash.

VB .NET scripts now

continue to run successfully in the CIMPLICITY Script Editor.

Multiple VB Scripts/Logged Errors

DE6821 Case-1-3164070747 SF-00178007

When multiple Visual Basic (VB) scripts were launched many errors were logged in the core Status Log. Example

Multiple VB scripts can now be successfully launched with no errors logged to the core Status Log.

Process MAC-EMRP

Procedure script

Status failure

Source COR_BASIC_ERR

Error message

System.ArgumentNullException:

Value cannot be null.

Parameter name

assemblyFi

Dynamic Configuration/Point Type

DE6824 Case-1-3713619774 SF-00178997

Changing a point type using dynamic configuration could cause errors (e.g. indicating that there was a size mismatch).

Dynamic configuration can be successfully used to change the data type

GE Digital 120


of any type of points (e.g. derived/global).

Scripts/BlinkFill DE6825; Case-1-3382418752; SF-00177499 DE7000; Case-1-3909839549; SF- 00178790

When the sample script subroutine ExprListAnimElement_AnimatesBlink

Fill() was used in the BlinkFill sample

script, it failed.

• New CimEdit/CimView object types, DGefBlinkLineFor

mat and DGefBlinkFillFor

mat, are added for

supporting blink animation.

• New sample scripts now include the blink animation object types.

Note: The new sample scripts are available in this IPI's General Information: Points and Scripting topic.

Delta Accum/Derived Point Process

DE6992 Case-NA SF-00236237

A virtual $DERIVED point using Delta Accum

calculation would crash the Derived Point Process (PTMDP) if the expression was configured with a non-existent point ID.

PTMDP will not crash even if

the expression is configured with a non-existent point ID.

GefProcedure.Duplicate/ Expressions

DE7216 Case-1-2914907711 SF-00178066

The CimEdit/CimView object model GefProcedure.Duplicate method would

crash if the procedure contained expressions.

GefProcedure.Duplicate

no longer crashes of it contains expressions.

CimView/Language Set by a Script

DE7193 Case-NA SF-00230890

CimView would crash when the language for the screen was supposed to be set by a script.

CimView now runs correctly when the language for the screen is set by a script.

CLIE/Long Virtual Point Name in Expression

DE7194 Case-NA SF-00247908

When using CLIE Import to import a file that contained a virtual point with an expression that contained a long point name: 1. CLIE would generate an error 2. When opening the imported point's Point Properties dialog box in the Workbench, the Workbench would crash.

Points with this type of configuration can now be imported without errors; the Workbench can open the point's Properties dialog box and display the expected properties for the point's configuration


GE Digital 121



CimProjectList DE7117 SF-00243715

A C# script that attempted to

instantiate the CimProjectList object would

crash instantly.

C# scripts can now successfully instantiate the CimProjectList

object.

CLIE/%VAL Alarm Messages

DE7287 SF-00216088

When importing new points using CLIE, the description in the Point Alarm type record remained uninitialized. As a result, the following occurred: 1. The record was not treated as point alarm. 2. %VAL was not parsed and

populated. 3. Each time the *.csv file

was opened and closed with %VAL

message, an additional type record was incorrectly added.

Now when CLIE is used to import points with a %VAL alarm message, the points

are imported properly with no errors.

CLIE/Points with Additional Roles

US4539 SF-NA

When Import/Export Configuration (CLIE) imported points that were assigned to additional roles outside of the default set of roles configured in CIMPLICITY, processing the resulting large .rol files caused

the import to take an unacceptable amount of time.

Processing .rol files has been

optimized so when a CLIE imports points, even points that are assigned additional roles, the process is much faster.

Manual Mode/Could not Turn Off

DE7323 SF-00247178

If Manual Mode was enabled on a device point and the project was stopped/restarted, Manual Mode could not be turned off.

If Manual Mode is set on a device point, it can now be turned off after a project has stopped/restarted.

$ALARM.ACTIVE/Number Reported

DE6835 SF-00180333

Enterprise server points $ALARM.ACTIVE could report an

extremely large number, at times, billions of available outstanding alarms.

$ALARM.ACTIVE performance counter

now

• Displays the minimum value as 0.

• Increments on every active alarm in the System


GE Digital 122



BOOLEAN Point/QUALITY.ALARMED Attribute

DE7472 SF-00259121

If a virtual BOOLEAN point included an equation that was configured with a QUALITY.ALARMED

attribute, an error message would incorrectly report that the "...point ID does not exist..."

Virtual BOOLEAN points that are configured with a QUALITY.ALARMED attribute in an

equation now perform correctly.

CimDataItem Object/Caused Errors

DE7487 SF-00261329

Object model code did not run properly when it used the CimDataItem object.

Object model code that includes the CimDataItem object now runs

successfully.

Virtual Equation Points/Timestamps

DE7533 SF-00263256

If a virtual point was set up as an equation-based point it would not always display the correct timestamp in Point Control Panel. It would display Dec31, 1969.

Virtual points that are set up as equation-based points will now display the correct timestamp in Point Control Panel

CimPoint.LogDataHistorian Example

DE7366 SF- 00254295

The CimPoint.LogDataHistorian

method example in the documentation did not work properly in C# scripting.

The CimPoint.LogDataHistorian

method example is correct; the method now performs correctly when that example is used.

Script/.exe Format/Message Box

DE7534 SF- 00264004

The Script engine did not represent any string literals used in a script correctly during runtime. This could manifest itself in many different types of symptoms with a script not working correctly when compiled into an .exe.

Example When a simple script calling a Message Box was compiled into an .exe format, the message in the

Message box would be truncated.

String literals in a script, which is compiled into an .exe file are now

are used correctly during runtime. Important: Recreate the script .exe

after the SIM is installed.

GE Digital 123


Delta Accumulator Point Resets

DE7607 SF-00222077

At times the Delta Accumulator points did not reset properly after the reset point attempted to trigger a reset. Note: The Delta Accumulator point value could be reported as being too high and the reset failed

Delta Accumulator points now reset successfully after the reset point triggers the reset.

On Digital Point State High Points/SQL Server

DE7538 SF- 00262451

Database Logging failed to log On Digital Point State

High points to SQL Server.

Database Logging successfully logs On Digital Point State High

points to SQL Server.

Delta Accumulator Point Updates

DE7610 SF-00221750

Delta Accumulator points' expression values did not update when an update occurred.

Delta Accumulator points' expression values now reflect all updates.

Enum Alarm State Value/PTMRP

DE7423 SF-NA

If an Enum value (initialized value) was in an alarm state at the project's startup, the Point Manager Resident Process (PTMRP) would crash (halt).

PTMRP continues to run if an Enum value (initialized value) is in an alarm state at the project's startup.

Scripts as .exe Programs DE7706; SF-00269514 DE7735; SF-00272768

In many instances, scripts that ran as compiled .exe programs

did not work properly. Note: Issues included (but were not limited to) string literal and PointGet/PointSet

functions.

Scripts that ran as compiled .exe

programs did not work properly in the many instances.




Alarm point limits

DE8180 SF-00284454

Modifying the Point Alarm Limits causes the Point Management process (PTMRP) to halt.

Updating Alarm Point Limits succeeds without any impact on Point Management.


GE Digital 124



C# Scripting/ Point.SetArray/Point.SetArray and Point.Set Methods

DE8253; SF-00287479 DE8459; SF-00291380

When invoking the Point.SetValue or Point.SetArray methods using the C# APIs, this would automatically call the Point.Set method. This behavior was a deviation from the Basic Script methods which required an explicit call to Point.Set after invoking the Point.SetValue or Point.SetArray methods.

Now when invoking Point.SetValue or Point.SetArray methods through C#, the Point.Set method no longer gets triggered automatically. The Point.Set method must be invoked separately.

Calculated Points/Bad Initial Timestamps

DE8513 SF-00275348

A calculated point that was configured with an equation and an initial value of "0" would show an invalid timestamp on startup.

Now when using a calculated point that is configured with an equation and an initial value, it will generate a valid timestamp on startup.

Periodic Maintenance DE8265 SF-00277805

When using the Configuration Object Model to manipulate a Database Logger table, there was no method available to turn on or off the Timed/Gated maintenance ’Periodic’ option.

New Methods have now been added to CimTable object of the Configuration Object Model to enable/disable the following options: ▪ PeriodicMaintenance ▪ SyncMaintenance ▪ DigitalMaintenance ▪ LowSpaceTrigger ▪ LogCountMaintenance Note: The new sample scripts are available in this IPI's Enhancements to Maintenance Scripting Functions topic.


GE Digital 125



Virtual Points/TimeStamps

DE9633 SF-00302471

When a source point, used in the IsAvailable() method in an equation that is configured on a virtual point, is unavailable, then the virtual point will have an invalid timestamp.

When a source point, used in the IsAvailable() method in an equation that is configured on a virtual point, is unavailable, then the virtual point will now contain valid timestamp.

Event Editor/EMRP Crash

DE9224 SF-00300204

If a series of Events/Actions are configured in the Event Editor and you change the View to "View by Action", then enabling/disabling events when an action is chosen in the "View by action" view causes EMRP to crash.

Enabling/Disabling events when an action is chosen in the "View by action" view no longer results in EMRP Crashes.

Expression Editor/GetToken Function

DE9693 SF-00299342

When GetToken

(<Source_String>,

<Token_Separators>,

<TokenIndex0Based>)

function is configured such that <TokenIndex0Based> is greater than <Source_String> number of tokens, CimView object displays default text string instead of an empty string.

If <TokenIndex0Based> is greater than <Source_String> number of tokens, the CimView object now displays an empty string as expected.

Expression Editor/Mid Function

DE9692 SF-00299254

When Mid (<Source_String>,

<StartPosition>,

<Character Count>)

function is configured such that <StartPosition> is greater than <Source_String> length, CimView object displays default text string instead of an empty string.

If <StartPosition> is greater than <Source_String> length, the CimView object now displays an empty string as expected.

Calculated Points/Dynamic Configuration

DE8142 SF-00286080

When class object is added in Dynamic Mode, the virtual calculated point expression did not update in dynamic configuration mode.

The virtual calculated point expression updates successfully in dynamic configuration mode when class object is added in Dynamic Mode.

DE9690 SF-00307534

GE Digital 126

Event Editor/Corrupted ID

When a project is upgraded to CIMPLICITY 9.0, the ID Field shows corrupted value in Event Editor.

Upgrading a project to CIMPLICITY 9.0 no longer shows corrupted ID in Event Editor.

CimEdit/ /NoExit Command

DE9145 SF-00281989

CimView launched with /NoExit command line argument does not get closed when CloseEx function is invoked through script.

CimView launched with /NoExit command line argument now gets closed successfully when CloseEx function is invoked through script.




Virtual Points/ Dynamic Import

DE8808 SF-00295924

When virtual points are imported dynamically, virtual points that are configured with an equation but no initialization do not get any values until the project is restarted.

When virtual points are imported dynamically they will now update properly without the need for a project restart.

Error Message/ CimProjectData.GetNext

DE9843; SF-00309735 DE10453; SF-00315121

When the CimProjectData.GetNext method is used in a VB script, an error is reported during script compilation.

Using the CimProjectData.GetNext method in a VB script no longer reports errors during script compilation. At runtime a TRUE/FALSE value is returned as expected.




Quality Operations/ IsConfigured()

DE10480 SF-00315716

When IsConfigured() function is used in an expression, CimView application would crash in the following circumstances: 1. Non-existing point is accessed in IsConfigured() function. 2. Point ID accessed in IsConfigured() function is enclosed with Double Quotes.

Now, when IsConfigured() function is used in an expression, CimView application does not crash.


GE Digital 127



Points Control Panel/ Value Accumulation

DE11100; SF-00321694 DE11049; SF-00315044

When value accumulator point updates are being monitored from Point Control Panel, the updates do not happen properly and value accumulation continues from last value before update.

When value accumulator point updates are being monitored from Point Control Panel, the updates now happen properly and value accumulation continues from last update.

Points Cross Reference/ Incomplete Points List

DE11304 SF-00324001

When displaying the points used in a project, the Point Cross Reference tool does not properly list points created by scripts.

When displaying the points used in a project, the Point Cross Reference tool now properly lists the points created by scripts.

User Defined Point Attributes/ Invalid Timestamps

DE11101 SF-00321377

When user define point values are updated, the timestamp value for USER_FLAGS attribute does not get updated appropriately.

When user define point values are updated, the timestamp value for USER_FLAGS attribute now gets updated appropriately.

EMRP Crash DE11400 SF-00314963

When using scripting functionality, memory leak and subsequent crash of EMRP Process occurs.

When using scripting functionality, memory leak and subsequent crash of EMRP Process no longer occurs.

Configuration Object model/ CimEvent.EventExecution property

DE11747 SF-00306305

When the Configuration Object Model is used to query CimEvent.EventExecution property value of a configured Event in a CIMPLICIY project, the queried value is not returned properly.

When the Configuration Object Model is used to query CimEvent.EventExecution property value of a configured Event in a CIMPLICIY project, the queried value is now returned properly.


GE Digital 128



Point Control Panel/ Project Points

DE8457 SF-00289040

When viewing project points from Browse Dialog in Point Control Panel application, project points do not get listed properly.

When viewing project points from Browse Dialog in Point Control Panel application, project points now get listed properly.

Calculated Points/ Value Reset issue

DE8844 SF-00296811

When resetting an equation point having initialized value and a reset, the configured "initialized value" does not get set properly.

When resetting an equation point having initialized value and a reset, the configured "initialized value" does not get set properly.

EMRP Crash DE10592 SF-00215264

When NAN values being processed on Virtual Points, EMRP and Basic Script Engine crashes are observed.

NAN values are now processed properly on Virtual Points and any errors that occur during this process now get handled properly.

Class Events/ Event Triggering

DE11743 SF-00328142

When an event of type "Alarm Generated" is configured for a class, the event gets triggered for any project ID.

When an event of type "Alarm Generated" is configured for a class, the event now gets triggered only for the specified AlarmID.

EMRP Process/ Scripting Crash issues

DE13269; SF-00337194 DE11706; SF-00327815

When running multiple C# scripts for reading/writing points in a CIMPLICITY Project, Substantial memory growth occurs, eventually leading to random application crashes.

When running multiple C# scripts for reading/writing points in a CIMPLICITY Project, substantial memory growth and subsequent application crashes no longer occur.

Points Control Panel/ Application Crash

DE11818 SF-00329040

Application Crash occurs when long point name is specified in the Point Browse Dialog.

Application no longer crashes when long point name is specified in the Point Browse Dialog.


GE Digital 129



Import Export/ Importing Roles

DE12076 SF-00331123

When points with long names are imported using CLIE tool into a project, the information about roles configured for points do not get imported properly.

When importing points with long names using CLIE tool into a project, the information about roles configured for points now get imported properly.

EMRP/ Crash, Hang and Memory Leak Issues


When using Event Manager functionality, multiple issues related to memory leaks, process hangs and crashes were observed.

Issues related to memory leaks, hangs and crashes no longer occur when using Event Manager functionality.




Virtual Points/ Scripted Points

DE9621 SF-00302795

When a virtual point that uses an equation was created via script, it would not work properly.

Virtual points with an equation created via script, now work as expected.

Script Editor/ Saving Scripts

DE8015 SF-00281121

When saving modified scripts using CIMPLICITY 9.0 .NET script editor, changes in other saved scripts get overwritten.

When saving modified scripts using CIMPLICITY 9.0 .NET script editor, changes in other saved scripts no longer get modified.


GE Digital 130



EMRP/ Loading DLLs and Crashes

DE11144 SF-00322225

When a starting project having custom DLLs configured, Event Manager crashes are observed and DLLs do not get loaded properly.

When a starting project having custom DLLs configured, Event Manager crashes are no longer seen and configured DLLs get loaded properly.

Virtual Points/ Workbench Crash

DE15176 SF-00353241

Workbench crash occurs when attributes of a virtual point are modified and committed.

Workbench no longer crashes when attributes of a virtual point are modified and committed.

Point Properties/ Regional Settings

DE15255 SF-00368185

When decimal separator setting for a project is changed, the device-point custom conversions do not work properly.

When decimal separator setting for a project is changed, the device-point custom conversions now work properly.

Virtual Points/ Point Expressions

DE15179 SF-00367410

Expressions that use Instr( ) or InstrCS( ) functions with empty ("") source string do not get evaluated properly.

Expressions that use Instr( ) or InstrCS( ) functions with empty ("") source string now get evaluated properly.

Virtual Points/ Point Expressions

DE13810 SF-00345127

When viewing the points in Point Control Panel, invalid timestamps are shown for virtual points having AL() expressions configured.

When viewing the points in Point Control Panel, timestamps are shown properly for virtual points having AL() expressions configured.


GE Digital 131



EMRP/ Performance Issue

DE16564 SF-00180679

When a virtual point is duplicated in dynamic mode, the duplicated points do not get updated properly.

Duplicate points created in dynamic mode, now updated properly.

EMRP/ Performance Issue

DE13856 SF-00348702

When scripts containing events are used in CIMPLICITY Project, memory growth and performance degradation are observed.

When scripts containing events are used in CIMPLICITY Project, memory growth and performance degradation are no longer seen.

EMRP/ Alarm Events

DE8887 SF-00291181

While editing events using the Event Editor, wildcard characters are not working properly.

While editing events using the Event Editor, wildcard characters now work properly.

Script Editor/ Intellisense Support

DE7856 SF-00277481

When editing .NET scripts, the intellisense functionality does not work as expected.

When editing .NET scripts, the intellisense functionality now works as expected.

EMRP/ Crash Issue

DE14511 SF-00357642

When using Event Manager functionality, process crashes were observed.

Application crashes no longer occur when using Event Manager functionality.




.NET Scripting/ Intellisense Support

DE16873 SF-00383867

When large .NET Scripts are being edited, the built-in intellisense support responds very slowly and causes unnecessary delays.

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.

EMRP/ Exception Handling

DE17272 SF-00335476

When the Try/Catch Exception blocks are used in scripting, information about the point causing the exception is not available.

When the Try/Catch Exception blocks are used in scripting, information about the point causing the exception is now made available.

GE Digital 132


EMRP/ Script Execution

DE17577 SF-00388082

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.

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.

EMRP/ Application Crash

DE17262 SF-00178716

When multiple scripts are accessing the same script or point simultaneously, the Event Manager process can crash randomly.

When multiple scripts are accessing the same script or point simultaneously, the Event Manager process no longer crashes.

CIMPLICITY Points/ Reset Point Timestamps

DE16519 SF-00378115

When a CIMPLICITY point configured with reset point configured updated, the time stamp information is not updated properly.

When a CIMPLICITY point configured with reset point configured updated, the time stamp information is now updated properly.

EMRP/ Column Sorting

DE15666 SF-00373298

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.

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.

EMRP/ Object names

DE11783 SF-00328444

When Event ID/Action ID is fetched from scripts, incorrect object names are returned.

When Event ID/Action ID is fetched from scripts, object names are now returned correctly.

.NET Scripting/ Persistence of data

DE16874 SF-00385377

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.

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.


GE Digital 133



Point Control Panel/ Set Empty String

DE18281 SF-00401417

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.

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.

.NET Scripting/ Invalid ActionIDs

DE18351 SF-00403905

When Cimplicity.CimGetEMEvent().ActionID is used in a Script, incorrect action ID is returned.

When Cimplicity.CimGetEMEvent().ActionID is used in a Script, valid action ID is now returned.

Configuration Object Model/ Memory Leaks

DE9152 SF-00299367

When objects are created using the Configuration Object model, memory leaks are observed.

When objects are created using the Configuration Object model, memory leaks are no longer seen.




Points/ Point Creation Timestamp

DE18660 SF-00283462

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.

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.

EMRP/ Dynamic Mode Crashes

DE18682 SF-00412373

When running a script that does dynamic configuration writes, and saves to a class object, EMRP process crashes occur at random.

When running a script that does dynamic configuration writes, and saves to a class object, EMRP process crashes no longer occur.

EMRP/ Random Crashes

DE17558 SF-00388301

When custom scripts configured using .NET scripting languages are being executed at runtime, EMRP Process crashes at random.

When custom scripts configured using .NET scripting languages are being executed at runtime, EMRP Process crashes no longer occur.

GE Digital 134


Delta Accumulator Point Values

DE18549 SF-00389431

When a delta accumulator point value is updated by configured expression point or by reset point, the updated value is not saved properly. On restarting the project, the delta accumulator point value is not updated properly.

When a delta accumulator point value is updated by configured expression point or by reset point, the updated value is now saved properly. On restarting the project, the delta accumulator point value now gets updated properly.




.NET Scripting/ Updating Array Elements

DE17555 SF-00393346

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.

Points/ Point Creation Timestamp

DE18742 SF-00407529

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.

When "Edit Global Script" option is used to modify a global script, the edit window now brings up the selected script properly.




Points/ Points Browse Tool

DE14872 SF-00422222

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


GE Digital 135



Points/ Points Browse Tool

DE17609; SF-00352736 DE17650; SF-00387727

When browsing points of a project from a Viewer, the point browser dialog crashes randomly.

When browsing points of a project from a Viewer, the point browser dialog no longer crashes.




Point Translation/ Memory Growth Issues

DE22664 SF-00441120

When CimView opens a screen containing a trend object, then the PTX_RP process may experience a memory growth.

When CimView opens a screen containing a trend object, then the PTX_RP process memory growth no longer occurs.




EMRP/ Application Crash

DE18203 SF-00428119

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


GE Digital 136



Events Editor/ Point ID Name

DE37231 SF-00412632

When viewing points configured for events in Event Editor, invalid characters are shown in Point ID Field.

When viewing points configured for events in Event Editor, invalid characters no longer appear in Point ID Field.

PTMRP/ Application Crash

DE28676 SF-00452095

When executing a CIMPLICITY Project, occasional process crashes occur in PTMRP Process.

When executing a CIMPLICITY Project, occasional process crashes no longer occur in PTMRP Process.

EMRP/ Memory Leaks

DE20165 SF-00428120

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.




PTX_RP/ Memory Leaks

DE40924 SF-00473253

When reading points via script in a project, reading unavailable points information causes memory leaks in PTX_RP Process.

When reading points via script in a project, reading unavailable points information no longer causes memory leaks in PTX_RP Process.

Points/ Point Change Events

DE34440 SF-00462824

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.

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.

Quick Watch/ Point Value Evaluation

DE39497 SF-00470188

When debugging a script during runtime, Invalid characters are shown in Quick Watch Window while viewing point values.

When debugging a script during runtime, point values are now shown properly in Quick Watch Window.

Scripting/ Events

DE39806 SF-00470198

When debugging a script during runtime, the changes made to Event Information is not applied properly.

When debugging a script during runtime, the changes made to Event Information is now applied properly.

GE Digital 137


Points/ Point Object

DE41098 SF-00451752

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.

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.




Points/ Change Approval

DE46902 SF-00476462

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.

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.




PTMDP/ Memory Leaks

DE58021 SF-00475592

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.

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.

Event Manager/ Long Point Names

DE58357 SF-00483692

When PointEvent.ID attribute of EMEvent is accessed at runtime, the name of tags configured with long names is not returned properly.

When PointEvent.ID attribute of EMEvent is accessed at runtime, the name of tags configured with long names now gets returned properly.

Points/ Enumerations

DE60583 SF-00493535

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 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 138



Point ID/Values DE66941 SF-00528497

When a dynamic change is made to a virtual point, its saved value reverts to a previous value.

When a dynamic change is made to a virtual point, its saved value does not revert to a previous value.

.NET scripts/ Online update

DE66021 SF-00523237

.NET scripts with a dynamic configuration are not updated online.

.NET scripts with a dynamic configuration are now updated online.

Points/ Accessing Array Elements

DE61742 SF-00476975

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 not displayed.

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 displayed.

EMRP/Process Crash

DE57721 SF-00381936

When starting a CIMPLICITY Project in Run Mode, the EMRP Process stops responding if you pause or restart it during project startup.

When starting a CIMPLICITY Project in Run Mode, the issue of the EMRP Process not responding no longer occurs if you pause or restart it during project startup.


GE Digital 139

3.8 ISSUES RESOLVED: PROFICY INTEGRATION.



iPower/Event List Timestamps

DE8466 SF-00262094

Timestamps for Event Lists shown in iPower do not match the timestamps from server for delayed alarms.

Timestamps for Event Lists shown in iPower now match the timestamps from server for delayed alarms.




Proficy Change Management

DE9306 SF-00301161

Trusted Users are not able to use Auto Login Configuration feature as expected to automatically log into CIMPLICITY and Change Management.

Trusted Users are now able to use Auto Login Configuration feature to automatically log into CIMPLICITY and Change Management. For more information on Auto Login Support Configuration Settings refer to Auto Login Support for Trusted Users - Configuration Settings Page


GE Digital 140



Proficy Change Management/ Domain Authentication

DE7858 SF-00249795

When attempting to use Change Management on a CIMPLICITY 8.1 Version project that has Domain Authentication enabled, the users mapped to the project are unable to perform change updates. An Invalid Perform User ID error message is displayed instead.

After upgrading to 9.0 Version, the Change Management can be successfully used on a CIMPLICITY project that has Domain Authentication enabled to perform change updates.

iPower/Unsolicited Points

DE10349 SF-00259985

When Manual Mode enabled for a Class Object is turned off, the value from device is not read if the *.I0 tag is set up for an update criteria of Unsolicited.

A new global parameter now enables reading of value from device when Manual Mode is turned off. The global parameter is as follows: PTMRP_FORCE_PT_READ_MAN_MODE_OFF

Purpose Enables reading of value from device when Manual Mode is turned off


Y Value is read for points, with Unsolicited update criteria, from device when Manual Mode is truned off.

N Value is read for points, with Unsolicited update criteria, does not get updated with value from device when Manual Mode is turned off.




iPower/Buffered Reports

DE10985 SF-00260107

When processing multiple updates for a device point from an IEC 61850 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 61850 buffered report through PDS, the derived point now processes all the available updates as expected.


GE Digital 141



iPower/Event List Timestamps

DE8466 SF-00262094

Timestamps for Event Lists shown in iPower do not match the timestamps from server for delayed alarms.

Timestamps for Event Lists shown in iPower now match the timestamps from server for delayed alarms.

iPower/ Copying Class Objects

DE16071 SF-00273300

When running iPower, attempting to copy an iPower object from one project to another causes workbench to hang during the copy operation.

When running iPower, copying an iPower object from one project to another happens successfully and workbench no longer hangs during the copy operation.




iPower/ Copying Class Objects

DE18559 SF-00390162

When running iPower, attempting to copy a class object from one project to another 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.




iPower/ Application Process Crash

DE36285 SF-00464898

When running iPower, attempting to dynamically modify class objects, PTMRP/ PTXRP application crashes occur occasionally.

When running iPower, attempting to dynamically modify class objects, PTMRP/PTXRP application crashes no longer occur.


GE Digital 142



iPower/Buffered Reports

DE60550 SF-00260107

When processing multiple updates for a device point from an IEC 61850 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 61850 buffered report through PDS, the derived point now processes all the available updates as expected.


GE Digital 143

3.9 ISSUES RESOLVED: PROFICY PROCESS SYSTEMS.



Data Items/On Change, Poll after Set

DE7085 Case-1-3846140445 SF-00178054

PPS data items were being configured with On Change Update Criteria and Poll after Set, neither of which is supported by PPS.

Now, PPS data items are not being configured with On Change Update Criteria and Poll after Set, neither of which is supported by PPS.




Proficy Process Systems/ Alarm Acknowledgement

DE11710; SF-00313914 DE11521; SF-00303406

When acknowledging alarms from PPS ALARM_A and ALARM_D Faceplates, the acknowledgement does not happen properly after entering the normal state.

When acknowledging alarms from PPS ALARM_A and ALARM_D Faceplates, the acknowledgement now happens properly even after entering the normal state.




Proficy Process Systems/ Alarms Acknowledgement

DE11520 SF-00313914

Acknowledging of alarms from PPS does not occur as expected.

Alarms can now be acknowledged from PPS as expected.




Object Builder/ Events and Actions

DE16653; SF-00180127 DE16657; SF-00255443

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 144



Proficy Process Systems/ Rate of Change Alarms Suppression

DE18737; SF-00409939 DE19543; SF-00280335 DE19551; SF-00343298

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 must 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 145

3.10 ISSUES RESOLVED: PROJECT AND SYSTEM MANAGEMENT.



Action Calendar/DST DE6068 Case-NA SF-00217698

Automatic Daylight Savings Time (DST) caused the Action Calendar to misrepresent workdays/weekdays. In some instances, it shifted an entire month by one day. Example On the calendar:

• Monday. a workday turned yellow indicating it was a weekend day.

• Saturday, a weekend day, turned, green indicating it was a workday.

Automatic DST now advances the Action Calendar clock by one hour only.

Action Calendar/12:00AM Events

DE6917 Case-1-3390720040 SF-00179299

In some circumstances the Events configured in the Action Calendar would not trigger if the time of the event was around the 12:00 AM time-frame. Note: The same events worked at different times of day but would not work when crossing through the 12:00 AM boundary.

Events configured in the Action Calendar trigger correctly even when the time of the event occurs around the 12:00 AM time-frame.

Directory Comparison Report/IE All Versions

DE6301 Case-1-3000189816 SF-00177595

When a CIMPLICITY Directory Comparison Report was opened in Internet Explorer 10 the scrolling and Prev/Next buttons did not work properly.

Now in all Internet Explorer versions, including Internet Explorer 11, both columns in the Directory Comparison Report scroll together and the Prev/Next buttons navigate from/to each section of the report where differences exist.

Startup Options/Nuisance message

DE6819; Case-1-3182731674; SF-00068479 DE6818; Case-1-3145307700; SF-00046582 DE6820; Case-1-3192408574; SF-00046291

(In CIMPLICITY v8.2 SIM 22) An error message would open when the Apply button was clicked in the CIMPLICITY Options dialog box>Startup Options tab. The message, which reported "Unable to open SC Manager" prevented changes from taking effect.

Changes are again made successfully when the Apply button is clicked on the CIMPLICITY Options dialog box>Startup Options tab; no error message is triggered.

GE Digital 146


Mapped Drive/Project Start

DE6834 Case-1-2759760172 SF-00077865

If more than one project was mapped to a network drive, only one project could be started on the mapped drive. A second project could not be started.

More than one project can now be started on a mapped drive. Note: The number of projects that can be started depending on your system's resources.

Project Upgrade Corruption

DE5811 Case-1-4093212101 SF-00179307

If a project was upgraded from CIMPLICITY v8.0 to CIMPLICITY v9.0 it could get corrupted; the point list could not be viewed in the Workbench.

Projects can be successfully upgraded from CIMPLICITY v8.0 to CIMPLICITY v9.0 R2.

Compare Master and Data Report


After doing a configuration update the "Compare Master and Data” report would still show differences after adding a point and doing a configuration update.

The comparison report will no longer show these differences.

Process Health Parameters/Disabled Fields

DE6994 Case-NA SF-00237379

Process Health Parameters caused errors attempting to validate disabled fields.

Process Health Parameters now sets disabled fields back to previously set values.




DEP, ASLR

DE6178; SF-00178636 US4542; SF-NA

Data Execution Prevention (DEP) or Address Space Layout Randomization (ASLR), which can help reduce the risk to executables were not enabled.

CimEdit/CimView are now more secure with DEP/ASLR enabled Important: Some ActiveX controls (e.g. VisiconX) will not work with the updated CimEdit/CimView executables. To continue working with these type of controls, use the CimEdit/CimView .exe files

that are in the install's exe>NODEP folder.


GE Digital 147



Log Viewer List View/Long Messages

DE7471 SF-00230502

When messages were logged to CIMPLICITY COR_STATUS log that contained 260 characters or more the Log Viewer List View message displayed visible corruption at the end of the message.

Messages displayed in the list view will be truncated to 257 character +”...” to indicate that the message was truncated. The full message can be seen in the log entry's Detail View. The List View control has a hard limit of 260 characters.




Action Calendar/Event and Action association

DE8064 SF-00280670

In the Action Calendar, under certain circumstances, Actions associated with an Event are no longer visible.

In the Action Calendar, Actions associated with an Event remain visible.

Login/Logout Functionality

DE8230 SF-00180674

When there are a rapid succession of Logout/Login operations, values for expressions are incorrectly displayed as unavailable in CimView.

When there are a rapid succession of Logout/Login operations, valid expressions are not incorrectly displayed as unavailable in CimView screens.




Login/Login Dialog

DE7903; SF-00279276 DE9384; SF-00302213

When using the CimpLogin.ocx login dialog, it would hang after a successful login.

When using the CimpLogin.ocx login Dialog of CIMPLogin.OCX it will now close properly after a successful login.


GE Digital 148



Project Upgrade/Upgrade Time

DE9689 SF-00307533

When upgrading a project, the upgrade process takes a long time to complete and causes the system to become unresponsive

The time taken to upgrade a project has been reduced significantly and thereby leads to reduced load on the system.

Project Upgrade/Event Editor Crash

DE9035 SF-00297080

When a project is upgraded from a lower version to CIMPLICITY 9.0, Event Manager Resident Process (EMRP) crash occurs on start.

A project can now be upgraded from a lower version to CIMPLICITY 9.0 and started successfully without any Event Manager Resident Process (EMRP) crashes on start.




Workbench/ %PATH% Environment Variable

DE10391 SF-00314846

A CIMPLICITY Workbench crash could occur when the Windows Environment Variable %PATH% contained a long value.

If the Windows Environment Variable %PATH% has a very long value, the CIMPLICITY Workbench will now log an error message in status log and exit gracefully.




Action Calendar/ Events and Actions

DE10479 SF-00308468

When viewing the configuration for Action Calendar, incomplete list of associated Events and Actions is shown.

When viewing the configuration for Action Calendar, list of associated Events and Actions is now shown correctly.


GE Digital 149



Environment Variables/ pm_driver Crash

DE12079 SF-00329476

When commands are executed from an external command prompt, crashes are observed with pm_driver application.

Commands are now executed properly from an external command prompt and no crashes are observed with pm_driver application.




Workbench/ Configuration Update

DE15083 SF-00363701

When updating project configuration, if the persistdata.index and persistdata.data files in the project /data folder are read-only, then a CIMPLICITY Workbench crash occurs.

When updating project configuration, if the persistdata.index and persistdata.data files in the project /data folder are read-only, then the CIMPLICITY Workbench no longer crashes.

Project Shutdown/ EMRP Process Crash

DE14413; SF-00354681 DE15115; SF-00364062

During shutdown, event manager resident process crashes occasionally.

The event manager resident process no longer crashes during shutdown.

Project Startup/ Loading DLLs

DE11227 SF-00320070

When starting a project that uses .NET Assembly, not all DLL references get loaded at startup.

When starting a project that uses .NET Assembly, all DLL references now properly get loaded at startup.

Project Startup/ Application Error

DE11146 SF-00322499

When a project is being started, "Beginning or End of file reached" warning message gets logged.

When a project is being started, "Beginning or End of file reached" warning message no longer gets logged.


GE Digital 150



Workbench/ Device Points

DE14880 SF-00357077

When listing the points of a project, the device points would take a significant time to load/display.

Loading and displaying of device point data no longer takes a significant period.

Project Creation/ OPCUA Protocol Configuration

DE10884; SF-00318159 DE13809; SF-00345349

When using the Project Wizard to configure a new OPC UA device, it was possible to experience a process hang.

When using the Project Wizard to configure a new OPC UA device, a process hang is no longer observed.

Workbench/ Configuration Update

DE16114 SF-00180177

When a project is running and time zone changes occur, some of the system variables do not update properly until the project is restarted.

When the project is running and time zone changes occur, system variables now update properly.




Workbench/ Log Viewer

DE17782 SF-00396163

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.

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.

Workbench/ Domain Authentication

DE17681 SF-00394549

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


GE Digital 151



Workbench/ Project Upgrade

DE18230 SF-00399993

When starting an upgraded project, the user is requested to perform configuration update even when no changes are done.

When starting an upgraded project, the user is now requested to perform configuration update only when project has been modified since last update.




Workbench/ Domain Integration

DE18304 SF-00393684

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

Workbench/ UR Resource Leaks

DE18093 SF-00398067

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.




Workbench/ Project Configuration Update

DE18230 SF-00399993

When starting an upgraded project, the user is requested to perform configuration update for each project start operation, even when no modifications are done.

When starting an upgraded project, the user is now requested to perform configuration update at project start only when modifications are done.

Workbench/ Application Process Crash

DE17909; SF-00381858 DE18658; SF-00406990

When running a CIMPLICITY Project, occasional PTX_RP Process crashes occur.

When running a CIMPLICITY Project, occasional PTX_RP Process crashes no longer occur.


GE Digital 152



Workbench/ Project Upgrade Crash

DE15799 SF-00424432

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.

Workbench/ AMV Sound Manager

DE18616 SF-00391433

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.

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.




Workbench/ WebView Whitespacing

DE30814 SF-00456488

When using the Whitelist feature for configuring WebView sessions the configured values get truncated.

When using the Whitelist feature for configuring WebView sessions the configured values no longer get truncated.


GE Digital 153



Workbench/ WebView Whitespacing

DE37165 SF-00467292

When a web page is created in a folder on a remote node, the Whitelist feature does not get enabled properly and the configured webpage fails to load.

When a web page is created in a folder on a remote node, the Whitelist feature now gets enabled properly and the configured webpage loads properly.




Workbench/ Application Crash

DE39078 SF-00463883

When configuring OPC Client Device, workbench crashes are observed.

When configuring OPC Client Device, workbench crashes are no longer seen.

Workbench/ Filtering Points

DE39191 SF-00470333

When viewing points in Workbench, filter settings are not applied when displaying points.

When viewing points in Workbench, filter settings are now applied properly and points are displayed properly based on the configured filter options.


GE Digital 154

3.11 ISSUES RESOLVED: RECIPES



Upload Recipe/Insufficient Memory

DE7895 SF-00264181

When attempting to upload a recipe in a CIMPLICITY project with many configured recipes, the operation fails with an error: STG_E_INSUFFICIENT_MEMORY.

Recipes may now be uploaded into a CIMPLICITY project with many configured recipes.




Recipes/ Recipe Upload - Corruption Issue

DE15153 SF-00422712

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.




Recipes/ Text Data Type Variables

DE60736 SF-00475786

When a CIMPLICITY Project, configured with Recipes having virtual points of Text Data Type, is in run mode, the values of variables are not updated in the recipe control.

When a CIMPLICITY Project, configured with Recipes having virtual points of Text Data Type, is in run mode, the values of variables are updated in the recipe control.


GE Digital 155

3.12 ISSUES RESOLVED: SERVER REDUNDANCY.



Alarm Setup/Offline Configuration

DE7266 SF-00177527

If an Alarm Setup was configured for a redundant pair when the project was offline, the Workbench: 1. Did not detect the change 2. Did not prompt for a configuration update. As a result, 1. The alarm setup, which was not copied to the Secondary node until a configuration update was performed, was only properly available on the Primary node. 2. When the Secondary node became the master, if there had not been a configuration update, the alarm setup did not work for clients.

If a project is offline, the Workbench now prompts for a configuration update after the Alarm Setup configuration is changed and before the project starts.




Alarm Setup/Offline Configuration From a Viewer

DE7476 SF-00177527

When an Alarm Setup was configured from a Viewer for a redundant pair while the project was offline, the Primary and Secondary servers did not synchronize, even when they were up and running again.

If an alarm setup is configured from a Viewer for a redundant pair both the primary and secondary servers must be running to make sure they will be synchronized. This requirement is by design and will not change.




Server Redundancy/Viewer to active server access

DE7927 SF-NA

When there are active references to points that are Class Object attributes with a combined length greater than 32 characters, ptm_rp.exe would crash during a failover.

ptm_rp.exe no longer crashes and all the points continue to function correctly.


GE Digital 156



Server Redundancy/PTM Process Termination

DE8916 SF-00291553

When starting a project, if a logical link between a device communications driver and Point Management failed because the logical link shared file was in use, it would cause Point Management to self-terminate.

Now when starting a project, the logical link shared file names are tested to confirm they are available prior to attempting to use them. If the shared file names are used, the new ones are obtained to confirm that they are not in use. In addition, the Point Management process will no longer self-terminate when this situation is encountered.




Server Redundancy/ Process Termination

DE5765; SF-00209114 DE12879; SF-00317576

When starting a project configured with redundancy support, if bulk operations like addition/deleting of points are performed, the resident processes terminate occasionally.

When starting a project configured with redundancy support, the resident processes no longer get terminated unexpectedly, if bulk operations like addition/deleting of points are performed during startup.




Server Redundancy/ Process Termination

DE14420 SF-00348037

When a project having On Demand points configured with Delay Load is used with Server Redundancy, the slave node in the redundant pair logs errors in corelog for point updates on an On Demand point.

When a project having On Demand points configured with Delay Load is used with Server Redundancy, the slave node in the redundant pair no longer logs errors in corelog for point updates on an On Demand point.


GE Digital 157



Server Redundancy/PTM_RP Process Termination

DE5765; SF-00209114 DE12877; SF-00331840 DE13292; SF-00330088 DE13800; SF-00326227 DE13802; SF-00203971 DE13815; SF-00347227 DE14623; SF-00323382 DE14628; SF-00319791 DE14631; SF-00358206 DE14632; SF-00326198 DE14993; SF-00318740 DE14995; SF-00349317 DE15659; SF-00364925 DE15661; SF-00354793 DE12878; SF-00332477

When starting a project configured with redundancy support, the Point Management process gets terminated occasionally.

When starting a project configured with redundancy support, the Point Management process no longer gets terminated.




Server Redundancy/ Primary Server Fail-over

DE42385 SF-00447900

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.


GE Digital 158

3.13 ISSUES RESOLVED: STATISTICAL PROCESS CONTROL (SPC).



SPC/ Moving Range Charts

DE16754 SF-00286343

SPC ”Moving Range” chart does not display values for the selected range.

SPC ”Moving Range” chart now displays values for the selected range.




SPC/ Timestamp Values

DE18437 SF-00402203

When a project having SPC is configured to log values into SQL, invalid timestamps are being logged by the SPC Module.

When a project having SPC is configured to log values into SQL, proper timestamps are now set for values being logged by the SPC Module.




SPC/ Data Import/Export

DE17890 SF-00429636

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.




SPC/ Duplicate Data Records

DE31619 SF-00450851

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.


GE Digital 159

3.14 ISSUES RESOLVED: TRACKER/ORDER EXECUTION MANAGEMENT



Ranges/Referenced by Criteria Sets

DE7311 SF-00180122

If a user attempted to modify a range that was referenced by criteria sets, it would fail.

Ranges that are referenced by criteria sets can now be modified.

Ranges/Referenced by Criteria Sets

DE7247 SF-00249260

Trkcollector.exe could crash

when multiple Tracker projects ran on the same computer and one project was stopped.

Trkcollector.exe continues to run

when multiple Tracker projects run on the same computer and one project is stopped.




PRT_DC/Shifting Regions DE7486 SF-00260020

PRT does not respond when multiple items per location are moved in a shifting region.

PRT works as expected when moving multiple items per location in a shifting region.

RLM Script/RCO Site DE7702 SF-00270280

RCO Site crashes when RCO Object is declared globally in a script.

RCO Site no longer crashes when RCO Object is declared globally in a script.

CimBasic/ProjectID DE7527 SF-00178179

If you use a long Project ID String for setting ProjectID, then memory corruption would occur.

You can use long Project ID Strings for setting ProjectID without any memory corruption issues.

PRT_CNT/COR_LOG Messages DE7525 SF-00179024

Every attempt to get back a connection was being logged by PRT_CNT when TADB was disconnected.

Only the initial connection failure information is now logged. No additional connection errors will be logged until the connection is restored and lost again.

GE Digital 160


TQE/Expression Editor DE7521 SF-00178890

After deleting an expression, a new expression with same name cannot be created in the Expression Editor.

Once an expression is deleted, a new expression can now be created, inheriting the revision history of the original expression.

TADB/Save Named Expression DE7523 SF-00178693

Single quotes in named expression comments results in failures during save operations.

Single quote in expression comments now works without any failures.

TrkItemAgent/AttributeName Expression

DE7771 SF-NA

Blanks in Shifting Regions were being processed by TrkCollector, resulting in large delays

TrkCollector no longer processes shifting region blanks.




PRT_UI/Hang Issue

DE7850 SF-00277228

The Tracker display process (PRT_UI) hangs when using $UNK_SER and $UNKNOWN item types.

The Tracker display process (PRT_UI) no longer hangs when using $UNK_SER and $UNKNOWN item types.

PRT_UI/Project Selection

DE7915 SF-00264169

Projects could not be selected from the Tracker display (PRT_UI's) using a keyboard.

Projects can now be selected from the Tracker display (PRT_UI's) using a keyboard.

Tracker/Item ID Values

DE7938 SF-00279170

The Tracker display (PRT UI) was incorrectly accepting Item IDs or Reference IDs containing commas and semicolons resulting in downstream errors.

The Tracker display (PRT UI) no longer accepts Item IDs or Reference IDs containing commas and semicolons.


GE Digital 161



PRT_DC/Project Upgrade

DE8851 SF-00295940

After upgrade, PRT_DC does not start when region validation is configured.

PRT_DC now starts successfully when region validation is configured.




Tracker Agent API/Performance Degradation

DE9844 SF-00305274

A performance degradation was observed when iterating through the entire Tracking Image Collection of items using Tracker Item Agent and Tracker Region Agent objects. The performance is improved when the iteration is done using PRT objects via BCL scripts.

Performance improvements have been done to reduce the time taken to iterate through the entire Tracking Image Collection of items using the Tracker Item Agent and Tracker Region Agent objects. Also, the following additional properties have been added to TrkAttributes object in the Tracker Agent API: 1. Class(index) as Long 2. ItemID(index) String 3. LastModDate(index) as Date 4. Name(Index) as String 5. ProjectName(index) as String 6. Value(index) as Variant 7. VirtualID(index) as String

Tracker APIs/ TADB De-Synchronization

DE8914 SF-00297140

When items are added using Tracker APIs, TADB and PRT end up in a De-Synchronized state and duplicate entries get created in TADB.

Adding Items using the Tracker API’s no longer leads to a desynchronized state of TADB and PRT. Also, duplicate entries no longer get created in TADB.

PRTCNT/ Value Truncation

DE9251 SF-00300179

When displaying extended attribute data using PRTCNT, a type conversion would truncate the length of the value displayed to a limit that is less than permitted.

When displaying extended attribute data using PRTCNT, the type conversion no longer truncates the length of value displayed to a limit that is less than permitted.


GE Digital 162



TADB/ Improper Updates

DE11327 SF-00322575

When inserting items in PRT, the new items with blank references were incorrectly matched to items without reference ID in TADB, leading to data corruption.

When inserting items in PRT, matching of items with blank or empty references no longer occurs and prevents data corruptions.

TADB/ Internal Hold Attribute

DE10454 SF-00315357

When TADB is enabled, requesting the internal hold attribute from an item will return 0, even when the internal hold is set.

Correct value of internal hold attribute, based on the internal hold setting on the item, is now returned.

Data Import/ prt_import crash

DE10467 SF-00305851

When insufficient inputs are provided to the extended attribute record, the prt_import tool crash occurs.

When insufficient inputs are provided to the extended attribute record, the prt_import tool no longer crashes.

Tracker DevCom/ Point Timestamps

DE11145 SF-00322364

Timestamps of Tracker DevCom points get updated without a change in underlying point data source. This leads to errors when updating application logic based on device point timestamps.

Timestamps of Tracker DevCom points now get updated only when underlying point data source has changed. Thus, updating of application logic based on device point timestamps occurs correctly.

Data Export/ prt_export configuration

DE10956 SF-00316873

When exporting data from the Tracker Module, the delimiter characters configured in prt_export config file are not used in the output file.

When exporting data from the Tracker Module, the delimiter characters configured in prt_export config file are now used in the output file as specified.


GE Digital 163



Tracker DevComm/ DLL Registration

DE11507 SF-00326299

When installing SIM on Viewer Node, the Tracker DevComm Dll fails to get registered on the node.

When installing SIM on Viewer Node, the Tracker DevComm Dll now gets registered on the node successfully.

Tracker Agent API/Performance Degradation

US11450 SF-00305274

A performance degradation was observed when iterating through the entire Tracking Image Collection of items using Tracker Item Agent and Tracker Region Agent objects. The performance is improved when the iteration is done using PRT objects via BCL scripts.

Performance improvements have been done to reduce the time taken to iterate through the entire Tracking Image Collection of items using the Tracker Item Agent and Tracker Region Agent objects. Also, the following additional properties have been added to TrkAttributes object in the Tracker Agent API: 1. Class(index) as Long 2. ItemID(index) String 3. LastModDate(index) as Date 4. Name(Index) as String 5. ProjectName(index) as String 6. Value(index) as Variant 7. VirtualID(index) as String Note: Please check Tracker Collector Enhancements for more information.

TrkItemAgent/Regex Expression

DE11298 SF-00323817

When comparing expressions, case sensitive matching of expressions do not occur.

Case sensitive matching of expressions are now allowed when comparing expressions.

RCO/TADB Import Export Tool/SQL Server Authentication

DE11357 SF-00228956

When importing an RCO Database or TADB Meta data into an SQL Database, the SQL Server authentication details cannot not used.

When importing an RCO Database or TADB Meta data into an SQL Database, the SQL Server authentication, if provided, will now be used for authentication purposes.

Tracker Agent Object/Attribute Limits

DE11396 SF-00321809

When modifying or updating extended attribute value using PRT_UI, user is limited to 255 characters, as compared to 512 characters when modifying the value programmatically.

The limit for extended attribute value is now limited to 512 characters both programmatically and from PRT_UI.

GE Digital 164


Tracker Device Communication/ Data Corruption

DE11435 SF-00322124

When using Tracker Device Communication, the point values get corrupted or become unavailable at times.

The point values obtained using Tracker Device communication no longer get corrupted or go unavailable during usage.

PRT_DC/ Synchronization Errors

DE11518; SF-00325751 DE11934; SF-00329597

When performing maintenance operations, invalid synchronization error messages get generated.

When performing maintenance operations, invalid synchronization error messages no longer get generated.

PRT_UI/ Item Attribute Data

DE11647 SF-00326842

When displaying attribute data of an item of type $UNK_SER, values do not get displayed properly.

When displaying attribute data of an item of type $UNK_SER, values now get displayed properly.

TrkItemAgent/Attribute Value Comparison

DE11708 SF-00328092

When comparing attribute values, the values being compared do not get cast properly, resulting in invalid comparisons.

When comparing attribute values, the values being compared now get cast properly and no invalid comparisons occur.

PRT_UI/ Crash Issue DE11927 SF-00327618

PRT_UI crash occurs when moving items that were deleted and recreated into locations occupied by normal / regular items

PRT_UI no longer crashes when moving items that were deleted and recreated into locations occupied by normal / regular items

TADB/ Item Rename Operation

DE11957 SF-00329506

When trying to access serialized items from script, some of the items are not read properly

When accessing serialized items from script, all items are read properly as expected.

TADB/ Item Rename Operation

DE11930; SF-00329174 DE11929; SF-00329527

With TADB enabled, locating an item after renaming is not possible at times.

With TADB enabled, locating an item after renaming now happens successfully.


GE Digital 165



PRT_DC/ Process Hang

DE13081 SF-00322084

When using a Tracker project, Tracker PRT_DC process hangs occasionally.

When using a Tracker project, Tracker PRT_DC process hangs no longer occur.

Tracker/ Help for Custom Function Block

DE11395 SF-00324597

When custom block is created, the help text displayed in custom function block gets truncated and it is not possible to re-size the help controls.

When custom block is created, the help text displayed in custom function block no longer gets truncated and the help controls can be re-sized as needed.

Data Import-Export/ Identifying Special Characters

DE11597 SF-00326590

When working on a Tracker project, the PRT_Export and PRT_Import processes do not recognize carriage return and line feed characters in attribute names or values properly.

When working on a Tracker project, the PRT_Export and PRT_Import processes now recognize carriage return and line feed characters in attribute names or values properly.

Tracker Device Communication/ Solve Interface

DE12286 SF-00331577

When Solve Interface is used via script in a Tracker project, the constant for "InternalHold" get mapped incorrectly. Also, the SQL generation script gets omitted when itemClass is specified with missing parentheses.

When Solve Interface is used via script in a Tracker project, the constant for "InternalHold" now gets mapped correctly. The SQL generation script no longer gets omitted if itemClass is specified with missing parentheses.

Tracker Device Communication/ Data Integrity Issues

DE12468 SF-00333234

When using a Tracker project, if there is item location mismatch due to movement of items, invalid error messages about data integrity issues get logged.

When using a Tracker project, if there is item location mismatch due to movement of items, invalid error messages about data integrity issues do not get logged.

PRT_CNT/ CPU Utilization

DE12928 SF-00336218

When using a Tracker project is configured to count attributes from multiple regions, the prt_cnt.exe process ends up with high CPU utilization.

When using a Tracker project is configured to count attributes from multiple regions, the prt_cnt.exe process no longer causes CPU utilization issues.

Tracker Device Communication/ Global Parameters

DE9801 SF-00307527

When reading system attributes, global parameters do not get read properly.

When reading system attributes, global parameters now get read properly.


GE Digital 166



Tracker Collector/ Error Messages

DE12609 SF-00335063

When an item is deleted from a running project, the item gets deleted, but error messages are logged in corelog.

Error messages are no longer logged in corelog when an item is deleted from a running project. The selected item gets deleted properly.

RCO/ Memory Leaks

DE12792 SF-00336216

With BASIC_MULTITHREAD_COM flag set to Y, using RCO results in memory leaks

With BASIC_MULTITHREAD_COM flag set to Y, memory leaks are no longer observed while using RCO.

PRT_DC/ Bad File Lengths

DE13075 SF-00302050

Using prt_glb_vfy.exe application causes Tracker configuration files to go into an invalid state.

Using prt_glb_vfy.exe application no longer causes Tracker configuration files to go into an invalid state.

WYSIWYG Forms/ Memory Leaks

DE13088 SF-00339826

When broadcasting a WYSIWYG object with lot of Point Data Sources, resource leaks are observed.

Resource leaks are no longer seen when broadcasting a WYSIWYG object with lot of Point Data Sources.

PRT/ Filter Support

DE14427; SF-00354180 DE14763; SF-00356840

PRT.ItemLocate returns items from multiple projects even after PRT.ProjectID is set to a single project.

PRT.ItemLocate now returns items based on the configured filter attribute.

TrkCollector/ Cache Updates

DE14625 SF-00355740

When using TrkCollector, attribute changes to cache are not saved properly.

When using TrkCollector, attribute changes to cache now saved properly.

RCO/ Refresh Issue

DE14762 SF-00357575

When using RCO, some of the dialogs do not refresh properly.

When using RCO, the dialogs now refresh and display properly.

PRT_CNT/ Performance Issue

DE14505 SF-00355738

When processing PRT_CNT requests, performance drop is seen for trkcollector module leading to denial of service issues.

When processing PRT_CNT requests, performance drop is no longer seen for trkcollector module. Denial of service issues no longer occur.

PRT_DC/ Process Crash

DE13854 SF-00348693

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.

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.


GE Digital 167



TADB Util/ Memory Corruption

DE15732 SF-00373591

When starting a Tracker project with TADB enabled, memory corruption issues are observed.

When starting a Tracker project with TADB enabled, memory corruption issues are no longer observed.

Tracker DevComm/ Crash on stop

DE15795 SF-00373258

When stopping a Tracker project, Tracker DevCom crashes are observed.

When stopping a Tracker project, Tracker DevCom crashes no longer occur.

TADB/ Error Messages

DE15797 SF-00374309

When executing scripts in a Tracker Project, some error messages are logged with insufficient information into log

When executing scripts in a Tracker Project, the error messages are now logged with proper information into log




Tracker Collector/ Error Messages

DE17651 SF-00393068

When logging is enabled for a region and there is a route configured that has the region as the source, but no destination region, and there is more than one project running on the node, then error messages are logged in System Log.

When logging is enabled for a region and there is a route configured that has the region as the source, but no destination region, and there is more than one project running on the node, error messages are no longer logged in System Log.




BCO Objects/ ASCII Broadcast Forms

DE17992 SF-00395474

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 168



PRT_CLIENT/ Item Type ID

DE18160 SF-00393321

When PRT_CLIENT is used in a Tracker project to route an item between projects, and the route has a "Setpoint ID" field populated for the route, then when the item transitions occur, the Item Type ID is not written out.

When PRT_CLIENT is used in a Tracker project to route an item between projects, and the route has a "Setpoint ID" field populated for the route, then when the item transitions occur, the Item Type ID now gets written out as expected.

Trkcollector.exe/ Application Crash

DE18931 SF-00405210

When an application configured with Tracker is run, TrkCollector application crash occurs occasionally.

When an application configured with Tracker is run, TrkCollector application occasional crashes no longer occur.

Tracker/ PRT_UI process crash

DE16113 SF-00424655

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 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




Tracker Configuration UI/ Historical TADB

DE22548 SF-00434546

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 using Tracker Configuration UI to enable/disable TADB replication in Historical TADB, SQL Stored Procedures now get executed properly and failures no longer occur.

Tracker/ PRT_EXPORT.exe process crash

DE17736 SF-00425563

When using prt_export.exe to export data, application crash occurs if NO_TRKPRO extension is used in the command line.

When using prt_export.exe to export data, application crash no longer occurs if NO_TRKPRO extension is used in the command line.


GE Digital 169



Tracker/ Range Maintenance Error

DE70957 SF-00502099

In a Tracker application that does not use TADB, when you use the Tracker Configuration utility to access Range Maintenance and create a range, a blank error message appears.

In a Tracker application that does not use TADB, when you use the Tracker Configuration utility to access Range Maintenance and create a range, a meaningful error message appears.

Tracker Query/ New Item Error

DE70370 Internal

In the Tracker Query window, when you enter a new Item Type manually instead of selecting it from the drop-down list box, the error message that appears is not dismissed even after you select OK.

In the Tracker Query window, when you enter a new Item Type manually instead of selecting it from the drop-down list box, the error message that appears is dismissed after you select OK.

Tracker/ PRTV DE70099 SF-00348852

When the PRTV command is run for a file in a Tracker project, duplicate records are created.

When the PRTV command is run for a file in a Tracker project, duplicate records are not created.

Tracker/ PRT_IMPORT.EXE Performance

DE68661 SF-00535596

The performance of running the prt_import.exe file degrades during import.

The performance of running the prt_import.exe file during import has improved by approximately 96 percent.

TRK_DC/ Process Crash and Memory Leak

DE66246 SF-00508237

When running a Tracker project for a long time, memory leaks occur and occasionally processes stop responding on the TRK_DC module.

When running a Tracker project for a long time, memory leak issues and occasional cases of processes not responding no longer occur on the TRK_DC module.

Item Agent/ “Where” Clause

DE65485 SF-00529749

When the Tracker Item Agent is used to filter the item collection returned by using the “Where” clause, no items are returned.

When the Tracker Item Agent is used to filter the item collection returned by using the “Where” clause, the restricted set of items are returned.


GE Digital 170

3.15 ISSUES RESOLVED: TRENDS AND DGR



Trend Logged Lines/Back Button

DE6099 Case-1-1566081001 SF-00177416

When a user clicked the Back button on a Trend screen that was displaying logged line data from SQL Server a Mutex type error would be sent to the Status log.

When the Back button is clicked on a Trend screen that displays logged line data from SQL Server, the trend scrolls back; an error is not logged to the Status log.

Trend Objects/Overlay Screens

DE6113 Case-1-3837988991 SF-00177460

If CimView screens with Trend objects repeatedly overlaid other CimView screens with Trend objects, CimView would crash.

CimView screens with Trend objects can now repeatedly overlay other CimView screens with Trend objects.

Trend Objects/Browsing DE6117 Case-1-1498028500 SF-00177396

CimView would crash at times, when a user browsed among Trend OCX objects and added/deleted Historian and/or logged Trend lines.

CimView continues to run when a user browses among a screen's Trend objects and adds/deletes Historian and/or logged Trend lines.

Trend/Zoom with Reference Line

DE6410 Case-1-1797631581 SF-00177359

A Trend chart that included a Reference line could be zoomed only one time; additional attempts had no effect. Note: The Zoom worked correctly if the Reference line was made invisible or removed from the chart.

A Trend chart that includes a reference line (visible or invisible) now zooms correctly.

Trend/_TIME_ DE6832 Case-1-2838531001 SF-00069773

Data from GROUP Log tables would not display on Trend charts if the logged points had IDs that included the characters _TIME_.

Points with IDs that include the characters _TIME_ now

successfully display on Trend charts that pull data from GROUP Log tables.

DGR/State Change DE6781 Case-1-1056528547 SF-00051511

DGR would crash after it was repeatedly paused, changed speed and returned to play.

DGR continues to operate correctly when it is repeatedly paused, changed speed and returned to play.

GE Digital 171


Historian Lines/Interpolated, Sample Interval Display Issues

DE5764 Case-NA SF-00221056

A Historian trend line with an interpolated retrieval mode and sample interval that was 40 minutes or more would not display

A Historian trend lines with an interpolated retrieval mode and sample interval that is 40 minutes or more display correctly.

Class Attribute/DGR/CimView

DE6038 Case-NA SF-00221421

If a class attribute was accessed directly from a screen and DGR was used on that screen both CimView and DGR would fail when DGR went back from Historical to Live mode..

CimView and DGR will continue to run when a class attribute is accessed directly from the screen when DGR is used on the screen.




QuickTrends/Multiple Lines/Server Redundancy

DE7636; SF- 00217148 DE7652; SF-00250236

If many 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. 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.

QuickTrends will now successfully display multiple lines when Server Redundancy is enabled.




Trend/WriteReferenceFile Method

DE8256 SF-00268510

WriteReferenceFile Method does not generate output file as expected on systems with Regional Settings configured.

WriteReferenceFile Method now generates output file as expected on systems with Regional Settings configured.


GE Digital 172



Trend/Logged Errors

DE9731; SF-00300308 DE9403; SF-00237921

When trend methods are called from scripts to add lines to trend object, status log error messages errors get logged in the core Status Log.

Trend methods can now be successfully called from scripts to add lines to trend object, with no errors logged to the core Status Log.




DGR/Displaying Scaled Values

DE10850; SF-00318504 DE9787; SF-00308673

When the client’s applications are run in DGR mode, EU conversion rules are incorrectly applied to device point values, resulting in improper display.

When the client’s applications are run in DGR mode, EU conversion rules are now correctly applied to device point values and displayed properly. Note: In DGR mode, the EU conversion rules are not applied to values retrieved from SQL server for points of QINT and UQINT data types.




Trend/ Procedures

DE14421 SF-00350694

When adding new lines to the trend chart via a procedure, not all lines get added properly.

When adding new lines to the trend chart via a procedure, all lines now get added properly.

Trend/ SQL Passwords

DE13295 SF-00341338

When special characters are used in the password for an SQL User, the data logged into SQL Server via data logger does not get retrieved using the QuickTrend.

When special characters are used in the password for an SQL User, the data logged into SQL Server via data logger can now be retrieved using the QuickTrend.


GE Digital 173



Trend/ Logged Errors

DE7920; SF-00280013 DE9405; SF-00301928 DE12536; SF-00255784

When QuickTrend tool is used to view trending of values, User DSNs created during the trending operations do not get deleted, resulting in reduced machine performance levels.

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.

Trend/ SQL Passwords

DE13295 SF-00341338

When special characters are used in the password for an SQL User, the data logged into SQL Server via data logger does not get retrieved using the QuickTrend.

When special characters are used in the password for an SQL User, the data logged into SQL Server via data logger can now be retrieved using the QuickTrend.




Trend/ User DSNs

DE12536 SF-00255784



Trend/ DeleteTrendLine Method

DE17652 SF-00393780

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.

Quick Trend/ User DSN

DE15986 SF-00376562



GE Digital 174


Trend/ Historian Line Types

DE7337 SF-00253320

When plotting trend for Interpolated lines, the samples do not get plotted properly for time durations that are greater than an hour.

Trend for Interpolated lines with sample intervals beyond an hour now get plotted properly.




Trend/ AddLoggedLine Method

DE16256 SF-00374140

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.

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.





DE18495 SF-00406993

When a Trend control used on a screen has historian logged points configured, multiple login requests are shown to user.

When a Trend control used on a screen has historian logged points configured, multiple login requests are no longer shown to user.


DE18161 SF-00399411

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.

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.

GE Digital 175


Quick Trend/ User DSN

DE15986 SF-00376562



QuickTrends/ Multiple Lines/ Server Redundancy

DE7652; SF-00250236 DE7636; SF-00217148

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

QuickTrends will now successfully display multiple lines when Server Redundancy is enabled.

DGR/ Replay Freeze Issue

DE18778 SF-00398821

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.




Trend/ AddLoggedLine Method

DE12534 SF-00323263

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.

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.


GE Digital 176




DE17738 SF-00428686

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




Trend/ Line Types

DE29428 SF-00453292

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.




Trend/ Reference Line Exports

DE44669 SF-00479503

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.


GE Digital 177

4 KNOWN ISSUES

Known issues in the CIMPLICITY V9.0+ releases are as follows.

Product Limitation: Saving User Name and Password from Login Dialog. When specifying username and password in the Login Dialog, user can enable a check box to indicate that the login credentials be persisted. This support is not working at present and is a known issue.

Product Limitation: Changing Origin of a Point during Import using CLIE Tool DE32091 SF-00457615 The Origin or type of point cannot be changed using CLIE Tool while importing points into a CIMPLICITY Project.

WebSpace Compatibility Update 4 The WebSpace Compatibility Update 4 is applicable for SIMs starting CIMPLICITY 9.0 SIM 20. This update patch is not compatible with older SIMs.

Mouse Move Operations on Touch Enabled Screens Mouse Move operations on Touch Enabled Screens do not work as expected.

Ad hoc Point by Address/CIMPLICITY OPC UA Client Ad-hoc Point by Address is not supported for CIMPLICITY OPC UA Client in this release.

Redundancy/CIMPLICITY OPC UA When configuring host redundancy for the OPC UA, the secondary server is always active.

Performance Counters on 64-Bit Operating Systems (For 64-bit operating system users) HMI performance counters are not available in the 64-bit Performance Monitor. Following are solutions to the two issues that you can encounter if you try to use the 64-bit Performance Monitor.

Issue Resolution

HMI performance counters do not display in the Performance Monitor User Interface.

Run the 32-bit executable: ..\SysWOW64\perfmon.exe

Data logging log file for HMI performance counters is empty when a data collector for HMI performance counters is created.

Use the 32-bit executable ..\SysWOW64\perfmon.exe

Note: Replace 64-bit logging service with 32-bit logging service. A Windows sc.exe utility is available.

Review Microsoft documentation for details.


4.1 ADMINISTRATOR PRIVILEGES REQUIRED

One or more tabs in the CIMPLICITY® Options dialog box require you to run the Workbench as administrator. Exactly what tabs require this depends on the operating system and your system configuration.

Messages include the following.

GE Digital 178

You need administrator privilege to configure the items on this page Unable to open SC Manager.

The following two options are available to access these features.

Run as Administrator 1. Right-click the Workbench in the Windows Start menu>Proficy HMI SCADA - CIMPLICITY 9.0 section (or

Start Page). 2. Select Run as administrator on the Popup menu.

The CIMPLICITY Workbench opens. 3. Open the CIMPLICITY project through the Workbench.

Result: Windows administrators will have access to the CIMPLICITY Options dialog box for the session that the project is opened using Run as administrator.

Note: If you use this method frequently, create a Workbench shortcut on your desktop.

Set Local Security 1. Open the Local Security Policy window. 2. Do the following.

GE Digital 179

1. Expand Local Policies in the Local Security Policy window left-pane. 2. Select Security Options. 3. Right-click User Account Control: Run all administrators in Admin Approval Mode. A User Account Control : Run all administrators in Admin Approval Mode dialog box opens.

3. Select Disabled on the Local Security Setting tab. 4. Click OK.

Result: Windows administrators will have access to the CIMPLICITY Options dialog box tabs whenever it is opened.


4.2 SQL SERVER

SQL Server 2014 Express Conflict with SQL Server 2012 Express There is a conflict when installing SQL Server 2014 Express on a machine that has SQL Server 2012 Express installed. If you plan to install SQL Server 2014 Express and have SQL Server 2012 Express already installed, uninstall SQL Server 2012 Native Client first. The SQL Server 2014 installation will update SQL Server 2012 Native Client with an updated version.

SQL Server 2005 Data Importing to SQL Server 2012 SQL Server can be upgraded to have SQL Server 2012 successfully log data from CIMPLICITY v8.0+ with SQL server 2005 (or lower) logging data. This requires some steps that

1. Upgrade the CIMPLICITY v8.0 project to CIMPLICITY v9.0. 2. Start the upgraded project.

This will create the tables in the CIMPLICITY v9.0 SQL 2012 database with corresponding indexes and constraints.

3. Stop the upgraded project. 4. Open the Import Data Wizard. 5. Perform an Import task with the SQL 2005 CIMPLICITY database as the source. 6. Do the following in the Select Source Tables and Views dialog box for each of the table’s Column

Mappings: 7. Click Edit Mappings.

A Column Mappings dialog box opens.

GE Digital 180

A. Select the Delete rows in Destination table radio button. Note: If append rows to existing rows in the table is chosen, errors are generated including: Unable to insert read only field of Sequence_number field.

B. Select the Enable identity insert check box. 8. Continue with the SQL Server Import and Export Wizard. 9. Select the following in the Review Data Type Mapping dialog box.

On Error (global) Ignore

On Truncation (global) Ignore

10. (After data is imported) Start the upgraded project to log data in the tables. Result: Data, including the CIMPLICITY V9.0 long point IDs will be logged successfully.

SQL Server Configuration Manager Does Not Display CIMPLICITY Issues have been observed using the Start Menu or Start Page to open the SQL Server Configuration Manager on Windows 2012 64-bit and Windows 2008 Enterprise 64-bit machines when both CIMPLICITY v9.0 with SQL Express 2012 and Historian with the Alarm Archiver are running on the same machine. Not all the actual instances display in the SQL Server Configuration Manager. Open the SQL Server Configuration Manager, instead, through Windows Explorer. The path is: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Microsoft SQL Server

2012\Configuration Tools\SQL Server Configuration Manager.


4.3 TRACKER PROJECT UPGRADE AND TADB REPLICATION

When opening a Tracker Project on a system that has CIMPLICITY 9.0 Version installed with SIM 21 patch, an upgrade to the project might be required. During the project upgrade process, TADB Replication errors might be encountered.

GE Digital 181

If TADB Replication errors occur, before attempting to re-open the Tracker Project, the options mentioned below must be followed to mitigate upgrade failure errors: 1. Attempt to open the Tracker Project after disabling TADB Replication option. 2. If replication errors are still reported, then:

a. Attempt to Suspend and Resume the Replication. b. If the replication errors are still reported, then run command to drop the subscriptions before

trying to open the project. 3. Once the project has been upgraded successfully, re-enable the TADB Replication Option for the project. The section below explains the above listed steps in detail: 1. Attempt project upgrade operation by disabling the TADB Replication Option: To ensure that there are no

replication related errors, please disable TADB Replication Option by turning off the Replication option manually or by running the following SQL Query Command on the TADB Database:

USE [<TADB Database Name>]

GO

UPDATE [dbo].[TADBConfig]

SET value=0

WHERE name = ‘Replication’

GO

Once the TADB Replication option has been disabled, the Tracker Project, when opened in Workbench will request an upgrade. During upgrade, if replication errors, such as "Could not drop Article. A subscription exists on it." are reported, then please perform the following steps: a) Run "cimsp_SuspendReplication" stored procedure on the project's TADB Database, as shown below:

Use[<TADB Database Name>]

GO

DECLARE @return_value int

EXEC @return_value = [dbo].[cimsp_SuspendReplication]

SELECT ‘return value’ = @return_value

GO

If the stored procedure executes successfully, then resume the replication by executing the following command set:

Use[<TADB Database Name>]

GO

DECLARE @return_value int

EXEC @return_value = [dbo].[cimsp_ResumeReplication]

SELECT ‘return value’ = @return_value

GO

Once the replication is resumed, the project upgrade must happen successfully.

b) However, if replication errors "Could not drop Article. A subscription exists on it." are reported, then

drop the associated subscriptions by executing the following query: EXEC sp_dropsubscription

@publication= '<TADB Database Name>', @subscriber = 'all' , @article

= 'all'

Now reopen the project and the upgrade process must happen successfully. 2. Once the project has been successfully upgraded, the TADB Replication option must be re-enabled from

the TADB Datasource Specification Dialog so that the necessary subscriptions are re-created in the project.

GE Digital 182


GE Digital 183

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

Number Additional Information

McAfee Agent 5.0.5.658 Last security update check: 4/24/2018 12:06:50 PM

Last agent-to-server

communication: 4/24/2018 11:09:11 AM

McAfee GTI Proxy Agent 2.0.0.705 Language: English (United States)

McAfee Host Intrusion

Prevention

8.0 Build date: Tuesday, April 18, 2017

Build Number: 8.0.0.4228

Security Content Version: 8.0.0.8330

Security Content Created On: Wednesday, April 04, 2018

Patch: 9

McAfee VirusScan

Enterprise +

AntiSpyware Enterprise

8.8.0

(8.8.0.1804)

Build date: 3/31/2017

Scan engine version (32-

bit)

5900.7806

Scan engine version (64-

bit)

5900.7806

DAT version 8872.0000 DAT Created on: 4/23/2018

Buffer Overflow and

Access Protection DAT

version

750


5.2 CIMEDIT/CIMVIEW

CimLayout Configuration

DE17241

GE Digital 184

SF-00428593

When configuring child screen placement in CimLayout, if the "Resize Weight" field is set to "Both", then the "Location" value will not have an impact on the screen placement. Also, the field will be read-only and user will not be allowed to make any modifications to it.


5.3 DEVICE COMMUNICATIONS

CIMPLICITY OPC Server

RALLY-DE6066 Case-1-4008767351 SF-00178869

In previous versions, the project name was optional when dealing with item IDs used by an OPC Client. In CIMPLICITY V8.2 and higher, when using point by address for the project ID must be included.

Project Point Item ID Project point item ID syntax is: \\PROJECT\POINT.ATTRIBUTE

Field Description

PROJECT Required A CIMPLICITY project name under which the reference is made.

Important: When using point by address for the item IDs used by an OPC Client, the project ID must be included.

POINT Required The name of a CIMPLICITY project point.

ATTRIBUTE Required A server-defined string specifying the type of information associated with the point. A point has several attributes.

Point by Address Item ID Syntax Point by address item ID syntax is \\PROJECT\@DEVICE=xxx|ADDR=yyy|[TYPE=zzz]

Note: [ ] indicates that the entry is optional.

Keyword/Field Description

PROJECT Required A CIMPLICITY project name under which the reference is made.

Important: When using point by address for the item IDs used by an OPC Client, the project ID must be included.

DEVICE Required Any valid CIMPLICITY device identifier.

ADDR Required A valid device address for the specified device.

TYPE Optional Any valid CIMPLICITY point type.

Default INT

SCAN Optional Multiple of the device scan rate at which the data will be collected.

Default 1

OFFSET Optional Bit offset for the address of BOOL, BYTE or WORD points

Default 0

ACCESS Optional Either READ or WRITE.

Default READ

GE Digital 185

Keyword/Field Description

ELEM Optional The number of elements (for an array).

Default 1

ORIGIN Optional The point's origin - use one of the following:

ORIGIN Point Type

DEV Device

DIA Diagnostic

ALW Ethernet Global Data

Default DEV


5.4 LOGGING

Database Logger/Microseconds Database Logger provides microsecond support. However, adding microsecond resolution can only be stored in a database that has a column configured to handle microseconds. If you have a database that is older, you must manually update and/or recreate it to include a microsecond column. Note: SQL Server 2008 is the minimum SQL Server version that provides microsecond support.


5.5 NETWORKING

WebView and 64-Bit Browsers (For 64-bit operating system users) WebView will not run in a Native 64-bit browser. CIMPLICITY applications that run in WebView, such as CimView, are 32-bit applications and will only run in WOW mode supported applications such as Internet Explorer 32-bit.


5.6 POINTS AND SCRIPTING

Batch Point Operations CIMPLICITY uses SavePointBatch and DeletePointBatch, which can optimize doing many add or

remove point operations in scripts. Important: When a point operation involves a point batch, the batch lives in memory. As a result, the larger the batch, the more memory is consumed (e.g. 100,000 points would end up ramping the process memory up into the gigabytes). When batches are in smaller, more efficient sizes, adding and/or deleting points using batch operations are faster in CIMPLICITY v9.0 than they were in CIMPLICITY v8.2. Long Point IDs

GE Digital 186

➢ To work with the CIMPLICITY v9.0 both the Server and the Viewer need to have CIMPLICITY v9.0 installed.

➢ Consult the documentation for any third party products being used. ➢ Make sure any renamed points are renamed wherever they exist in CIMPLICITY v9.0 features.

GE Digital 187

BlinkFill Sample Scripts DE6829 Case-1-3909839549 SF-00178790 Following are sample scripts for the sample script, BlinkFill.

Notes

➢ Object types, DGefBlinkLineFormat and DGefBlinkFillFormat, which were added in

CIMPLICITY v8.2 SIM 27 for supporting blink animation, are included in these samples. ➢ These changes were made for the issue CIMP-6053; Case-1-3382418752.

GefBlinkFillFormat (object) Represents the attributes of the blink interior portion of an object,

Parameter Details

Description: The format is only applied if the AnimatesBlinkFill property is true.

Example

Sub ExprListAnimElement_GetBlinkFill() Dim oCimExprListAnim As GefExprListAnim Dim oCimExprListAnimElmt As GefExprListAnimElement Dim oCimFillFmt As GefBlinkFillFormat Set oCimExprListAnim = CimGetObject.ExprListAnim Set oCimExprListAnimElmt = oCimExprListAnim.Add oCimExprListAnimElmt.Expression = "1" oCimExprListAnimElmt.AnimatesBlink = True oCimExprListAnimElmt.AnimatesBlinkFill = True Set oCimFillFmt = oCimExprListAnimElmt.GetBlinkFill(True) oCimFillFmt.Solid oCimFillFmt.ForeColor.RGB = &HBB& 'red CimGetScreen.Refresh False End Sub

Properties: Application , BackColor , ForeColor , GradientColorType , GradientDegree , GradientShades , GradientStyle , GradientVariant , Parent , Pattern , Type Methods: None , OneColorGradient , Patterned , Solid , TwoColorGradient

Note: GefBlinkFillFormat is similar to GefFillFormat, look into GefFillFormat for other

examples.

GE Digital 188

GefBlinkLineFormat (object) Represents the attributes of the blinkline portion of an object.

Parameter Details

Description: The GefBlinkLineFormat object represents the attributes of the Blink Line configuration

of an object.

Example

Sub ExprListAnimElement_GetBlinkLine() Dim oCimExprListAnim As GefExprListAnim Dim oCimExprListAnimElmt As GefExprListAnimElement Dim oCimObjLineFmt As GefBlinkLineFormat Set oCimExprListAnim = CimGetObject.ExprListAnim Set oCimExprListAnimElmt = oCimExprListAnim.Add oCimExprListAnimElmt.Expression = "1" oCimExprListAnimElmt.AnimatesBlink = True oCimExprListAnimElmt.AnimatesBlinkLine = True Set oCimObjLineFmt = oCimExprListAnimElmt.GetBlinkLine(True) oCimObjLineFmt.DashStyle = gefLineSolid oCimObjLineFmt.ForeColor.RGB = &HBB& 'red CimGetScreen.Refresh False End Sub

Properties: Application , DashStyle , ForeColor , Parent , Weight

Note: GefBlinkLineFormat is similar to GefLineFormat, however following properties are not

supported ➢ BeginArrowheadLength , BeginArrowheadStyle , BeginArrowheadWidth

➢ EndArrowheadLength , EndArrowheadStyle , EndArrowheadWidth

Please review GefLineFormat topics in the CIMPLICITY documentation for other examples.


GE Digital 189

5.7 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 4.8.259 (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 4. 2. Proficy WebSpace Compatibility Update 4: Proficy WebSpace Compatibility Update 4 (64 bit):

PWS48_CompatibilityUpdate_004_x64. The recommendation is to install WebSpace 4.8.259, 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 190

6 SPECIAL INSTRUCTIONS

NONE.


GE Digital 191

7 CONTACT GE DIGITAL

Visit us on the World Wide Web at http://www.ge.com/digital/ For GE Digital Sales and Marketing information please call 1-800-433-2682 For GE Digital Technical Support please call 1-800-433-2682 Submit a technical question via the web at: http://digitalsupport.ge.com

Technical Support E-mail: [email protected] Go to: Table of Contents

http://www.ge.com/digital/

http://digitalsupport.ge.com/

mailto:[email protected]

cimplicity 9.0 important product information

Documents