What is the difference between ISOBUS VT Version 3 and Version 4?

VIRTEC display.

The ISO 11783-6 standard was most recently released in 2010. As of this release, three common versions of the Virtual Terminal (VT) are specified. These versions are referenced in the standard as “Version 2”, “Version 3”, and “Version 4”. Based on recent ISOBUS Plugfest attendance, a survey of the industry shows a few Version 2 devices still in common use, a small number of Version 4 devices in use, and a large majority of devices using Version 3. The standard requires that an Electronic Control Unit (ECU) and a VT communicating via the VT standard should use the standard according to the lowest VT version of the pair, e.g. a VT at Version 4 and an ECU at Version 3 should use Version 3 communications.

LabVIEW Issues When Upgrading From Windows XP To Windows 7

In April 2014 Microsoft will stop supporting Windows XP. Microsoft has developed a Compatibility Toolkit (ACT) to see if your current computer will be able to support the transition to Windows 7.

LV Logo

Through experience and hard work, we’ve identified fixes to common issues moving LabVIEW to Windows 7. Some of the issues we have encountered during upgrades include getting administrative rights to the system and  accounting for the Windows 7 directory structure change where the files are located at “C:\Program Files (x86)\” instead of “C:\Program Files\” for non-native Windows 7 applications.

Additionally, issues may occur if your computer is part of a domain where certain Windows Services start up automatically on boot-up. If you run into a domain issue you may want to try the following:

Read more

Case Study: Vehicle Controls for an Electro-Hydraulic Construction Machine

We were asked to assist in the development of the controls for a complex construction machine using Model Based Software Design (MBSD). This was the first project in which the OEM used MBSD and therefore it was a high-visibility project.

Heavy equipment in action.

We faced many challenges in this project. The control algorithm was very complex, and had already been developed by the OEM in Matlab – the accuracy of the implementation of the algorithm was critical. Verification of the algorithm was a key component of this project. Adding to the complexity, the input signals to the system were very noisy and required disturbance rejection. Any instabilities in the system had the potential to cause injuries or property damage, so it was key to tune the system properly. Requirements for the project were also being developed in parallel to implementation.

Welcome to the DISTek Blog

Hello, I want to welcome you to the DISTek blog, a place for the talented engineering staff of DISTek Integration, Inc. to share knowledge with the world. To learn more about DISTek, who we are, and what we do, check out our website.


On this blog, look for helpful software engineering tips, case studies, and interesting experiences from our embedded software, test system design, and model based software experts.

We will also be sharing pictures and info from shows we attend, and other fun stuff too.

I would suggest adding a bookmark, there is a lot to come!