Ni-DAQLV error -10243, error-1000​8 & error-1040​1

Question

I am using labvirew6.0. I have the following errors "Ni-DAQLV error -10243, error-10008 & error-10401" Do I need to install the latest drivers on my system?I still want to use labview6.0?

Answer 1

Hello
I am using labview 7.0, Max 3.1.1.3004 and i am having the same problem.
We currently have two pc's running labview 7.0. This system is step up with one
pc as the main controlling pc and the other pc mainly collect data and
transfers it to the main pc. PC1 is the main controlling pc and PC2 is the
data collecting pc it has a daq card 6025E and two 6527 cards.
The
6025E is used to collect and monitor transducer and collect pressure readings.
The 6527 are you use to trigger I/Q points to open and close doors, trigger
LEDS and other functions on our system. This current system works fine. What we
are attempting to do is recreate a complete back system, the PCs.
This Code written by a third party and we no longer have them as a resource.
The un-complied code is broken up into to sections one set of code is for PC1
and the other set of code is for PC2. So we took the un-complied code for PC1
and complied on what is going to be our back up PC1, all went good and the back
for PC1 is ready. Here is where we run in problems. We took the un-complied
code for PC2 and complied it on back up PC2.
BackUp
PC2 contains one 6025E card and two 6527 cards.  When we try to run the
EXE file we get a 10001 only if a file called niconfig.daq is within the folder
containing the exe file. When I remove this file called niconfig.daq, we now
get 10243 error code. Since we are unable to contact the original programmer I
have not clue it that niconfig.daq file needs to be there or not.
How do you read a .daq file anyway in text pad it's unreadable.
 Error code 10243 says occurred at DIO Port
Config, I can find that .vi within the code but how do I know what needs to be
changed in that .vi,  DIO Port
Config  is a labview pre-built vi and not
a customer vi. any ideas of what that could be?  I saw the post suggesting the  driver update i will try that and let you know if it fixes the problem.  anyone have any ideas?
FYI  lvdaq.dll 7.256.3.1 is also complied and place in the same folder with our EXE