Manual
Manual
This documentation describes the set-up and operation of the Remote HMI Device Manager, henceforth referred to as "software" for short.
The purpose of the software is to parameterise the Remote HMI firmware and manage the firmware licences. The Remote HMI firmware is henceforth referred to as "firmware" for short.
The products and services referred to in this documentation are registered trademarks and as such the property of their manufacturers.
This documentation is intended for administrators and production engineers who are authorised to parametrise HMI systems and set up remote connections.
This documentation uses the following symbols, highlights and notes:
|
Notes on system security and how to avoid data loss
|
|
Important information on workflow and its optimisation
|
|
Notes on Pro licence functions
|
|
Heading of an instruction
|
First step
Interim result Second step
Result of action
|
|
Apply |
indicates a button on the user interface |
|
Dashboard |
indicates a register, menu or a function of the user interface |
|
[F8] |
indicates a key of the keyboard |
|
|
|
R. STAHL HMI Systems GmbH |
|
|
Adolf-Grimme-Allee 8 |
|
|
50829 Köln |
|
|
Germany |
|
|
Telephone: |
+49 221 76806-1200 |
|
Facsimile: |
+49 221 76806-4200 |
|
Homepage: |
r-stahl.com/de |
The software complements the firmware and is used for central parameterisation and licence management. The software access to the firmware must be granted in the Thin Client firmware under the System & Proxy menu item. Once access has been granted, several Thin Clients can be configured and parameterised via templates with the same settings.
Access to the Thin Client is also possible via the Remote Access function. This remote access via VNC must be permitted under the System & Proxy menu item in the firmware.
The software can be installed on a workstation or on a server. It can be used by multiple users.
The software supports the management of templates and device settings in databases. Each database can be password-protected against unauthorised access.
A licence key must be activated in order to use the software.
Without a licence key the software works as a demo version limited to one Thin Client with Remote HMI Firmware version 6 or above.
The user activates the licence key in the software and connects it with the PC or server on which the software is installed.
|
The Pro package licences of the firmware can only be used together with the Device Manager. It is not possible to activate the package licences in the Thin Client's firmware.
|
The size of the management licence for the Device Manager must be the same as that of the Pro package licence. This means that in order to use a Pro package licence for 10 Thin Clients, a management licence for 10 Thin Clients must be available in the Device Manager.
The Remote HMI V6 firmware is a Thin Client software developed for the process industry which is supplied together with R. STAHL SERIES 500 operating devices. It is used to establish and secure remote connections to one or more workstations or application servers. This makes remote access from one operating station to one or more workstations or servers possible.
The devices are connected to the Ethernet via the Ethernet interface (copper or fibre optic). The number of available Ethernet adapters varies depending on the device platform.
The HMI operating stations and the Industrial Box PCs are integrated as Thin Clients and use the available network resources. Depending on the network architecture and access authority level, a remote connection can be established via the IP address to any Ethernet station. The firmware supports the Remote Desktop Protocol (RDP), Virtual Network Computing (VNC) and Keyboard Video Mouse over Internet Protocol (KVM over IP). The Thin Client can use the firmware to call up applications installed on the connected workstations or installed on virtual servers.
The illustration shows a redundant virtual network. It connects Thin Clients via an RDP, VNC or KVM-over-IP connection with workstations and servers. In such a network, every Thin Client can access connected systems and call up applications from there.
RDP connection About RDPThe Remote Desktop Protocol (RDP) is a protocol for remote access. It can be used to display and control screen content of a remote workstation. RDP is an integral part of all Windows operating systems.
A special session is started on the server for the RDP access, and only the connected client can access this session.
The size of the displayed screen content is determined on the Thin Client's display size. If the screen content is only displayed on one half of the Thin Client it will be scaled accordingly.
A Windows server is required for several RDP connections to access one server. A client access licence is required for each client to access and connect to the Windows server. Licencing depends on the operating system of the server.
Either the computer name or the server IP address can be used for addressing.
If you want the option of redundant connections we recommend you use the DNS naming system.
VNC connection About VNCVirtual Network Computing (VNC) is a platform-independent server system. VNC operates according to the Client-Server model.
The VNC service displays the screen content of a remote PC (server) on a local computer (client) The client sends the keyboard and mouse actions to the remote server. This way, the client can use the resources, applications and programs of the server.
The server's display size determines the size of the displayed screen content. If the server display screen ratio is different to that of the Thin Client, the screen content will be compressed or displayed with black edges.
VNC allows multiple access to the server. The display of the clients is then synchronised.
The VNC service must be installed on the remotely controlled PC (host). The Thin Client accesses the VNC server via a VNC viewer application. The installation and configuration of the VNC system on the server and the client requires administrator access authority. The VNC communication between server and client does not require this level of access authority.
VNC services are available from various providers. Depending on the VNC server, these systems have different functionalities.
|
For detailed information and a description of the VNC service, please refer to the documentation of the provider.
|
In order to be able to establish a VNC connection, the VNC server system must be activated on the host. The VNC service acquires the IP address needed for this connection from the settings of the PC's network connection. Depending on the configuration, the IP address is specified manually or allocated by a DHCP server. In the firmware's address book, this IP address is defined as the server IP of the VNC connection.
KVM-over-IP connection About KVM over IP
KVM over IP provides remote access to keyboard-video-mouse systems (KVM). With these systems, a workstation is connected with keyboard, mouse and screen via an external KVM-over-IP box. The KVM-over-IP box is integrated into the network via an Ethernet interface. Data transmission is via the VNC protocol. A VNC service has been installed to establish the connection. The workstation that is part of the KVM system does not require a network connection or a software installation.
The access control system of the Remote firmware is based on three user roles. These are tiered in a hierarchy.
|
User role |
Description |
|
Operator |
The operator can switch between the displays of the connected systems and operate these systems remotely. The operator has access to the basic settings. He or she cannot make any changes to the firmware. |
|
Engineer |
The production engineer can set up, parametrise and delete remote connections. With the Pro licence, the engineer can add existing applications in the firmware. He or she cannot access the Windows user interface of the Thin Client.
The engineer can adjust the following settings: Displays User Interface Connections Keyboard Wedge
|
|
Admin |
The administrator has full access authority to the Windows user interface of the Thin Client. In addition to the options available to the production engineer, the administrator can install third-party applications and drivers on the Thin Client. He or she can configure the network, make system settings via the Remote HMI menu user interface and log into the regular Windows user interface as Admin.
The following adjustments in the Settings can only be made by the administrator: Maintenance System & Proxy Protection Access Control Import & Export Update
|
The Admin and Engineer user roles can be password-protected in the "Access Control" menu.
When the firmware is started up for the first time, the user roles are de-activated and the firmware starts with the Admin user role. Password protection is not active.
|
The Admin and Engineer user roles should only be given to staff familiar with Thin Client administration.
|
The software will start with the following screen.
|
|
opens menu |
|
|
closes menu |
Operating elements vary depending on the menu.
|
Element |
Meaning |
|
|
Switch activated |
|
|
Switch deactivated |
|
|
Button |
|
|
Input field |
|
|
Scroll bar |
|
|
Check box activated |
|
|
Check box deactivated |
Use the main menu to set up the software.
The main menu contains the following functions:
|
Menu entry |
Description |
|
Open Database |
open existing database |
|
New Database |
create new database |
|
Set / Reset Database Password |
Set or reset password for the database |
|
Settings |
Open settings menu |
|
License Manager |
Open licence manager |
|
Firmware Update |
Update firmware |
|
About |
Information on the Device Manager |
|
Legal Notice |
Information on the licence terms of the Device Manager |
You can save the templates and the firmware configurations of the connected devices in databases. The software saves the data in RDM files (name.rdm). You can protect these files with a password.
The License Manager menu contains two registers to manage the licences.
The structure of the lists and the editing options depend on the register.
You can search for product keys in the Search Product Key field.
|
Editing options in the Remote HMI Device Manager register |
|
|
Assign |
assigns licence to the current database |
|
Release |
releases licences for the current database |
|
Add product key |
adds a product key |
You can search for device names in the Search to search for device names. You can narrow down the search by filtering with the Type or Folder/Group columns.
|
Editing in the Remote HMI (Pro Licence) register |
|
|
Get License Status |
calls up the firmware licence status of the device |
|
Add product key |
adds a product key |
Use the Settings menu to set up the software.
|
Database |
specifies how the database reacts during start-up |
|
Size |
specifies the text and element size of the user interface |
|
Request Download Timeout |
specifies the reaction time (timeout) for the user to confirm or reject the acceptance of the device data.
0 seconds; confirmation by user not possible (force download) 1 to 120 seconds
|
|
Logfile |
activates the debugging log function (logfile) |
Go to the Firmware Updates menu for a list of available devices and to initiate a firmware update.
Use the Search to search for device names. You can narrow down the search by filtering with the Type or Folder/Group columns.
|
Options in the Firmware Updates menu |
|
|
Select Firmware File |
opens the search window |
|
Start Download |
downloads the firmware update to the Thin Client |
|
Show changelog |
shows the change log |
|
For an update to be carried out successfully, the UWF filter must be deactivated in the firmware.
|
Go to the Devices menu to add devices to a database and edit them. You can manage address book and applications for each device.
The devices are listed and managed in folders. The menu contains the following elements:
You have the following options in the edit mode:
|
Symbol |
Meaning |
|
|
connected |
|
|
unavailable, no response to ping request |
|
|
available, not connected |
The software supports the import and transmission of the firmware configuration and the storage of entries in the Address Book and Applications registers as templates.
You have the following options:
|
Update from device |
Import the settings of the selected Thin Client |
|
Save as Template |
Save settings as template |
|
Send configuration |
Transmit configuration to Thin Client |
The register bar contains the following functions:
|
Register |
Description |
|
Overview |
Overview of system and connection information, display of event log for device |
|
Address Book |
Diagnosis and management of remote connections |
|
Applications |
Display and management of applications |
|
Networks |
Display and set-up of the network adapters only available with remote access |
|
Settings |
Menus for display and set-up of system, security and network parameters only available with remote access |
Use the Templates menu to save address book entries and applications as templates, edit and send them to a device.
The Templates menu consists of two registers.
|
+ Add New Template |
|
When a template has been opened, you have the following options:
|
Delete |
|
|
Rename |
|
|
Send configuration |
to Thin Client |
The Overview register shows the current device data and the last actions in the event log.
Use the Address Book register to call up or manage configured remote connections or create new remote connections.
The Address Book register lists all configured remote connections.
The software supports the import and transmission of the firmware configuration and the storage of entries in the Address Book and Applications registers as templates.
You have the following options:
|
Update from device |
Import the settings of the selected Thin Client |
|
Save as Template |
Save settings as template |
|
Send configuration |
Transmit configuration to Thin Client |
|
|
opens an item in the list |
|
|
closes an item in the list |
The available edit functions or buttons depend on the sub-menu.
|
|
Add |
Adds a new entry. |
|
|
Clear all |
Deletes all entries in the list |
|
|
Edit |
Opens the highlighted entry for editing |
|
|
Copy |
Copies the highlighted entry and opens the copy for editing |
|
|
Delete |
Deletes the highlighted entry |
|
|
Manage |
Navigates back to the list level |
|
|
Apply |
Applies input |
|
|
Revert |
Rejects input |
|
|
Up |
Moves the highlighted entry one place up in the list |
|
|
Down |
Moves the highlighted entry one place down in the list |
|
|
Edit profile |
Opens the dialogue for editing the remote profile |
You can call up the remote connection via the keyboard if you have specified a hotkey under the Hotkey function. Three keys can be specified.
|
First key |
Second key |
Third key |
|
[Shift] |
[Ctrl] |
none |
|
[Ctrl] |
[Alt] |
[F1] ... [F12] |
The Ctrl key must not be selected twice.
The menus and operating elements look different in the firmware and in the software. Menu items with identical names have identical functionality.
|
If a connection in the address book is greyed out, the user's authority level is too low to access it.
|
|
Symbol |
Meaning |
|
|
connected |
|
|
not connected |
|
|
connection not possible |
|
|
default, will be connected automatically during start-up |
|
|
connected, parallel remote connection, active in the background (multi-session connections require a Pro licence) |
|
The simultaneous use of multiple remote connections (multi-session connection) requires the Pro licence and must be activated in the Connections menu.
|
If the parallel use of several remote connections has been activated, the connections will be displayed as follows:
|
Requires a Pro licence.
|
Use the Applications register to add and manage links to Windows tools and applications, virus protection software or EXE applications such as the Citrix Receiver. You can configure the display and behaviour of an app with various settings, and manage access via the user roles.
Before you can add an app you need to install it on the Thin Client. The Thin Client has to meet the system requirements of the app.
The Applications register shows the connected Apps.
The software supports the import and transmission of the firmware configuration and the storage of entries in the Address Book and Applications registers as templates.
You have the following options:
|
Update from device |
Import the settings of the selected Thin Client |
|
Save as Template |
Save settings as template |
|
Send configuration |
Transmit configuration to Thin Client |
|
|
opens an item in the list |
|
|
closes an item in the list |
The available edit functions or buttons depend on the sub-menu.
|
|
Add |
Adds a new entry. |
|
|
Clear all |
Deletes all entries in the list |
|
|
Edit |
Opens the highlighted entry for editing |
|
|
Copy |
Copies the highlighted entry and opens the copy for editing |
|
|
Delete |
Deletes the highlighted entry |
|
|
Manage |
Navigates back to the list level |
|
|
Apply |
Applies input |
|
|
Revert |
Rejects input |
|
|
Up |
Moves the highlighted entry one place up in the list |
|
|
Down |
Moves the highlighted entry one place down in the list |
|
|
Terminate |
only available with remote access Forces the shut-down of an open application with possible loss of data |
|
|
Select file |
only available with remote access Opens the selection window for executable files |
An application can be selected via the keyboard if a hotkey has been created under the Hotkey menu item. Three keys can be specified.
|
First key |
Second key |
Third key |
|
[Shift] |
[Ctrl] |
none |
|
[Ctrl] |
[Alt] |
[F1] ... [F12] |
The Ctrl key must not be selected twice.
|
Each hotkey can only be allocated once.
|
You can define a command line parameter for each app that allocate application-specific parameters.
Example:
In the browser, the -k www.stahl.de parameter entry calls up the website www.stahl.de in the kiosk mode.
|
Please refer to the description of each application for information on permitted command line parameters.
|
|
Level |
Meaning |
|
Run as standard user |
Starts the application with standard user authority |
|
Run as administrator user |
Starts the application with Administrator authority You can define name and password for the Admin account in the System & Proxy menu. |
|
Run elevated |
Starts the application with extended Administrator authority You can define name and password for the Admin account in the System & Proxy menu. |
The menus and operating elements look different in the firmware and in the software. Menu items with identical names have identical functionality.
You can freely chose the icons representing the apps in the list. In the interest of user-friendliness we recommend you use commonly used symbols.
|
Symbols |
|
A selection of icons standing for different types of app. |
|
Engineer, Admin: Defines who is authorised to start the app. If no symbol is shown all user roles are authorised to start the app. |
|
default, will be connected automatically during start-up |
|
Read only
The settings can only be changed remotely (see Remote access to a device).
|
Use the Networks register to configure the Thin Client for incorporation in the network.
The number and designation of available Ethernet adapters depend on the Thin Client's hardware.
|
Settings on the Windows network level can have an impact on the entire network. Only click on the Advanced if you know your way around Windows network settings. If not, ask your network administrator for help.
|
|
|
Advanced functions |
Opens the Windows network settings |
|
|
Apply |
Applies input |
|
|
Revert |
Rejects input |
|
|
Create/remove team |
Opens the teaming function dialogue |
|
|
Renew IP settings |
Requests renewed IP configuration from the DHCP server |
The Adapter section lists information on the chosen Ethernet adapter.
|
Name |
Name of the Ethernet adapter |
|
MAC |
MAC address of the Ethernet adapter |
|
Driver |
Version of the adapter driver |
|
Speed |
Speed of the Ethernet connection |
|
Status |
Status of Ethernet connection |
|
Read only
The settings can only be changed remotely (see Remote access to a device).
|
The Settings register contains many functions with which the Engineer or Admin can configure the firmware.
The Settings register contains the following menus:
|
Menu |
Contents |
Authorised user |
|
Information |
Current system data, settings and configurations The menu contents vary depending on the device platform. |
|
|
Maintenance |
Functions required for the maintenance of the Thin Client. Allows addition of third-party software and drivers. Activation of Pro licence and Windows LTSB |
Admin |
|
System & Proxy |
Settings concerning device name (in the network) and proxy server |
Engineer / Admin |
|
Protection |
Settings concerning system security |
Engineer / Admin |
|
Displays |
Settings for up to 6 displays |
Engineer / Admin |
|
User Interface |
Behaviour of RemoteHMI menu |
Admin |
|
Access Control |
Setting up of protected user roles |
Admin |
|
Connections |
Settings of connection options |
Engineer / Admin |
|
Keyboard Wedge |
Setting up the COM interfaces for external scanners or readers |
Engineer / Admin |
|
Import & Export |
Functions for the export and import of the device configuration |
Engineer / Admin |
|
Updates |
Firmware updates |
Admin |
|
Legal Notice |
Information on licence terms and conditions for the software used on the Thin Client |
|
The Information menu lists the current system data, settings and configurations. The menu contents vary depending on the device platform.
|
Menu |
Contents |
|
Main |
Essential system information, OS image and firmware version |
|
System |
Information on hardware and operating system This varies depending on the device type. |
|
Network |
Information on computer name and addresses of the proxy server, the device and the gateway |
|
Remote Access |
Information on the status of the remote connections |
|
Protection |
Up-to-date information on system security |
|
Submodules |
List of sub-module versions |
The settings in the Settings and Networks firmware registers can only be changed via remote access.
|
The remote access must be permitted in the firmware under System & Proxy . Depending on the settings a password might be required.
|
|
Opening the main menu
|
Click on
 to open the main menu. |
|
Adding a software licence
|
Open the License Manager menu. In the Remote HMI Device Manager menu, click on Add new product key .
The system will open the activation dialogue.
|
|
Adding a firmware licence
|
Open the License Manager menu. In the Remote HMIs (Pro License) register, click on Get License Status .
The list shows the installation ID and the licence status. In the Remote HMI Device Manager register, click on Add product key , if you want to activate a Pro licence.
The system will open the activation dialogue.
|
|
Adding a firmware licence in the Devices menu
|
Mark the device in the Devices menu. Click on Add Pro License , if you want to activate a Pro licence.
The system will open the activation dialogue.
|
|
If the PC has internet access, you can activate the Pro Licence online via the software.
If not, you need to request the activation code from remotehmi-licensing.stahl.de .
|
Under Product key , enter the licence key you received. Under Company Name , enter your company name. Under Name , enter the name of the licence holder. Under Email Address , enter the e-mail address of the licence holder. Click on Activate Online to activate the licence online.
Click on Activate Offline to activate the licence offline. |
|
Activating the licence online via internet access
|
Make sure the PC has internet access. Click on Activate Online .
The system will start the activation process.
If the activation has been successful, the system will issue a corresponding message, and the licence key will be shown in the list. |
|
Activating the licence offline
|
|||
In the browser, go to the following website: remotehmi-licensing.stahl.de. Select "License Activation". Fill in the form and request the activation code.
|
|||
|
You will receive an e-mail with the activation code to the e-mail address specified in the form. This may take up to five minutes. If you receive no such e-mail, please check your spam folder.
|
In the Activate License window, click on Activate Offline .
|
Under Product key, enter the product key. Under Activation Code, enter the activation code you were given. Under Company Name, enter your company name. Under Name , enter the name of the licence holder. Under Email Address , enter the e-mail address of the licence holder. Click on Activate Offline .
The system will start the activation process.
If the activation has been successful, the system will issue a corresponding message, and the licence key will be shown in the list. |
|
Adding a device
|
Open Devices. Click on Add Device to open the search window. Click on Start Scan.
The network will be searched for available devices. The title bar will show the number of available and new devices.
If all devices have already been added, the list of search results will be empty. Select the device you want from the search results. Confirm your selection.
The device will be added to the list.
|
|
Open edit mode
|
Open Devices. Click on Edit mode to open the edit mode. Highlight the entry and click on Rename selected item to rename the device or the folder. Highlight the entry and click on Delete selected item to delete the device or the folder. Click on Add folder to add a folder. Click on Revert all to revert all entries.
|
|
Adding a folder
|
Open Devices. Activate the edit mode. Click on Add Folder . Enter a name and confirm the entry.
The folder will be added.
|
|
Reading device data (Update from Device)
|
|||
Open Devices. Highlight a device. Click on Device section . Confirm with Yes .
The system will adopt the configuration and issue a message.
|
|||
|
Creating a template of a device
|
Open Devices. Highlight a device. Click on Save as Template .
The Save as Template window will pop up. Enter a name and confirm the entry.
The template will be saved.
|
|
Sending a configuration to the device
|
|||
Open Devices. Highlight a device. Click on Send configuration .
The Download to device window will pop up.
Activate Force Download if you want to force the download. Click on Start download .
A progress bar shows how the data transfer is progressing.
If you want to abort the transfer, click on Cancel .
The system will issue a message.
|
|||
The automatic logon at the server can be configured in the settings of the remote connection. For this you need the user ID and the password for the server.
|
Only users with authority for remote access to the server can log on to the server. Check the user authority at the server or the KVM box.
|
Different parts of the server screen can be displayed. You can configure the display via Show on when creating the remote connection.
The following display options are available:
|
Symbol |
Name |
Meaning |
|
|
Full display |
shows the full screen |
|
|
Left display half |
Scales the remote screen content and displays it on the left hand side |
|
|
Right display half |
Scales the remote screen content and displays it on the right hand side |
|
|
Upper display half |
Scales the remote screen content and displays it at the top half |
|
|
Lower display half |
Scales the remote screen content and displays it at the bottom half. |
You can configure how the remote connection behaves during a system startup or when it is lost, as follows:
|
Auto connect on system startup |
|
Automatically establishes a connection during system startup, is represented by the |
|
|
During a system startup the dial-up must be started manually |
|
|
Auto reconnect on connection loss |
|
Automatically reconnects after the connection has been lost |
|
|
After the connection has been lost, the dial-up must be started automatically |
You will need the IP address or the name of the server for the configuration. These are stored in the system properties of the server.
|
For RDP connections, remote access must be explicitly permitted in the server's system properties. The remote access must be configured for the user.
|
Open the Address Book register. Click on + Add .
A new address book entry is created. Click on Edit . In Connection Settings, via the drop-down field Type, select "RDP". Under Name, enter the name of the connection. Under Server Address, enter the IP address or the name of the server.
Under User Name and Password, enter the logon data of the server. If you want to be able to call up the remote connection via the keyboard, use Hotkey to specify a hotkey. Click on Show on to select the display option. Specify the minimum user role required for the manual set-up of the connection.
Click on Apply to set up the connection.
The connection is shown in the address book.
|
||||||
The VNC software must be installed on the Thin Client and the server, requiring Administrator authority on both.
To set up the connection you require the IP address of the VNC server and, depending on the configuration, the VNC password.
|
If the port number of the VNC server is different from the standard port, the IP address needs to be extended to include the port number, for example: 192.168.1.23:5901
|
Open the Address Book register. Click on +Add .
A new address book entry is created. Click on Edit . In the Connection Settings, select "VNC" from the Type drop-down field. Under Name, enter the name of the connection. Under Server Address, enter the IP address of the server.
Enter the logon data of the server. If you want to be able to call up the remote connection via the keyboard, use Hotkey to specify a hotkey. Under Show on, select the display option. Specify the minimum user role required for the manual set-up of the connection.
Click on Apply to set up the connection.
The connection is shown in the address book.
|
||||||
The process varies according to which VNC service is used. For more information, please refer to the documentation provided by the VNC service manufacturer.
|
This process requires Administrator authority.
|
Make sure that the Thin Client can contact the host. If both are part of the same network, this will be the case. Make sure the VNC service is installed and activated on the host (see Activating VNC server system on the host). If the network connection is protected via a firewall you need to configure this firewall. Permit network communication via the port where the VNC service is ready to receive (5900 as a standard). If the network connection is protected via a router, you need to configure this router. For the transfer of network communication, specify every configured port where the VNC service is ready to receive (5900 as a standard). Check whether the VNC service is working properly and whether it accepts incoming connections.
The host is ready.
|
The process varies according to which VNC service is used. For more information, please refer to the documentation provided by the VNC service manufacturer.
|
This process requires Administrator authority.
|
Make sure that the Thin Client can contact the host. If both are part of the same network, this will be the case. If the VNC connection of the Thin Client is protected via a proxy server you have to specify the proxy server in the VNC viewer.
The Thin Client is ready
|
|
This test can only be conducted via remote access to the Thin Client.
|
|
In order to be able to edit the settings, the connection must be inactive.
|
|
Moving connections in the list
|
Open the entry in the Address Book register with  .Click on ↑ to move the entry up one place in the list. Click on ↓ to move the entry down one place in the list.
The connection is moved in the list.
|
|
Editing connection settings
|
Deactivate the connection in the Address Book register. Open the entry. Click on Edit to edit the settings. Change the settings as required. Click on Apply to accept the changes. Click on Revert to reject the changes. Click on Manage to edit the list.
Click on [  ] to close the entry and return to the list. |
|
Deleting a connection
|
Deactivate the connection in the Address Book register. Open the connection. Click on Delete to delete the connection. Confirm the security message.
The connection is deleted.
|
|
Copying a connection
|
Deactivate the connection in the Address Book. Open the entry. Click on Copy to copy the settings.
A new entry is created. Open the entry and edit the settings as required. Click on Apply to accept the changes. Click on Revert to reject the changes. Click on Manage to edit the list.
Click on [ ] to close the entry and return to the list. |
|
The remote access must be permitted in the firmware under System & Proxy . Depending on the settings a password might be required.
|
|
Connecting to the device
|
Under Devices, select the device you want to access remotely.
The device configuration will pop up. Select the Remote Access register. Click on Connect to connect to the Thin Client.
Once the connection has been established, a preview of the screen content of the Thin Client will pop up.
|
Click on Fullscreen to switch to full screen mode.
|
|
Please also refer to the notes and instructions of the firmware manual.
|
|
Disconnecting the remote connection
|
Click on Disconnect to actively disconnect the connection. On exiting the Remote Access register, the connection will be disconnected.
|
|
Requires a Pro licence.
|
|
Compatibility with third-party software The firmware is qualified for software that is included in the delivery of the supported HMI devices. R. STAHL HMI Systems GmbH does not accept any liability for the functionality of the software of any other providers. Before installing software of other providers make sure it is compatible.
|
|
Checking system requirements and ability to run of the application
|
Make sure that the application is compatible. Check whether the system requirements are met. Check whether the application can be installed on the Thin Client. This is done in the Admin role. Check whether the application works smoothly.
If all conditions have been met, the application is compatible and able to run.
|
|
Adding an app
|
||||||
Open the Applications. Click on +Add .
A new entry is created. Open the entry. Go to Icon, select a suitable symbol from the drop-down field. Activate Autostart if you want the application to start automatically. Under Name, enter the name of the application. If you want to be able to call up the remote connection via the keyboard, use Hotkey to specify a hotkey. Enter the file path to the program file on the Thin Client in the Path field. If you want to define application-specific parameters, click on Parameters to enter a command line parameter. For information on possible parameters please refer to the manual of the application. Under Application privilege level to specify how the application should be started. Activate Close RemoteHMI menu on app start if you wish to close the firmware when starting the application.
Activate Use predefined admin login credentials if you want to start the application via the login data of the Thin Client. Enter the user name and the password. Click on Min user role required to start app manually to define the lowest required user authority level for starting the application.
Click on Apply to accept the input.
The application will be displayed on the dashboard and in the Applications register. Click on Manage to move the app in the list. Click on [ ] to close the entry and return to the list.Check whether the app opens correctly when clicking on the entry.
|
||||||
|
Moving an application in the list
|
In the Applications register, open the entry you want by clicking on .Click on ↑ to move the entry up one place in the list. Click on ↓ to move the entry down one place in the list.
|
|
Changing application settings
|
Open the entry you want in the Applications register. Click on Edit to edit the settings. Make the required changes. Click on Apply to accept the changes. Click on Revert to reject the changes. Click on Manage to edit the list.
|
|
Copying an application
|
Check the compatibility and ability to run of the application before creating a link to a new application (see "Adding apps") Open the Applications register. Open the entry you want to copy. Click on Copy to copy the application's settings.
A new entry is created. Click on Select File and select the program in Windows Explorer. Open the entry and change its settings as described under Adding apps. Click on Apply to apply the changes. Click on Revert to reject the changes. Click on Manage to move the app in the list.
Click on [ ] to close the entry and return to the list. |
|
Closing an application
|
|||
Open the entry you want in the Applications register. Click on Terminate to force the termination of the application. Confirm the security message.
The application is shut down.
|
|||
|
Deleting the link to the application
|
|||
Open the entry you want in the Applications register. Click on Delete to delete the link. Confirm the security message.
The link to the app is deleted.
|
|||
|
Creating templates
|
Open Templates. Click on Add new Template . Enter a name and confirm the entry.
The template will be added.
|
|
Editing templates
|
Open Templates. Select the template you wish to edit.
The template will be opened for editing.
|
|
Transferring template to device
|
|||
Open Templates. Click on Send configuration .
The Send configuration to device dialogue will pop up. Select the device to which you want to transfer the template.
Activate Force Download if you want to force the download. Click on Start transfer .
A progress bar shows how the data transfer is progressing.
If you want to abort the transfer, click on Cancel .
The system will issue a message.
|
|||
You can save the templates and the firmware configurations of the connected devices in databases. The software saves the data in RDM files (name.rdm). You can protect these files with a password.
|
Opening the main menu
|
Click on
to open the main menu. |
|
Creating a database
|
Click on New Database to create a new database. Enter a name. Click on Browse to select a folder in which you want to save the database and confirm your selection. Click on Create database .
The new database will be opened.
|
|
Opening a database
|
Click on Open Database to open an existing database. Click on "Browse" to select a database and confirm your selection. Click on Open .
The new database will be opened.
|
|
Creating or changing a password
|
|||
Click on Set / Reset Database password. Enter a password (min. 5 characters long) and confirm.
The next time you open the database you will be asked to enter the password.
|
|||
|
Deleting a password
|
Click on Set / Reset Database password. Click on Reset Password to remove an existing password.
The database is now no longer password-protected.
|
|
Opening the main menu
|
Click on
to open the main menu. |
|
Specifying and editing settings
|
|||
Activate Open last database at start to open the database you last used after a re-start. Click on Remote HMI Manager text size to specify the text size. Click on Request Download Time to specify the time available to the firmware user to confirm or reject changes.
|
|||
|
Accept or reject settings
|
Click on Apply to accept the settings. Click on Revert to reject the changes.
|
|
Opening the main menu
|
Click on
to open the main menu. |
|
Carrying out a firmware update
|
||||||
Click on Select Firmware File to select the update file in the Windows Explorer. Click on Start Download to download the update to the Thin Client.
A progress bar shows how far the update installation has progressed.
If the update has been finished, the system will issue a message.
|
||||||
|
No connection possible between Remote HMI Device Manager and Thin Client |
||
|
Cause |
How to fix it |
Who |
|
Incorrect network configuration | Check network configuration.
|
Engineer |
|
Access from Device Manager to Thin Client not permitted | Allow access in the System & Proxy menu.
|
Engineer |
|
These settings can only be made at the Thin Client.
|
|
Configuration of remote access to the Thin Client via VNC and RDM
|
Activate Allow configuration export/import via RemoteHMI Device Manager to allow the export and import of the Thin Client configuration via the RemoteHMI Device Manager. Activate Allow remote access via VNC to allow the VNC remote access to the Thin Client. Enter the password for the remote control. As an option, enter a password for remote access without operating permit. Click on Advanced VNC Server Config if you need to change the VNC settings. Click on Input blocking during remote access to define access behaviour during a remote connection. Activate Off to allow local and remote operation during remote access. Activate Local to block local operation of the Thin Client during remote access. Activate Remote on local activity, inactivity timeout = 3 sec to block the remote operation via local operation during remote access.
This block is removed if no local operation occurs during a specified idle period. The factory setting for this idle period is 3 seconds. This can be adjusted. To adjust the idle period, click on Advanced VNC Server Config .
|
The following explains the procedure for the TightVNC server.
In order to be able to establish a VNC connection, the VNC server system must be activated on the host. The VNC service acquires the IP address needed for this connection from the settings of the PC's network connection. Depending on the configuration, the IP address is specified manually or allocated by a DHCP server. In the firmware's address book, this IP address is defined as the server IP of the VNC connection.
The following parameters are necessary to configure the VNC connection. The actual name may vary depending on the VNC server system used.
The VNC server address is the same as the server IP address or the server name.
The VNC server systems usually have several ways to find out the address with which the server can be addressed in the network.
In addition to the IP address, port numbers can be allocated in the settings of the VNC server, with which the server can be addressed in the network.
The target address of the Host PC must be located in the network of the Thin Client or must be contactable from the Thin Client.
|
Accept connections on port
 |
Defines the server connection port for data transmission (standard port 5900). If you are using a different port due to network conflicts you need to configure this port. Check the settings of a firewall. |
VNC server applications authenticate users of a VNC connection via a password. The following password procedures are available:
|
None |
No password is defined. The VNC server on the host allows access to each remote PC (Remote HMI) requesting a VNC connection via its address. |
|
VNC password |
Defines one or more passwords (depending on VNC server application) which the VNC server system requests from the Client for authentication purposes. |
|
Windows password |
Uses the Windows access authentication. The VNC server system grants the client access to the host if logged on with the valid Windows password. |
|
Single sign on |
Uses Windows access authentication and authentication via Windows-based login. The VNC server system grants access to the client if the user has entered a valid Windows login. |
Most VNC servers use encryption to protect the transmission of image, mouse and keyboard data from unauthorised access.
|
Always on |
Data is always encrypted |
|
Prefer on |
Data is always encrypted unless the Thin Client requests no encryption (standard). This setting is necessary if the configuration requests no encryption. |
|
Prefer off |
Data is not encrypted unless the Thin Client requests encryption. This setting is necessary if the configuration requests encryption. |
Allows the host user to accept or reject a connection request. Since the host is usually used for direct remote access, this setting is not relevant for the Thin Client connection.
Specifies that the VNC server system is automatically activated when Windows is started. If this function is not activated, the remote access must be explicitly started after a system start of the host PC.
EMERSON's DeltaV®-Remote-Desktop-Connection-Client (DRDC) allows access to a virtualised operator or engineering workstation within a DeltaV®-virtualisation architecture. This way, applications that run on a distributed control system can be accessed via the Ethernet.
You can add a DRDC connection via an app in the Applications register (see Adding apps).
|
Requires a Pro licence.
|
|
For the software to be updated, the current software version must first be de-installed.
|
De-install the old software version. Double-click on the ...Setup.exe update file. Follow the instructions of the installation assistant.
A progress bar tracks the progress of the installation. Once the installation has been completed, the system will issue a message. Open the software.
During the start you can either open an existing database or create a new one.
|
