NI Blog
-
KeaneSenses
on:
Avoid Test System Downtime This Holiday Season With CableSense™ Technology
-
Priley
on:
These are a few of our favorite things … about the LabVIEW NXG FPGA Module
-
Sumedha
on:
Designing LabVIEW NXG: Collaboration
-
Taylor_R.
on:
Designing LabVIEW NXG: Libraries
-
Sumedha
on:
Designing LabVIEW NXG: SystemDesigner
-
Darin_G
on:
Designing LabVIEW NXG: Linking
-
andre.buurman@carya on: Designing LabVIEW NXG: Introduction -
Jimmie_A.
on:
Aarhus University: A Hotbed of Forward-Thinking Innovation
-
Snacleb_23
on:
How to Take Advantage of the Industrial IoT for Predictive Maintenance Applications
-
TobiasG
on:
Announcing: Our 3GPP Compliant Reference Test Solution for New Radio
Designing LabVIEW NXG: Collaboration
As more and more businesses aim to leverage the power of collaboration, we want to ensure you and your team can develop and deliver efficiently in LabVIEW NXG while integrating with your company’s development systems.
One challenge teams face while collaborating on the same project is ensuring that all systems are up to date with all the needed dependencies. Keeping everyone informed about which toolkits and drivers to use for a project can be difficult, especially if it’s a project you’re restarting after a while.
One improvement we’ve made in this area with LabVIEW NXG 3.0 is the addition of a new “Package Dependency Document” in the project. You can “capture” your project’s software dependencies by right clicking on it. From there, the tool will inspect your code and populate this document with information on the packages (including toolkits and drivers) that your project requires. When someone who doesn’t have these packages installed opens this document, they’ll be informed and shown a button to install all the missing packages.
Since VIs are binaries, we know that working with version management tools and LabVIEW can been challenging sometimes. To help, we were mindful of this in LabVIEW NXG and made the VIs xml based.
Another struggle with version management tools that some LabVIEW users shared involved dirty dots on the caller VIs. As a result of that feedback, we introduced concepts like the dependencies being managed by the project instead of VIs, and libraries assigning namespaces.
We also have a Compare tool that you can use to compare VIs as well as project files.
We aren’t saying things are perfect with LabVIEW NXG while collaborating in big teams. We still face many challenges like complicated xml, files getting dirty when not expected sometimes, and distributed version management workflows without the ability to lock files. However, some of the core decisions in LabVIEW NXG have set us up for easier version management and collaboration in the future. Give us your feedback on how we can best improve your collaboration experience in LabVIEW NXG.
Read more about designing LabVIEW NXG >>
