The challenge for NI will be keeping three groups happy including existing users as well as those moving to LabVIEW 2017 and LabVIEW NXG. LabVIEW NXG will be the base for the merged versions. In the meantime, projects using compatible subsets can be moved from earlier versions of LabVIEW and LabVIEW 2017 to LabVIEW NXG. NI will be combining the two forks together in the future. Integrated exploration and analysis tools allow LabVIEW NXG users to quickly examine information accessible to the hardware without writing application code. It includes new exploration and analysis tools (Fig. It is designed improve the experience for new users, providing more intuitive support for its graphical programming environment. LabVIEW NXG brings a new IDE and approach to the LabVIEW arena. LabVIEW NXG was a blank slate developed in parallel with LabVIEW 2017, making it difficult to incorporate all the latest features, and even some existing features that are more complicated to support initially. The connections can handle all data types, from scalars to clusters and objects. Channel-wire support for FPGAs provides an asynchronous communication support for user-defined malleable virtual instruments (VIs). It is designed to simplify programming data transfer between parallel loops. The new version adds a channel wire to the IDE. LabVIEW NXG brings a new look-and-feel to the LabVIEW IDE. RTI’s latest DDS incarnation supports OMG’s new security standard for DDS.ġ. It is upward compatible, and adds new features like integration with Real Time Innovations' Connext DDS using the RTI DDS Toolkit for LabVIEW. LabVIEW 2017 is essentially an improved version of the prior incarnation of LabVIEW. NI is delivering two partially compatible versions: LabVIEW 2017 and LabVIEW NXG (Fig. I think NI’s approach is the more successful of the two. They have taken a different approach to bringing new technology to the table. Two tools I have been using have come to this juncture: National Instruments’ (NI) LabVIEW and Mozilla’s Firefox.
It may be years before some software gets tossed to the dustbin, but these days it often winds up as open source with the hopes that it becomes someone else’s opportunity (problem). Often the retiring of software is done with experimental tools. Microsoft does a pretty good job supporting its users and developers, but it still retires technologies after a long period of time. Regardless, it’s important to maintain compatibility when there are many users since they may take to the hills and use other software if migration to a new platform is too painful. It is one of the successes, and the bane, of platforms like Microsoft Windows.
0 kommentar(er)
