IO644 Usage Notes v2
IO644 Usage Notes v2 — Usage information about the
I/O module
Description
This section provides additional information about the IO644 CANopen Slave
module.
EDS File
To set up CANopen communication, you must import the electronic data sheets (EDS)
of the CANopen slave devices into your CANopen Master configuration tool or PLC
programming tool. Speedgoat does not provide a default EDS file for the IO644.
Instead, you can export an EDS file from the IO644 Setup block that is specific to
your Simulink model.
For simulation purposes, you can import EDS files from other vendors and
autogenerate a communication interface in Simulink ready for use with the IO644. The
createFromEds function places the IO644 Setup, PDO, and Object driver
blocks into the model and automatically sets the block parameters according to the
objects defined in the EDS file.
Communication Object Identifier (COB ID)
With CANopen, each information shared on the network is a COB (Communication
Object) and has a COB ID (Communication Object Identifier). The COB ID includes the
unique 11-bit CAN ID and additional information. This CAN ID ranges from 0 to 2047.
The CANopen standard defines the following CAN ID ranges:
Pre-defined Objects
Some objects in the object dictionary are mandatory for the basic operation of the
I/O module. These objects are automatically created according to the parameters of
the Setup and PDO blocks, and must not be added by Object blocks.
Front Plate Description
IO644 PCI and PCIe modules
The rotary switch has no functional role.
IO644 mPCIe module
Note that in some real-time target machines,
the mPCIe module is reversed; that is, the Error LED appears on the right.