Transmit CAN message to selected CAN device
Vehicle Network Toolbox: CAN Communication
The CAN Transmit block transmits messages to the CAN network using the specified CAN device. The CAN Transmit block can transmit a single message or an array of messages during a given timestep. To transmit an array of messages, use a mux (multiplex) block from the Simulink® block library. You cannot have more than one Transmit block in a model using the same NI-XNET device channel.
You need a license for both Vehicle Network Toolbox™ and Simulink software to use this block.
The CAN Transmit block has one input port. This port accepts a CAN message packed using the CAN Pack block. It has no output ports.
CAN is a peer-to-peer network, so when transmitting messages on a physical bus at least one other node must be present to properly acknowledge the message. Without another node, the transmission will fail as an error frame, and the device will continually retry to transmit.
The CAN Transmit 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 the Simulink documentation.
The CAN Transmit block supports the use of code generation along with the packNGo function to group required source code and dependent shared libraries. For more information, see 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.
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 Build Process (Simulink Coder).
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
supported by Simulink
Coder to set up and manage the build
information for your models. The
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
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 Build Process Customization (Simulink Coder).
Configure your CAN Configuration block before you configure the CAN Transmit block parameters.
Select the CAN device and channel for transmitting CAN messages to the network. This list shows 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.
Select this option to enable periodic transmission of the message on the configured channel at
the specified message period. The period references real time, regardless of the Simulink model time step size (fundamental sample time) or block execution sample time.
This is equivalent to the MATLAB function
The periodic transmission is a nonbuffered operation. Only the last CAN message or set of muxed messages present at the input of the CAN Transmit block is sent when the time period occurs.
Specify a period in seconds. This value is used to transmit
the message in the specified period. By default this value is