Anybus CompactCom 40 User Manual

JSON 67 (258)
JSON response example (using inst):
[
"FF",
"A201",
null,
null,
"01FAC105"
]
metadata.json
GET adi/metadata.json?offset=<offset>&count=<count>[&callback=<function>]
GET adi/metadata.json?inst=<instance>&count=<count>[&callback=<function>]
These object calls fetch a sorted list of metadata objects for up to <count> ADIs, starting from
<offset> or <instance>.
The returned information provided is a transparent representation of the attributes available in
the host Application Data object (FEh). See the Anybus CompactCom 40 Software Design
Guide for more information about the content of each attribute.
The ADI metadata is static during runtime.
Request data:
Name Data Type Description
offset Number Offset is the “order number” of the first requested ADI.
The first implemented ADI will always get order number 0. Meta-
data objects for <count> number of existing ADI will be returned. I.
e. non-existing ADIs are skipped.
inst Number Instance number of first requested ADI.
Metadata objects for <count> number of ADI values are returned.
A null object will be returned for non-existing ADIs
count
String Number of requested ADI values
callback Number Optional.
A callback function for JSONP output.
Response data:
Name Data Type Description
instance Number
-
name
String May be NULL if no name is present.
numelements Number
-
datatype Number
-
min String Hex formatted string, see Hex Format Explained, p. 83 for more
information.
May be NULL if no minimum value is present.
max
String Hex formatted string, see Hex Format Explained, p. 83 for more
information.
May be NULL of no maximum value is present.
access
Number Bit 0: Read access
Bit 1: Write access
Anybus
®
CompactCom
™
40 PROFINET IRT Network Guide SCM-1202-023 EN 1.8

Anybus CompactCom 40 Specifications

General

Brand	Anybus
Model	CompactCom 40
Category	Control Unit
Language	English