Labview 5.0 VI errors

[putnam59]

Hello, I am attempting to resurrect a test PC that is using Labview 5.0. 

I do not have source code or a block diagram for the VIs that are being used.  I have been advised by NI support that means it cannot be brought  into a more current version of Labview. 

The hardware is  a NI Lab-PC-1200 Series running Windows 98. The original drive crashed and I have replaced the drive and restored the copy of Labview 5 from the server and the custom VI files  and associated libraries that are used. 

When I attempt to open the VI for the test routine I get the following error: 

Error 7 Occurred at Open File+.vi

Possible reasons: 
Labview: File not found.
Or
NI-488 Non-existent board.

Continue Stop

If I choose Continue, the entire application quits. If I choose Stop, the front
panel opens but the buttons and functions don’t work and when I close the file, it ask if I want to save changes to VIs open  in memory. If I choose yes to all, the next time the VI is opened the Labview program starts to open then exits. 

I opened the library file and the Open File+.vi is in the library and it allows me to open the Open File+.vi, and the other VIs in the library are there as well. I have verified the path in preferences is correct.

I have attempted a mass compile with no change in the results.

I have created a new library, copied all the VIs in it, and put that in the path for Labview, and it will still generate an error: it will open then ask if I want to save changes. If save is chosen, Labview appears to save changes then closes. Next time the VI is opened, Labview exits. If changes aren't saved, Labview exits. 

I would sincerely appreciate suggestions or recommendations.

[GerdW]

Hi putnam,

why don't you do yourself a favour and replace that stone-old PC-1200/LV5.0 combination by a recent LabVIEW version and a USB-6003?

This also is considered "basic", allows for 100kS/s sample rate, supports even 16bit ADC resolution - and is supported by DAQmx!

Bonus: you can replace that old PC too with a modern one with an OS allowing you to connect that new PC to any network without getting into trouble with the company IT department…

[Hooovahh]

---

@putnam59

 If I choose Continue, the entire application quits. If I choose Stop, the front 

panel opens but the buttons and functions don’t work and when I close the file, it ask if I want to save changes to VIs open  in memory. If I choose yes to all, the next time the VI is opened the Labview program starts to open then exits. 

When you click stop the front panel is shown, and the code is no longer running.  I'm betting there is a broken arrow which is why none of the controls do anything.

I know you may feel like you are very close to making it work, like all you need is one last piece.  But I agree with Gerd.  This is an application likely written around 20 years ago!  And without the source code, or documentation you have very little you can do to fix it.  If you understand the basics of what the application does, and what you need it to do, I'd hire an alliance partner to try to recreate the functionality you need.  If all you need is to take some measurements and log it then this could be done pretty quickly with modern tools like DAQmx.

[Michael_Munroe · Accepted solution]

I started programming with LabVIEW 5.1 and understand how you would like to get this to work again.  The Open File+.vi is not source of the problem, but the location where the problem occurs.  Some file that is critical to the operation is not where it is expected.  I see 4 possible issues and 3 things to try.

Issues:

1. Your application hierarchy is not as expected

2. There is a configuration file that is not where it is expected

3. Something is missing from LabVIEW

4. Something is missing from DAQ

Things to try:

1. Look on the original computer for a configuration file (like c:\cal\cal.txt)

2. Add the mail application VI to the LLB and set as top-level.  It will open when you double-click the llb

3. Confirm the existence of <vilib>DAQ/EASYIO.llb

The configuration file is most likely your problem

[putnam59]

Thank you all for your replies. 

I will pursue the course of action you have recommended later today, Michael. 

[putnam59]

Follow up: 

1. There is a config file at C:\cal\cal.txt

Contents are: 9.554, 9.470, 2.14

2. Did not attempt adding mail application vi, will do so and advise. 

3. Confirmed existence of <vilib>DAQ/1EASYIO.llb

thank you for your time.