UK Smart MeteringKnowledge ProjectStructured SRV and specimen referenceBrowse SRVs

GBCS 16.2 / Auxiliary Controller Event Log

Failure in changing or maintaining Auxiliary Controller state

This is a log entry, not an Alert. It carries no Event / Alert code: it is identified by the outcome field of the Auxiliary Controller Event Log entry, set to 0x02 (Failure).

Log entry identity

Auxiliary Controller Event Log

Section 16.2 requires Event / Alert codes to be two octets and to take a value from Table 16.2. This row is an exception: its Event / Alert Code cell readsSee Use Case ECS35g, which points at the Use Case that reads the log rather than naming a code.

Log
Auxiliary Controller Event Log
Identified by
outcome = 0x02 (Failure)
Entry fields
hanCommandID, outcome, switchNumberAndAction
Read by
ECS35g Read Auxiliary Controller Event Log — message code 0x00FD

Whenever it receives a Report Event Status command with an Event Status of either 0x02 or 0xFE, the ESME shall add an entry to the Auxiliary Controller Event Log where outcome is set to 0x02 ('Failure') if Event Status is 0xFE ('Load Control Event command Rejected') in the command.

SEC Schedule 8 GB Companion Specification, section 7
SRV 6.13 — read this log →SRV 6.13 message patterns →

Alert Details

WAN: NMandatedNon-criticalPre-config: N/A

Device Specific Details

ESME
Supplier

Message Patterns and Examples

This row is not a WAN Alert, so it is never transmitted to the DSP or to a Known Remote Party and has no delivery pattern. It is recorded in the Auxiliary Controller Event Log and read through SRV 6.13.