Quick Start

Follow download the package → start Watchdog → sign in to TGateway for your first installation. If the gateway is already available, go directly to TGateway sign-in.

Download the package

1. Open the download center and choose Watchdog.
2. Select the operating system and processor architecture of the gateway computer. For example, use win-x64-WatchDog.zip for Windows x64 or linux-x64-WatchDog.zip for Linux x64. On Windows, check Settings → System → About; on Linux, uname -m reports x86_64 for x64 or aarch64 for ARM64.
3. Extract the complete package into a permanent directory. Keep its files and subdirectories together.
4. Standard TGateway and Watchdog packages require .NET 10 Runtime. Use the download center to select the matching OS and architecture. Studio project compilation and analysis require the .NET 10 SDK. Self-contained and AOT packages do not require a separate runtime.

Watchdog starts and supervises TGateway. Use TGateway to configure collection, forwarding and alarms; use Watchdog to manage processes and project packages. Studio is optional and is installed separately for project maintenance and remote publishing.

Service addresses and deployment requirements

Services and access addresses

Service	Default address	Purpose
Studio (optional)	http://<server-ip>:5100	Manage multiple projects and publish them remotely. It is not required for normal gateway runtime.
TGateway	http://<gateway-ip>:6100	Configure collection, variables, rules, alarms, forwarding, and permissions.
Watchdog	http://<gateway-ip>:6200	Start and supervise TGateway, and manage projects and backups.

Watchdog and TGateway run on the gateway device. Watchdog starts and supervises the TGateway process. Install Studio separately only when you need centralized management of multiple projects or remote publishing.

Before you start

Check	Requirement
Operating system	Use a product-supported Windows or Linux system.
Runtime	Standard TGateway and Watchdog packages require .NET 10 Runtime. Studio project compilation and analysis require the .NET 10 SDK. Use the download center to select the matching OS and architecture. Self-contained or AOT packages do not require a separate runtime.
Ports	Confirm that TGateway port 6100 and Watchdog port 6200 are available. Check port 5100 only when Studio is installed. Allow the ports through the firewall when remote access is required.
Watchdog file	Windows package: TGateway.Watchdog.exe; Linux package: TGateway.Watchdog.
Studio file (optional)	Windows package: TGateway.Studio.exe; Linux package: TGateway.Studio. Keep it with the other Studio files.
Runtime directories	Keep GatewayApp, Projects, and Configuration beside the programs, and give the runtime account read/write access.
Permissions	Open an administrator terminal to start the bundled Windows release or install its service. On Linux, grant execute permission and directory read/write access to the runtime account.
Default account	The bundled default account is admin with password 111111. Change it immediately after the first login.

Start the gateway

Start Watchdog first. Confirm both Watchdog and TGateway are reachable before configuring automatic startup.

Windows direct start

On the gateway device, right-click Start and open Terminal (Admin) or Windows PowerShell (Admin). Accept the Windows elevation prompt, then run Watchdog from its release directory. A normal terminal may report that the operation requires elevation:

Set-Location 'D:\TGateway\WatchDog'
.\TGateway.Watchdog.exe

Replace the example directory with the actual installation directory. Start the program from its own directory; do not copy only the executable to another location.

Linux direct start

On the gateway device, run:

cd /opt/TGateway/WatchDog
chmod +x TGateway.Watchdog
./TGateway.Watchdog

Replace /opt/TGateway with the actual installation directory.

Watchdog starts TGateway from the adjacent GatewayApp directory. You can configure an empty project directly in Runtime Web; creating a project in Studio first is optional. To restore an existing project, use Project Management in Watchdog to upload and apply its package. If Watchdog cannot find the gateway program, check that the release package is complete.

Confirm startup

1. Open http://<gateway-ip>:6200 and confirm that the Watchdog login page appears.
2. Follow Watchdog sign-in, including first-time initialization if requested, and check the dashboard. TGateway should show a running state.
3. Open http://<gateway-ip>:6100 and confirm that the TGateway login page appears.
4. If Studio is installed, open http://<server-ip>:5100 and confirm that its login page appears.

Sign in to Watchdog

Open http://<gateway-ip>:6200 and sign in.

The unchanged bundled default is admin / 111111. Watchdog and Runtime maintain separate credentials; changing a password in one does not update the other.

If the page requests first-time initialization, the installer must read Data/watchdog_bootstrap.token in the Watchdog directory on the gateway computer, enter that token on the initialization page, and set a new administrator password. Then sign in as admin with the new password. Keep the token out of public messages and screenshots.

Use the dashboard to view the gateway process, runtime parameters, and logs. Confirm that TGateway is running and use the API port shown there to open Runtime; this example uses 6100.

Sign in to TGateway

Open http://<gateway-ip>:6100, enter the account and password, and click Login. The bundled default is admin / 111111; use the supplied account if your administrator has changed it. Change the default password in User Management after your first login.

After login, the System Overview page opens.

First checks after login

Confirm gateway name, project name, version, and licensed capacity before making changes. Missing menus can indicate a different instance or account permission. Runtime runs collection, calculation, alarms, rules, and forwarding; Studio maintains and publishes projects; Watchdog manages deployed processes and health. Their hosts and credentials can differ.

Closing the browser or selecting Disconnect ends the browser session while runtime tasks continue. Use the relevant management page to stop a device, target, or service. An empty new project is expected; start with your first collected point, then use Project configuration and delivery for the full workflow.

Step	Page	Check
1	System Overview	The page loads and project information and system resources show no obvious error.
2	Collection Configuration	For an existing project, confirm its channels, devices, variables, and new samples. For an empty project, configure the first point before assessing device status.
3	Data Forwarding	If the project uses forwarding, check its groups, targets, and an independently received payload. An empty forwarding list is expected before configuration.
4	System Logs	No continuous connection, authentication, read/write, or save errors appear.
5	User Management	Change the default password and assign accounts according to responsibilities.

Startup is complete when Watchdog reports TGateway running and you can sign in to Runtime and open System Overview. Continue with your first collected point.

Optional: start and sign in to Studio

When Studio is needed, start it separately on the engineer's computer:

Set-Location 'D:\TGateway\Studio'
.\TGateway.Studio.exe

Start Studio separately only when it is needed:

cd /opt/TGateway/Studio
chmod +x TGateway.Studio
./TGateway.Studio

Sign in to Studio (optional)

Open http://<server-ip>:5100 only when Studio is deployed.

Use Site management to maintain gateway connections. For optional local simulation, create or import a project in Local Simulation Configuration at the bottom of the menu, or run a separate local Gateway. The first successful login opens Overview directly; use the upper-right user menu to change your password when needed.

Common problems

Symptom	What to check
The browser cannot open the page	Confirm that the corresponding service is running, the port is free, and the firewall allows the connection.
The page works locally but not through the device IP	Check the listening address, remote-management settings, and network firewall rules.
Login fails	Check the account, password, user status, and accidental spaces in the password.
The page returns to the login screen	Check whether the service has just restarted, then refresh and sign in again.
Studio cannot see Watchdog	From the Studio computer, open the Watchdog address and check network access, account permissions, and Watchdog logs.
TGateway does not start automatically	In Watchdog, inspect the gateway startup log, the completeness of GatewayApp, directory permissions, and the configured port. An empty project can start without a prior Studio publication.

Configure automatic startup

After direct startup and sign-in work, stop the manually started Watchdog before starting its service, so that two processes do not use the same ports.

Windows: install a service

Install as a Windows service

After direct start works, close the manually started Watchdog before starting its service so that two processes do not compete for the same ports. Open PowerShell as administrator and fill in the actual Watchdog path before creating the service:

$watchdogExe = 'D:\TGateway\WatchDog\TGateway.Watchdog.exe'

sc.exe create TGatewayWatchdog binPath= "`"$watchdogExe`"" start= auto DisplayName= "TGateway Watchdog"
sc.exe start TGatewayWatchdog
Get-Service TGatewayWatchdog

When Get-Service shows Running, open the Watchdog and TGateway addresses again. If the service does not start, check the executable path, working-directory permissions, and the Windows Event Viewer. Create a separate Studio service only when Studio must run continuously.

Linux: install a systemd service

Install as a Linux systemd service

After direct start works, close the manually started Watchdog before starting its service so that two processes do not compete for the same ports. Create /etc/systemd/system/tgateway-watchdog.service:

[Unit]
Description=TGateway Watchdog
After=network.target

[Service]
Type=simple
User=tgateway
WorkingDirectory=/opt/TGateway/WatchDog
ExecStart=/opt/TGateway/WatchDog/TGateway.Watchdog
Restart=always
RestartSec=10

[Install]
WantedBy=multi-user.target

Replace User, WorkingDirectory, and ExecStart with the actual account and installation directory. The account must be able to read and write the Watchdog, GatewayApp, and Projects directories.

Enable and start the service:

sudo systemctl daemon-reload
sudo systemctl enable tgateway-watchdog
sudo systemctl start tgateway-watchdog
sudo systemctl status tgateway-watchdog

When the status shows active (running), open the Watchdog and TGateway addresses. Create a separate systemd service for Studio only when Studio must run continuously.

Next steps

• Collection Configuration: Configure channels, devices, and variables, then verify addresses and data types in More Functions → Debug.
• Data Forwarding: Send data to an external system or database.
• TGateway Web Operation Manual: Find functions by task.
• Studio Web Operation Manual: Use Studio for project management and remote publishing.
• Watchdog Web Operation Manual: Manage services, projects, and backups.