NI ECU Measurement and Calibration Toolkit 2.3.1 Win32Eng NI电子控制单元测量和校准工具包ECUMC2.3.1下载

石鑫华视觉

Windows系统下（Linux和MAC系统下请自行了解清楚）NI的各种软件、模块、工具包、驱动程序，使用NI许可证管理器来激活的，绝大部分的都可以使用NI Lincense Activator来激活：NI序列号Serial Number生成激活工具NI License Activator，LabVIEW/VBAI/VDM/VAS等软件模块工具包破解工具不限版本http://visionbbs.com/thread-490-1-1.html

视觉论坛的各种NI资源，除了视觉相关的模块有使用外，大部分的都不会使用，仅提供资源不提供技术支持。资源的下载地址一般会同时提供NI官方和百度网盘的地址。某些工具包NI地址失效或没有NI地址，只能使用百度网盘地址；如果百度网盘地址失效过期，可联系论坛客服更新。NI的服务器在美国，有时候速度很慢或下载容易出错，这样会造成安装时各种错误而无法安装。建议在下载完成后，对下载资源做校验和(NI一般会提供MD5或SHA256等)验证，与官方或视觉论坛提供的校验和对比，一致就可以安装；如不一致，则需要重新下载。视觉论坛早期下载上传的资源，基本上都是正常下载的资源；2019后下载的资源，都与NI的正确校验和对比过，保证是正确的资源才上传到百度网盘。校验和工具下载地址：文件Hash计算器FHash，文件校验和验证下载文件正确性验证，MD5值计算、SHA1值计算、SHA256值计算、CRC32值计算http://visionbbs.com/thread-26524-1-1.html

NI ECU Measurement and Calibration Toolkit 2.3.1 Win32Eng NI电子控制单元测量和校准工具包ECUMC2.3.1下载

ECU测量和校准工具包
ECU测量和校准（ECUMC）工具包用于为电子控制单元（ECU）设计和验证提供测量和校准。
ECU测量和校准工具包是LabVIEW、LabWindows/CVI和Microsoft C/C ++编程环境的软件附件。该软件支持通用测量和校准协议（Universal Measurement and Calibration Protocol，XCP）及CAN校准协议（CAN Calibration Protocol，CCP），提供了许多高级且易用的函数。这些协议可让用户可根据ASAM (.A2L)数据库文件的定义，读写内部ECU变量及特性。通过(.A2L)数据库文件，工具包自动应用所有换算信息并以工程单位返回数据，便于简单地分析、演示及记录。此外，该工具包还提供了常见应用的示例，例如使用一维到三维用户界面来测量ECU变量或控制ECU特性。LabWindows标志经Microsoft公司授权使用。Windows是Microsoft公司在美国和其他国家的注册商标。


2.3.1（在NI官网还有2.2/2.3版本，但是我方未能找到相关资源，无法提供下载）

2.3.1版本未找到单独的安装版本，但是可以通过2013Fall或2014Spring的核心开发套件的SRLDVD进行安装。

NI Developer Suite 2013 Fall Win32/64 Eng/Chn NI核心开发套件2013秋季版 基于LabVIEW 2013版
http://visionbbs.com/thread-25059-1-1.html

NI Developer Suite 2014 Spring Win32/64 Eng/Chn NI核心开发套件2014春季版 基于LabVIEW 2013SP1版
http://visionbbs.com/thread-25060-1-1.html

ECU Measurement and Calibration Toolkit (ECU M&C) 2.3.1 Readme

June 2013

Thank you for using National Instruments products.

For more information about this product, refer to ni.com/support.

This file contains information about the ECU Measurement and Calibration Toolkit (ECU M&C) Software for Windows 7/Vista/XP and LabVIEW™ Real-Time (RT). Information in this file is in the following sections:

Documentation

Installation

Installing the ECU Measurement and Calibration Toolkit with a LabWindows/CVI Upgrade

Supported Operating Systems

Supported Software and Hardware

Supported Development Environments

ECU Simulator

Using LabVIEW Real-Time (RT)

New Features Compared to ECU M&C Toolkit 1.0

New Features Compared to ECU M&C Toolkit 2.0

New Features Compared to ECU M&C Toolkit 2.1

New Features Compared to ECU M&C Toolkit 2.1.2

New Features Compared to ECU M&C Toolkit 2.1.4

New Features Compared to ECU M&C Toolkit 2.1.5

New Features Compared to ECU M&C Toolkit 2.2

New Features Compared to ECU M&C Toolkit 2.2.1

New Features Compared to ECU M&C Toolkit 2.3

Additional Programming Topics and Known Issues

Additional Topics and Known Issues for use of XCP/CCP Custom Device for NI VeriStand

Bug Fixes

Automating the Installation of NI Products

How to Use NI Software with Microsoft Windows 8

Important Information

---

Documentation

The ECU Measurement and Calibration Toolkit User Manual is the primary reference document. This manual includes an introduction to the CAN Calibration Protocol (CCP) and Measurement and Calibration Protocol (XCP). It also explains how to get started with application development and includes a complete reference for all ECU M&C Toolkit functions.

The ECU Measurement and Calibration Toolkit User Manual is in Adobe Acrobat Portable Document Format (PDF). You can download the Acrobat Reader for free at www.adobe.com.

You can open the ECU Measurement and Calibration Toolkit User Manual from Start» Programs»National Instruments»ECU MC Toolkit»ECU Measurement and Calibration Toolkit Manual.

Links to the NI-CAN Hardware and Software Manual are in the online help for each NI-CAN function within the National Instruments LabVIEW and LabWindows™/CVI™ development environments.

Online help for the NI-CAN features within Measurement & Automation Explorer (MAX) is in the MAX Help Topics menu. The MAX help topics for NI-CAN also include a link to the NI-CAN Hardware and Software Manual.

Back to Top

---

Installation

Before installing the ECU M&C Toolkit software, log on as Administrator or as a user with Administrator privileges. The ECU M&C Toolkit software setup program must have Administrator privileges because the program modifies the configuration registry of your system. Complete the following steps to install the ECU M&C Toolkit software:

• Insert the ECU M&C Toolkit software CD into your CD-ROM drive. The installer launches if your CD-ROM drive plays data CDs automatically. If the installer does not launch automatically, navigate to the CD using Windows Explorer and launch the autorun.exe file from your ECU M&C Toolkit Software CD.
• The installation wizard guides you through the necessary steps to install the ECU M&C Toolkit software. You can go back and change values where appropriate by clicking the Back button. You can exit the setup where appropriate by clicking Cancel.
• When the installation is complete, click Finish.
  

Back to Top

---

Installing the ECU Measurement and Calibration Toolkit with a LabWindows/CVI Upgrade

When you execute a LabWindows/CVI upgrade, and the ECU Measurement and Calibration Toolkit is installed on your computer, the ECU Measurement and Calibration Toolkit supports the earlier LabWindows/CVI version.

To use the ECU Measurement and Calibration Toolkit in the new LabWindows/CVI version, complete the following steps:

• Uninstall the ECU Measurement and Calibration Toolkit using the Windows Control Panel (Add or Remove Programs»National Instruments Software»NI ECU Measurement and Calibration Toolkit).
• Reinstall the ECU Measurement and Calibration Toolkit. The installation routine now recognizes the new LabWindows/CVI version and installs the support for the new LabWindows/CVI version.
  

Note: The ECU Measurement and Calibration Toolkit is no longer supported in the earlier LabWindows/CVI version after you complete these steps.

Back to Top

---

Supported Operating Systems

This version of the ECU M&C Toolkit software supports only the following operating systems:

• Windows 8 (32-bit and 64-bit)
• Windows 7 Service Pack (SP) 1 (32-bit and 64-bit) or newer
• Windows Vista (32-bit and 64-bit)
• Windows XP SP3(32-bit) or newer
  

For more information about using National Instruments hardware and software products with Windows 7, refer to ni.com/windows7.

National Instruments recommends using Service Pack 2 when using the USB-847x interfaces in hyperthread or multicore/CPU environments on Microsoft Windows XP.

Back to Top

---

Supported Software and Hardware

This version of the ECU M&C Toolkit software supports the following software and hardware:

• NI-CAN software version 2.7 or newer
• NI-CAN hardware supported by NI-CAN 2.7
• NI-XNET software version 1.8 or newer
• NI-XNET CAN hardware supported by NI-XNET 1.8
• CompactRIO and R-Series hardware using the NI 9852/NI 9853 CAN Module for CompactRIO
  

The ECU M&C Toolkit software supports only National Instruments CAN hardware products. For information about software for CAN products from other vendors, refer to the documentation you received with those products.

Note: PCMCIA-CAN and PCMCIA-CAN/2 interfaces are not supported on the 64-bit version of Windows Vista.

Back to Top

---

Supported Development Environments

This version of the ECU Measurement and Calibration Toolkit supports the following development environments:

• LabVIEW 2010 (32-bit), 2011 (32-bit), 2012 (32-bit), 2013 (32-bit)
• LabVIEW Real-Time (ETS) 2010, 2011, 2012, 2013
• LabWindows/CVI 8.0 or newer
• NI VeriStand 2010, NI VeriStand 2011, NI VeriStand 2012
• Microsoft Visual C/C++ 6.0
  

Note: You can use the ECU M&C Toolkit on CompactRIO or R-Series with LabVIEW 2009 or newer only.

Back to Top

---

ECU Simulator

The ECU M&C Toolkit software simulates an ECU. All ECU M&C Toolkit examples are preconfigured to communicate with the ECU simulation using the ASAM 2MC CCPECU.A2L file if using CCP or the XCPECU.A2L file if using the XCP Slave Simulator.

LabVIEW users using CCP can find the ECU simulator, seed-key DLL, and corresponding A2L file at \\Examples\ECUMC.

LabVIEW users using XCP can find the ECU simulator, seed-key DLL, and corresponding A2L file at \\Examples\ECUMC.

MS VC users using CCP can find the ECU simulator, seed-key DLL, and corresponding A2L file at C:\Documents and Settings\All Users\Documents\National Instruments\ECU Measurement and Calibration Toolkit\Examples\MS Visual C\CCPECU.

MS VC users using XCP can find the ECU simulator, seed-key DLL, and corresponding A2L file at C:\Documents and Settings\All Users\Documents\National Instruments\ECU Measurement and Calibration Toolkit\Examples\MS Visual C\XCPECU.

Back to Top

---

Using LabVIEW Real-Time (RT)

To use the ECU M&C Toolkit on a LabVIEW RT system, you must download your ASAM 2MC database (*.A2L) file to the RT target. The LabVIEW Real-Time Engine running on the PXI LabVIEW Real-Time controller supports a File Transfer Protocol (FTP) server. You can access the LabVIEW RT target FTP server using any standard FTP utility for transferring files to and from the hard drive or CompactFlash. For further information about how to download your A2L file to the RT target, refer to LabVIEW Real-Time (RT) Configuration in the ECU Measurement and Calibration Toolkit User Manual.

Back to Top

---

New Features Compared to ECU M&C Toolkit 1.0

The ECU M&C Toolkit 2.0 release adds the following features:

• Support for Universal Measurement and Calibration Protocol (XCP) on CAN and Ethernet (TCP and UDP).
• New property for Measurements and Characteristics: Comment.
• New property for DAQ Lists: Samples Pending.
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.0

The ECU M&C Toolkit 2.1 release adds the following features:

• Support for LabVIEW 8.2.0.
• New MC DAQ List Initialize VI for LabVIEW and mcDAQListInitialize function for C define a DAQ list on a specific DAQ list number.
• Support for the 32 and 64-bit versions of Windows Vista.
• You now can write the X axis of a characteristic using the mcPropChar_X_Axis property.
• You now can write the Y axis of a characteristic using the mcPropChar_Y_Axis property.
• You can change the byte order of a characteristic from Intel to Motorola and vice versa using the mcPropChar_ByteOrder property.
• You can change the byte order of a measurement from Intel to Motorola and vice versa using the mcPropMeas_ByteOrder property.
• Support for NI USB-8473 (1-port, High-Speed CAN, USB interface) and NI USB-8473s (1-port, High-Speed CAN, USB interface with synchronization).
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.1

The ECU M&C Toolkit 2.1.1 release adds the following features:

• Support for LabVIEW 8.5 and 8.6.
• Support for LabWindows/CVI 8.5.
• New set of functions to generate measurements without an A2L database (mcECUCreate, mcConversionCreate, mcEventCreate, and mcMeasurementCreate).
• New read mode for DAQ List to acquire DAQ List data as timestamped value pairs.
• You can activate address mapping if defined in an A2L database using the mcPropECU_MappingMode property.
• You can specify distinct mapping directions if defined in an A2L database using the mcPropECU_MappingSource and mcPropECU_MappingTarget properties.
• You can deactivate the use of the CCP command EXCHANGE_ID, which is used by default when a connection to an ECU is initiated.
• You can deactivate the use of all optional CCP commands such as GET_SEED, UNLOCK, DNLOAD_6, and more using the related properties mcPropOptCmd_xxx.
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.1.2

The ECU M&C Toolkit 2.1.2 release adds the following features:

• Support for LabVIEW 2009.
• Support of CompactRIO (Pharlap and VxWorks based targets) and R-Series.
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.1.4

The ECU M&C Toolkit 2.1.5 release adds the following features:

• Support for LabVIEW 2010.
• Removed support for LabVIEW 8.2.
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.1.5

The ECU M&C Toolkit 2.2 release adds the following features:

• Support for LabVIEW 2011.
• Removed support for LabVIEW 8.5.
• Support for NI VeriStand 2010.
• Support for NI VeriStand 2011.
• Support for Logging of CCP commands within the XCP Spy utility. The utility has been renamed into "CCP and XCP Spy"
• Support for ECU variants.
• Support for reading ECU object hierarchies out of ASAM A2L files that support the GROUP keyword.
• Support for converting measurement values into symbolic text entities.
• Native support for NI-XNET for the ECU M&C ECU simulator and all examples.
• New property mcPropDAQ_TimeSinceLastFrame to verify last received DAQ List timestamp to verify ECU connection status and DAQ List operation.
• New property mcPropECU_SeedChkDllPath to use seedkey DLLs from different location as corresponding ASAM A2L file.
• New example of how to use a remote seedkey (for example, if the original seedkey does not support the target operating system).
• The ECU MC Installer does not contain driver software for your NI-CAN or NI-XNET hardware products. Those installers are part of your hardware. You can download the latest installers from ni.com.
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.2

The ECU M&C Toolkit 2.2.1 release adds the following features:

• Support for LabVIEW 2012.
• Removed support for LabVIEW 8.6.
• Support for converting symbolic text entities into measurement values.
• New property mcPropDAQList_Name to query the name of a predefined DAQ List.
• New property mcPropDAQList_DisplayIdentifier to query the name of a predefined DAQ List Identifier.
• New property mcPropChar_Scale_Factor reads the scaling factor defined for a Characteristic in the A2L database.
• New property mcPropChar_Scale_Offset reads the scaling offset defined for a Characteristic in the A2L database.
• New property mcPropChar_Scale_Type reads the scaling type defined a Characteristic in the A2L database.
• New property mcPropChar_Scale_TextValues_Size reads the length needed to store the comma separated list of text values that can be converted into raw values.
• New property mcPropChar_Scale_TextValues reads the comma-separated list of text values that can be converted into raw values.
• New function mcTextToDouble converts a numerical value to a text string using an enumeration or range text scaling.
• New features within the XCP/CCP Custom Device for NI VeriStand:
  
  • Support to set the Event Channel Number as decimal instead of using the Event Channel number from the A2L database.
  • Support to set the ECU Byte Order instead of using the ECU Command Byte Order from the A2L database.
  • Support to set the Command Byte Order instead of using the Command Byte Order from the A2L database.
  • Support to set the Delay before reconnect time. This time defines the time to wait after an CCP/XCP communication error before trying to connect to the ECU again.
  • Support to manually connect or disconnect a CCP/XCP connection. The Connect Channel allows to disconnect and reconnect the ECU when the VeriStand application is running. For example, it allows you to stop the ECU, reflash it with an external program, and restart it without stopping VeriStand.
  • Support to use Multiple Master Devices in a single System Explorer Definition. (Note: Each Master must use a different Custom Device Communication Port.)
    
  
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.2.1

The ECU M&C Toolkit 2.3 release adds the following features:

• Added support for NI VeriStand 2012.
• The NI VeriStand 2012 Custom Device supports Multiple DAQ Lists with independent timing.
• The NI VeriStand 2012 Custom Device supports manually setting the DAQ List Prescaler value.
• If using NI-XNET hardware, the ECU M&C Toolkit uses Frame Queue Session by default.
• Support for reading ECU object hierarchies out of ASAM A2L files that support the FUNCTION keyword.
• Added native NI-XNET support for all CVI examples.
  

Back to Top

---

New Features Compared to ECU M&C Toolkit 2.3

The ECU M&C Toolkit 2.3.1 release adds the following features:

• Added support for LabVIEW 2013.
• Removed support for LabVIEW 2009.
• Added a new utility NI ECU MC A2L Viewer which can import and display ASAM A2L files.
• Added property mcPropECU_LogFileName in order to log CCP or XCP protocol trafic into an ASCII file. On LabVIEW RT and CompactRIO targets, the logfile is created on the target system and needs to be transferred to the host after logging has been completed. Note that no additional CAN port is used for the logging which makes this method superior to any other method like running a bus monitor in parallel.
• Added ECU timeout properties mcPropECU_XCP_Timeout_T1, mcPropECU_XCP_Timeout_T2, mcPropECU_XCP_Timeout_T3, mcPropECU_XCP_Timeout_T4, mcPropECU_XCP_Timeout_T5, mcPropECU_XCP_Timeout_T6, mcPropECU_XCP_Timeout_T7 which are defined in the ASAM XCP standard for the various XCP commands. For details which timeout applies to a specific command, please refer to the ASAM XCP standard. The values are typically read from an A2L file but may be overridden manually. Note that this value might be modified by the mcPropECU_TimingFactor property.
• Added ECU timeout properties mcPropECU_CCP_Timeout_T_std , mcPropECU_CCP_Timeout_T_pgm, mcPropECU_CCP_Timeout_T_mem, mcPropECU_CCP_Timeout_T_diag, mcPropECU_CCP_Timeout_T_act which are defined in the ASAM XCP standard.
  

Back to Top

---

Additional Programming Topics and Known Issues

ECU M&C Toolkit 2.2 supports CCP Version 2.1.

ECU M&C Toolkit 2.2 does support symbolic conversion tables for reading only. Refer to mcDoubleToText for further information.

NI-IO Trace monitors function calls to the ECU M&C Toolkit API. This tool helps in debugging programming problems in the application. To launch this tool, open the Software branch of the MAX Configuration tree, right-click NI IO Trace, and select Launch NI IO Trace. If more than one National Instruments driver is installed on your computer, you can specify which APIs to spy on at any time. By default, all installed APIs are enabled. To select the APIs to spy on, select Spy»Options, select the View Selections tab, and select the APIs under Installed API Choices.

The following LabVIEW example VIs do not run under LabVIEW Real-Time and LabVIEW Base Development System:

• Edit a characteristic.vi
• Measurement and Calibration Application.vi
  

To make these examples run, remove the subVI call from 3DDisplayWrapper.vi in MCCharacteristicsEditors.llb.

If you are using an NI USB-8473 or NI USB-8473s, the ECU M&C Toolkit is based internally on the NI-CAN Frame API. For this reason, the following properties are not available for the GetProperty function:

• CRO Task (mcPropCRODAQ_DTO_Task)
• DTO Task (mcPropDAQ_DTO_Task)
• SamplesPending (mcPropDAQ_SamplesPending)
  

The LabVIEW project examples for CompactRIO and R-Series are configured for use with NI 985x C-Series only.

The ECU M&C ECU Simulator (DemoECU) is not supported under CompactRIO.

The Basic Examples and some advanced examples are not supported under cRIO using XCP/TCP and XCP/UDP. To use those examples, you need to modify the communication parameters like the IP Address.

Errata to the ECU M&C Documentation: mcDAQReadTimestamped is documented as not waiting for messages, returning samples from messages received since the previous function call. In fact, mcDAQReadTimestamped waits until NumberOfSamplesToRead has been collected. To avoid blocking, use mcPropDAQ_SamplesPending to check the number of collected samples.

Known Functional Issue: Bug ID 407844: mcDAQReadTimestamped does not return correct timestamp information. This issue will be fixed in the next release. If you would like more information on this issue feel free to contact NI and referencing the ID number given in this document. You can contact us through any of the normal support channels including phone, email, or the discussion forums. See www.ni.com/contact to contact us.

Back to Top

---

Additional Topics and Known Issues for XCP/CCP Custom Device for NI VeriStand

ECU M&C Toolkit 2.2 supports NI VeriStand 2010 and 2011.

Refer to the XCP/CCP Custom Device online help for information about using the NI XCP/CCP Custom device with VeriStand 2010 and 2011.

Upgrade Note: If you are upgrading your XCP/CCP Custom Device from the already-installed National Instruments Developer Zone download, you need to clear the XCP/CCP controls from the NI VeriStand project temporary screen files directory.

Upgrading Existing VeriStand System Definitions From a Previous Custom Device Version: System Definitions created with an older version of the XCP/CCP Custom Device need to be mutated to the new version before they can be used. You can mutate the system definition by simply opening the System Definition file in the System Explorer and saving.

The CCP/XCP on CAN communication introduces higher busloads on the CAN network: If you are using CCP or XCP on CAN, the NI VeriStand Custom Device can add flexible configurations for reading and writing Characteristics and Measurements from the ECU. The new feature in the 2.3 release for NI VeriStand 2012 allows you to run multiple Characteristic as well as Measurement read or write tasks in parallel. If you set up such a complex system, every task introduces some amount of busload onto the CAN network, because those CCP/XCP commands are based on a handshake protocol. If you run the CCP/XCP on CAN a protocol to its limits, the introduced busload on the CAN network will increase significantly, and the ECU may not respond in the predefined time anymore. The reason is that there may not be enough free network bandwidth. In such cases, we recommended analyzing the CAN busload on the CAN network and trying to keep CAN traffic below values of 60% to 70%, to keep the network in an operable state. A typical indicator of running into such CCP/XCP on CAN protocol limits is a timeout error when executing a Characteristic/Measurement read or write operation. Therefore, we recommend checking the XCP/CCP Custom Device error status variable, whether the error 0xFFFB67FE "A timeout occurred waiting for a response from the ECU" occurs.

Back to Top

---

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed between ECU M&C Toolkit 2.1.0 and ECU M&C Toolkit 2.1.2.

If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of the ECU M&C Toolkit.

Bug ID	Fixed Issue
105783	Fixed the issue that the XCP Spy does not analyze the byte order.
105788	Fixed the issue that a XCP DAQ Lists does not work correctly if GET_DAQ_PROCESSOR_INFO is not implemented in the ECU.

The following items are the IDs and titles of a subset of issues fixed between ECU M&C Toolkit 2.1.5 and ECU M&C Toolkit 2.2.

If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of the ECU M&C Toolkit.

Bug ID	Fixed Issue
281478	If a LINEAR scaling was used in the COMPU_METHOD, the scaling was inverted (ax+b) but should be x/a-b.
282606	Each created DAQ list had the same number of ODTs, and each ODT had the same number of entries. This has been fixed so that a more local strategy is used, which saves a bit of ECU memory, and independent of whether one or two event channels are assigned to the DAQ lists.
307974	Fixed a LabVIEW exception when calling mcGetNames concurrently from two independent threads.
311204	Fixed the sporadic loss of data when reading DAQ-Lists over XCP on TCP/IP.
314259	Fixed a Multithreading Issue to access the same A2L file from two threads to read out Names and Properties in parallel.
317747	Fixed to read/write DTO or CRO properties for a XCP task instead of using the A2L file defaults.
328358	ECU MC Installer does not require NI RIO 3.2 during a cRIO installation.

The following items are the IDs and titles of a subset of issues fixed between ECU M&C Toolkit 2.2 and ECU M&C Toolkit 2.2.1.

If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of the ECU M&C Toolkit.

Bug ID	Fixed Issue
361795	Fixed the Remote Seedkey DLL to connect to the SeedKey Server on the host, when the SeedKey Client on the target has a static IP address assigned.

The following items are the IDs and titles of a subset of issues fixed between ECU M&C Toolkit 2.2.1 and ECU M&C Toolkit 2.3.0.

If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of the ECU M&C Toolkit.

Bug ID	Fixed Issue
396227	Fixed an issue for XCP use case where the EV_CMD_PENDING event did not restart the timeout.
396926	Fixed the A2L import to be able to read in PROTOCOL_LAYER "IF_DATA XCP" block.

Back to Top

---

Automating the Installation of NI Products

You can automate the installation of most NI products using command-line arguments to suppress some or all of the installer user interface and dialog boxes. However, starting with the August 2012 releases (products using NI Installers version 3.1 or later), you may need to perform additional steps before or during a silent installation of NI software.

If the NI product you are installing uses Microsoft .NET 4.0, the .NET installer may run before any NI software installs and may require a reboot before the installation of NI software begins. To avoid a .NET reboot, install .NET 4.0 separately before you install NI software.

For more information, refer to the following KnowledgeBase articles:

• For more information on silent installations of individual NI products, refer to KB 4CJDP38M, Automating the Installation of a Single Installer.
• For more information on silent installations of suited NI products, such as NI Developer Suite, refer to KB 4GGGDQH0, Automating the Installation of a Suited Installer.
• To determine what version of NI Installers your product contains, refer to KB 4CJDR18M, How Can I Determine the Type and Version of My National Instruments Installer?.
  

Back to Top

---

How to Use NI Software with Microsoft Windows 8

When you install National Instruments software on Microsoft Windows 8, you will notice a few additional tiles on the Start screen, including shortcuts to NI application software products such as NI LabVIEW, Measurement & Automation Explorer (MAX), and the new NI Launcher.

Using NI Launcher

NI Launcher helps you find and launch installed NI products. It provides you with a method of finding NI products similar to the Start menu in previous versions of Microsoft Windows. To use NI Launcher, click the NI Launcher tile on the Start screen. NI Launcher launches the desktop and opens a menu containing a list of NI products. Click any NI product to launch it.

Note  Unlike previous versions of Microsoft Windows, MAX does not appear as a desktop shortcut. You can launch MAX either from the Start screen or from within NI Launcher.

Pinning Frequently Used Applications

For convenience, you can pin your most-used NI applications, such as MAX, to either the Start screen or the Taskbar on the desktop, as necessary:

Current Application	Icon Location	Pin to Action
Windows 8 Desktop	Desktop Taskbar	Right-click application and select Pin to Taskbar
Windows 8 Desktop	Start screen	Right-click application and select Pin to Start
Windows 8 Start screen	Desktop Taskbar	Right-click application and select Pin to taskbar from the menu bar on the bottom of the screen

Finding All Programs

If you want to find a particular application or related files, such as documentation files, from the Start screen, you can access all installed files by right-clicking anywhere on the Start screen and selecting All apps. A list of all installed software and related files appears, in alphabetical order by creator or type.

For more information about NI support for Windows 8, visit ni.com/windows8.

Back to Top

---

Important Information

Copyright

© 2007–2013 National Instruments. All rights reserved.

Under the copyright laws, 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.

National Instruments 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.

End-User License Agreements and Third-Party Legal Notices

You can find end-user license agreements (EULAs) and third-party legal notices in the following locations after installation:

• Notices are located in the \_Legal Information and directories.
• EULAs are located in the \Shared\MDF\Legal\license directory.
• Review \_Legal Information.txt for information on including legal information in installers built with NI products.
  

Trademarks

Refer to the NI Trademarks and Logo Guidelines at ni.com/trademarks for information on National Instruments trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.

Members of the National Instruments Alliance Partner Program are business entities independent from National Instruments and have no agency, partnership, or joint-venture relationship with National Instruments.

Patents

For patents covering the National Instruments products/technology, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.