System Requirements

To make use of this feature the following requirements must be matched.

  • All computers must be on the same network.
  • The product must be installed on both computers.
  • A WebServer application (e.g.: TWebServer, IIS) must be running on the remote computer.


How to Use

To enable this feature, your Project should make use of a Communication Protocol. In your Engineering environment, navigate to the Devices > Channel 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.


If the 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.


This feature is available for all of the available protocols.

If the channel is either PI, Tundra or Prediktor, the tag's Historical Data that was configured in the Device > Points tab is returned by the Remote Computer.

Important

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).


Channel Configuration

To start the remote setup, navigate to the Devices > Channels tab. Under the RemoteSettings column, insert the IP Address where the device will run remotely.

Any other tab related to those Channel settings (Nodes and Points) are configured as they would be in a local configuration.



Project in Execution

Before running the Project, 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 Project (TStartup) will connect to the remote computer that is running the TWebServer or IIS through the  ProjectServer. Format: IP:port (e.g.: 192.168.1.1:3100 - default port is 80).
  • Windows Firewall or any other firewall in every router must enable some Inbound and Outbound ports on both computers.
  1. WebServer port - 80, 3100 or other.
  2. TServer port - 3101 or other.


TWebServer or IIS only needs to be executed on the Remote Computer.


Once the Project is launched, you will notice 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 also look at the Task Manager and browse for that same TRemoteDevice. 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.


  • No labels