[BUG] PinSiteData not listing all sites for a pin that shares a digital resource

[swuwu15]

Describe the bug
When having a digital pin defined as:

Connection pin="PinA" siteNumber="0,1" instrument="HSD_P174" channel="0"
Connection pin="PinA" siteNumber="2,3" instrument="HSD_P114" channel="0"

The PinSiteData object returned from performing a measurement operation only contains 2 of the active 4 sites defined.

To Reproduce
Steps to reproduce the behavior:

1. Define a DUT pin that has multiple sites sharing a digital resource

   

2. Obtain the DigitalSessionsBundle object associated to that pin

   

3. Perform a measurement that returns a PinSiteData Object and inspect it

   

Expected behavior
Even tho its understood that the instrument session for shared resources will only contain a single PinSetString (single resource for both sites), it is believed that the PinSiteData object should still list all active sites (e.g show repeated data for the shared instrument sites).

System Setup(please complete the following information):

• STS Software Version: 24.5.2
• Hardware: Virtual Machine
• Instrumentation: PXIe-6571

NI Support Status
Has this issue been reviewed separately by NI Support team member? No.

Additional context
Costumer is using shared resources to perform board checkers in grouped sites.

[github-actions]

Thank you for posting, the NI development team has been notified and a corresponding work item has been created internally. The team will review and reply back if any further clarification is required.

[Mattjet27]

As my my response to you in issue #174 stated, Shared Pins (i.e. a pin mapping the same instrument channel to multiple sites) is not currently supported. That was a general statement, it was not specific to DCPower and applies to all instrument types. However, the good news is that this is something we are actively working on and should have available within our next release (v25.5). Therefore, this would appear to be a duplicate bug for the same underlying issue we are already away of and are working on. I will now close this issue and mark it as a duplicate.