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 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 can now attach custom information to a CAN channel, message, or database using the new UserData property.
You can now use the discard function to clear all available messages on a CAN channel without restarting the channel.
You can now use MATLAB variables to represent sampling time in Vehicle Network Toolbox Simulink blocks.
You can no longer access receiveRaw and canMessageCompatibilityMode 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 Signals property 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.
The canMessageImport function 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.
Note: For a complete list of supported hardware, visit the Vehicle Network Toolbox product page at the MathWorks Web site www.mathworks.com/products/vehicle-network.
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 Vehicle CAN Bus for more information.
You can now generate code from Simulink blocks in Vehicle Network Toolbox. Models containing the CAN Receive, CAN Transmit, and CAN Configuration blocks run successfully in Accelerator, Rapid Accelerator, External, and Deployed Modes. These blocks also now support using the Simulink Coder™ packNGo function.
The receiveRaw function no longer works in the current release of Vehicle Network Toolbox.
You cannot access direct signal properties or use the canMessageCompatibilityMode function 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 Signals property of message objects.
The new canMessageImport function 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
Use the transmitEvent function in MATLAB to enable messages for event-based transmission.
Use the transmitPeriodic function 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.
The receiveRaw function will be removed in a future release. In earlier software versions, the receiveRaw function 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 receive function is significantly increased and you can use it to receive all messages.
The receiveRaw function will be removed in a future release. You will see a warning when you use this function. Use the receive function instead.
The Signals property 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 Signals property 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 Signals property to access physical signal values. Update your code if you are using a CAN database and direct signal properties. Refer to the Signals property for more information. It is recommended that you update your code and use the new Signals property 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 canMessageCompatibilityMode function to restore access to direct signal properties.
The BusLoad property displays the load on the CAN bus associated with the CAN message traffic on Kvaser devices.
The filterSet function now automatically calculates and applies the best case filter settings from an array of CAN IDs.
Version 1.0 of the Vehicle Network Toolboxtm_vehiclenetworktoolbox; supports the Vector CAN database.
You can encode and decode CAN traffic messages with Version 1.0 of the Vehicle Network Toolboxtm_vehiclenetworktoolbox;.
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|
|R2012b||Old Message Filtering Functions Removed|
|R2012a||receiveRaw Function No Longer Available|
|R2011b||New CAN Message Filtering Functions|
|R2011a||receiveRaw function Removed|