Help with Error -10401 occurred at AO Group Config

Question

I am receiving the error: "Error -10401 occurred at AO Group Config" and have been unable to fix it. 
Some background: This is someone else's program who has since left, so I am not very familiar with it. It was running fine a little while ago, until the PCI-GPIB card broke.  We got a new GPIB card (essentially the exact same model; the old one was 183619B-01; the new one is 183617K-01) and now this error appears every time I try to run it. 
I believe this is being thrown by the "AO Config.vi" in my VI Hierarchy.  From reading other forums, such as this: http://digital.ni.com/public.nsf/allkb/46F78EDD19BA0CC386256CEE007201FC and this: http://forums.ni.com/t5/LabVIEW/Change-in-PCI-Device-Number/m-p/2312186#M726679, it seems it may be a problem with properly assigning device numbers.  (The new GPIB card  may have been assigned a new device number while the program is calling the old one).  However, the solution offered is to right-click on the device in MAX and change the device number, but when I right-click I am not given that option (see attached image). On the other hand, it could also be some sort of driver problem.  
I am running LabVIEW 8.2.1 and Measurement and Automation Explorer 4.2.1.3001 on Windows XP SP2.  Any help is greatly appreciated.  
Attachments:
error.PNG ‏89 KB
right click.PNG ‏77 KB
hierarchy.PNG ‏94 KB

Answer 1

Hi bh424,
I would make sure that you have updated drivers as you mentioned. If you are using TDAQ make sure to reset the device driver mentioned in the KB you listed.
Another thought would to be to remove and readd the device in MAX to refresh it, and potentially change the naming in your program to reference a new named device. If you cannot rename the device in MAX you could look at repointing the device in your code.
Are you able to communicate with the device at all in MAX through simple queries? From the right click screenshot it looks like *IDN did not communicate properly.
Have you also refreshed the list or rebooted your machine?
http://digital.ni.com/public.nsf/allkb/23B5918E5604915B86256C2B005F4D70?OpenDocument
I would first ensure you can communicate with the new card in MAX alone. Here are some troublehsooting steps if that is not the case:
http://digital.ni.com/public.nsf/allkb/A80DBFCCAC36EBDE862562C80058856E?OpenDocument
There is also the possibility that the card is broken as well. If it was indeed purchased from a 3rd party vendor, there is less we know about the card or what could have been done to it before you acquired it.
Regards,
James W.
Applications Engineer
National Instruments