Daren,
This is expected behavior due to an abnormal termination of your CVI exe when two processes are running (that is, when both your CVI exe and MAX are running) and one of the process is terminated without closing correctly the session to the PXI-4072.
You would get error BFFA4011 if you:
1. Open MAX (process 1) and run an action that opens a session to the PXI-4072 (like Self-Test, Reset, or just expanding "Devices and Interfaces", which opens a session to the DMM to retrieve information from the board, like the calibration information)
2. Run your CVI exe (process 2) and terminate it inapropriately
3. Try to run Self-Test, or Reset, etc in MAX.
Throughout all this time both processes were running so the memory allocated by DMM never gets released appropriately.
You would NOT see this error if you:
1. Run your CVI exe and terminate it inapropriately
2. Try to run again your CVI exe
You will see that under this circumstance you do not get the error saying that the device is already in use by another process.
If you are debugging your CVI exe and you are planning on terminating the application without closing the session appropriately using niDMM_Close, use one of the following options to avoid getting this error:
1. Before terminating your CVI exe let it close the session to the PXI-4072 using niDMM_Close
2. If you terminate your CVI exe without closing the session, make sure you close MAX afterwards. Then you can re-open MAX to run Self-Test, Reset, etc.
3. Make sure MAX is closed before you begin debugging your CVI exe. This way, after you terminate it abnormally (without calling niDMM_Close) you can open MAX and run Self-Test, Reset, etc without getting the BFFA4011 error.
Please reply to this post if you need further assistance. Regards,
Claudia L
DMM R&D
National Instruments