CAN Receive

Receive message from CAN network

• Library:

• Simulink Support Package for Raspberry Pi Hardware / Communication

• 

Description

The CAN Receive block receives messages from the CAN network. This block uses SocketCAN which is a device-independent driver for implementing the CAN interface supporting all CAN shields.

The CAN Receive block supports Raw data and CAN Msg as output types. To use a CANdb (CAN database) file or to specify signals manually, use CAN Msg output type and the CAN Unpack block. The CAN Unpack block is available from Vehicle Network Toolbox™. For more information on the CAN Unpack block, see CAN Unpack.

You can use CAN Receive block to interact with a real or virtual CAN interface. To bring up the CAN interface with Raspberry Pi™, refer to the user guide of your CAN shield. For more information on how to set up a virtual CAN interface, see Setup Virtual CAN Interface.

Ports

Output

Data — Message data port

vector | scalar

Received message data, returned as a vector or scalar.

Data Types: uint8 | CAN Msg

Status — Status of output message

scalar

Status of the received output message.

Data Types: uint8

Error — Error codes

scalar

Error codes.

Dependencies

To enable this parameter, select Output Error.

00	00	00	00	00	RXWAR	RXEP	RXOVR
bit7	bit6	bit5	bit4	bit3	bit2	bit1	bit0

RXOVR: Receive Buffer Overflow Flag bit

RXEP: Receive Error-Passive Flag bit

RXWAR: Receive Error Warning Flag bit

Remote — Remote message flag

scalar

Remote message flag.

Dependencies

To enable this parameter, select Output Remote.

Parameters

CAN interface — Name of CAN interface

can0 (default) | char

Enter the name of the real or virtual CAN interface. To find the name of the CAN interface, in the Raspberry Pi terminal, execute the ifconfig command.

Set up CAN interface — Set up CAN interface type

on (default) | off

Select this parameter to bring up the CAN interface on the Raspberry Pi before transmitting the CAN frames.

CAN interface type — Type of CAN interface

Real (default) | Virtual

Select the type of the CAN interface.

• If the CAN interface type is Real, set this parameter to Real. Setting this parameter to Real will not bring up the CAN interface in these scenarios.

  • The interface is already brought up on the target with a CAN-Bus Speed that does not match with the CAN Bus Speed (kBit/s) parameter. The block will not transmit the CAN frames. Bring the existing interface down before enabling this parameter.

  • If the interface is already brought up on the target with the CAN-Bus Speed that matches with the CAN Bus Speed (kBit/s)parameter. The block will transmit the CAN frames.

• If the CAN interface type is Virtual, set this parameter to Virtual.

Dependencies

To enable this parameter, select Set up CAN interface.

Data to be output as — Data output type

Raw data (default) | CAN Msg

Data type used for receiving messages.

Identifier Type — Message identifier type

Standard (11-bit identifier) (default) | Extended (29-bit identifier)

Message identifier type.

Dependencies

To enable this parameter, set Data to be output as to Raw data.

Message ID — Message identifier

100 (default) | numeric identifier of length 11 or 29 bits

Message identifier, which is 11 bits long for the standard frame size or 29 bits long for the extended frame size, specified in decimal, binary, or hex. For binary and hex formats, use bin2dec(' ') and hex2dec(' '), respectively, to convert the entry. The message identifier is coded into a message that is sent to the CAN bus.

Dependencies

To enable this parameter, set Data to be output as to Raw data.

Message Length — Length of message

8 (default) | positive integer

Message length.

Dependencies

To enable this parameter, set Data to be output as to Raw data.

Sample Time — Block sample time

0.1 (default) | double

Sample time.

Output Error — Output error codes

off (default) | on

Select to output error codes if the message transfer fails.

Output Remote — Enable remote messages

off (default) | on

Select to output remote messages.

Version History

Introduced in R2019b