Operating guide: Device and Tag configuration: save, apply, and verify
Device and Tag saves automatically start application. Check save, application, connection and Tag data in order.
1. Find the definition to change
Location: Configuration Center → Device Management or Tag Management. Edit the required object in the current local Site.
- Find the Device by its stable code. Before editing its protocol connection, inspect the saved settings, intended endpoint, and Enabled state.
- For an address, data type, scan interval, alarm, or trend change, select the Device in Tag Management and open the relevant Tag tab.
- Verify Device Code and Tag Code. A regular Tag uses the saved codes joined by a dot, for example PumpPLC.Pressure. Remote Site items cannot be edited in the local definition form.
Expected result Check the target and fields, then save in the original editor.
2. Save the Device or Tag
Saving submits the definition and automatically attempts to apply it to collection. No separate publication is required.
- Click Create device at the end of the Device wizard, or save an existing Device. In the Tag editor, review the fields and click Save.
- Wait for the result; reopen the object to check codes, connection or address fields, enablement, and changed alarm or trend settings.
- If the Tag is saved but alarm-rule synchronization fails, its definition is not rolled back. Keep the current draft, reload, and reconcile the Tag and each alarm rule separately.
Expected result Check persistence and alarm synchronization separately; a successful save does not prove connectivity or valid data.
3. Inspect application and connection
Device details distinguish Configuration application, PLC connection, and Collection. Connection check is an optional diagnostic, not a prerequisite for creation.
- Open Device details and inspect Configuration application. Saved, awaiting application means it is pending; Current configuration applied means the saved Device definition is active.
- Check PLC connection and Collection separately. Standby, not collecting, connection unconfirmed, and connection failure have different meanings.
- If a new Device has no Tags, create and enable the required points in Tag Management. After the first physical Tag is saved, collection still needs an available IO Owner and its first good reading.
Expected result Check save, application, connection and collection states separately.
4. Verify Tag data and dependent functions
For collection changes, verify the target Tag’s quality, timestamp, and value.
- Select the Device and Tag in Tag Test and add it to the monitor. Check live connection, quality, time, and value.
- After an address or type change, compare with the Device address map and expected units. For alarm or trend changes, inspect the corresponding page for new records.
- If configuration is applied but the Tag has no good data, investigate connection, collection ownership, enablement, and address.
Expected result Trends do not backfill data from before recording was enabled.
5. Reconcile conflict, timeout, or uncertainty
A timed-out request or failed refresh may still follow a completed save. Read the current definition before submitting again.
- For a Device unknown-outcome prompt, click Reload and reconcile. For a version conflict, choose Reload latest version and compare it with the local draft.
- For an uncertain Tag mutation, use Reload and reconcile to read the server definition. Correct validation errors before a new save.
- For a partially completed import, review import records, current Tags, and alarm rules; precheck only the remaining or corrected rows again.
Expected result Use the current server state; timeouts and partial results do not mean complete failure.
6. Restore a target definition
Restore connection or Tag parameters in the original editor and save. This applies definitions, not PLC values or deleted history.
- Open the affected Device or Tag and compare its current values with the target configuration record.
- Change the necessary fields and save once. If alarms are involved, check each rule and its category number separately.
- Recheck configuration application, connection, collection, and Tag Test. Inspect alarms and trends where they depend on the change.
Expected result Check the restored definition and runtime state separately.
