Start and sign in

Complete one task: enter TGateway from an installed package and identify the correct gateway. If it is not installed, first follow the appropriate deployment guide.

In a normal site installation, Watchdog and TGateway run on the same machine. Watchdog starts and supervises TGateway. Studio adds centralized management of multiple sites; it is not required for your first collection.

Start the gateway

1. If Watchdog is installed as a system service, confirm that service is running. Otherwise use Windows foreground launch or Linux foreground launch. Do not start a second instance.
2. On the deployment host, open http://localhost:6200 and sign in to Watchdog. The unchanged bundled account is admin with password 111111; use the supplied site account if credentials have been changed.
3. On Dashboard, confirm that TGateway is running. If it is stopped, inspect the current project and logs before starting it.
4. Leave Watchdog or its service running and open TGateway.

Watchdog runs the bundled gateway in GatewayApp. An empty project can be configured directly in Runtime. Use project management to upload and apply a package only when restoring an existing project.

For a container running TGateway directly, skip Watchdog sign-in and use the published container Web address.

Sign in to TGateway

1. Open http://localhost:6100. From another computer, use the deployment host IP, such as http://192.168.1.20:6100, rather than that computer’s own localhost.
2. Enter the gateway account and select Sign in. The unchanged bundled credentials are also admin / 111111.
3. Open System Overview. After the first default-account login, change the password.

Watchdog and TGateway manage separate credentials. Changing one password does not update the other. Use the actual address if ports were changed, and do not expose default credentials for public management.

Identify the workspace

• Check the instance and its device, variable, alarm, and forwarding counts in System Overview. Empty lists are normal in a new project.
• For an existing project, compare device names and the point list with the site handover. If menus are missing, check both the instance address and account permissions.
• Watchdog manages processes and project packages. TGateway performs collection, variables, rules, alarms, forwarding, and formal script compilation. Studio provides centralized management, remote updates, script analysis, and code completion.

Closing the browser or selecting Disconnect ends the browser session; collection continues. Stop devices or services from their respective management controls.

Completion and next step

This task is complete when TGateway accepts sign-in and opens System Overview, with Watchdog showing the gateway running. For a direct container deployment, also confirm that the container stays running.

Continue with Collect your first point and read the known simulator value 1234. Add forwarding, history, and alarms individually after this check.

If a page does not open