NI-XNET 21.0 Bug Fixes

概览

The following items are notable issues fixed between the release of NI-XNET 20.7 and NI-XNET 21.0, including additional patches and service packs. If you have an issue 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 NI-XNET.

Bug Number

Legacy ID

Description

Details

1004118

J1939 PS Field Is Included in the PGN When Sending TP.CM_RTS Frames

The J1939 protocol allows for data payloads greater than eight bytes by splitting them across a single packet comprising multiple frames. SAE J1939-21 specifies that, for the PGN in the payload of the first frame, "the least significant byte of the PGN is set to zero" when the PF value is less than 240. However, in NI-XNET the least significant byte contains the destination address.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-XNET 19.6

Resolved Version:

NI-XNET 21.0

Added:

Jul 27, 2021

1080099

XNET Database Editor Cannot Open LDF File Containing a Signal Larger Than 32 Bits

An error occurs when the XNET Database Editor loads an LDF file that contains a signal larger than 32 bits.

Workaround:

Convert the LDF file to AUTOSAR XML before opening the file in XNET Database Editor.

Reported Version:

NI-XNET 20.5

Resolved Version:

NI-XNET 21.0

Added:

Jul 27, 2021

1230469

XNET IP Stack on Linux RT Generates Errors If Called After DAQ Start Task

On Linux RT, creating an XNET IP Stack after starting a DAQ task returns error -13028.

Workaround:

On Linux RT, create the XNET IP Stack before starting the DAQ task.

Reported Version:

NI-XNET 20.5

Resolved Version:

NI-XNET 21.0

Added:

Jul 27, 2021

1349049

FlexRay Startup Frames Fail When Multiple Startup Frames Share the Same Slot

Cycle multiplexing enables multiple frames to be sent in the same communication cycle slot, but on different cycle counters. However, when multiple startup frames share the same slot, only one of the frames is transmitted successfully. The other frames appear to transmit in the echoed stream on the transmit side, but no frame goes out on the bus (not transmitted or received).

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-XNET 20.1

Resolved Version:

NI-XNET 21.0

Added:

Jul 27, 2021

1431882

For Automotive Ethernet Raw Frame Format, FCS is Being Returned as Little Endian

When using the raw frame format in LabVIEW or C API, the frame check sequence (FCS) is included as part of the packet data byte stream and is returned incorrectly in little endian format.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI-XNET 20.5

Resolved Version:

NI-XNET 21.0

Added:

Jul 27, 2021

1499506

Timing Types from a Third Party CAN Database Are Imported Incorrectly

When a third-party CAN database (DBC) is imported to the XNET Database Editor, a timing type may be inadvertently changed (e.g., from Cyclic Data to Event Data).

Workaround:

Save the database as an XML file before importing it to the XNET Database Editor.

Reported Version:

NI-XNET 19.0

Resolved Version:

NI-XNET 21.0

Added:

Jul 27, 2021

1499511

Unable to Use I/O Control to Populate CAN/LIN/FlexRay Signals on Linux RT Target

When a Linux RT target in a LabVIEW project is disconnected/reconnected while a VI is open, I/O control signals are not populated from the database and are unavailable in the selection list.

Workaround:

Close and reopen the VI.

Reported Version:

NI-XNET 20.5

Resolved Version:

NI-XNET 21.0

Added:

Jul 27, 2021

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).