Reservation · owner · enabled state

An RCB that appears occupied is evidence of another client context.

Do not clear or overwrite it blindly. First identify whether the block is enabled, reserved, owned or simply not writable through the current association.

Immediate answer

Find another approved RCB or coordinate ownership.

Inspect all BRCBs and URCBs linked to the required DataSet. A different block may provide equivalent coverage without disturbing an existing SAS, gateway or engineering client.

What to retain
  • RCB reference and type
  • DataSet reference and exact members
  • reservation or owner value
  • enabled state and configuration revision
  • write response or service error
Diagnostic path

Separate occupied, unsupported and stale state.

An RCB may be actively used, reserved by another association, left with stale-looking metadata, restricted by access policy or exposed differently between the SCL file and the running IED.

01

Inventory all candidate RCBs

Group by DataSet coverage and buffered or unbuffered type before choosing a control block.

02

Read before writing

Capture reservation, owner, enable state and configuration revision with the current association.

03

Test availability without disruption

Prefer a visibly unused approved block. Treat a rejected reservation or enable request as meaningful evidence.

04

Escalate ownership conflicts

Coordinate with the SAS or gateway owner rather than forcing a release during live system work.

ARSAS RCB availability and selected RCB SCL export workflow

Compare availability before selecting an integration path

ARSAS exposes RCB inventory and lets the engineer choose a controlled selected-RCB export baseline.

Related guides

Confirm the selected reporting path is useful.

Check silent reporting, BRCB versus URCB and empty DataSet behavior.

Engineering boundary

Use the evidence to narrow the cause—not to claim conformance.

ARSAS can expose live model, report, GOOSE, file, control and diagnostic evidence. Final conclusions still depend on the approved project design, vendor documentation, test procedure, network access and independent verification.

Technical review

Written and reviewed by Ari Sulistiono.

Reviewed 20 July 2026 for practical IEC 61850 laboratory, FAT, SAT, commissioning and troubleshooting use.

Verified stable release

Download ARSAS 1.6.18 for Windows.

Use the installer for a normal workstation, choose the portable ZIP for a controlled folder deployment, and verify the published SHA-256 before use.

What’s new, limitations and signing status →