Example Finder broken in LabView 7.1 in OS-X 10.4?

I've just tried to install LabView 7.1 (and then upgraded to 7.1.1) on a Mac running OS-X 10.4.2. The Example Finder and other features (e.g., no Welcome Screen) do not seem to run. I went and installed on another system running 10.3.9 and all was fine. Is this a known problem? Is there a patch?

Sorry, I wasn't clear in my post. It did not work in 7.1 either. I had tried upgrading to 7.1.1 to see if that made the difference, but it did not. I have already tried installing 7.l twice.
In the LabView opening screen, I try to launch the Example Finder either in the Open... or Help... buttons. The "Launching Example Finder" small window flashes briefly, but nothing happens. The examples themselves are there, if opened manually, and they work.
JLS wrote:
Hello, I have not heard of this problem. So, it worked with 7.1, you upgrade to 7.1.1, and certain features are broken, but only on a 10.4.2 machine, and not a 10.3.9 machine. Have you tried uninstalling and reinstalling? I know that's a bit arduous, but for something like this I think it's worth a try. Perhaps something happened after your 7.1 install that affected the 7.1.1 upgrade. In this case, performing them one after the other may yield the correct behavior. Definitely repost if the uninstall/reinstall doesn't work, and we'll explore other options! Thank you, Best Regards, JLS

Similar Messages

Labview 7 for Linux on Redhat9,NI example Finder not working.

I have Labview7 for Linux on Redhat9, installed at /usr/local/lv71. "NI example Finder" is not working, the function of browser, search,submit,none is working. When I try to close it, the window looks dead, cannot close it. I will force to close it. What is the problem? Where are the examples?
Another question: the simple help text is working, but the details help is not working. I can open the help file by Mozilla. But I want the help could be linked, like what it is in Windows platform.
Thanks

Hello �
If whenever you type �labview� at the prompt, LabVIEW 7.1 is launched, it probably means that the paths are setup to launch 7.1 but it doesn�t necessarily mean that you do not have LabVIEW 7.0 installed.
If you only installed LabVIEW 7.1 in that computer, it is possible that somebody else had installed LabVIEW 7.0 before.
What I suggest doing is to run the UNINSTALL scripts for both, LabVIEW 7.0 and 7.1, and reinstall LabVIEW 7.1 as root, not as user.
Hope that helps!
S Vences
National Instruments

Example Finder Error- unsuccessful in sending a request to the NI Helpserver

HI
I have got a problem with Example Finder and when I double click on an example I get this error after about 3 or 4 minutes.
An error occurred. The NI Example finder was unsuccessful in sending a request to the NI Helpserver
Wud u plz let me know what is the problem and how can I open the examples.
Solved!
Go to Solution.

Check this first: Error when opening NI Example Finder: The NI HelpServer could not be found
The intention there is to check the service and to make sure your firewall isn't blocking the port.
Also, check to see if any other NI services are disabled. If there are, turn them on one by one to see if that fixes the problem. You may have to restart LabVIEW after each attempt.

How do I see the source code for 'NI Example Finder'?

At the LabView Express demo, the rep showed us how to view the source code for 'NI Example Finder' (started with Help, Find Examples...). Please refresh my memory.
--todd

There are a couple of VI's that shipped with LabView 7.0, but you can't see the diagrams.
C:\Program Files\National Instruments\LabVIEW 7.0\resource\system\HelpServer.llb\Run Example Finder__NATIONAL INSTRUMENTS.vi
Press Ctrl-E on this VI and it prompts you for a password.
This VI is run by C:\Program Files\National Instruments\LabVIEW 7.0\resource\system\HelpServer.llb\HelpServer__NATIONAL INSTRUMENTS.vi
There's also C:\Program Files\National Instruments\LabVIEW 7.0\help\_exfinder.llb\Example Finder Launcher.vi.
Tyring to open this VI starts the NI Example Finder. Note the taskbar icon which is different from the normal VI icon.
It seems like NI is trying to keep us out, even if it used LabView to develop the Example Finder.

How to find out the labview-version of a vi

Hello,
is there a way to find out the labview-version of a vi?
I have different projects here and o am not sure which project is created with which labview-version.
Now i can do it manually to open each vi with different lv-version and check when i can opn it.
Or is there a tool that can do this for me?
thanks for tips

TedAnderson wrote:
Ultimately I wrote the utility that I'm attaching to this post. It's in LV2012, so it will only report LV versions up through 2012.
This isn't true at all. The "Get VI Version" invoke node will return the version of the VI, regardless of the development environment. If you used that property in LabVIEW 7.1 and the VI file was a 2013 it will return the version 2013 which is the version of the VI, not the version of the developement environment.
My utility will examine all vi, vit, and ctl files. lvproj files throw error 1059 when input to Get VI Reference.
This is because the project is not a VI and getting the VI reference to a non VI file throws an error. To do this you would need to use the Project >> Open Invoke node to get a reference to the project, and then use that reference to get the version.
I also couldn't help but notice you aren't closing any of your references that you are opening. This will mean each time you run this VI your memory will increase. It will also increase much faster with a larger number of VIs. Put a Close Reference function closing all the VI references you open.
If you are interested in reading the version from disk instead of opening references you will need to look at the "vers" block data in the VI. Assembling it is a little bit of a pain but you can figure it out if you know the version you are looking for when developing the code.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

How do I find broken aliases

I relocated some of the files on my iMac, not I don't know if such move has invalidated any existing aliases. I want to find all the broken aliases.
I looked into Spotlight. It does not seem to have an option to do so.
I opened the command window and tried to use the good old UNIX "find" command.
find -L . -type l -print
Only the good linked files are shown. All the broken alias (i.e. the alias points to a non-existing file because it moved or deleted) were not shown. I used one of the known broken alias to test if the search was effective. The answer is no. The broken alias is displayed as a zero size file. The UNIX "ls -l" command does not even show the "l" indicator in the permission code. A valid alias is shown with the "l".
Please tell me if you know any trick to find all the broken aliases.
Thanks in advance.

Thanks for the information. For some reason, my file system still have a few invalid aliases. They may or may not be caused by the file move. They may be caused by changes in my external drive. Perhaps something was changed off-line or while I was in another login account. Apparently if User1 and user2 both have an alias on a file and when user1 move that file, user2 alias will not be updated. It may not have happened like that, but it appears to.
Other than buying a software for the task. Is there anyway to find broken aliases using out-of-the-box Apple software tools?

In Example Finder, I can't open the example, error: server not running

It say's the web server is not running when I try to click into any examples. It's installed under academic license 12.0.1.f3

Hello,
Does this issue only occur when you are logged on to the Domain? In other words, if you donot log on to the network does the example finder work correctly then? If so then you probably have to ask your System Administrator to allow access for the NI System Web server in your Firewall.
A good resource for finding out what ports should be opened in the Firewaal to have NI SW work correctly is:
http://digital.ni.com/public.nsf/allkb/CEF5A3568A5DA71D8625732800520EA1?OpenDocument
Regards,
Rik Prins, CLD
Applications Engineering Specialist Northern Europe, National Instruments
Please tip your answer providers with kudos.
Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense

Example finder不能用了

请查看我发的附件，那是我打开NI example finder时弹出的画面，不知道是什么原因，我可以看到例子，但是双击无法打开。
谢谢
附件:
example.JPG ‏9 KB

You could refer the two website as follows:
http://digital.ni.com/public.nsf/websearch/32B30FC6CC22A06C86256E59007F79A9?OpenDocument
http://digital.ni.com/public.nsf/websearch/BB4F052E48D9476186256FFD0067A992?OpenDocument

Finding an example to run on labview 7 w/6025E

We bought a 6025E, have the Labview 7 Express eval SW. It appears that we can only modify existing code so it appears to us that we have to find a suitable example to run on our system. (OT we spent a lot of time looking for something called DIO Port 2.vi for one of the examples)
DOes anyone out there have example code that we can use to evaluate labview 7 and the 6025E?
Many thanks for reading, more of course for any assistance......
Rob Roy

"Hello JDesRosier;
Yes, we have purchased a 6025E card and want to evaluate which application (Labview Express or LabWindows) to purchase. Our plan is to use the demo of labview 7 express first to develop a simple test, and then use the labwindows demo to develop and evaluate the same test. This would give us a good feel (we thought) for which product we want to purchase. Our problem appears to be that without a license (Labview or LabWindows) we can only modify an existing task, channel, or scale according the measurement explorer. We are not sure what that (Message from ME) really means except that we are left to wonder what it means not having experience with the products.
We need an example program that we can use directly or modify for the 60
25E card that will give us a sense of what the test programming will be like in Labview 7 express. Our test scenario is to set a state, read our inputs, wait a period of time, change state, read our inputs, wait a period of time. We would like to use a spread sheet form to control the output states and compare the input states against, as well as set the period of time for each state. Setting a state includes setting the direction register for those ports or bits that can be set. If this is an easy demo or if it already exists in a state that we should be able to use and evaluate then please point us to the right location or source.
Our operating system is Windows XP Pro, internet connected, and can be set to host for GOTOMYPC or Windows remote assistance should there be an active interest in getting us going. We have a contractor in house whose job it was to set up a demo test but we are afraid that we shackled his efforts by not having the software already purchased. Is this a f
air assumption?
Your thoughts, assistive actions, and criticism is welcome.
Sincerely,
Rob Roy

Picture alias in finder broken

Sorry for the bad subject title, and english i suppose.
In Finder you have on the left side a menu with shortcuts.
One of them is the Picture alias, if you drop a jpg on this, you can see a green PLUS button, and the folder pictures wil open.
If i do this once, it is oke, but when i go back to, for example documents, and want's to do the same trick, i get a error message says, that the pad cannot be found.
So i have to delete the alias, en place a new one.
The same will happen, i can use it once, en the second time the link is broken.
Does someone know a solution?

Log back into your normal user account:
Here's the whole litany for thoroughly checking your home folder.
1. Navigate to ~(YourHome/Library/Fonts - drag this folder to the desktop.
• Restart and test your applications.
• If they work start adding the fonts back few at a time.
( Likely suspects are Times RO & Helvetica Fractions, also if you do not use Classic you can trash the classic fonts.)
2. Check Preferences Thoroughly;
• Navigate to ~(YourHome/Library/Preferences drag this folder to the desktop.
• Restart and test your applications.
• If this works, save the old preferences folder somewhere else or on disk, name it "old prefs" .
** Note: A very important file is the "com.apple.Mail.plist" preference file located in the Preferences folder which contains all email account settings and general mail preferences (hold this one and replace if your problem is not with Mail).
You'll have to go through some of your System Preferences and apps to set the preferences back to how you like them. (Or if you have the time and inclination, "cherry pick" through until you find the problem one or two.)
3. Check Permissions Inside Home Folder
• Navigate to YourHome/Library.
• Get Info (Command - i) on folders for apps you are having problems with.
• Open the "Ownership & permissions" disclosure triangle.
• Make sure you are the owner, with "read and write" access.
• Click on "apply to all"
• If this is correct, open the "Applications Support" folder and do the same procedure (Command+I) for the folders with the names of the applications you are having trouble with.
Note:
The reason to check this is because repairing permissions with Disk Utility doesn't touch permissions inside your home folder.
4. Navigate to YourHome/Library/Caches and drag this folder to the trash, then log out and back or restart. There is no need to replace this folder.
-mj
[email protected]

VI documentation feature broken in labview 8.0, 8.20, 8.21, 8.5

The VI documentation feature is broken. Descriptions of type def controls are not added to the vi documentation report. Also, all the clusters are parsed and inserted in the control tables wrong. Independent cluster controls show up as elements of other clusters.
Since we've been through four releases without a fix, does anyone know f this feature is supported anymore? It is useless in its current state, so it seems as though it isn't.
-Devin
I got 99 problems but 8.6 ain't one.

tst,
I am using vi documentation to create help files for an API I am working on. The API will be distributed to customers of a new embedded motion control product my company makes to provide labview support. So I am simply printing documentatin to rtf files from my API vi's with vi descriptions, icons, and controls to make it look just like NI's help files for their vi's. Once I have them all created I will import them into a chm file with a utility I have. Then I'll go back and link them in the vi's so the API will be self-documenting and have help files attached to everything. And it will all go in a big source distribution. I don't think I'm doing anything weird here. This seems like it is exactly how NI would recommend it.
The problem source distributions are broken and so is vi documentation in 8.0, 8.2, and 8.21, and vi doc is still broken in 8.5. But I can't ship the API in 8.5 anyway because our customers probably won't have it yet.
So yeah in the first thread I just posted about descriptions not being included. But I am also seeing error clusters, for example, included inside all my waveform controls. Is there an error cluster inside a waveform control that I don't know about? I've never seen that before.
-Devin
I got 99 problems but 8.6 ain't one.

Finder Broken

So I'm pretty sure that the logmein software (logmein.com) has somehow broken my Finder or a link between the System and the Finder. I've uninstalled logmein, but the damage has been done. Here's what's happening...
My computer is set to turn on in the morning before I get to work, then perform backups and shutdown after I leave. But lately it hasn't been working. When I come in the morning, my computer is on and logged in, but I have a blank desktop (with my desktop photo showing). No desktop files or alias', no Macintosh HD. I can click on the Finder icon in the dock and it all comes back and works fine throughout the day. But it doesn't seem to be shutting down at night. When I manually perform a shutdown (normal - through the apple menu), all the apps will shutdown properly, and the Finder will quit. But the computer doesn't shut off. It looks like it does in the morning with the blank desktop. The only way to turn off the machine is a hard boot.
So how do I fix that? I'm guessing a reinstall of the OS would get it done, but I'm looking for a less nuclear solution. Any ideas?

Perhaps when you removed the app which may have caused this issue,
not all of it went away. Did it include its own Uninstaller as part of the app?
If not, there are free ware Uninstall apps available for download that can
help find parts of applications that were installed into locations where the
bits won't get trashed by a simple drag or move to trash action.
I've looked around and there are a few free-ware ones, per this example.
• AppCleaner v. 1.1.2 (for 10.4 & later) - actually 'donationware' runs free:
http://www.freemacsoft.net/AppCleaner/
A variety of Uninstall apps for Mac are listed online, such as this page shows:
• *Uninstallers for Mac*:
http://download.cnet.com/mac/uninstallers/3150-2096_4-0.html
There may be other ways to schedule what you want, perhaps via a different
application; and just maybe one of the other choices is more compatible(?)
In this matter, I have no immediate ideas of my own, however.
Since I recently acquired another Mac, not a replacement for any others, it
is running Leopard 10.5.8 and fully updated as of yesterday; a G4 mini.
The others all are running Tiger 10.4.11 (and gracefully) so I am starting to
remember what put me off about Leopard 10.5 in the first place, years ago.
Hopefully you won't have to go as far as another install; that should not be
required. There may be some trail of information in the computer's logs;
either in Console (several, won't apply to the matter) or maybe in Profiler.
Some logs show all kinds of stuff going on behind the scenes and of those,
there would likely be evidence. Here is another info source for ideas:
• Uninstalling Applications in Mac OS X:
http://guides.macrumors.com/UninstallingApplications_in_Mac_OSX
Does a second user account exhibit any odd effects, or is the issue confined
only to the main User account? You could set up a new admin level user and
migrate your basic stuff over to it, being careful to not move everything over.
Then delete the old user account, if the issue can be shown to reside there.
In fact, you could probably find the cause and be rid of it. There may be some
preference .plist kinds of files created by the app in question, to be removed.
But I have no idea to what extent that would involve looking into it.
Good luck, & happy computing!

My compiled help files was working and now is broken in LabVIEW 2009

I've created a .chm file for distributing an add-on VI Library. In order to get my product certified as "LabVIEW compatible", a help file with pretty good documentation is required. Using the Microsoft Help Workshop, I have created a .chm file that works in LabVIEW 8.5 and 8.6. Once I distribute to LabVIEW 2009, the javascript portions of the help file fail. These functions are:
1) Place on Block diagram
2) Find on Functions Palette
3) Open Example
I have determined that this is due to a variable written in NI glang.chm file. The file internal to the chm file is called "lvversion.js" and contains a variable named "lvversion". The marketing decision to name the product "LabVIEW 2009" has contributed to this problem since this variable is equal to "9.0.0", yet the path is (typically) C:\Program Files\National Instruments\LabVIEW 2009\help
I originally decompiled NIs glang.chm file to analyze the javascript functions that are required for the above 3 buttons to work.I found that NI hardcodes the URL of the help services in a file called "helpserver.js" to be something like "http://127.0.0.1:3580/National%20Instruments/LabVIEW/LabVIEW {major-version}" where major version is "8.5" rather than "8.5.1"
A call to the function "openProj" would then look something like:
http://127.0.0.1:3580/National%20Instruments/LabVIEW/LabVIEW 8.5/OpenVIFromHelp?PROJ=myProject.lvproj
NI hardcodes these URL in glang.chm::/helpserver.js, and I would gladly read them directly if Javascript were less crippled. Since that hasn't worked yet, I did a regular expression in javascript to determine the version based on the path of the document. This worked until LabVIEW 2009 where the path is (typically):
C:\Program Files\National Instruments\LabVIEW 2009
but the version in glang.chm::/lvversion is "9.0.0"
Yes, I can workaround that by doing some javascript that says:
if(version == 2009)
            version = "9.0"
        else
            version = version
However, when 9.0.1 comes out, will it be LabVIEW 2009 still, or LabVIEW 2010? I'd like my javascript code to decoupled from any particular version so I don't have to relase a new version of my toolkit for each LabVIEW major or minor release.

OK I finally worked around this. Here is some javascript code that will look for a file called "lvversion.js" inside the <LabVIEW Directory>\help\glang.chm file. save this as a javascript file named "myjavascript.js"
var path=getPath();
function getPath() {
path = unescape(location.pathname); //replace %20 with " ", etc.
path = path.replace("@MSITStore:","");
path = path.replace(/\w+.html/,""); //strip off .html file
path = path.replace(/\w+.chm::./,""); //strip off .chm file
//Write javascript paths to page. Helpserver URL is hardcoded in each LabVIEW version
document.writeln("<script src=\"ms-its:" + path + "glang.chm::/lvversion.js\"></"+"script>");
document.writeln("<script src=\"ms-its:" + path + "glang.chm::/helpserver.js\"></"+"script>");
return path;
Then refer to it in an html document that will be compiled into a .chm file along with the javascript.
<script src="myjavascript.js" type="text/javascript"></script>
Now when you call functions from NI's glang.chm::/helpserver.js file, you won't need to prepend and URL or path information to the function to determine which version of LabVIEW you are in. I tested this on 8.5, 8.6, and 2009 and it now pulls up all my examples properly in all of those versions. The following demnostrates a call to "openProj" which opens a project containing all of my examples from a javascript button in the detailed help .html file that gets compiled into the .chm file:
<p class="Body">Refer to the Read From Mobile Registry VI in the <span class="Monospace">labview\user.lib\mobile_registry\examples\Mobile Registry Examples.lvproj</span> for an example of using the Close Registry Key VI.</p><p class="Body"><a href="javascript&colon;openProj('user.lib%5C%5Cmobile_registry%5C%5Cexamples%5C%5CMobile%20Registry%20Examples.lvproj');"><img src="minibutton.gif" border="0"></a> Open example&nbsp</p>

Example study problems for Labview

I've found 3 sample Labview study problems, on the NI website, that are intended to be used as practice tests for the CLD. These posts were the Traffic Light Controller, the Security System and the Car Wash problems.
Does anybody know of an area where I can find more LV example problems to practice with that are similiar in scope to these problems?

If you can solve the example exams that they provide in the 4 hour limit then you have a good chance of passing. This means lock yourself in a room, start from scratch, and code for 4 hours straight and see what you have at the end of 4 hours. It is not the same as programming 1 hour a day for four days. Keep in mind that you need to read and follow the LabVIEW style guide to the best of your ability. As it states on the sample exams:
Programming style (15 points)
Functionality (15 points)
Documentation (10 points)
This means that you get 15 points (37.5%) to make it work. If you don't do the documentation or have good programming style you will fail. Based on my personal experience if you have less than two years of solid LabVIEW then the prep course would be a good choice. This assumes that you have good programming style and use all that is recommended in the exam and LabVIEW style guide.
Matt
Matthew Fitzsimons
Certified LabVIEW Architect
LabVIEW 6.1 ... 2013, LVOOP, GOOP, TestStand, DAQ, and Vison

Urgent! How can I find broken VIs reported by TS 3.0 deployment

Having problem resolving errors. TestStand 3.0 and Labview 7.0

Hi Sharlan,
Mass-compiling the folder(s) containing the VIs you are calling in your TestStand sequence(s) is the easiest way to find the broken VIs. To do this, startup LabVIEW, click Tools >> Advanced >> Mass Compile.
David Mc.
NI Applications Engineer

Example Finder broken in LabView 7.1 in OS-X 10.4?

Similar Messages

Maybe you are looking for