Federation organizes multiple sites into one runtime topology. Each site has its own site code, public address, local node, and visible modules. Single-site projects usually keep only the local site. Multi-site projects must maintain stable site codes and reachable addresses.
Federation organizes multiple sites into one runtime topology. Each site has its own site code, public address, local node, and visible modules. Single-site projects usually keep only the local site. Multi-site projects must maintain stable site codes and reachable addresses.
Redundancy controls which node currently collects a device. Only one active collection node should poll, write, and publish live values for the same device at one time. Standby nodes stay ready and take over when the active node fails.
Screens, import, alarms, and trends use the local device and tag configuration. Federation makes sites visible to each other and decides which node currently collects a PLC. A remote site having the same tag name does not mean the local server already has that tag.
Use System Status first, then Sites and Devices. Confirm runtime topology, public site address, node count, standby nodes, and current collection devices. Also separate local PLC tags from federated mirror tags when reading tag counts and lists.
Check System Status, then Modules, then Sites, Devices, and Tag Diagnostics. The most common issues are wrong site addresses, unreachable remote nodes, missing failover, or federated mirror tags being mistaken for local PLC tags.
