Exceptions¶

Every RSIPI exception derives from RSIError, so except RSIError catches them all. The hierarchy groups network, safety, configuration, state, data and motion failures.

Reference¶

exceptions ¶

Custom exception hierarchy for RSIPI library.

Provides specific exception types for different failure modes to enable targeted error handling in applications using RSIPI.

RSIError ¶

Bases: Exception

Base exception for all RSIPI-related errors.

RSINetworkError ¶

Bases: RSIError

Base class for network-related errors.

RSIConnectionError ¶

Bases: RSINetworkError

Failed to establish or maintain connection with robot controller.

RSITimeoutError ¶

Bases: RSINetworkError

Network operation timed out.

RSIPacketError ¶

Bases: RSINetworkError

Invalid or corrupted packet received.

RSISafetyError ¶

Bases: RSIError

Base class for safety-related errors.

RSISafetyViolation ¶

Bases: RSISafetyError

Motion command violates safety limits.

RSIEmergencyStop ¶

Bases: RSISafetyError

Emergency stop is active, blocking all motion.

RSILimitExceeded ¶

Bases: RSISafetyViolation

Value exceeds configured safety limits.

Subclasses RSISafetyViolation: exceeding a limit IS a safety violation, and the API docstrings tell callers to catch RSISafetyViolation for out-of-range corrections. Kept distinct so code that wants only limit breaches (rather than any violation) can still select it.