nidigital_spi example returns errors when the service and TestStand sequence are in different directories

[bkeryan]

Bug Report

The nidigital_spi example resolves file paths differently in the service vs. the TestStand code module:

• The service resolves file paths with respect to the service directory.
• The TestStand code module resolves file paths with respect to the TestStand search paths, including the directory containing the sequence file.

If you statically register the example by copying it from the measurementlink-python Git repo to C:\ProgramData\National Instruments\MeasurementLink\Services\nidigital_spi, then the TestStand sequence in C:\ProgramData works but the TestStand sequence in the measurementlink-python Git repo fails.

Repro or Code Sample

Run python scripts\install_examples.py.
Cd to C:\dev\measurementlink-python\examples\nidigital_spi and run poetry install to create a virtualenv for the TestStand code module.
Open C:\dev\measurementlink-python\examples\nidigital_spi\NIDigitalSPI.seq in TestStand and run it.

Expected Behavior

The sequence passes.

Current Behavior

The sequence fails with this error:

Error executing substep 'Post'.
Exception calling application: -1074118557: The specified levels or timing sheet name was not found. Ensure that you load levels and timing sheets before you applying them.

Device: DigitalPattern1
Levels Sheet: C:\ProgramData\National Instruments\MeasurementLink\Services\nidigital_spi\PinLevels.digilevels

This is because the TestStand code module loaded C:\dev\measurementlink-python\examples\nidigital_spi\PinLevels.digilevels, not C:\ProgramData\National Instruments\MeasurementLink\Services\nidigital_spi\PinLevels.digilevels.

Your Environment

• OS & Device: Windows 10
• ni-measurementlink-service version: 1.0.1
• MeasurementLink version: 2023 Q2
• Python version: 3.9

AB#2381210