Purpose

Sets a property for the specified A2L database file, Measurement Task or Characteristic referenced by the reference in terminal. The poly VI selection determines the property to set. Format

Input

Name is not used, and can be left unwired. This parameter may be used for further extensions.
Reference in specifies a valid task handle depending on the information which has to be set. If a generic property has to be set, a db ref handle is needed. If a Measurement property has to be set, a valid DAQ ref handle has to be wired into reference in. If an ECU property has to be set, a valid ECU ref handle has to be wired into reference in.
Value is a poly output value that specifies the property value. You select the property to set as value by selecting the poly VI type. The data type of value is also determined by the poly VI selection. For information about the different properties provided by MC Set Property.vi, refer to the Poly VI Types section. To select the property, right-click the VI, go to Select Type, and select the property by name.
Error in is a cluster which describes error conditions occurring before the VI executes. If an error has already occurred, the VI returns the value of the error in cluster to error out.
status is TRUE if an error occurred. This VI is not executed when status is TRUE.
code is the error code number identifying an error. A value of 0 means success. A negative value means error: VI did not execute the intended operation. A positive value means warning: VI executed intended operation, but an informational warning is returned. For a description of the code, wire the error cluster to a LabVIEW error-handling VI, such as the Simple Error Handler.
source identifies the VI where the error occurred.

Output

Reference out is a copy of the reference in terminal which can be wired through subsequent ECU M&C VIs.
Error out describes error conditions. If the Error in cluster indicated an error, the Error out cluster contains the same information. Otherwise, Error out describes the error status of this VI.
status is TRUE if an error occurred.
code is the error code number identifying an error. A value of 0 means success. A negative value means error: VI did not execute the intended operation. A positive value means warning: VI executed intended operation, but an informational warning is returned. For a description of the code, wire the error cluster to a LabVIEW error-handling VI, such as the Simple Error Handler.
source identifies the VI where the error occurred.

Description

There are four types of properties which can be modified in the poly input value: ECU-specific properties, DAQ-specific properties, Characteristic-specific properties, and Measurement-specific properties.

ECU-Specific Properties

ECU-specific properties relate to the setting of the ECU. If you need to change a property of the ECU you need a valid ECU reference, but the ECU should not be connected. First, call MC ECU Open.vi, followed by MC Set Property.vi and then MC ECU Connect.vi. If you have already connected to the ECU, you can change an ECU property by calling MC ECU Disconnect.vi, followed by MC Set Property.vi, and then MC ECU Connect.vi again. Refer to the ECU-Specific Properties table below for a list of ECU-specific properties that can be used to define the poly input value.

DAQ-Specific Properties

You cannot set a property while the task is running. If you need to change a property prior to starting the task, call MC DAQ Initialize.vi, followed by MC Set Property.vi and then MC DAQ Start Stop.vi. After you start the task, you also can change a property by calling MC DAQ Start Stop.vi, followed by MC Set Property.vi, and then restart the task with MC DAQ Start Stop.vi. Refer to the DAQ-specific Properties table for a list of DAQ-specific properties that can be used to define the poly input value.

Poly VI Types

ECU-Specific Properties

Type Hierarchy Sub-Hierarchy Parameter Description Notes
ECU CCP — CRO Id Sets the CRO ID, which is used to send commands and data from the host to the slave device. If bit 31 (hex 0x80000000) of the value is set, the value is considered an extended CAN identifier (29-bit).
ECU CCP — Baud Rate Sets the Baud Rate used by the CAN interface with CCP protocol. This property applies to all tasks initialized with the Interface. You can specify the following basic baud rates as the numeric rate: 33333, 83333, 100000, 125000, 200000, 250000, 400000, 500000, 800000, and 1000000. You also can specify advanced (custom) baud rates depending on the interface type. Refer to the NI-XNET or NI-CAN Help for more information.
ECU CCP — Termination For all XNET devices, the termination is software selectable. XNET provides the option of 120 Ω between Bus Plus and Bus Minus or no termination. The Termination property configures the onboard termination of the NI-XNET interface CAN connector (port). The Boolean property supports two values: TRUE = Termination ON and FALSE = Termination Off. However, different CAN or LIN hardware has different termination requirements, and the termination values have different meanings. Refer to the Termination attribute in the XNET API for more details. (This property is supported for NI-XNET devices only.)
ECU CCP — Station Address Sets the Station Address of the slave device. CCP is based on the idea that several ECUs can share the same CAN Arbitration IDs for CCP communication. To avoid communication conflicts, CCP defines a Station Address that has to be unique for all ECUs sharing the same CAN Arbitration IDs. Unless an ECU has been addressed by its Station Address, the ECU must not react to CCP commands sent by the CCP master.
ECU CCP — SeedKey Cal Name Sets the filename of the SeedKey DLL used for Calibration purposes. For Remote Seedkey access (refer to the LabVIEW examples), set the name to RSK:<server ip address>,<port>.
ECU CCP — SeedKey DAQ Name Sets the filename of the SeedKey DLL used for DAQ purposes. For Remote Seedkey access (refer to the LabVIEW examples), set the name to RSK:<server ip address>,<port>.
ECU CCP — SeedKey Prog Name Sets the filename of the SeedKey DLL used for programming purposes. For Remote Seedkey access (refer to the LabVIEW examples), set the name to RSK:<server ip address>,<port>.
ECU CCP — DTO Id Sets the DTO ID, which is the CAN identifier for the Data Transmission Object (DTO). The DTO is used by the CCP slave devices to return data and status information to the application. If bit 31 (hex 0x80000000) of the value is set, the value is considered an extended CAN identifier (29-bit).
ECU CCP — Master Id Sets the identifier of the CCP master that is used by the CCP command EXCHANGE_ID as a parameter. This ID information is optional and specific to the ECU implementation. For more information about the CCP master ID, refer to the documentation for the ECU.
ECU CCP — Single Byte DAQ List? Sets the ECU to support single-byte or multi-byte DAQ list entries.

Measurement-Specific Properties

Type Hierarchy Sub-Hierarchy Parameter Description Notes
Measurement — — Byte Order Sets the specified byte order of the selected Measurement:

0—Intel format

Bytes are in little-endian order, with least-significant bit first.

1—Motorola format

Bytes are in big-endian order, with most-significant bit first.

Characteristic-Specific Properties

Type Hierarchy Sub-Hierarchy Parameter Description Notes
Characteristic — — Byte Order Sets the specified byte order of the entire Characteristic:

0—Intel format

Bytes are in little-endian order, with least-significant bit first.

1—Motorola format

Bytes are in big-endian order, with most-significant bit first.
Characteristic — — X Axis Sets the X-axis values on which the Characteristic is defined. The Characteristic dimension must be at least 1.
Characteristic — — Y Axis Sets the Y-axis values on which the Characteristic is defined. The Characteristic dimension must be 2.

DAQ-Specific Properties

Type Hierarchy Sub-Hierarchy Parameter Description Notes
DAQ — — Mode Sets the selected I/O mode for the M&C Measurement task.

0—DAQ List

The data is transmitted from the ECU in equidistant time intervals as defined in the A2L database. The data can be read back with the MC DAQ Read.vi as Single point data using sample rate = 0, or as a waveform using a sample rate > 0. Input channel data is received from the DAQ messages. Use MC DAQ Read.vi to obtain input samples as single-point, array, or waveform.

1—Polling

In this mode the data from the Measurement task is uploaded from the ECU whenever MC DAQ Read.vi is called.
DAQ — — SampleRate SampleRate specifies the timing to use for the samples of the (NI-CAN) task. The sample rate is specified in Hertz (samples per second). A sample rate of zero means to sample immediately.

For a DAQMode of mcDAQModeDAQList, SampleRate of zero means that MC DAQ Read.vi returns a single sample from the most recent messages received, and greater than zero means that MC DAQ Read.vi returns samples timed at the specified rate. For DAQMode of mcDAQModePolling, SampleRate is ignored.
DAQ — — Event Channel Name Sets the event channel name to which the Measurement task is assigned. If there is no event channel name defined in the A2L file, you can set the Event Channel Number manually by passing a decimal number as a string.
DAQ — — Prescaler Sets the prescaling factor, which reduces the desired transmission frequency of the associated DAQ list.
DAQ CCP — DTO Id Sets the DTO ID, which is used by the ECU to send DAQ list data to the CCP master. If bit 31 (hex 0x80000000) of the value is set, the value is considered an extended CAN identifier (29-bit).
DAQ XCP — Timing Source Sets the DAQ Timing Source property value. The default is Automatic.
Note The Timing Source property is only supported with XCP protocol.

Values are:

0Automatic

The default method (1, 2, or 3, below) is selected.

1Host Timing

Timestamps are generated from the host system time whenever a frame arrives.

This mode is always available.

This is the default for XCP on TCP/UDP if the ECU does not support timestamps.

2CAN Timing

Timestamps are generated from the network interface hardware (e.g. NI-XNET hardware).

This mode is available only if the network hardware generates timestamps.

This is the default for XCP on CAN if the ECU does not support timestamps.

3ECU Timing

Timestamps are taken from the ECU data. The Start Time is taken from the host, and increments are taken from the ECU.

This mode is only available if the ECU generates timestamps; in this case, it is default.