VXI and VME

cancel
Showing results for 
Search instead for 
Did you mean: 

Conversion of MXI/VXI Win 3.XX to Win98/LabView 7.00 with MAX.

 

Hello,

 

I am trying to install Win 98/ Labview 7.00 to a system with AT-MXI board. In order to use MAX for self test purposes I have to use Win98 with Labview 7.00 as minimum configuration while using VXI 3.10 and NI-VXI upgrade for Windows 95 as available support for 98/95 for AT-MXI board.

 

  1. Can I use Labview’s programming power for this upgrade?
  2. Is it possible to see AT-MXI board under MAX’s device and interface for AT-MXI board.

     

  3. Is it possible to use previous test code in C in Labview?

     

Thanks,

 

Hasan

0 Kudos
Message 1 of 17
(10,206 Views)
The latest version of NI-VXI to support the AT-MXI only installs support for LabVIEW 4.x, which indicates the age of the system you are using.  I would recommend that you remain with the current system which you have working, until you can perform a full upgrade to bring your system up to current standards.

Based on the age of your system, I would recommend that you look into replacing the system with a PXI solution, in order to bring your system up to the latest technology.  If you must continue to use VXI, I would recommend that you replace your MXI interface with a MXI-2 interface such as the NI VXI-PCI8015.   This will allow you to easily utilize your VXI system in Windows XP using the latest versions of LabVIEW.

National Instruments PXI Products
National Instruments VXI-PCI8015


I will attempt to answer your original questions, but as I have mentioned, this is a very old system which is no longer supported by National Instruments:

1. Can I use LabVIEW's programming power for this upgrade?
     The latest supported version of LabVIEW for your AT-MXI is LabVIEW 4.x.   It may be possible to use the installed VIs in LabVIEW 7.0, but  this would not be supported by National Instruments in any way.

2. Is it possible to see AT-MXI board under MAX's device and interface for AT-MXI board?
     The AT-MXI driver for Windows 95/98 is older than Measurement and Automation Explorer, and will not appear under Devices and Interfaces.

3. Is it possible to use previous test code in C in LabVIEW?
    C Code can be executed in LabVIEW either as a Code Interface Node (CIN) or by making a DLL call.  Not all C code can be used as a CIN, so the DLL method would be recommended.  Either of these methods will require modifications to your existing code in order to use it in LabVIEW.   You may be able to make this code work in LabVIEW 7.0, but its functionality will not be supported by NI.


Jason S.
Applications Engineer
National Instruments
Message 2 of 17
(10,191 Views)

Hi Jason,

How about just replacing the MXI AT board with MXI-2 PCI board?

Is it possible run the system, I mean original test programs written in C and at the same time use MAX to troubleshoot and functionality checks only?

Does it matter for VXI which MXI board installed on the controlling computer?

Thanks.

 

0 Kudos
Message 3 of 17
(10,185 Views)
You would need to replace both the PCI board and the VXI Controller with MXI-2 equivalents.  The VXI-PCI8015 kit I reference in my previous post includes both needed devices.  Performing this upgrade would let you upgrade the controlling computer to a newer machine capable of running Windows XP.

You should still be able to execute your original applications, and MAX will be available to you to configure and test your configuration.

Let me know if you would be interested in discussing this upgrade option with one of our configuration specialists, I already have your contact information from your previous interaction to technical support.

Jason S.
Application Engineer
National Instruments
0 Kudos
Message 4 of 17
(10,169 Views)

Hi Jason,

Yes, please let me know the cost of such an upgrade and most importantly, is there a possibly to have a conflict when I will run original test programs written in C on DOS platform, win 3.xx.

 

Regards,

Hasan

0 Kudos
Message 5 of 17
(10,160 Views)
Hasan,

Do you have access to all of the original source code so that you could recompile your code if necessary, or do you have to be able to run this application without access to the source code?

Jason Smith
Applications Engineer
National Instruments
0 Kudos
Message 6 of 17
(10,157 Views)

Hi Jason,

I have the source codes, but I don't have the compiler. My programming knowledge is limited by programming in Basic, Fortran and learning LabView recently.

I don't know how to install the drivers and how to control the instruments on the VXI side, I only used a GPIB board under LabView with the original drivers from Tektronix and MXI/VXI issues seems more complex than controlling instrument with LabView. I expected to find some self test panels in MAX for the MXI board after installing 98, VXI 3.10 but I could not.

Having said that, I would like to upgrade this system to XP, LabView 8 platform and use this opportunity to be familiar with MXI/VXI and learn how to program and trouble-shoot the system.

The system has some other hardware, like power supplies and instruments; I don't know if I can find the drivers for them for XP.

Regards,

Hasan

 

0 Kudos
Message 7 of 17
(10,153 Views)
I have verified that for the most part the Windows 3.1 driver should be compatible with the latest available for Windows XP.  It is difficult to say 100% that your code will run with zero modification, but most applications should not require modification.

Somebody should be contacting you to discuss the options you have to upgrade the system, and to help you determine the best way to meet the goals you have for this system.

Jason S.
Applications Engineer
National Instruments
0 Kudos
Message 8 of 17
(10,146 Views)
I actually have more information regarding the use of applications written using the Windows 3.1 version of the NI-VXI driver.  While the function calls remain the same, and major modifications to your code will not be needed, you will need to be able to recompile your code so that it will be able to properly access the Win32 version of the driver.  You mentioned that you have the source code for your application, but that you do not have a compiler.  Is a compiler something that you would be able to obtain?  If you are unable to find a compiler for your code, you may need to just keep your system as it is in Windows 3.1 until it can be replaced with a newer solution.

Jason S.
Applications Engineer
National Instruments
0 Kudos
Message 9 of 17
(10,136 Views)

Hello!

I have managed to upgrade an old system with AT-MXI-1. It used to work on an old 486 with Win95. We have bought a new pentium 4 computer with ISA slots (mainboard Supermicro P4SCA). The installation of NI-VXI 1.1 drivers on Windows 2000 was done according to instructions on NI site, VISA was taken from LV6, that is 2.6, and because of an old AT-GPIB-TNT (non P&P!) card, I used NI488.2 1.7 drivers. I installed the LV 8.0 and the system works!

I have installed vxi tools and the stubs package (_vxitls.zip and vxistubs.zip) from NI ftp site and porting the most VIs from Labview 5.1 was fully automatic - no changes needed.

Hovever, I have some VIs with interrupt functions, and they are missing some functions like EnableVXIint, VXIIntHandler and others. I know I could make new wrappers around VISA interrupt functions but it would be much easier for me to find the file 10vxiint.llb, where this functions are. It is not in a forementioned stubs package. Is it possible to get this file or just give me a pointer, on which LV CD could I find it?

Thank you for the answer.

0 Kudos
Message 10 of 17
(9,814 Views)