Manual

© EA Elektro-Automatik in 2022, this information is subject to change without notice 5433200840_manual_elr_10000_2u_3kw_en_02
3.5 Remote control
3.5.1 General
Remote control is possible via one of the built-in interfaces (analog, USB, Ethernet) or via one of the optional interface modules.
One of the digital interface is the master-slave bus. It means that a Slave model is supposed to be controlled from a master
unit via the master-slave bus. Controlling a Slave device via its rear USB port is considered an exception.
Important here is that only the analog or any digital interface can be in control. It means that if an attempt was made to switch
to remote control via the digital interface whilst analog remote control is active (pin REMOTE = LOW) the device would report
an error via the digital interface. In the opposite direction, a switch-over via pin REMOTE would be ignored. However, status
monitoring and reading of values are always possible.
3.5.2 Control locations
Control locations are those locations from where the device can be controlled. Essentially there are two: at the device (manual
operation) and external (remote control). The following locations are dened:
Displayed location Description
Remote: None If neither of the other locations is displayed then manual control is active and access from
the analog and digital interfaces is allowed.
Remote: <interface_name> Remote control via any interface is active
Local Remote control is locked, only manual operation is allowed.
Remote control may be allowed or inhibited using the setting Allow remote control (see “3.4.3.1. Sub menu “Settings”” ). In
inhibited condition the status “Local” will be displayed top right. Activating the inhibit can be useful if the device is remotely
controlled by software or some electronic device, but it’s required to make adjustments at the device or deal with emergency.
Activating condition Local causes the following:
• If remote control via the digital interface is active (e. g. Remote: USB), then it’s immediately terminated and in order to con-
tinue remote control once Local is no longer active, it has to be reactivated at the PC
• If remote control via the analog interface is active (Remote: Analog), then it’s temporarily interrupted until remote control is
allowed again by deactivating Local, because pin REMOTE continues to signal “remote control = on”, unless this has been
changed during the Local period.
3.5.3 Remote control via a digital interface
3.5.3.1 Selecting an interface
In addition to the built-in USB and Ethernet ports, all models of this series support the following optionally available interface
modules:
Short ID Type Ports Description*
IF-AB-CANO CANopen 1 CANopen slave with generic EDS
IF-AB-RS232 RS232 1 Standard RS232, serial
IF-AB-PBUS Probus 1 Probus DP-V1 slave
IF-AB-PNET1P ProNet 1 Pronet DP-V1 slave
IF-AB-PNET2P ProNet 2 Pronet DP-V1 slave, with switch
IF-AB-CAN CAN 1 CAN 2.0 A / 2.0 B
IF-AB-ECT EtherCAT 2 Standard EtherCAT slave with CoE
IF-AB-MBUS1P ModBus TCP 1 ModBus TCP protocol via Ethernet
IF-AB-MBUS2P ModBus TCP 2 ModBus TCP protocol via Ethernet
* For technical details of the various modules see the extra documentation “Programming Guide Modbus & SCPI”
3.5.3.2 Programming
Programming details for the rear interfaces, the communication protocols etc. are to be found in the documentation “Pro-
gramming Guide ModBus & SCPI“ which is supplied on the included USB stick or which is available as download from the
manufacturer’s website.