Expert Sensor Box 7213 - Humidifier GUDE - Free user manual and instructions
Find the device manual for free Expert Sensor Box 7213 GUDE in PDF.
| Product Type | Humidifier with integrated sensor box |
| Brand | Güde |
| Model | Expert Sensor Box 7213 |
| Dimensions (W x H x D) | 200 x 300 x 200 mm |
| Weight | 1.5 kg |
| Power Supply | 220-240 V AC, 50/60 Hz |
| Power Consumption | 25 W (max) |
| Water Tank Capacity | 3.0 L |
| Mist Output | 250 ml/h (max) |
| Noise Level | ≤ 35 dB(A) |
| Coverage Area | Up to 30 m² |
| Humidity Sensor | Built-in, range 20-90% RH |
| Temperature Sensor | Built-in, range 0-50°C |
| Display | LED touch panel with humidity and temperature readout |
| Functions | Auto mode, manual mist level, timer (1-12 h), sleep mode, child lock |
| Filter Type | Replaceable evaporative filter (model: GF-7213) |
| Water Level Indicator | Yes, visual and audible alert |
| Cleaning & Maintenance | Weekly cleaning of tank and filter; descale monthly |
| Safety Features | Auto shut-off when tank empty, overheat protection |
| Warranty | 2 years |
| Repairability | Replaceable filter and fan; spare parts available |
| Package Contents | Humidifier, filter, user manual, quick start guide |
Frequently Asked Questions - Expert Sensor Box 7213 GUDE
User questions about Expert Sensor Box 7213 GUDE
0 question about this device. Answer the ones you know or ask your own.
Ask a new question about this device
Download the instructions for your Humidifier in PDF format for free! Find your manual Expert Sensor Box 7213 - GUDE and take your electronic device back in hand. On this page are published all the documents necessary for the use of your device. Expert Sensor Box 7213 by GUDE.
USER MANUAL Expert Sensor Box 7213 GUDE
1.1 Security Advice 6 1.2 Content of Delivery 6 1.3 Description 6 1.4 Installation 7
1.4.1 Terminal Assignment 8
1.5 Redundant Voltage Supply 9 1.6 Technical Specifications .... 10 1.7 Sensor 10
2. Operating 14
2.1 Operating the device directly 15 2.2 Control Panel 15 2.3 Maintenance 17
2.3.1 Maintenance Page 19 2.3.2 Configuration Management 20 2.3.3 Bootloader Activation 21
3. Configuration 23
3.1 Output Ports 24 3.1.1 Watchdog 25 3.2 Input Ports 27 3.3 Ethernet 27
3.3.1 IP Address 28 3.3.2 IP ACL 29 3.3.3 HTTP 30
3.4 Protocols 31
4.4 Automated Access 50
4.5 SNMP 51
4.5.1 Device MIB 7213 53
4.5.2 Device MIB 7214 55
4.6 SSL 56
4.7 Console 58
4.7.1 SSH 62
4.7.2 Push Messages 62
4.7.3 Console Cmd 7213 63
4.7.4 Console Cmd 7214 68
4.8 Modbus TCP 74
4.9 Messages 79
5. Support 80
5.1 Data Security 81
5.2 Contact 81
5.3 Declaration of Conformity 82
5.4 FAQ 82
Index 84
Device Description
1 Device Description
1.1 Security Advice
- The device must be installed only by qualified personnel according to the following installation and operating instructions.
- The manufacturer does not accept responsibility in case of improper use of the device and particularly any use of equipment that may cause personal injury or material damage.
- The device contains no user-maintainable parts. All maintenance has to be performed by factory trained service personnel.
- The device may only be connected via a low voltage power supply to 230V AC (50 Hz or 60 Hz) power supply sockets.
- The device is intended for indoor use only. Do NOT install them in an area where excessive moisture or heat is present.
- Because of safety and approval issues it is not allowed to modify the device without our permission.
- The device is NOT a toy. It has to be used or stored out of range of children.
- Care about packaging material. Plastics has to be stored out of range of children. Please recycle the packaging materials.
- In case of further questions, about installation, operation or usage of the device, which are not clear after reading the manual, please do not hesitate to ask our support team.
1.2 Content of Delivery
The package includes:
• Expert Sensor Box 7213 / 7214 • Power supply unit 7903 (12V DC, 1 A) (for 7213-1, 7213-2, 7213-3) - Quick Start Guide
1.3 Description
Depending on the model, the Expert Sensor Box 7213 / 7214 offers several environmental sensors. The device has the following features:
Devices with voltage input:
• Temperature Sensor (Expert Sensor Box 7213-1 / 7214-1) - Sensors for temperature and humidity (Expert Sensor Box 7213-2 / 7214-2) - Sensors for temperature, humidity and air pressure (Expert Sensor Box 7213-3 / 7214-3)
Devices with additional Power-over-Ethernet (PoE):
• Temperature Sensor (Expert Sensor Box 7213-11 / 7214-11) - Sensors for temperature and humidity (Expert Sensor Box 7213-12 / 7214-12) - Sensors for temperature, humidity and air pressure (Expert Sensor Box 7213-13 / 7214-13)
General:
- Connection for 2 optional sensors for ambient monitoring (temperature, humidity and air pressure)
- Console commands via SSH and Telnet
- SSH support with public key and passwords
- Programmable timetables for console commands
- Dual TCP/IP stack with IPv4 and IPv6 support (IPv6-ready)
- Control and monitoring of the device via Ethernet with an integrated web server with SSL encryption (TLS 1.1, 1.2, 1.3)
- Configuration with CGI parameters and JSON messages via HTTP (REST API) • SNMP (v1, v2c and v3, traps)
- Modbus TCP support
- Radius support
- Generation of messages (e-mail, syslog and SNMP traps) depending on sensor measurement limits
- Firmware update during operation via Ethernet possible • Encrypted e-mails (SSL, STARTTLS)
- Access protection through IP access control
- Low own consumption • Developed and produced in Germany
Additionally with Expert Sensor Box 7214:
- An additional input for redundant voltage supply (12 V DC 1 A)
- A switchable, potential-free relay output with change-over contact (NO and NC), high switching capacity 36 V, 3 A
- The relay has high contact reliability even at very small loads
- Switch state and switch-on delay (0 ... 9999 seconds) can be set for the relay output after power failure
- Programmable timetables and turn-on/turn-off sequences
- A watchdog (ICMP / TCP) can be assigned to the output port
- Passive signal input for polling NO/NC devices (e.g., smoke detector, leak sensor, door contact) • The signal input has a 12 V connector for supplying the NO/NC devices
1.4 Installation

- Connector Sensor Port 1
- Connector Sensor Port 2
- Ethernet connector (RJ45) (with Pwr3 = only devices with PoE)
- Status LED
- Connector (Pwr1) for power supply 12 V DC, 1 A

- Housing for integrated Sensor
- Connector (Pwr2) for power supply 12 V DC, 1 A (only ESB 7214)
- Passive input (only ESB 7214)
- Potential-free relay output (only ESB 7214)
- Select Button
Power Supply
If the device has PoE or a second input for the supply voltage, all voltage sources can be connected at the same time. This allows redundancy in the power supply.
Start-up the device
- Connect the device (Pwr1 or Pwr2) to the AC Adaptor (12 V DC, 1 A).
- Optional connect the device to a second AC Adaptor (12 V DC, 1 A).
- Plug the network cable into the Ethernet (RJ45).
- Attach the optional external sensors to the connectors.
- Connect the passive inputs and relay outputs to compatible devices.
1.4.1 Terminal Assignment
The terminal assignment of the terminals is printed on the housing surface:

The digital signal input (input ports) goes to the logic state "LOW" when the pin "In" and the center pin "GND" are bridged, otherwise the state is "HI". The text outputs associated with the "LOW" and "HI" states can be defined in the Input Ports configuration. In the default configuration, the logic states are inverted so that the state "HI" is assumed for a bridged contact.
This means that there is only a connection between the center pin (COM) and the NC-pin (Normally Closed) for the output ports in the "Off" state. If the relay is in the "On" state, then there is only contact from the center pin (COM) to the NO-pin (Normally Open).
As an alternative to the connection of "In" and "GND", voltages of up to 24 V (= VInmax) can be connected to the input "In". For voltages less than 4 V the state goes to "LOW", for voltages greater than 8 V the "HI" state is assigned.
1.5 Redundant Voltage Supply
If the device and the connected switch support Power-over-Ethernet, the power supply via PoE has priority and the device is powered only via PoE. Alternatively, the device can be supplied via up to two power supply units. If both power supplies (only ESB 7214) are connected at the same time, the current is split up. The current distribution depends on the difference between the output voltages of the two power supplies.
1.6 Technical Specifications
| Interfaces(only ESB 7214)(only ESB 7214)(only ESB 7214) | 1 x socket for power supply2 x RJ45 for external sensors1 x Ethernet connector RJ451 x additional socket for power supply1 x switchable output1 x passive signal input |
| Network connectivity | 10/100 MBit/s 10baseT Ethernet |
| Protocols | TCP/IP, HTTP/HTTPS, SNMP v1/v2c/v3, SNMP traps,Syslog, E-Mail (SMTP), Modbus, Radius |
| Power Supply | AC Adaptor (12V DC, 1 A)Power-over-Ethernet Module |
| PoE Module (not all models) | 802.3af (802.3at Type 1) PoE, Class 0 |
| Environment• Operating temperature• Storage temperature• Humidity | 0°C - 50 °C-20°C - 70 °C0% - 95% (non-condensing) |
| Case | Powdered steel case |
| Measurements | 80 mm x 100 mm x 34 mm (H x W x D)90 mm x 100 mm x 34 mm (H x W x D) (with flaps) |
| Weight | approx. 280g |
Plug for power supply connection:
System terminal 2-pole
AK1550/2-3.5-GREEN
Connector for switching outputs and signal inputs:
System terminal 3-pole
AK1550/3-3.5-GREEN
1.7 Sensor
Two external sensors can be connected to the Expert Sensor Box 7213 / 7214. The following sensors are currently available:

7102
| Humidity/Temperature Sensor 7102 (End-of-Life) | |
| Cable length | ≈ 2m |
| Connector | RJ45 |
| temperature range | -20°C to +80°C, ±0,5°C (maximum) and ±0,3°C (typical) |
| air humidity range (non-condensing)) | 0-100%, ±3% (maximum) and ±2% (typical) |

7101

7104 - 7106
| Product Name | 7101 | 7104-1 | 7105-1 | 7106-1 |
| Calibrated Sensor | - | 7104-2 | 7105-2 | 7106-2 |
| Cable length | ≈ 2m | ≈ 2m | ≈ 2m | ≈ 2m |
| Connector | RJ45 | RJ45 | RJ45 | RJ45 |
| temperature range | -20°C to +80°C at ±2°C (maximum) and ±1°C (typical) | -20°C to +80°C at ±2°C (maximum) and ±1°C (typical) | -20°C to +80°C at ±2°C (maximum) and ±1°C (typical) | -20°C to +80°C at ±2°C (maximum) and ±1°C (typical) |
| air humidity range (non-condensing) | - | - | 0-100%, ±3% (maximum) and ±2% (typical) | 0-100%, ±3% (maximum) and ±2% (typical) |
| air pressure range (full) | - | - | - | ± 1 hPa (typical) at 300 ... 1100 hPa, 0 ... +40 °C |
| air pressure range (ext) | - | - | - | ± 1.7 hPa (typical) at 300 ... 1100 hPa, -20 ... 0 °C |
| Protection | IP68 | - | - | - |

7201, 7202
| Product Name | 7201 | 7202 |
| Cable length | - | - |
| Connector | RJ45 | RJ45 |
| temperature range | -20°C to +80°C at ±2°C (max-imum) and ±1°C (typical) | -20°C to +80°C at ±2°C (max-imum) and ±1°C (typical) |
| air humidity range (non-condensing) | - | 0-100%, ±3% (maximum) and ±2% (typical) |
The sensors are detected automatically after connection. The green LED on the RJ45 sensor connector then lights up permanently. If the sensor value is displayed permanently on the display, the green LED flashes. The sensor values are displayed directly on the "Control Panel" website:
| Id | Name | Temperature°C | Humidity% | Dew Point°C | Dew Diff°C | PressurehPa |
| 1: 7106 | 7106 | 22.5 | 34.2 | 5.9 | 16.6 | 1013.8 |
A click on the link in the "Name" column opens the display of the Min and Max values. The values in a column can be reset using the "Reset" button. The "Reset" button in the name column deletes all stored Min and Max values.
| Id | Name | Temperature°C | Humidity% | Dew Point°C | Dew Diff°C | PressurehPa |
| 1: 7106 | 7106 | 22.5 | 34.4 | 6.1 | 16.5 | 1013.8 |
| 30m min | 0.0 | 34.1 | 5.9 | 16.4 | 125.0 | |
| 30m max | 22.6 | 34.7 | 6.2 | 300.0 | 1013.8 | |
| Reset | Reset | Reset | Reset | Reset | Reset |
Operating
2 Operating
2.1 Operating the device directly
Status-LED
The Status LED shows the different states of the device:
- red: The device is not connected to the Ethernet.
- orange: The device is connected to the Ethernet and waits for data from the DHCP server.
- green: The device is connected to the Ethernet and the TCP/IP settings are allocated. • periodic blinking: The device is in Bootloader mode.
Switching the relay with the button (only ESB 7214)
Press and hold the button for a total of 6 seconds. After the first 3 seconds the status LED flashes in a long ON, short OFF rhythm. Wait another 3 seconds, and the status LED flashes in a twice short, and once long rhythm. At this moment, press the button once again briefly to switch the relay, or if you wait 6 seconds instead, the device returns to its initial state.
2.2 Control Panel
The relay output, the passive signal input and the additional input for the power supply are only available on the Expert Sensorbox 7214. The possibility of power supply via Power-over-Ethernet (PoE) also varies depending on the model.
Access the web interface: http://"IP-address" and log-in.

| Port | Name | null | time since transition | toggle count |
| Input 1 | Input | 0: off / open | 00:30:51 | 0 |
| Id | Name | Temperature °C | Humidity % | Dew Point °C | Dew Diff °C | Pressure hPa |
| 1: 1006 | 7106 | 25.3 | 39.5 | 10.6 | 14.8 | 1019.5 |
| 2: 7106 | 7106 | 25.1 | 40.9 | 10.8 | 14.2 | 1021.3 |
| 3: 7106 | 7106 | 24.9 | 40.9 | 10.7 | 14.2 | 1020.7 |
| Pwr 1 | Supply 12V 1 | On |
| Pwr 2 | Supply 12V 2 | Off |
The web page provides an overview of the switching state, the sensor, as well as the external sensors, provided that they are connected. When the port is clicked, a panel with buttons to control the port appears:

1: Output Port

Off
Reset
Batch
Close
The Port icon is green when the relay is closed, or red in the open state. An additional small clock icon indicates that a timer is active. Timer can be activated by delay, reset or batch mode.

An activated Watchdog is represented by an eye icon. An "X" means, that the address that should be observed, could not be resolved. Two circular arrows show a booting status.

The port can be switched manually with the "On" and "Off" buttons. If the port is turned on, it can be turned off by pressing the "Reset" button, until after a delay it turns itself on again. The delay time is determined by the parameter Reset Duration, which is described in the chapter "Configuration - Output Ports". The "Close" button dissolves the panel again.
Batch mode
The port can be set for a selectable period of time to the state "switch on" or "switch off". After the selected time it is automatically switched to the second preselected state.

Optionally the device can be switched via a Perl script or external tools like wget. More information is available on our support wiki at www.gude.info/wiki.
| Port | Name | null | time since transition | toggle count |
| Input 1 | Input | 0: off / open | 00:35:10 | 0 |
The web page contains a status overview of the passive signal input, the time since the last change, and a counter of the switching cycles. The name and text for a logical state of the input is configured in the chapter Configuration-Input Ports.

The voltage inputs (Pwr1 and Pwr2) show if they are connected to a power supply or Power-over-Ethernet (PoE) is active.
2.3 Maintenance
The actual device generation with IPv6 and SSL allows all maintenance functions in the web interface to be carried out on the Maintenance Page.
Maintenance in the web interface
The following functions are available from the maintenance web page:
- Firmware Update
- Change the SSL certificate
- Load and save the configuration
- Restart the device
- Factory Reset
- Jump into the Bootloader
- Delete the DNS cache
Upload Firmware, Certificate or Configuration
On the Maintenance Page, select the required file with "Browse..." in the sections "Firmware Update", "SSL Certificate Upload" or "Config Import File Upload" and press "Upload". The file is now transferred to the update area of the device and the contents are checked. Only now, pressing the "Apply" button will permanently update the data, or abort with "Cancel".

Only one upload function can be initiated with a reboot, e.g., you cannot transmit firmware and configuration at the same time.

If after a firmware update, the web page is not displayed correctly anymore, this may be related to the interaction of JavaScript with an outdated browser cache. If a Ctrl-F5 does not help, it is recommended that you manually delete the cache in the browser options. Alternatively, you can test start the browser in "private mode".

During a firmware update, old data formats are sometimes converted to new structures. If an older firmware is newly installed, the configuration data and the energy users may be lost! If the device then does not run correctly, please restore the factory settings (e.g., from the Maintenance Page 1).
Actions in Bootloader mode
If the web interface of the device is no longer accessible, the device can be put into Bootloader mode (see chapter Bootloader activation) [1]. The following functions can be executed using the GBL_Conf.exe application:
- Set IPv4 address, net-mask and gateway
- Turn HTTP password on and off
- Turn IP-ACL on and off
- Factory Reset
- Jump into the bootloader (can be switched on and off)
- Restart the device

For devices with relays, entering or exiting the bootloader mode does not change the state of the relays as long as the operating voltage is maintained.
The GBL_Conf.exe program is available free of charge on our website www.gude.info and can also be found on the enclosed CD-ROM.

Interface GBL_Conf
To check the network settings with GBL_Conf.exe, start the program and choose "All Devices" in the "Search" menu. From the list select the appropriate device. The lower part of the left half of the window now shows the current network settings of the device. If the IP address is displayed with the default settings (192.168.0.2), either no DHCP server is present on the network, or there could be no free IP address assigned to it.
- Activate the Bootloader Mode (see Chapter Bootloader Mode) and choose in menu "Search" the item "Bootloader-Mode Devices only"
- Enter the desired settings in the edit window and save them with "Save Config".
- Deactivate the boot loader mode for the changes to take effect. Select again "All Devices" in the "Search" menu of GBL_Conf.exe.
The new network configuration is now displayed.
Factory Reset
The device can be reset to the factory default via the web interface from the Maintenance Page or from the Bootloader mode (see chapter Bootloader activation). All TCP/IP settings are reset in this operation.

If a unit is set to factory defaults, an uploaded certificate or updated firmware will
be preserved.
2.3.1 Maintenance Page
This section provides access to important functions such as Firmware Update or Restart Device. It is advisable to set an HTTP password for this reason.

Firmware Update: Start a firmware update.
SSL Certificate Upload: Saves your own SSL certificate. See chapter "SSL" for the generation of a certificate in the right format.
Config Import File Upload: Loads a new configuration from a text file. To apply the new configuration, a "Restart Device" must be executed after the "Upload".
Config File Export: Saves the current configuration in a text file.

Saving the configuration should only be carried out in an SSL connection, since it contains sensitive password information (even if it is encrypted or hashed).
Restart Device: Restarts the device without changing the status of the relays.

Some functions such as a firmware update or changing of the IP-address and TP settings require a restart of the device. A jump to the boot loader or a restart of device lead by no means to a change of the relay states.
Restore Fab Settings and Restart Device: Performs a restart and resets the device to factory default. 22
Enter Bootloader Mode: Jumps into bootloader mode, where additional settings can be made with GBL_Conf.exe.
Flush DNS Cache: All entries in the DNS cache are discarded and address resolutions are requested again.
2.3.2 Configuration Management
The device configuration can be saved and restored in the maintenance area. 19
Config Import File Upload
Choose File
Upload
Config File Export
The "Config File Export" function can be used to save the current configuration as a text file. The syntax used in the configuration file corresponds to the commands of the Telnet console. If the configuration of a device is to be restored from a text file, load the file with "Upload" and restart the device with "Restart Device".

Saving the configuration should only be carried out in an SSL connection, since it contains sensitive password information (even if it is encrypted or hashed). For these reasons, it is advisable to carefully handle the generated configuration files when having.
Editing the configuration file
It is possible to customize a saved configuration file with a text editor for your own needs. For example, one scenario would be to use a script language to automate the creation of many customized versions of a configuration, then equip a large number of devices with an individualized configuration. Also Upload and restart with CGI commands can be done in scripting languages. With use of the comment sign "#" you can quickly hide single commands or add personal notes.
If you modify a configuration file manually, it is not always clear which limits are allowed for parameters. After uploading and restarting, commands with invalid parameters are ignored. Therefore, the generated configuration includes comments describing the boundaries of the parameters. Where "range:" refers to a numeric value, and "len:" to a text parameter. E.g:
email auth set 0 #range: 0..2
email user set "" #len: 0..100
The command "system fabsettings" from the beginning of a generated configuration file brings the device into the factory state, and then executes the individual commands that modify the configuration state. It may be desirable to make the changes relative to the current configuration, and not out of the factory state. Then the "system fabsettings" should be removed.
No output of default values
The configuration file contains (with exceptions) only values which differ from the default. The command "system fabsettings" (go to the factory state) from the beginning of a generated configuration file should not be removed, otherwise the device can get incompletely configured.
Configuration via Telnet
The configuration files can in principle also be transferred in a Telnet session, but then the settings are changed during operation, and not completely when restarting, as it would have been the case with an upload. It can happen that events are triggered at the same time as the device is configured. One should therefore:
a) disable the function b) completely parametrize c) reactivate the function
An example:
email enabled set 0
email sender set "" #len: 0..100
email recipient set "" #len: 0..100
email server set "" #len: 0..100
email port set 25
email security set 0 #range: 0..2
email auth set 0 #range: 0..2
email user set "" #len: 0..100
email passwd hash set "" #len: 0..100
email enabled set 1 #range: 0..1
2.3.3 Bootloader Ac va on
The configuration of the device from the application "GBL_Conf.exe" is only possible if the device is in Bootloader Mode.
Activation of the Bootloader Mode (1-Button)
1) via push button:
- Press and hold the button for 3 seconds until the Status LED flashes slowly. If a display is available, "Press again to jump to BOOTLOADER" appears. Then briefly press the button again to activate the boot loader, or if you wait 3 seconds instead, the device returns to the initial state.
2) or
- Remove the power supply
- Hold down the "Select" button. If the push button is recessed, use a pin or paper clip
- Connect the operating voltage
3) by Software: (only if "Enable FW to BL" was previously activated in the "GBL_Conf.exe" application)
- Start the "GBL_Conf.exe" program
- Do a network search with the "Search" menu action
- Activate in menu "Program Device" the item "Enter Bootloader"
Whether the device is in Bootloader mode is indicated by the flashing of the status LED, or it is shown in "GBL_Conf.exe" application after a renewed device search (appendix "BOOT-LDR" after the device name). In Bootloader mode the program "GBL_Conf.exe" can disable the password and the IP ACL, perform a firmware update, and restore the factory settings.

For devices with relays, entering or exiting the bootloader mode does not change the state of the relays as long as the operating voltage is maintained.
Abandonment of the Bootloader Mode (1-Button)
1) via push button:
- Hold down the button for 3 seconds until the status LED flashes in a long-on, short-out rhythm. If a display is available, "Press again to jump to FIRMWARE" appears. Then briefly press the button again to activate the boot loader, or if you wait 6 seconds instead, the device returns to the initial state. 2) or
- Remove and connect the power supply without operating a button 3) by Software:
- Start the "GBL_Conf.exe" application
- Do a network search with the "Search" menu action
- In menu "Program Device" activate the item "Enter Firmware"
Factory Reset (1-Button)
If the device is in bootloader mode, it can always be put back to its factory default. All TCP/IP settings are reset in this operation.

If a unit is set to factory defaults, an uploaded certificate or updated firmware will be preserved.
1) via push button:
- Activate the Bootloader Mode of the device
- Press and hold the button for 6 seconds. After the first 3 seconds, the status LED flashes in a long-on, short-out rhythm, and if a display is present, "Press again to jump to FIRMWARE" appears. Wait another 3 seconds, and the status LED flashes in a twice short, and once long rhythm. For devices with a display "Press again to FABSETTINGS" is shown. At this moment briefly press the button again to activate the factory reset, or if you wait 6 seconds instead, the device returns to the initial state.
- During reset to fabsetting, the status LED flashes rapidly, please wait until the LED flashes slowly (approx. 5 seconds).
2) by Software:
- Activate the Bootloader Mode of the device
- Start the GBL_Conf.exe program
- In the "Program Device" menu, activate the "Reset to Fab Settings" item
- The status LED will blink in a fast rhythm; please wait until the LED blinks slowly (about 5 seconds)
Configuration
3 Configuration
TCP/IP configuration by DHCP
After switching on, the device scans the Ethernet for a DHCP server and requests an unused IP address. Check the IP address that has been assigned and adjust if necessary, so that the same IP address is used at each restart. To turn off DHCP, use the software GBL_Conf.exe or use the configuration via the web interface.
To check the network settings with GBL_Conf.exe, start the program and choose "All Devices" in the "Search" menu. From the list, select the appropriate device. The lower part of the left half of the window now shows the current network settings of the device. If the IP address is displayed with the default settings (192.168.0.2), either no DHCP server is present on the network, or there could be no free IP address assigned to it.
3.1 Output Ports
Output Ports
Choose Output Port to configure:
Label:
1: Output Port
Output Port
Initialization status (coldstart):
Initialization delay:
Repower delay:
Reset duration:
Enable watchdog:
○ on ○ off ● remember last state

○ yes ● no
Apply
Choose Output Port to configure: This field is used to select the Output Ports to be configured.
Label: You can assign a name up to 15 characters for each of the Output Ports. Using the name, an identification of the device connected to the port can be facilitated.
Start-up Monitoring
It is important, that if necessary the condition of the Output Ports can be restored after a power failure. Therefore each port can be configured with Initialization status to a specific start-up state. This start-up sequence can be carried out delayed by the parameter Initialization Delay. There is in any case a minimum one-second delay between switching of ports.
Initialization status(coldstart): This is the port state (on, off, remember last state) the port should be set when the device is turned on. The setting "remember last state" saves the last manually set state of the Output Port in the EEPROM.
Initialization delay: Here can be configured how long the port should wait to switch to its defined state after the device is turned on. The delay may last up to 8191 seconds. This corresponds to a period of approx. two hours and 20 minutes. A value of zero means that the initialization is off.
Repower delay: When this feature is enabled (value greater than 0), the Output Port will switch itself on again a specified time after it has been disabled. Unlike the "Reset" button this function applies to all switch actions, including SNMP, or an optional serial interface.
Reset Duration: When the "Reset" button is triggered, the device turns the Output Port off, waits for the time entered here (in seconds) and turns the Output Port on.
3.1.1 Watchdog
The watchdog feature enables you to monitor various remote devices. To do this, either ICMP pings or TCP pings are sent to the device being monitored. If these pings are not answered within a certain time (both the time and the number of attempts can be set), the port is reset. This allows, for example, to automatically restart servers or NAS systems that are not responding. The IP master-slave port mode allows you to switch a port depending on the availability of a remote device.
When a watchdog is activated, it presents various information in the Control Panel. The information is color-coded.
- Green text: The watchdog is active and regularly receives ping replies.
- Orange text: The watchdog is currently enabled and waits for the first ping response.
- Red text: The watchdog is active and no longer receives ping replies from the configured IP address.
After the watchdog has been enabled, the display remains orange until the watchdog receives a ping response for the first time. Only then is the watchdog activated. Even after triggering a watchdog and a subsequent output port reset, the display will remain orange until the device is rebooted and responds again to ping requests. This prevents a premature watchdog reset of the port, for example, when a server needs a long time for a file check.
You can monitor devices on your own network, as well as devices on an external network, for example, the operating status of a router.

Enable watchdog: Enables the watchdog function for this output port.
Watchdog type: Here you can choose between monitoring by ICMP pings or TCP pings.
- ICMP pings: The classic ping (ICMP echo request). It can be used to check the accessibility of network devices (for example, a server).
- TCP pings: With TCP pings, you can check if a TCP port on the target device would accept a TCP connection. Therefore, a non-blocked TCP port should be selected. A good choice would be port 80 for HTTP or port 25 for SMTP.
TCP port: Enter the TCP port to be monitored. When using ICMP pings, this is not needed.
Hostname: The name or IP address of the monitored network device.
Ping interval: Select the frequency (in seconds) at which the ping packet is sent to each network device to check its operating status.
Ping retries: After this number of consecutive unanswered ping requests, the device is considered inactive.
Watchdog mode: When 'Reset port when host down' is enabled, the Output Port is turned off and switched back on after the time set in 'Reset Duration'. In mode 'Switch off once when host down', the Output Port remains disabled.
At the default setting ('Infinite wait for booting host after reset'), the watchdog monitors the connected device. When there is no longer a reply after a set time, the watchdog performs the specified action, usually a reset of the Output Port. Now the watchdog waits until the monitored device reports again on the network. This may take several minutes depending on the boot duration of the device. Only when the device is accessible from the network again is the watchdog re-armed. If the option 'Repeat reset on booting host after x ping timeout' is enabled, this mechanism is bypassed. Now the watchdog is re-activated after N ping intervals (input field 'ping timeouts').
When enabling the IP master-slave mode, the port is switched depending on the availability of a remote device. Depending on the configuration, the port is switched on when the terminal is reachable, or vice versa.
The option 'Repeat reset on booting host after x ping timeout' has the following pitfall: If a server connected to the monitored port requires a long boot process (e.g., it is doing a file system check), the server would probably exceed the tripping time of the watchdog. The server would be switched off and on again, and the file system check would be restarted. This would be repeated endlessly.
Count PING requests as unreplied when Ethernet link is down: If the Ethernet link of the device is not active, watchdog monitoring is not possible and the watchdog function is not activated. If this option is activated, a watchdog is also triggered if the Ethernet link is down.
3.2 Input Ports
Output Ports · Input Ports
Configuration - Input Ports

Apply
Choose Input port to configure: This field is used to select the input port to be configured.
Name: You can assign a name of up to 15 characters for each of the Input Ports. Using the name, identification of the device connected to the port can be facilitated.
Inverted Input: Inverts the assignment of the input signal to a logical HI / LOW state.
Input HI Text Message: Text display in the control panel and messages when a HI signal is present at the input port.
Input LOW Text Message: Text display in the control panel and messages when a LOW signal is present at the input port.
Enable input events: Enables Input Port monitoring.
Message Channels: Enables the generation of messages on different channels.
On input is HI: Switching action when Input Port changes from LOW to HI.
On input is LOW: Switching action when Input Port changes from HI to LOW.
Console push-messages: This option allows the output of sensor values on the console at a configured time interval, or when a certain threshold has been reached.
3.3 Ethernet
3.3.1 IP Address
IP Address · IP ACL · HTTP Server
Hostname
Hostname: ESB-7214
IPv4
Use IPv4 DHCP: yes no
IPv4 Address: 192.168.3.47
IPv4 Netmask: 255.255.240.0
IPv4 Gateway address: 192.168.1.3
IPv4 DNS address: 192.168.1.5
IPv6
Use IPv6 Protocol: yes no
Use IPv6 Router Advertisement: ☑ yes ☑ no
Use DHCP v6: ☐ yes ☑ no
Use manual IPv6 address settings: ○ yes ● no
Hostname: Here you can enter a name with up to 63 characters. This name will be used for registration on the DHCP server.

Special characters and umlauts can cause problems in the network.
IPv4 Address: The IP address of the device.
IPv4 Netmask: The network mask used in the network.
IPv4 Gateway address: The IP address of the gateway.
IPv4 DNS address: The IP address of the DNS server.
Use IPv4 DHCP: Select "yes" if the TCP/IP settings should be obtained directly from the DHCP server: When the function is selected, each time the device powers up it is checked if a DHCP server is available on the network. If not, the last used TCP/IP setting will be used further.
Use IPv6 Protocol: Activates IPv6 usage.
Use IPv6 Router Advertisement: The Router Advertisement communicates with the router to make global IPv6 addresses available.
Use DHCPv6: Requests IPv6 addresses of the configured DNS server from an existing DHCPv6 server.
Use manual IPv6 address settings: Activates the entry of manual IPv6 addresses.
IPv6 status: Displays the IPv6 addresses over which the device can be accessed, and additionally DNS and router addresses.
IPv6 status
Current IPv6 status:
IPv6 Addr:
fe80::219:32ff:fe00:996d
2007:7dd0:ffcl:l:219:32ff:fe00:996d
IPv6 DNS Server:
2007:7dd0:ffcl:1:20c:29ff:feaf:93c
IPv6 Router:
fe80::20c:29ff:feaf:93c

For IP changes a firmware reset is required. This can be done in the Maintenance page. A restart of the device leads by no means to a change of the relay states.
Manual IPv6 Configuration
IPv6 (manual)
IPv6 Addresses:
2007:7dd0:ffc1:0:219:32ff:fe00:996d
/ 64
IPv6 DNS addresses:
2007:7dd0:ffc1:0:20c:29fffeaf:93c
/ 64
IPv6 Gateway address:
fe80::20c:29ff:feaf:93c
The input fields for the manual setting of IPv6 addresses allow you to configure the prefix of four additional IPv6 device addresses, and to set two DNS addresses, and a gateway.
3.3.2 IP ACL
IP Address · IP ACL · HTTP Server
ICMP Ping
Reply ICMP ping requests:

no
IP Access Control List
Enable IP filter:
yes no
- Grant IP access to host/net:
1234::4ef0:eec1:0:219:32ff:fe00:f124

- Grant IP access to host/net:
192.168.1.84

- Grant IP access to host/net:
mypc.locdom

- Grant IP access to host/net:
192.168.1.0/24

- Grant IP access to host/net:
1234:4ef0:eec1:0::/64

Apply
Reply ICMP ping requests: If you enable this feature, the device responds to ICMP pings from the network.
Enable IP filter: Enable or disable the IP filter here. The IP filter represents an access control for incoming IP packets.

Please note that when IP access control is enabled, HTTP and SNMP only work if appropriate servers and clients are registered in the IP access control list.

If you choose a wrong IP ACL setting and lock yourself out, please activate the tloader Mode and use GBL_Conf.exe to deactivate the IP ACL. Alternatively, you can reset the device to factory defaults.
3.3.3 HTTP
IP Address · IP ACL · HTTP Server
HTTP

HTTP Password

HTTP Server option: Selects whether access is possible only with HTTP, HTTPS, or both.
Server port HTTP: Here you can set the port number of the internal HTTP. Possible values are from 1 to 65534 (default: 80). If you do not use the default port, you must append the port number to the address with a colon to address the device from a web browser. For example: "http://192.168.0.2:800"
Server port HTTPS: The port number to connect to the web server via the SSL (TLS) protocol.
Supported TLS versions: Limits the supported TLS versions.
Enable Ajax autorefresh: If this is activated, the information on the status page is automatically updated via HTTP request (AJAX).

For some HTTP configuration changes, a firmware reset is required. This can be done on the Maintenance web page. A restart of the device does not lead to a
change of the relay states.
Enable password protection: Password access protection can be activated. If the admin password is assigned, you can only log in by entering this password to change settings. Users can log in by entering the user password to query status information and initiate switching operations.
Use radius server passwords: Username and password are validated by a Radius Server.
Use locally stored passwords: Username and password are stored locally. In this case, an admin password and a user password must be assigned. The password can have a maximum of 31 characters. The names "admin" and "user" are provided for the user name in the password entry mask of the browser. In factory settings, the password for the admin is set to "admin" or "user" for the user password.

If the password mask is redisplayed, only four "bullets" are shown as a symbolic placeholder, since for security reasons the device never stores the password itself, but only the SHA2-256 hash. If you want to change a password, the complete password must always be re-entered.

If you have forgotten your password, please activate the bootloader mode and then turn off the password prompt in GBL_Conf.exe.
3.4 Protocols
3.4.1 Console
Delay after 3 failed logins:

○ yes ● no
○ yes ● no
○ yes ● no
○ yes ● no
○ yes ● no
Enable SSH:
SSH TCP port:
Activate echo:
Push messages:

yes ○ no
○ yes ● no
Require user login (Telnet/SSH):
Use radius server passwords:
Use locally stored passwords:
Username:
Set new password:
Repeat password:
Upload SSH public rsa key:
yes ○ no
○ yes ● no
yes ○ no


□ Delete public key
Enable Telnet: Enables Telnet console.
Telnet TCP port: Telnet sessions are accepted on this port.
Raw mode: The VT100 editing and the IAC protocol are disabled.
Activate echo: The echo setting if not changed by IAC.
Active negotiation: The IAC negotiation is initiated by the server.
Require user login: Username and password are required.
Delay after 3 failed logins: After 3 wrong entries of username or password, the next login attempt is delayed.
Use radius server passwords: Username and password are validated by a Radius Server.
Use locally stored passwords: Username and password are stored locally.
3.4.2 Syslog
Enable Syslog: Enables the usage of Syslog Messages.
Syslog Server: If you have enabled Syslog Messages, enter the IP address of the server to which the syslog information should be transmitted.
3.4.3 SNMP
SNMP v2 private Community:

private
(16 char. max)
(16 char. max)
SNMP v3
Enable SNMP v3: yes no
SNMP v3 Username:

(32 char, max)
SNMP v3 Authorization Algorithm: SHA2-256
Set new Authorization password:
Repeat Authorization password:


(8 char. min, 32 char. max)
SNMP v3 Privacy Algorithm: AES-128
Set new Privacy password:
Repeat Privacy password:


(8 char. min, 32 char. max)
SNMP Traps
Send SNMP Traps: SNMP v3 Traps
SNMP trap receiver 1 :

SNMP-get: Enables the acceptance of SNMP-GET commands.
SNMP-set: Allows the reception of SNMP-SET commands.
SNMP UDP Port: Sets the UDP port where SNMP messages are received.
Enable SNMP v2: Activates SNMP v2.

Because of security issues, it is advisable to use only SNMP v3, and to disable SNMP v2. Accesses to SNMP v2 are always insecure.
Community public: The community password for SNMP GET requests.
Community private: The community password for SNMP SET requests.
Enable SNMP v3: Activates SNMP v3.
SNMP v3 Username: The SNMP v3 User Name.
SNMP v3 Authorization Algorithm: The selected Authentication Algorithm.
SNMP v3 Privacy Algorithm: SNMP v3 Encryption Algorithm.

If the password mask is redisplayed, only four "bullets" are shown as a symbolic placeholder, since for security reasons the device never stores the password itself, but the key formed using the Authorization Algorithm. If you want to change a password, the complete password must always be re-entered.

The calculation of the password hashes varies with the selected algorithms. If the authentication or privacy algorithms are changed, the passwords must be re-entered in the configuration dialog. "SHA-384" and "SHA-512" are calculated purely in software. If "SHA-512" is set on the configuration page, the time for the key generation may take up to approx. 45 seconds.
Send SNMP traps: Here you can specify whether, and in what format the device should send SNMP traps.
SNMP trap receiver: You can insert here up to eight SNMP trap receivers.
MIB table: The download link to the text file with the MIB table for the device.
More information about SNMP settings is available from our support or can be found on the Internet at www.gude.info/wiki.
3.4.4 Radius
Enable Radius Client:
Use CHAP:




Use Message Authentication:
Default Session Timeout:



Primary Server:
Set new shared secret:
Repeat new shared secret:
Timeout:
Retries:

Use backup server:
Backup Server:
Set new shared secret:
Repeat new shared secret:
Timeout:
Retries:



Enable Radius Client: Enables validation over Radius.
Use CHAP: Use CHAP password encoding.
Use Message Authentication: Adds the "Message Authentication" attribute to the Authentication Request.
Primary Server: Name or IP address of the Primary Radius server.
Shared secret: Radius Shared Secret. For compatibility reasons, only use ASCII characters.
Timeout: How long (in seconds) will be waited for a response from an Authentication Request.
Retries: How often an authentication request is repeated after a timeout.
Use Backup Server: Activates a Radius Backup server.
Backup Server: Name or IP address of the Radius Backup server.
Shared secret: Radius Shared Secret. For compatibility reasons, only use ASCII characters.
Timeout: How long (in seconds) will be waited for a response from an Authentication Request.
Retries: How often an authentication request is repeated after a timeout.
Test Radius Server
Test Username:
Test Password:

Test Radius Server
Test Username: Username input field for Radius test.
Test Password: Password input field for Radius test.
The "Test Radius Server" function allows you to check whether a combination of Username and Password is accepted by the configured Radius Servers.
3.4.5 Modbus TCP
- reply 21s ago, 11ms signal delay
· Tue Feb 19 2019 16:50:33 GMT+0100 (Central European Standard Time)
Backup NTP server:
1.pool.ntp.org
Timezone:
Timezone:
(GMT+01:00) Berlin, Paris, Central
Daylight Saving Time (DST):
yes no
Clock
Current Systemtime (UTC): 15:50:54 19.02.2019 (1550591454)
Current Localtime: 16:50:54 19.02.2019
Browsertime: 16:50:54 19.02.2019
Set clock:
set manually
set to Browsertime
Apply
Enable Time Synchronization: Enables the NTP protocol.
Primary NTP server: IP address of the first NTP server.
Backup NTP server: IP address of the second NTP server. Used when the first NTP server does not respond.
Timezone: The set time zone for the local time.
Daylight Saving Time: If enabled, the local time is converted to Central European Summer Time.
set manually: The user can set a time manually.
set to Browsertime: Sets the time corresponding to web browser.

If Time synchronization is enabled, a manual time will be overwritten at the next synchronization.
3.5.2 Timer
NTP · Timer
Timer - Basic Settings
Enable Timer:
Syslog verbosity level:

Timer - Rules
New Rule: simple Timer
New Rule: advanced Timer
Apply
Enable Timer: Enables or disables all timers globally.
Syslog verbosity level: Sets the verbosity level for timer syslog output.
New Rule simple Timer: Shows a dialog for a simple timer rule.
New Rule advanced Timer: Brings up the dialog for advanced timer settings.
3.5.3 Timer Configuration
There are three possibilities in the timer configuration: Create a simple timer, add an advanced timer, or change an existing configuration.

Timer rules are only executed if the device has a valid time. See Configuration 37

This chapter of the manual applies to all Gude devices. Devices without switchable devices can only have an advanced timer. For an action only the "Action CLI" tab is available there, and not the "Action PortSwitch" tab.
Timer - Basic Settings
Enable Timer:

yes ○ no
Syslog verbosity level:
normal
↓
Timer - Rules
Rule 1: 1: Power Port On
New Rule: simple Timer
New Rule: advanced Timer
Create a simple timer
When "New Rule: simple Timer" is activated, the following dialog is displayed:
Timer Rule
Switch
1: Power Port

On ▼
From

: 30

11 ▼

[Non-Text]

[Non-Text]

On weekdays:

√ Tue

Thu

Sat

Save
Cancel
Here you set which port is to be switched for which period and on which weekdays the rule is active. In this example, the period 9:00 to 17:00 is changed to 9:30 to 11:00 compared to the default input mask. This rule is also not applied to Saturdays and Sundays. The now existing rule says that on every day, except Saturday and Sunday, port 1 is switched on at 9:30 a.m. and switched off after 1.5 hours. A click on "Save" saves this rule.

For example, using only one timer rule to turn on a port at 9:00, and turn it off at
20:00. If at 9:00 the timer is triggered, a batch mode is created to switch off after 11 hours. If the batch mode is running, the port is locked against manual operation on the web page. Also nothing happens on a day at 20:00, if this rule is entered at 10:00, because the rule is triggered at 9:00, and the batch mode then switches off at 20:00. If you don't want this behavior, please use a second rule to explicitly switch off the port at 20:00.
Creating an Advanced Timer
If you create an advanced timer or change an already existing timer, an extended dialog is always shown:

Here you can see the extended representation of the simple timer from the previous example. The action is started every day of every month at 9:30. The weekdays Saturday and Sunday are excluded. An existing rule can be removed with the "Delete" button.

If a rule is deleted, the following rules move up. The numbering of the subsequent rules also changes by one. This also applies to the index in the console commands.

A simple timer is directly "enabled", on a new complex timer the "enable trigger" option must be switched on manually. You can set a probability and a scatter for the timer rules. Here the rule is executed with 100% probability. A jitter of 0 means that the action takes place exactly at the programmed time. As an action mode, a port can be switched, alternatively a console command (CLI Cmd) can be executed.
On the "Action PortSwitch" tab, the switching function can be set in more detail. Port 1 is switched on and switched off again after 1.5 hours.

"Action PortSwitch" is only available for devices with switchable ports.
Extending a Rule
For demonstration purposes, the simple timer from the previous example is extended here:

The action will now not only start at 9:30, but also at 17:30. There are more changes: The timer is only active between October and December, also the action does not take place on the first day of a month.
Since all fields in the mask are always taken into account, it is not possible to define the times 9:30 and 17:10 in a single timer rule. You need a second rule for this. If you set hours 9 and 17, as well as minutes 10 and 30, then the four times 9:10, 9:30, 17:10 and 17:30 would be programmed.
In order to change a field in this input mask without changing the state of the other fields, the Ctrl key must be pressed during the mouse click.

With this rule, the time period in the "Options" tab is limited to the period between December 5, 2018 and July 4, 2019. In this example, the timer rule is executed with a random trigger probability of 90%.

In addition to port 1, port 5 is activated here and deactivated again after 90 minutes.

A popup at the mouse pointer shows the port number of the corresponding field.
Console Commands

Instead of switching a port, you can run one or more console commands. These commands are entered in the "Action CLI" tab. The "Action CLI" tab can only be selected if the option "Perform CLI Cmd" is activated under "Options".

Example: Switching a Port on a Date
If you want to switch on a timer on a certain date at a time and switch it off at a later time, you cannot do it directly with a simple timer. Therefore it can be useful to first create the timer as a simple timer and then adjust it in the extended dialog.

Switches port 3 on every day at 9:25, and off again at 17:30. Save the simple rule.

Then you call up the created timer and enter in the "Options" tab the date on which the switching process should take place.
Example: Rolling Shutter

You can use the jitter e.g. for a roller shutter control. In the classic example of a roller shutter control, in order to confuse potential burglars, you do not always want to raise and lower the blinds at the same times. A jitter of 1800 seconds means that the action is performed randomly between 30 minutes before and 30 minutes after the programmed time. The probability (Random Trigger Probability) of the execution is here 100%.

Further examples can be found at www.gude.info/wiki/timer
3.6 Sensors

Sensor: Selects a type of sensor to configure it. The first digit "1" indicates the number of the sensor port (only important for devices with more than one sensor port). This is followed by the sensor name, and the changeable sensor name.
Sensor Name: Changeable name for this sensor. Temperature and humidity can have different names, even if they are from the same sensor.
Select Sensor Field: Selects a data channel from a sensor.
Enable ... Messages: Enables the generation of sensor messages.
Maximum/Minimum value: Here you can choose whether, and at what Maximum/Minimum temperature or humidity measurements limits the alerts are send via SNMP traps, syslog or E-Mail.
Hysteresis: This describes the margin of when an event is generated after the measured value has crossed the chosen limit.
Message channels: Enables the generation of messages on different channels.
Console push-messages: This option allows the output of sensor values on the console at a configured time interval, or when a certain threshold has been reached.
Min/Max measurement period: Selects the time range for the sensor min/max values on the overview web page.
Hysteresis Example:
A Hysteresis value prevents that too much messages are generated, when a sensor value is jittering around a sensor limit. The following example shows the behavior for a temperature sensor and a hysteresis value of "1". An upper limit of "50 °C" is set.
Example:
49.9 °C - is below the upper limit
50.0 °C - a message is generated for reaching the upper limit
50.1 °C - is above the upper limit
...
49.1 °C - is below the upper limit, but in the hysteresis range
49.0 °C - is below the upper limit, but in the hysteresis range
48.9 °C - a message is generated for underrunning the upper limit inclusive hysteresis range
...
3.6.1 Port Switching

This chapter describes in general the configuration of switching actions, using an example for a device with 2 ports. Models with only one port must be abstracted.
Depending on the measured current and the measured sensor values, switching actions can be triggered. During operation, the actions configured for crossing the limits are executed. For example, when a value moves from the range "above max value" inside the range "below max value", the action defined for "below max value" is performed. In the case of device start, configuration or plug-in of the sensor, the actions corresponding to the range in which the current temperature is located are switched.
Example with "Maximum value" of 65 °C, "Minimum value" of 25 °C and hysteresis of 3 °C. The dotted line shows the hysteresis.

- When above Max value:
- When below Max value:
- When above Min value:
- When below Min value:
Switch port 1: Output Port ▼ to Off ▼
Switch port 1: Output Port ▼ to On ▼
Switch port 2: Output Port ▼ to On ▼
Switch port 2: Output Port ▼ to Off ▼
Actions during configuration, device start or plugging in the sensor (for given example):
| actual temperature during configuration | actions |
| 70 °C | Port 1 Off (above max) + Port 2 On (above min) |
| 45 °C | Port 1 On (below max) + Port 2 On (above min) |
| 20 °C | Port 1 On (below max) + Port 2 Off (below min) |
Action matrix during operation when limit values are exceeded (for given example):
| to "above max" | to "below max" | to "above min" | to "below min" | |
| from "above max" | - | P1 On | P1 On | P1 On + P2 Off |
| from "below max" | P1 Off | - | - | P2 Off |
| from "above min" | P1 Off | - | - | P2 Off |
| from "below min" | P1 Off + P2 On | P2 On | P2 On | - |

Only the switching operations for which actions have been defined, are triggered. If no "On" or "Off" action is defined for a port, the port can never reach this state by exceeding sensor values. Unless it is the initial state.
3.7 E-Mail
Enable E-Mail:
yes no
Sender address:
sender@provider.net
Recipient address:
info@gude.info
SMTP server:
smtp.provider.de
SMTP server port:
25 (Default: 587)
SMTP Connection Security:
STARTTLS
Authentication
SMTP Authentication (password):
LOGIN
Username:
Set new password:

Repeat password:
Enable E-Mail: Activates the E-Mail dispatch of messages.
Sender address: The E-Mail address of the sender.
Recipient address: The E-Mail address of the recipient. Additional E-Mail addresses, separated by comma, can be specified. The input limit is 100 characters.
SMTP Server: The SMTP IP-address of the E-Mail server. Either as FQDN, e.g: "mail.gmx.net", or as IP-address, e.g: "213.165.64.20". If required, attach a designated port, e.g: "mail.gmx.net:25".
SMTP server port: The port address of the E-Mail server. In the normal case this should be the same as the default, that is determined by the setting SMTP Connection Security.
SMTP Connection Security: Transmission via SSL or no encryption.
SMTP Authentication (password): Authentication method of the E-Mail Server.
Username: User name that is registered with the SMTP E-Mail server.
Set new password: Enter the password for the login to the E-Mail server.
Repeat password: Enter the password again to confirm it.

If the password mask is redisplayed, only four "bullets" are shown as a symbolic placeholder, since for security reasons the password is never shown itself. If you want to change a password, the complete password must always be re-entered.
E-Mail Logs: Logging of E-Mail system messages.
Specifications
4 Specifications
4.1 IP ACL
IP Access Control List
The IP Access Control List (ACL IP) is a filter for incoming IP packets. If the filter is active, only the hosts and subnets whose IP addresses are registered in the list can contact via HTTP or SNMP, and make changes. For incoming connections from unauthorized PCs, the device is not completely transparent. Due to technical restraints, a TCP/IP connection will be accepted at first, but then rejected directly.
Examples:
| Entry in the IP ACL | Meaning |
| 192.168.0.123 | the PC with IP Address "192.168.0.123" can access the device |
| 192.168.0.1/24 | all devices of subnet "192.168.0.1/24" can access the device |
| 1234:4ef0:eec1:0::/64 | all devices of subnet "1234:4ef0:eec1:0::/64" can access the device |
If you choose a wrong IP ACL setting and lock yourself out, please activate the Bootloader Mode and use GBL_Conf.exe to deactivate the IP ACL. Alternatively, you can reset the device to factory default.
4.2 IPv6
IPv6 Addresses
IPv6 addresses are 128 bits long and thus four times as long as IPv4 addresses. The first 64 bits form a so-called prefix, the last 64 bits designate a unique interface identifier. The prefix is composed of a routing prefix and a subnet ID. An IPv6 network interface can be reached under several IP addresses. Usually this is the case under a global address and the link-local address.
Address Notation
IPv6 addresses are noted in 8 hexadecimal blocks of 16 bits, while IPv4 normally is noted in decimal. The separator is a colon, not a period.
E.g.: 1234:4ef0:0:0:0019:32ff:fe00:0124
Leading zeros may be omitted within a block. The previous example can be rewritten as:
1234:4ef0:0:0:19:32ff:fe00:124
One may omit one or more successive blocks, if they consist of zeros. This may be done only once within an IPv6 address!
1234:4ef0::19:32ff:fe00:124
One may use the usual decimal notation of IPv4 for the last 4 bytes:
1234:4ef0::19:32ff:254.0.1.36
4.3 Radius
The passwords for HTTP, telnet, and serial console (depending on the model) can be stored locally and / or authenticated via RADIUS. The RADIUS configuration supports a primary server and a backup server. If the primary server does not respond, the RADIUS request is sent to the backup server. If the local password and RADIUS are enabled at the same time, the system first checks locally, and then in the event of a failure the RADIUS servers are contacted.
RADIUS attributes
The following RADIUS attributes are evaluated by the client:
Session-Timeout: This attribute specifies (in seconds) how long an accepted RADIUS request is valid. After this time has elapsed, the RADIUS server must be prompted again. If this attribute is not returned, the default timeout entry from the configuration is used instead.
Filter-Id: If the value "admin" is set for this attribute, then admin rights are assigned for the login, otherwise only user access.
Service-Type: This is an alternative to Filter-Id. A service type of "6" or "7" means admin rights for the HTTP login, otherwise only limited user access.
HTTP Login
The HTTP login takes place via Basic Authentication. This means that it is the responsibility of the web server, how long the login credentials are temporarily stored there. The RADIUS parameter "Session-Timeout" therefore does not determine when the user has to login again, but at what intervals the RADIUS servers are asked again.
4.4 Automated Access
The device can be accessed automatically via four different interfaces, which offer different possibilities to access the configuration data and status information. Only http and the console (telnet and serial) provide full access to the device.
List of different access options (if supported by the model):
| Interface | Scope of Access |
| HTTP | read / write all configuration dataread / write all status information |
| Console [58] | read / write all configuration dataread / write all status information |
| SNMP [57] | read / write status of Power Ports (relays or eFuses)read / write names of Power Ports (relays or eFuses)read / write status of Port start configurationread / write status Buzzerread / write configuration of power sourcesread / write fan configurationread measurement values of external sensorsread measurement values of all energy sensorsread NTP time and statusresetting the energy metersread the status of Overvoltage Protection |
| Modbus TCP [74] | read / write status of Power Ports (relays or eFuses)read status of Inputsread / write configuration of power sourcesread / write fan configurationread measurement values of external sensorsread measurement values of all energy sensorsread the status of Overvoltage Protection |
The device can be controlled via HTTP interface with CGI commands and returns the internal configuration and status in JSON format. The structure of the CGI commands and the JSON data is explained in more detail in our Wiki article:
http://wiki.gude.info/EPC_HTTP_Interface
4.5 SNMP
SNMP can be used for status information via UDP (port 161). Supported SNMP commands are:
- GET
- GETNEXT
- GETBULK
- SET
To query via SNMP you need a Network Management System, such as HP OpenView, OpenNMS, Nagios etc., or the simple command line tools of NET-SNMP software. The device supports SNMP protocols v1, v2c and v3. If traps are enabled in the configuration, the device messages are sent as notifications (traps). SNMP Informs are not supported. SNMP Requests are answered with the same version with which they were sent. The version of the sent traps can be set in the configuration.
MIB Tables
The values that can be requested or changed by the device, the so-called "Managed Objects", are described in Management Information Bases (MIBs). These substructures are subordinate to so-called "OID" (Object Identifiers). An OID digit signifies the location of a value inside a MIB structure. Alternatively, each OID can be referred to with its symbol name (subtree name). The device's MIB table can be displayed as a text file by clicking on the link "MIB table" on the SNMP configuration page in the browser.
SNMP v1 and v2c
SNMP v1 and v2c authenticates the network requests by so-called communities. The SNMP request has to send along the so-called community public for queries (read access) and the community private for status changes (write access). The SNMP communities are read and write passwords. In SNMP v1 and v2 the communities are transmitted unencrypted on the network and can be easily intercepted with IP sniffers within this collision domain. To enforce limited access we recommend the use of DMZ or IP-ACL.
SNMP v3
Because the device has no multiuser management, only one user (default name "standard") is detected in SNMP v3. From the User-based Security Model (USM) MIB variables, there is a support of "usmStats ..." counter. The "usmUser ..." variables will be added with the enhancement of additional users in later firmware versions. The system has only one context. The system accepts the context "normal" or an empty context.
Authentication
The algorithms "HMAC-MD5-96" and "HMAC-SHA-96" are available for authentication. In addition, the "HMAC-SHA-2" variants (RFC7630) "SHA-256", "SHA-384" and "SHA-512" are implemented.
"SHA-384" and "SHA512" are calculated purely in software. If "SHA-384" or "SHA-512" is set on the configuration page, the time for the key generation may take once up to approx. 45 seconds.
Encryption
The methods "DES", "3DES", "AES-128", "AES-192" and "AES-256" are supported in combination with "HMAC-MD5-96" and "HMAC-SHA-96." For the "HMAC-SHA-2" protocols, there is currently neither RFC nor draft that will allow for cooperation with an encryption.
While in the settings "AES-192" and "AES256" the key calculation is based on "draft-blumenthalphoto-aes-usm-04", the methods "AES 192-3DESKey" and "AES 256-3DESKey" utilize a key generation, which is also used in the "3DES" configuration ("draft-reeder-snmpv3-usm-3desede-00"). If one is not an SNMP expert, it is recommended to try in each case the settings with and without "...- 3DESKey".
Passwords
The passwords for authentication and encryption are stored only as computed hashes for security reasons. Thus it is, if at all, very difficult to infer the initial password. However, the hash calculation changes with the set algorithms. If the authentication or privacy algorithms are changed, the passwords must be re-entered in the configuration dialog.
Security
The following aspects should be considered:
- If encryption or authentication is used, then SNMP v1 and v2c should be turned off. Otherwise the device could be accessed with it.
- If only authentication is used, then the new "HMAC-SHA-2" methods are superior to the MD5 or SHA-1 hashing algorithms. Since only SHA-256 is accelerated in hardware, and SHA-384 and SHA-512 are calculated purely in software, one should normally select SHA-256. From a cryptographic point of view, the security of SHA-256 is sufficient for today's usage.
- For SHA-1, there are a little less attack scenarios than MD5. If in doubt, SHA-1 is preferable.
- Encryption "DES" is considered very unsafe, use only in an emergency for reasons of compatibility!
- For cryptologists it's a debatable point whether "HMAC-MD5-96" and "HMAC-SHA-96" can muster enough entropy for key lengths of "AES-192" or "AES-256".
- From the foregoing considerations, we would recommend at present "HMAC-
SHA-96" with "AES-128" as authentication and encryption method.
Change in Trap Design
In older MIB tables, a separate trap was defined for each combination of an event and a port number. This results in longer lists of trap definitions for the devices. For example, from epc8221SwitchEvtPort1 to epc8221SwitchEvtPort12. Since new firmware versions can generate many more different events, this behavior quickly produces several hundred trap definitions. To limit this overabundance of trap definitions, the trap design has been changed to create only one specific trap for each event type. The port or sensor number is now available in the trap as an index OID within the variable bindings.
In order to recognize this change directly, the "Notification" area in the MIB table has been moved from sysObjectID.0 to sysObjectID.3. This way, unidentified events are generated until the new MIB table is imported. For compatibility reasons, SNMP v1 traps are created in the same way as before.
NET-SNMP
NET-SNMP provides a very widespread collection of SNMP command-line tools (snmpget, snmpset, snmpwalk etc.) NET-SNMP is among others available for Linux and Windows. After installing NET-SNMP you should create the device-specific MIB of the device in NET-SMP share directory, e.g. after
c:\usr\share\snmp\mibs
or
/usr/share/snmp/mibs
So later you can use the 'subtree names' instead of OIDs:
Name: snmpwalk -v2c -mALL -c public 192.168.1.232 gudeads
OID: snmpwalk -v2c -mALL -c public 192.168.1.232 1.3.6.1.4.1.28507
NET-SNMP Examples
Query Power Port 1 switching state:
snmpget -v2c -mALL -c public 192.168.1.232 epc822XPortState.1
Switch on Power Port 1:
snmpset -v2c -mALL -c private 192.168.1.232 epc822XPortState.1 integer 1
4.5.1 Device MIB 7213
Below is a table of all device-specific OIDs which can be accessed via SNMP. In the numerical representation of the OID the prefix "1.3.6.1.4.1.28507" (Gude Enterprise OID) was omitted at each entry in the table to preserve space. The example for a complete OID would be "1.3.6.1.4.1.28507.60.1.1.1.1". A distinction is made in SNMP OIDs between tables and scalars. OID scalars have the extension ".0" and only specify a value. In SNMP tables the "x" is replaced by an index (1 or greater) to address a value from the table.
| Name | OID | Type | Acc. |
| Description | |||
| esb7213TrapCtrl | .66.1.1.1.1.00 = off 1 = Ver. 1 2 = Ver. 2c 3 = Ver. 3 | Integer32 | RW |
| esb7213TrapIPIndex | .66.1.1.1.2.1.1.xA unique value, greater than zero, for each receiver slot. | Integer32 | RO |
| esb7213TrapAddr | .66.1.1.1.2.1.2.xDNS name or IP address specifying one Trap receiver slot. A port can optionally be specified: 'name:port' An empty string disables this slot. | OCTETS | RW |
| esb7213POE | .66.1.5.10.0signals POE availability | Integer32 | RO |
| epc7213NTPTimeValid | .66.1.5.15.1.0Show if valid Time is received | INTEGER | RO |
| epc7213NTPUnixTime | .66.1.5.15.2.0show received NTP time as unixtime (secs since 1 January 1970) | Unsigned32 | RO |
| epc7213NTPLastValidTimestamp | .66.1.5.15.3.0show seconds since last valid NTP timestamp received | Unsigned32 | RO |
| esb7213SensorIndex | .66.1.6.1.1.1.xNone | Integer32 | RO |
| esb7213TempSensor | .66.1.6.1.1.2.xactual temperature | Integer32 | RO |
| esb7213HygroSensor | .66.1.6.1.1.3.xactual humidity | Integer32 | RO |
| esb7213InputSensor | .66.1.6.1.1.4.xlogical state of input sensor | INTEGER | RO |
| esb7213AirPressure | .66.1.6.1.1.5.xactual air pressure | Integer32 | RO |
| esb7213DewPoint | .66.1.6.1.1.6.xdew point for actual temperature and humidity | Integer32 | RO |
| esb7213DewPointDiff | .66.1.6.1.1.7.xdifference between dew point and actual temperature (Temp - DewPoint) | Integer32 | RO |
| esb7213ExtSensorName | .66.1.6.1.1.32.xA textual string containing name of a external Sensor | OCTETS | RW |
Notes
- Legacy - The command has been replaced by a newer version
- Command can be entered on any level
- The output may show 2 lines - the 1st line shows the actual state, the 2nd line the status after reboot
- The output may show several lines
- N/A
- Please see the External Sensor Field Table for the right sensor index
External Sensor Type Table "{7x01=0|7x02=1|7x03=2}"
| Index | Description | Products |
| 0 | Temperature | 7001, 7101, 7201 |
| 1 | Temperature, Humidity | 7002, 7102, 7202 |
| 2 | Temperature, Humidity, Air Pressure | 7003, 7103, 7203 |
External Sensor Field Table "{sen_field}"
| Index | Description | Unit |
| 0 | Temperature | °C |
| 1 | Humidity | % |
| 2 | Digital Input | bool |
| 3 | Air Pressure | hPa |
| 4 | Dew Point | °C |
| 5 | Dew Point Temperature Difference | °C |
4.5.2 Device MIB 7214
Below is a table of all device-specific OIDs which can be accessed via SNMP. In the numerical representation of the OID the prefix "1.3.6.1.4.1.28507" (Gude Enterprise OID) was omitted at each entry in the table to preserve space. The example for a complete OID would be "1.3.6.1.4.1.28507.61.1.1.1". A distinction is made in SNMP OIDs between tables and scalars. OID scalars have the extension ".0" and only specify a value. In SNMP tables the "x" is replaced by an index (1 or greater) to address a value from the table.
| Name | OID | Type | Acc. |
| Description | |||
| esb7214TrapCtrl | .67.1.1.1.1.00 = off 1 = Ver. 1 2 = Ver. 2c 3 = Ver. 3 | Integer32 | RW |
| esb7214TrapIPIndex | .67.1.1.1.2.1.1.xA unique value, greater than zero, for each receiver slot. | Integer32 | RO |
| esb7214TrapAddr | .67.1.1.1.2.1.2.xDNS name or IP address specifying one Trap receiver slot. A port can optionally be specified: 'name:port' An empty string disables this slot. | OCTETS | RW |
| esb7214portNumber | .67.1.3.1.1.0The number of Relay Ports | Integer32 | RO |
| esb7214PortIndex | .67.1.3.1.2.1.1.xA unique value, greater than zero, for each Relay Port. | Integer32 | RO |
| esb7214PortName | .67.1.3.1.2.1.2.xA textual string containing name of a Relay Port. | OCTETS | RW |
| esb7214PortState | .67.1.3.1.2.1.3.xcurrent state of a Relay Port | INTEGER | RW |
| esb7214PortSwitchCount | .67.1.3.1.2.1.4.xThe total number of switch actions occurred on a Relay Port. Does not count switch commands which will not switch the relay state, so just real relay switches are displayed here. | Integer32 | RO |
| esb7214PortStartupMode | .67.1.3.1.2.1.5.xset Mode of startup sequence (off, on , remember last state) | INTEGER | RW |
| esb7214PortStartupDelay | .67.1.3.1.2.1.6.xDelay in sec for startup action | Integer32 | RW |
| esb7214PortRepowerTime | .67.1.3.1.2.1.7.xDelay in sec for repower port after switching off | Integer32 | RW |
| esb7214PortResetDuration | .67.1.3.1.2.1.8.xDelay in sec for turning Port on again after Reset action | Integer32 | RW |
| esb7214ActiveInputs | .67.1.5.6.1.0Number of supported Input Channels. | Unsigned32 | RO |
| esb7214InputIndex | .67.1.5.6.2.1.1.xNone | Integer32 | RO |
| esb7214Input | .67.1.5.6.2.1.2.xInput state of device | INTEGER | RO |
| esb7214InputName | .67.1.5.6.2.1.32.xA textual string containing name of the Input | OCTETS | RW |
| esb7214POE | .67.1.5.10.0signals POE availability | Integer32 | RO |
| esb7214PwrSupplyIndex | .67.1.5.13.1.1.xIndex of Power Supply entries | Integer32 | RO |
| esb7214PwrSupplyStatus | .67.1.5.13.1.2.xshows status of the Power Supply 1 = fst, 2 = snd etc. | INTEGER | RO |
| epc7214NTPTimeValid | .67.1.5.15.1.0Show if valid Time is received | INTEGER | RO |
| epc7214NTPUnixTime | .67.1.5.15.2.0show received NTP time as unixtime (secs since 1 January 1970) | Unsigned32 | RO |
| epc7214NTPLastValidTimestamp | .67.1.5.15.3.0show seconds since last valid NTP timestamp received | Unsigned32 | RO |
| esb7214SensorIndex | .67.1.6.1.1.1.xNone | Integer32 | RO |
| esb7214TempSensor | .67.1.6.1.1.2.xactual temperature | Integer32 | RO |
| esb7214HygroSensor | .67.1.6.1.1.3.xactual humidity | Integer32 | RO |
| esb7214InputSensor | .67.1.6.1.1.4.xlogical state of input sensor | INTEGER | RO |
| esb7214AirPressure | .67.1.6.1.1.5.xactual air pressure | Integer32 | RO |
| esb7214DewPoint | .67.1.6.1.1.6.xdew point for actual temperature and humidity | Integer32 | RO |
| esb7214DewPointDiff | .67.1.6.1.1.7.x | Integer32 | RO |
| difference between dew point and actual temperature (Temp - DewPoint) | |||
| esb7214ExtSensorName | .67.1.6.1.1.32.x | OCTETS | RW |
| A textual string containing name of a external Sensor | |||
Notes
- Legacy - The command has been replaced by a newer version
- Command can be entered on any level
- The output may show 2 lines - the 1st line shows the actual state, the 2nd line the status after reboot
- The output may show several lines
- N/A
- Please see the External Sensor Field Table for the right sensor index
External Sensor Type Table "{7x01=0|7x02=1|7x03=2}"
| Index | Description | Products |
| 0 | Temperature | 7001, 7101, 7201 |
| 1 | Temperature, Humidity | 7002, 7102, 7202 |
| 2 | Temperature, Humidity, Air Pressure | 7003, 7103, 7203 |
External Sensor Field Table "{sen_field}"
| Index | Description | Unit |
| 0 | Temperature | °C |
| 1 | Humidity | % |
| 2 | Digital Input | bool |
| 3 | Air Pressure | hPa |
| 4 | Dew Point | °C |
| 5 | Dew Point Temperature Difference | °C |
4.6 SSL
TLS Standard
The device is compatible with TLS v1.1 to TLS v1.3 standards, but due to lack of security, SSL v3.0, TLS 1.0, and RC4, MD5, SHA1, and DES encryption are disabled. All ciphers use Diffie-Hellman key exchange (Perfect Forward Secrecy).
TLS 1.3 performance
The interaction of TLS 1.3 and unsecure certificates and a web browser with Chromium Engine (Google Chrome or MS Edge) can lead to performance losses, and thus longer loading times. In this constellation, the Chromium Engine does not correctly support the SSL Session Cache (Session Tickets) and the math unit of the embedded CPU may be overwhelmed with continuous RSA operations. There are some possible workarounds:
- Use secure certificates (official certificate authority or marked as secure in the OS) • or use of the Firefox browser • or use of ECC 256 (no RSA) certificates • or configure to "TLS v1.2 only
Creating your own Certificates
The SSL stack is supplied with a specially newly generated self-signed certificate. There is no function to generate the local certificate anew at the touch of a button, since the required random numbers in an embedded device are usually not independent enough. However, you can create new certificates and import them to the device. The server accepts RSA (2048/4096) and ECC (Elliptic Curve Cryptography) certificates.
Usually OpenSSL is used to create an SSL certificate. For Windows for example, there is the light version of Shining Light Productions. There you open a command prompt, change to the directory "C:\OpenSSL-Win32\bin" and set these environment variables:
set openssl_conf=C:\OpenSSL-Win32\bin\openssl.cfg
set RANDFILE=C:\OpenSSL-Win32\bin\.rnd
Here are some examples for the generation with OpenSSL:
Creation of a self-signed RSA 2048-bit certificate
openssl genrsa -out server.key 2048
openssl req -new -x509 -days 365 -key server.key -out server.crt
RSA 2048-bit certificate with Sign Request:
openssl genrsa -out server.key 2048
openssl req -new -key server.key -out server.csr
openssl req -x509 -days 365 -key server.key -in server.csr -out server.crt
The server keys should be created with "openssl genrsa". The Gude device processes keys in the traditional PKCS#1 format. This can be recognized by the fact that the generated key file starts with "-----BEGIN RSA PRIVATE KEY-----". If the file starts with "-----BEGIN PRIVATE KEY-----", the file is in PKCS#8 format and the key is not recognized. If you have only a key in PKCS#8 format, you can convert it to PKCS#1 with openssl: "openssl rsa -in pkcs8.key -out pkcs1.key".
ECC Certificate with Sign Request:
openssl eparam -genkey -name prime256v1 -out server.key
openssl req -new -key server.key -out server.csr
openssl req -x509 -days 365 -key server.key -in server.csr -out server.crt
If you have created your key and certificate, both files are concatenated to one file:
Linux:
cat server.crt server.key > server.pem
Windows:
copy server.crt + server.key server.pem
The created server.pem can only be uploaded in the maintenance section of the device.
If several certificates (Intermediate CRTs) should also be uploaded to the device, one should make sure that firstly the server certificate and secondly the Intermediates are assembled, e.g:
cat server.crt IM1.crt IM2.crt server.key > server.pem

An uploaded certificate will be preserved when a device is put back to factory defaults. 22
Performance Considerations
If RSA 4096 certificates are used, the first access to the web server can take 8-10 seconds, because the math unit of the embedded CPU is highly demanded. After that, the parameters are in the SSL session cache, so all other requests are just as fast as with other certificate lengths. For a quick response even on the first access, we recommend RSA 2048-bit certificates that offer adequate security, too.
4.7 Console
For the configuration and control of the device, there is a set of commands with parameters that can be entered through a console. The console is available via Telnet, or for devices with RS232 port through using a serial terminal. It is not necessary to use Telnet, in Raw Mode a simple TCP/IP connection is sufficient to send commands. The communication can also be performed automated (e.g. via scripting languages). The console features are configured through the web interface. 32
Command Set
There are several command levels. The following commands are usable from each level:
| back | go back one level |
| help | all commands of the actual level |
| help all | show all commands |
| logout | logout (only when login required) |
| quit | quit console |
The "help" command returns all the commands of the current level. If "help" is called from the top level, e.g. the line "http [subtopics]" appears. This means that there is another level for "http". With the command "http help" all commands below "http" are shown. Alternatively, with entering "http" you can select the http level, and "help" shows all the commands on the selected level. The command "back" again selects the top level. It is possible to use "help" at any position: "http passwd help" provides all commands that have the prefix "http passwd".
You will find a complete list of all possible device commands in the chapter "Cmd Overview".
Parameter
If parameters are expected for the command, the parameter may be passed as numeric or constant. If e.g. you get the following line as help:
http server set {http_both=0|https_only=1|http_only=2}
the following instruction pairs are equivalent:
http server set https_only http server set 1
or
http server set https_both http server set 0
Numerical parameters can be entered with different bases. Here is an example of the decimal value 11:
| Base | Input |
| decimal (10) | 11 |
| hexadecimal (16) | 0xb |
| octal (8) | 013 |
| binary (2) | 0b1011 |
Bit Field Parameter
Some parameters can take several values at the same time. In the following example, all values between 0 and 5 can be set. In the help, this can be recognized by the fact that the values are not separated by the "|" character, but by commas.
" {EVT_SYSLOG=0,EVT_SNMP=1,EVT_EMAIL=2,EVT_SMS=3,EVT_GSMEMAIL=4,EVT_BEEPER=5}"
To set EVT_SYSLOG and EVT_EMAIL in a command, you can use the following syntax:
>extsensor 1 2 0 events type set "EVT_SYSLOG,EVT_EMAIL" OK.
or numeric
>extsensor 1 2 0 events type set "0,2" OK.
Additionally you can set all values with "ALLSET" or encode any bit pattern as hexadecimal with a syntax like "#7f1a".
Return Values
If a command is unknown or a parameter is incorrect, the output "ERR." is given at the beginning of the line, followed by a description of the fault. Successful instructions without special return value will be acknowledged by "OK.". All other return values are output within a single line. There are two exceptions:
- Some configuration changes that affect TCP/IP and UDP need a restart to be applied. These parameters are output on two lines. In the first line the current value is shown, on the second row the value after a restart. In the "Cmd Overview" table this is marked with "Note 2".
- Other configurations (such as the assigned IPv6 addresses) have several values that can change dynamically. This is marked with "Note 3" in the "Cmd Overview" table.
Numerical Returns
For parameters that support constants, these constants are output as return values. To
better deal with scripting languages, it may be easier to work only with numerical returns. The command "vt100 numeric set ON" enables that only numerical values appear.
Comments
If you use a tool to send an entire file of commands via Telnet, it is helpful if you can place comments in there. Beginning with the comment character "#", the remaining contents of a line is ignored.
Telnet
If the configuration "Raw Mode" is turned off, it is tried to negotiate the Telnet configuration between client and server using IAC commands. If this fails, the editing functions are not active, and the "Activate echo" option determines whether the characters sent to the Telnet server will be returned. Normally the client begins with the IAC negotiation. If this is not the case with the client, the device configuration "Active negotiation" should be turned on.
Raw Mode
If you want to use the console only automated, it may be advantageous to set the configuration "Raw mode" to "yes" and "Activate echo" to "no". Then there is no interfering interaction with the editor functions and there is no need to filter the sent characters to process the return values.

If in the console "Raw mode" is activated but not in the used Telnet client, the IAC commands sent at the beginning can appear as interfering characters in the command (partially invisible).
Editing
The following edit functions are available when the terminal supports VT100, and Raw Mode is deactivated. Entered characters are inserted at the cursor position.
| Keys | Function |
| Left, Right | moves cursor left or right |
| Pos1, End | moves cursor to the beginning or end of line |
| Del | deletes character under the cursor |
| Backspace | deletes character left of cursor |
| Up, Down | shows input lines history |
| Tab, Ctrl-Tab | completes the word at cursor |
| Ctrl-C | clears the line |
Sensor Examples
a) External Sensors
>extsensor all show
E=1,L="7106",0="21.3°C",1="35.1%",3="1013hPa",4="5.2°C",5="16.0°C"
E=2,L="7102",0="21.2°C",1="35.4%",4="5.3°C",5="15.9°C"
The command lists one connected external sensor per line, and the individual measured values are separated by commas after the label name. The digit before the equal sign corresponds to the Index field in the External Sensor Table.
Values are separated by commas after the label name. The digit before the equal sign corresponds to the Index field in the External Sensor Table.
Displays temperature of the sensor at Port 1
b) Line Sensors
This command outputs all line sensor values in one line. A list of all fields (according to the energy sensor table) is transferred as parameter. In this example these are the fields Absolute Active Energy (0), Power Active (1), Voltage (2), Current (3) and Reset Time (12).
>linesensor all "0,1,2,3,12" show
L=1,L="Power Port",0="13000Wh",1="0W",2="225V",3="0A",12="998218s"
L=2,L="Power Port",0="13000Wh",1="0W",2="223V",3="0A",12="996199s"
This command outputs all line sensor values in one line. A list of all fields (according to the energy sensor table) is transferred as a parameter. In this example, these are the fields Absolute Active Energy (0), Power Active (1), Voltage (2), Current (3), and Reset Time (12).
>linesensor 1 "0,1,2,3,12" show
>linesensor 1 1 show
These variants give the sensor values of the field list or of a sensor at Line-In 1.
For devices with Overvoltage Protection, the "linesensor all" command also outputs the state of the protection ("OVP=x"). A "1" means ok, a "0" a failure of the protection.
This command outputs all port sensor values in one line. A list of all fields (according to the energy sensor table) is passed as parameter. In this example these are the fields Absolute Active Energy (0), Power Active (1), Voltage (2), Current (3) and Reset Time (12).
>portsensor all "0,1,2,3,12" show
P=1,L="Power Port",0="13000Wh",1="0W",2="225V",3="0A",12="998218s"
P=2,L="Power Port",0="13000Wh",1="0W",2="225V",3="0A",12="996199s"
...
P=12,L="Power Port",0="13000Wh",1="0W",2="225V",3="0A",12="998218s"
This command outputs all port sensor values in one line. A list of all fields (according to the energy sensor table) is passed as a parameter. In this example, these are the fields Absolute Active Energy (0), Power Active (1), Voltage (2), Current (3), and Reset Time (12).
>portsensor 2 "0,1,2,3,12" show
>portsensor 2 1 show
These variants give the sensor values of the field list or a sensor to at Outlet Port 2.
d) Displaying Port Relays
>port all state 1 show
P1=ON, P2=OFF, P3=ON, P4=OFF, P5=OFF, P6=OFF, P7=OFF, P8=ON
The command "port all state {MODE0=0|MODE1=1|MODE2=2} show" returns the switching state of all relays in 3 possible formats.
e) Switching Port Relays
#port all state set "1,2,12" 1 OK.
The command syntax "port all state set "{port_list}" {OFF=0|ON=1}" sets a list of ports to ON=1 or OFF=0.
4.7.1 SSH
The device supports SSH-2 connections with public key or username and password authentication. Users and passwords can be stored locally or retrieved via a radius server. If you want to use SSH in a terminal, Activate echo should be enabled.
Public Keys
RSA and ECDSA public keys are accepted.


Generated keys can be copied directly from e.g. putty gen,

and inserted into the Configuration - Console input field. Public keys are accepted in SSH2 or OpenSSH format.
4.7.2 Push Messages
On the console channels (Telnet, SSH or serial console) push messages can be activated, which output sensor values in time intervals (every n seconds) or from an adjustable change of the sensor value threshold on this channel. The generated message always starts with a "#" and ends with a CR/LF. This also applies to sensor limit value messages if "Console" is selected as message channel in Sensors - Configuration.
If you open a Telnet or SSH connection, you can use "console telnet pushmsgs set 1" or "console ssh pushmsgs set 1" to temporarily activate the push messages. From now
on push messages will be sent asynchronously on this channel. The asynchronicity of the messages can cause problems on a connection if you send commands yourself. Then there are the possibilities:
- Filter all incoming characters between "#" and CR/LF
- or open a second channel (Telnet, SSH, serial) and activate Push Messages
4.7.3 Console Cmd 7213
| Command | Description | Note |
| logout | go to login prompt when enabled | 2 |
| quit | quits telnet session - nothing in serial console | 2 |
| back | back one cmd level | 2 |
| help | show all cmds from this level | 2 |
| help all | show all cmds | 2 |
| clock | enters cmd group "clock" | |
| clock ntp enabled set {OFF=0|ON=1} | enables ntp | |
| clock ntp enabled show | shows if ntp enabled | |
| clock timezone set {minutes} | sets timezone | |
| clock timezone show | shows timezone | |
| clock dst enabled set {OFF=0|ON=1} | enables dst | |
| clock dst enabled show | shows if dst is enabled | |
| clock manual set "{hh:mm:ss yyyy-mm-dd}" | sets time and date manually | |
| clock show | shows actual time and date | |
| clock ntp server {PRIMARY=0|BACKUP=1} set "{dns_name}" | sets ntp server name | |
| clock ntp server {PRIMARY=0|BACKUP=1} show | shows ntp server name | |
| console | enters cmd group "console" | |
| console version | shows unique console version number | |
| console telnet enabled set {OFF=0|ON=1} | enables telnet on/off | |
| console telnet enabled show | shows if telnet enabled | |
| console telnet port set {ip_port} | sets telnet port | |
| console telnet port show | shows telnet port | |
| console telnet raw set {OFF=0|ON=1} | sets raw mode (disables editing) on/off | |
| console telnet raw show | shows if raw mode enabled | |
| console telnet echo set {OFF=0|ON=1} | enables echo on/off | |
| console telnet echo show | shows if echo enabled | |
| console telnet activeneg set {OFF=0|ON=1} | enables telnet active negotiation (IAC) on/off | |
| console telnet activeneg show | shows if active negotiation enabled | |
| console telnet login set {OFF=0|ON=1} | enables login on/off | |
| console telnet login show | shows if login enabled | |
| console telnet login local set {OFF=0|ON=1} | enables local login on/off | |
| console telnet login local show | shows if local login enabled | |
| console telnet login radius set {OFF=0|ON=1} | enables login for RADIUS on/off | |
| console telnet login radius show | shows if RADIUS login enabled | |
| console telnet login delay set {OFF=0|ON=1} | enables delay (after 3 login fails) on/off | |
| console telnet login delay show | shows if login delay enabled | |
| console telnet pushmsgs config set {OFF=0|ON=1} | enables persistent push msgs | |
| console telnet pushmsgs config show | shows if persistent push msgs are enabled | |
| console telnet pushmsgs set {OFF=0|ON=1} | enables temporary push msgs | |
| console telnet pushmsgs show | shows if temporary push msgs are enabled | |
| console telnet user set "{username}" | sets login user name | |
| console telnet user show | shows login user name | |
| console telnet passwd set "{passwd}" | sets login password | |
| console telnet passwd hash set "{passwd}" | sets login hashed password | |
| console ssh enabled set {OFF=0|ON=1} | enables SSH | |
| console ssh enabled show | shows if SSH enabled | |
| console ssh port set {ip_port} | sets SSH port | |
| console ssh port show | shows SSH port | |
| console ssh echo set {OFF=0|ON=1} | enables echo on/off | |
| console ssh echo show | shows if echo enabled | |
| console ssh pushmsgs config set {OFF=0|ON=1} | enables persistent push msgs | |
| console ssh pushmsgs config show | shows if persistent push msgs are enabled | |
| console ssh pushmsgs set {OFF=0|ON=1} | enables temporary push msgs | |
| console ssh pushmsgs show | shows if temporary push msgs are enabled | |
| console ssh public hash set "{passwd}" | sets hash of SSH public key | |
| console ssh public hash show | shows hash of SSH public key |
| enters cmd group "email" | |
| email enabled set {OFF=0|ON=1} | enables email on/off |
| email enabled show | shows if email is enabled |
| email sender set "{email_addr}" | sets email sender address |
| email sender show | shows email sender address |
| email recipient set "{email_addr}" | sets email recipient address |
| email recipient show | shows email recipient address |
| email server set "{dns_name}" | sets email SMTP server address |
| email server show | shows email SMTP server address |
| email port set {ip_port} | sets email SMTP port |
| email port show | shows email SMTP port |
| email security set {NONE=0|STARTTLS=1|SSL=2} | sets SMTP connection security |
| email security show | shows SMTP connection security |
| email auth set {NONE=0|PLAIN=1|LOGIN=2} | sets email authentication |
| email auth show | show email authentication |
| email user set "{username}" | sets SMTP username |
| email user show | shows SMTP username |
| email passwd set "{passwd}" | sets SMTP password |
| email passwd hash set "{passwd}" | sets encrypted SMTP password |
| email testmail | send test email |
| ethernet | enters cmd group "ethernet" |
| ethernet mac show | shows MAC address |
| ethernet link show | shows ethernet link state |
| ethernet phyprefer set {10MBIT_HD=0|10MBIT_FD=1|100MBIT_HD=2|100MBIT_FD=3} | sets preferred speed for PHY Auto Negotiation |
| ethernet phyprefer show | shows preferred speed for PHY Auto Negotiation |
| ethernet poe show | shows if Power-over-Ethernet is activated |
| extsensor | enters cmd group "extsensor" |
| extsensor all show | shows all values from connected external sensors |
| extsensor all show | shows all plugged sensors and fields |
| extsensor {port_num} {sen_field} value show | shows sensor value 6 |
| extsensor {port_num} {sen_type} label set "{name}" | sets sensor name to label 6 |
| extsensor {port_num} {sen_type} label show | shows label of sensor 6 |
| extsensor {port_num} type show | shows type of sensor |
| extsensor {port_num} {sen_type} {sen_field} events set {off=0|on=1} | enables sensor events on/off 6 |
| extsensor {port_num} {sen_type} {sen_field} events show | shows if sensor events are enabled 6 |
| extsensor {port_num} {sen_type} {sen_field} events type set "{EVT_SYSLOG=0,EVT_SNMP=1,EVT_EMAIL=2,EVT_SMS=3,EVT_GSMEMAIL=4,EVT_BEEPER=5,EVT_DISPLAY=6,EVT_CONSOLE=7"} | enables different event types 6 |
| extsensor {port_num} {sen_type} {sen_field} events type show | shows what event types are enabled 6 |
| extsensor {port_num} {sen_type} {sen_field} maxval set {num} | sets maximum value for sensor 6 |
| extsensor {port_num} {sen_type} {sen_field} maxval show | shows maximum value for sensor 6 |
| extsensor {port_num} {sen_type} {sen_field} min-val set {num} | sets minimum value for sensor 6 |
| extsensor {port_num} {sen_type} {sen_field} min-val show | shows minimum value for sensor 6 |
| extsensor {port_num} {sen_type} {sen_field} hyst set {num} | sets hysteresse value for sensor 6 |
| extsensor {port_num} {sen_type} {sen_field} hyst show | shows hysteresse value for sensor 6 |
| extsensor {port_num} {sen_type} {sen_field} pub-lish mode set {NONE=0|INTERVAL=1|DIFFERENCE=2} | sets publish mode |
| extsensor {port_num} {sen_type} {sen_field} pub-lish mode show | shows publish mode |
| extsensor {port_num} {sen_type} {sen_field} pub-lish trigger set {float} | sets trigger value for publish |
| extsensor {port_num} {sen_type} {sen_field} pub-lish trigger show | shows trigger value for publish |
| extsensor period set {24H=0|12H=1|2H=2|1H=3|30MIN=4} | sets sensor Min/Max measurement period |
| extsensor period show | shows sensor Min/Max measurement period |
| http | enters cmd group "http" |
| http server set {HTTP_BOTH=0|HTTPS_ONLY=1|HTTP_ONLY=2} | sets connection types the webserver accepts |
| http server show | shows webserver accepting connection types |
| http port set {ip_port} | sets http port |
| http port show | shows http port |
| http portssl set {ip_port} | sets https port |
| http portssl show | shows https port |
| http tls mode set {TLS12=0|TLS13_12=1| TLS13=2|TLS13_12_11=3} | restricts TLS mode |
| http tls mode show | shows TLS mode restriction |
| http ajax enabled set {OFF=0|ON=1} | enables ajax autorefresh on/off |
| http ajax enabled show | shows if ajax autorefresh enabled |
| http passwd enabled set {OFF=0|ON=1} | enables http password on/off |
| http passwd enabled show | shows if http password enabled |
| http passwd local set {OFF=0|ON=1} | enables local login on/off |
| http passwd local show | shows if local login enabled |
| http passwd radius set {OFF=0|ON=1} | enables login for RADIUS on/off |
| http passwd radius show | shows if RADIUS login enabled |
| http passwd user set "{passwd}" | sets http user password |
| http passwd admin set "{passwd}" | sets http admin password |
| http passwd hash user set "{passwd}" | sets hashed http user password |
| http passwd hash admin set "{passwd}" | sets hashed http admin password |
| ip4 | enters cmd group "ip4" |
| ip4 hostname set "{name}" | sets device hostname |
| ip4 hostname show | shows device hostname 3 |
| ip4 address set "{ip_address}" | sets IPv4 address |
| ip4 address show | shows IPv4 address 3 |
| ip4 netmask set "{ip_address}" | sets IPv4 netmask |
| ip4 netmask show | shows IPv4 netmask 3 |
| ip4 gateway set "{ip_address}" | sets IPv4 gateway address |
| ip4 gateway show | shows IPv4 gateway address 3 |
| ip4 dns set "{ip_address}" | sets IPv4 DNS server address |
| ip4 dns show | shows IPv4 DNS server address 3 |
| ip4 dhcp enabled set {OFF=0|ON=1} | enables IPv4 DHCP on/off |
| ip4 dhcp enabled show | shows IPv4 DHCP state 3 |
| ip6 | enters cmd group "ip6" |
| ip6 enabled set {OFF=0|ON=1} | enables IPv6 on/off |
| ip6 enabled show | shows if IPv6 is enabled 3 |
| ip6 routadv enabled set {OFF=0|ON=1} | enables IPv6 router advertisement |
| ip6 routadv enabled show | shows IPv6 router advertisement state 3 |
| ip6 dhcp enabled set {OFF=0|ON=1} | enables IPv6 DHCP on/off |
| ip6 dhcp enabled show | shows if IPv6 DHCP is enabled 3 |
| ip6 address show | show all IPv6 addresses 4 |
| ip6 gateway show | show all IPv6 gateways 4 |
| ip6 dns show | show all IPv6 DNS server 4 |
| ip6 manual enabled set {OFF=0|ON=1} | enables manual IPv6 addresses |
| ip6 manual enabled show | shows if manual IPv6 addresses are enabled 3 |
| ip6 manual address {1..4} set "{ip_address}" | sets manual IPv6 address |
| ip6 manual address {1..4} show | shows manual IPv6 address 3 |
| ip6 manual gateway set "{ip_address}" | sets manual IPv6 gateway address |
| ip6 manual gateway show | shows manual IPv6 gateway address 3 |
| ip6 manual dns {1..2} set "{ip_address}" | sets manual IPv6 DNS server address |
| ip6 manual dns {1..2} show | shows manual IPv6 DNS server address 3 |
| ipacl | enters cmd group "ipacl" |
| ipacl ping enabled set {OFF=0|ON=1} | enables ICMP ping on/off |
| ipacl ping enabled show | shows if ICMP ping enabled |
| ipacl enabled set {OFF=0|ON=1} | enable IP filter on/off |
| ipacl enabled show | shows if IP filter enabled |
| ipacl filter {ipacl_num} set "{dns_name}" | sets IP filter {ipacl_num} |
| ipacl filter {ipacl_num} show | shows IP filter {ipacl_num} |
| modbus | enters cmd group "modbus" |
| modbus enabled set | |
| modbus enabled show | shows if Modbus is enabled |
| modbus port set | |
| modbus port show | shows Modbus TCP port |
| radius | enters cmd group "radius" |
| radius {PRIMARY=0|SECONDARY=1} enabled set | |
| radius {PRIMARY=0|SECONDARY=1} enabled show | enables radius client |
| radius {PRIMARY=0|SECONDARY=1} server set | |
| radius {PRIMARY=0|SECONDARY=1} server show | show if radius client enabled |
| radius {PRIMARY=0|SECONDARY=1} server show | sets radius server address |
| radius {PRIMARY=0|SECONDARY=1} server show | shows radius server address |
| radius {PRIMARY=0|SECONDARY=1} password set "{passwd}" | sets radius server shared secret |
| radius {PRIMARY=0|SECONDARY=1} password hash set "{passwd}" | sets radius server decrypted shared secret |
| radius {PRIMARY=0|SECONDARY=1} auth timeout set {num_secs} | sets server request timeout |
| radius {PRIMARY=0|SECONDARY=1} auth timeout show | shows server request timeout |
| radius {PRIMARY=0|SECONDARY=1} retries set {num} | sets server number of retries |
| radius {PRIMARY=0|SECONDARY=1} retries show | shows server number of retries |
| radius chap enabled set <off=0/on=1> | enables CHAP |
| radius chap enabled show | shows if CHAP is enabled |
| radius message auth set <off=0/on=1> | enables request message authentication |
| radius message auth show | shows if request message authentication is enabled |
| radius default timeout set {num_secs} | sets default session timeout (when not returned as Session-Timout Attribute) |
| radius default timeout show | shows default session timeout |
| snmp | enters cmd group "snmp" |
| snmp port set {ip_port} | sets SNMP UDP port |
| snmp port show | shows SNMP UDP port |
| snmp snmpget enabled set {OFF=0|ON=1} | enables SNMP GET cmds on/off |
| snmp snmpget enabled show | show if SNMP GET cmds are enabled |
| snmp snmpset enabled set {OFF=0|ON=1} | enables SNMP SET cmds on/off |
| snmp snmpset enabled show | show if SNMP SET cmds are enabled |
| snmp snmpv2 enabled set {OFF=0|ON=1} | enables SNMP v2 on/off |
| snmp snmpv2 enabled show | show if SNMP v2 is enabled |
| snmp snmpv2 public set "{text}" | enables SNMP v3 on/off |
| snmp snmpv2 public show | show if SNMP v3 isenabled |
| snmp snmpv2 private set "{text}" | sets SNMP v2 public cummnity |
| snmp snmpv2 private show | shows SNMP v2 public community |
| snmp snmpv3 enabled set {OFF=0|ON=1} | sets SNMP v2 private community |
| snmp snmpv3 enabled show | shows SNMP v2 private community |
| snmp snmpv3 username set "{text}" | sets SNMP v3 username |
| snmp snmpv3 username show | shows SNMP v3 username |
| snmp snmpv3 authalg set {NONE=0|MD5=1|SHA1=2|SHA256=3|SHA384=4|SHA512=5} | sets SNMP v3 authentication |
| snmp snmpv3 authalg show | show SNMP v3 authentication algorithm |
| snmp snmpv3 privalg set {NONE=0|DES=1|3DES=2|AES128=3|AES192=4|AES256=5|AES192*=6|AES256*=7} | sets SNMP v3 privacy algorithm |
| snmp snmpv3 privalg show | show SNMP v3 privacy algorithm |
| snmp snmpv3 authpasswd set "{passwd}" | sets SNMP v3 authentication password |
| snmp snmpv3 privpasswd set "{passwd}" | sets SNMP v3 privacy password |
| snmp snmpv3 authpasswd hash set "{passwd}" | sets SNMP v3 authentication hashed password |
| snmp snmpv3 privpasswd hash set "{passwd}" | sets SNMP v3 privacy hashed password |
| snmp trap type set {NONE=0|V1=1|V2=2|V3=3} | sets type of SNMP traps |
| snmp trap type show | show SNMP trap type |
| snmp trap receiver {trap_num} set "{dns_name}" | sets address and port of SNMP trap receiver {trap_num} |
| snmp trap receiver {trap_num} show | show address and port of SNMP trap receiver {trap_num} |
| syslog | enters cmd group "syslog" |
| syslog enabled set {OFF=0|ON=1} | enables syslog msgs on/off |
| syslog enabled show | show if syslog enabled |
| syslog server set "{dns_name}" | sets address of syslog server |
| syslog server show | shows address of syslog server |
| system | enters cmd group "system" |
| system restart | restarts device |
| system fabsettings | restore fab settings and restart device |
| system bootloader | enters bootloader mode |
| system flushdns | flush DNS cache |
| system uptime | number of seconds the device is running |
| system name show | shows device name |
| system version show | shows actual firmware version |
| timer | enters cmd group "timer" |
| timer enabled set {OFF=0|ON=1} | enables timer functions |
| timer enabled show | shows if timer a enabled |
| timer syslog facility set {0..23} | sets facility level for timer syslog |
| timer syslog facility show | shows facility level for timer syslog |
| timer syslog verbose set {0..7} | sets verbose level for timer syslog |
| timer syslog verbose show | shows verbose level for timer syslog |
| timer {rule_num} enabled set {OFF=0|ON=1} | enables rule |
| timer {rule_num} enabled show | shows if rule is enabled |
| timer {rule_num} name set "{name}" | sets name of rule |
| timer {rule_num} name show | shows name of rule |
| timer {rule_num} {FROM=0|UNTIL=1} set "{yyyy-mm-dd}" | sets date range of rule |
| timer {rule_num} {FROM=0|UNTIL=1} show | shows date range of rule |
| timer {rule_num} trigger jitter set {0..65535} | sets jitter for rule |
| timer {rule_num} trigger jitter show | show jitter of rule |
| timer {rule_num} trigger random set {0..100} | sets probability for rule |
| timer {rule_num} trigger random show | shows rule probability |
| timer {rule_num} trigger {HOUR=0|MIN=1|SEC=2|DAY=3|MON=4|DOW=5} set "{time_date_list}" | sets time date list |
| timer {rule_num} trigger {HOUR=0|MIN=1|SEC=2|DAY=3|MON=4|DOW=5} show | shows time date list |
| timer {rule_num} action mode set {SWITCH=1|CLI=2} | sets switch or cli cmd |
| timer {rule_num} action mode show | shows if switch or cli cmd |
| timer {rule_num} action {SWITCH1=0|SWITCH2=1} {OFF=0|ON=1} set "{port_list}" | sets port list for switch cmd |
| timer {rule_num} action {SWITCH1=0|SWITCH2=1} {OFF=0|ON=1} show | shows port list for switch cmd |
| timer {rule_num} action delay set {0..65535} | delay between cmds |
| timer {rule_num} action delay show | shows delay between cmds |
| timer {rule_num} action console set "{cmd}" | sets cmd string |
| timer {rule_num} action console show | shows cmd string |
| timer {rule_num} action hash set "{data}" | sets action binary form |
| timer {rule_num} action hash show | shows action binary form |
| timer {rule_num} delete | delete one timer |
| timer delete all | delete all timer |
| vt100 | enters cmd group "vt100" |
| vt100 echo set {OFF=0|ON=1} | sets console echo state |
| vt100 echo show | shows console echo state |
| vt100 numeric set {OFF=0|ON=1} | sets numeric mode |
| vt100 numeric show | shows numeric mode state |
| vt100 reset | resets terminal |
Notes
- Legacy - The command has been replaced by a newer version
- Command can be entered on any level
- The output may show 2 lines - the 1st line shows the actual state, the 2nd line the status after reboot
- The output may show several lines
- N/A
- Please see the External Type and External Sensor Field Tables for the correct sensor index
External Sensor Type Table "{sen_type}"
Constants "{7x01=0|7x04=0|7x02=1|7x05=1|7x06=2}"
| Index | Description | Products |
| 0 | Temperature | 7001, 7101, 7201 |
| 0 | Temperature | 7004, 7104, 7204 |
| 1 | Temperature, Humidity | 7002, 7102, 7202 |
| 1 | Temperature, Humidity | 7005, 7105, 7205 |
| 2 | Temperature, Humidity, Air Pressure | 7006, 7106, 7206 |
External Sensor Field Table "{sen_field}"
| Index | Description | Unit |
| 0 | Temperature | °C |
| 1 | Humidity | % |
| 2 | Digital Input | bool |
| 3 | Air Pressure | hPa |
| 4 | Dew Point | °C |
| 5 | Dew Point Temperature Difference | °C |
4.7.4 Console Cmd 7214
| Command | Description | Note |
| logout | go to login prompt when enabled | 2 |
| quit | quits telnet session - nothing in serial console | 2 |
| back | back one cmd level | 2 |
| help | show all cmds from this level | 2 |
| help all | show all cmds | 2 |
| clock | enters cmd group "clock" | |
| clock ntp enabled set {OFF=0|ON=1} | enables ntp | |
| clock ntp enabled show | shows if ntp enabled | |
| clock timezone set {minutes} | sets timezone | |
| clock timezone show | shows timezone | |
| clock dst enabled set {OFF=0|ON=1} | enables dst | |
| clock dst enabled show | shows if dst is enabled | |
| clock manual set "{hh:mm:ss yyyy-mm-dd}" | sets time and date manually | |
| clock show | shows actual time and date | |
| clock ntp server {PRIMARY=0|BACKUP=1} set "{dns_name}" | sets ntp server name | |
| clock ntp server {PRIMARY=0|BACKUP=1} show | shows ntp server name | |
| console | enters cmd group "console" | |
| console version | shows unique console version number | |
| console telnet enabled set {OFF=0|ON=1} | enables telnet on/off | |
| console telnet enabled show | shows if telnet enabled | |
| console telnet port set {ip_port} | sets telnet port | |
| console telnet port show | shows telnet port | |
| console telnet raw set {OFF=0|ON=1} | sets raw mode (disables editing) on/off | |
| console telnet raw show | shows if raw mode enabled | |
| console telnet echo set {OFF=0|ON=1} | enables echo on/off | |
| console telnet echo show | shows if echo enabled | |
| console telnet activeneg set {OFF=0|ON=1} | enables telnet active negotiation (IAC) on/off | |
| console telnet activeneg show | shows if active negotiation enabled | |
| console telnet login set {OFF=0|ON=1} | enables login on/off | |
| console telnet login show | shows if login enabled | |
| console telnet login local set {OFF=0|ON=1} | enables local login on/off | |
| console telnet login local show | shows if local login enabled | |
| console telnet login radius set {OFF=0|ON=1} | enables login for RADIUS on/off | |
| console telnet login radius show | shows if RADIUS login enabled | |
| console telnet login delay set {OFF=0|ON=1} | enables delay (after 3 login fails) on/off | |
| console telnet login delay show | shows if login delay enabled | |
| console telnet pushmsgs config set {OFF=0|ON=1} | enables persistent push msgs | |
| console telnet pushmsgs config show | shows if persistent push msgs are enabled | |
| console telnet pushmsgs set {OFF=0|ON=1} | enables temporary push msgs | |
| console telnet pushmsgs show | shows if temporary push msgs are enabled | |
| console telnet user set "{username}" | sets login user name | |
| console telnet user show | shows login user name | |
| console telnet passwd set "{passwd}" | sets login password | |
| console telnet passwd hash set "{passwd}" | sets login hashed password | |
| console ssh enabled set {OFF=0|ON=1} | enables SSH | |
| console ssh enabled show | shows if SSH enabled | |
| console ssh port set {ip_port} | sets SSH port | |
| console ssh port show | shows SSH port | |
| console ssh echo set {OFF=0|ON=1} | enables echo on/off | |
| console ssh echo show | shows if echo enabled | |
| console ssh pushmsgs config set {OFF=0|ON=1} | enables persistent push msgs | |
| console ssh pushmsgs config show | shows if persistent push msgs are enabled | |
| console ssh pushmsgs set {OFF=0|ON=1} | enables temporary push msgs | |
| console ssh pushmsgs show | shows if temporary push msgs are enabled | |
| console ssh public hash set "{passwd}" | sets hash of SSH public key | |
| console ssh public hash show | shows hash of SSH public key | |
| enters cmd group "email" | ||
| email enabled set {OFF=0|ON=1} | enables email on/off | |
| email enabled show | shows if email is enabled | |
| email sender set "{email_addr}" | sets email sender address | |
| email sender show | shows email sender address | |
| email recipient set "{email_addr}" | sets email recipient address | |
| email recipient show | shows email recipient address | |
| email server set "{dns_name}" | sets email SMTP server address | |
| email server show | shows email SMTP server address | |
| email port set {ip_port} | sets email SMTP port | |
| email port show | shows email SMTP port | |
| email security set {NONE=0|STARTTLS=1|SSL=2} | sets SMTP connection security | |
| email security show | shows SMTP connection security | |
| email auth set {NONE=0|PLAIN=1|LOGIN=2} | sets email authentication | |
| email auth show | show email authentication | |
| email user set "{username}" | sets SMTP username | |
| email user show | shows SMTP username | |
| email passwd set "{passwd}" | sets SMTP password | |
| email passwd hash set "{passwd}" | sets encrypted SMTP password | |
| email testmail | send test email | |
| ethernet | enters cmd group "ethernet" | |
| ethernet mac show | shows MAC address | |
| ethernet link show | shows ethernet link state | |
| ethernet phyprefer set {10MBIT_HD=0|10MBIT_FD=1|100MBIT_HD=2|100MBIT_FD=3} | sets preferred speed for PHY Auto Negotiation | |
| ethernet phyprefer show | shows preferred speed for PHY Auto Negotiation | |
| ethernet poe show | shows if Power-over-Ethernet is activated | |
| extsensor | enters cmd group "extsensor" | |
| extsensor all show | shows all values from connected external sensors | |
| extsensor all show | shows all plugged sensors and fields | |
| extsensor {port_num} {sen_field} value show | shows sensor value | 6 |
| extsensor {port_num} {sen_type} label set "{name}" | sets sensor name to label | 6 |
| extsensor {port_num} {sen_type} label show | shows label of sensor | 6 |
| extsensor {port_num} type show | shows type of sensor | |
| extsensor {port_num} {sen_type} {sen_field} events set {off=0|on=1} | enables sensor events on/off | 6 |
| extsensor {port_num} {sen_type} {sen_field} events show | shows if sensor events are enabled | 6 |
| extsensor {port_num} {sen_type} {sen_field} events type set "{EVT_SYSLOG=0,EVT_SNMP=1,EVT_EMAIL=2,EVT_SMS=3,EVT_GSMEMAIL=4,EVT_BEEPER=5,EVT_DISPLAY=6,EVT_CONSOLE=7"} | enables different event types | 6 |
| extsensor {port_num} {sen_type} {sen_field} events type show | shows what event types are enabled | 6 |
| extsensor {port_num} {sen_type} {sen_field} maxval set {num} | sets maximum value for sensor | 6 |
| extsensor {port_num} {sen_type} {sen_field} maxval show | shows maximum value for sensor | 6 |
| extsensor {port_num} {sen_type} {sen_field} min-val set {num} | sets minimum value for sensor | 6 |
| extsensor {port_num} {sen_type} {sen_field} min-val show | shows minimum value for sensor | 6 |
| extsensor {port_num} {sen_type} {sen_field} hyst set {num} | sets hysteresse value for sensor | 6 |
| extsensor {port_num} {sen_type} {sen_field} hyst show | shows hysteresse value for sensor | 6 |
| extsensor {port_num} {sen_type} {sen_field} pub-lish mode set {NONE=0|INTERVAL=1|DIFFERENCE=2} | sets publish mode | |
| extsensor {port_num} {sen_type} {sen_field} pub-lish mode show | shows publish mode | |
| extsensor {port_num} {sen_type} {sen_field} pub-lish trigger set {float} | sets trigger value for publish | |
| extsensor {port_num} {sen_type} {sen_field} pub-lish trigger show | shows trigger value for publish | |
| extsensor {port_num} {sen_type} {sen_field} {BELOWMIN=0|ABOVEMIN=1|ABOVEMAX=2|BELOWMAX=3} port set {port_num} | sets Port for Power Port Switching actions | 6 |
| extsensor {port_num} {sen_type} {sen_field} {BELOWMIN=0|ABOVEMIN=1|ABOVEMAX=2|BELOWMAX=3} port show | shows Port for Power Port Switching actions | 6 |
| extsensor {port_num} {sen_type} {sen_field} {BELOWMIN=0|ABOVEMIN=1|ABOVEMAX=2| | sets Port state for Power Port Switching actions | 6 |
BELOWMAX=3} state set {OFF=0|ON=1|
DISABLED=2}
extsensor {port_num} {sen_type} {sen_field}
{BELOWMIN=0|ABOVEMIN=1|ABOVEMAX=2|
BELOWMAX=3} state show
extsensor period set {24H=0|12H=1|2H=2|1H=3|
30MIN=4}
extsensor period show
shows Port state for Power Port Switching actions
sets sensor Min/Max measurement period
shows sensor Min/Max measurement period
http
http server set {HTTP_BOTH=0|HTTPS_ONLY=1}
HTTP ONLY=2}
http server show
http port set {ip_port}
http port show
http portssl set {ip_port}
http portssl show
http tls mode set {TLS12=0|TLS13_12=1}
http passwd user set "{passwd}"
http passwd admin set "{passwd}"
http passwd hash user set "{passwd}"
http passwd hash admin set "{passwd}"
enters cmd group "http"
sets connection types the webserver accepts
shows webserver accepting connection types
sets http port
shows http port
sets https port
shows https port
restricts TLS mode
shows TLS mode restriction
enables ajax autorefresh on/off
shows if ajax autorefresh enabled
enables http password on/off
shows if http password enabled
enables local login on/off
shows if local login enabled
enables login for RADIUS on/off
shows if RADIUS login enabled
sets http user password
sets http admin password
sets hashed http user password
sets hashed http admin password
input
input {port_num} state show
input all state {MODE0=0|MODE1=1|MODE2=2}
show
input {port_num} name set "{name}"
input {port_num} name show
input {port_num} invert enabled set {off=0|on=1}
input {port_num} invert enabled show
input {port_num} label {LOW=0|HIGH=1} set
"{name}
input {port_num} label {LOW=0|HIGH=1} show
input {port_num} events set {off=0|on=1}
input {port_num} events show
input {port_num} events type set
"{EVT_SYSLOG=0, EVT_SNMP=1, EVT_EMAIL=2}
, EVT_SMS=3, EVT_GSMEMAIL=4, EVT_BEEPER
=5, EVT_DISPLAY=6, EVT_CONSOLE=7}
input {port_num} events type show
input {port_num} {LOW=0|HIGH=1} port set
{port_num}
input {port_num} {LOW=0|HIGH=1} port show
input {port_num} {LOW=0|HIGH=1} state set
{OFF=0|ON=1|DISABLED=2}
input {port_num} {LOW=0|HIGH=1} state show
input volt3 state show
input volt12 state set {OFF=0|VLO=1|VHI=2}
input volt12 state show
enters cmd group "input"
shows input state
shows input state of all ports in 3 different view
modes
sets sensor name to label
shows label of sensor
inverts input on/off
shows if input inverted
sets input low/high text
shows inputs low/high text
enables input events on/off
shows if input events are enabled
enables different event types
shows what event types are enabled
sets Port for Power Port Switching actions
shows Port for Power Port Switching actions
sets Port state for Power Port Switching actions
shows Port state for Power Port Switching actions
shows state of 3V input voltage {ON=1|VERR=3}
sets state of 12V input voltage
shows state of 12V input voltage {OFF=0|VLO=1}
VHI=2|VERR=3} incl possible error condition
ip4
ip4 hostname set " {name}"
ip4 hostname show
ip4 address set "{ip_address}"
ip4 address show
ip4 netmask set "{ip_address}"
ip4 netmask show
ip4 gateway set "{ip_address}"
ip4 gateway show
ip4 dns set "{ip_address}"
ip4 dns show
ip4 dhcp enabled set {OFF=0|ON=1}
ip4 dhcp enabled show
enters cmd group "ip4"
sets device hostname
shows device hostname 3
sets IPv4 address
shows IPv4 address 3
sets IPv4 netmask
shows IPv4 netmask 3
sets IPv4 gateway address
shows IPv4 gateway address 3
sets IPv4 DNS server address
shows IPv4 DNS server address 3
enables IPv4 DHCP on/off
shows IPv4 DHCP state 3
ip6
enters cmd group "ip6"
| ip6 enabled set {OFF=0|ON=1} | enables IPv6 on/off | |
| ip6 enabled show | shows if IPv6 is enabled | 3 |
| ip6 routadv enabled set {OFF=0|ON=1} | enables IPv6 router advertisement | |
| ip6 routadv enabled show | shows IPv6 router advertisement state | 3 |
| ip6 dhcp enabled set {OFF=0|ON=1} | enables IPv6 DHCP on/off | |
| ip6 dhcp enabled show | shows if IPv6 DHCP is enabled | 3 |
| ip6 address show | show all IPv6 addresses | 4 |
| ip6 gateway show | show all IPv6 gateways | 4 |
| ip6 dns show | show all IPv6 DNS server | 4 |
| ip6 manual enabled set {OFF=0|ON=1} | enables manual IPv6 addresses | |
| ip6 manual enabled show | shows if manual IPv6 addresses are enabled | 3 |
| ip6 manual address {1..4} set "{ip_address}" | sets manual IPv6 address | |
| ip6 manual address {1..4} show | shows manual IPv6 address | 3 |
| ip6 manual gateway set "{ip_address}" | sets manual IPv6 gateway address | |
| ip6 manual gateway show | shows manual IPv6 gateway address | 3 |
| ip6 manual dns {1..2} set "{ip_address}" | sets manual IPv6 DNS server address | |
| ip6 manual dns {1..2} show | shows manual IPv6 DNS server address | 3 |
| ipacl | enters cmd group "ipacl" | |
| ipacl ping enabled set {OFF=0|ON=1} | enables ICMP ping on/off | |
| ipacl ping enabled show | shows if ICMP ping enabled | |
| ipacl enabled set {OFF=0|ON=1} | enable IP filter on/off | |
| ipacl enabled show | shows if IP filter enabled | |
| ipacl filter {ipacl_num} set "{dns_name}" | sets IP filter {ipacl_num} | |
| ipacl filter {ipacl_num} show | shows IP filter {ipacl_num} | |
| modbus | enters cmd group "modbus" | |
| modbus enabled set | enables Modbus TCP support | |
| modbus enabled show | shows if Modbus is enabled | |
| modbus port set | sets Modbus TCP port | |
| modbus port show | shows Modbus TCP port | |
| port | enters cmd group "port" | |
| port {port_num} state set {OFF=0|ON=1} | sets port to new state | |
| port {port_num} state show | shows port state | |
| port all state set "{port_list}" {OFF=0|ON=1} | sets several ports in one cmd - e.g. port all state set "1,3,5" 1 | |
| port all state {MODE0=0|MODE1=1|MODE2=2} show | shows all port states in 3 different view modes | 4 |
| port {port_num} reset | start reset sequence for port | |
| port {port_num} toggle | toggles port | |
| port {port_num} batch set {OFF=0|ON=1} wait {num_secs} {OFF=0|ON=1} | starts batch mode for port | |
| port {port_num} batch cancel | cancels batch mode | |
| port {port_num} label set "{name}" | sets port label name | |
| port {port_num} label show | shows port label name | |
| port {port_num} initstate coldstart set {OFF=0|ON=1|REMEMBER=2} | sets port coldstart initialization | |
| port {port_num} initstate coldstart show | shows port coldstart initialization | |
| port {port_num} initstate delay set {num} | sets port init delay | |
| port {port_num} initstate delay show | shows port init delay | |
| port {port_num} repowerdelay set {num} | sets port repower delay | |
| port {port_num} repowerdelay show | shows port repower delay | |
| port {port_num} resettime set {num} | sets port reset duration | |
| port {port_num} resettime show | shows port reset duration | |
| port {port_num} watchdog enabled set {OFF=0|ON=1} | sets port watchdog to on/off | |
| port {port_num} watchdog enabled show | shows port watchdog state | |
| port {port_num} watchdog mode set {OFF=0|PORT_RESET=1|IP_MS=2|IP_MS_INV=3} | sets port watchdog mode | |
| port {port_num} watchdog mode show | shows port watchdog mode | |
| port {port_num} watchdog type set {WD_ICMP=0|WD_TCP=1} | sets port watchdog type | |
| port {port_num} watchdog type show | shows port watchdog type | |
| port {port_num} watchdog link down set {OFF=0|ON=1} | sets if watchdog active when eth link down | |
| port {port_num} watchdog link down show | shows if watchdog active when eth link down | |
| port {port_num} watchdog host set "{dns_name}" | sets port watchdog host target | |
| port {port_num} watchdog host show | shows port watchdog host target | |
| port {port_num} watchdog port set {ip_port} | sets port watchdog TCP port | |
| port {port_num} watchdog port show | shows port watchdog TCP port | |
| port {port_num} watchdog pinginterval set {num} | sets port watchdog ping interval | |
| port {port_num} watchdog pinginterval show | shows port watchdog ping interval | |
| port {port_num} watchdog pingretries set {num} | sets port watchdog ping retries | |
| port {port_num} watchdog pingretries show | shows port watchdog ping retries | |
| port {port_num} watchdog retrybooting set {OFF=0|ON=1} | sets port watchdog retry booting to on/off |
| port {port_num} watchdog retrybooting show | shows port watchdog retry booting state |
| port {port_num} watchdog bootretries set {num} | sets port watchdog retry boot timeout |
| port {port_num} watchdog bootretries show | hows port watchdog retry boot timeout |
| radius | enters cmd group "radius" |
| radius {PRIMARY=0|SECONDARY=1} enabled set <off=0/on=1> | enables radius client |
| radius {PRIMARY=0|SECONDARY=1} enabled show | show if radius client enabled |
| radius {PRIMARY=0|SECONDARY=1} server set "<dns_name>" | sets radius server address |
| radius {PRIMARY=0|SECONDARY=1} server show | shows radius server address |
| radius {PRIMARY=0|SECONDARY=1} password set "{passwd}" | sets radius server shared secret |
| radius {PRIMARY=0|SECONDARY=1} password hash set "{passwd}" | sets radius server encrypted shared secret |
| radius {PRIMARY=0|SECONDARY=1} auth timeout set {num_secs} | sets server request timeout |
| radius {PRIMARY=0|SECONDARY=1} auth timeout show | shows server request timeout |
| radius {PRIMARY=0|SECONDARY=1} retries set {num} | sets server number of retries |
| radius {PRIMARY=0|SECONDARY=1} retries show | shows server number of retries |
| radius chap enabled set <off=0/on=1> | enables CHAP |
| radius chap enabled show | shows if CHAP is enabled |
| radius message auth set <off=0/on=1> | enables request message authentication |
| radius message auth show | shows if request message authentication is enabled |
| radius default timeout set {num_secs} | sets default session timeout (when not returned as Session-Timout Attribute) |
| radius default timeout show | shows default session timeout |
| snmp | enters cmd group "snmp" |
| snmp port set {ip_port} | sets SNMP UDP port |
| snmp port show | shows SNMP UDP port |
| snmp snmpget enabled set {OFF=0|ON=1} | enables SNMP GET cmds on/off |
| snmp snmpget enabled show | show if SNMP GET cmds are enabled |
| snmp snmpset enabled set {OFF=0|ON=1} | enables SNMP SET cmds on/off |
| snmp snmpset enabled show | show if SNMP SET cmds are enabled |
| snmp snmpv2 enabled set {OFF=0|ON=1} | enables SNMP v2 on/off |
| snmp snmpv2 enabled show | show if SNMP v2 is enabled |
| snmp snmpv2 public set "{text}" | enables SNMP v3 on/off |
| snmp snmpv2 public show | show if SNMP v3 is enabled |
| snmp snmpv2 private set "{text}" | sets SNMP v2 public cummnity |
| snmp snmpv2 private show | shows SNMP v2 public community |
| snmp snmpv3 enabled set {OFF=0|ON=1} | sets SNMP v2 private community |
| snmp snmpv3 enabled show | shows SNMP v2 private community |
| snmp snmpv3 username set "{text}" | sets SNMP v3 username |
| snmp snmpv3 username show | shows SNMP v3 username |
| snmp snmpv3 authalg set {NONE=0|MD5=1|SHA1=2|SHA256=3|SHA384=4|SHA512=5} | sets SNMP v3 authentication |
| snmp snmpv3 authalg show | show SNMP v3 authentication algorithm |
| snmp snmpv3 privalg set {NONE=0|DES=1|3DES=2|AES128=3|AES192=4|AES256=5|AES192*=6|AES256*=7} | sets SNMP v3 privacy algorithm |
| snmp snmpv3 privalg show | show SNMP v3 privacy algorithm |
| snmp snmpv3 authpasswd set "{passwd}" | sets SNMP v3 authentication password |
| snmp snmpv3 privpasswd set "{passwd}" | sets SNMP v3 privacy password |
| snmp snmpv3 authpasswd hash set "{passwd}" | sets SNMP v3 authentication hashed password |
| snmp snmpv3 privpasswd hash set "{passwd}" | sets SNMP v3 privacy hashed password |
| snmp trap type set {NONE=0|V1=1|V2=2|V3=3} | sets type of SNMP traps |
| snmp trap type show | show SNMP trap type |
| snmp trap receiver {trap_num} set "{dns_name}" | sets address and port of SNMP trap receiver {trap_num} |
| snmp trap receiver {trap_num} show | show address and port of SNMP trap receiver {trap_num} |
| syslog | enters cmd group "syslog" |
| syslog enabled set {OFF=0|ON=1} | enables syslog msgs on/off |
| syslog enabled show | show if syslog enabled |
| syslog server set "{dns_name}" | sets address of syslog server |
| syslog server show | shows address of syslog server |
| system | enters cmd group "system" |
| system restart | restarts device |
| system fabsettings | restore fab settings and restart device |
| system bootloader | enters bootloader mode |
| system flushdns | flush DNS cache |
| system uptime | number of seconds the device is running |
| system name show | shows device name |
| system version show | shows actual firmware version |
| timer | enters cmd group "timer" |
| timer enabled set {OFF=0|ON=1} | enables timer functions |
| timer enabled show | shows if timer a enabled |
| timer syslog facility set {0..23} | sets facility level for timer syslog |
| timer syslog facility show | shows facility level for timer syslog |
| timer syslog verbose set {0..7} | sets verbose level for timer syslog |
| timer syslog verbose show | shows verbose level for timer syslog |
| timer {rule_num} enabled set {OFF=0|ON=1} | enables rule |
| timer {rule_num} enabled show | shows if rule is enabled |
| timer {rule_num} name set "{name}" | sets name of rule |
| timer {rule_num} name show | shows name of rule |
| timer {rule_num} {FROM=0|UNTIL=1} set "{yyyy-mm-dd}" | sets date range of rule |
| timer {rule_num} {FROM=0|UNTIL=1} show | shows date range of rule |
| timer {rule_num} trigger jitter set {0..65535} | sets jitter for rule |
| timer {rule_num} trigger jitter show | show jitter of rule |
| timer {rule_num} trigger random set {0..100} | sets probability for rule |
| timer {rule_num} trigger random show | shows rule probability |
| timer {rule_num} trigger {HOUR=0|MIN=1|SEC=2|DAY=3|MON=4|DOW=5} set "{time_date_list}" | sets time date list |
| timer {rule_num} trigger {HOUR=0|MIN=1|SEC=2|DAY=3|MON=4|DOW=5} show | shows time date list |
| timer {rule_num} action mode set {SWITCH=1|CLI=2} | sets switch or cli cmd |
| timer {rule_num} action mode show | shows if switch or cli cmd |
| timer {rule_num} action {SWITCH1=0|SWITCH2=1} {OFF=0|ON=1} set "{port_list}" | sets port list for switch cmd |
| timer {rule_num} action {SWITCH1=0|SWITCH2=1} {OFF=0|ON=1} show | shows port list for switch cmd |
| timer {rule_num} action delay set {0..65535} | delay between cmds |
| timer {rule_num} action delay show | shows delay between cmds |
| timer {rule_num} action console set "{cmd}" | sets cmd string |
| timer {rule_num} action console show | shows cmd string |
| timer {rule_num} action hash set "{data}" | sets action binary form |
| timer {rule_num} action hash show | shows action binary form |
| timer {rule_num} delete | delete one timer |
| timer delete all | delete all timer |
| vt100 | enters cmd group "vt100" |
| vt100 echo set {OFF=0|ON=1} | sets console echo state |
| vt100 echo show | shows console echo state |
| vt100 numeric set {OFF=0|ON=1} | sets numeric mode |
| vt100 numeric show | shows numeric mode state |
| vt100 reset | resets terminal |
Notes
- Legacy - The command has been replaced by a newer version
- Command can be entered on any level
- The output may show 2 lines - the 1st line shows the actual state, the 2nd line the status after reboot
- The output may show several lines
- N/A
- Please see the External Type and External Sensor Field Tables for the correct sensor index
External Sensor Type Table "{sen_type}"
Constants "{7x01=0|7x04=0|7x02=1|7x05=1|7x06=2}"
| Index | Description | Products |
| 0 | Temperature | 7001, 7101, 7201 |
| 0 | Temperature | 7004, 7104, 7204 |
| 1 | Temperature, Humidity | 7002, 7102, 7202 |
| 1 | Temperature, Humidity | 7005, 7105, 7205 |
| 2 | Temperature, Humidity, Air Pressure | 7006, 7106, 7206 |
External Sensor Field Table "{sen_field}"
| Index | Description | Unit |
| 0 | Temperature | °C |
| 1 | Humidity | % |
| 2 | Digital Input | bool |
| 3 | Air Pressure | hPa |
| 4 | Dew Point | °C |
| 5 | Dew Point Temperature Difference | °C |
4.8 Modbus TCP
If Modbus TCP is activated in the configuration, the ports (relays, outputs, eFuses) can be switched and the following data is callable:
Address range overview:
| Device Resource | Start | End | Modbus Data Type |
| Power/Output/eFuse Ports | 0x000 | 0x3ff | Coils |
| DC Inputs | 0x400 | 0x7ff | Discrete Inputs |
| Stop Condition active | 0x800 | 0x800 | Discrete Inputs |
| POE active | 0x801 | 0x801 | Discrete Inputs |
| Status Power Sources | 0x1000 | 0x100f | Discrete Inputs |
| OVP active (Line-Ins) | 0x1010 | 0x101f | Discrete Inputs |
| eFuse Errors | 0x1100 | 0x11ff | Discrete Inputs |
| Info Area | 0x000 | 0x005 | Input Registers |
| CPU Sensor values | 0x080 | 0x083 | Input Registers |
| External Sensors | 0x100 | 0x1ff | Input Registers |
| Fan Level | 0x200 | 0x20f | Input Registers |
| Line Energy Sensors | 0x400 | 0x39ff | Input Registers |
| Port Energy Sensors | 0x3a00 | 0x81ff | Input Registers |
| Bank Energy Sensors | 0x8200 | 0x823f | Input Registers |
| Power Source Sensors | 0x8240 | 0x827f | Input Registers |
| Bank Power Source Select | 0x000 | 0x00f | Holding Registers |
| Fan Mode | 0x010 | 0x01f | Holding Registers |

This chapter is general for all Gude devices. Depending on the device type, some items or certain sensors are not available.

All calculations in this chapter are based on addresses starting at "0". For some Modbus TCP utilities, however, the addresses start at 1, in which case a 1 must be added to the addresses in this chapter. Please try both possibilities for tests!
The Unit-ID is ignored because the device is uniquely identified by its IP address.
Supported Modbus TCP Functions
| Function | Request Code |
| Read Coils | 0x01 |
| Read Discrete Inputs | 0x02 |
| Write Single Coil | 0x05 |
| Write Multiple Coils | 0x0f |
| Read Input Registers | 0x04 |
| Read Holding Registers | 0x03 |
| Write Holding Register | 0x06 |
| Write Multiple Holding Registers | 0x10 |
| Read Device Identification | 0x2B / 0x0E |
Coils
| Device Resource | Start | End | Device Function |
| Power/Output/eFuse | 0x000 | 0x3ff | Coil represens Port State |
Discrete Inputs
| Device Resource | Start | End | Function when set |
| DC Inputs | 0x400 | 0x7ff | Input logically 1 |
| Stop Condition active | 0x800 | 0x800 | Stop Input active |
| POE active | 0x801 | 0x801 | POE active |
| Status Power Sources | 0x1000 | 0x100f | Power Source active |
| OVP active (Line-Ins) | 0x1010 | 0x101f | OVP active |
| eFuse Error | 0x1100 | 0x11ff | eFuse Error |
| Status Power Sources | Offset |
| EPC 8221 / 8226 | 0 = Bank A, 1 = Bank B |
| ENC 2111 / 2191 | 0 = Pwr1, 1 = Pwr2 |
| ESB 7213 / 7214 | 0 = Pwr1, 1 = Pwr2 (only 7214) |
Input Registers
| Device Resource | Start | End | Function |
| Info Bereich | 0x000 | 0x005 | see table |
| CPU Sensor values | 0x080 | 0x083 | see table |
| Externe Sensoren | 0x100 | 0x1ff | see table |
| Fan Level | 0x200 | 0x20f | 0 (aus) bis 3 (maximal) |
| Line Energy Sensors | 0x400 | 0x39ff | see table |
| Port Energy Sensors | 0x3a00 | 0x81ff | see table |
| Bank Energy Sensors | 0x8200 | 0x823f | see table |
| Power Source Sensors | 0x8240 | 0x827f | see table |
Info Area
| Address | Width | Information |
| 0 | 16-bit | Number of Ports (Relay) |
| 1 | 16-bit | Number of Ports (Outlets) with Energy Measurement |
| 2 | 16-bit | Number of Banks |
| 3 | 16-bit | Number of Line-In |
| 4 | 16-bit | Phases per line |
| 5 | 16-bit | Number of Inputs |
Sensor Type Description
| Address | Width | Information |
| 0x080 to 0x083 | 16-bit (signed) | CPU Sensor values |
| 0x100 to 0x1ff | 16-bit (signed) | external Sensors |
| 0x400 to 0x39ff | 32-bit (signed) | Line Energy Sensors |
| 0x3a00 to 0x81ff | 32-bit (signed) | Port Energy Sensors |
| 0x8200 to 0x823f | 16-bit (signed) | Bank Energy Sensors |
| 0x8240 to 0x827f | 16-bit (signed) | Power Source Energy Sensors |
CPU Sensor Values
| Offset | Sensor Field | Unit |
| 0 | Vsystem | 0.01 V |
| 1 | Vaux | 0.01 V |
| 2 | Vmain | 0.01 V |
| 3 | CPU Temperature | 0.1 °C |
External Sensors:
The measured value of the external sensors are coded as fixed point arithmetic. For a factor of e.g. 0.1 in the unit the value must be divided by 10 in order to reach the real measured value. A value of 0x8000 means that no sensor is plugged into the corresponding port, or the corresponding field in the sensor is not available. The formula for the address is (the port numbers start at zero):
0x100 + Port * 8 + Offset

In the Expert Sensor Box 7213 / 7214, the internal sensor corresponds to the value Port = 0, and is coded Port = 1 for Sensor 2 and Port = 2 for Sensor 3.
| Offset | Sensor Field | Unit |
| 0 | Temperature | 0.1 °C |
| 1 | Humidity | 0.1 % |
| 2 | Digital Input | bool |
| 3 | Air Pressure | 1 hPa (millibar) |
| 4 | Dew Point | 0.1 °C |
| 5 | Dew Point Difference | 0.1 °C |
For example, the humidity of the second port has the address: 0x100 + 1 * 8 + 1 = 0x109
Energy Sensors:
We distinguish the line sensors (which correspond to the input circuits) and the port sensors, which measure the energy that is passed over the switched port. The measured values of the energy sensors are returned as signed 32-bit integers. The high-order 16 bits start on the even address, followed by the low-order 16 bits on the odd address. To calculate the address, there are the following formulas (the values for line, port, and phase start at zero):
The measured values of the energy sensors are returned as signed 32-bit integers. The high-order 16 bits start on the even address, followed by the low-order 16 bits on the odd address. To calculate the address, use the following formulas (values for line, port, and phase start at zero):
Port: 0x3a00 + Port * 0x120 + Phase * 0x60 + Offset * 2
For devices with only one phase, the phase is set to zero in the formula.

For devices with only one phase, the phase is set to zero in the formula.
"Power Active" for 1st line sensor and 3rd phase: 0x400 + 0 * 0x120 + 2 * 0x60 + 1 * 2 = 0x4C2
"Voltage" for 2nd line sensor and single phase device: 0x400 + 1 * 0x120 + 2 * 2 = 0x524
"Power Angle" for 4th port sensor and single phase device: 0x3a00 + 3 * 0x120 + 6 * 2 = 0x3d6c
"Power Angle" for 4th port sensor and single phase device: 0x3a00 + 3 * 0x120 + 6 * 2 = 0x3d6c
| Offset | Sensor Field | Unit |
| 0 | Absolute Active Energy | Wh |
| 1 | Power Active | W |
| 2 | Voltage | V |
| 3 | Current | mA |
| 4 | Frequency | 0.01 hz |
| 5 | Power Factor | 0.001 |
| 6 | Power Angle | 0.1 degree |
| 7 | Power Apparent | VA |
| 8 | Power Reactive | VAR |
| 9 | Absolute Active Energy Resettable | Wh |
| 10 | Absolute Reactive Energy | VARh |
| 11 | Absolute Reactive Energy Resettable | VARh |
| 12 | Reset Time - sec. since last Energy Counter Reset | s |
| 13 | Forward Active Energy | Wh |
| 14 | Forward Reactive Energy | VARh |
| 15 | Forward Active Energy Resettable | Wh |
| 16 | Forward Reactive Energy Resettable | VARh |
| 17 | Reverse Active Energy | Wh |
| 18 | Reverse Reactive Energy | VARh |
| 19 | Reverse Active Energy Resettable | Wh |
| 20 | Reverse Reactive Energy Resettable | VARh |
| 21 | Residual Current Type A | mA |
| 22 | Neutral Current | mA |
| 23 | Residual Current Type B RMS | 0.1 mA |
| 24 | Residual Current Type B DC | 0.1 mA |

Whether the measured values "Residual Current" and "Neutral Current" are supported depends on the respective device model. For measured values such as "Neut-Current", which are independent of the phase, the same value is returned for all cases.
DC Energy Sensors:
With the EPC 8291 / 8290 devices, the voltage and current of the individual banks and voltage sources can be read out. The measured values of the energy sensors are returned as signed 16-bit integers. The following formulas are available for the address (the values for Bank and PowerSrc start at zero):
Bank: 0x8200 + Bank * 2 + Offset
Power Source: 0x8240 + PowerSrc * 2 + Offset
Examples:
"Voltage" at third bank: 0x8200 + 2 * 2 + 0 = 0x8204
"Current" at first PowerSrc: 0x8240 + 0 * 2 + 1 = 0x8241
| Offset | Sensor Field | Unit |
| 0 | Voltage | 0.01 V |
| 1 | Current | mA |
Holding Registers
| Device Resource | Start | End | Function |
| Bank Power Source | 0x000 | 0x00f | Sets Power Source for Bank |
| Fan Mode | 0x010 | 0x01f | 0 = Automatic / 1 = Maximum |
Device Identification
Returns manufacturer name and device identification:
| Request Code | 1 Byte | 0x2b |
| MEI Type | 1 Byte | 0x0e |
| Read Dev ID code | 1 Byte | 0x01 |
| Object Id | 1 Byte | 0x00 |
| Response Code | 1 Byte | 0x2b |
| MEI Type | 1 Byte | 0x0e |
| Read Dev ID code | 1 Byte | 0x01 |
| Conformity Level | 1 Byte | 0x01 |
| More Follows | 1 Byte | 0x00 |
| NextObjectID | 1 Byte | 0x00 |
| Number of Objects | 1 Byte | 0x03 |
| Object ID | 1 Byte | 0x00 |
| Object Length | 1 Byte | n1 |
| Object Value | n1 Bytes | "Company Id" |
| Object ID | 1 Byte | 0x00 |
| Object Length | 1 Byte | n2 |
| Object Value | n2 Bytes | "Product Id" |
| Object ID | 1 Byte | 0x00 |
| Object Length | 1 Byte | n3 |
| Object Value | n3 Bytes | "Product Version" |
4.9 Messages
Depending on adjustable events, various messages can be sent from the device. The following message types are supported:
- Sending of e-mails
- SNMP Traps
- Syslog messages
E-Mail messages
Email messages are triggered by the following events:
- Switching of the Ports
- Loss / return of voltage at power supply (only ESB 7214)
- Exceeding of the max / min values of attached sensors • State change of digital sensor input ports
SNMP Traps
SNMP Traps are system messages that are sent via the SNMP protocol to different recipients. SNMP traps are triggered by the following events:
- Switching of the Ports
- Exceeding of the max / min values of attached sensors • State change of digital sensor input ports
Syslog messages
Syslog messages are simple text messages that are sent via UDP to a syslog server. Under Linux, normally a syslog daemon is already running (eg. syslog-ng), for Microsoft Windows systems some freeware programs are available on the market. The syslog messages are sent for the following events:
- Turning on the device
- Enable/disable of syslog in the configuration
- Switching of the Ports
- Loss / return of voltage at power supply (only ESB 7214)
- Exceeding of the max / min values of attached sensors • State change of digital sensor input ports
Support
5 Support
You will find the latest product software on our website at www.gude.info available for download. If you have further questions about installation or operation of the unit, please contact our support team. Furthermore, we present in our support wiki at www.gude.info/wiki FAQs and configuration examples.
5.1 Data Security
To provide the device with a high level of data security, we recommend the following measures:
- Check that the HTTP password is switched on.
- Set up your own HTTP password.
- Allow access to HTTP via SSL (TLS) only.
- Use TLS 1.3 if possible and avoid TLS 1.1.
- Enable authentication and encryption in SNMPv3.
- Disable SNMP v2 access.
- Enable STARTTLS or SSL in the e-mail configuration.
- Archive configuration files securely.
- In the IP ACL, enter only the devices that require access to HTTP or SNMP.
- Use SSH if possible, since Telnet is not encrypted.
- Set login for telnet or serial console.
- Modbus TCP is not encrypted, only activate it in a secure environment.
- Activate "Message Authentication" in RADIUS.
When accessed from the Internet
- Use a randomized password with at least 32 characters.
- If possible, place the device behind a firewall.
5.2 Contact
GUDE Systems GmbH
Managing Director: Dr.-Ing. Michael Gude
Value added tax identification number (VAT): DE 122778228
5.3 Declaration of Conformity
This product from the Expert Sensor Box 7213 / 7214 series is in conformity with the European directives for CE marking applicable to this product. The complete CE declaration of conformity for this product can be found on the website www.gude.info in the download section of the product.
5.4 FAQ
- What can I do if the device is no longer accessible?
- If the Status LED is red, the device has no connection to the switch. Unplug and plug the Ethernet cable. If the Status LED is still red, try other switches. If one uses no switch, but connects e.g. a laptop directly to the device, make sure you are using a crossover Ethernet cable.
- If the status LED is orange for a longer time after unplugging and plugging the Ethernet cable, then DHCP is configured, but no DHCP server was found in the network. After a timeout, the last IP address is configured manually.
- If there is a physical link (status LED is green) to the device, but you can not access the web server, bring the device into bootloader mode and search for it with GBL_Conf.exe. Then check the TCP-IP parameters and change them if necessary.
- If the device is not found by GBL_Conf.exe in bootloader mode, you can reset the settings to factory defaults as the last option.
- Why does it sometimes take so long to configure new SNMPv3 passwords on the website?
The authentication methods "SHA-384" and "SHA-512" are calculated purely in software, and can not use the crypto hardware. On the configuration page, e.g. "SHA-512", needs up to 45 seconds to calculate the key.
- Can you enter multiple e-mail recipients?
- Yes. In the E-Mail configuration in the Recipient Address field, it is possible to enter multiple e-mail addresses separated by commas. The input limit is 100 characters.
- Why did the MIB tables change after the firmware update?
- Since the number of possible event types was increased, the previous trap design resulted in an excess of trap definitions: See Change in Trap Design [53]
- Importing an older firmware
- During a firmware update, old data formats are sometimes converted to new structures. If an older firmware is newly installed, the configuration data and the energy meters may be lost! If the device then does not run correctly, please restore the factory settings (e.g. from the Maintenance Page): 19
6. Disable switching events
- You can set the sending of syslog, emails, etc. when switching ports (only concerns Gude devices with relays) under "System" in the sensor configuration.[44]
- A -
Antenna terminal 7
automated Access 50
- B -
Bootloader Mode 17, 21
- C -
Certificate-Upload 17, 19
clear DNS-Cache 19
Configuration Management 20
Content of Delivery 6
Declaration of Conformity 82
Description 6
device MIB 53
- E -
E-Mail 47
Ethernet connector 7
- F -
Factory Reset 17
FAQ 82
Firmware Upload 17
Firmware-Update 19
- G -
GBL_Conf.exe 17
-H-
HTTP 30
HTTPS 30
-1-
Installa on 7
IP-ACL 29,49
IP-Address 28
IPv6 49
-L-
load Configuration 19
- M -
Maintenance 17
messages 79
Modbus TCP 74
- N -
NTP 37
-0-
Ok button 7
Operating the device directly 15
- P -
Power Ports 24
Push Messages 62
- R -
Radius 50
Redundant Voltage Supply 9
Restart 19
RS232 connector 7
- S -
Security Advice 6
Select button 7
Sensors 10,44
signal strength 7
SIM card slot 7
SNMP 33,51
SSH 62
SSL 56
Start-up the device 7
Status LED 7
Status-LED 15
syslog 33
-T-
Technical Specifications 10
Terminal Assignment 8
Timer 38
Timer Configuration 38
TLS 56
- W -
Watchdog 25

GUDE

Expert Sensor Box 7213/7214