3
AuthorizedClient (entry of password required)
4
Service (entry of password required)
■
Has limited functionality compared to the SOPAS ET configuration software.
The functionality of the web server depends on the firmware version of the device.
3. Command strings (telegrams)
■
Command strings (CoLa) are used to configure device parameters and trigger
device functions (e.g. reading).
■
Command strings can be inputted in telegram style at one of the available data
interfaces (Aux or host interface) of the device. The telegram response of the
device to the command is always sent to the interface on which the telegram was
received. In contrast to this, the read result data can be outputted to all data inter‐
faces except for the USB interface.
■
The communication between the SOPAS ET configuration software and the device
can be monitored and recorded via the terminal emulator in SOPAS ET. Com‐
mands can also be sent to the device. For more details on using the terminal, see
the SOPAS ET manual.
■
Documents listing and describing the available commands strings can be obtained
from SICK on request.
NOTICE
Both the command strings and the SOPAS ET configuration software are based on
a command language that has direct access to the command interpreter of the
device. The command language must be used with care, as the commands
received by the device are executed immediately.
Parameter values modified by means of commands are initially only active in the
current parameter set in the volatile working memory of the device. To perma‐
nently save the modified parameter set, it needs to be copied to the non-volatile
parameter memory using the relevant command. This ensures the changes are
not lost when the supply voltage to the device is switched off.
Any changes to the parameter values in the device made using command strings
will only appear in the SOPAS ET configuration software after the following actions:
•
An upload of the current parameter set from the device, or
•
A synchronization between the device and SOPAS ET
4. Control software of a PLC controller
■
The controller of a fieldbus (e.g. PLC) configures the device. For a PROFINET con‐
troller, for example, this is done via PROFINET by means of GSD parameterization.
Backup of the parameter set as a configuration file in the PROFINET controller. The
controller reconfigures the device at every PROFINET restart.
■
Integrating the device into the most important fieldbus systems is made simpler
with SICK function blocks for the relevant bus controller. See the “Downloads /
Software” section online at:
°
°
■
Function blocks based on command strings (CoLa).
5. SICK AppStudio development environment
■
Used, for example, to implement user-specific data output protocols for the device.
Based on functionality already pre-installed in the programmable device.
■
The app programmed using SICK AppStudio is loaded onto the device as a sensor
app.
■
More information is available online at:
8
OPERATION
80
O P E R A T I N G I N S T R U C T I O N S | RFU63x, RFU65x
8014335/ZTL9/2018-10-14 | SICK
Subject to change without notice