08-19-2009 03:33 PM
Solved! Go to Solution.
08-20-2009 09:41 AM
08-20-2009 12:46 PM
Grant - As I mentioned, I have placed these .M functions in the same location under C:\Documents and Settings\jmasse\My Documents\LabVIEW Data on both computers. (Using the default path works on one PC but not the other.)
And I have verified the path through the Tools >> Options menu ON BOTH SYSTEMS. They are setup identically via the Tools >> Options menu.
I have a common repository for the files I share between systems and I will download the lastest files onto each system but each environment is configured individually.
Each system has its own LabView Prof Develop 8.5, so each LabView environment is configured via the Tools >> Options menu. Each system has the .M files under C:\Documents and Settings\jmasse\My Documents\LabVIEW Data.
Like I mentioned, even the default path will not work on one system. Is there something else that got ommitted during loading of LabView or something wierd like that?
08-20-2009 03:28 PM
08-21-2009 04:04 AM
The Vi is not broken. The only way I can tell that there may be a path issue is when I run the VI that it gives me a line# error. That line is when the mathsript node encounters the external function.
As for the Mathscript Window, I am not sue if that would work since I pass in many parameters to the Mathscript Node.
I am wondering if it is not a path issue but a mathscript issue. Now that I realize it, there are other external functions that seem to work OK but it is 1 particular function that gives me the error - three times - each time it is called. What is strange is that it works on one PC but not the other and both environments are identical.
08-21-2009 12:33 PM
08-21-2009 01:52 PM
Grant - thanks for sticking with me. There is no warning glyph in the upper right hand corner and this is part of a project (though when I troubleshoot I just open the lower Vi containing the node). I may provide a copy of my work but it will probably work on your machine since it runs on my office machine. (I'd like to have you look at one last thing before I send it.)
There is a strange LabView phenomenom between the two machines. When I open a probe for the Mathscript node, on the good system it pops right open (about 5 seconds) but the other system takes over two minutes and it starts loading all the mathscript VIs and dlls at this point instead of the beginning like the good machine does. I'd hate to say it but it looks like I need a rebuild. Any last minute suggestions prior to this?
08-21-2009 02:28 PM
08-26-2009 01:34 PM - edited 08-26-2009 01:40 PM
Grant - thanks for the help. I found another post regarding an "Error -90051 occurred at Error in line 68. You specified an invalid number of input parameters for this function." that I was getting in the popup window. It mentioned that he purposely broke the .m file so that LabView would see the broken .m file. He then restored the .m file to its original state and viola, LabView was happy. So I tried it and the same happened. After many days of banging my head, the solution was to have Labview see a broken .m file and then fix the .m file. Sounds like a LabView issue to me. Anyway thanks for the help.