GE Industrial Solutions 6KCV301DNET - Manual (Page 17)

6KCV301DNET
17
——————
Interface card DeviceNet
——————
3.2.1.6 Behavior
This object is the interface between the DeviceNet network and all Drive pa-
rameters. The access to the Drive parameter is carried out by the parameter
index; if the parameter does not exist or may not be accessed for any reason
(for example: try to write a read only parameter) an error code will be returned.
Drive parameters in text format cannot be accessed.
In the following are repeted patterns of how the data frame of data has to be
composed for reading/writing Drive parameters.
3.2.1.6.1 Write Drive Parameter
In this example the writing of a Drive parameter is shown; the cases of positive
or wrong writing are distinguished.
3.2.1.6.1.1 Write Drive Parameter Request
The data frame for writing a drive parameter is composed as follows:
DATA TYPE FIELD VALUE MEANING
Byte
Service
Code
33hex
Set Drive Parameter -
Object Specific Service.
Class ID 66hex
Drive Parameter Access
Class Object.
Instance
ID
XXXX
Drive Parameter Index in
format Low byte-High
byte.
XX
Low byte-Low word drive
parameter value.
XX
High byte-Low word drive
parameter value.
XX
Low byte-High word drive
parameter value.
XX
High byte-High word
drive parameter value.
dn360
VALUE Byte 2)
See Note 1)
1) Byte or Word depending on the type of allocation executed by the Master.
2) The number of bytes of the “Value”-field depends on the length of the
Drive parameter; i.e.: if the Drive parameter type is “Integer” the length of
VALUE is 2 bytes.