Balluff BNI EIP-508-105-Z067, Configuration Manual

Page: 86 / 88

42 english
954775_AB ∙ EN ∙ E22; Subject to modification. Replaces C22.
6.8.3 Requesting port information
All relevant configuration and status data for all IO ports of
a module can be requested via:
http://[ip-address]/api/balluff/v1/ports/information
Fig. 6-41: Requesting the port identification
6.8.4 Requesting an IO-Link device parameter
(applicationSpecificTag)
Device-specific parameters can be requested via the
following addresses:
– http://[ip-address]/api/balluff/v1/devices/identification
– http://[ip-address]/iolink/v1/devices/[deviceAlias]/
identification
A request via the generic REST API is the bulk version of
the identical request via JSON for IO-Link .
In the case of a request via JSON for IO-Link , a deviceAlias
is also specified. This corresponds to the device
designation that must be configured previously. The
standard device designation is Port_Xyz , with yz
representing the port number (e.g. Port_00 ).
In the case of successful execution, a JSON object with
parameters such as vendorID , productName and
applicatonSpecificTag
is supplied as a response.
6
WebUI/web interface (continued)
6.8.5 Setting an IO-Link device parameter
(applicationSpecificTag)
The use of a POST request requires login (see
chapter 6.8.1 on page 41).
Device-specific parameters for connected IO-Link devices
can be set via the following address:
http://[ip-address]/iolink/v1/devices/{deviceAlias}/
parameters/{index}/value
The
deviceAlias corresponds to the device designation of
the IO-Link device (e.g. Port_00 ). The Index reflects the
ISDU parameter variable to be set in the IO-Link device. In
the case of the applicationSpecificTag , this would be the
value 24.
To set values, a JSON object must also be specified, in
which corresponding parameters and values are specified
as in the following example:
{ “value”: [
49,
50,
51,
52,
53,
54
]}
In the case above, parameter 24 ( applicationSpecificTag )
was described with the ASCII string 123456 .
Successful execution is not confirmed in the form of a
JSON object, but with a Code 204 ( Successful operation ).
6.8.6 Setting a master parameter (sysName)
The use of a POST request requires login (see
chapter 6.8.1 on page 41).
A master parameter, such as SysName , can be set via the
following address: http://[ip-address]/api/balluff/v1/
A JSON object with the corresponding information must
also be specified:
{
“sysName”: “[SysName]”
}
Successful execution is not confirmed in the form of a
JSON object, but with a Code 204 ( Successful operation ).
If you are unable to implement your application
case with the examples listed below and the
information from the specifications for the REST
APIs, please contact us with a description of your
application case.
You can find the corresponding contact details at
www.balluff.com
.
BNI EIP-508-105-Z067
Network interface