Vacon 100 - Page 43

Communications vacon • 41
24-hour support +358 (0)201 212 575 • Email: vacon@vacon.com
6
As an example, if the drive parameter with ID=2291
d
(08F3
h
) is read from the drive, then the
Get_Attribute_Single service request is targeted at the Vendor Parameters class, instance 08
h
and
attribute F3
h
.
The Vacon 100 integrated EtherNet/IP implementation supports the above mechanism from OPTCQ
for backwards compatibility reasons. It shall also support the use of a 16-bit attribute identifier, in
which case the request shall always be targeted to instance #1 of the class.
With the same example above, the request would be targeted at the same class, instance 01
h and
attribute 08F3
h
.
Instance Service “Get_Attribute_Single”
This class has an instance service named “Get_Attribute_Single” which has the Service Code 0E
h
.
When invoked in an instance, the parameter ID to be fetched from the drive is calculated, then the
read operation is started and once available, a response is provided to the master.
The format of the message is as follows (Vacon 100):
The old format of the message is as follows (OPTCQ option board):
Instance Service “Set_Attribute_Single”
This class has an instance service named “Set_Attribute_Single” which has the Service Code 10
h
. When
invoked in an instance, the parameter ID to be modified in the drive is calculated. The data type,
write permission etc. is verified before the write operation is started. When the operation finishes,
or if an error occurs, an appropriate response is provided to the master.
The format of the message is as follows (Vacon 100):
Table 27.
Drive prm ID high octet Drive prm ID low octet
Attribute # high octet Attribute # low octet
Table 28.
Field Data
Service Code 0E
h
Class Code A0
h
Instance Number 01
h
Attribute ID XXXX
h
Table 29.
Field Data
Service Code 0E
h
Class code A0
h
Instance Number YY
h
Attribute ID XX
h