LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

NI-DAQ 6.9.3 and Labview 8.2

I am attempting to integrate some old DIO and MIO cards with Labview 8.2.1 on Windows XP platform.  I saw a procedure where you can load the Traditional NI-daq support in Labview 8.2.1 folder.  I have loaded the Traditional Daq driver 6.9.3.   After running Resman successfully, I could see all cards in my device interface under MAX.  However, I still cannot get the cards to just initialize.  The two cards of interest are:  VXI-DIO-129 Digitial I/O and the VXI-MIO 64XE-10.  Any other suggestions someone can offer me?
 
Thanks,
 
Michael
0 Kudos
Message 1 of 7
(3,895 Views)
Hello Michael,

These cards are no longer officially supported, but here is something you can try to initialize these cards.  If you're getting any specific errors, post them here and we'll do our best to troubleshoot them.

While other combinations of the drivers might work correctly, here is a list of drivers that has been tested limitedly on a Windows 2000 computer with MXI-2 that can be used as a starting point. From a clean image of Windows 2000, install the following programs in the order below:  From a clean image of Windows 2000, install the following programs in the order below:
  1. NI-VXI 3.3.1, the complete installation. This will install VISA 2.6.1.
  2. CVI 6.0, or LabVIEW (preferably an older version).
  3. NI-DAQ 6.9.3. Do not install any later patch.
  4. NI-488.2 2.1. This version will not upgrade VISA or MAX.
  5. Go into MAX and expand Devices & Interfaces. Right-click on the VXI system and run Resource Manager.
  6. Right-click on the VXI system and go to Properties. This will be for the PCI-MXI-2 card. On the General tab, click on Hardware Configuration. On this General Tab at the Quick Configuration section, choose VXI-DAQ Configuration. You will need to do this again for the VXI-MXI-2 card in the frame. You will have to reboot both your computer and the chassis.
  7. You may need to run Resource Manager again at this point. After doing that, and refreshing MAX, your VXI-MIO should show up in Devices and Interfaces.
Note: Other combinations of the driver might function correctly.

Thanks,

Meghan
Applications Engineer
0 Kudos
Message 2 of 7
(3,876 Views)
Megan,
 
I am responding to your email sent to awhile ago.  First, on Step 2 (load cvi 6.0 or labview (an older version)), I have to use Labview 8.2.1 or upgrade to 8.5.  Secondly, I am still unable to get this to work.  Secondly, I attempted to load Test Executive 5.1 and call it with Labview 8.2.1 and it crashes and closes Labview altogether.  Could this be related to not having the correct DAQ driver installed?  Suggestion?
 
Thanks,
 
Michael
 
0 Kudos
Message 3 of 7
(3,797 Views)
G. Mike,

As I stated, these are unsupported cards.  I can try to help you if you can tell me a specific error you are getting.

Thanks,

Meghan
0 Kudos
Message 4 of 7
(3,775 Views)
G Mike,

As per this KnowledgeBase article, Test Executive 5.1.1 is the latest version of Test Executive and is the version that is compatible with LabVIEW 8.2.1, but not with LabVIEW 8.5.  For your reference, National Instruments has used Test Executive as a foundation for its newer product line, NI TestStand.  Significant upgrades and improvements over Test Executive have been made and I definitely recommend you download the free evaluation of TestStand, which you may find here.

As for your current predicament involving the LabVIEW crash you are experiencing, you should try opening up the Test Executive VIs in an intermediate version of LabVIEW (somewhere between LabVIEW 5.0 and LabVIEW 8.2.1) and recompiling the VIs.  Then they should open in LabVIEW 8.2.1.
Derrick S.
Product Manager
NI DIAdem
National Instruments
0 Kudos
Message 5 of 7
(3,752 Views)

Thanks Derrick.  That was great information.  I will definitely try your suggestions.  I inherited this job so I want to cover all basis before starting.  Two questions before I go:

  1. Does each individual VI need to be opened before compiling them to 6.1, for example, or when I load the VI's under 6.1, Labview will ask me if I want to save them as 6.1 vi's?
  2. Do you know whether there exist a converter program of sort that will convert Test Executive sequencing program files into Test Stand or does this have to be done manually?  The Test Executive is large and also calls a large amount of VI's to run.
0 Kudos
Message 6 of 7
(3,735 Views)
G Mike,

I certainly understand your predicament and thus I personally hope that we can continue to be of help even though you are using pieces of hardware/software that are no longer officially supported by our department.

Here is what I found regarding your issue by simply searching on the National Instruments homepage:

  1. It seems to me like you could mass compile all of your VIs instead of having to compile them one-by-one.  This option is also accessible by the Tools»Advanced»Mass Compile menu within the LabVIEW environment.
  2. There exists a Sequence File Converter with TestStand that should handle the conversion between Test Executive sequences and TestStand sequences.  Furthermore, we provide documentation on making the conversion that installs by default to the <TestStand>\Docs\Help directory after you complete the installation of TestStand.



Message Edited by Derrick S on 11-06-2007 02:29 PM
Derrick S.
Product Manager
NI DIAdem
National Instruments
0 Kudos
Message 7 of 7
(3,710 Views)