# Conflicting Acronyms in Web Manager

**URL:** <http://discussions.gridprotectionalliance.org/t/conflicting-acronyms-in-web-manager/1454>\
**Category:** openHistorian\
**Created:** [October 27, 2025, 7:31am UTC](http://discussions.gridprotectionalliance.org/t/conflicting-acronyms-in-web-manager/1454 "2025-10-27T07:31:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vishnu\_S\_Nair](http://discussions.gridprotectionalliance.org/user_avatar/discussions.gridprotectionalliance.org/vishnu_s_nair/32/1615_2.png) [@Vishnu\_S\_Nair](http://discussions.gridprotectionalliance.org/u/Vishnu_S_Nair)\
**Post date:** [October 27, 2025, 7:31am UTC](http://discussions.gridprotectionalliance.org/t/conflicting-acronyms-in-web-manager/1454/1 "2025-10-27T07:31:48Z")

</div>

I have connected a PMU simulator to openPDC and then connected the openPDC to openHistorian at a different port. The data is being successfully streamed to openHistorian via a PDC instance, under which a PMU device instance is created.

While the PDC and its PMU device have unique acronyms during their set up in the desktop OH manager, the moment I open the PDC instance in the web manager, under input devices, its acronym is set to that of its PMU device, thus showing the same acronym error.

Because of this I feel, i am not able to see the data in the element list in grafana, which is the ultimate issue at hand.

---

<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:** [January 15, 2026, 4:52am UTC](http://discussions.gridprotectionalliance.org/t/conflicting-acronyms-in-web-manager/1454/2 "2026-01-15T04:52:44Z")

</div>

Generally, the openPDC should not allow duplicated acronyms for device names. When using STTP, multiple connections can use a source prefix, here to also ensure uniqueness.

Can you better explain the “same acronym error” you are seeing?
