Identification data Origin
For example, Profil_OSM_V10.txt Profile MIB-II
Address HW Config/OPC server "IP address" /
SNMP variable ".&ipAddress()"
Description Not available
Message
Device type
2)
WBM
1)
"Device Type" /
SNMP variable ".sysDescr"
Manufacturer WBM
1)
"automationManufacturerId" Not available
Article number
3)
SNMP variable ".snInfoOrderNr"
Serial number SNMP variable ".snInfoSerialNr"
Installation date Not available
HW revision SNMP variable ".snHWVersion" Not available
SW revision SNMP variable ".snSWVersion" Not available
Last update Time stamp of the updating of the identification data
Comment HW Config/OPC server "Comment"
1)
WBM = Web based management (Web interface of the network object)
2)
If the SNMP variable ".sysDescr" contains identification information in addition to the device
type, this will be displayed in the corresponding field. The "Device type" field only displays
information about the device type.
3)
Article number = Also order number or MLFB
6.12.4 Identification data for AS objects
Where does the identification data for an AS object come from?
In the case of the faceplate for AS objects, the identification data is read from the properties
of the module or dynamically from the CPU.
The following table shows the assignment of the identification data displayed on the MS to the
origin.
Identification data Origin
HID / TAG
static
dynamic
HW Config "Higher level designation" (HID)
I&M data (SZL), (I&M1 Tag_Function)
LID
static
HW Config "Designation" or "Name"
Address HW Config
"Slot/address information"
Description
static
dynamic
HW Config "additional information"
I&M data (SZL), (I&M3 Descriptor)
Message Not available
Operator control and monitoring
6.12 Origin of the identification data
Maintenance Station
Function Manual, 03/2016, A5E36187641-AA 185