Much of the software engineering industry uses testing techniques that aren't often available to those of us in the embedded industry. In my experience, this has definitely been true of automated UI testing while working on ISOBUS VT clients. In a previous position, I spent much of my time creating test frameworks, including those for testing web applications through the UI.
Regular DISTek blog readers will have noticed that we took a VT server implementation to AEF PlugFest in spring 2017. Part of our motivation from the start of this project has been to give VT client developers the ability to automate functional testing of their applications.
If you’re a regular reader of this blog, then you probably know a lot of about the areas that DISTek works within. Our expertise ranges across the off-highway vehicle industry (including agriculture, construction, and forestry) with engineers that specialize in a variety of disciplines. Out of convenience, we typically group these disciplines into three big areas (“embedded software”, “automation and test”, and “modeling and simulation”), but the reality is that we do all kinds of projects that cross-over between these disciplines.
Another year has come and gone and many eventful happenings took place in the history of DISTek. We may look back at 2015 as a turning point due to the substantial changes we made in all aspects of our business. Those end-of-the-year cards you get in the mail always seem to be bragging a little too much, but that is just what I am going to do because I think the year DISTek had is worth bragging about.
In college, I had a physics class called Modeling and Simulation of Physics Systems in which students wrote code to model the physical behavior of various systems. The final project of the class involved choosing a system of interest, developing a model for it, and presenting the results with some sensatory aid.
The last two months we have covered how to do data acquisition in .NET. This month we will go over how to integrate LabVIEW and .NET together in a hybrid application. I am going to demonstrate how to use a LabVIEW server application to acquire data using DAQmx and send it to a .NET client application. The client can then display the data using more visually appealing Microsoft controls and then sends the data back to the server to demonstrate two-way TCP communication.
Last month we discussed a little bit about what National Instruments DAQmx and Measurement Studio are and how they can be used to create .NET applications which leverage National Instruments data acquisition hardware. This month we are going to jump in to a high-level practical explanation on how to get started doing data acquisition in .NET.
National Instruments provides a wide array of data acquisition hardware for use in many platforms, operating systems, and busses. The most common way provided to interface with the hardware is through the NI-DAQmx drivers. These DAQmx drivers can be used to interface with hundreds of different DAQ devices across several different application development platforms. In this three part blog series, we are going to explore specifically how to use National Instruments data acquisition hardware in .NET applications. Part one will introduce a little bit of background into DAQmx and Measurement Studio. Part two will explain how to get started in adding National Instruments hardware to your .NET project. Finally, part three will provide some examples for hybrid systems combining LabVIEW and .NET as a way to fully utilize National Instruments hardware while retaining the advantages of .NET.
A few months ago in this blog I gave a very broad overview of Task Controller (TC). The Virtual Terminal is probably the best-known ISOBUS feature given its visual prominence, but TC is a popular topic to discuss in the ISOBUS world because it offers many intriguing possibilities … and seeks to fulfill many of the promises of precision agriculture across manufacturers. I thought it would be useful to spell out some of the details of TC as it can be a quite confusing subject. In this post, I will walk through the components and the steps of a typical TC session.