Main Content

CAN Receive

Receive CAN messages from specified CAN device

expand all in page
  • CAN Receive block

Libraries:
Vehicle Network Toolbox / CAN Communication

Description

The CAN Receive block receives messages from the CAN network and delivers them to the Simulink® model. It outputs one message or all messages at each timestep, depending on the block parameters.

Note

You need a license for both Vehicle Network Toolbox™ and Simulink software to use this block.

The CAN Receive block stores CAN messages in a first-in, first-out (FIFO) buffer. The FIFO buffer delivers the messages to your model in the queued order at every timestep.

Note

You cannot have more than one CAN Receive block in a model using the same PEAK-System device channel.

Other Supported Features

The CAN Receive block supports the use of Simulink accelerator mode. Using this feature, you can speed up the execution of Simulink models. For more information on this feature, see Acceleration (Simulink).

The CAN Receive block supports the use of code generation along with the packNGo function to group required source code and dependent shared libraries.

Code Generation

Vehicle Network Toolbox Simulink blocks allow you to generate code, enabling models containing these blocks to run in accelerator, rapid accelerator, external, and deployed modes.

Code Generation with Simulink Coder

You can use Vehicle Network Toolbox, Simulink Coder™, and Embedded Coder® software together to generate code on the host end that you can use to implement your model. For more information on code generation, see Generated Code Compilation (Simulink Coder).

Shared Library Dependencies

The block generates code with limited portability. The block uses precompiled shared libraries, such as DLLs, to support I/O for specific types of devices. With this block, you can use the packNGo function supported by Simulink Coder to set up and manage the build information for your models. The packNGo (Simulink Coder) function allows you to package model code and dependent shared libraries into a zip file for deployment. You do not need MATLAB® installed on the target system, but the target system needs to be supported by MATLAB.

To set up packNGo:

set_param(gcs,'PostCodeGenCommand','packNGo(buildInfo)');

In this example, gcs is the current model that you want to build. Building the model creates a zip file with the same name as model name. You can move this zip file to another machine and there build the source code in the zip file to create an executable which can run independent of MATLAB and Simulink. The generated code compiles with both C and C++ compilers. For more information, see Code Compilation Customization (Simulink Coder).

Note

On Linux® platforms, you need to add the folder where you unzip the libraries to the environment variable LD_LIBRARY_PATH.

Examples

Periodic CAN Message Transmission Behavior in Simulink

Periodic CAN Message Transmission Behavior in Simulink

Set up periodic transmission and reception of CAN messages in Simulink® using MathWorks® virtual CAN channels. The virtual channels are connected in a loopback configuration.

Set Up Communication Between Host and Target Models

Set Up Communication Between Host and Target Models

Set up CAN communication between host-side CAN Vector blocks and target models. This example uses:

Log and Replay CAN Messages

Log and Replay CAN Messages

Log and replay CAN messages using MathWorks® Virtual CAN channels in Simulink®. You can update this model to connect to supported hardware on your system.

Ports

Output

expand all

The CAN Msg output port contains one or more packed CAN messages received at that particular timestep, output as a signal bus or CAN_MESSAGE. The output includes either one or all messages for that timestep, depending on the setting of Number of messages received at each timestep.

Data Types: CAN_MESSAGE | bus

The f() output port is a trigger to a Function-Call subsystem. If the block receives a new message, it triggers a Function-Call from this port. You can then connect to a Function-Call Subsystem (Simulink) to unpack and process a message.

Data Types: function-call event

Parameters

expand all

Tip

Configure your CAN Configuration block before you configure the CAN Receive block parameters.

Select from the list the CAN device and a channel on the device you want to receive CAN messages from. This field lists all the devices installed on the system. It displays the vendor name, the device name, and the channel ID. The default is the first available device on your system.

Programmatic Use

Block Parameter: Device
Type: character vector, string

Select the filter for standard IDs. Choices are:

  • Allow all (default): Allows all standard IDs to pass the filter.

  • Allow only: Allows only the ID or range of IDs specified in the text field, specified as a single ID or an array of IDs. You can also specify disjointed IDs or arrays separated by a comma. For example, to allow IDs 400 through 500, and 600 through 650, enter [[400:500],[600:650]]. Standard IDs must be positive integers from 0 to 2047. You can also specify hexadecimal values with the hex2dec function.

  • Block all: Blocks all standard IDs from passing the filter.

Programmatic Use

Block Parameter: StdIDsCombo
Type: character vector, string
Values: 'Allow all' | 'Allow only' | 'Block all'
Default: 'Allow all'

If using 'Allow only', set the filter values with the following:

Block Parameter: StandardIDs
Type: character vector, string
Values: integer scalar or row vector

Select the filter on this block for extended IDs. Choices are:

  • Allow all (default): Allows all extended IDs to pass the filter.

  • Allow only: Allows only those IDs specified in the text field. Allows only the ID or range of IDs specified in the text field, specified as a single ID or an array of IDs. You can also specify disjointed IDs or arrays separated by a comma. For example, to accept IDs 3000 through 3500, and 3600 through 3620, enter [[3000:3500],[3600:3620]]. Extended IDs must be positive integers from 0 to 536870911. You can also specify hexadecimal values using the hex2dec function.

  • Block all: Blocks all extended IDs from passing the filter.

Programmatic Use

Block Parameter: ExtIDsCombo
Type: character vector, string
Values: 'Allow all' | 'Allow only' | 'Block all'
Default: 'Allow all'
Block Parameter: ExtendedIDs
Type: character vector, string
Values: integer scalar or row vector

Specify the sample time of the block during the simulation. This is the rate at which the block is executed during simulation. The default value is 0.01 simulation seconds. For more information, see Timing in Hardware Interface Models.

Programmatic Use

Block Parameter: SampleTime
Type: character vector, string
Values: double
Default: '0.01'

Select how many messages the block receives at each specified timestep. Valid choices are:

  • all (default): The CAN Receive block delivers all available messages in the FIFO buffer to the model during a specific timestep. The block generates one function call for each delivered message. The output port always contains one CAN message at a time.

  • 1: The CAN Receive block delivers one message per timestep from the FIFO buffer to the model.

If the block does not receive any messages before the next timestep, it outputs the last received message.

Programmatic Use

Block Parameter: MsgsPerTimestep
Type: character vector, string
Values: 'all' | '1'
Default: 'all'

Output a native Simulink bus signal. For more information on Simulink bus objects, see Composite Interfaces (Simulink).

Programmatic Use

Block Parameter: BusOutput
Type: character vector, string
Values: 'off' | 'on'
Default: 'off'

Extended Capabilities

Version History

Introduced in R2009a

See Also

Blocks

Functions

Topics