error 10401 DIO port config PCI-DIO-32HS

[Steve_S1]

Hi,

I'm having issues running an existing application with a new PC. I installed the PCI-DIO-32HS OK and it is recognised in MAX under Traditional DAQ. I installed the updated TDAQ drivers 7.4.4 on the machine and reset the driver in Traditional DAQ.  I still have this error! I have also uninstalled and rebooted my machine several times! Self test also runs without errors. Does anyone have any idea what I can do? Is there any config I've missed?

[Ian Colman]

Hi Steve,

It is possible that LabVIEW is being run before MAX has assigned a hardware handle for your device. Have a look the following knowledge base article on our website which should hopefully be of help to you:

http://digital.ni.com/public.nsf/websearch/46F78EDD19BA0CC386256CEE007201FC?OpenDocument

Please let me know how you get on with this and if this doesn’t help, then could I ask which version of LabVIEW you are using in your new system?

Regards,

Ian Colman
Applications Engineer
National Instruments

[Steve_S1]

Thanks Ian,

The app was running at start up so I disabled this and ran it after xp had fully booted. I still have the same failure!

The version I have is 8.2.

Steve

[Ian Colman]

Hi Steve,

If you saved your existing code with options, and chose to save it as a development distribution so that you could bring over the library files to your new system, this is probably the cause of your error code. If possible, what I’d like you to is return to your old system, then resave just the VI itself, and if you have any of your personal VI's that are stored in a .llb file save them as well. Then load the VI and any personal .llb's on the new system and see if you have any problems.

Let me know if you are able to do this and if so, how you get on.

Ian C.

Message Edited by Ian Colman on 10-16-2007 09:59 AM

[Steve_S1]

Hi Ian,

Unfortunatly I don't have access to the old system (It's still in use at our customers site. All I had to work with was a complete set of the VI's. Is there anything I can do with these?

Steve

[Ian Colman]

Hi Steve,

You should be okay but after looking into this in detail I’m going to need a little bit more information I’m afraid (apologies for not being able to providing a quick answer to your problem). Are you working from a .VI file or is it an executable application that doesn’t run properly on your machine? Can I also ask if you have any non-.vi files for the application you are dealing with? I’m specifically thinking of any library files that may be conflicting with the libraries already on your computer.

Many Thanks,

Ian C.

[Steve_S1]

Ian,

The application runs from a vi that is placed in the start up directory (this problem still occurs, even if the vi is moved into the root directory). I have also used a dll file to interface with a north atlantic industries card.

The application was originaly written in LV 6. The problem has occured after I have imported the application onto the new pc running a fresh LV8.2.

Thanks,

Steve

[Ian Colman]

Hi Steve,

Thanks for all the information you've provided and your patience with getting this solved. It seems we've exhausted any library problems I can think of right now, but its possible that a more simple problem is to blame regarding the device names/MAX assignments on your machine and in your code. Is it possible for you to give me a screenshot of max with your PCI-DIO-32HS card selected, and a screenshot of the LabVIEW code where the task is configured? The more information you can give the better really so a copy of a whole VI would be preferable instead of a screenshot of the LabVIEW code but i understand completly if you are not able to attach your whole VI.

Kind Regards,

Ian

[Steve_S1]

Ian,

I have noticed that after the main VI errors, if the vi is continued, then put back into operation mode, the application seems to run ok. Although, I don't have anything to send the card to test it fully.

I have attached a screenshot of the MAX screen showing the card. The main vi uses several other vi's and as such am unable to attach them here. I have taken a screenshot of the area that is error (or i believe so). The vi that errors is the dig line. Which contains the DIO port config.vi.

I hope this helps. Let me know if I need to send more information.

[Ian Colman]

Hi Steve,

That’s a great help thanks. When using T-DAQ you assign a number to the device in max and then this number is used in your LabVIEW code to identify which device to access. It is likely that your device is configured as Device 1 in MAX; but in the ‘Write to Digital Line’ VI in your code, the device input is wired as Device 15. You can either change this to device 1 in your code, or a better option would be to configure your DAQ card to device 15 in MAX. To do this, right click on the device in the Traditional DAQ category of MAX, go to properties, and then change the device number to 15.

Hope this solves your problem,

Ian