IFM AL4002, Руководство по эксплуатации

Страница: 30 / 68

AL4002 Remote I/O module 16 DI
30
{
"code":"request",
"cid":-1,
"adr":"devicetag/applicationtag/getdata"
}
• Response:
{
"cid":-1,
"data":{"value":"Do not use"},
"adr":"devicetag/applicationtag/getdata",
"code":200
}
9.2.2 Getting started
To register the device description:
u Send the following POST request to the ifm IoT Core:
{"code":"request", "cid":-1, "adr":"gettree"}
w
ifm IoT Core returns the device description as a structured JSON object.
u
Identify all substructures and the data points contained therein in the tree structure of the JSON
object.
u
Identify the applicable services for the access to substructures and the data points contained
therein.
9.2.2.1 Notes on configuration
The configuration created via the IoT Core (API, IoT Core Visualizer) is overwritten when a
connection is established between the device and the fieldbus PLC.
9.2.3 General functions
The device has the type “device” (
Ò
Types
/
48). The following services can be applied to the root
element of the device tree:
Service Description
../gettree Provide the complete tree or subtree of the device description (JSON)
../getidentity Read identification information of the device
../getdatamulti Reading several elements sequentially
../getelementinfo Reading detailed information of an element
../getsubscriberlist Print a list of all active notification subscriptions
../querytree Search device description for specific elements
The following services can be applied to elements of the type
data
depending on its access rights:
Service Description
../getdata Reading the value of the element
../setdata Write the value of the element
9.2.3.1 Example: Outputting the subtree
Task: Output all direct sub-elements of the node firmware.