Hello NI Community,
I am experiencing persistent VISA communication issues with my setup, which includes NI-MAX and LabVIEW 2013. I have already gone through several troubleshooting steps, including uninstalling and reinstalling drivers, but the problem remains unresolved.
Problem Description:
1. Error in NI-MAX:
- In NI-MAX, under "Devices and Interfaces," there is a warning with a yellow exclamation mark labeled "VISA Warning."
- When I open the VISA Test Panel for any device, I receive the following error:
"VISA: (Hex 0xBFFF0011) Insufficient location information or the device or resource is not present in the system."
- This issue also appears: VISA Warning: 0x3FFF0077 in NI Measurement & Automation Explorer
2. Error in LabVIEW:
Troubleshooting Steps Taken:
1. Driver Reinstallation:
- I have uninstalled and reinstalled various drivers, including NI-VISA, NI-488.2, and NI-DAQmx.
- I followed the proper steps to ensure a clean installation, including rebooting the system after each step.
2. Closed and Reopened COM Ports:
- I closed all COM ports via the Device Manager and restarted the system.
3. Checked VISA Properties in NI-MAX:
- I noticed a new "VISA Properties" tab in NI-MAX with a field for "VISA Alias on My System," which is currently empty. I am not sure if this is relevant to the issue.
Additional Information:
- The problem maybe started occurring after a recent Windows update. Could this update have caused the issue?
- I have verified that all physical connections are secure and correct.
- The GPIB Analyzer in NI-MAX shows a disabled NDAC line, which might indicate a communication problem.
Request for Assistance:
1. Could the recent Windows update be responsible for these VISA communication issues?
2. Are there any additional steps or specific settings I should check in NI-MAX or LabVIEW to resolve this issue?
3. Is there a recommended procedure for thoroughly troubleshooting and resolving this kind of VISA error?
Thank you very much for your help! I have spent the past two full days reading through forums, and a colleague who is an expert mentioned that when this type of driver issue occurs, sometimes he has had to resort to formatting the computer. I would really like to avoid such a drastic measure.
