LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

determine device number after crash

First, let me start by stating that I have never programmed or set up a system that was developed under Labview.  Recently, we had a system that was running under windows 95 crash.  I am still fairly new to the company and found out there was no backup, no source code, and the company that developed it has gone out of business.  That said, we had some installation disks (floppies) that we were sent over the years for installation and some files were recovered from the Win 95 hard drive.  On the new PC is XP.  I think I determined what files are required and, at least, I have the program now where it will start, but I get errors, 10007, 10401 AO buffer write, Device is not Nat. Instr...... and 10608 Buffer write..... I have searched the knowledge base and it looks like maybe the device addresses might not be right?  That is one of kbs suggest to look at that.  However, in this instance, I do not know what they should be.  Now for what I have done.  I installed NI-DAQ7.1 with defaults (NI-SWITCH, NO-VISA, etc.). I ran the installation utility that was on the disk and it installed LV runtime engine 5.1.  The cards are PCI-6503(Device 3), PCI-6711(Device 1), PCI-6713 (Device 2), and PCI-MIO-16XE-50 (Device 4).  All of these card show up under traditional NI-DAQ Devices in MAX.  One other thing I did because of a previous error, was to perform the test for each card in MAX.  I would appreciate any help in getting this running.  One piece I left out is that some of the files from the old drive show a TMExplorer.exe, which I believe was used to configure originally?  I don't know and I cannot seem to find out much about it, nor can find a download or get the TMExplorer.exe to run.  Would this be of any good?  Thanik you.

 

 

 

 

 

0 Kudos
Message 1 of 4
(2,599 Views)

T&M Explorer is an older program that is not supported on XP which is probably why it will not run. LabVIEW 5.1 is not officially supported on Windows XP either; but if you get it working, great. If the incompatibility does cause problems, the good news is that all four of these cards are still compatible with our latest LabVIEW and DAQmx drivers.

Did you get all four cards to work in the test panels in MAX? If so, then your good to start reprogramming the lost files, assuming you get around the LabVIEW 5.1 and XP incompatibility. If the old files are each stand alone programs you will have to learn where in the program the device is selected and reselect the device as it stands with the new device ID. Or, you could rename the device in MAX to match the program so you don't need to reset all of the recovered programs. If you have to upgrade to our latest LabVIEW and DAQmx driver, everything will have to be reprogrammed. None of the traditional DAQ programming will function in our latest LabVIEW versions.
Vince M
Applications Engineer
0 Kudos
Message 2 of 4
(2,569 Views)

Thanks for the information.  Not having the source code, I took a guess that the device numbers might match the slot number.  Fortunately, this was a good guess.  The application took out without any further issues.  Also, it is running on Runtime Engine V5.1 and NI-DAQ7.1 (as some of the kbs suggested).  I am glad  we dodged that bullet, but what a crash course.  Best regards. 

0 Kudos
Message 3 of 4
(2,561 Views)
Then make sure you take good notes as to what you did to get it working and store copies of it everywhere, particularly a copy with those floppies!Smiley Wink
0 Kudos
Message 4 of 4
(2,553 Views)