You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

Overview

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:

System Requirements

To try to use this feature, be sure that these requirements are met:

  • All computers must be on the same network.
  • The product must be installed on both computers.

Using Remote Channels

To use the remote the Device Module, your project should use a communication protocol ir order to use this feature. Follow the steps below to enable the remote channel feature.

  1. Access Devices → Channels.
  2. Create a new channel clicking the plus icon.
  3. Once created, in the Initial State column, select the Remote option from the Combo Box.

  4. Now, in the Remote Settings column, insert the IP Address where the device will run remotely.


If the Remote settings column is not visible on the grid, enable it by right-clicking the grid header and selecting it from the list.

Important

Some protocol drivers that contain specific access permissions (e.g., PI) must be executed by Windows Users. This means that the TWebServer or IIS must be executed by the same Windows User (even when the Project runs as a service).

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.

Remote Channel 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. It will be formatted in an IP:Port format (For example: 192.168.1.1:3100).

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

  • Windows Firewall or 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.

Once you launch the solution, you will notice the following things.

  • You will see 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, you can see the same TRemoteDevice process running in the task manager. The command line for this process will show more information related to the Channel we are running on the remote machine, such as the Channel Name, Server’s IP, and Port Number.

In this section:

The root page @parent could not be found in space v10.

  • No labels