IO-Link master with EtherCAT interface DataLine 4 ports IP 65 / IP 66 / IP 67
43
Example: Using DNS support
61152
Example 1:
gettree
Synonymous requests:
•
http://192.168.23.70:8080/gettree
•
http://example.org:8080/gettree
Example 2:
subscribe
Synonymous requests:
•
with IP address
{
"cid": 11
"code": 10,
"adr." "setasync/datachanged/subscribe",
"data":{
"datatosend":["setasync"],
"callback":"192.168.23.70:8080/dump"}
}
•
with host name
{
"cid": 11
"code": 10,
"adr": "setasync/datachanged/subscribe",
"data":{
"datatosend":["setasync"],
"callback":"http://example.com:8080/dump"}
}
>
9.2.4
IoT: Configuring access rights
59785
Substructure:
iotsetup
Available data points:
Name
Description
Access
../accessrights
Access rights to the IO-Link master
rw
rw ... read and write
If in IoT and EtherCAT projection software the parameter [Access Rights] is = [Et
IoT], the parameter values set in the EtherCAT projection software will always apply.
If in IoT the parameter [Access Rights] is = [IoT only], set the parameter [Access Rights] =
[Keep settings] in the EtherCAT projection software.
If in LR DEVICE the parameter [Access Rigts] is = [Et IoT (read-only)], write access
to the device configuration via LR DEVICE and IoT core services is blocked. To enable write
access again, set the parameter to [Et IoT] via fieldbus configuration software.
Changes of the parameter [Access Rights] will only be effective after restarting the IO-Link
master (
→
Firmware: Reboot the device
(
>