Atmel ATSAM3S-EK2 Hoja De Datos
![Atmel](https://files.manualsbrain.com/attachments/0369829915bda09f9c2e00fb805a7753579683b5/common/fit/150/50/8d2bf08978ec3e5bc63f4343ac5e91ce8d0e40045619fa520d910d64af8f/brand_logo.png)
24
Atmel AVR2055
8348D-AVR-06/12
The event duration is one minute, and start time is 10 seconds from now, and so once
a Report Event Status command with Completed status is received, a new event
Load Control Event command can be generated. When the corresponding response
callback is invoked, the status of the Load Control Event command is sent to the
UART:
+Load Control Event Response (<status>)
4.9.3 Interaction with the Meter
Every
REQUEST_SENDING_PERIOD
seconds (by default 15), the ESP application
invokes
ZCL_AttributeReq()
to send a Read Attribute command to Meter (see
Section
) to read the current value of the Current Summation Delivered attribute in
the Metering cluster. It outputs:
->Metering: read attr
On receipt of a Read Attribute Response command from Meter,
ZCL_ReadAttributeResp()
callback is invoked, and the following message will be
sent to the UART:
<-Read Attr response: success
t = <value>
t = <value>
If the Read Attribute command failed, then it outputs:
<-Read Attr response: fail
At this point, the application also takes the Meter device’s response, and forwards it
as a Display Message command to the IPD device without any response. When the
corresponding response callback is invoked, the status of the Display Message
command is sent to the UART:
+Display Message Response (<status>)
4.9.4 Trust center swap out functionality
There are two possible scenarios implemented by the ESP application in relation to
the trust center swap out use case. In one, the ESP, acting as a trust center, saves its
current application link keys in their entirety, which corresponds to a temporary
unavailability, possibly due to some power failure scenario, of the trust center and its
subsequent restoration to the previous working state. In the other, the ESP, acting as
a trust center, saves its current application link keys’ hashes.
The second behavior corresponds to an old ESP device being completely re-
The second behavior corresponds to an old ESP device being completely re-
commissioned, either through a firmware upgrade or through a physical substitution
of a new device. The fact that the link keys’ hashes are available on the new device
indicates that the relevant security information has been transferred from the old trust
center to the new one. The devices on the network will detect that the hashes are
now in use and automatically initiate a new key establishment procedure with the trust
center.
When the ESP is in the network, the user can press
When the ESP is in the network, the user can press
SW0
to save the current link keys’
hashes or
SW1
to save the current link keys. To restore the link keys, the user has to