VI Analyzer does not show up in tools menu

[shb]

According to this formum message the VI analyzer is available in normal LabVIEW. (Without most tests and no right click in Project, but it is there.) But I do not find it in the tools menu where it should be. (A printscreen is in this forum message.)

According to my answer to the first message, I must have found the menu. But now I looked for it in LabVIEW 8.6, 2012 and 2013 without finding it. The llbs are there in <LabVIEWdir>/project/_VI Analyzer, but nothing is in the tool menu. Why not?

[Stephan_D]

Hi

It is maybe necessary to install the VI Analyzer seperate. Use this link to download the 2013 version of the VI Analyzer:

http://ftp.ni.com/evaluation/labview/ekit/other/downloader/2013VIAnalyz-Win_downloader.exe

Is the VI Analyzer available in LabVIEW 2013 after the installation?

Regards,

Stephan

[shb]

According to this message installation of VI Analyzer Toolkit is *not* necessary.

[Darren · Accepted solution]

If you place your test LLBs in the [LabVIEW Data]\VI Analyzer Tests folder, they should show up in all of your LabVIEW installations without requiring installation of the VI Analyzer Toolkit (in LabVIEW 8.6 and later). Make sure the test is saved in the earliest LabVIEW version you want to support. On Windows 7, the [LabVIEW Data] folder is here:

C:\Users\[username]\Documents\LabVIEW Data

If you're still having trouble, let me know which test(s) specifically you're trying to use, and I can make sure there aren't any problems with the tests themselves.

[shb]

Right, at least one test must be in [LabVIEW Data]\VI Analyzer Tests for showing the VI Analyzer in the Tools menu. (Except if the toolkit is installed.)

How could I oversee all the notes in the LabVIEW Help (tools menu, Creating a VI Analyzer Task, ...)?

[kmurphs]

In some instances, you might have that folder "[LabVIEW Data]\VI Analyzer Tests" with some tests inside and the menu option would not show still (even after restarting LabVIEW and the PC).

Add a new test, or just duplicate one of the existing ones (you will have to restart LabVIEW after).

Note that, a couple of weeks ago, I had the same problem and the accepted answer solved it for me. Now the issue reappeared today, and this fixed it.