WEBVTT

00:00:00.000 --> 00:00:02.060
A meter reading tells you what happened.

00:00:02.060 --> 00:00:04.100
Its timestamp tells you when.

00:00:04.100 --> 00:00:08.220
If two meters have different clock times, comparing their events can give a misleading

00:00:08.220 --> 00:00:09.620
sequence.

00:00:09.620 --> 00:00:14.440
Keeping clocks aligned helps you compare logged demand, events and, on suitable

00:00:14.440 --> 00:00:18.540
analysers, disturbances across a site.

00:00:18.540 --> 00:00:23.700
RTC means Real Time Clock: the meter's own date and time.

00:00:23.700 --> 00:00:26.720
Synchronisation adjusts that clock against a reference.

00:00:26.720 --> 00:00:31.580
The reference, the communication path and the meter's supported functions all matter.

00:00:31.580 --> 00:00:35.260
Display resolution is not the same thing as clock accuracy.

00:00:35.260 --> 00:00:37.180
Start with software updates.

00:00:37.180 --> 00:00:42.180
In PAS, Monitor, then RTC shows the computer and meter times.

00:00:42.180 --> 00:00:44.920
Set updates the meter from the computer.

00:00:44.920 --> 00:00:51.500
For repeated updates, Logs, then Upload Scheduler includes RTC Synchronization Enable.

00:00:51.500 --> 00:00:55.940
The schedule must be enabled, PAS must remain running and online, and the meter must be

00:00:55.940 --> 00:00:56.880
reachable.

00:00:56.880 --> 00:00:59.600
The computer also needs a suitable time reference.

00:00:59.600 --> 00:01:04.340
PAS and eXpertPower can update the meter's clock by writing its time registers over

00:01:04.340 --> 00:01:05.260
Modbus.

00:01:05.260 --> 00:01:08.900
Think of this as software sending the meter a new date and time.

00:01:08.900 --> 00:01:12.580
The register layout and permitted write sequence depend on the model, so a detailed

00:01:12.580 --> 00:01:15.420
integration uses that meter's protocol guide.

00:01:15.420 --> 00:01:19.460
For ongoing updates, configure the service or schedule and check the result.

00:01:19.460 --> 00:01:23.640
Simply reading the meter, or enabling a communications client, does not prove that clock

00:01:23.640 --> 00:01:25.900
updates are taking place.

00:01:25.900 --> 00:01:29.320
SNTP stands for Simple Network Time Protocol.

00:01:29.320 --> 00:01:33.280
A supported meter periodically requests time from a network time server.

00:01:33.280 --> 00:01:38.240
The Pro series manual describes primary and secondary servers, a polling interval and an

00:01:38.240 --> 00:01:39.380
enable setting.

00:01:39.380 --> 00:01:43.480
It also requires SNTP to be selected as the clock source.

00:01:43.480 --> 00:01:48.280
For the documented EM235 and PM335 setup, the service uses

00:01:48.280 --> 00:01:49.760
the first Ethernet interface.

00:01:49.760 --> 00:01:54.160
Its network settings must allow it to reach the chosen server.

00:01:54.160 --> 00:01:57.060
PTP means Precision Time Protocol.

00:01:57.060 --> 00:02:01.280
It distributes a common time reference over a suitably designed network.

00:02:01.280 --> 00:02:06.720
The Pro series manual describes an IEEE 1588, version two

00:02:06.720 --> 00:02:09.760
grandmaster and compatible network switches.

00:02:09.760 --> 00:02:14.100
Matching the supported profile and network arrangement is part of the design.

00:02:14.100 --> 00:02:17.760
Connecting a meter to an ordinary Ethernet network does not establish precision

00:02:17.760 --> 00:02:19.420
synchronisation.

00:02:19.420 --> 00:02:23.440
IRIG-B carries a time code from a compatible master clock over a dedicated signal

00:02:23.440 --> 00:02:24.460
connection.

00:02:24.460 --> 00:02:29.460
As a specific example, the PM180 PMU documentation describes IRIG-B

00:02:29.460 --> 00:02:34.540
synchronisation and a PTP option requiring the appropriate Ethernet port.

00:02:34.540 --> 00:02:38.920
Use the instructions for the exact module, signal format and terminals.

00:02:38.920 --> 00:02:43.900
These options are not a promise that every SATEC meter has the same clock inputs.

00:02:43.900 --> 00:02:49.260
The ETC-II shows another approach: a gateway can make periodic clock updates

00:02:49.260 --> 00:02:52.700
to supported connected devices from its own clock.

00:02:52.700 --> 00:02:56.640
Its manual describes enabling this within the Data Server.

00:02:56.640 --> 00:02:59.000
The gateway itself must have the right time.

00:02:59.000 --> 00:03:03.600
A gateway's clock, its time-source inputs and the updates it sends downstream are three

00:03:03.600 --> 00:03:05.340
separate things to check.

00:03:05.340 --> 00:03:09.440
Time zone and daylight-saving settings are another part of the job.

00:03:09.440 --> 00:03:13.760
They control how time is interpreted or displayed locally; they do not repair an

00:03:13.760 --> 00:03:15.000
inaccurate reference clock.

00:03:15.000 --> 00:03:19.620
Check the installation's required time basis before comparing records.

00:03:19.620 --> 00:03:23.280
Avoid having different systems repeatedly set the same meter to different time

00:03:23.280 --> 00:03:24.600
references.

00:03:24.600 --> 00:03:26.960
Finish by checking operation.

00:03:26.960 --> 00:03:31.700
Read back the meter time, inspect the available synchronisation status and review

00:03:31.700 --> 00:03:33.560
relevant events.

00:03:33.560 --> 00:03:37.480
Check what happens if the time source or network becomes unavailable.

00:03:37.480 --> 00:03:42.060
Choose a method supported by the actual meter and the accuracy the application needs.

00:03:42.060 --> 00:03:46.020
That gives the timestamps meaning, from routine energy records to detailed event

00:03:46.020 --> 00:03:46.340
analysis.

