vi analyzer error 1430

[elrathia]

I was using VI Analyzer yesterday fine. This morning I fire it up after shutting LabVIEW down overnight, and I get error 1430. I'm using LabVIEW version 10. I don't understand what the error description is telling me.

What's this mean? The program runs fine.

[Doug-B]

Hey elrathia,

The error you are getting is indicating that the VI Analyzer was unable to find the path to your VI in the expected location. Did anything of note change, to your knowledge, between the time the Analyzer was working as expected and the time you started getting the error? Anything that might have changed the file path of the VI you are trying to analyze might have been the cause of this error.

Thanks,

Doug B 

[Darren · Accepted solution]

This error is happening during execution of the Modularity Index test.  If your COTS Subpanel.vi isn't broken (like with missing subVIs), then my best guess is that something is wrong with the list of excluded folders for the test.  Can you post a screenshot of your Modularity Index test configuration, like this one?  I want to see if anything looks fishy with your excluded folders list:

Ideally, you could also post the VI (and all its subVIs) to help me further investigate the issue, but I don't know if that's possible on your end.

[elrathia]

Here's the window. Looks like some paths are missing.

I added the same paths as shown in the Fan Out item and the error disappeared. I have no idea how it forgot those for that test only. I don't think I changed anything drastic.

Anyway, thanks guys for the help!

Also, how do you get images to show inline?

[Darren]

I'm glad the issue is resolved, although I'm concerned that we don't know how those <Not A Path> items showed up in the first place.  Please let me know if you see the issue again.

Oh, and you can get images to show in-line with your message with the "Insert/edit image" button in the post toolbar:

[elrathia]

Thanks. I will let you know if it recurrs.

[elrathia]

Bad news. This recurred, with a different program entirely. I am using LabVIEW 2010. Had 3 instances of 'Not a Path' in the Analyzer Config file.

[Darren]

I really don't know what could be causing this.  If you end up being able to reproduce the issue, I could possibly debug it if I had the same file structure as you, along with the config file.