Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Here, we'll show you how It is possible to execute the Device Module Device in a Remote Computer. This single configuration allows , allowing an out-of-the-box setup for gateway and tunneling applications. 

On this page:

Table of Contents
maxLevel3
stylenone


System Requirements

To try to use this feature, the following requirements must be 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.
    Image Added
  4. Now, in the Remote Settingscolumn, insert the IP Address where the device will run remotely.
    Image Added

Note

If the Remote settings

How to Use

To enable this feature, your 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.

Image Removed

In the Initial State column, select the Remote option from the ComboBox
Note

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.

Image Removed

.

Image Removed

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.


Note
titleImportant

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

Channel Configuration

To start the remote setup, go to the Devices → Channelstab. Under the RemoteSettings column, insert the IP Address where the device will run remotely.


Image Removed

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.

Project in

Remote Channel Execution

Before running the Projectsolution, 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

    Solution (TStartup) will connect to the remote computer that is running the TWebServer or IIS through the

    ProjectServer. Format:

    SolutionServer. It will be formatted in an IP:

    port (e.g.

    Port format (For example: 192.168.1.1:3100

    - default port is 80

    ).

    Note

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


  • Windows Firewallor any other firewall in every router must enable some Inbound and Outbound ports on both computers.
      WebServer port -
        • WebServices ports: 10108, 80, 3100, or other.
        • TServer port
      -
        • : 3101 or other
      . NoteTWebServer or IIS only need to be executed on the Remote Computer
        • .

      Once you launch the Project is launchedsolution, you will notice the following things.

      • You will see a non-default message in
      the TStartup
      • the TStartup dialog window
      ,
      • stating that the Module Device was started remotely.
      TStartup dialog window messageImage Removed
      • A process
      called TRemoteDevice
      • 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.

       TRemoteDevice running on Task ManagerImage Removed

      • On the Remote computer,
      we
      • you can
      also look at the Task Manager and browse for that same TRemoteDevice
      • 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.
       TRemoteDevice.exeImage Removed

    In this section:

    Page Tree
    root@parentDevices (Field Communication)
    spacesV10