Start with the teamwork symptom
Select the problem shown at the site. The app will separate a U2U communication fault from normal standby, failover, cascade, or scheduled rotation.
PROBLEM TO DIAGNOSE
Choose the closest symptom. The result will check whether the behavior is a fault or a normal teamwork response.
TEAM IDENTIFICATION
Network reminder: The U2U network is a private controls network. Do not connect it to the building or IT network. Record existing settings before changing addresses, groups, IP information, teamwork, standby, or rotation.
Fast path: Correct the expected and connected unit counts, then answer only the checks you know. The most relevant check section opens automatically.
DISPLAYED INFORMATION
Optional. Type the event exactly as displayed.
U2U NETWORK CHECKS
TEAMWORK / STANDBY CONDITIONS
Dynamic Unit Staging enabled through iCOM-SWhen enabled, iCOM-S staging order overrides traditional U2U address order.
Mode 3 prerequisites verifiedVariable-capacity cooling, variable-speed fans, supply control sensors and required remote-sensor setup.
Primary finding
Complete the conditions first
Teamwork Mode—
Connected Units—
Unit Status—
WHAT SHOULD BE HAPPENING
MOST LIKELY CAUSES
DIAGNOSTIC ORDER
Field reminder: Save or record every unit’s existing U2U and teamwork settings before changing them. Correct one confirmed conflict at a time, then verify communication and group behavior before moving to the next setting.