The Internet of Things (IIoT) offers unprecedented possibilities for industries. Stay ahead with EcoStruxure™ Plant and Machine.Learn more
...with the EcoStruxure™ Facility Expert (formerly known as Facility Hero) app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
The story behind the Shedd Aquarium, a smart, sustainable facility that connects people to animals, with EcoStruxure™.Discover how
Welcome to the Schneider Electric Global Website×
Goals and Symptoms
Causes and Fixes
Not all sources logged by the data recorder appear when querying the node in the VIP.
Duplicate labels cause a second VIP node to be created named
VIP.<Computer Name>(<Data Recorder Name>~)
Some of the parameters would be logged under this newly created node.
It is possible to query across both nodes to obtain all of the information logged by the particular data recorder affected. However, when doing so, the values read will span two rows since there are two sources (nodes) in the query. See the following screenshot for an example:
In order to correct this problem, there are several methods available:
1. Modify the labels in the VIP such that there are no duplicate labels
2. Edit the query manually and refer to the sources in the SELECT statement but only the host in the FROM clause as shown below:
,"<value>@VIP.CALONGDLSAS02(B15 Daily Log~1)"
FROM --(*vendor(PML),product(LogServer) downstream@VIP.CALONGDLSAS02 *)--
ORDER BY timestamp DESC
(Removed Image URL: /PubResEXPORT.nsf/2b87ee90be777fc085257c28006ee4ef/a2d3999d814ec8e6c125765d00162e3a/fl_block_5/0.1AE4?OpenElement&FieldElemFormat=gif)
All content © 1992-2007 Schneider Electric
Sign up for all the latest solutions, offers and best practices straight to your inbox.
We are excited that you have joined the group. You will receive your welcome email soon describing the program and what to expect in the upcoming weeks. Enjoy!