Write Event 10 in Metrology Event Log

Dimensione: px

Iniziare la visualizzazioe della pagina:

Download "Write Event 10 in Metrology Event Log"

Mariangela Manzi
6 anni fa
Visualizzazioni

1 Sincronizzazione Leggera (Light Synchronization out of a broadcast window, e.g. a FAC session, after a push) Amendment to UNI/TS Sincronizzazione e Impostazione DC/GW Synch UNIX Time Write UNIX Time 0-0: IC 2 Attr 2 Drift < 60 sec Set B0 in Diagnostic Data is invalidated at SAC level when received with B0 bit set Monthly Cumulative Drift <= 60 sec This shall be understood as the absolute value of the sum of the drifts (with sign) during a month Send NAK Execute Synchronization Response

2 Sincronizzazione Leggera (Light Synchronization during a broadcast window) Amendment to UNI/TS Sincronizzazione e Impostazione DC/GW Synch UNIX Time Write UNIX Time 0-0: IC 2 Attr 2 Metrology Event Log Drift < 60 sec Set B0 in Diagnostic Data is invalidated at SAC level when received with B0 bit set Monthly Cumulative Drift <= 60 sec This shall be understood as the absolute value of the sum of the drifts (with sign) during a month Execute Synchronization

3 Impostazione del Clock (Clock Setting) Installer/Maintainer Client Management Client «Clock Flavour» Write Clock 0-0: IC 8 Attr 3 - time_zone IC 8 Attr 5 - daylight_savings_begin IC 8 Attr 6 - daylight_savings_end IC 8 Attr 7 - daylight_savings_deviation IC 8 Attr 8 - daylight_savings_enabled «Time Setting» command Write UNIX Time 0-0: IC 2 Attr 2 UNI/TS Device Mode is «NOT CONFIGURED»? Action Clock 0-0: IC 8 Method 6 «shift» Write Event 11 in See Clock Synchro XX pages Accept Immediately with no diluted synch Response

4 Sincronizzazione Forte (Strong Clock Synchronization) Management Client «Time Setting» command See Clock Setting page UNI/TS Device Mode is «NOT CONFIGURED»? Action Clock 0-0: IC 8 Method 6 «shift» Drift > 60 s Synch < 60s supported? Set B0 in Diagnostic Data is invalidated at SAC level when received with B0 bit set Execute Synchronization See Clock Synchro Test MG page Send NAK Do not synchronize (weak reject) Response

5 Clock Synchro Test (Management Client) >= 60 sec and <= 4h Drift > 60 s Synch Algo = 0? Synch Algo = 2? Reopens closed intervals? Synch Algo = 1? Synch Algo = 3 Schedule at a later time to avoid reopening a closed interval Reopens closed intervals? Write Event 12 in Schedule at a later time to avoid reopening a closed interval Execute Synch

6 Sincronizzazione Forte (Strong Clock Synchronization) Installer/Maintainer Client «Time Setting» command UNI/TS Device Mode is «NOT CONFIGURED»? Write UNIX Time 0-0: IC 2 Attr 2 See Clock Setting page Drift > 60 s Synch < 60s supported? Set B0 in Diagnostic Data is invalidated at SAC level when received with B0 bit set Execute Synchronization See Clock Synchro Test I/M page Send NAK Do not synchronize (weak reject) Response

7 Clock Synchro Test (Installer/Maintainer Client) >= 60 sec and <= 4h Drift > 60 s Synch Algo = 0? Synch Algo = 2? Reopens closed intervals? Synch Algo = 1? Synch Algo = 3 Write Event 12 in Reopens closed intervals? Execute Synch Send NAK

8 Riferimento UNI/TS UNI/TS UNI/TS Attività Drift residuo <= 2sec La propagazione dell'ora dal SAC ai deve avvenire con un errore massimo di 2 sec Sotto i 60 secondi il Gdm può non effettuare la sincronizzazione e/o può non generare l'evento di sincronizzazione Fra 60 sec e 4 ore [estremi inclusi], sincronizzazione con evento [o registri] Sopra le 4 ore, invalidare le letture Registrazioni a seguito di sincronizzazioni (non riaprire un periodo già chiuso) Il DC/GW può sincronizzare il GdM. Il GdM deve rifiutare i comandi di sincronizzazione dal DC/GW se la deriva in valore assoluto è maggiore o uguale a 60 secondi. In tal caso una condizione di errore deve essere fatto pervenire al SAC Si possono accettare comandi per uno scostamento totale di 60 secondi al mese Si assume [-11-4] che il timestamp contenuto nelle CF push sia sincronizzato con l'orologio interno del GdM a meno di un tempo LBT (<= 0.8sec) Conseguentemente tale timestamp è usato dal SAC come riferimento del clock del GdM e confrontato con il relativo timestamp allegato alla APDU da parte del GW/DC LEGGERA FORTE distribuzione di un riferimento temporale da parte del DC/GW con UNIX time impostazione/sincronizzazione del clock (via Clock-IC8A2 oppure via Clock-IC8M6) References UNI/TS UNI/TS UNI/TS Activity Residual Drift <= 2sec Propagation of clock from HES to the s shall happen with a maximum deviation of 2 seconds Below 60 seconds, the may not execute the synchronization and/or may not generate the relevant synchronization event Between 60 sec and 4 hours [extreme values included], the synchronization shall be executed and synchronization registers shall be updated. It is optional to generate synchronization events Above 4 hours, the readings (archive) shall be invalidated from the reception of the command onwards. Invalidation shall be active until a new valid clock setting / synchro command is received Intervals that are already closed cannot be opened (daily & billing) DC/GW can synchronize the meter The meter shall accept synchronization commands if the drift (in absolute value) is less than 60 seconds. The meter can accept commands up to a total drift of 60 seconds / month If meter is not synchronized in this way, the HES shall be informed Due to UNI/TS , it is assumed that the timestamp that is found in a PUSH CF is synchronized with the internal RTC of the meter, with the precision of a LBT timeout [approx 0.8 secs] This timestamp is subsequently used by the HES as a reference for clock and it is matched against the timestamp attached to that same APDU (PUSH CF) by DC/GW LEGGERA / LIGHT FORTE / STRONG distribution of a time reference by DC/GW using UNIX time setting / synchronization of clock (via Clock-IC8A2 or via Clock-IC8M6)

Documenti analoghi

Downloading and Installing Software Socio TIS

Object: Downloading and Installing Software Socio TIS compiler: L.D. Date Revision Note April 17 th 2013 --- For SO XP; Win 7 / Vista step Operation: Image A1 Open RUN by clicking the Start button, and