This read-write control injects a single bit error into the test pattern currently being sent on the interface when set to inject(2); the agent returns a bad-value error if no pattern is being sent, and reading the object always returns noOp(1) regardless of prior writes. Admins use it to deliberately introduce a known error into an active test-pattern transmission, useful for validating that error-detection and reporting on the far end (or devDS1MonResultErrorCount locally) is working correctly. An admin verifying end-to-end error monitoring would write inject(2) here while a test pattern is running, then confirm the expected error shows up in the monitoring results.