05-08-2007 01:11 PM
05-09-2007 01:30 PM
05-10-2007 08:41 AM
Hi Andrew, here is the information you were looking for:
1. There were no changes that I am aware of to the computer. It is a dedicated PC to the above mentioned testing apparatus.
2. The error is getting thrown from the AI Group Config VI (this VI is found within he AI Config VI).
3. I can successfully run a test panel for the PCI-6024E in MAX, All of the channels are measuring correct values. I have manually measured them. I have also tested to make sure the hardware is all working correctly. According to MAX nothing is wrong.
4. As for the Traditional DAQ Virutal Channel info you required, I am not sure how to create a traditional virtual channel or where to find the traditional NI-DAQ driver that is installed on my system. I did create a new channel under the virutal channel in the Data Neightborhood option tree and tested that. Is that the same?
I have run the NI-488.2 Troubleshooter since I posted that message. It says that I am Missing Interface. The error message is as follows (in blue text)
One or more missing GPIB interfaces.
There are several reasons why you might encounter this problem:
Reason: Your GPIB interface is incorrectly installed.
Solution: Please verify that your GPIB interface is correctly installed and rerun the NI-488.2 Troubleshooting Wizard.
Reason: You are using a non-Plug-and-Play interface (e.g., AT-GPIB/TNT, PC/104-GPIB, PXI-8156) and you did not use the Add New Hardware Wizard to add the interface to your system properly.
Solution: Click the Add Hardware button and the Add GPIB Hardware wizard will guide you through the process of adding GPIB hardware.
Reason: For the PCMCIA-GPIB and PCMCIA-GPIB+, the PCMCIA host controller must be working properly in order to use the GPIB interface.
Solution: Use the Windows Device Manager to verify that your PCMCIA host controller is functioning correctly. Start the control panel by selecting "Start>>Settings>>Control Panel", open the System icon, select the Hardware tab and click on the Device Manager button. If you select "View>>Devices by type", you can look at the PCMCIA adapter properties to ensure it is correctly enabled.
Could this be the cause of all my problems? If so why would this error come about if nothing has changed and how would I go about fixing it?
Any help would be greatly appreciated.
Adam
05-11-2007 04:57 PM - edited 05-11-2007 04:57 PM
NOVA,
It is good to hear that your 6024 is working in MAX. I am curious why you ran the 488.2 troubleshooter, as you did not talk about using any 488.2 and did not list any GPIB equipment in your first post. If you do not have any 488.2 equipment, this error is expected behavior. I may suggest trying an example program (Help >> Find Examples .. >> Directory Structure >> daq >> analog in), and see if you get any errors. Is there a small piece of code you can make which will reproduce this problem? A screenshot of the error would also be helpful.
Also, how did you find that the error is being thrown by the AI Group Config VI? Did you do highlight execution? Is the error telling you this? The more detail you can give, the better we can help.
Message Edited by David L. on 05-11-2007 04:57 PM
05-11-2007 06:00 PM
David,
I appologize for the confusion, you are right, I don't have any 488.2 devices in my system.
As for the error message that is dumped out of AI Group Config, it is listed in the error itself. I have highlight executioned the program, everything is fine going into the AI Config VI, but the error pops out of the AI Group Config VI listed. Does that give you any ideas?
Adam
05-14-2007 03:38 PM
Adam,
From what we have talked about, I believe something has changed in the setup. Since the card is working in MAX, and obtaining correct readings, if you are using any tasks in MAX – are they still there and the same as before? What about the example programs mentioned previously, do they work?
A few screenshots of the error, along with posting your code may help. (You may need to zip the files if the code is large) I cannot guarantee to fix the code, but can look too see if something jumps out that may be causing this issue.