Sudden LabVIEW 6.0 instability and a programming query

[andrewW]

Hi all!

LabVIEW 6.0 instability:
-------------------------
After roughly a year of stable operation, my LabVIEW 6.0 (Win 2000 NT)
is suddenly given to wanton bouts of instability. The software is installed on
my lab PC and handles a modest 5 instruments over a PCMCIA-GPIB
interface. The program crashes with the following error message:

"LabVIEW.exe has generated errors and will be closed by Windows.
You will need to restart the program.

An error log is being created."

The generated error log file is then "www.log" which I cannot make head or
tail of. Anyone dealt with this problem in their travails? I suspect wayward
web and networking settings are to blame but am too green to try
anything drastic. I am a bit w
ary of having to reinstall the software as I
need one more series of measurements before writing my MSc thesis.
Typical measurements last 72 hrs+.

Programming query:
-------------------------
I wish to program a master ".vi" to contain and singly execute ("case")
independently functioning slave ".vi" 's. My chief problem is that the
"slaves" each have many setup parameters, many unique but some
common. As the common setup parameters are constants, I would
like to rationalise the final solution by centalising their specification
at the "master" level. The goal is for the "master" to:

1. Be the site of specification of all constants
2. Enable the user to specify unique parameters before execution of
every "case"d "slave"


Thanks in advance.



Best regards,

Andrew

[Randy_H]

Andrew,

Please look for Failure_Log.txt in the LabVIEW TEMP directory (look at Tools >> Options >> Paths for the absolute path to this directory). This is the error log the message is talking about it. Also, what has happened to your computer (software install, uninstall, driver upgrade, service pack, etc.) when this started? It could be a very minor thing. I would suggest repairing the install of LabVIEW to see if that fixes thing. Go to Add/Remove Programs and choose to uninstall LabVIEW 6.0.x or later. A dialog box will open and one of the options will be to do a repair. (If you are using LabVIEW 5.1.x or earlier, then do a full uninstall and reinstall again.)

As for your second question, are you using LabVIEW 6.1? If you are, then you can use the event stru
cture to monitor which "case" you will be running and only show the configuration parameters you need to show. If you are not using LabVIEW 6.1, then I would suggest putting each "case" on a separate TAB control page and all of the consistant configuration parameters on an additional page.

Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

[andrewW]

Thanks for your reply, Randy.

> Please look for Failure_Log.txt in the LabVIEW TEMP directory (look at
> Tools >> Options >> Paths for the absolute path to this directory).
> This is the error log the message is talking about it. Also, what has
> happened to your computer (software install, uninstall, driver
> upgrade, service pack, etc.) when this started? It could be a very
> minor thing. I would suggest repairing the install of LabVIEW to see
> if that fixes thing. Go to Add/Remove Programs and choose to uninstall
> LabVIEW 6.0.x or later. A dialog box will open and one of the options
> will be to do a repair. (If you are using LabVIEW 5.1.x or earlier,
> then do a full uninstall and reinstall again.)
>

The only incremental installation to the system si
nce last year is
an update of the F-Secure Antivirus package. I will be attempting
a repair tomorrow.

> As for your second question, are you using LabVIEW 6.1? If you are,
> then you can use the event structure to monitor which "case" you will
> be running and only show the configuration parameters you need to
> show. If you are not using LabVIEW 6.1, then I would suggest putting
> each "case" on a separate TAB control page and all of the consistant
> configuration parameters on an additional page.
>

I am using LabVIEW 6.0 and will be doing so for the remainder of my
MSc thesis period (till mid October).


Cheers!

Andrew