Warning
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.
Issue
StruxureWare Building Operation Extended trend logs have an incorrect unit associated with the measured value.
Product Line
EcoStruxure Building Operation
Environment
StruxureWare Building Operation 1.3.x
Cause
It is possible to create extended trend logs by selecting multiple trend logs and using the right click option to create extended trend logs. The software incorrectly associates all of the created trend logs with the first trend log object's associated unit even if the other trend logs in the selection use different units.
Resolution
The cause of the problem is resolved in a forthcoming release (1.4.0) however if the system is in the state currently additional steps must be taken.
The method to resolve this problem depends on the need to maintain the existing extended trend log data or not.
1. Accept loss of data
Delete the extended trend logs that have incorrect units and create each extended trend log individually and avoid multiple selections.
2. Avoid loss of data
- Export the trend logs in StruxureWare Workstation.
- Modify the export file and edit the unit value for the Extended trend log
- The unit will need to be validated with another export that contains an object of the correct unit type.
- Example of Units
% - 0x200001
F - 0x280003
no unit - 0x10001
inH20 - 0x230005
ppm - 0x200002
kW - 0x3210001
- Import the modified file and when it detects a naming conflict allow it to rename the Trend log with a "2" notification.
- Stop the data collection on the original trend logs and once the retention levels of the new trend logs meets your site requirements delete the old trend logs with the incorrect data.
Please be aware this issue could impact meter reports from WebReports detailed in Energy Reports not working in 1.3 and earlier