HMS Networks Anybus CompactCom 40 Network Manual page 160

® ™
Anybus CompactCom 40 - PROFINET IRT Transparent
Ethernet
2. Reidentifying Your Product
After successful setting of the Setup Complete attribute in the Anybus Object (01h), the Anybus module asks
for identification data from the host PROFINET IO Object (F6h). Therefore, the attributes listed below shall be
implemented and proper values returned.
Object/Instance Attribute
PROFINET IO #1,Device ID
Object (F6h),
Instance 1
PROFINET IO #2,Vendor ID
Object (F6h),
Instance 1
PROFINET IO #3,Station
Object (F6h), Type
Instance 1
PROFINET IO #8, I&M
Object (F6h), Order ID
Instance 1
PROFINET IO #10, I&M
Object (F6h), Hardware
Instance 1 Revision
PROFINET IO #11, I&M
Object (F6h), Software
Instance 1 Revision
PROFINET IO #13, I&M
Object (F6h), Profile ID
Instance 1
PROFINET IO #14, I&M
Object (F6h), Profile
Instance 1 Specific type
2.1. Additional GSD File Information
The GSD file keyword "ProductFamily" shall correspond to the vendor's name of the device.
The GSD file keyword "MainFamily" lists the kinds of devices for which the product shall be listed. As of GSD
specification v2.3, the following "families" are available:
"General", "Drives", "Switching Devices", "I/O", "Valves", "Controllers", "HMI","Encoders", "NC/RC", "Gateway",
"PLCs", "Ident Systems", "PA Profiles", "Network Components", "Sensors".
3. Factory Default Reset
Reset command to Application Object (FFh) must be supported.
When PROFINET IO modules are delivered, they are required to be in their "Factory Default" state. For PROFINET
devices this means that their Station Name is empty ("""") and that the IP suite is not assigned (IP 0.0.0.0). When
a Factory Default Reset command is received from the network, the Anybus module will erase all IP and Station
Name information and inform the host application that a hardware reset of the Anybus module is required. This
is done by sending a Reset command to the Application Object (FFh) of the host. For more details, please consult
the Anybus CompactCom Software Design Guide.
Page 152 of 177
Explanation Default
With this attribute you Device ID: 0010h
set the Device ID of the
device
With this attribute you Vendor ID: 010Ch
set the Vendor ID of the (HMS)
device
With this attribute you "CompactCom 40
set the station type of PIR"
the device
With this attribute you "CompactCom 40
set the Order ID that is PIR"
used in the I&M data
With this attribute you (Hardware Rev.)
set the I&M Hardware
Revision
With this attribute you (Software Rev.)
set the I&M Software
Revision
With this attribute you 0xF600 (Generic
set the I&M Profile ID device)
With this attribute you 0x0004
set the I&M Profile (Communication
Specific type Module)
Reidentifying Your Product
Customer Comment
sample
Device ID: This information must match the keys
YYYYh of the "DeviceIdentity" of the GSD-
file. Note that the GSD file keyword
"VendorName" must correspond to the
Vendor ID:
Vendor ID value.
XXXXh
"Cust-PNIO- Optional if Application Object, Instance
Dev" 1, Attribute 9 "Product Name" is
implemented. In this case the product
name common for all networks will be
used as Station Type/Device Type on
PROFINET.
"Cust-PNIO- This information must match the keys of
Dev" "theOrderNumber" of the GSD-file.
"0002h" Optional. This information must match
the keys of the "HardwareRelease" of
the GSD-file.
"V2.5.3" Optional. This information must match
the keys of the "SoftwareRelease" of the
GSD-file.
API number Optional, Only relevant for multi-API
of profile. implementations like PROFIdrive.
Profile Optional, Only relevant for multi-API
specific type, implementations like PROFIdrive.
defined by
profile.
SCM-1202-021 Version 2.6