Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

Reinstalling product bought in 2004

Hi

 

I bought and used NI-DAQ 7 in 2004/2005. Recently the customer asked me to do some more work so I reinstalled the card in a windows 7 PC and the software. I am using Visual studio 2008 so didn't check the box for visual studio 2005 when installing.

 

After downloading updated drivers I have the card working as evidenced by the test panel.

 

I now need the assembly reference dlls NationalInstruments.Common and NationalInstruments.DAQmx. for my software.

 

These will be .NET2.0 dlls so can you let me know where I obtain these.

 

Many thanks in advance

 

Ray

0 Kudos
Message 1 of 7
(4,301 Views)

I thought I had found the answer. I uninstalled my NI DAQ 7 then downloaded and installed NI DAQ 871. This gave me the dotNET 2 assemblies (NI.DAQmx and NI.Common) which I added to my programs and saved them as well.

 

But then my ADC card was not recognised in Measurement explorer. I tried updating it's driver but windows told me that the driver PCI-2625 was the latest one.

 

So uninstalled NI DAQ 871 and reinstalled NI DAQ 7. I could not install any assembly dlls because I was told that was not possible because I had not got dotNET 1.1 Framework installed which is correct, of course I am running dotNet 2. However when the loading had finished I copied NI.DAQmx and NI.Common back into the National Instruments directory and re referenced them in my program.  The card worked ok in Test Panel now.

 

I could now compile my adc program and produce an exe file. I thought I had cracked it but no, on running the program I got an error message "A procedure imported by National Instruments.DAQmx version 8.7.20.11 Culture Neutral PublicKeyToken=454464cdeaab541 could not be loaded".

 

So where to go from here. Do I have to install dotNET 1 Framework to make this card work. Any suggestions gratefully received

 

Ray

0 Kudos
Message 2 of 7
(4,290 Views)

Hi Ray,

 

I have been looking into your issues for you. Firstly, I must explain that National Instruments do not officially support Windows 7 and that you would achieve far greater success rates if you were using an officially supported platform.

 

I have a number of questions which relate to this issue. My first question is, which DAQ device are you using? Secondly, have you had this device working in the past with a different version of Windows or Visual Studio. A third question is, are you using the traditional DAQ driver or DAQmx? You mentioned that you installed the DAQmx 8.7.1 driver and reinstalled the traditional DAQ 7 driver, though the error message you are receiving suggests you are using DAQmx.

 

The error message that you are receiving also suggests that this is a National Instruments product related issue rather than a problem with your .NET framework.

 

Many thanks,

 

Christian Hartshorne

Applications Engineering 

National Instruments

0 Kudos
Message 3 of 7
(4,273 Views)

Hi Christian

 

Thanks for your reply

 

1. I have had this system running under Windows XP with dotNet 1.1 framework installed, and using VisualStudio 2005, and it is running with the customer with either windows 2000 or XP.

2. The card is NI-DAQ 7 (this is the name on the manual) which I bought in 2004, just after these new adcs came out and I am running with DAQmx.

 

As I mentioned before the card is running ok and is visible in Measurement explorer and in Test panel where I can see the analog input channels.

 

Device manager shows it with a driver PCI- 6259 and the driver in System32\DRIVERS\ is npalk.sys. This has a time stamp of 07/07/2004 which ties up with the card date.

 

I feel the problem is to do with some form of incompatibility with the API's referenced in VisualStudio, and thus embodied in my application, and the  card drivers which must need dotNet framework 1.1, to use these APIs. I hesitate to install 1.1  on my machine since it is now obsolete but unless you can suggest anything better I might have to do this.

 

It is perhaps not a real problem but just a security problem with your software designed to prevent folks from doing what I have attempted to do, maybe there is some way of defeating this security key and it might then all work ok.

 

I am surprised that you do not support windows 7, the release candidate has been around now for at least 6 months and I have been using this full time, as have millions of other folks round the world, and it is supposed to be compatible with Vista driver wise.

 

Newly purchased machines now have windows 7 installed (and no dotNet 1.1) so might I suggest that you consider tackling the support for this with a matter of urgency.

 

Best Regards

 

Ray

 

0 Kudos
Message 4 of 7
(4,267 Views)

Hello Ray,

 

Just to clarify,  DAQmx 9.0.2 is fully supported on Windows 7 x86 and x64.  Your PCI-6259 card will work with this driver.

 

Regards,

Seth B.
Principal Test Engineer | National Instruments
Certified LabVIEW Architect
Certified TestStand Architect
0 Kudos
Message 5 of 7
(4,257 Views)

Hi Ray,

 

Following on from what was said by Seth.B, I strongly recommend that you download and install the latest version of DAQmx (NI-DAQmx 9.0.2) which (as Seth.B mentioned) will work with your PCI- 6259 card. The fact that your card was functioning correctly under different versions of Windows and Visual Studio suggests a compatibility issue between your driver and your operating system.

 

If your problem persists following the installation of the new driver, let me know and I will endeavor to find you a solution.

 

Regards,

 

Christian Hartshorne

Applications Engineering

National Instruments 


 

0 Kudos
Message 6 of 7
(4,234 Views)

Hi Christian

 

Have downloaded and installed NI-DAQmx 9.02; the compatibilty issues have now gone away. I had hoped my software would run without any problems but I find that when I try to start analogTask I get an error :

NI Platform Services:  The requested memory could not be allocated. Task Name: analogTask Status Code: -50352.

 

Presumably there are some differences in the API causing this. I'll have to study some of your examples to see what has changed. 

 

Thanks for the help

 

 Ray

0 Kudos
Message 7 of 7
(4,223 Views)