<< Click to Display Table of Contents >> Navigation:  »No topics above this level« DCAN line

It is possible to send and receive CAN messages to and from a CAN bus using the DCAN (direct CAN) line (message exchange according to the producer/consumer principle). The DCAN line also supports RTR (Remote Transmission Request) objects.

Unlike INA2000 communication via CAN, the contents of the CAN messages are not interpreted. This allows communication with CAN slaves to be established for example.

The following topics are covered in this section:

•DCAN process objects

•DCAN access types

•DCAN event types

•DCAN communication

DCAN process objects

A line object, a device object, a station object, and a variable object are all necessary to send or receive CAN messages with a certain CAN ID.

Process objects in the DCAN line:

Allowed object structure for DCAN process objects:

DCAN access types

The following table shows an overview of all access types which are regulated via a line. All access types not listed here as well as access types to the PVI base object are executed by PVI Manager and therefore work independently of the line being used. The corresponding process object type is listed in the "Type" column.

DCAN event types

The following table shows an overview of all event types which can be generated from a line. All event types which are not listed are generated by PVI Manager and therefore work independently of the line being used.