Remote Modbus Polling with Tatsoft FrameworX & Valtoris Gateways

Configuration workflow

1. Verify and bind a static WAN address on the Valtoris Gateway.
2. Configure firewall Port Forwarding to route external Modbus traffic (Port 502) to the internal PLC.
3. Test the connectivity using a standard Windows Ping diagnostic.
4. Initialize the Modbus TCP Channel and Remote Node in FrameworX Designer.
5. Map device Points (Tags) and launch the Runtime to begin demand-driven polling.

1. Valtoris Gateway: Network & Interface Preparation

To enable Tatsoft FrameworX to query field devices reliably, we must establish a stable WAN connection and configure the router’s interfaces.

Step 1.1: Verify Interface Status

Navigate to Network -> Interfaces in the Valtoris Web GUI. Here you can overview your active LAN, WAN, and 4G connections.

Fig 1. Checking the status of all network interfaces to ensure active connections.

Step 1.2: Bind a Static WAN Address

Click EDIT on your active WAN interface. To ensure SCADA always knows where to poll, switch the Protocol to Static address and assign a fixed IPv4 address (e.g., 192.168.1.200).

Fig 2. Assigning the static IP 192.168.1.200 to the gateway’s WAN interface.

Fig 3. Confirming the protocol switch to finalize the static IP binding.

2. Firewall & Port Forwarding Setup

Next, we must instruct the gateway to allow external SCADA requests and route them directly to the Modbus device on the local network.

Step 2.1: Allow WAN Zone Traffic

Navigate to Network -> Firewall. Ensure that the wan zone’s Input, Output, and Forward settings are set to accept so traffic is not dropped.

Fig 4. Configuring Firewall Zones to accept incoming connection requests from the SCADA network.

Step 2.2: Configure Port Forwarding Rule

Go to the Port Forwards tab and create a new rule for FrameworX:

• External Port: 502 (Standard Modbus Port expected by FrameworX)
• Internal IP Address: 192.168.8.182 (The local IP of your field PLC or Modbus device)
• Internal Port: 502

Fig 5. Establishing the rule to route external TCP Port 502 traffic to the internal asset.

3. Pre-Flight Diagnostic Check

Before launching your IIoT platform, it is highly recommended to perform a standard Windows ping test to verify the hardware tunnel is accessible.

Fig 6. Pinging the Gateway’s IP (192.168.1.200). A <1ms response confirms a flawless physical and network connection.

4. Tatsoft FrameworX: Channel & Tag Binding

With the Valtoris Gateway acting as a transparent bridge, we configure the FrameworX Designer.

Step 4.1: Initialize Modbus TCP Channel

Navigate to Devices -> Channels. Create a channel specifying Protocol as Modbus and Interface as TCPIP.

Fig 7. Creating a Modbus Master Connector (TCP/IP) within the FrameworX device tree.

Step 4.2: Define the Remote Node

Go to Devices -> Nodes and create a node (LTE400_Node). In PrimaryStation, enter the Gateway’s IP and Port: 192.168.1.200;502;1.

Fig 8. Directing the node’s PrimaryStation to the Valtoris Gateway’s WAN IP.

Step 4.3: Map Device Points (Tags)

Go to Devices -> Points and create a TagName (Temp_Value). Assign it to your Node and set the Address to 40001.

Fig 9. Mapping the TagName to the specific Modbus holding register (40001).

Crucial Step: Double-click the cell to open Tag Properties and ensure the Enable checkbox is ticked, otherwise data will not be polled.

Fig 10. Verifying the Tag Properties. The tag must be explicitly ‘Enabled’.

5. Runtime Execution & Live Monitoring

Tatsoft FrameworX utilizes a Demand-Driven Polling Engine. Data is only requested when actively required by an interface.

Step 5.1: Configure & Launch Runtime

Navigate to Runtime -> Startup. Ensure your Devices, Displays, Alarms, and Historian modules are selected for the Production profile, then click Run Startup.

Fig 11. Selecting the necessary modules for the Runtime execution.

Fig 12. The TServer startup log. (Note: Ensure all required Windows .NET/C++ redistributables are installed if you encounter local environment errors here).

Step 5.2: HMI Display Binding (Success!)

By dragging the Temp_Value tag onto a live Display, the engine is forced to poll. The data will seamlessly traverse the Valtoris Gateway.

Fig 13. Absolute Success! Real-time data (e.g., ’85’) is successfully penetrating the remote network and updating the UI instantly.