PXI

cancel
Showing results for 
Search instead for 
Did you mean: 

NI MAx and Resource Manager Algorithm

We're trying to add a new resource to NI MAX according to the PXIe spec (PXI Express Software Specification).

As far as I understand the NI resource manager should comply to this

Accordingly to chapter 3.5.1

ingdb_0-1726486282392.png

We managed so far that our dll is loaded but no call to API is done. A call to our dll with Python and ctypes is working. Do we miss some additional configuration in NI MAX?

 

In detail we did that:

We have placed our registry entry under PXISA\Services\System Modules\<our vendor name>\<our product name>.

We have built test 32bit DLL, which contains corresponding exported functions: PXISA_SystemModule_GetCount, PXISA_SystemModule_GetName, PXISA_SystemModule_GetInformation, PXISA_SystemModule_GetChassisEEPROM, PXISA_SystemModule_SMBusOperation.
And we see from Process Monitor utility, that NI Resource manager indeed reads registry entry and loads our DLL. It is confirmed by our custom logging inside the DLL.
We expect, that at least PXISA_SystemModule_GetCount should be called on this step, but that does not happen.

Thanks for any hints or tips

0 Kudos
Message 1 of 1
(125 Views)