Why PXIe-4133 Lock on Trigger Line After Forcefully Terminated

Updated May 29, 2026

Reported In

Issue Details

In our test architecture, the test program relies on ni4133_ConfigurePulseEvent to export events to PXI_Trig0 in order to synchronize with other instruments.

However, when the automated test software crashes or is forcefully terminated, the device driver continues to hold control of the PXI_Trig0 trigger line, which is in a locked state.

When the test software is restarted, PXI_Trig0 remains occupied, preventing subsequent test runs from using the trigger line for synchronization and thereby causing inter-instrument synchronization failures.

Solution

It is expected behavior that the PXIe‑4133 does not properly execute ni4133_Close to release its resources when the automated test software crashes or is forcefully terminated.
To recover and release the occupied trigger line, please restart the NI PXI Resource Manager service from an administrator‑privileged command prompt. This action is sufficient to restore the trigger line to a usable state.

net stop "NI PXI Resource Manager"

net start "NI PXI Resource Manager"

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums

Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.