Data Synchronization

Data synchronization writes a variable from one collection device to a variable on another. Each rule is a one-way mapping for setpoint coordination, state transfer, or periodic refresh.

Open the page

Sign in to the WEB configuration interface and open Development Configuration → Data Synchronization. Search by rule name, filter by sync mode or enabled state, and use pagination, sorting, and automatic refresh.

Create a synchronization rule

1. Create two different collection devices and their variables in Collection Configuration. Confirm that the source variable can be read.
2. Enable the target variable and allow variable RPC writes. Its access mode must permit writes, and it must not use a special method. Source and target must have the same data type and array length.
3. Click Add sync, enter a name, and select the source device, source variable, target device, and target variable. For large variable lists, search by name and load more results as needed.
4. Select On change or Interval, and enable Force sync if required. For initial field configuration, leave the rule disabled, save it, and verify the mapping before enabling it.

5. Enable the rule and inspect State, Last successful sync, and Successful writes. Verify the actual value on the target device. Writes require an online source device with a valid collected value.

Parameters

Choose a sync mode

On change

The rule initially aligns the target with the source, then synchronizes subsequent source changes. Ordinary On change mode does not continuously write an unchanged source value.

For example, map a temperature setpoint on the production PLC to a setpoint on the coordinated PLC. Change the source setpoint and verify that the successful-write count increases and the target updates. Then hold the source steady and observe the target and count.

Enable Force sync when the source must maintain the target value. Under suitable commissioning conditions, change the target and verify that it returns to the source value after the target change is collected. Force sync depends on collection and communication; it does not instantly intercept external writes.

Interval

Interval mode writes again at the configured period even if the source is unchanged. Edit the rule, select Interval, enter a period such as 5000 milliseconds, and save. Observe multiple successful writes and verify the target value.

With Force sync disabled, an externally changed target is realigned on a subsequent periodic write. Enabling Force sync also allows a collected target change to trigger correction. Choose a period that respects the device’s permitted write rate and avoids unnecessary repeated writes.

Common operations

Monitor and maintain rules

Use a row’s Edit action to change its mapping or parameters, or its enabled switch to control execution. Select rows for bulk deletion. Export a backup before deletion; disable a rule when only a temporary stop is needed.

Failed writes are retried and do not increase the successful-write count. After recovery, verify both the target value and subsequent successful records.

Export and import Excel configuration

1. Click Export all and save the .xlsx file. All rules are exported regardless of filters, page, or selection. An empty configuration still exports complete headers as an import template.
2. Edit the DataSync worksheet in Excel. Keep its name and column headers, and follow the table below. Referenced devices and variables must already exist; import does not create them.
3. Click Import, then Upload in the Import Excel dialog. Select the file, verify its name, and click Import.

4. After import, verify source and target mappings, sync modes, enabled states, and runtime results. If errors are reported, correct the file and import again.

Both English and Chinese headers are recognized. The entire file is validated before a single merge: matching rules are updated and rules absent from the file are retained. Any error cancels the import without partial changes. Each import accepts up to 100000 nonempty configuration rows, and disabled rules must also satisfy validation.

Use device and gateway redundancy

With device redundancy configured, rules bind to the primary configuration’s variable identity and use the currently active device endpoint. Do not create duplicate mappings for standby devices or treat them as independent variable configurations. See Collection Strategy for device redundancy settings.

With Gateway Redundancy, only the working node performs synchronization writes. The standby displays Standby, and the new working node continues after takeover. Rule configuration is transferred with gateway redundancy configuration snapshots. During commissioning, verify target writes and states before and after switching, and avoid two working nodes controlling the same target.

This page configures variable writes between collection devices. The redundancy page’s data synchronization interval controls data synchronization between gateway nodes and serves a different purpose.

Grant permissions

In Role Management, grant the Data Synchronization menu and appropriate permissions. Viewing, saving, deleting, exporting, and importing are separate permissions. Saving also controls the enabled switch. Grant viewing for monitoring, and grant configuration or Excel operations only to users who need them.

Notes

• Only one enabled rule may write to a target variable. Synchronization loops are rejected; do not configure mutually overwriting A → B and B → A mappings.
• Source and target data types and array lengths must match. Types are not automatically converted. Review variable read or write transformations when conversion is needed.
• Forced and interval synchronization repeatedly write to the target. Verify the target address, write permissions, and permitted field values, then commission a small set of rules first.
• Choose intervals according to source collection periods and target response capacity. Page auto-refresh updates the display only and does not change execution periods.

Troubleshooting