January 2022
This file contains late breaking news about ECU Measurement and Calibration (ECUMC) Toolkit and supersedes any information found in other documentation included in the distribution.
Refer to NI Linux Technology for the most recent information about Linux support at National Instruments.
Refer to the ECU Measurement and Calibration Toolkit Release Notes for known issues, bugs fixed since the last release, and other release details.
Launching ECUMC Standalone Utilities
Using the ECU Measurement and Calibration Toolkit C API
ECUMC Toolkit software for Linux 64-bit architecture has been tested on the following distributions:
ECUMC Toolkit requires a 64-bit distribution and does not support 32-bit applications.
NI provides a repository add-on for all supported drivers that you can install using your Linux distribution's native package manager.
After the driver package(s) are installed, you must rebuild the new packages for the system kernel. NI recommends that you run the command 'dkms autoinstall' after installation, and before rebooting the system, to install the latest revision of all modules that have been installed for other kernel revisions. After doing so, the installed device drivers will function immediately on the next system start.
The following list details the hardware models supported in ECUMC Toolkit 21.5 for Linux.
1 The NI-9860 is supported only with TRC-8542 and TRC-8543 transceiver cables and installed in a cDAQ-9185 or cDAQ-9189 CompactDAQ Ethernet chassis
For more information, see Linux Limitations.
The NI-XNET Hardware Configuration Utility, nixnetconfig, is a command line interface configuration utility for Linux desktop distributions. This utility provides functionality similar to the Measurement and Automation Explorer (MAX) graphical configuration utility, which is not supported on Linux. Run nixnetconfig to start the utility and configure supported NI-XNET interfaces and devices.
You can launch the following ECUMC utilities either by desktop shortcut or by command line. Desktop shortcuts appear in your application launcher by the name of the utility. To use the command line, open a terminal window and type the executable name. For example, to launch the NI ECUMC A2L Viewer from command line, run ni-ecumc-a2l-viewer.
Desktop Shortcut | Executable | Description |
---|---|---|
NI ECUMC A2L Viewer | ni-ecumc-a2l-viewer | Use to display A2L databases for XCP and CCP. |
NI ECUMC XCP and CCP Trace | ni-ecumc-xcp-ccp-trace | Use to analyze XCP and CCP communication between your ECUMC application and ECUs. |
NI ECUMC Demo ECU XCP | ni-ecumc-demo-ecu-xcp | Contains tools to simulate ECU communication using XCP protocol. |
NI ECUMC Demo ECU CCP | ni-ecumc-demo-ecu-ccp | Contains tools to simulate ECU communication using CCP protocol. |
The following information describes how to get started using the ECUMC C API on a Linux platform.
To compile an application that uses the ECUMC C API, include the header file niemc.h at the top of the source file:
#include <niemc.h>The niemc.h header file is located in the standard include path:
/usr/includeAs niemc.h is installed to the default include directory, the compiler automatically finds it; there is no need to explicitly specify the include path to compile the program.
The ECUMC C API is provided by the library libniemcc. Use the following option in the linker command line to add the libniemcc library:
-lniemccThe libniemcc library is installed in the following directory:
/usr/lib/x86_64-linux-gnuIf required, add it to the linker's search path with the following command line option:
-L/usr/lib/x86_64-linux-gnuComplete the following steps to create a simple program using the ECUMC C API:
Use a web browser to view the ECUMC Toolkit documentation at https://www.ni.com/r/ecumchelp. You can also find a copy of the ECUMC Toolkit Help installed at /usr/share/doc/ni-ecumc.
This release includes examples showing the use of ECUMC Toolkit 21.5 in C and LabVIEW.
C examples are located in /usr/share/doc/ni-ecumc/examples. Make files are provided that link to the necessary libraries.
The LabVIEW examples are located in the LabVIEW examples directory.
The read-meas-polling.c example connects the ECU described by an A2L file and reads measurement values using XCP on CAN, XCP on CAN FD, XCP on UDP, XCP on TCP/IP, or CCP.
Before running read-meas-polling.c, copy the example to a writable location, such as the home directory, and adjust all parameters in the code to match the values used in your setup. Run the makefile provided with the example, which will generate an executable called read-meas-polling. Run this program against your ECU to capture the specified measurement values. Make sure to start your ECU before running the example. Running the example requires reading an A2L file (see declarations within the source code).
Some features discussed in the ECUMC Toolkit 21.5 documentation are unavailable on Linux.
Copyright
© 2009–2022 National Instruments Corporation. All rights reserved.
This publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.
NI respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.
Notices are located in the /usr/share/doc/ni-ecumc/NOTICES directory. EULAs are located in the /usr/share/ni/licenses directory.
If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.
Content from the IVI specifications reproduced with permission from the IVI Foundation.
The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.
Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on NI trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.
For patents covering the NI products/technology, refer to the NI Patent Notice at ni.com/patents.
378694A-01