Currently, a method like PIServer.CreatePIPoints returns AFListResults<String, PIPoint>. Very similarly, PIPoint.FindPIPointsByPath will return AFKeyedResults<String, PIPoint>. The functionality of each result is essentially the same; they even have, for most practical purposes, the same associated properties and methods and thus; they should not be different object types.
Sharing an object type across all of these PIPoint-related functionalities would allow developers to more easily share methods for these related functions (Such as error handling methods).0 votes
Currently, the AFSKD GetValue() method supports GetValue().ValueAsInt32, .ValueAsDouble, and .ValueAsSingle. However, there are other possible AF Value Types, such as "Boolean". The AFSDK should expand the GetValue().ValueAs functionality to include all possible AF Value Types.0 votes
It should be possible to get all nested attribute templates without having to make multiple calls to the Web API.0 votes
We are planning to do this for PI Web API 2018.
When requesting time series data for multiple attributes using a streamset request and the PlotValues endpoint, it would be helpful if the response had the timestamps all lined up. This makes it easier to render the data, particularly if the data is being visualized in a stacked area series.0 votes
This is something we would like to do but the nature of PlotValues makes this difficult to do if not impossible. The PlotValues endpoint returns a time series with the most visually significant values for each pixel on a display. Even though the data values are actual recorded values, the values from different data streams have nothing to do with each other. The timestamps for different streams probably won’t line up.
- Don't see your idea?