Vehicle Network Toolbox™ now supports analysis of CAN data from National Instruments® NI-XNET hardware.
of the CAN channel object enables you to compute the absolute time
of CAN message data and signal values.
Vehicle Network Toolbox now supports hardware triggering from National Instruments NI-XNET devices and National Instruments DAQ devices.
You can now trigger the start of an NI-XNET CAN device channel, and synchronize the start with an NI DAQ device.
You can configure synchronization and triggering with the
StartTriggerTerminal property on the NI-XNET
CAN channel object. This property string value configures a synchronization-trigger
connection to start the NI-XNET CAN channel on the connected source
The following properties of NI-XNET CAN channel objects are now supported:
Protocol level status of the network indicating potential error or
bus off states
Number of receive error events detected by the device at the protocol
— Number of transmit error events detected by the device at
the protocol level
Configure the on-board termination of the NI-XNET device that controls
Beginning in this release, Vehicle Network Toolbox no longer supports National Instruments NI-CAN devices.
This release does not support NI-CAN devices. To continue using NI-CAN devices, use an earlier version of Vehicle Network Toolbox. Alternatively, consider using a device supported in this release. For more information, see CAN Bus Support from Vehicle Network Toolbox.
This release of Vehicle Network Toolbox supports the SAE J1939 vehicle bus. This support includes:
A command-line set of operations for access to J1939 channels and parameter groups. For more information on these, use the following MATLAB command:
A J1939 Communication block library, available in the Simulink Library Browser, under the Vehicle Network Toolbox node.
For a full listing, see the
CAN database operation category
in the output from the MATLAB command:
You can import messages into Vehicle Network Toolbox four
times faster than before using the
CAN Simulink blocks are now optimized for code generation. Improvements include:
Generated code is optimized and no longer contains mismatched data type comparisons.
Improved MISRA compliance.
Optimized constraint checks to avoid unnecessary saturation of code.
Easier integration of custom transmit and receive blocks into existing applications.
You can now install these supported CAN devices via the Support Package Installer
You can now use Vehicle Network Toolbox with NI CAN devices that use the NI-XNET driver including NI PCI-8511, NI PCI-8512, NI PCI-8513, NI PXI-8511, NI PXI-8512, and NI PXI-8513.
You can now use Vehicle Network Toolbox with PEAK-System devices including PCAN-USB, PCAN-USB PRO, PCAN-ExpressCard, PCAN-PCI, PCAN-PCI Express, and PCAN-cPCI families.
You can now use Vehicle Network Toolbox with Kvaser Blackbird V2, Kvaser Leaf Light V2, and Kvaser Mini PCI Express devices.
You can now use new MATLAB functions to transmit and receive messages on your vehicle network using XCP.
You can now use new Simulink® XCP blocks to build a model that communicates with a CAN bus or an ECU.
You can now use new MATLAB functions and Simulink XCP blocks to read data acquisition lists and write data stimulation lists to an XCP channel.
You can now use seed and key security to control access to your ECU using XCP over CAN.
The following filtering functions have been removed:
Use these new message filtering functions instead:
You cannot access any of the old message filtering functions. Replace all instances of the old functions with the new functions.
You can now attach custom information to a CAN channel, message,
or database using the new
You can now use the
to clear all available messages on a CAN channel without restarting
You can now use MATLAB variables to represent sampling time in Vehicle Network Toolbox Simulink blocks.
You can no longer access
functions in the MATLAB workspace.
You cannot access direct signal properties as of R2012a of Vehicle Network Toolbox.
Update your code to access physical signal values through the
of message objects.
You can use these functions to filter standard and extended CAN messages:
You can now use Vector and Kvaser CAN devices with Vehicle Network Toolbox on a 64-bit Windows® system.
You can now create your own Receive and Transmit blocks that communicate with unsupported hardware. You can use these custom blocks with the available Vehicle Network Toolbox Simulink blocks.
now import messages faster from Vector and Kvaser log files.
Vehicle Network Toolbox supports NI CAN devices. You can use these devices for CAN communication in the toolbox and with CAN blocks in Simulink.
For a complete list of supported hardware, visit the Vehicle Network Toolbox product
page at the MathWorks Web site
You now have the option to filter incoming messages in the CAN Tool and display only the messages you want to see, using message IDs. See Monitoring CAN Message Traffic for more information.
You can now generate code from Simulink blocks in Vehicle Network Toolbox.
Models containing the CAN Receive, CAN Transmit,
Configuration blocks run successfully in Accelerator,
Rapid Accelerator, External, and Deployed Modes. These blocks also
now support using the Simulink Coder™
receiveRaw function no longer works in
the current release of Vehicle Network Toolbox.
You cannot access direct signal properties or use the
to restore access to direct signal properties starting with the current
release of Vehicle Network Toolbox. Update your code to access
physical signal values through the
of message objects.
allows you to import CAN messages from Vector or Kvaser CAN log files.
The CAN Tool includes many enhancements such as:
A redesigned, flexible interface
Ability to decode messages attached to CAN database files
in MATLAB to enable messages for event-based transmission.
in MATLAB to enable messages for periodic transmit. You can also
configure the CAN Transmit block to send messages periodically.
Vehicle Network Toolbox supports Kvaser CAN devices, including these products:
Leaf Light Rugged
You can use these devices with the Vehicle Network Toolbox™tm_vehiclenetworktoolbox; and the CAN block library.
For a complete list of devices, see the Supported Hardware page at the MathWorks® Web site.
receiveRaw function will be removed
in a future release. In earlier software versions, the
expedited receive capability with minimal processing time and maximized
message throughput. With enhanced toolbox performance this capability
is no longer required. Performance of the standard
is significantly increased and you can use it to receive all messages.
receiveRaw function will be removed
in a future release. You will see a warning when you use this function.
displays each physical signal as defined for a CAN message in the
CAN database. The
Signals property is not applicable
if you are not using a CAN database.
Signals displayed by the
replaces access to direct signal property display of CAN messages.
It has also increased the toolbox performance and the throughput of
the message receive and transmit functions.
Direct signal properties will no longer appear in a message
output. Use the new
to access physical signal values. Update your code if you are using
a CAN database and direct signal properties. Refer to the
for more information. It is recommended that you update your code
and use the new
because all access to direct signal properties will be removed in
a future release. If you cannot update your code at this time, you
can use the
to restore access to direct signal properties.
displays the load on the CAN bus associated with the CAN message traffic
on Kvaser devices.
filterSet function now automatically
calculates and applies the best case filter settings from an array
Version 1.0 of the Vehicle Network Toolbox supports the Vector CAN database.
You can encode and decode CAN traffic messages with Version 1.0 of the Vehicle Network Toolbox.
Version 1.0 of Vehicle Network Toolbox allows you to filter CAN messages by message ID.
With Version 1.0 of Vehicle Network Toolbox you can log and replay CAN messages.
Version 1.0 of Vehicle Network Toolbox comes with a Simulink CAN block library that you can use to simulate CAN network models.
Version 1.0 of Vehicle Network Toolbox provides a simple GUI that allows you to monitor CAN message traffic.
|Release||Features or Changes with Compatibility Considerations|
|R2016a||Discontinued support for NI-CAN devices|
|R2012b||Old Message Filtering Functions Removed|
|R2012a||receiveRaw Function No Longer Available|
|R2011b||New CAN Message Filtering Functions|
|R2011a||receiveRaw function Removed|