Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance.
When viewing a meter consumption report, the values shown in the report does not match the values in the extended trendlog in SmartStruxure
SmartStruxure 1.5 and below
Generally this will happen if the meter is reset and that time the last value of that meter will set a BaseValue. To calculate the total consumption of the meter we are adding the BaseValue to the offset.
This means that the value shown will be the logged value + the offset.
In some cases however you would want to completely reset the log and just show the same values that are represented in the extended trendlog.
It has been identified, that a defect causing a trend logging a 0 after each restart triggers this reset. Request the latest hotfix for 1.5 from Product Support in order to avoid this happening in the future.
Note: This issue (Defect #26360) has been fixed in 1.6.1 release.
1. Open "SQL Management Studio" and connect to the database "StruxureWareReportsDB"
2. Locate the log you want to reset using this query:
SELECT * FROM tbLoggedEntities
3. Note the ID of the log you want to reset
4. Reset the log using the following query, replacing xxxx with the ID of the log
DECLARE @id INT
SET @id = xxxx
UPDATE tbLoggedEntities SET BaseValue = 0 WHERE ID = @id
UPDATE tbLogTimeValues SET FloatValue = OdometerValue WHERE ParentID = @id
##WARNING## The above script will reset BaseValue to 0 this may impact on any previous Meter Readings. Please contact Product Support to discuss this if you have concerns before applying this script.