Operating instructions

5. How to Access the Parameters
5.1. Explicit Messages
DeviceNet is based on the CAN protocol. This means that every message contains an 11-bit CAN
identifier field to define the connection ID. These CAN identifiers are also used to determine access
priority.
The MAC ID is stored in the header of the message, which is split into four different message
groups.
10
9 8 7 6 5 4 3 2 1 0 Identifier bits
0 Group 1 ID Source MAC ID Message Group 1
1 0 MAC ID Group 2 ID Message Group 2
1 1 Group 3 iD Source MAC ID Message Group 3
1 1 1 1 1 Group 4 ID Message Group 4
1 1 1 1 1 1 1 X X X X Invalid Can Identifiers
FC 100, 200 and 300 parameters can be accessed by the Standard DeviceNet service Explicit
Message. Two classes of explicit messages are supported: Message group 2: Explicit messages
take place via pre-defined master/slave connections. Message group 3: Explicit messages take
place via dynamically established lower prioritized connections.
5.2. Object Classes
The following Standard DeviceNet objects can be accessed:
Class ID 01h Identity Object Class ID 10h Parameter Group Object
Class ID 03h DeviceNet Object Class ID 28h Motor Data Object
Class ID 04h Assembly Object Class ID 29h Control Supervisory Object
Class ID 05h Connection Object Class ID 2Ah AC/DC Drive Object
Class ID 0Fh Parameter Object Class ID 2Bh Acknowledge Handler Object
The following DeviceNet Vendor Specific Objects are also available:
Class ID 100d to 119d Danfoss Classes.
The above Object classes are described in the following sections:
DeviceNet Object Classes and
Danfoss Object Classes .
5.3. DeviceNet Object Classes
5.3.1. Class ID 01h Identity Object
This is a standard DeviceNet Object for identification of the device (frequency converter). The
Heartbeat Interval can be set in this Object. The attributes supported for this class are listed below.
FC 100/ 200/ 300 DeviceNet 5. How to Access the Parameters
MG.33.D3.02 - VLT
®
is a registered Danfoss trademark 39
5