12-17-2021 03:21 PM
When running the "Easy VI Analysis.vi" found in the LV examples, it is also executing the Block Diagram color and Front Panel color tests found in the "C:\Users\<user>\Documents\LabVIEW Data\VI Analyzer Tests\" folder.
Removing the 2 color tests llbs from the \LabVIEW Data\VI Analyzer Tests\ folder stops them from being reported (of course)
Opening the sample.viancfg file used in the example, with both Notepad++ and the VI Analyzer tool, revealed no color tests are specified.
Steps to reproduce:
1) Exit LabVIEW
2) Copy "Block Diagram Color.llb"** and/or "Panel Color.llb" tests to "C:\Users\<user>\Documents\LabVIEW Data\VI Analyzer Tests\"
3) Open "C:\Program Files (x86)\National Instruments\LabVIEW 2020\examples\VI Analyzer Toolkit\Easy VI Analysis.vi"
4) run the vi
5) observe the extra color tests being reported (see image below)
6) exit LabVIEW and remove the 2 color tests files from the "\Documents\LabVIEW Data\VI Analyzer Tests\" folder
7) open and re-run "\examples\VI Analyzer Toolkit\Easy VI Analysis.vi"
.8) note the lack of color tests being reported
** File was renamed to something a bit more recognizable. (copyright was left in place)
Currently using LV 2020 SP1 (Ver: 20.0.1 32-bit)
01-06-2023 12:50 PM
For better or worse, the VI Analyzer API has always behaved this way (since VI Analyzer 1.0 released with LabVIEW 7.0). A VI Analyzer task (.cfg or .viancfg file) will have all tests selected when loaded in the VI Analyzer API... you would then need to write code to go in and call VIAn Select Tests.vi to disable whichever tests you don't want to run.
Sorry for the inconvenience.
01-06-2023 02:24 PM
To be clear, VI Analyzer will blindly run every test found in "C:\Users\<user>\Documents\LabVIEW Data\VI Analyzer Tests\" unless it has been specifically disabled. Well, that is not ideal.
Hopefully no one else has more custom VIA tests than I do! (not likely in my current company)