Tutorial
8 (36)
3.3.1
Reidentifying Your Product
After successful setting of attribute #5 (Setup Complete) in the Anybus Object (01h), the Any-
bus CompactCom 30 asks for identification data from the CANopen Object (FBh). Therefore,
the attributes listed below shall be implemented and proper values returned.
Object/Instance
Attribute
Explanation
Default
Customer
sample
Comment
CANopen Object
(FBh), Instance 1
#1, Vendor
ID
With this at-
tribute you set
the Vendor ID
of the device.
Vendor ID:
001Bh
Vendor ID:
1111h
This information must
match the keyword values
of the “Device” section in
the EDS file.
CANopen Object
(FBh), Instance 1
#2, Prod-
uct Code
With this at-
tribute you set
the Product
Code of the
device
0000 000Ah
0000 2222h
CANopen Object
(FBh), Instance 1
#3, Major
Revision
With this at-
tribute you set
the Major Re-
vision of the
device.
0001
CANopen Object
(FBh), Instance 1
#4, Minor
Revision
With this at-
tribute you set
the Minor Re-
vision of the
device.
0001
CANopen Object
(FBh), Instance 1
#6, Manu-
facturer
Device
Name
With this at-
tribute you set
the Product
Name of the
device.
Anybus-CC
CANopen
“Widget”
This information must
match the keyword values
of the Device section in
the EDS file.
3.3.2
Factory Default Reset
Reset command to Application Object (FFh) must be supported
When Anybus CompactCom 30 CANopen products are delivered, they are required to be in
their Factory Default state. The application has to support reset with power cycle and factory de-
fault reset, see
Network Reset Handling, p. 13
.
3.3.3
Modify the EDS File
Modify the Anybus CompactCom CANopen EDS file so that it corresponds to the vendor prod-
uct (e.g. Vendor ID, Product Name and Product Number along with ADI object names, that cor-
respond to descriptive names in the application. Also the ADI information must correspond.).
The EDS file has to contain all ADIs created by the application. Run the EDS file checker pro-
gram from
www.can-cia.org
.
See also
Electronic Data Sheet (EDS), p. 9
.
Anybus
®
CompactCom
™
30 Network Guide
HMSI-168-78 EN 4.1