TGateway
An edge gateway platform for industrial sites
Connect PLCs, instruments, sensors, robots and acquisition modules. Collect, process, evaluate alarms and forward data close to the equipment.
Prepare data at the site, then deliver what the application needs to MES, SCADA, databases and cloud platforms.
Why use an edge gateway?
Industrial sites combine varied device protocols, unreliable networks, large data volumes and short response times. An edge gateway keeps essential processing on site.
Reduce network traffic
Filter, transform and aggregate data locally, then upload the information the application needs.
Respond locally
Evaluate alarms, execute rules and control devices without a cloud round trip.
Keep the site running
Continue collecting, caching and processing data during temporary network outages.
Connect different devices
Use protocol plugins to connect devices from different vendors and communication systems.
Applications
Device data collection
Connect factory PLCs, instruments, sensors and robots, with shared point-list and device-status management.
Production monitoring
Inspect live production status, quality data and alarms to support site decisions.
Data aggregation and synchronization
Forward to MES, SCADA, databases, MQTT brokers or cloud platforms, and aggregate multiple edge gateways.
Product components
Three management interfaces have distinct roles: Studio maintains projects, Watchdog supervises services, and TGateway configures the running gateway.
Studio
Create, import, verify and publish projects, manage sites and tunnel access, and retrieve projects for maintenance. Local simulation is optional.
Watchdog
Supervise runtime processes, check their health, recover from abnormal exits, and manage projects and backups.
TGateway
Configure collection, variables, rules, C# scripts, alarms, forwarding, logs and permissions in the core runtime.
Core capabilities
Before deployment
Watchdog starts and supervises the gateway. Deploy Studio separately when needed. See Quick Start for installation, runtime dependencies and sign-in.
System requirements and default ports
| Item | Studio reference | TGateway reference |
|---|---|---|
| OS | Windows 10/11, Linux | Windows 10/11, Windows Server 2016+, Linux |
| CPU (x64 deployment) | 2 or more cores recommended | 1 or more cores; match the processor architecture to the package |
| Memory | 2 GB or more recommended | 256 MB minimum, 512 MB or more recommended |
| Storage | 4 GB or more recommended | 2 GB or more |
| Runtime | Project compilation and analysis require the .NET 10 SDK. | Standard packages require .NET 10 Runtime. Self-contained or AOT packages need no separate runtime. |
Default Web ports: 5100 for Studio, 6100 for TGateway and 6200 for Watchdog. Check listener addresses, remote-management settings and firewall rules.
Studio and Watchdog listen on 0.0.0.0 by default and support HTTP access by IP. Login passwords use a one-time RSA-OAEP-SHA256 public-key challenge. Use HTTPS to protect Bearer tokens, project packages and other administrative data in transit.
Capacity depends on protocols, device response times, point lists, scripts, forwarding, storage and hardware. Run capacity verification on the real communication path and reserve CPU, memory, disk and offline-cache capacity.
Without a commercial license, use up to 50 channels, 50 devices and 1000 variables. Exceeding any limit requires a source license or CNY 1,998 activation code license, which has no Gateway instance-count limit. See commercial licensing.
Get started
Choose the next guide for your task, from first startup to protocol configuration.