ClearSCADA 2007 R1 Known Issues

[sbeadle1]

📖 Home  Back  
Please read the information below prior to upgrading to ClearSCADA 2007 R1 for important information on changes in this version and any known issues.

• Business Objects have released Crystal Reports XI Developer Edition Release 2. This version is compatible with ClearSCADA 2007 R1. If you wish to edit any report, you MUST use Crystal Reports XI Release 2. This is available as a free upgrade to Crystal Reports XI Release 1 from the Business Objects website for those customers owning Crystal Reports XI Release 1. You cannot use Release 1 to edit reports in ClearSCADA 2007 R1.

• Context-sensitive help will not work when the ClearSCADA 2007 R1 server is emulating a previous version.

• User favorites cannot be exported from ClearSCADA 2007 R1 to previous versions due to a change in format to support the new super favourites feature.

• Previous versions of ClearSCADA would allow logic programs and scripts to modify properties of objects in template instances even if the property override on that property would not normally allow the change. This would then result in template instance database integrity errors. In ClearSCADA 2007 R1, the product has been modified such that logic programs and scripts can only change these properties if the property override allows it. This may mean that programs that worked in earlier builds will not work correctly in this version. Property overrides will need to be modified to allow the programs to continue to work properly once this new version is installed.

• The way system commands are executed has changed in ClearSCADA 2007 R1. When upgrading to this release, you must configure the username and password for system commands in the server config tool otherwise the system commands will not run.

• Due to changes for Windows Vista, the configuration files for ViewX have changed location. See ClearSCADA 2007 R1 Changes To File Locations for specific details. This means that previously where only 1 file had to be managed per machine now multiple files need to be managed and new logon sessions catered for. For example if a standard "ViewX Global Settings.dat" is used on machines and is copied by administrators to all machines to ensure consistency then now multiple files need to be copied to multiple user directories. When a new user is created then the file needs to also exist in the "Default User" (if Vista works that way) so when the new user gets a copy of the directory they also get the correct settings files.

• Due to the changes in file locations, there can be problems if you downgrade from ClearSCADA 2007 R1 to ClearSCADA 2007 R0. In ClearSCADA 2007 R0 and earlier versions, the path lengths are restricted to 64 characters, this is not the case in ClearSCADA 2007 R1. When a server is downgraded, the file locations can get truncated, resulting in the server not running correctly. It is recommended that on a downgrade that the file locations are manually checked to ensure that they are shorter than the 64 character limit and altered as necessary.

• ClearSCADA 2007 R0 contained a bug, where it allowed mimic parameters to contain special characters. Mimic parameters containing special characters are inaccessible to client side scripts. ClearSCADA 2007 R1 has been fixed to disallow special characters in mimic parameters, ensuring that any parameter created by a user can be accessed by a script.

• Registry settings for client application are now stored in HKEY_CURRENT_USER instead of HKEY_LOCAL_MACHINE. The main settings affected by this are the ViewX & DBClient log file settings, and the ViewX/Mimics key used by mimic animations & pick actions. These settings will be reset to defaults on an upgrade.

• On Windows Vista, the following programs require Administrator rights and will give a UAC prompt when run interactively:

• DBServer

• All drivers

• ClearSCADA Client (Control Panel)

• Service Manager

• AE Printer

• Licence Server

• Port Server

• Demo

• All other programs (ViewX, Server Icon, Server Status, Server Config, SCXCmd) all run as a standard user. Note that attempting to start DBServer from the system tray icon will give a UAC prompt.

• On a clean install on Windows Vista, ViewX will not be able to create a default system when it is first run, unless it is run as Administrator. In this case, or if there is no server running on the local machine, the ClearSCADA Client control panel applet will be displayed.

• Similar to issues with logic and scripts being allowed to write to non-overridden properties in template instances, previous versions of ClearSCADA would allow the Flow Run objects configuration to be read even if the property overrides on the Flow Run would not normally allow this. In ClearSCADA 2007 R1, the product has been modified such that a 'Read Configuration' may only be executed if the property override allows it. This may mean that Flow Run objects that were able to perform a 'Read Configuration in earlier builds will not work correctly in this version. Property overrides will need to be modified to allow the 'Read Configuration to continue to work properly once this new version is installed. Currently if the upload fails due to fields not having property overrides enabled, then up to 3 event journal messages will be logged. One for general flow run configuration fields that could not be updated, one for compressibility calculation fields that could not be updated and one for flow calculation fields that could not be updated. These event journal messages will indicate which specific fields in those areas that do not have property overrides.  It should also be noted that if the uploaded field does not have a property override and the value is the same as the database it will not be reported as a failure.  The fields that need to have property override enabled on them are as listed below (all items with 'Yes' written in the 'Uploaded' column).

Flow Run Object Fields

Name	Uploaded
AlarmLogScanInterval	No
AlarmLogScanOffset	No
AlarmLogSeverity	No
AllowAutoReadOfConfig	No
AreaOfInterest	No
AreaOfInterestId	No
Confirm	No
ContractBasePressure	Yes
ContractBaseTemp	Yes
ContractHour	Yes
ContractUnits	Yes
ContractWetGasMeterFact	Yes
CurrentScanInterval	No
CurrentScanOffset	No
DailyHistScanInterval	No
DailyHistScanOffset	No
EventLogScanInterval	No
EventLogScanOffset	No
EventLogSeverity	No
FlowRunConfigScanInt	No
FlowRunConfigScanOffset	No
FlowRunId	Yes
FlowRunNumber	No
HourlyHistScanInterval	No
HourlyHistScanOffset	No
HysteresisUnits	Yes
InputUnits	Yes
InService	No
LowFlowEvents	Yes
OutstationId	No
ReadConfigAtStartup	No
Severity	No
Source	No
SourceName	No
StaticPresAltitude	Yes
StaticPresAtmospheric	Yes
StaticPresInputReg	Yes
StaticPresInputType	Yes
StaticPresLatitude	Yes
StaticPresLocation	Yes
StaticPressureType	Yes
StaticPresTapLocation	Yes
StatPresEngAtFullScale	Yes
StatPresEngAtZeroScale	Yes
StatPresRawAtFullScale	Yes
StatPresRawAtZeroScale	Yes
TempEngAtFullScale	Yes
TempEngAtZeroScale	Yes
TempInputReg	Yes
TempInputType	Yes
TempRawAtFullScale	Yes
TempRawAtZeroScale	Yes

AGA8 Fields

Name	Uploaded
Argon	Yes
CarbonDioxide	Yes
CarbonMonoxide	Yes
CompositionUnits	No
ConfigurationEvents	Yes
EthaneC2H6	Yes
HeatingValue	Yes
Helium	Yes
HexanesPlus	Yes
HexanesPlusnDecane	Yes
HexanesPlusnHeptane	Yes
HexanesPlusnHexane	Yes
HexanesPlusnNonane	Yes
HexanesPlusnOctane	Yes
HexanesPlusRatios	Yes
Hydrogen	Yes
HydrogenSulfide	Yes
iButane	Yes
iPentane	Yes
MethaneCH4	Yes
nButane	Yes
nDecane	Yes
nHeptane	Yes
nHexane	Yes
Nitrogen	Yes
nNonane	Yes
nOctane	Yes
nPentane	Yes
Oxygen	Yes
PropaneC3H8	Yes
RelativeDensity	Yes
Source	Yes
Water	Yes

NX-19 Fields

Name	Uploaded
CarbonDioxide	Yes
ConfigurationEvents	Yes
HeatingValue	Yes
Nitrogen	Yes
SpecificGravity	Yes

AGA-3 (1985 & 1992)

Name	Uploaded
BetaRatio	Sort of. This is calculated from orifice and pipe diameter fields. Field is read only.
ChamberType	Yes
DiffPressureDeadband	Yes
IsentropicExponent	Yes
OrificeDiameter	Yes
OrificeMaterial	Yes
OrificeMeasurementTemp	Yes
PipeDiameter	Yes
PipeMaterial	Yes
PipeMeasurementTemp	Yes
StaticPressureDeadband	Yes
TemperatureDeadband	Yes
Viscosity	Yes

AGA-7

Name	Uploaded
KFactor	Yes
LowFlowDetectTime	Yes
LowFlowPulseLimit	Yes
MFactor	Yes
TurbineInputRegister	Yes
TurbineInputType	Yes

V-Cone

Go: Home Back

Name	Uploaded
Coefficient1	Yes
Coefficient10	Yes
Coefficient2	Yes
Coefficient3	Yes
Coefficient4	Yes
Coefficient5	Yes
Coefficient6	Yes
Coefficient7	Yes
Coefficient8	Yes
Coefficient9	Yes
ConeDiameter	Yes
ConeMaterial	Yes
ConeMeasurementTemp	Yes
FlowCoefficents	Yes
IsentropicExponent	Yes
PipeInsideDiameter	Yes
PipeMaterial	Yes
PipeMeasurementTemp	Yes
ReynoldsNumber1	Yes
ReynoldsNumber10	Yes
ReynoldsNumber2	Yes
ReynoldsNumber3	Yes
ReynoldsNumber4	Yes
ReynoldsNumber5	Yes
ReynoldsNumber6	Yes
ReynoldsNumber7	Yes
ReynoldsNumber8	Yes
ReynoldsNumber9	Yes
Viscosity	Yes