Moved to unplanned until #981 is planned for fix.

NI-Digital now supports multi-instrument sessions. This is the recommended usage. So we won't add niDigital_EnableMatchFailCombination to nidigital anymore.

NI-Digital now supports multi-instrument sessions which handles the NI-Sync driver internally. This is the recommended usage. So we won't add niDigital_EnableMatchFailCombination to nidigital anymore.

It's actually NI-TClk that's handled internally by the multi-instrument session. Whether using a multi-instrument session or multiple individual sessions NI-Sync will be called by the NI-Digital API, but opening and closing the NI-Sync session is still handled by the NI-Sync API.

Whether using a multi-instrument session or multiple individual sessions with NI-TClk, niDigital_EnableMatchFailCombination is still the entrypoint that a user would call to do whatever it does. There is no alternative entrypoint, so I'm reopening this.

We should maybe only support calling it from a multi-instrument session, though.

Note that this function still wouldn't be useful without a way to open an NI-Sync session, so it will remain unplanned, for now.

@ni-jfitzger Here is a potential workaround for the NI-Sync session:

https://github.com/ni/miv-examples/tree/main/src/NI-SyncPython

A pre-release version of an official nisync API was published.
https://pypi.org/project/nisync/