On this page

Environment setup

Decide where the gateway will run and which device it will connect to. For a first installation, obtain the Watchdog package and .NET 10 Runtime.

Choose the components

Task	Component
Run collection, rules, alarms and forwarding	Watchdog package, including TGateway
Manage projects across sites, update remotely, and provide script analysis and completion	Add Studio when needed
Configure an existing gateway	A browser; Studio is optional

Watchdog and TGateway run on the same site machine and share its operating system and runtime environment. The Watchdog package includes the gateway program. Studio may run independently; it is optional for a normal gateway deployment. Production script editing, compilation and execution take place in TGateway.

Hardware and storage

Item	TGateway reference
Memory	512 MB minimum, 1 GB or more recommended.
Storage	8 GB or more, with additional room for history, logs, project backups and offline cache according to retention.
CPU	At least one core; select the package matching the processor architecture.
Studio	Optional separate deployment; two cores, 2 GB memory or more recommended, with at least 8 GB storage.

These requirements do not establish a fixed variable capacity. Before delivery, perform capacity verification with the actual protocols, collection intervals, scripts and forwarding load.

Check the operating system and architecture

Windows: open Settings → System → About and select the package matching the system type.
Linux: run uname -m. x86_64 means x64; aarch64 means ARM64.
Docker: follow container deployment to prepare an image and persistent storage.

Install .NET 10 Runtime for the same operating system and architecture. The download center includes official runtime links.

Prepare the first collection

Item	What to confirm
Device address	IP and port, or serial port settings
Protocol	The matching collection plugin
Test variable	One known address, data type, unit and expected value
Network	The gateway can reach the device and required ports
Storage	Writable release directory and room for logs, history and offline cache

Without equipment, use the built-in simulator in your first collection.

Default management ports

Component	Web port	Purpose
TGateway	`6100`	Collection, variables, rules, alarms and forwarding.
Watchdog	`6200`	Same-host gateway supervision, site projects and backups.
Studio	`5100`	Multi-site management, remote updates and language services.

For remote access, replace localhost with the deployment host IP. Expose only the required listeners, change the default password and use HTTPS on untrusted networks.

Continue with Quick start. Before delivery, validate capacity with real devices, variables and forwarding workloads.