Overview
Here, we'll show you This page aims to show how to execute the Device Module in a Remote Computer. This single configuration allows an out of-the-box setup for gateway and tunneling applications.
On this page:
Table of Contents maxLevel 3 style none
System Requirements
Should this be a subsection of the below section?
To use this feature, the following requirements must be met:
- All computers must be on the same network.
- The product must be installed on both computers.
Using Remote Channels
First
How to Use
To enable this feature, your Project project should use a Communication Protocol. In your Engineering environment, go to the Devices → Channels Tab, and create a new Channel for one of the protocols on the list.
Once a Channel is created, you will find a column called RemoteSettings in the configuration grid.
communication protocol ir order to use this feature. Follow the steps below to enable the remote channel feature.
- Access Devices → Channels.
- Create a new channel clicking the plus icon.
- Once created, in the Initial State column, select the Remote option from the Combo Box.
- Now, in the Remote Settingscolumn, insert the IP Address where the device will run remotely.
| Note |
|---|
If the column Remote settings column is not visible on the grid, you need to enable it by right-clicking the grid header, and selecting it from the list. |
In the Initial State column, select the Remote option from the ComboBox.
The images below showcase this process.
This feature is available for all available protocols. If the channel is either PI, Tundra or Prediktor, the tag's Historical Data that was configured in the Devices → Points tab is returned by the Remote Computer. Any other tab related to those Channel settings (Nodes and Points) are configured as they would be in a local configuration.
| Note | ||
|---|---|---|
| ||
Some protocol drivers must be executed by Windows Users that contain certain access permissions (e.g.: PI). This means that the TWebServer or IIS must be executed by the same Windows User (even when the Project runs as a service). |
Any other tab related to those Channel settings (Nodes and Points) are configured as they would be in a local configuration.
Solution in Execution
Before running the solution, there are some important details that must be taken into account:
- The Remote Device will be executed remotely using the settings from the Device/Channels/RemoteSettings option.
- The Solution (TStartup) will connect to the remote computer that is running the TWebServer or IIS through the SolutionServer. Format: it will be formatted in a IP:port (e.g.Port format (For example: 192.168.1.1:3100- default port is 80).
- Windows Firewallor any other firewall in every router must enable some Inbound and Outbound ports on both computers.
- WebServer
- ports: 80, 3100 or other.
- TServer port
- : 3101 or other.
| Note |
|---|
TWebServer or IIS only need to be executed on the Remote Computer. |
Once the Solution is launched, you will notice the following things.
- You will se a non-default message in the TStartup dialog window, stating that the Module Device was started remotely.
- A process called TRemoteDevice can be found running in the Task Manager on the Server computer. This application is responsible for launching the Device Module on the Remote PC.
- On the Remote computer, we can
- the
- same TRemoteDevice process running inthe task manager. The command line for this process will show more information related to the Channel we are running on remote machine, such as the Channel Name, Server’s IP, and Port Number.
In this section:
| Page Tree | ||||
|---|---|---|---|---|
|