ABB Error 90779 — CIP Safety Ownership Conflict

What it means · Ce que ça veut dire

CIP Safety Ownership Conflict — ABB robot hardware event on the CIP Safety Ownership Conflict (IRC5). Specific to this controller generation. Severity: Major. Field diagnosis below (French); your robot's own manual remains authoritative.

An external CIP Safety Scanner tries to connect and write to the CIP Safety Adapter. However, another Scanner with different IP Address and/or Safety Network Number (SNN) already owns that connection of the CIP Safety Adapter. The IP Address and SNN of the current owner are written to Non Volatile Memory of the CIP Safety Adapter. - 1 An external CIP Safety Scanner will not be able to connect and read or write signals to the CIP Safety Adapter of the Robot Controller. Le texte constructeur de ce code n'existe qu'en anglais dans les manuels ABB dont il provient. Il est reproduit tel quel ci-dessus ; le manuel de votre robot fait foi.

What to check · Que vérifier

• Inspect the CIP Safety Ownership Conflict, its wiring and connections first.
• Match this code against your robot's event-log timeline before swapping parts.
• Follow the French field checks below — they are the tested sequence for this fault.
• probable : - 1 The IP Address and/or SNN of the external CIP Safety Scanner has changed.
• - 2 The connection on this CIP Safety Adapter is already owned by another external CIP Safety Scanner.
• Verify that the IP Address and SNN of the external CIP Safety Scanner is as intended.
• Reset CIP Safety to clear the ownership from Non Volatile Memory of the CIP Safety Adapter.

Frequently asked · Questions fréquentes

What does ABB error 90779 mean?

ABB 90779 (“CIP Safety Ownership Conflict”): CIP Safety Ownership Conflict — ABB robot hardware event on the CIP Safety Ownership Conflict (IRC5). Specific to this controller generation. Severity: Major. Field diagnosis below (French); your robot's own manual remains authoritative.

How do you troubleshoot ABB error 90779?

Inspect the CIP Safety Ownership Conflict, its wiring and connections first. Match this code against your robot's event-log timeline before swapping parts. Follow the French field checks below — they are the tested sequence for this fault.

Related codes / Codes liés