VI Analyzer Error 1430

[Jim_K]

Upgraded from LabVIEW 2012 SP1 to LabVIEW 2013, and I am getting error 1430 with two different projects. I am using previously saved VI Anayzer .cfg file which ran without error in LabVIEW 2012 SP1, but now both give errors with tests Fan Out and Modularity Index. How do I fix this?

Jim

[Darren]

Jim, can you post a simple project + .cfg file that demonstrates the problem?

[Jim_K]

Darren,

When I create a new project it does not have this problem. And then I tried making a new .cfg file for the existing project. Works fine. Something is happening to the old .cfg file which was created pre-LabVIEW 2012 when I open it in LabVIEW 2013. Since it doesn't take much time to record what was customized on a scrap of paper and make a new .cfg file, this is an acceptable solution to me. Only issue is that we have a .cfg file saved for every released application, so we will probably end up making a new .cfg file as we upgrade each project to LabVIEW 2013. (Since both of the existing projects I have so far opened in LabVIEW 2013 have had the same problem, I am thinking all the existing projects will have the same problem). I will ask one of my co-workers to check their projects and see if the same problem occurs.

Jim

[Darren]

Ok, Jim, keep me posted. If you want to post one of the .cfg files that's having issues, that would be great. If you want to investigate the issue more on your end, you can check out the VI Analyzer CFG Exporter on the VI Analyzer Enthusiasts community to parse the test configuration information stored in your old .cfg files.