This project has moved. For the latest updates, please go here.

Problem with Meta Data Refresh using GEP

Developer
Sep 19, 2013 at 2:46 PM
We have a Gateway Exchange Protocol setup between two instances of openPDC. The publisher server is running openPDC v1.5.207. The subscriber server is running openPDC v1.5.244.

We have Meta Data Refresh currently enabled on the subscribing server. We get all our PMUs and meta data on this server, except for the ID Codes of the PMUs. All ID codes on the subscriber get set to 0, rather than being set as the ID Code on the publisher server.

Is this a bug? Is this the normal operation of Meta Data Refresh?

Thanks,
Kyle
Coordinator
Oct 14, 2013 at 1:33 PM
Don't think the ID code get transmitted - this is an oversight - we will add this.
Coordinator
Oct 15, 2013 at 8:00 PM
This has been corrected with GSF check-in 87448 (http://gsf.codeplex.com/SourceControl/changeset/87448). It will be rolled into next openPDC build and therefore available in the meta-data.

Thanks,
Ritchie
Marked as answer by ritchiecarroll on 11/1/2013 at 11:38 AM
Developer
Oct 20, 2013 at 10:22 PM
Thanks for the update Ritchie!
Developer
Nov 18, 2013 at 6:41 PM
Is this update available in the openPDC 2.0 RC2?

Thanks,
Kyle
Coordinator
Nov 18, 2013 at 7:04 PM
Yes, it is.
Developer
Nov 25, 2013 at 4:35 PM
Below is the existing Gateway Transport connection string we are using on the subscriber openPDC Server. Can a coordinator please provide an example of how this new change with the ID Codes would be added to the connection string?

transportprotocol=tcp;server=192.168.1.5:6165;islistener=false;interface=0.0.0.0;internal=true;autoConnect=true;bufferSize=2097152;outputMeasurements={FILTER ActiveMeasurements WHERE SourceNodeID IS NOT NULL}

Thanks,
Kyle
Coordinator
Nov 25, 2013 at 4:47 PM
As a result of this change, ID codes are now included by default as part of the metadata exchange. Additionally, ID codes that get transmitted trickle down to the configuration of the systems receiving the data. You should not need to modify your subscriber connection strings.

If your subscribers are not receiving ID codes, you may be overriding the metadata tables in your publisher connection string such that ID code is not being transmitted.

Thanks,
Stephen
Developer
Nov 25, 2013 at 5:18 PM
Thanks Stephen. As we get to testing this in the next month, I will let you know if anything comes up.

Best,
Kyle