-
Notifications
You must be signed in to change notification settings - Fork 51
NI XNET XNET ECU Properties
- Cluster
- Comment
- Configuration Status
- FlexRay:Coldstart?
- FlexRay:Connected Channels
- FlexRay:Startup Frame
- FlexRay:Wakeup Channels
- FlexRay:Wakeup Pattern
- Frames Received
- Frames Transmitted
- LIN Master
- LIN Version
- LIN:Initial NAD
- LIN:Configured NAD
- LIN:Supplier ID
- LIN:Function ID
- LIN:P2min
- LIN:STmin
- Name (Short)
- SAE J1939:Preferred Address
- SAE J1939:Node Name
Data Type | Direction | Required? | Default |
---|---|---|---|
nxDatabaseRef_t | Read Only | N/A | N/A |
XNET PDU
nxPropPDU_ClusterRef
This property returns the reference (nxDatabaseRef_t) to the parent cluster in which the PDU has been created. You cannot change the parent cluster after creating the PDU object.
Data Type | Direction | Required? | Default |
---|---|---|---|
char * | Read/Write | No | Empty String |
XNET Signal
nxPropSig_Comment
Comment describing the signal object.
A comment is a string containing up to 65535 characters.
Data Type | Direction | Required? | Default |
---|---|---|---|
i32 | Read Only | No | N/A |
XNET Signal
nxPropSig_ConfigStatus
The signal object configuration status.
Configuration Status returns an NI-XNET error code. You can pass the value to the nxStatusToString error code input to convert the value to a text description of the configuration problem.
By default, incorrectly configured signals in the database are not returned from the XNET Frame Signals property because they cannot be used in the bus communication. You can change this behavior by setting the XNET Database ShowInvalidFromOpen? property to true. When a signal configuration status becomes invalid after the database is opened, the signal still is returned from the Signals property even if the ShowInvalidFromOpen? property is false.
Examples of invalid signal configuration:
- The signal is specified using bits outside the frame payload.
- The signal overlaps another signal in the frame. For example, two multiplexed signals with the same multiplexer value are using the same bit in the frame payload.
- The frame containing the signal is invalid (for example, a CAN frame is defined with more than 8 payload bytes).
Data Type | Direction | Required? | Default |
---|---|---|---|
char * | Read/Write | Yes | Defined in nxdbCreateObject |
XNET Subframe
nxPropSubfrm_Name
String identifying a subframe object.
Lowercase letters (a–z), uppercase letters (A–Z), numbers, and the underscore (_) are valid characters for the short name. The space ( ), period (.), and other special characters are not supported within the name. The short name must begin with a letter (uppercase or lowercase) or underscore, and not a number. The short name is limited to 128 characters.
A subframe name must be unique for all subframes in a frame.
This short name does not include qualifiers to ensure that it is unique, such as the database, cluster, and frame name. It is for display purposes.
You can write this property to change the subframe's short name.
Data Type | Direction | Required? | Default |
---|---|---|---|
bool | Read Only | N/A | N/A |
XNET ECU
nxPropECU_FlexRayIsColdstart
Indicates that the ECU is sending a startup frame.
This property is valid only for ECUs connected to a FlexRay bus. It returns true when one of the frames this ECU transmits has the XNET Frame FlexRay:Startup? property set to true. You can determine the frame transmitting the startup using the XNET ECU FlexRay:Startup Frame property. An ECU can send only one startup frame on the FlexRay bus.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | No | Calculated from Cluster Settings |
XNET ECU
nxPropECU_FlexRayConnectedChs
This property specifies the channel(s) that the FlexRay ECU (node) is physically connected to. The default value of this property is connected to all channels available on the cluster.
This property corresponds to the pChannels node parameter in the FlexRay Protocol Specification.
The values supported for this property (enumeration) are A = 1, B = 2, and A and B = 3.
Data Type | Direction | Required? | Default |
---|---|---|---|
nxDatabaseRef_t | Read Only | N/A | N/A |
XNET ECU
nxPropECU_FlexRayStartupFrameRef
Returns the refnum to the startup frame the ECU sends.
This property is valid only for ECUs connected to a FlexRay bus. If the ECU transmits a frame (refer to the XNET ECU Frames Transmitted property) with the XNET Frame FlexRay:Startup? property set to true, this property returns this frame. Otherwise, it is empty.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | No | None |
XNET ECU
nxPropECU_FlexRayWakeupChs
This property specifies the channel(s) on which the FlexRay ECU (node) is allowed to generate the wakeup pattern. The default value of this property is not to be a wakeup node.
When importing from a FIBEX file, this parameter corresponds to a WAKE-UP-CHANNEL being set to True for each connected channel.
The values supported for this property (enumeration) are A = 1, B = 2, A and B = 3, and None = 4.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | No | 2 |
XNET ECU
nxPropECU_FlexRayWakeupPtrn
This property specifies the number of repetitions of the wakeup symbol that are combined to form a wakeup pattern when the FlexRay ECU (node) enters the POC:WAKEUP_SEND state. The POC:WAKEUP_SEND state is one of the FlexRay controller state transitions during the wakeup process. In this state, the controller sends the wakeup pattern on the specified Wakeup Channel and checks for collisions on the bus.
This property is used when FlexRay:Wakeup Channels is set to a value other than None and FlexRay:Use Wakeup? is True.
This property corresponds to the pWakeupPattern node parameter in the FlexRay Protocol Specification.
The supported values for this property are 2–63.
Data Type | Direction | Required? | Default |
---|---|---|---|
nxDatabaseRef_t * | Read/Write | No | Empty Array |
XNET ECU
nxPropECU_RxFrmRefs
Returns an array of refnums to frames the ECU receives.
This property defines all frames the ECU receives. All frames an ECU receives in a given cluster must be defined in the same cluster.
Note Invalid clusters, frames, and signals are not returned in properties that return XNET I/O Names for the database.
Data Type | Direction | Required? | Default |
---|---|---|---|
nxDatabaseRef_t * | Read/Write | No | Empty Array |
XNET ECU
nxPropECU_FrmsTx
Returns an array of refnums to frames the ECU transmits.
This property defines all frames the ECU transmits. All frames an ECU transmits in a given cluster must be defined in the same cluster.
Note Invalid clusters, frames, and signals are not returned in properties that return XNET I/O Names for the database.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | N/A | N/A |
XNET ECU
nxPropECU_LINInitialNAD
Initial NAD of a LIN slave node. NAD is the address of a slave node and is used in diagnostic services. Initial NAD is replaced by configured NAD with node configuration services. This property must be defined before reading, either by writing to the property or by importing from an LDF.
Caution This property is not saved in the FIBEX database. You can import it only from an LDF file.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | N/A | N/A |
XNET ECU
nxPropECU_LINConfigNAD
Configured NAD of a LIN slave node. NAD is the address of a slave node and is used in diagnostic services. Initial NAD is replaced by configured NAD with node configuration services. This property must be defined before reading, either by writing to the property or by importing from an LDF.
Caution This property is not saved in the FIBEX database. You can import it only from an LDF file.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | N/A | N/A |
XNET ECU
nxPropECU_LINSupplierID
Supplier ID is a 16-bit value identifying the supplier of the LIN node (ECU). This property must be defined before reading, either by writing to the property or by importing from an LDF.
Caution This property is not saved in the FIBEX database. You can import it only from an LDF file.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | N/A | N/A |
XNET ECU
nxPropECU_LINFunctionID
Function ID is a 16-bit value identifying the function of the LIN node (ECU). This property must be defined before reading, either by writing to the property or by importing from an LDF.
Caution This property is not saved in the FIBEX database. You can import it only from an LDF file.
Data Type | Direction | Required? | Default |
---|---|---|---|
Double | Read/Write | N/A | N/A |
XNET ECU
nxPropECU_LINP2min
The minimum time in seconds between reception of the last frame of the diagnostic request and the response sent by the node. This property must be defined before reading, either by writing to the property or by importing from an LDF.
Caution This property is not saved in the FIBEX database. You can import it only from an LDF file.
Data Type | Direction | Required? | Default |
---|---|---|---|
Double | Read/Write | N/A | N/A |
XNET ECU
nxPropECU_LINSTmin
The minimum time in seconds the node requires to prepare for the next frame of the diagnostic service. This property must be defined before reading, either by writing to the property or by importing from an LDF.
Caution This property is not saved in the FIBEX database. You can import it only from an LDF file.
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | No | 254 (Null) |
XNET ECU
nxPropECU_J1939PreferredAddress
The preferred J1939 node address to be used when simulating this ECU. If you assign this ECU to an XNET session (nxPropSession_J1939ECU property), XNET will start address claiming for this address using the nxPropECU_J1939NodeName property and use the address for the session when the address is granted.
Data Type | Direction | Required? | Default |
---|---|---|---|
u64 | Read/Write | No | 0 |
XNET ECU
nxPropECU_J1939NodeName
The preferred J1939 node address to be used when simulating this ECU. If you assign this ECU to an XNET session nxPropSession_J1939ECU property), XNET will start address claiming for this address using this node name and the nxPropSession_J1939PreferredAddress) property.
Data Type | Direction | Required? | Default |
---|---|---|---|
bool | Read/Write | No | False |
XNET ECU
nxPropECU_LINMaster
Determines whether the ECU is a LIN master (true) or LIN slave (false).
Data Type | Direction | Required? | Default |
---|---|---|---|
u32 | Read/Write | Yes | N/A |
XNET ECU
nxPropECU_LINProtocolVer
Version of the LIN standard this ECU uses. The values (enumeration) for this property are:
- nxLINProtocolVer_1_2
- nxLINProtocolVer_1_3
- nxLINProtocolVer_2_0
- nxLINProtocolVer_2_1
Creating and Setting Up a gRPC Server
Session Utilities API Reference
gRPC API Differences From C API
Sharing Driver Sessions Between Clients
C API Docs
NI-DAQmx
- gRPC API Differences From C API
- Task Configuration And Control
- Channel Configuration And Creation
- Timing
- Triggering
- Read Functions
- Write Functions
- Export Hardware Signals
- Scale Configuration
- Internal Buffer Configuration
- Advanced Functions
- System Configuration
- Error Handling
- Buffer Attributes
- Calibration Info Attributes
- Channel Attributes
- Device Attributes
- Export Signal Attributes
- Persisted Channel Attributes
- Persisted Scale Attributes
- Persisted Task Attributes
- Physical Channel Attributes
- Read Attributes
- Scale Attributes
- System Attributes
- Task Attributes
- Timing Attributes
- Trigger Attributes
- Watchdog Attributes
- Write Attributes
NI-DCPOWER
- Setup Functions
- Configure Functions
- Measurement Functions
- Control Functions
- Trigger And Event
- Attribute Functions
- Query Functions
- Calibration Functions
- Utility Functions
- Supported Device
- Source Attributes
- Transient Attributes
- Voltage Attributes
- Current Attributes
- Pulse Voltage Attributes
- Pulse Current Attributes
- Cutoff Attributes
- Measurement Attributes
- Trigger Attributes Functions
- Event Attributes
- Advanced Attributes
- Inherent Ivi Attributes
- Supported Device Attributes
NI-DIGITAL PATTERN DRIVER
- Init And Close Functions
- Session Locking Functions
- Utility Functions
- Error Handling Functions
- Calibration Functions
- Attributes Functions
- Pin Map Functions
- Low Level Functions
- Low Level Action Functions
- Pin Control Functions
- Static IO Functions
- Clock Generator Functions
- Levels And Timing Functions
- TDR Functions
- PPMU Configuration Functions
- DC Voltage Functions
- DC Current Functions
- PPMU Action Functions
- Pattern Configuration Functions
- Pattern Action Functions
- History Ram Functions
- Source Memory Functions
- Capture Memory Functions
- Triggers And Events Functions
- Conditional Jump Trigger Functions
- Sequencer Flag Functions
- Sequencer Register Functions
- Match Fail Combination Functions
- Pattern Results Functions
- Sort Results Functions
- Frequency Measurement Functions
- IVI Inherent Attributes
- Specific Driver Information Attributes, Read Only
- Driver Setup Information Attributes
- Device Attributes
- Pin Control Attributes
- Level Configuration Attributes
- Trigger Configuration Attributes
- PPMU Attributes
- Patterns Attributes
- Pattern Opcode Event Attributes
- Timing Offset Attributes
- Keep Alive Attributes
- Frequency Measurement Attributes
- Clock Generator Attributes
- History RAM
- Synchronization Attributes
- TDR Endpoint Termination Attributes
NI-FGEN
- Setup Functions
- Configuration Functions
- Standard Output Functions
- Arbitrary Waveform Output Functions
- Arbitrary Sequence Output Functions
- Incremental Waveform Write Functions
- Configure Clock Functions
- Trigger And Syncronizations Functions
- 5404 Routing Functions
- Script Output Functions
- Configure Onboard Signal Processing Functions
- Configure Peer To Peer Functions
- Attribute Functions
- Waveform Control Functions
- Error Functions
- Output Attributes
- Arbitrary Waveform Attributes
- Data Transfer Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Attributes
- Standard Function Attributes
- Clock Attributes
- Event Attributes
- Triggering Attributes
- Instrument Specific Attributes
- Inherent IVI Attributes
- 5401 5411 5431
NI-RFmx Bluetooth
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Packet Attributes
- Auto Detect Signal Attributes
- Modacc Attributes
- ACP Attributes
- Twenty dB Attributes
- Frequency Range Attributes
- TXP Attributes
- Advanced Attributes
NI-RFmx NR
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attributes Functions
- Fetch Results Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Signal Detection Attributes
- Component Carrier Attributes
- List Attributes
- Modacc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- TXP Attributes
- Pvt Attributes
- Advanced Attributes
NI-RFmx LTE
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Ch Configuration Functions
- NB IoT Configuration Functions
- ModAcc Configuration Functions
- ACP Configuration Functions
- CHP Configuration Functions
- OBW Configuration Functions
- SEM Configuration Functions
- PVT Configuration Functions
- SlotPhase Configuration Functions
- SlotPower Configuration Functions
- Set And Get Attribute Functions
- ModAcc Fetch Functions
- ACP Fetch Functions
- CHP Fetch Functions
- OBW Fetch Functions
- SEM Fetch Functions
- PVT Fetch Functions
- SlotPhase Fetch Functions
- SlotPower Fetch Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- Component Carrier Attributes
- ModAcc Attributes
- ACP Attributes
- CHP Attributes
- OBW Attributes
- SEM Attributes
- PVT Attributes
- SlotPhase Attributes
- SlotPower Attributes
- Advanced Attributes
NI-RFmx SpecAn
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Read Functions
- Fetch Functions
- Utility Functions
- Marker Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- ACP Attributes
- Cdf Attributes
- CHP Attributes
- Fcnt Attributes
- Harm Attributes
- OBW Attributes
- SEM Attributes
- Spectrum Attributes
- Spur Attributes
- TXP Attributes
- AMPM Attributes
- Dpd Attributes
- IQ Attributes
- IM Attributes
- NF Attributes
- Phasenoise Attributes
- PAVT Attributes
- Advanced Attributes
NI-RFmx WLAN
- gRPC API Differences From C API
- General Functions
- Configuration Functions
- Set And Get Attribute Functions
- Fetch DSSS ModAcc Functions
- Fetch OFDM ModAcc Functions
- Fetch SEM Functions
- Fetch TXP Functions
- Fetch PowerRamp Functions
- Utility Functions
- Build String Functions
- Advanced Functions
- General Attributes
- Trigger Attributes
- OFDM Attributes
- Auto Detect Signal Attributes
- DSSS ModAcc Attributes
- OFDM ModAcc Attributes
- SEM Attributes
- TXP Attributes
- PowerRamp Attributes
- Advanced Attributes
NI-RFSA
- General Functions
- Configuration Functions
- Acquisition Functions
- Utility Functions
- Calibration Functions
- General Attributes
- Vertical Attributes
- Signal Path Attributes
- Acquisition Attributes
- Acquisition Attributes
- Triggers Attributes
- Events Attributes
- Device Characteristics Attributes
- Peer To Peer Streaming Attributes
- Configuration List Attributes
- Inherent IVI Properties Attributes
- De-embedding Attributes
- Self Calibration Attributes
- Factory Calibration Attributes
- External Alignment Attributes
- Device Specific Attributes
NI-RFSG
- General Functions
- Generation Configuration
- Utility Functions
- Calibration Functions
- Arb Attributes
- Clock Attributes
- Configuration List Attributes
- De-embedding Attributes
- Device Characteristics Attributes
- Device Specific Attributes
- Events Attributes
- External Calibration Attributes
- Inherent IVI Attributes Attributes
- IQ Impairment Attributes
- Load Configurations Attributes
- Modulation Attributes
- Obsolete Attributes
- Peer To Peer Attributes
- RF Attributes
- Self Calibration Attributes
- Triggers Attributes
NI-SCOPE
- Setup Functions
- Configure Functions
- Attribute Functions
- Acquisition Functions
- Measurement Functions
- Calibrate Functions
- Utility Funcitons
- Error Handling Functions
- IVI Compliance Or Obsolete Functions
- Vertical Attributes
- Horizontal Attributes
- Trigger Attributes
- Clocking Attributes
- Synchronization Attributes
- Acquisition Attributes
- Waveform Measurements Attributes
- Onboard Signal Processing Attributes
- Peer To Peer Streaming Attributes
- Device Attributes
- IVI Or Obsolete Attributes
- Instrument Capabilities Attributes
- If Digitizer Attributes
NI-XNET
- gRPC API differences from C APIs
- General Functions
- Cluster Properties
- Database Properties
- Device Properties
- ECU Properties
- Frame Properties
- Interface Properties
- LIN Schedule Entry Properties
- LIN Schedule Properties
- PDU Properties
- Session Ethernet Properties
- Session Frame Properties
- Session Interface Properties
- Session Properties
- Session SAE J1939 Properties
- Signal Properties
- Subframe Properties
- System Properties
- IP-Stack Functions
- Socket Options
- Socket Functions