Error 1097 the first time calling LinearFit.vi using the bisquare fit method

[dlabar]

When I start LabView (8.2) and run a certain vi, I get Error 1097 the first time I call LinearFit.vi and the fit method is "Bisquare".  If I try calling LinearFit.vi again, it works fine (no error).  If the method is "Least Square" or "Least Absolute Residual", I don't get the error ever.  Any suggestions on what I may be doing wrong, or if I'm not doing anything wrong, how to get around this annoying error?

I just tried creating a new vi with nothing but the LinearFit.vi in it, and the error occurs the first two times I run the vi, but not on subsequent attempts.  I've attached the simple vi to this message.

[daveTW]

Hello dlabar,
I don't get the error when I run your VI. Do you get the error with that data in the array constant? Did you alter the "Linear Fit.vi" in vilib?
Greets, Dave

[dlabar]

Hi Dave.  Yes, I do get the error using that array constant, or any other data I input.  As far as I know, I haven't altered LinearFit.vi.  What is the easiest way to check for sure?

Thanks,
Dan

[daveTW]

Hi Dan,
I don't know how to check this except to compare the BD. The path to the Linear Fit.vi is "..\National Instruments\LabVIEW 8.2\vi.lib\Analysis\6fits.llb\Linear Fit.vi" and the BD look like this:

 

Greets, Dave

Message Edited by daveTW on 03-21-2007 03:43 PM

[dlabar]

Hi Dave.  Yes, my BDs look like this.  The file dates for "Linear Fit.vi", "Linear Fit (Bisquare).vi" and "lvanlys.dll" are also about the same as the install date.  So I don't think they have been modified.

[eek]

After navigating to Help>>Explain Error and typing in the error code you have mentioned, one can see LabVIEW's explaination of the error you have recieved.

"LabVIEW:  An exception occurred within the external code called by a Call Library Function Node. This might have corrupted LabVIEW's memory. Save any work to a new location and restart LabVIEW."

So indeed, it seems as though there have been some sort of corruption in your vi library. An easy fix may be to simply repair (or even uninstall and reinstall) LabVIEW 8.2.

Emilie Kopp | Applications Engineer

[dlabar]

I had been limping along with several error messages until I decided to upgrade to 8.5 earlier this week.  I had tried repairing 8.2, but that didn't work.  Removing all NI software and then installing 8.5 did work, however.  Thanks for your help.