There were quite a few firsts at this year's NI Week. This year, for example, the event was not held in August as usual, but in May. But it wasn't just the date that was new: for the first time, it wasn't Dr. Truchard but Alex Davern, CEO of National Instruments, who took to the keynote stage. After 40 years, 'Dr. T' handed over the reins to his successor Alex Davern at the turn of the year.

However, the real highlight of the four-day event was the long-awaited Labview NXG: Version 1.0 of Labview Next Generation was presented at the same time as Labview 2017. Labview NXG is intended to close the gap between configuration-based software - for which no programming knowledge is required - and user-defined programming.

Although Labview NXG still lags behind the established Labview in terms of functionality, it is characterized by its simpler usability. Labview NXG is therefore initially intended primarily for newcomers and occasional users. Further development is set to continue at a rapid pace: The beta version of Labview NXG 2.0 was already on display at NI Week, which will be available as a final version at the end of the year. There are many new features in terms of version management and a convenient package manager. The next versions will also make up for the difference in functionality compared to the classic Labview.

During the product presentation, Labview 'father' Jeff Kodosky will talk about the development of NXG: According to him, NI focused for a long time on providing Labview with additional functions and options. The original goal of enabling users to automate their measurement tasks as quickly and efficiently as possible was somewhat pushed into the background. This is exactly where Labview NXG comes in: Common applications can be realized with a simple, configuration-based approach. For more complex requirements, the complete, open graphical programming functions of Labview are available in the form of G-code.

New, programming-free workflows in version 1.0 increase productivity in the acquisition and iterative analysis of measurement data. The necessary program code is created in the background. For example, code sections corresponding to 50 lines of text-based code can be inserted using drag-and-drop. Labview NXG also includes a completely reprogrammed editor, which contains functions frequently requested by experienced users (for example, the long-awaited zoom function), but also offers improved user-friendliness for newcomers and occasional users. The new editor also supports the integration of a wider range of programming languages.

Two versions of Labview

However, Labview NXG 1.0 does not yet have the full range of functions of the classic Labview. This applies to both hardware support and software options, i.e. many add-ons and modules that are not yet supported. NI therefore also presented the Labview update in version 2017 at the same time. Labview NXG, on the other hand, is initially aimed at the target group of 'non-programmers'. The aim is to make the software easier to use for this group of non-traditional programmers: If you want to create a simple measurement in classic Labview, you always start with a blank VI. Like a blank sheet of paper, this can be quite intimidating. In Labview NXG, there are now Express VIs: These are tools that the user uses to configure their measurement. A single mouse click generates Labview code with, for example, 20 elements that are wired together. This code can be edited in the classic way or configured again with the Express VI tool.

For existing users, however, this function is not yet a reason to switch to Labview NXG. Jeffrey Phillips, Section Manager in Strategic Marketing for the software division of National Instruments, does not expect any rapid version changes at the moment. There is too much Labview code in use for this, which would have to be laboriously converted or is not yet supported at all.

But in the long term, Labview NXG is set to replace the classic Labview. With the next versions of Labview NXG, the range of functions is to be gradually increased until the classic versions have caught up. Even then, NI does not want to force customers to switch. Instead, users should convince themselves of the superiority of Labview NXG and switch of their own accord. Only when the majority of customers have made the switch will classic Labview slowly disappear. An exact timetable for this has not yet been set. Alex Davern assumes that this will take at least five years. And even after that, users of classic Labview will continue to receive support and bug fixes.

Labview NXG 2.0 Beta

To show where the journey is heading, National Instruments also presented the beta version of Labview NXG 2.0 at NI Week. The second version is aimed at existing users for whom the interactive workflow is not the most important feature. Instead, Labview NXG 2.0 focuses on other elements, such as system management or a better class infrastructure.

Existing customers rarely need help with the development of a software project with Labview. On the other hand, they need specific help with maintenance, administration or the portability of the user interface. The beta version of Labview NXG 2.0 therefore supports, among other things, a more open file format to enable easier internal software version management, for example. A package manager is now also integrated directly into Labview.

Another point is the support of Internet technologies with the new Web VI: A new compiler translates Labview code into Java script, which can be executed by practically all common browsers. This means that Labview programs can also be controlled from mobile devices such as smartphones or tablets.

Author:
Matthias Heise is editor of the sister magazine Elektronik

5G in the field

The 'mmWave Channel Sounder' from AT&T can be used to investigate 5G channels in the field. It is based on the mmWave transceiver system from National Instruments.

© National Instruments

5G technology also played a major role at NI Week. To realize 5G, new frequency ranges beyond 6 GHz must be developed. The mm-waves behave completely differently to previously used frequencies, so a lot of research is still needed. Millimeter waves have been used for some time, but not in mobile communications, but in satellite-based communications and in the military sector. As a result, there is very little public data on the subject, as Sarah Yost, Product Marketing Manager in the Software Defined Radio (SDR) division at National Instruments, explains.

To change this, the American telecommunications group AT&T has developed the 'mmWave Channel Sounder' and presented it at NI Week. The system consists of a transmitter and a receiver part, with which the behavior of 5G communication in the real world is to be examined. The transmitter and receiver are also designed to be mobile. The channel sounder is based on the mmWave transceiver system from National Instruments, which premiered last year. In line with this system, new 28 GHz radio receivers were presented at NI Week, which can now transmit and/or receive signals in the frequency range from 27.5 GHz to 29.5 GHz with a real-time bandwidth of 2 GHz.

The new radio receivers are compatible with the radio receivers introduced last year for the frequency range from 71 GHz to 76 GHz, which are also used in AT&T's system. Since the software is also compatible with both radio receivers, users can customize the mmWave transceiver system for the desired frequency range by simply exchanging the radio receivers. The baseband software of the mmWave transceiver system provides a complete physical layer for the 5G specifications proposed by 3GPP and Verizon, which can be used as source code in Labview.