# Source Index difference between openPCD Manager and Protocol Specific settings

**URL:** <http://discussions.gridprotectionalliance.org/t/source-index-difference-between-openpcd-manager-and-protocol-specific-settings/1266>\
**Category:** openPDC\
**Created:** [May 24, 2024, 3:35pm UTC](http://discussions.gridprotectionalliance.org/t/source-index-difference-between-openpcd-manager-and-protocol-specific-settings/1266 "2024-05-24T15:35:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Korunekosama](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/korunekosama/32/708_2.png) [@Korunekosama](http://discussions.gridprotectionalliance.org/u/Korunekosama)\
**Post date:** [May 24, 2024, 3:35pm UTC](http://discussions.gridprotectionalliance.org/t/source-index-difference-between-openpcd-manager-and-protocol-specific-settings/1266/1 "2024-05-24T15:35:04Z")

</div>

Hello,  
In PMU connection Tester ‘Protocol Specific’ Tab, the IEEEC37.118.PhasorDefinition3 (Ia) Index is ‘0’  
 ![image](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/b/bdb658b8fca3ecfa9d98d5e54ec7543679449bd0.png)  
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](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/e/e5a0bcf16514fafe4909042d8e81796884c56d02.png)  
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

---

<div class="post-metadata">

**Author:** ![ritchiecarroll](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/ritchiecarroll/32/2_2.png) [@ritchiecarroll](http://discussions.gridprotectionalliance.org/u/ritchiecarroll)\
**Post date:** [May 24, 2024, 4:05pm UTC](http://discussions.gridprotectionalliance.org/t/source-index-difference-between-openpcd-manager-and-protocol-specific-settings/1266/2 "2024-05-24T16:05:31Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![clackner-gpa](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/clackner-gpa/32/556_2.png) [@clackner-gpa](http://discussions.gridprotectionalliance.org/u/clackner-gpa)\
**Post date:** [January 29, 2025, 8:09pm UTC](http://discussions.gridprotectionalliance.org/t/source-index-difference-between-openpcd-manager-and-protocol-specific-settings/1266/3 "2025-01-29T20:09:02Z")

</div>

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

Hope this helps,  
Christoph

---

<div class="post-metadata">

**Author:** ![Korunekosama](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/korunekosama/32/708_2.png) [@Korunekosama](http://discussions.gridprotectionalliance.org/u/Korunekosama)\
**Post date:** [February 12, 2025, 8:25am UTC](http://discussions.gridprotectionalliance.org/t/source-index-difference-between-openpcd-manager-and-protocol-specific-settings/1266/4 "2025-02-12T08:25:32Z")

</div>

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](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/c/c883bcc9b1f69091da070f8701babb88c8d2819c.png)

![image](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/4/4986c38b1cf37fe51c9fed1933b5979767ab1fca.png)

![image](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/a/a0c6bacf304518b38df7c966e7e19defe5d3d639.png)

Maybe a wrong download link ? The .exe version seems to be the same as in august 2024.  
 ![image](http://discussions.gridprotectionalliance.org/uploads/default/original/2X/a/a1727e15721cce95e30857add0a3a49b58c1c294.png)

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