Source Index difference between openPCD Manager and Protocol Specific settings

GPA Products openPDC
1

Hello,
In PMU connection Tester ‘Protocol Specific’ Tab, the IEEEC37.118.PhasorDefinition3 (Ia) Index is ‘0’
image
To be sure that this ‘remote’ measurement will be related to the ‘Ia’ measurement I declare on my local OpenPDC ; I’m trying to put the ‘0’ value in OpenPDC Manager :
image
Unfortunately, when I’m clicking on ‘save’, the source Index is automatically set to ‘1’ ; even in the database (measurement.PhasorSourceIndex).

Are those two values related ; or are they used to describe two different things ?
Is it possible to have an OpenPDC Manager / Database Source Index value identical to the one specified in PMU Connection Tester ?

Thanks for the help,

Regards

2

Sorry for the confusion there - in the code, the phasor definition is zero-based - but in the modeled configuration, the phasor definition is one-based.

I’ll add a task to update the UI on that screen in the PMU Connection Tester to show a one-based index.

Hope that helps!

Ritchie

1 Like
3

Hi Korunekosama,
We have included this change in the latest nigthlybuild available at: https://gridprotectionalliance.org/nightlybuilds/PMUConnectionTester/Beta/PMUConnectionTester.Installs.zip

Hope this helps,
Christoph

4

Hi Christoph,
Thanks for the change. Unfortunately, it doesn’t seems to have change.
I’ve download the nightly build today and tested it, but the Index value is still ‘0’ in the ConfigFrame2

image
image803×84 8.01 KB

image

image

Maybe a wrong download link ? The .exe version seems to be the same as in august 2024.
image

It’s not very problematic, though: as long as we are aware of this difference in base reference ‘0’ / ‘1’, we can easily make the conversion. The key is simply knowing it.

Regards

Stephane