6-4 Explicit Messaging on DeviceNet™
•Size:
This identifies the size of the transaction body in bytes. The
transaction body begins at word 3. The maximum size is 58 bytes.
The Size data size is one byte.
• Service:
This code specifies the type of request being delivered. The
Service data size is one byte.
•MAC ID:
The DeviceNet™ network node address of the device for which
the transaction is intended is identified here. The slave device
must be listed in the scanner module’s scan list and be on-line for
the explicit message transaction to be completed.
•Class:
The desired DeviceNet class is specified here.
• Instance:
This code identifies the specific instance within the object class
towards which the transaction is directed. The value zero is
reserved to denote that the transaction is directed towards the
class itself versus a specific instance within the class.
• Attribute:
This code identifies the specific characteristic of the object
towards which the transaction is directed. The attribute data size
is one word.
Setting up the Data File The following table lists the most common transaction types (get
information and set information), and the appropriate service, class,
instance, and attribute that corresponds to the type.
Table 6.6 Common Configuration Examples for ArmorStart
➊ The numeric values are in a hexadecimal format.
➋ This is the actual parameter number.
➌ The code “1” specifies the value of the instance (parameter).
Transaction Type Service ➊ Class ➊ Instance ➊ Attribute ➊
Get_Attribute_Single 0x0E 0x0F Par. #
➋ 1 ➌
Set_Attribute_Single 0x10 0x0F Par. # ➋ 1 ➌
To Next Page
Loading...
Need help?
General
