Community Browser
cancel
Showing results for 
Search instead for 
Did you mean: 

Designing LabVIEW NXG: Migration

Active Participant

From the early days of LabVIEW NXG development, NI R&D realized we needed to provide a mechanism for users to migrate their code to LabVIEW NXG. Many of you use your own templates when starting new projects or leverage libraries of reusable VIs that you have developed over years. Using that IP saves you time and money during development, and we want that same IP to be available to you when you start projects in LabVIEW NXG.  

 

 

Reducing Risk With Conversion  

 

 

We designed the Code Conversion Utility for LabVIEW NXG for migrating small to medium-size projects and libraries from supported versions of LabVIEW to LabVIEW NXG. While the language of G is mostly the same, there are some fundamental differences between LabVIEW and LabVIEW NXG that make this migration more complex than those you may have done in the past. Unlike moving projects between versions of LabVIEW, the Code Conversion Utility creates an entirely new version of the converted project on disk, and the original files are untouched. This means you can evaluate how your project or library migrates without any risk to your existing code.  

 

Not everything that exists in LabVIEW has an exact equivalent in LabVIEW NXG. In some cases, this is because the equivalent feature is not ready yet. You can review the LabVIEW NXG Roadmap for an idea of when those features are coming.  

 

In other cases, the best practices may have changed, or there may have been a fundamental change in technology. Panel design is an example of the latter. While we’re very excited about the modern and innovative panel editor (and can’t wait to see what you build with it), it’s changed drastically in LabVIEW NXG, and migrating VIs with complex LabVIEW front panels is challenging.  

 

 

Letting Users Decide What Matters 

 

 

From discussions with many of you, we realized it’s key that we don’t try to decide which changes are important for a user. The Code Conversion Utility generates a comprehensive, interactive report that lists all changes that occurred during conversion, so you can decide which changes are important to you.  

 

We’ve been putting the utility through its paces by using the Code Conversion Utility extensively within NI to migrate our own libraries vi.lib, dozens of NI drivers, and more than a thousand instrument drivers on IDNet to LabVIEW NXG 

 

We’re excited to see the amazing things all of you achieve with LabVIEW NXG. The Code Conversion Utility is just one tool to help you make the transition. 

 

If you want to delve into this further or need help with migration, look for NI Alliance Partners in the Partner Migration Services Program. These migration experts are happy to help you and your projects get up and running in LabVIEW NXG! 

 

Read more about designing LabVIEW NXG >>