DISCLAIMER
The example below is intended to demonstrate one or more features or methods and is presented as a configuration example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.
Sometimes it is necessary to import historic data to ClearSCADA points. Several methods exist in the Historic aggregate class for that. The ones we are going to discuss in this article are: LoadDataValue, LoadDataValues, LoadDataFile.
Below a brief description on how those methods can be used:
LoadDataValue
LoadDataValue( Reason{BYTE.EN_US},
Quality{LONG.EN_US},
Timestamp{TIME.EN_US},
Value{VARIANT.EN_US} )
Values for Quality parameter (ClearSCADA uses standard OPC HDA quality definitions), e.g.:
LoadDataValues
LoadDataValues( Value{Array of Variant},
Timestamp{Array of Time},
Quality{Array of Long},
Reason{Array of Byte} )
Same as LoadDataValue except the parameters passed in are arrays instead of single values. A maximum of 5,165 elements are allowed in the arrays, otherwise an error will be raised.
The Reason argument is optional - when omitted defaults to 0 (Current Data).
LoadDataFile
LoadDataFile( FileName{STRING.EN_US} )
The LoadDataFile method takes a filename as its single parameter. This is the name of a local CSV on the main server. Some points to note about the files to be imported:
- LoadDataFile is much faster at importing records than LoadDataValues.
- You can invoke the methods from scripts, ST logic programs or external tools by using Automation Interface or .NET API.
The example below is intended to demonstrate one or more features or methods and is presented as a configuration example only. Schneider Electric assumes no liability for the use or application of this example or any portion thereof.
Sometimes it is necessary to import historic data to ClearSCADA points. Several methods exist in the Historic aggregate class for that. The ones we are going to discuss in this article are: LoadDataValue, LoadDataValues, LoadDataFile.
Below a brief description on how those methods can be used:
LoadDataValue
LoadDataValue( Reason{BYTE.EN_US},
Quality{LONG.EN_US},
Timestamp{TIME.EN_US},
Value{VARIANT.EN_US} )
Values for Quality parameter (ClearSCADA uses standard OPC HDA quality definitions), e.g.:
- 0 = Bad
- 64 = Uncertain
- 192 = Good
- 0 = Current Data
- 1 = Value Change
- 2 = State Change
- 3 = Timed Report
- 4 = End of Period
- 5 = End of Period Reset
- 6 = Override
- 7 = Release Override
- 8 = Modified/Inserted
LoadDataValues
LoadDataValues( Value{Array of Variant},
Timestamp{Array of Time},
Quality{Array of Long},
Reason{Array of Byte} )
Same as LoadDataValue except the parameters passed in are arrays instead of single values. A maximum of 5,165 elements are allowed in the arrays, otherwise an error will be raised.
The Reason argument is optional - when omitted defaults to 0 (Current Data).
LoadDataFile
LoadDataFile( FileName{STRING.EN_US} )
The LoadDataFile method takes a filename as its single parameter. This is the name of a local CSV on the main server. Some points to note about the files to be imported:
- Each line of the CSV file specifies a single record and has the format: YYYY,MM,DD,HH,MM,SS,Value
- The file must be in ANSI format.
- To insert comments into the file, start the line with a semi-colon.
- Time stamps must be in chronological order, from older to newer.
- Reason is set to 0 (Current Data) on import.
- LoadDataFile is much faster at importing records than LoadDataValues.
- You can invoke the methods from scripts, ST logic programs or external tools by using Automation Interface or .NET API.
Publicado para:Schneider Electric Mexico
