Input DescriptionΒΆ

Using CAN2A_REC, CAN telegrams with 11 bit identifiers according to CAN 2.0A can be received. Only those telegrams can be received, the identifiers of which have been enabled previously. Enabling the individual identifiers is done in the controller configuration. For each identifier a corresponding buffer, the buffer size and its behavior if the buffer is full has to be defined. Received telegrams with non-enabled identifiers are automatically rejected by the Communication Module. See CAN2A_INFO, output NUM_INV CAN2A_INFO.

../_images/8242e435e3899c640a33139000eba54e

EN

Data_Type Default_Value Range Unit
BOOL - - -

The Function Block is activated (EN = TRUE) or deactivated (EN = FALSE) via input EN. If the Function Block is active, the current values are available at the outputs. If the Function Block detects a CAN Communication Module with a configured CAN 2.0A protocol at the specified SLOT, this is indicated by DONE = TRUE and ERR = FALSE. The corresponding status information is then available at the Function Block outputs.

SLOT

Data_Type Default_Value Range Unit
BYTE - - -

At input SLOT, the Communication Module slot (module number) is selected to used by the Function Block.

The internal Communication Module always has the module number 0. All external Communication Modules are serially numbered from right to left, starting with module number 1.

ID

Data_Type Default_Value Range Unit
WORD - - -

Input ID is used to specify the identifier of the CAN 2.0A telegrams to be read from the buffer. If no buffer has been specified for the selected identifier using the controller configuration, this is indicated accordingly at the Function Block outputs.

DATA

Data_Type Default_Value Range Unit
DWORD - - -

Input DATA is used to specify the address starting from which the received CAN 2.0A telegrams should be written. Usually, this specification is done via the ADR operator and should point to variables of the type CAN2A_MESSAGE_TYPE or CANOpen_MESSAGE_TYPE.