Skip to main content

System Settings

Use System Settings to manage alarm recovery, network parameters, time synchronization, restart operations, configuration backups, and PING checks. For failover configuration, takeover, recovery, and troubleshooting, see Gateway Redundancy.

Operation boundaries

System settings are part of the operation and maintenance function. Before modifying the network, time, redundancy, or performing a restart, confirm the maintenance window, remote connection method, and backup configuration; Do not arbitrarily adjust these parameters during critical stages of equipment operation on the production floor.

First, look at the terminology

TerminologyOn-site understanding
PINGnetwork connectivity test. PING only indicates that the IP is reachable and does not necessarily mean that Web, database, MQTT, or PLC ports are always available.
DHCPautomatically acquires IP, gateway, and DNS. Production gateways are generally recommended to use a fixed IP to avoid address changes after reboot.
DNSdomain name resolution server. When using domain names to connect to services like MQTT, OPC UA, Webhook, NTP, etc., you need to have a usable DNS.
NTP / UTCNTP is the server for automatic time calibration; UTC is the Universal Standard Time. Alarms, historical data, and log checks rely on accurate timing.

Function Entry

After logging into GatewayRuntime Web, enter "System Management → System Settings."

System Settings Page

Module List

ModulePurpose
Gateway FailoverOpen the dedicated Gateway Redundancy manual for pairing, data synchronization, automatic takeover, manual switching, and troubleshooting.
Alarm ConfigurationConfigure whether the alarm is removed directly from the real-time alarm list after recovery.
Network ConfigurationView network card information and edit DHCP, IP, subnet mask, gateway, and DNS server.
Time Sync ConfigurationView local time, UTC time, and time zones, manually set system time, configure NTP servers, and sync intervals.
System controlRestart the GatewayRuntime runtime, restart the application, download and configure database backups.
PING TestPerform connectivity tests on specified IPs or domain names, checking successes, failures, packet loss rates, average latency, and per-packet results.

Alarm Configuration

Click "Alarm Configuration" on the left. This module is used to set the handling method after alarm recovery.

Alarm Configuration Page

Configuration ItemsDescription
Remove immediately after alarm recoveryOnce enabled, remove alarms from the real-time alarm list during recovery; When closed, the restored alarm still needs to be confirmed before being removed.

The switch will save immediately after switching. Before modifying the production environment, confirm the duty and alarm confirmation processes to avoid premature removal of alarms during resumption.

Network Configuration

Click "Network Configuration" on the left. The page displays the current network card list and supports refreshing and editing.

Network Configuration Page

ColumnDescription
Network card nameNetwork interface name.
DescriptionNetwork interface description.
TypeNetwork interface type.
StatusEnabled or disabled status.
IP addresscurrent network card IP.
Subnet maskCurrent subnet mask.
GatewayDefault Gateway.
MAC addressphysical address of the network card.
DHCPwhether DHCP is enabled.
OperationOpen the network configuration side panel.

When editing network configurations, the following fields can be maintained.

Configuration ItemsDescription
Network Card NameRead-only displays the current network card.
Enable DHCPAfter activation, the system automatically obtains network parameters.
IP addressdisplayed and editable when DHCP is closed. The fixed address of the gateway operating host in the field network should be filled in.
Subnet maskdisplayed and editable when DHCP is closed. It must match the on-site network segment plan; incorrect entries will prevent devices on the same network segment from accessing it.
Gatewaydisplayed and editable when DHCP is closed. When accessing cross-subnet devices, NTP servers, or external platforms, the correct default gateway must be provided.
DNS Serversupports multi-value input and allows you to choose or manually create DNS addresses. When accessing MQTT, Kafka, OPC UA, Webhook, or NTP services using domain names, you need an available DNS.
Note

Modifying the network card, gateway, or DNS may cause the current web connection to be interrupted. Before saving, please confirm the remote access method and backup connections on site.

After enabling DHCP, IP, subnet masks, gateways, and DNS are assigned by the network environment, and addresses may change after device reboot or lease updates. When the production gateway requires a fixed access address, static IPs are prioritized or fixed leases are bound to the on-site DHCP server.

Time Sync Configuration

Click "Time Sync Configuration" on the left. The page is divided into two sections: "System Time" and "NTP Configuration."

Time Sync Configuration Page

AreaConfiguration ItemsDescription
System timeLocal timeHost local time.
System timeUTC timecurrent UTC time.
System timeTime zoneName of the host time zone.
System timetime zone IDHost time zone identifier.
System TimeSet TimeOpen the "Set System Time" side panel, select a new time, and confirm save.
NTP ConfigurationEnable NTPControl whether NTP Auto-Sync is enabled.
NTP configurationNTP serverdisplays after enabling NTP, supporting multi-selection, filtering, and manual creation.
NTP configurationsynchronous intervaldisplays a range of 1 to 1440 minutes after enabling NTP.
NTP configurationinstant synchronizationexecutes NTP synchronization instantly.
NTP configurationsavesave NTP enabled status, server list, and sync interval.

Manually setting system time affects collection timestamp, alarm time, historical data storage time, and certificate verification. After enabling NTP, you should specify the time server that the gateway can access; When the intranet cannot access the public network, use the on-site intranet NTP server. The synchronization interval is measured in minutes, ranging from 1 to 1440.

System Control

Click "System Control" on the left. This module provides runtime reboot, application restart, and configuration database backup.

System Control Page

OperationsDescription
Restart the RuntimeRestart the GatewayRuntime runtime. A confirmation popup will appear before execution. Suitable for scenarios such as reloading the runtime after saving or restarting to recover abnormal collection.
Restart the softwareRestart the application. After execution, the web connection will be interrupted and you need to reconnect. Suitable for scenarios where the application itself is abnormal or system parameter adjustments require a full reboot.
Backup Configuration DatabaseDownload a coherent SQLite single-file snapshot containing WAL committed data that can be opened independently for configuring backups or delivering archives. For large-scale configuration, modify network parameters, adjust dual-machine hot standby, or back up before release, it is recommended.
Note:

Operations involving runtime or application restart may affect collection, data forwarding, and web connections. Please perform in the maintenance window.

PING Test

Click "PING Test" on the left. After entering the target address, you can set the number of tests and timeout, then click Start Test.

PING test page

parametersDescription
Destination addressIP address or domain name to be tested.
Number of tests:number of PING requests, ranging from 1 to 20.
TimeoutTimeout per request, ranging from 1000 to 30,000 milliseconds.
Start testingperform PING tests.
Clear resultsClear the current test results.

After testing, the page displays summary cards and packet-by-package tables.

ResultsExplain
Target hostsActual response target hosts.
Number of SuccessesNumber of Successful Responses.
Number of failuresNumber of times no response or errors occur.
Packet loss ratefailure rate.
Average latencyAverage round-trip time for successful requests.
Delay rangeMinimum and maximum round-trip times.
Packet-by-packet resultsStatus, response address, latency, TTL, and error messages for each request.

successful PING only indicates that the network layer is reachable and cannot prove that MQTT, OPC UA, database, or Webhook service ports are available. If ping succeeds but business connection fails, continue to check the destination port, firewall, account password, certificates, and protocol configuration.