Parameterization of CAN 2.0A / CAN 2.0B¶
The CAN data transmission requires a buffer for the incoming data that can be read with Function Blocks of library CANopen_AC500_Vxx.lib.
Right-click CAN_2_0A_11_bit_identifier_ (CAN 2.0A) or CAN_2_0B_29_bit_identifier_ (CAN 2.0B) and select Add object.
For CAN 2.0A select Buffer for CAN 2A. For CAN 2.0B select Buffer for CAN 2B from the list.
In the device tree, double-click on Buffer_for_CAN_2A (Buffer for CAN2A) or Buffer_for_CAN_2B (Buffer for CAN2B) to open the Buffer configuration in the editor window.
The following parameters are available:
| Parameter | Default value | Value | Meaning |
|---|---|---|---|
| Identifier | 0 | CAN 2A: 0…2047 CAN 2B: 0…536870911 |
The value of the CAN identifier that is compared with the identifier of the incoming telegrams. The telegrams will be added to the buffer if the identifier matches. |
| Number of receive buffers | 1 | 1..16 | The size of the buffer in number of telegrams. |
| Behaviour on receive buffer overflow | Overwrite | Overwrite | The oldest telegram in the buffer is overwritten by the incoming telegram. |
| Discard | The incoming telegrams are discarded as long as the buffer is full. | ||
| Wait | The incoming telegram is stored as soon as a telegram is read out of the buffer. | ||
Enable triggering of IEC task (only for CM598-CN) |
No | No | No triggering of IEC task |
| Yes | On receiving of a CAN object with this identifier the CAN manager triggers an IEC task. A task of type “triggered by external event” has to be configured. The external event has to be “CAN2A event”/”CAN2B event”. |