VI export to text-base format for AI analysis

[dberenguer]

We would like to use AI to analyze our LabView projects, containing logic and graphic components, and assist us in the process of maintaining the code. However, LabView's source files are not something that an AI can understand. Is there any way to export VI's to something like XML, JSON or yaml? What we are looking for is a way to identify logic links between blocks, inputs and outputs, locate where a given functionality is being implemented or simply understanding what each class is doing. Our projects have become too big, with dozens of VI's and classes and understanding the code is being a challenge for anyone not having participated in the development.

Thanks in advance for your ideas,

Daniel.

[GerdW · Accepted solution]

Hi Daniel,

---

@dberenguer wrote:

Is there any way to export VI's to something like XML, JSON or yaml? What we are looking for is a way to identify logic links between blocks, inputs and outputs, locate where a given functionality is being implemented or simply understanding what each class is doing.

---

Write your own converter:

1. use LabVIEW scripting to determine the components of the VI (block diagram)
2. write all found components (and their linking) into a text file of your own formatting...

Why don't you use Nigel as it is already trained by NI?

[santo_13]

It looks like NigelAI is still at an Advisor level and uses the BD image to analyze instead of the underlying code.

[dberenguer]

First time I hear about Nigel AI. We're gonna look into it ASAP. Thanks!