Issue
When using the Virtual ION Processor to log data, often times the data is logged as a custom quantity under the VIP node name. This can cause problems when creating dashboards, or running reports that look for specific quantity ID's in the ION databases.
Product Line
SturxureWarePower Monitoring Expert 7.x
Power Monitoring Expert 8.x
Power Monitoring Expert 9.0
Power Monitoring Expert 2020
Power Monitoring Expert 2021
Power Monitoring Expert 2022
Power Monitoring Expert 2023
Environment
PME Designer
Cause
The issue is caused by VIP programming that does not follow the Default Measurement Name@Group.Source format when labeling quantities to be logged.
Resolution
*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).
If the values have already been assigned incorrectly, then please see FA233508 for how to reassign a custom quantity logged under the VIP node.
Before creating a framework please see FA233509 for a list of all Default Measurement Labels that can be used. Once the preferred Measurement and Group.Source names are confirmed then follow the procedure below to assign the label.
NOTE: If a measurement is chosen that is already being logged by the assigned source, then a conflict be created that will create "misleading" source names in the database which will prevent the data from being logged under the preferred device. The other measurement either needs to be stopped logging before creating the new measurement or a new measurement label needs to be select for the assignment in the VIP.
When using the Virtual ION Processor to log data, often times the data is logged as a custom quantity under the VIP node name. This can cause problems when creating dashboards, or running reports that look for specific quantity ID's in the ION databases.
Product Line
SturxureWarePower Monitoring Expert 7.x
Power Monitoring Expert 8.x
Power Monitoring Expert 9.0
Power Monitoring Expert 2020
Power Monitoring Expert 2021
Power Monitoring Expert 2022
Power Monitoring Expert 2023
Environment
PME Designer
Cause
The issue is caused by VIP programming that does not follow the Default Measurement Name@Group.Source format when labeling quantities to be logged.
Resolution
*Warning: Take backups of any files prior to modifying them. Ensure the backups are in a location that will not be overwritten (i.e. the Desktop).
If the values have already been assigned incorrectly, then please see FA233508 for how to reassign a custom quantity logged under the VIP node.
Before creating a framework please see FA233509 for a list of all Default Measurement Labels that can be used. Once the preferred Measurement and Group.Source names are confirmed then follow the procedure below to assign the label.
NOTE: If a measurement is chosen that is already being logged by the assigned source, then a conflict be created that will create "misleading" source names in the database which will prevent the data from being logged under the preferred device. The other measurement either needs to be stopped logging before creating the new measurement or a new measurement label needs to be select for the assignment in the VIP.
- Take a backup of the VIP framework files being edited:
- Backup the vip.cfg and vip.bak files located at Install root\Power Monitoring Expert\config\cfg\vip\vip.
- Backup the vip.cfg file located at Install root\Power Monitoring Expert\config\diagram\nd
- Open the VIP in PME Designer and find the module containing the custom quantity label to be reassigned.
- It is suggested that the labels be created in an arithmetic module for organization and error mitigation purposes.
- Rename the label using the Default Measurement Name@Group.Source format.
- Save the changes and exit Designer.
게시 대상: 슈나이더 일렉트릭 Korea
