Goose data are not appearing in Grafana

logesaustralia · July 29, 2020, 6:31am

Hi,

Please find my analysis and queries, please review them and clarify.

PMU data (IEC 61850-90-5) is streaming data continuously. Whereas goose data is arriving based on events (e.g. open/close).

Below logic is implemented in openHistorian’s Grafana Service to fetch the PMU data:

• Grafana UI is requesting data for specific interval (e.g last 5 mins data).
• openHistorian Grafana service is calculating the data resolution for given interval using some
calculations.

Sample code:

long range = (stopTime - startTime). Ticks;

if (range <= TimeSpan.TicksPerHour && !measurementIDs.Any(measurementID => (metadata.TryGetValue(measurementID, out row) ? int.Parse(row[“FramesPerSecond”].ToString()) : 1) > 1)) return Resolution.Full;

if (range <= Ticks.PerMinute) return Resolution.Full;
if (range <= Ticks.PerMinute * 5L) return Resolution.TenPerSecond;
if (range <= Ticks.PerMinute * 30L) return Resolution.EverySecond;
if (range <= Ticks.PerHour * 3L) return Resolution.Every10Seconds;

When Grafana requesting data for specific time interval, resolution always falling like Resolution.TenPerSecond or Resolution.Every10Seconds with respective of interval length (ticks).

Once resolution is calculated then Grafana service is fetching the data from Historian data service and return them to Grafana UI.

According to Goose data, resolution must be “Full”, because Goose data will not fall under any variations or interval like TenPersecond or EverySecond.

My Queries:

Is there any possibility to identify whether this measurement id is belonging to goose device?

Or

Is there any way to access openHistorian database from “OpenHistorian.Adapters”?
Specifically, TrendValueAPI.cs file.

ritchiecarroll · July 29, 2020, 7:33pm

From within Grafana for this lower resolution data I would use the Interval function with a value of zero:

github.com

GridProtectionAlliance/gsf/blob/master/Source/Documentation/GrafanaFunctions.md#interval

# GSF Grafana Functions

The Grafana interfaces defined in the Grid Solutions Framework allow for aggregation and operational functions on a per-series and per-group basis. The following defines the [available functions](#available-functions) and [group operations](#group-operations) that are available for a data source implementing the GSF Grafana interface, e.g., [openHistorian](https://github.com/GridProtectionAlliance/openHistorian). Note that any data source that implements the [GrafanaDataSourceBase](https://github.com/GridProtectionAlliance/gsf/blob/master/Source/Libraries/Adapters/GrafanaAdapters/GrafanaDataSourceBase.cs) class will automatically inherit this functionality.

## Series Functions

Various functions are available that can be applied to each series that come from a specified expression, see full list of [available functions](#available-functions) below. Series expressions can be an individual listing of point tag names, Guids or measurement keys separated by semi-colons - or - a [filter expression](https://github.com/GridProtectionAlliance/gsf/blob/master/Source/Documentation/FilterExpressions.md) that will select several series at once. Filter expressions and individual points, with or without functions, may be selected simultaneously when separated with semi-colons:

* Example: `PPA:15; STAT:20; SetSum(Count(PPA:8; PPA:9; PPA:10)); FILTER ActiveMeasurements WHERE SignalType IN ('IPHA', 'VPHA'); Range(PPA:99; Sum(FILTER ActiveMeasurements WHERE SignalType = 'FREQ'; STAT:12))`

Many series functions have parameters that can be required or optional &ndash; optional values will always define a default state. Parameter values must be a constant value or, where applicable, a named target available from the expression. Named targets are intended to work with group operations, i.e., [Set](#set) or [Slice](#slice), since group operations provide access to multiple series values from within a single series. The actual value used for a named target parameter will be the first encountered value for the target series &ndash; in the case of slice group operations, this will be the first value encountered in each slice. Named target parameters can optionally specify multiple fall-back series and one final default constant value each separated by a semi-colon to use when the named target series is not available, e.g.: `SliceSubtract(1, T1;T2;5.5, T1;T2;T3)`

To better understand named targets, follow these example steps:

 1. The following expression produces two unwrapped voltage phase angle series:

    [`UnwrapAngle(DOM_GPLAINS-BUS1:VH; TVA_SHELBY-BUS1:VH)`](#unwrapangle)

 2. Values from one of the series can now be substracted from values in both of the series at every 1/30 of a second slice:

This file has been truncated. show original

logesaustralia · August 3, 2020, 5:12am

Hi Ritchie,

I was trying to configure the Grafana GSF function, but I’m getting “Invalid request error” in browser.

I tried below
My Goose Measurement ID is “ABC_GOOSE-DV1”
This data will be occurring randomly, not sequential manner.

Time duration : Last 6 hours
Interval function
Interval(0,NanoSecond, ABC_GOOSE-DV1)

Can you please provide me a sample interval function to handle this scenario?
Basically I need to pull all goose data without any interval for this Measurement ID (ABC_GOOSE-DV1).

Please help.

Note that, I put “NonoSecond” as least option. I don’t want any interval, need full data.

Thanks & Regards
Logu

logesaustralia · August 4, 2020, 10:39pm

Hi Ritchie/Stephen,

Please help on this. This is my urgent requirement.

Regards
Logu

ritchiecarroll · August 5, 2020, 2:49am

What happens when you try this:

Interval(0, ABC_GOOSE-DV1)

logesaustralia · August 5, 2020, 3:31am

Hi Ritchie,
I tried below expression, no response. However looks like this expression is not correct. Please confirm
Goose Intervel1

Also I tried with Nano second, I got below error in code level.
GooseInterval with Nonosecond

Thanks & Regards
Logu

ritchiecarroll · August 5, 2020, 1:35pm

Try switching to “Type: Text Editor” and entering the text directly as it does not look like it’s picking up the function correctly in the “Element List” picker expression.

logesaustralia · August 6, 2020, 4:21am

Hi Ritchie,

thanks for your information, its working fine.

Thanks & Regards
Logu